Cluster III · Article ii of forty

SAP Digital Access, the indirect-access mechanism.

SAP Digital Access charges for documents created in the SAP digital core by external systems or users. The Admodum read on the nine document types, the measurement protocol, the document classification trap and the negotiation surface.

ClusterSAP
Read13 minutes
AuthorDiane K. Caldwell
PublishedJanuary 2025
UpdatedApril 2025

Key takeaways

Section i

The mechanism replacement.

Digital Access replaced the previous SAP indirect-access model (which counted external-system users as if they were SAP named users). The replacement was a recognition that the named-user model could not accommodate machine-to-machine, third-party-system and customer-portal access scenarios at scale: counting customers visiting a portal as named users typically produced commercial outcomes neither side could sustain.

The Digital Access model counts documents instead: a sales order created in the SAP digital core by an external e-commerce platform is a Digital Access document; a financial entry created in the digital core by a third-party financial-consolidation system is a Digital Access document. The wider indirect-access history spoke reads the model transition in detail.

Section ii

The nine document types.

The Digital Access model defines nine document types. The Sales document covers sales orders. The Invoice document covers billing documents (the invoice on the AR side, the invoice receipt on the AP side). The Purchase document covers purchase orders. The Service and Maintenance document covers service orders, work orders and maintenance orders. The Manufacturing document covers production orders.

The Quality Management document covers inspection lots. The Time Management document covers time and attendance entries. The Financial document covers financial postings (excluding the postings already produced by the Sales, Invoice and Purchase documents). The Material Movement document covers material movement records.

Section iii

The price asymmetry.

The nine document types are not priced equally. The Sales, Invoice and Purchase documents carry the principal per-document price. The other six document types are sold at materially lower per-document rates. The asymmetry is structural: the Sales, Invoice and Purchase documents are the high-frequency, externally-driven document types that the model is principally designed to capture.

The buyer-side reading on the asymmetry is the mix reading: an estate with heavy Manufacturing and Material Movement document volume reads commercially differently from an estate with heavy Sales and Purchase document volume. The mix shapes the commercial outcome more than the absolute document count. The wider SAP system measurement spoke reads the measurement protocol against the mix question.

Section iv

The measurement protocol.

The measurement protocol is the SAP Passport report (the report supplied via the Digital Access Adoption Programme, with the option to run it as a standalone exercise outside the DAAP). The report runs against the SAP digital core for a defined period (typically twelve months) and counts the documents created in the period by the in-scope document types. Each document carries a classification: the document type, the creator (SAP-licensed user, machine user, external system), the source.

The classification rules read against an explicit SAP ruleset; the buyer can run a parallel classification and contest individual document classifications where the audit-side reading differs from the buyer-side reading. The wider DAAP conversion spoke reads the Digital Access Adoption Programme as a discount-mechanic.

Section v

The classification trap.

The principal classification trap is the SAP-user-created-via-API document. A document created in the digital core via an API call by an integration platform (a Boomi, a MuleSoft, an SAP Integration Suite flow, a custom integration) that authenticates as an SAP-licensed user is, in many readings, an SAP-licensed-user document and not a Digital Access document.

The audit-side reading is the converse: the authentication identity is incidental; the document is created from outside the SAP user-interface boundary, so it is a Digital Access document. The buyer-side artefact is the integration-platform inventory: every integration, every authentication identity, every document type produced, every classification basis. The wider SAP audit defence spoke reads the contest protocol.

Section vi

The negotiation surface.

The Digital Access negotiation surface has five axes. The document-count baseline (the measured-period document count, against an agreed scope). The document-type mix (the proportion of the count that falls in the three high-priced types). The classification position (the disputed documents, the API-created documents, the chain documents that produce multiple downstream documents from a single source). The DAAP discount (the SAP-offered discount for early adoption of the Digital Access model). The contract construct (the baseline document allocation, the renewal posture, the over-baseline true-up mechanic).

Digital Access is a document-counting mechanism, not a user-counting mechanism. The mix shapes the outcome more than the count.

The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.

More from the SAP cluster

Continue the reading.

Article iii

Indirect access, the history

The historical model that Digital Access replaced and the reasons for the change.

Article iv

DAAP conversion

The Digital Access Adoption Programme as a commercial discount-mechanic.

Article xxi

SAP system measurement

The measurement protocol against which the Digital Access count is established.

Engage

Read your Digital Access position with a senior advisor.

A senior Admodum SAP advisor will read your Passport report, your integration-platform inventory and your document classification position against your renewal and audit posture on a private call. Active audit moments route to Audit Defence.

Independence
Admodum is not a partner, reseller, or affiliate of SAP, or of any other software vendor. No reseller margin, no referral commission, no audit-subcontract relationship.