Executive Clarity · CFO & Finance

The licensing decision inside RISE vs GROW

Behind the deployment-model debate sits a quieter decision with longer consequences: Private Cloud sells you a capacity currency, Public Cloud sells you business roles. Same S/4HANA core — two commercial logics.

The question

When your organisation chooses between SAP's Private Cloud (RISE) and Public Cloud paths, what exactly are you buying — and which commercial mechanics will still be shaping your costs, sizing and flexibility in year four of the contract?

Decision factors

The documented facts — Private Cloud sells FUEs

  • Private Cloud licensing runs on the Full Usage Equivalent (FUE) — a single capacity currency instead of a price list of named-user types. SAP's published conversion: 1 FUE covers 1 Advanced user, 5 Core users or 30 Self-Service users; a Developer draws 2 FUEs.
  • FUE quotas can be re-allocated during the term — a departing power user's share can become five occasional users without a contract change. This is the model's genuine flexibility.
  • User classification is not guesswork: SAP's Trusted Authorization Review (STAR) evaluates thousands of authorization combinations to sort each user into Advanced, Core or Self-Service — an automated evidence base for sizing the FUE contract before you sign it.
  • The quiet coupling: your system sizing is bound to your FUE volume. SAP's service description ties each infrastructure tier — and the HANA memory that comes with it — to FUE ranges. Additional HANA memory can be subscribed separately in fixed units, but the baseline you stand on is set by the users you licensed.

The documented facts — Public Cloud sells roles

  • The current Public Cloud packages license role-based user types — Finance and Supply Chain in Base and Premium variants, plus a Combo user for people working across both — instead of an abstract capacity unit.
  • The entitlement model is nested: a higher-tier user automatically contains the rights of the tiers below it within its domain. Licence planning becomes a mapping of business roles to packages, not a conversion arithmetic.
  • The commercial floor is a pooled Base-user minimum, shared across the Base types — lowered in January 2026 from 25 to 15 users, which reads as SAP opening the model further down the midmarket.

The documented facts — Digital Access counts the same way in both

  • When third-party systems, bots or devices create documents in the SAP core, Digital Access licensing applies — and its counting logic is identical in both worlds: only the initial creation of a document counts; reading, updating and deleting are free.
  • Follow-on documents generated inside S/4HANA from an already-counted document are not counted again, and SAP-application-to-SAP-application traffic does not draw from the counter.
  • Nine document types carry weighting factors: financial and material document line items count at 0.2; sales, purchase, invoice, service and the other operational types at 1.0.
  • Commercially the wrappers differ: Public Cloud editions carry included document allotments, while in Private Cloud Digital Access is typically a separately licensed item on top of the FUE contract. The included volumes and thresholds are contract-specific — read yours, not a blog.

Inference

  • The FUE model optimises for portfolio flexibility — but the sizing coupling means unused user quota is not simply waste you can trim: it can be load-bearing for the infrastructure tier your operation stands on. Licence optimisation and system sizing are one negotiation, not two.
  • The Public Cloud model optimises for procurement legibility — buying centres recognise themselves in the packages. The price of that legibility: classification moves from an automated authorization review to a functional mapping of what people actually do, and misclassification risk moves to the customer's side of the table.
  • Digital Access is where architecture decisions become invoices. An integration pattern chosen by a solution architect — direct third-party posting versus SAP-to-SAP routing — changes what the meter reads. The counting rules are public and stable; what varies is whether anyone in your programme owns them.

Point of view

Licensing is treated as procurement's last mile — reviewed after the deployment model, the partner and the scope are already chosen. That order is backwards. The commercial mechanics above are not consequences of your transformation decisions; they are inputs to them. An organisation that understands FUE mechanics, role nesting and Digital Access before the deployment-model decision negotiates all three as one system — and avoids discovering in year two that its "flexible" contract has a load-bearing wall exactly where it wanted to cut.

Monday-morning questions

  • Who on our side can explain, unaided, what one FUE is — and what our proposed FUE count implies for the infrastructure tier we are being offered?
  • Have we run an authorization-based user classification (STAR or equivalent) on our real usage — or are we sizing the contract on role titles and optimism?
  • For a Public Cloud path: who mapped our actual business roles to Base, Premium and Combo types, and what evidence backs the mapping — and what classification tooling does SAP offer for it?
  • Which of our integrations create documents in the SAP core, and who has read the Digital Access schedule in our draft contract — including what is already included?
  • If our user mix changes by a third in either direction, what does each model let us do mid-term — and what does it force us to keep?

Where this sits in the decision chain

This page is the commercial layer beneath the RISE vs GROW decision and the Public vs Private Cloud suitability question. The numbers flow into the business case and TCO baseline; the partner sitting across the table is examined in partner economics; licence governance after go-live belongs to the operating discipline in transformation governance. A practitioner's view of licence governance, metrics and audit readiness: Auf einen Espresso mit Svenja Vorwerk.

Sources

Further reading: the comparison that prompted this page — "SAP Lizenzmodelle im Vergleich: Private Cloud (RISE) vs. Public Cloud (Business Suite Packages)" by Rebecca Froehlich-Tuthill (LinkedIn, July 2026) — a licence-management specialist's deeper cut into the same mechanics, in German.

Editorial standard: vendor facts, inference and point of view are kept separate above; every fact is drawn from SAP's published documentation, and figures we could not verify against public sources are omitted. No prices appear here by design — commercial terms belong in your contract, not on a website. Published 2026-08-04 · By Andreas BORN.