The Full Use Equivalent (FUE) is the SAP-defined commercial seat unit inside RISE with SAP and GROW with SAP. The Admodum read on the conversion ratios, the inflation factor, the buyer-side evidence and the negotiation surface.
The Full Use Equivalent is the SAP-defined commercial seat unit against which the RISE with SAP and GROW with SAP subscriptions are priced. The Professional FUE is the reference unit (one FUE per Professional seat). The conversion table defines the ratios at which lighter on-premise user classes convert into the FUE count.
The conversion ratios published by SAP for the typical conversion table are: Professional at one FUE per seat; Functional at one fifth (one FUE per five Functional seats); Productivity at one tenth (one FUE per ten Productivity seats); Self-Service at one thirtieth (one FUE per thirty Self-Service seats). The Developer and Test categories convert under separate rules. The wider RISE bundle anatomy read sets the context for the FUE inside the bundle.
The conversion arithmetic typically produces an inflated FUE count against the equivalent on-premise named-user inventory. A buyer with two thousand Professional, ten thousand Functional and thirty thousand Self-Service named-user seats converts to two thousand plus two thousand plus one thousand, or five thousand FUEs. The same buyer running on-premise reads thirty thousand seats; the FUE count reads five thousand seat-equivalent, but the commercial weight against the Professional reference is heavier than the buyer's on-premise commercial weight against the Professional list price.
The inflation factor varies by category mix. A Professional-heavy estate experiences a smaller inflation; a Self-Service-heavy estate experiences a larger inflation, because the lighter classes convert into the FUE count at a higher implicit unit-cost weight than the on-premise unit-cost weight against the same activity. The buyer-side evidence is the per-seat commercial weight pre-and-post conversion. The RISE versus on-premise spoke compares the commercial weight at the route level.
The S/4HANA Cloud user-class set differs from the ECC named-user class set. The S/4HANA Cloud classes are: Advanced Use (Professional-equivalent), Core Use (Functional-equivalent), Self-Service Use (Self-Service-equivalent). The classes do not map one-to-one with the ECC categories. The conversion typically reads ECC Professional into Advanced, ECC Functional and Productivity into Core, ECC Self-Service into Self-Service, with a Developer track and a Test track outside the production seat count.
The re-mapping is a buyer-side negotiation surface. A buyer with an over-classified ECC estate (Professional seats that are used at the Functional level) can carry the over-classification into the FUE conversion if the re-mapping is automatic. The named-user recategorisation spoke reads the recategorisation mechanic that sits upstream of the FUE conversion.
The buyer-side recount evidence is the activity log: the ST03N transaction-code execution log (the buyer's record of every transaction code each user executed in the measurement window); the change-document log (the record of create, update and delete activity by user); the SM04 session-activity log (the active-session record); and the role-assignment dump from SU01 (the assigned authorisation profiles per user).
The evidence reduces the over-classified seat count. A user with no Professional-level transaction code execution in the measurement window is a Functional-level user; a user with no Functional-level transaction code execution is a Self-Service-level user. The evidenced recategorisation reduces the FUE count before the conversion ratio is applied. The Admodum read in the SAP system measurement spoke documents the measurement-window mechanic.
The FUE count carried into the renewal cycle compounds the inflation factor. The SAP-side renewal proposal reads the current FUE count and applies the contracted uplift. A buyer that accepts the conversion-ratio default at the original RISE transaction and does not run the recategorisation evidence at the renewal compounds the inflated FUE count across each renewal cycle.
The buyer-side artefact at the renewal is the same activity-evidenced recount, repeated against the current measurement window. The artefact gives the buyer the basis to reduce the FUE count at renewal rather than uplift on the inflated baseline. The SAP renewal cycle spoke reads the renewal-cycle mechanic in detail.
The FUE-conversion negotiation surface has five axes: the activity-evidenced recategorisation count (pre-conversion); the conversion-ratio applied to the lighter classes (the one-to-thirty ratio is more negotiable than the one-to-one reference); the Developer and Test exclusion from the production seat count; the carve-out for read-only users (the buyer's evidence on read-only versus write activity); and the BTPEA-credit interaction (where BTPEA-consuming users sit against the FUE count).
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 broader buyer-side methodology sits in the how we work overview.
The six components of the RISE with SAP subscription and the FUE commercial unit.
The activity-evidenced recategorisation mechanic that sits upstream of the FUE conversion.
The renewal cadence inside which the FUE count compounds across cycles.
A senior Admodum SAP advisor will read your activity-evidenced recategorisation, your conversion-ratio exposure and your renewal-cycle compounding on a private call. Active renewal moments route to Renewal Programme; the broader SAP reading sits in the SAP knowledge hub.