A Full User Equivalent (FUE) is the consumption metric SAP uses to price its cloud ERP bundles, RISE and GROW. Instead of counting named users, SAP maps every user authorisation to one of three categories — Advanced Use, Core Use and Self-Service Use — and converts them to FUEs at roughly 1:1, 5:1 and 30:1. You buy a pool of FUEs, not individual licences, which means the category mix you negotiate, not your raw headcount, determines the bill. This guide explains how the FUE metric works, how to calculate it, and how to keep it from quietly inflating your subscription.
The FUE replaced the perpetual named-user model when SAP shifted ERP to subscription. Under the old model you licensed each person as a Professional, Limited or Self-Service user and paid a per-user price plus 22% maintenance; under the FUE model you license a single pooled metric that abstracts users into a weighted count. The weighting is the whole point: a power user and an occasional self-service user are not billed equally, but the conversion ratios compress them onto one scale. The metric underpins both cloud routes covered in our RISE and GROW pillar guide, and it behaves slightly differently in RISE private edition versus GROW public edition.
SAP maps user authorisations to three use categories, each with a fixed FUE conversion ratio. The public-cloud (GROW) ratios are the benchmark below; private-edition (RISE) mappings follow the same three-tier logic with deal-specific adjustments.
| Use category | Conversion ratio | Typical roles | Cost weight |
|---|---|---|---|
| Advanced Use | 1 user = 1 FUE | Power users, broad create/change | 30× |
| Core Use | 5 users = 1 FUE | Role-specific transactional users | 6× |
| Self-Service Use | 30 users = 1 FUE | Leave, expenses, time entry | 1× |
FUE conversion ratios. The cost-weight column shows why category mapping matters: an Advanced user consumes thirty times the FUE budget of a Self-Service user.
The cost-weight column is the part SAP account teams do not dwell on. Because an Advanced Use authorisation is thirty times more FUE-expensive than a Self-Service one, the difference between an accurate mapping and a lazy one is enormous. Over-assign a few hundred users to Advanced Use and the subscription balloons — with no extra capability delivered to the business.
Count the users in each category, divide Core by 5 and Self-Service by 30, add the Advanced users at 1:1, and total the result. The worked example below shows how a 900-person deployment converts — and how a single re-mapping decision changes the number.
| Category | Users | Ratio | FUEs |
|---|---|---|---|
| Advanced Use | 50 | 1 : 1 | 50 |
| Core Use | 250 | 5 : 1 | 50 |
| Self-Service Use | 600 | 30 : 1 | 20 |
| Total | 900 | — | 120 FUEs |
Worked FUE calculation. The same 900 users could be 120 FUEs or far more, depending entirely on the category split.
Now change one assumption: move 150 of those Core users up to Advanced Use (a common over-classification). Those 150 users jump from 30 FUEs to 150 FUEs — adding 120 FUEs, doubling the subscription, for users whose work has not changed. That single line is why we treat the category mapping as the first and largest negotiation in any RISE or GROW deal.
We rebuild the category mapping against actual transaction profiles before SAP sets your baseline. No-obligation scoping call.
Right-size the category mapping. Because the cost weights are so lopsided, moving over-classified users to the lowest defensible tier is the dominant lever — far larger than any headline discount. In our 340+ engagements, 30–45% of users are typically mapped higher than their actual transaction profile justifies, and SAP's own usage data is what makes the down-mapping defensible. The steps below are the FUE-reduction sequence we run.
This is the cloud-era equivalent of named-user reclassification, the same discipline that drives the perpetual benchmarks in SAP license cost in 2026. It also connects directly to the route decision — the FUE math is what makes the RISE vs GROW vs on-prem comparison concrete. For the negotiation and audit work that surrounds it, see our contract negotiation and SAP audit defence practices, and the portfolio renegotiation case study for how FUE right-sizing fits a wider estate.
FUE benchmarks, the category-mapping math, and the clause positions we use on live SAP cloud deals.
A Full User Equivalent is SAP's cloud consumption metric for RISE and GROW. User authorisations are mapped to Advanced Use, Core Use or Self-Service Use and converted to FUEs at roughly 1:1, 5:1 and 30:1. You buy a pool of FUEs rather than individual named-user licences.
Count users per category, divide Core by 5 and Self-Service by 30, add Advanced at 1:1, and total. For example, 50 Advanced + 250 Core + 600 Self-Service = 50 + 50 + 20 = 120 FUEs. The category assignment, not headcount, drives the total.
Right-size the category mapping. Because an Advanced user costs five times a Core user and thirty times a Self-Service user, moving over-classified users to the lowest defensible tier is the dominant cost lever. In our engagements, 30 to 45 percent of users are typically mapped higher than their actual usage justifies.
Weekly compliance intelligence for IT leaders.
