A buyer-side reading list on SAP licensing. RISE with SAP and the cloud-bundle posture. S/4HANA conversion and the FUE economics. Digital Access and the document-counted indirect surface. ECC end-of-mainstream and the migration timeline. BTP and the consumption credit model. The pages below cluster the firm’s commentary into a single editorial reading set.
SAP is, commercially, a portfolio in motion. The ECC perpetual estate sits inside the on-premise legacy, with mainstream maintenance set to close at year-end 2027 (extended maintenance to 2030 at a premium). S/4HANA sits as the successor platform, sold either on-premise on the named-user metric or under RISE with SAP as a cloud-bundled subscription. Digital Access sits across the portfolio as the indirect-use measurement model. BTP sits as the platform layer with its own consumption-credit construct.
The implication for procurement is that any SAP decision is now a transition decision. A renewal of ECC maintenance buys time but not destination. A migration to S/4HANA on-premise carries a named-user re-licensing exercise (Professional, Functional, Productivity). A move into RISE replaces the perpetual entitlement with a subscription priced on Full Use Equivalents (FUE). An Admodum SAP engagement therefore models the three destinations as a single buyer-side decision before signature.
This pillar groups the firm’s SAP commentary into ten editorial sections. Each section names the load-bearing mechanic, links the deeper spoke articles, and points to the practice page, the relevant white papers and the knowledge hub for the buyer who wants the engagement methodology.
RISE with SAP is the named SAP-as-a-service offering. It bundles the S/4HANA Cloud subscription, the hyperscaler infrastructure, the SAP Business Technology Platform credits, the SAP HANA Cloud and an SAP-managed operations layer into a single subscription contract priced on Full Use Equivalents.
The procurement implication is that the RISE contract collapses several previously separate commercial decisions (the S/4HANA licence, the hyperscaler infrastructure choice, the BTP commitment, the operations contract) into one publisher-anchored bundle. The buyer’s leverage shifts; the cost-comparability shifts; and the exit cost (from RISE back to on-premise or to GROW with SAP) becomes the named long-term risk.
The Admodum methodology models RISE against the on-premise S/4HANA alternative on a five-year total-cost basis (subscription cost, infrastructure cost, operations cost, BTP credits, exit cost) and structures the RISE contract with named protections on FUE conversion, ramp profile, customer-specific termination rights and Digital Access posture. The full reading sits in the RISE Economics paper.
The S/4HANA on-premise model retains the named-user metric: Professional, Functional, Productivity and Developer users, with a published price per category. The S/4HANA Cloud and RISE model converts the named-user portfolio to a Full Use Equivalent (FUE) basket: one FUE equals one Advanced User, five Core Users or thirty Self-Service Users (with published ratios at the contract date).
The buyer-side question is which named-user categories the workforce really sits in. SAP’s default assumption in a conversion exercise is the buyer’s legacy mix, which is often biased toward Professional (the highest-priced category) because legacy categorisation was permissive. The Admodum methodology audits the actual SAP-system use against the named-user categorisation, re-categorises the population on use evidence and converts to FUE on the corrected mix.
The reclassification arithmetic frequently moves the FUE count by twenty-to-forty percent against the publisher’s straight-line conversion. The full reading sits in the S/4HANA Conversion paper. The conversion exercise is also the natural moment to retire shelfware named users that have not signed in.
Digital Access is SAP’s licensing model for non-human (indirect) use of the SAP system: third-party applications, RPA bots, middleware, IoT devices and other systems that create documents inside SAP. The measurement is by counted document type (sales documents, invoice documents, purchase documents, manufacturing documents, financial documents, master-data documents, time-management documents, materials-management documents, quality-management documents).
The buyer-side question is the document-counting baseline. The SAP Digital Access Adoption Programme (DAAP) credits the buyer’s existing indirect-use entitlement against the document count under the new model, with a discount tier for early adopters. The Admodum methodology audits the document-creation surface against the named integrations, sizes the Digital Access entitlement on observed throughput (twelve-month rolling, peak-month-banded) and structures the DAAP conversion to retire any contested indirect-use exposure.
The full reading sits in the SAP Digital Access paper. Digital Access closure removes a material source of indirect-use audit exposure across the SAP estate.
SAP’s historical position on indirect access is the named-user requirement for any human who accesses SAP data, regardless of whether that access is through SAPGUI, a web portal, a third-party application, a custom user interface or a downstream analytics tool. The position generated the long-running Diageo dispute, which crystallised the buyer-side risk and accelerated SAP’s move to the Digital Access model.
The buyer-side methodology runs a two-axis read. The named-user axis covers humans, and the categorisation must reflect actual access (not the published role). The Digital Access axis covers non-human integrations, and the document count must reflect actual document-creation throughput. The two axes together close the indirect-use exposure.
The Admodum methodology audits both axes, structures the DAAP conversion where appropriate and documents the closing position inside the renewal. The full reading sits in the Digital Access paper above and runs inside the Audit Defence programme where an audit is already in motion.
SAP ECC mainstream maintenance closes at year-end 2027. Extended maintenance (at a premium) runs to 2030. After 2030, the buyer either holds an unsupported ECC estate, runs third-party support (Spinnaker, Rimini Street) or completes the S/4HANA conversion.
The timeline implication is direct. A conversion programme that opens in 2026 has a four-year runway against the 2030 cliff; a programme that opens in 2028 carries a high probability of premium extended maintenance plus an accelerated conversion in parallel. The Admodum methodology runs the timeline against the buyer’s programme capacity, the data-volume realities and the FUE-conversion arithmetic.
The decision between on-premise S/4HANA, RISE with SAP and GROW with SAP (the mid-market cloud offering) sits inside the timeline read. Each destination carries its own commercial posture, its own data-residency profile and its own exit cost. The destination is selected on the buyer-side modelling, not the publisher’s default recommendation.
SAP Business Technology Platform is the SAP platform layer for integration, extension, data and AI services. BTP is priced on Cloud Platform Enterprise Agreement (CPEA) consumption credits, which the buyer commits to over a multi-year term and burns against the catalogue of BTP services.
The buyer-side question is the commitment level and the catalogue mix. BTP credits are flexible across services but the credit allocation must be sized against actual planned use (integration runs, extension applications, data-pipeline volume, AI model calls), and the catalogue prices reset against the rate card on a published cycle. The Admodum methodology sizes the BTP commitment against the deployed integration and extension surface, structures the credit pool to absorb the demand variability and renegotiates the commitment at each renewal window.
BTP credits inside a RISE contract sit within the FUE economics; BTP credits outside RISE sit on a standalone CPEA. The two paths have different commercial leverage and different unwind profiles.
SAP audits run through the SAP Global Licence Compliance organisation. The audit reads the deployed named-user count against the contracted named-user entitlement, the deployed indirect-use integrations against the Digital Access position and the System Measurement (USMM and LAW) reports against the contract.
The buyer-side defence methodology starts before the audit notice. The named-contact protocol, the scope-limitation moves, the USMM and LAW run posture, the document-creation surface reconciliation, the legal review of the SGS findings and the negotiation of the closing position. The closing position frequently includes a Digital Access conversion at the DAAP rates.
The full methodology runs inside the Audit Defence programme and the related Digital Access paper. The audit closes on the buyer’s terms; the position is documented inside the renewal.
The SAP commercial relationship runs on a multi-year cycle: typically a three- or five-year RISE contract, a three-year on-premise maintenance renewal or a multi-year CPEA for BTP. The renewal window opens nine to twelve months before contract anniversary; the negotiation runs against SAP’s fiscal-year-end calendar (31 December); the signature closes inside the publisher’s named fiscal quarter.
The Admodum SAP practice runs the cycle across every SAP engagement, under one of three commercial frameworks: fixed fee for scoped deliverables, contingency / gainshare for measurable savings and annual retainer for continuous coverage across the cycle.
The SAP knowledge hub aggregates the wider reading: the practice page, the three white papers, named case studies, blog analysis and an FAQ block for the buyer who is two clicks from a senior advisor call.
The pillar groups SAP commentary into ten sections above. The spoke band below opens the forty named articles inside the cluster, each one a deep-read on a specific SAP mechanic. The white papers below sit alongside the pillar as the methodology deliverables; the practice page sits alongside as the engagement entry point.
A short follow-up checklist for the reader who is closing this page: visit the SAP practice for the engagement entry point; visit the SAP knowledge hub for the aggregated reading; request the three SAP white papers (RISE Economics, S/4HANA Conversion, Digital Access); or open a private conversation with a senior Admodum SAP advisor through /contact/.
Forty named articles inside the SAP cluster. Each one is a deep-read on a specific SAP mechanic, written from the buyer’s seat.
A senior Admodum SAP advisor will run the methodology through with your CIO, CFO, procurement team or audit response team on a private call. The engagement runs as fixed fee, contingency or annual retainer. Active SAP audits route immediately to the Audit Defence programme.