SAP Indirect Access Playbook

SAP Digital Access Licensing: A CIO Playbook

How SAP Digital Access works, where it triggers, and how to control indirect access exposure. The CIO playbook for measuring, modeling, and negotiating SAP indirect use without overpaying.

Now that you have the framework

Apply it to your SAP situation.

25 minute call with our SAP practice lead. We will walk through your specific renewal, audit, or contract and tell you what we would do next. No follow up sales pressure unless you ask for one.

HomeSAP HubWhite PapersSAP Digital Access Licensing: A CIO Playbook
The Short Version

If you read nothing else

Bottom Line

SAP Digital Access is a per document indirect access model. It replaced named user licensing for indirect access in 2018 but the named user model still applies in parallel. Most enterprises overpay because they price every integration as if it generates documents. The playbook is to measure first, classify rigorously, and negotiate the rate before SAP fixes it.

Key Takeaways

Five conclusions

Documents not users. Digital Access counts 9 document types created by indirect access. Most CIOs cannot say which apply.
Audit measurements vary. SAP's measurement tools count differently than internal tools. Run both. Reconcile before the audit.
Adoption Program is dated. The Digital Access Adoption Program offered discounts for migration. The program window has changed. Confirm current status before relying on it.
RISE bundles indirect. RISE pricing includes Digital Access in some scenarios. Confirm in writing what is included and what is not.
Integration design matters. Aggregating documents at the integration layer reduces the count. Design integrations with Digital Access in mind.
Recommendations by Role

What to do this quarter

Chief Information Officer
  1. Inventory every external system that writes to SAP
  2. Classify each integration against the 9 document types
  3. Set a Digital Access budget separate from named user spend
Procurement
  1. Negotiate the Digital Access rate at the contract, not at audit
  2. Confirm in writing what RISE includes for indirect access
  3. Refuse to convert audit findings into a Digital Access renewal
Architecture
  1. Run the SAP Passport and DAE measurement tools in parallel
  2. Aggregate documents at the integration layer where possible
  3. Document every API and bot that touches SAP for the auditor
The Framework

Eight ideas

1. The Document Model

Digital Access counts 9 document types: sales, invoice, purchase, service, manufacturing, quality, time management, financial, and material movement. Each has a definition. Most overcounting comes from misclassification. Build the map.

2. Direct vs Indirect

Indirect access is access to SAP data through a non SAP UI or system. The boundary moves with each integration. Document the boundary for every external system.

3. Measurement Tools

SAP provides the Passport and DAE tools. They measure differently. Internal tools measure differently again. Run all three. Reconcile in writing before the audit.

4. The Adoption Program

SAP offered the Digital Access Adoption Program with discounts for migration from named user to document. The program changes. Confirm current commercial terms with SAP before relying on the discount.

5. RISE and S/4HANA Bundles

RISE pricing sometimes includes Digital Access. The bundle terms vary. Confirm in writing what is included and what is not. Demand it on the order form.

6. Integration Design

Aggregation at the integration layer reduces document count. Batching, summarizing, and middleware design matter. Engineer for the licensing model, not just the data flow.

7. Audit Posture

Digital Access audits are part of standard SAP audits. Treat them as separate negotiations from named user findings. Refuse to bundle.

8. The Negotiation

Digital Access rate per document is negotiable. The volume tier is negotiable. The bundle with named user is negotiable. The audit settlement is negotiable. Run them as separate motions.

Reference

Acronyms

DADigital Access
DAEDigital Access Estimation
RISERISE with SAP
S/4S/4HANA
ERPEnterprise Resource Planning
APIApplication Programming Interface
Methodology & Sources

This white paper draws on Redress Compliance engagements, public vendor documentation, and the active Redress benchmark program.

Portrait of Fredrik Filipsson
About the Author

Fredrik Filipsson

Co Founder, Redress Compliance
Connect on LinkedIn →
SAP renewal twelve months out?
Request a Renewal Review
Related

Continue

Skyscraper
Ready?

Vendor proposals are not contracts.

We work for the buyer. Always. There is no other side of our table.

The Licensing Insider

Vendor intelligence, audit alerts, and negotiation insights once a month. No spam.