How SAP S/4HANA user license types work in 2026. The professional, functional, and self service tiers, how they convert into FUE, and where the cost is set.
SAP S/4HANA splits users into professional, functional, and self service tiers, then converts each tier into Full User Equivalents, so the weighting of your user mix sets the cloud cost more than the headcount does.
Model it first with our SAP FUE calculator.
This guide is for SAP procurement and license managers sizing an S/4HANA subscription in 2026. Read it with the FUE licensing guide and the SAP Practice page.
S/4HANA splits users into professional, functional, and self service tiers. Each tier reflects the depth of access a user needs. SAP describes the product on its S/4HANA pages.
Professional users hold broad operational access. Functional users work within a narrower scope. Self service users act only on their own records.
Each tier carries a conversion ratio into Full User Equivalents. The weighted sum across all tiers is the contracted FUE count that prices the subscription. SAP RISE context sits on the RISE with SAP pages.
Professional users often count near a full unit, functional users a fraction, and self service users a small fraction. The exact figures vary by agreement.
S/4HANA tier to FUE conversion, illustrative
| Tier | Example weight | Best fit |
|---|---|---|
| Professional | 1.0 | Broad operational roles |
| Functional | 0.2 | Narrow scope work |
| Self service | 0.033 | Own record tasks |
The cost is set by the mix, not the headcount. A few professional users plus many self service users produces a small FUE total. Over assigning professionals reverses that and inflates the bill.
The biggest waste is mapping legacy professional users straight across when many should be functional or self service. The fix is to map from real usage.
The contracted FUE count carries straight into the renewal price. A corrected, lower tier mix is the anchor before discount talks begin. SAP cloud direction is covered in SAP news.
The standard approach is to map each existing ECC role to the nearest S/4HANA tier and accept the result. We disagree. Across the S/4HANA mappings Fredrik Filipsson benchmarked in 2024 to 2025, that lift and shift over assigned the professional tier by 20 to 35 percent, because old roles were broader than the work now needs. The buyer side move is to map from current usage, not from the legacy role catalog. Many users mapped as professional belong in the functional or self service tier, and correcting them cut the FUE total by 10 to 25 percent. Map the work people do today, not the roles they held in ECC.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
The tier you assign is the price you pay. In S/4HANA the user mix, not the headcount, writes the invoice.
SAP S/4HANA splits users into professional, functional, and self service tiers. Professional users hold broad access, functional users work in a narrow scope, and self service users act on their own records.
Each tier carries a conversion ratio into Full User Equivalents. The weighted sum across all tiers becomes the contracted FUE count that prices the subscription.
The professional tier costs the most because it carries the heaviest FUE weight, often near a full unit. Functional and self service users carry a fraction of that weight.
The mix sets the cost. A few professional users plus many self service users produces a small FUE total, while over assigning professionals inflates it sharply.
The most common waste is lifting legacy professional roles straight into S/4HANA when many users belong in the functional or self service tier. Mapping from real usage corrects it.
Across our benchmarks, correcting the tier mapping cut the FUE total by 10 to 25 percent. The saving comes from users wrongly mapped as professional against their actual work.
The functional tier in S/4HANA plays a similar role to a limited user, covering narrow scope work at a medium weight. The exact definitions follow the current S/4HANA model.
Review the mapping before every renewal and after any major rollout. Roles change as projects finish, and a mapping set at go live rarely matches later usage.
SAP RISE pricing benchmarks, the CVR framework, indirect access posture, and the buyer side moves across the full SAP estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
500+ enterprise clients. 11 vendor practices. Industry recognized. One conversation can change what you pay for the next three years.
One short note on SAP renewal moves, license classification, indirect access posture, and the buyer side moves we are running in client engagements.