A Full User Equivalent, or FUE, is the SAP S/4HANA Cloud licensing unit that converts different user types into a single weighted count, where one Advanced user equals one FUE, five Core users equal one FUE, and thirty Self-Service users equal one FUE. The metric replaced the long list of named-user categories with a single subscription currency, and the conversion ratios are where the cost is decided. A workforce that looks expensive counted as individual professional users can become affordable once mapped to the right FUE mix, and the reverse is equally true when users are mis-categorized upward.
The conversion ratios
S/4HANA Cloud groups users into bands by the depth of their access, and each band converts to FUE at a fixed ratio. The lighter the access, the more users fit inside one FUE. The table below shows the standard conversion used to size a subscription.
| User type | Access level | Users per FUE |
|---|---|---|
| Advanced Use | Full transactional and configuration access | 1 |
| Core Use | Standard operational transactions | 5 |
| Self-Service Use | Occasional self-service tasks | 30 |
The total FUE requirement is the sum of each band's users divided by its ratio. A population of 100 Advanced, 500 Core, and 3,000 Self-Service users converts to 100 plus 100 plus 100, or 300 FUE, even though the headcount is 3,600. Getting each user into the correct band is the heart of FUE counting, and the band definitions build on the older named user categories.
Why categorization decides cost
SAP's default tendency, and the safest position for SAP in an audit, is to push users into higher bands. A user who only approves the occasional purchase order does not need Advanced access, but if the role is provisioned with broad authorizations, an audit can classify it as Advanced and multiply its FUE cost thirtyfold against a Self-Service equivalent. The mapping of roles to bands is therefore a license design decision, not an administrative one. The distinctions between the bands are covered in the professional versus limited versus self-service users guide.
The thirtyfold spread between the top and bottom band is what makes FUE both an opportunity and a trap. A buyer that classifies carefully captures real savings, because most workforces are heavy on light users and light on power users. A buyer that lets SAP classify, or that over-provisions access out of administrative convenience, pays many times over for users who barely touch the system. The FUE model rewards the buyer that treats user classification as an ongoing discipline rather than a one-time setup, and it punishes the buyer that does not.
Negotiation point: Audit your authorization design before SAP audits it. Users provisioned with more access than their role uses get counted in the higher FUE band whether or not they exercise that access. Right-sizing authorizations so each user holds only the access the role needs can move thousands of users from Advanced or Core into Self-Service, and on a large S/4HANA Cloud estate that re-banding is frequently worth more than the headline subscription discount. Do the authorization cleanup before the FUE count is locked into the contract.
FUE in a RISE or GROW subscription
FUE is the user-side currency inside the cloud subscriptions SAP sells today. In a GROW with SAP or RISE subscription, the committed FUE quantity is the central commercial term, set against the converted user count and renegotiated as the workforce grows. Over-committing FUE at signature wastes subscription value, and under-committing exposes the buyer to overage, so the count has to be modeled against a realistic band mix before the term is agreed. The full commercial framework sits in the SAP RISE negotiation guide and the SAP licensing guide, and our SAP advisory practice models the FUE mix before the subscription is signed.