How SAP counts documents for Digital Access licensing: the nine document types, their weights, common pitfalls, tracking methods, and negotiation strategies for CIOs and procurement teams.
This article is part of our SAP Digital Access: The Complete Guide. For DAAP negotiation strategies, see SAP DAAP: How to Evaluate, Negotiate and Avoid Cost Traps.
Introduced in 2018, SAP's Digital Access model addresses indirect use licensing by charging based on certain documents created via external systems, rather than on each outside user. SAP has defined nine specific document types that count whenever a non-SAP application creates them.
This approach ties licensing fees to tangible business transactions rather than to the number of people. Only new document creations count. Retrieving data (read-only) or updating records does not. And if one external event triggers multiple SAP documents, only the first document (the originating document) counts.
Example. An external system creating a Sales Order that later spawns an SAP Delivery and Invoice incurs one document charge (for the order) rather than three. This "originating document" rule is critical for accurate counting and cost control.
| Document Type | How It Is Counted | Licence Weight |
|---|---|---|
| Sales Document (e.g. Sales Order) | Each line item counts | 1.0 |
| Invoice Document (Billing) | Each line item counts | 1.0 |
| Purchase Document (Purchase Order) | Each line item counts | 1.0 |
| Service and Maintenance Document | Count per document | 1.0 |
| Manufacturing Document (Production Order) | Count per document | 1.0 |
| Quality Management Document | Count per document | 1.0 |
| Time Management Document | Count per document | 1.0 |
| Financial Document (Financial Posting) | Each line item counts | 0.2 (20%) |
| Material Document (Inventory Movement) | Each line item counts | 0.2 (20%) |
Financial and Material documents are weighted at 0.2 per line item (five of these count as one full document) to reflect their typically large volumes. An IoT sensor posting 1,000 inventory movements would consume the equivalent of 200 documents (1,000 x 0.2), whereas 1,000 sales orders would be counted as 1,000 documents.
Double-counting follow-on documents. Only count the originating document from an external trigger. If an external order in SAP leads to a delivery and an invoice (generated internally), only the order should be counted for licensing.
Mixing up indirect vs direct usage. SAP's system does not flag how a document was created. You must distinguish documents entered by regular SAP users (not counted for Digital Access) from those created by external systems, or you will over-count usage.
Misidentifying document types. If an external process creates a SAP document that falls into one of the nine defined types, it is counted. If it creates something outside those categories, it likely does not count. Clarify any ambiguous scenario with SAP to avoid surprises.
Incorrect volume forecasts. Guessing wrong on volumes can hurt. If you exceed your licensed count, you face unbudgeted true-up costs. If you over-buy, you pay maintenance on unused capacity. Forecast carefully and include a reasonable buffer.
Ignoring low-weight documents. Do not ignore financial postings or material movements simply because they count for only 20%. Extremely high volumes of these (e.g., IoT devices generating many stock movements) can still add up and consume your licence allotment.
Yes. Digital Access covers indirect usage (documents created by non-SAP systems), but all human users logging directly into SAP still require the usual named-user licences. Document-based licensing is an add-on for external activities, not a replacement.
They include Sales, Invoice, Purchase, Service and Maintenance, Manufacturing, Quality Management, Time Management, Financial, and Material documents. Together, these cover the most common ERP transactions created via external systems.
SAP does not label documents as "indirect" out of the box. Enable the SAP Passport feature to tag external transactions, or examine which user or interface created the document (e.g., a dedicated technical user for external orders).
Exceeding your licensed quantity means you are out of compliance. In an audit, SAP would require you to purchase additional blocks to cover the overage (potentially with back-dated maintenance fees). There is no automatic system cap.
No. SAP encourages customers (especially moving to S/4HANA) to adopt it, but you can continue with traditional licensing if that proves cheaper. Some organisations run a hybrid model: keeping named-user licences for certain legacy integrations and using Digital Access for new ones.