Knowledge Hub · SAP

SAP. The buyer's reading room.

The SAP estate is governed by the RISE conversion arithmetic, the S/4HANA migration economics, the Digital Access indirect-access doctrine, the Named User reconciliation, the BTPEA scope, and the AnyPremise to RISE transition. This hub aggregates every piece of analysis Admodum has published on SAP. White papers, case studies, blog commentary, FAQ. All written from the buyer's side.

Visit the SAP practice Speak with a senior advisor
Sap licensing advisory

The RISE conversion runs on three arithmetics.

The credit table, the metrics translation, and the S/4HANA conversion economics. Every piece of analysis on this hub feeds the position paper that goes in front of SAP's account team.

i.
RISE with SAP
RISE conversion arithmetic, credit table treatment, FUE conversion methodology, services scope, hyperscaler treatment, GROW and RISE positioning and the closing economics of an AnyPremise to RISE transition.
Reading list →
ii.
S/4HANA conversion
Brownfield, greenfield and selective data transition, SAP Cloud Application Lifecycle Management, S/4HANA Enterprise Cloud and Private Cloud Edition, and the licence treatment at conversion from ECC and Business Suite.
Reading list →
iii.
Digital Access
Document-based indirect-access pricing, the historical indirect-access posture, the Digital Access Adoption Programme, document counting methodology and the contestation logic on third-party system integrations.
Reading list →
iv.
Named User reconciliation
Professional, Limited Professional, Productivity and Developer User categorisation, role-based mapping methodology, contractor and seasonal worker treatment, dormant-record cleanup and category over-assignment defence.
Reading list →
v.
BTPEA
Business Technology Platform Enterprise Agreement design, consumption model, application services entitlement, Integration Suite scope, Build entitlement and the AI Foundation commitment scope.
Reading list →
vi.
SAP audit defence
SAP Global Audit System engagement, scope contestation, evidence-gathering, user-category verification, Digital Access measurement, settlement negotiation and the closing letter that retires the audit.
Reading list →
Reading list · White papers
SAP research library.
All white papers →
RISE with SAP: the conversion arithmetic
Paper i · 28 pages
The credit table, the FUE conversion methodology, the services scope, the hyperscaler treatment, and the closing economics of an AnyPremise to RISE transition. Gated. Corporate email only.
Request →
Digital Access: the indirect-access playbook
Paper ii · 22 pages
Document-based indirect-access pricing, the Digital Access Adoption Programme, document counting methodology and the contestation logic on third-party system integrations.
Request →
S/4HANA conversion economics
Paper iii · 24 pages
Brownfield, greenfield and selective data transition, S/4HANA Cloud Editions, and the licence treatment at conversion from ECC and Business Suite. The credit table at conversion.
Request →
Named User reconciliation
Paper iv · 18 pages
Professional, Limited Professional, Productivity and Developer User categorisation, role-based mapping methodology, contractor treatment and category over-assignment defence.
Request →
BTPEA design
Paper v · 16 pages
Business Technology Platform Enterprise Agreement design, consumption model, application services entitlement, Integration Suite scope and AI Foundation commitment.
Request →
Documented outcomes · Case studies
SAP engagements on the record.
All 154 case studies →
RISE conversion at a global manufacturer
Case study i · RISE
AnyPremise to RISE conversion proposal at headline credit table. Custom credit redesign on services scope, hyperscaler exit option preserved, and FUE conversion reconciliation against functional populations. Close was on documented use cases, not the opening proposal.
Read →
Digital Access defence at a logistics group
Case study ii · Digital Access
Indirect-access audit on document counting methodology. Third-party system integration scope contested. Document counts reconciled against functional flows. Closing position protected the deployment without taking the opening exposure.
Read →
S/4HANA brownfield at a tier-one bank
Case study iii · S/4HANA
ECC to S/4HANA brownfield conversion economics. Credit table reconciled. Cloud Edition versus on-premises selected. Closing reconciliation between the legacy licence position and the new commitment.
Read →
Named User category reconciliation at a retailer
Case study iv · Named User
Professional and Limited Professional category mix reconciled against role-based mapping. Dormant records cleaned. Contractor entitlement reconciled. Category over-assignment defended at audit.
Read →
Analysis · Blog
Recent SAP commentary.
All blog →
RISE credit tables explained
Primer · RISE
The credit table is a translation. The translation runs through FUE conversion, services scope, hyperscaler treatment, and the AnyPremise reconciliation. Every credit has a denominator.
Read →
Digital Access: a six-year recap
Analysis · Indirect access
The indirect-access doctrine from the original judgments to the Digital Access Adoption Programme. Where the contestation logic lands in 2026.
Read →
S/4HANA: brownfield versus greenfield
Comparison · S/4HANA
The brownfield path retains historical complexity. The greenfield path resets the data model. Which path costs less depends on the legacy licence position.
Read →
Named User dormant-record cleanup
Tactical · Named User
Half of every Named User audit reads on records that should not be active. The cleanup runs against role-based mapping and a dormancy window.
Read →
Questions we hear
SAP FAQ.
When should a RISE conversion preparation cycle open?
Eighteen months before the AnyPremise renewal anchor. The credit table reconciliation, the FUE conversion methodology, the services scope, the hyperscaler treatment, and the closing economics all run inside the eighteen-month cycle. The Admodum Renewal Programme is the operating framework. The RISE white paper is the reading list.
What is the Digital Access contestation logic?
Document counting methodology, third-party system integration scope, and the historical indirect-access posture. The contestation runs against functional flows, not against the publisher's measurement tool. The white paper at Digital Access covers the methodology.
Is Admodum a partner or reseller of SAP?
No. Admodum is not a partner, reseller, or affiliate of SAP. The firm carries no SAP margin, no SAP referral commission, no implementation partner agreement, and no SAP audit subcontract. The buyer is the only client. See the firm page and the SAP practice page for the documented position.
How does Admodum charge on SAP work?
Three engagement models. Fixed fee on a scoped engagement, contingency tied to verified savings, and the annual retainer for an estate-wide programme. See Fixed Fee, Contingency, and Annual Retainer.
What is the retention regime on SAP papers?
Five years from engagement close. Every position paper, counter-position, evidence trail and closing memorandum is retained inside the firm. The buyer can request source workings at any point through the original advisor.

Subscribe to the SAP intelligence note.

Monthly. SAP-only. The RISE conversion arithmetic, the Digital Access posture, the S/4HANA migration economics, the Named User reconciliation, the BTPEA scope and the audit method we have seen in the last thirty days. Sent to corporate email addresses. No personal mail addresses.

Please enter a corporate email address. Personal addresses (gmail, hotmail, outlook, yahoo, icloud) are not accepted.
Corporate email required · Unsubscribe in one click
$510M
SAP Spend Advised
76
SAP Engagements
31
RISE Conversions
22
Audits Closed
18
SAP Papers
Independence
Admodum is not a partner, reseller, or affiliate of SAP, or of any other software vendor. No reseller margin, no referral commission, no audit subcontract.
Sap licensing advisory

Open a SAP conversation.

Practice covers RISE, S/4HANA, Digital Access, Named User, BTPEA and audit defence. Engagement structured as fixed fee · contingency · annual retainer.