| S/4HANA Cloud use type | FUE per user | Users per FUE |
|---|---|---|
| Developer access | 2 | 0.5 |
| Advanced use | 1 | 1 |
| Core use | 1/5 | 5 |
| Self-service use | 1/30 | 30 |
Source: SAP SE, RISE with SAP S/4HANA Cloud – Licensing Overview (March 2021, public SAP User Group webinar deck), slides 8 and 22. The legally binding definitions sit in your SAP S/4HANA Cloud Service Use Description and order form, which can differ by offering, edition, and date — confirm before you rely on a number.
Scope: this models the RISE with SAP / SAP S/4HANA Cloud FUE framework as SAP described it in the March 2021 deck cited above. It does not automatically apply to ECC named-user contracts, line-of-business cloud products, or every current SAP order form. Check how your own order form defines an FUE before relying on a result.
Users → FUE calculator
Enter how many users you need of each use type. Leave a field blank for zero.
- Exact total
- 0 FUE
- Decimal
- 0.00
- Rounded up (planning scenario)
- 0 FUE
Rounding up is a RenewalIQ planning assumption, not an SAP rule; SAP's deck does not say how fractions are treated. Your order form decides that.
Renewal or RISE decision within 120 days, or does your mapping not match the order form? Book a free 15-minute triage → (your inputs stay in this browser)
How many users does my FUE pool cover?
Enter your contracted FUE pool and pick one use type. The tool holds the other three counts above fixed and works out how many users of that type fit. The answer replaces the count you entered for that type rather than adding to it, and it doesn't propose a mix: you choose which type to flex.
Classic named users → S/4HANA Cloud use types
Moving from ECC or on-premise S/4HANA to RISE? Enter your classic named-user counts. Each row defaults to the use type SAP's deck shows as typical for that license. Change the target wherever a user's real activity differs. Classification goes by what each person actually does in the system, not by the license they hold today.
| Classic license (material no.) | Users | Target use type | FUE |
|---|---|---|---|
| 7003012 | 0 FUE | ||
| 7003012 | 0 FUE | ||
| 7017377 | 0 FUE | ||
| 7017378 | 0 FUE | ||
| 7003015 | 0 FUE | ||
| 7003013 | 0 FUE |
- Exact total
- 0 FUE
- Rounded up (planning scenario)
- 0 FUE
SAP's deck maps the SAP Professional User to advanced use for finance roles and to core use for sales, R&D and production-planning roles, which is why it gets two rows here. Users who only work in a separately licensed line-of-business solution may not need an S/4HANA use type at all. This crosswalk is a planning aid. SAP's own transition offer and your order form decide the result, and classic licenses outside SAP's slide (Limited Professional, for example) need a role-by-role decision.
Same 1,000 users, 47% fewer FUEs
An illustrative estate of 1,000 users, before and after classifying each person by what they actually do in the system. Headcount doesn't change. The FUE count falls because users move down to the cheapest use type their activity supports.
| Use type | Users before | Users after | Users per FUE | FUE before | FUE after |
|---|---|---|---|---|---|
| Developer access | 10 | 10 | 0.5 | 20 | 20 |
| Advanced use | 355 | 154 | 1 | 355 | 154 |
| Core use | 545 | 345 | 5 | 109 | 69 |
| Self-service use | 90 | 491 | 30 | 3 | 17 |
| Total | 1,000 | 1,000 | 487 | 260 |
This table rounds each use type up to a whole FUE: 491 self-service users are 16 11/30 FUE, shown as 17. The exact “after” total is 259 11/30 FUE. Whether your agreement rounds per line, on the total, or not at all depends on your contract.
Where the saving comes from: advanced users fall by 201 and core users by 200, while self-service grows by 401. One advanced user costs as much as 30 self-service users, so every user who only approves, views or enters time and is classified as advanced or core is expensive shelfware.
How to use the FUE math in your SAP negotiation
- Classify by activity, not by title. Pull last-login and transaction-usage data before SAP sizes the deal. A self-service user costs one-thirtieth of an advanced user, so pushing everyone with a doubtful classification up to “advanced” is the most expensive default there is.
- Make re-allocation rights explicit. SAP states that customers can re-allocate FUEs across user types to avoid shelfware. Get that right written into your agreement, along with how often you can use it.
- Size to the pool, then negotiate the rate. Settle the FUE count first, then negotiate the price per FUE. A low per-FUE rate on an inflated pool is not a win.
- Separate the things FUEs don't cover. Digital access, industry and line-of-business solutions, BTP credits, and add-ons such as Signavio or LeanIX are priced on their own metrics. Normalize every quote to the same scope before you compare.
Sizing a RISE deal or an SAP renewal?
For independent, buyer-side eyes on your user classification, FUE pool and RISE quote before your deadline, book a free 15-minute triage, or start with the free SAP playbook.
Book a free 15-min renewal triage → Get the free SAP renewal playbook →Frequently asked questions
What is an SAP Full Usage Equivalent (FUE)?
An FUE is the user metric for RISE with SAP and SAP S/4HANA Cloud. You buy a pool of FUEs and allocate it across use types with different weights. In SAP's 2021 licensing deck, one FUE equals one advanced-use user, five core-use users, or thirty self-service users, and one developer-access user takes two FUEs.
How do I calculate FUEs from my user counts?
Multiply each count by its weight and add them up: advanced users × 1, core users × 1/5, self-service users × 1/30, and developer users × 2. SAP's own example is 40 advanced, 75 core and 270 self-service users, which comes to 40 + 15 + 9 = 64 FUEs.
How do classic SAP named-user licenses map to FUE use types?
SAP's deck shows typical mappings: Professional User to advanced use (finance) or core use (sales, R&D, production planning), Project User to core use, Worker and Employee Users to self-service use, and Developer User to developer access. Actual classification depends on what each user does and on your contract.
Can I move FUEs between user types during the contract?
SAP's deck states that customers can re-allocate users across use types to avoid shelfware during the contract's life. Confirm how re-allocation works in your own agreement, and get it in writing.
Is there a minimum FUE purchase?
As a dated historical reference only: SAP's March 2021 deck listed minimums of 35 FUEs for RISE with SAP S/4HANA Cloud and 40 FUEs for the private edition. Offer names, packaging and minimums have changed since, so ask SAP for the current figure for your offering.