The history of indirect access from ECC to RISE.

Indirect access has been a recurring source of commercial friction between SAP and its customers across more than two decades of SAP commercial history. The dispute has reshaped its form multiple times, from the named user contracts of the R/3 era, to the headline indirect access disputes of the late 2010s, to the Digital Access Adoption Programme that SAP introduced in 2018, to the current shape of indirect and digital access inside the RISE with SAP commercial model. The history shapes the buyer position today, because the SAP contractual constructs of the current period carry the architectural memory of every prior cycle. A buyer that understands the history is materially better placed to negotiate the position in a current RISE proposal than a buyer that approaches indirect access as a single point construct.

The named user era and its commercial logic

The original SAP commercial model was constructed around the named user. Every human user of the SAP system was identified by a unique account, and the commercial right to use the system was sized by the count of named users in defined categories. The named user model was simple, transparent, and operationally enforceable, and it served the SAP commercial position effectively for the decade through which most enterprises consumed the SAP application primarily through human users at SAP terminals.

The named user model began to strain as the operating reality shifted. The strain surfaced first with the integration of third party applications, which exchanged data with SAP across interfaces that were not bound to a named user. The strain surfaced second with the rise of e commerce and self service portals, which routed end customer transactions into SAP through service accounts that aggregated many end users behind a single integration point. The strain surfaced third with the introduction of programmatic access through APIs, which exchanged transactions with SAP at volumes that bore no relationship to the named user envelope.

The SAP commercial position through this period held that any access to SAP data and any creation of SAP transactions required a commercial entitlement, and that the entitlement should be sized by the underlying activity rather than by the integration architecture. The buyer position held that the named user contract sized the entitlement at the contract signature, and that subsequent integrations did not require incremental entitlement provided the integrations operated within the technical envelope of the original contract.

The indirect access disputes of the late 2010s

The tension that had built across the named user era surfaced into the public record through a series of high profile indirect access disputes in the late 2010s. The disputes involved enterprises that had been using SAP integrated systems for many years without specific commercial provision for the indirect access. SAP audits identified the indirect transactions, scoped them against the SAP commercial model, and presented the affected enterprises with substantial back charge claims for the unentitled access.

The disputes were resolved through commercial settlements that varied substantially in magnitude and in structure. The published cases established that the indirect access exposure was real, that the audit identification was systematic, and that the back charge claims could be material relative to the original SAP contract. The disputes also established that the enterprise buyer position on indirect access was structurally weak, because the contractual basis for resisting the back charge was narrow and the operational evidence supported the SAP position in most cases.

The disputes shaped the buyer awareness of indirect access as a category of commercial exposure that required active management. The buyer community responded with a combination of architectural review, contractual renegotiation, and procurement discipline aimed at containing the indirect access exposure across the SAP estate.

The Digital Access Adoption Programme

SAP responded to the buyer community concern with the Digital Access Adoption Programme, which restructured the commercial position for indirect access around document level metering rather than around named users. The programme metered the indirect transactions by counting the SAP documents created by the integrated systems, and it priced the documents through a defined unit cost structure that was published in the SAP commercial catalogue.

The Digital Access model carried two advantages relative to the prior position. The first advantage was transparency, with the document count and the unit cost providing a defined commercial basis for the indirect access. The second advantage was forward looking, with the document model giving the buyer a defined metric to manage as the integration architecture evolved.

The Digital Access model also carried two structural weaknesses. The first weakness was the document definition, which was broad enough to include many transactions that the buyer did not consider commercially significant. The second weakness was the unit cost, which was set at a level that produced material commercial exposure for enterprises with high transaction volumes. The buyer community engaged with both weaknesses across the deployment of the programme, with mixed results in the negotiated outcomes.

Indirect and digital access inside RISE

The current shape of indirect and digital access inside RISE with SAP is constructed on top of the prior commercial models. The RISE contract typically includes a defined document envelope for the included digital access, with the envelope sized against the buyer historical transaction volume at the contract signature. The envelope is consumed against the actual document volume across the contract term, with overage charges applied if the consumption exceeds the envelope.

The current model preserves the document level metering of the Digital Access Adoption Programme, but the model also adds the complexity of the FUE conversion that the RISE model layers across the licence position. The document envelope and the FUE envelope are negotiated separately, but they interact across the integration architecture in ways that the SAP commercial team does not always make transparent. A buyer that negotiates the FUE envelope without simultaneously negotiating the document envelope risks signing a position that is balanced in the human user dimension and unbalanced in the digital access dimension.

The current model also includes price uplifts across the contract term that affect both the unit cost of the document envelope and the cost of overage charges. The indexation of the digital access cost is a meaningful component of the long term TCO, and the buyer position on the digital access indexation should be negotiated with the same discipline as the position on the platform indexation and the licence indexation.

Conclusion: the history shapes the position today

Indirect access has evolved across two decades of commercial history into the current digital access model inside RISE. The evolution carries the architectural memory of every prior dispute and every prior commercial settlement, and the current model reflects the resolution of tensions that the SAP commercial position and the buyer community position have negotiated through multiple cycles. A buyer that understands the history can negotiate the current position with the awareness that the SAP commercial team brings to the conversation. A buyer that approaches the digital access envelope as a single point construct in the current proposal will negotiate against a SAP team that has the full historical context, which is a structural asymmetry that the buyer should address before the conversation begins.