Key Takeaways
- SAP digital access optimisation in practice requires five concrete actions: independent measurement, exclusion identification, architecture review, commercial engagement, and governance embedding.
- Running USMM independently — before SAP does — gives you the foundational data to challenge any claim SAP subsequently raises.
- Exclusion categories typically reduce chargeable document counts by 30–65%; the most impactful are reversed documents, SAP-originated documents, and pre-DAAP legacy integrations.
- The commercial negotiation window with SAP is narrow and time-sensitive — understanding SAP's fiscal calendar, deal flow dynamics, and account team incentives directly affects the outcome.
- Embedding DAAP governance into change management processes prevents new digital transformation initiatives from inadvertently creating new digital access exposure.
The gap between understanding SAP digital access in theory and executing an optimisation programme in practice is where most enterprises get stuck. They know the DAAP model is complex, they suspect they are overpaying, but they do not know where to start, who should lead the work, or how to engage SAP without triggering a worse outcome than the status quo. This guide provides the practical methodology.
SAP digital access optimisation for enterprises requires cross-functional ownership — IT, legal, finance, and procurement all need to be aligned — and a sequenced approach that starts with data, moves to strategy, and culminates in commercial action. The following steps represent the methodology our SAP licence optimisation team applies across engagements, translated into a form that enterprise ITAM managers and SAP CoE leaders can execute.
Step 1: Run Your Own USMM Extraction Before SAP Does
The single most important practical action in any digital access optimisation programme is to run your own USMM extraction before SAP runs it for you. USMM (transaction USMM in SAP ECC or S/4HANA) produces a system-level measurement report that SAP uses to track named users and document creation events. Running it yourself first gives you three critical advantages: you understand your own data before SAP presents it to you, you can identify anomalies and contestable items before they become formal claims, and you control the narrative of your compliance position.
Schedule USMM Extraction
Run transaction USMM on your SAP ECC or S/4HANA production system. Export the full measurement report — named users and document counts by type. Do this quarterly to establish a baseline trend.
Extract Document Creation Logs at Integration Level
USMM shows totals. To identify which integration or application is creating which document volume, run ABAP extraction reports against the relevant SAP tables (VBAK for sales orders, EKKO for purchase orders, BKPF for journal entries, etc.). Map creation source to integration point.
Cross-Reference with System Landscape Directory (SLD)
The SLD contains the list of systems registered as connected to your SAP landscape. Cross-reference this against your own integration inventory. Systems not in the SLD but actively creating documents represent an undisclosed liability risk — fix this before SAP finds it.
Reconcile Against DAAP Contract Scope
Not all systems in your SLD are necessarily covered by your DAAP agreement. Review the agreement's scope provisions — which document types are included, which systems are named, and whether any legacy indirect access provisions apply to specific integrations.
Step 2: Build Your Exclusion Inventory
The exclusion inventory is the single most valuable commercial asset you can build in a digital access optimisation programme. It is a documented list of document-creation events that appear in your USMM count but should not be included in your DAAP obligation, with a supporting rationale for each category.
The following exclusion categories are consistently available across enterprise SAP estates. Each requires evidence — ABAP extraction data, integration logs, or contract provisions — to be defensible in a SAP discussion.
| Exclusion Category | Typical Volume Reduction | Evidence Required |
|---|---|---|
| Reversed/cancelled documents | 8–18% | ABAP report showing creation and same-day or next-day reversal with no business consequence |
| SAP-originated background documents | 5–20% | SAP program name in creation log (RSAP*, RKANBU*, batch input IDs) |
| SAP middleware-originated (PI/PO, Integration Suite) | 5–15% | Message routing logs showing SAP-licensed middleware as source |
| Pre-DAAP legacy integrations | Varies significantly | Integration go-live date predating DAAP agreement; legacy indirect access clause in original contract |
| Test/dev/sandbox system documents | 2–8% | System ID confirmation that source system is non-production |
| Documents with no downstream business impact | 3–10% | Process documentation showing documents created but never posted or approved |
Field Experience
In one global retail engagement, the exclusion inventory reduced the chargeable document count from 8.4 million annually to 3.1 million — a 63% reduction — before we had even engaged SAP commercially. The largest single exclusion: 2.8 million e-commerce order creation events that were generated by an integration pre-dating the DAAP agreement, covered under a legacy named-user indirect access clause that remained operative per the contract's supersession provisions.
Step 3: Map Your Integration Architecture for DAAP Exposure
Once you have a baseline document count and an exclusion inventory, the next step is to map your integration architecture against DAAP exposure — not just for the current state, but for the future state, given digital transformation roadmaps.
A practical integration DAAP assessment involves the following for each integration point in your landscape:
- Which SAP document types does this integration create, and at what volume?
- Is this integration covered by existing DAAP terms, legacy indirect access provisions, or neither?
- What is the business criticality of this integration — can it be redesigned without operational impact?
- If it is chargeable, what is the annual cost at current DAAP pricing, and does it have a trajectory?
- Are there architectural alternatives (SAP BTP routing, event-driven consolidation, API design changes) that would reduce the DAAP document count without reducing business value?
This mapping exercise typically surfaces 3–5 high-priority integrations that represent 70–85% of total digital access exposure. Concentrating optimisation effort on these integrations maximises return on time invested. For detailed guidance on integration-specific strategies, see our complete guide to SAP digital access optimisation.
Step 4: Build Your Commercial Negotiation Position
With independent measurement data, an exclusion inventory, and an integration architecture assessment in hand, you are ready to engage SAP commercially. The goal is either a DAAP agreement amendment (if you have a current DAAP agreement that is overpriced) or a structured DAAP negotiation (if you are entering DAAP for the first time or facing a true-up claim).
The commercial negotiation position should include:
- Your adjusted document count — total USMM count, less all defensible exclusions, with supporting evidence. Present this as your proposed DAAP baseline, not as a counter-argument to a SAP claim.
- Your future-state volume model — a 3–5 year projection of document volumes under your current integration roadmap. If the projection shows declining volumes (due to architecture changes or consolidation), this creates a commercial argument for lower DAAP pricing.
- Competitive context — SAP's competitive environment. The degree to which your enterprise is genuinely evaluating alternative platforms (Oracle Fusion, Microsoft Dynamics, Salesforce for CRM/ERP) affects SAP's willingness to make concessions.
- Timing — initiate commercial discussions in Q3 (July–September) or early Q4 (October–November) of SAP's fiscal year. SAP's December 31 fiscal year-end makes Q4 the highest-leverage negotiation window.
⚠ Do Not Negotiate Without Independent Representation
SAP's account teams are highly skilled at extracting maximum value from commercial discussions. Enterprise procurement teams negotiating DAAP without an independent adviser consistently achieve worse outcomes than those who engage specialist representation. The negotiation dynamics are asymmetric — SAP does this every day; your team does it once every 3–5 years.
Our SAP contract negotiation team provides dedicated support for DAAP renegotiations, including benchmarking against current market rates, structuring the negotiation sequence, and representing your interests in SAP discussions.
Step 5: Embed DAAP Governance in Change Management
The final and most often neglected step is embedding DAAP governance into your enterprise change management processes so that future digital transformation initiatives do not inadvertently create new digital access exposure without commercial awareness or budget approval.
Practical DAAP governance includes:
- A mandatory DAAP impact assessment for any new integration project connecting a third-party application to SAP — typically a two-page template completed by the integration architect and reviewed by the SAP CoE or ITAM team.
- A quarterly document count review, comparing current USMM extraction against the baseline, with escalation triggers if volumes exceed agreed thresholds.
- A DAAP clause in the procurement process for all new SaaS applications that may integrate with SAP — requiring vendor confirmation of integration approach and estimated document creation volume.
- An annual DAAP contract review — comparing your actual document count against contracted volumes, with early identification of true-up exposure or overpayment.
Enterprises with effective DAAP governance consistently outperform those without it in three metrics: lower average digital access cost per document, faster resolution of SAP compliance queries, and fewer surprise true-up claims. The governance investment — typically 2–4 days of ITAM team time per quarter — pays for itself many times over in avoided exposure.
For cost reduction strategies specifically, see our article on SAP digital access cost reduction strategies. For a complete action checklist, see our digital access optimisation checklist and action plan.
Get Your Digital Access Baseline in 5 Days
Our rapid DAAP diagnostic gives you an independent document count, exclusion inventory, and commercial negotiation position in five working days. Book a free consultation to scope your engagement.
Book Free DAAP Diagnostic →Frequently Asked Questions
Digital access optimisation requires joint ownership between the SAP CoE or ITAM team (technical measurement and architecture), IT procurement or commercial (contract management and negotiation), and legal (contract interpretation). In practice, the SAP CoE or a senior ITAM manager typically acts as programme lead, with legal and procurement engaged for the commercial phase. Without executive sponsorship at CIO or CFO level, the programme rarely achieves material commercial outcomes.
A full independent DAAP measurement for an enterprise with 5,000–20,000 SAP users and 10–30 third-party integrations typically takes 3–5 weeks. This includes USMM extraction, integration log analysis, exclusion inventory construction, and reconciliation against contract scope. Rapid diagnostic engagements (5 days) provide a preliminary view sufficient to structure a commercial negotiation without the full forensic depth.
If you are already in a formal SAP digital access audit, the immediate priority is to pause any voluntary data submission to SAP while you run independent measurement. You have contractual rights to review SAP's measurement methodology and to submit your own counter-measurement. Engaging independent advisers immediately — before the audit progresses to a settlement discussion — significantly improves outcomes. See our SAP audit defence service for dedicated audit response support.
Yes, in some scenarios. SAP BTP (Business Technology Platform) integration services — specifically Integration Suite — can act as a middleware layer between third-party applications and SAP that changes the licensing character of document creation events. Whether this approach is beneficial depends on your specific DAAP contract terms, the volume and type of documents involved, and the cost of BTP licensing relative to the DAAP savings. An independent analysis of the cost-benefit is essential before committing to this architecture change.