S/4HANA user license types, where the mix sets the money
S/4HANA splits users into professional, functional, and self service tiers, then converts each tier into Full User Equivalents at fixed ratios. The weighting means your user mix drives the subscription cost far more than your headcount does, and the mix is where the recoverable money hides.
Prepared by Redress Compliance · August 6, 2026 · SAP licensing advisory. Based on 30 to 40 S/4HANA user mappings benchmarked 2024 to 2026.
Executive summary
The three tiers describe depth of access. Professional users, SAP's Advanced use category, hold broad operational access: create, change, configure, across functional scope. Functional users, the Core use category.
Transact within a defined scope. Self service users act only on their own data: requests, approvals, timesheets, and reporting.
The money is in the conversion. Each tier maps into Full User Equivalents at fixed ratios: 1.0 per professional, 0.2 per functional, five to one, and 0.0333 per self service user, thirty to one.
The FUE total, not the headcount, is what the subscription is sized on, so moving one user from professional to functional removes four fifths of that user's cost, and to self service removes almost all of it.
Over assignment upward is the default error.
Across the user mappings we benchmarked, professional users were over assigned by 20 to 35 percent of seats, functional access was the honest fit for 25 to 40 percent of the professional population.
And correcting the tiers cut the FUE total by 10 to 25 percent, with no change to what any user could actually do.
One naming trap before you search your contract: SAP's paperwork calls the unit a Full Use Equivalent, while account teams and the market say Full User Equivalent. Same unit.
The definition that binds you sits in the Service Description Document behind your RISE or S/4HANA Cloud order, not in the deck the ratios were presented on, and it is the document the tier review has to be argued from.
The three tiers, and what each actually covers
Tier assignment should follow what a user does in the system, not their title or their department's importance. The functional differences are concrete:
| Tier | SAP contract category | What the user can do | FUE weight |
|---|---|---|---|
| Professional | Advanced use | Create, change, configure: full operational access across functional scope | 1.0 each |
| Functional | Core use | Operational transactions inside a defined scope: post, process, execute within their area | 0.2 each, five to one |
| Self service | Self service use | Own data only: requests, approvals, timesheets, expenses, reporting on their own records | 0.0333 each, thirty to one |
SAP's default landing for anything that used to be a Professional named user is the Advanced tier. Migrations from ECC carry the old user list across at the top weighting unless someone argues each population down, which is precisely why the over assignment is systematic rather than accidental.
The conversion moment is the negotiation moment.
The FUE conversion, worked
Take each population, multiply by its ratio, and add. The weighting means large headcounts collapse into small FUE totals when the mix is honest:
| User type | Headcount | FUE per user | Weighted FUE |
|---|---|---|---|
| Professional | 50 | 1.0 | 50 |
| Functional | 200 | 0.2 | 40 |
| Self service | 1,000 | 0.0333 | 33.3 |
| Total | 1,250 | 123.3, written as 124 |
A 1,250 person population lands at 124 FUEs: the light tier carries 80 percent of the headcount and about a quarter of the cost.
Now run the same population with the over assignment we actually find: move 60 of the functional users up to professional and the total jumps by 48 FUEs, a 39 percent increase in the bill for zero additional capability.
The FUE licensing guide covers the full calculation mechanics, and the FUE calculator runs your own numbers in minutes.
The SAP named user negotiation playbook
The tier definitions argued from the Service Description Document, the usage evidence method, the conversion moment strategy, and the order form language that holds the mix at renewal.
Get the white paper →Mapping users honestly, usage decides, not titles
The tier question for every user is behavioral: what transactions do they actually run, at what depth, in what scope? Three populations account for most of the recoverable money:
- The inherited professionals. Users carried across from ECC at the top tier because they held Professional named user licenses historically. Their current S/4HANA behavior, not their 2015 license, is what the tier should reflect.
- The single scope operators. Users who transact intensively but inside one functional area, warehouse, receivables, plant maintenance. Intensity is not breadth: they are the 25 to 40 percent of professionals whose honest tier is functional.
- The approvers and requesters. Managers who approve, staff who submit, occasional reporters. Their entire footprint is own data activity, and every one of them priced above self service is paying thirty times the honest rate.
The evidence is transaction history: actual usage pulled from the system, per user, classified against the tier definitions in the Service Description Document.
SAP's account team will map by role catalog and history; the buyer side mapping works from behavior, and the delta between the two mappings is the negotiation.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What we saw across user mappings, 2024 to 2026
Fredrik Filipsson benchmarked roughly 30 to 40 S/4HANA user mappings between 2024 and 2026, and the professional tier was consistently over assigned against actual usage, in migrations and in steady state estates alike:
Professional seats whose transaction history showed single scope or self service behavior, priced at the full weight anyway.
The subscription reduction from re tiering against evidence, with no user losing access they actually used.
The pattern behind the pattern was timing: the mix was set once, at migration or initial subscription, and never revisited, while the organization underneath it changed every year.
The estates that held their costs treated the tier mapping as a renewal artifact, refreshed against transaction history before every anniversary, and argued from the contract definitions rather than the account team's role catalog.
The broader subscription mechanics sit in the S/4HANA licensing guide.
Your first five moves
- Pull per user transaction history and classify actual behavior against the tier definitions in your Service Description Document, not against job titles.
- Re tier the single scope operators. The 25 to 40 percent of professionals working one functional area are functional users at one fifth the weight.
- Sweep the approvers and requesters into self service. Own data activity at thirty to one is the cheapest seat in the estate.
- Run the corrected mix through the FUE calculator and put the delta, in FUEs and dollars, at the top of the renewal position.
- Fix the mapping at the conversion or renewal moment, when the order form is open, and write the tier definitions into it. The SAP practice runs the mapping and the negotiation with you, on your side of the table.
Frequently asked questions
What are the SAP S/4HANA user license types?
Three tiers by depth of access: professional users, SAP's Advanced use category, with broad create, change, and configure access; functional users, the Core category, transacting within a defined scope; and self service users acting only on their own data.
Each tier converts into Full User Equivalents at a fixed ratio, and the subscription is sized on the FUE total.
What are the FUE conversion ratios for S/4HANA users?
Professional users convert at 1.0 FUE each, functional users at 0.2, five to one, and self service users at 0.0333, thirty to one.
A 1,250 person population with an honest mix of 50 professional, 200 functional, and 1,000 self service lands at about 124 FUEs, which is why the mix matters far more than the headcount.
What is the difference between Full Use Equivalent and Full User Equivalent?
Nothing: they are the same unit. SAP's contract paperwork says Full Use Equivalent while account teams and the market say Full User Equivalent.
The binding definitions sit in the Service Description Document behind your RISE or S/4HANA Cloud order, and that document, not the sales deck, is what a tier review must be argued from.
How do we know if users are over assigned to the professional tier?
Pull per user transaction history and compare behavior against the tier definitions. Single scope operators and approval only users sitting in the professional tier are the signatures.
Across our benchmarks, 20 to 35 percent of professional seats were over assigned, and 25 to 40 percent of professionals fit the functional definition.
How much can a tier remapping save on an S/4HANA subscription?
Correcting the mix cut the FUE total by 10 to 25 percent across our benchmarked mappings, with no user losing access they actually used.
On the worked example, moving 60 users one tier up in error adds 39 percent to the bill, so the same arithmetic runs in your favor when the correction goes the other way.
When is the best time to fix the S/4HANA user mix?
At the conversion to S/4HANA or RISE, and at every renewal, the two moments the order form is open.
SAP's default is to land legacy Professional named users in the Advanced tier wholesale, so the migration mapping deserves the most scrutiny, and the mix should be refreshed against transaction history before each anniversary.
