RISE with SAP is a bundled subscription wrapping S/4HANA Cloud, hyperscaler infrastructure, SAP-managed operations, the BTPEA credit and selected tools. The Admodum read on the components, the FUE conversion, the hyperscaler choice and the negotiation surface.
RISE with SAP is sold as a single subscription that wraps six components. The principal component is S/4HANA Cloud (Private Edition is the typical RISE variant; Public Edition is the smaller-footprint variant). The second component is the hyperscaler infrastructure (the compute, the storage, the network on a selected hyperscaler). The third component is the SAP-managed operations (the basis administration, the database operations, the patching, the upgrade management).
The fourth component is the BTPEA credit (a Business Technology Platform Enterprise Agreement credit pool with an annual consumption value). The fifth component is the SAP Signavio entitlement (process intelligence and process management tooling). The sixth component is the SAP LeanIX entitlement (the enterprise architecture management tooling, added to the RISE bundle in 2024). The wider SAP BTP overview spoke reads the BTPEA in the RISE context.
The RISE commercial unit is the Full Use Equivalent (FUE). A FUE is the SAP-defined seat unit against which the RISE subscription is priced. Existing on-premise named users are converted into FUEs using a ratio table: the Professional User typically converts at one FUE, the Functional User typically converts at one fifth of a FUE, and the Productivity, Self-Service and other lighter classes convert at smaller fractions (typically one-thirtieth for the Self-Service user).
The FUE-conversion arithmetic is the central commercial mechanic. A buyer with ten thousand Professional Users converts to ten thousand FUEs; a buyer with two thousand Professional plus ten thousand Functional plus thirty thousand Self-Service converts to approximately five thousand FUEs. The arithmetic typically inflates the seat-equivalent count over the named-user inventory by twenty to forty percent due to the conversion mechanic. The wider FUE conversion arithmetic spoke reads the conversion in commercial detail.
The hyperscaler choice inside RISE is a configurable parameter. SAP supports AWS, Microsoft Azure and Google Cloud for the RISE hyperscaler infrastructure (with Alibaba Cloud in selected geographies). The standard RISE construct positions SAP as the hyperscaler-relationship holder; the buyer does not contract with the hyperscaler directly for the RISE-allocated capacity.
The implication is the loss of the buyer's direct commercial reading with the hyperscaler (the buyer's existing EDP, MACC or hyperscaler-side discount surface does not apply to the RISE-allocated capacity). The PCE (Private Cloud Edition outside the RISE wrapper) route retains the buyer-as-hyperscaler-customer relationship. The wider SAP hyperscaler choice spoke reads the choice in detail; the wider SAP Private Cloud Edition spoke reads the PCE alternative.
The conversion credit applies the existing on-premise licence value as a credit against the RISE subscription. SAP's policy values the on-premise estate at a defined recovery rate (the percentage of the original licence value that converts to RISE credit). The conversion-credit calculation is the principal commercial lever in the transition negotiation: a higher recovery rate reduces the net-new RISE commitment.
The buyer-side artefact is the on-premise valuation schedule: every licence, every original price, every Software Maintenance attachment, every shelfware position. The wider SAP cloud conversion credits spoke reads the conversion-credit mechanic in negotiation detail.
RISE is one route to S/4HANA, not the only route. The alternative routes are: GROW with SAP (the Public Edition variant for smaller, standardised footprints), the SAP PCE (the Private Cloud Edition outside the RISE bundle, with the buyer holding the hyperscaler relationship), the on-premise plus BYO-hyperscaler route (S/4HANA on-premise licences on hyperscaler infrastructure that the buyer contracts directly), and the brownfield-stay route (the conversion of the existing ECC estate to on-premise S/4HANA without a cloud transition).
Each route has a distinct commercial profile, a distinct operating profile and a distinct exit profile. The wider RISE versus on-premise and GROW with SAP spokes are the route-comparison reads.
The RISE negotiation surface has six axes: the FUE count (the conversion ratio, the inflation factor, the buyer's evidence on actual seat use); the hyperscaler choice and the infrastructure pricing; the conversion-credit recovery rate; the BTPEA credit value (and the BTP consumption forecast against it); the term and the renewal-cycle uplift; and the exit terms (the post-RISE return-to-on-premise route, the data-portability terms, the notice period).
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The seat-conversion mechanic that sits at the heart of the RISE pricing.
The route-comparison framework that reads RISE against the alternatives.
The conversion-credit mechanism that values the existing on-premise estate.
A senior Admodum SAP advisor will read your existing on-premise estate, your FUE-conversion arithmetic and your hyperscaler context against the RISE construct on a private call. Active renewal moments route to Renewal Programme.