The Fundamental Distinction
SAP's indirect access and digital access frameworks exist to address the same underlying commercial question: how should SAP be paid when third-party systems, automated processes, or non-SAP users interact with SAP data and functionality? The two models answer this question through entirely different lenses — and choosing between them requires understanding both the mechanics and the economics of each.
The traditional indirect access model answers the question through people: it counts the number of identifiable users whose activity ultimately causes SAP data to be accessed or modified, and requires each such user to hold a named user licence. The Digital Access model answers the same question through documents: it counts the business documents created in SAP by external sources, using the DDLC (Digital Document Licence Consumption) metric, and assigns a price per document type.
Neither model is universally cheaper or more appropriate. The right choice depends on the nature of the integration scenario: the volume and predictability of document creation, the number of identifiable human users involved, and the specific document types triggered. In most large enterprises, both models apply simultaneously to different integration scenarios — a hybrid licensing approach is the norm, not the exception.
Head-to-Head Comparison
The following comparison covers the dimensions that matter most for buyers evaluating their indirect access licensing strategy.
| Dimension | Traditional Indirect Access (Named User) | Digital Access (DDLC) |
|---|---|---|
| What is counted | Identifiable users whose activity touches SAP data | Business documents created by external systems |
| Transparency | Low — SAP's interpretation of "indirect user" is broad and disputed | Higher — nine defined document types, measurable in advance |
| Read-only access | Potentially covered — SAP has historically argued read creates indirect obligation | Explicitly excluded — only document creation triggers cost |
| Cost scalability | Fixed per user — predictable but cannot scale down if users grow | Variable — scales with document volume, grows with automation |
| Best for | Low-volume scenarios with identifiable, countable external users | High-volume automated integrations, system-to-system data exchange |
| Audit risk | High — interpretation of "indirect user" is contested; back-claims common | Moderate — quantifiable, but volume spikes and line-item counting create exposure |
| DAAP available | No | Yes — up to 90% discount on initial document purchases |
| Applies to ECC | Yes — primary model for ECC environments | Optional via DAAP; mandatory in S/4HANA |
When Named-User Indirect Access Licences Work
The traditional named-user model remains appropriate — and often cheaper — in specific integration scenarios. The key factors that favour named-user licensing are a low and stable number of identifiable external users, and activity patterns that are user-driven rather than system-driven.
Scenario 1: Low-Volume External Portal Access
A company runs a supplier portal where 30 external vendors log in to view purchase orders and submit invoices. The vendors are identifiable individuals with stable accounts. Their interaction with SAP involves reading purchase orders (which does not trigger DDLC under Digital Access) and creating invoice documents. At 30 external users, the named-user licence cost (30 × approximately $50/user/month Limited User = $1,500/month = $18,000/year) may be lower than the Digital Access cost if those 30 vendors create high-volume, multi-line invoices. The breakeven calculation depends on monthly invoice volume and average line count per invoice.
Scenario 2: RPA Process with Bounded User Footprint
An RPA bot executes on behalf of a defined set of 10 finance users, submitting payments and creating journal entries in SAP. SAP may characterise the 10 human users behind the RPA as indirect users — requiring 10 named user licences for the finance process. If the RPA creates relatively few Financial Documents (DDLC type 08), the named-user approach could be cheaper. Model the actual document creation volume before choosing.
When Digital Access (DDLC) Is the Better Model
Digital Access becomes clearly superior as integration volume grows, as the number of external users becomes difficult to enumerate, and as automation replaces human-driven indirect activity. The model is structurally better suited to modern enterprise integration architectures.
Scenario 1: E-Commerce Integration Creating Sales Orders
A retailer's e-commerce platform creates Sales Orders in SAP for every online transaction — potentially tens of thousands per day. The individuals placing those orders are customers, not employees, and cannot realistically be assigned named user licences. Digital Access (DDLC type 01, Sales Documents, counted at line-item level) is the only commercially viable model for this scenario. The cost depends on negotiated document pricing and total annual order volume — but the named-user alternative (potentially millions of "indirect users") is not realistic.
Scenario 2: EDI Procurement Integration
A manufacturer's procurement system creates Purchase Orders in SAP via EDI from a supplier network. Thousands of POs with varying line counts are created automatically each month. No human user is directly creating these documents — they originate from the external procurement system. Digital Access (DDLC type 02, Purchase Documents) applies. Negotiating a sufficient pre-purchased document allotment at DAAP introductory pricing before adoption is the critical commercial step.
Scenario 3: IoT and Industry 4.0 Integrations
A manufacturer's production floor sensors and MES system create Manufacturing Documents (DDLC type 04), Material Documents (DDLC type 05), and Quality Management Documents (DDLC type 06) in SAP automatically based on production events. The volume is machine-driven and can reach millions of records per month. Digital Access is the only coherent model — named-user licensing for production machines is nonsensical. Buyers implementing Industry 4.0 integrations must model their DDLC consumption carefully before go-live.
Need a breakeven analysis for your indirect vs digital access decision?
Redress Compliance models both options against your actual integration landscape before you commit.The Hybrid Approach: Using Both Models Strategically
Most organisations with complex integration landscapes will use both models simultaneously — named-user licences for lower-volume, user-driven external access, and Digital Access DDLC licences for high-volume automated system integrations. This is not a compliance problem; it is the commercially rational approach and SAP explicitly supports it.
The strategic question is how to partition your integration landscape between the two models to minimise total cost. This requires a scenario-by-scenario analysis covering every external system and automated process that interacts with SAP. For each scenario: classify what document types are created and at what volume, calculate the annual DDLC cost at current market pricing, calculate the named-user equivalent cost, and select the lower-cost model. Aggregate across all scenarios to arrive at the total optimised licensing cost, then negotiate the resulting Digital Access document volumes and named-user entitlements as a coherent package.
Impact of S/4HANA Migration on the Choice
Organisations migrating from SAP ECC to S/4HANA — whether to on-premise S/4HANA, RISE with SAP, or SAP HANA Enterprise Cloud — face a model transition. In the ECC environment, the traditional indirect access (named-user) model governed. S/4HANA's commercial framework makes Digital Access the standard model for indirect activity. This transition is an opportunity to establish Digital Access licensing on the right commercial terms.
Pre-migration is the optimal time to adopt Digital Access via DAAP, taking advantage of the 90% introductory discount. The migration project itself often changes integration architectures — new Fiori interfaces may handle some scenarios previously covered by third-party portals, potentially reducing the indirect user count in the legacy model, while new BTP-based integrations may increase DDLC consumption. A Digital Access modelling exercise conducted as part of the migration planning workstream is not optional for organisations with material integration complexity.
Common Mistakes in Choosing Between the Models
The most frequent errors we observe in indirect versus digital access decisions share a common root: choosing based on assumptions rather than data. Organisations assume their user count is low without mapping every external system; assume digital access is cheaper without modelling line-item counting; assume the old named-user approach is "safer" when it actually carries higher audit risk due to SAP's broad interpretation of indirect user. All three assumptions can be wrong — and any one of them can result in a multi-million dollar exposure. The investment in an independent licensing model before you commit to an approach is invariably worthwhile.
Ready to make the right licensing choice for your SAP environment?
We build the model, run the numbers, and recommend the optimal approach — before SAP's auditors quantify your exposure.