A practical guide to SAP's Full-Use Equivalent model — the three user categories, FUE weightings, worked calculation examples, and optimisation strategies.
In SAP FUE licensing, instead of purchasing fixed seats for each user role, you buy a pool of FUEs that can be flexibly allocated across different user categories. Each FUE represents one “full” user’s worth of access, and lighter-use roles count as a fraction of an FUE.
This model was introduced for SAP S/4HANA Cloud (including RISE with SAP) to align costs with actual usage levels. You commit to a total number of FUEs (e.g., 100 FUEs) instead of specific counts of each license type. Users are categorised into Advanced, Core, or Self-Service based on their access needs.
As long as the weighted sum of all users stays within your purchased FUE pool, you are compliant. You can add or change user roles internally without renegotiating the contract, as long as you have enough FUE headroom.
For the full SAP user types overview, read our SAP Named User License Types: A Guide for CIOs.
| User Type | FUE Weight | Users per 1 FUE | Typical Usage |
|---|---|---|---|
| Advanced (Full Access) | 1.0 FUE/user | 1 user = 1 FUE | Enterprise-wide tasks; create/approve transactions across modules |
| Core (Limited Access) | 0.2 FUE/user | 5 users = 1 FUE | Departmental or routine tasks; restricted scope in specific functions |
| Self-Service (Occasional) | ~0.033 FUE/user | 30 users = 1 FUE | Very light use (self-service portal, approvals, time entry only) |
Note: SAP also defines a Developer user type, usually counted as 2.0 FUE each.
The key insight: an Advanced user “costs” 30 times more in license terms than a Self-Service user. The FUE model rewards you for right-sizing access.
For detailed breakdowns of each license category, see SAP S/4HANA Licensing Types Explained.
The formula is straightforward:
Total FUEs = (Advanced users × 1) + (Core users × 0.2) + (Self-Service users × 0.0333), rounded up to the nearest whole number.
A company has 50 Advanced users, 100 Core users, and 300 Self-Service users:
| Category | Users | FUE Weight | FUE Consumed |
|---|---|---|---|
| Advanced | 50 | × 1.0 | 50 FUE |
| Core | 100 | × 0.2 | 20 FUE |
| Self-Service | 300 | × 0.033 | 10 FUE |
| Total Required | 80 FUE | ||
Compare this to 450 users all as Advanced = 450 FUE. Proper categorisation reduced the FUE requirement by over 80%.
Account for future expansion — include a buffer of extra FUEs. But avoid padding too much (which leads to overbuying). SAP often has minimum FUE purchase requirements (e.g., 40 FUEs for RISE private edition).
Each user’s SAP role and authorisation should align with their FUE category. If someone is licensed as Core, their system roles should not include Advanced transaction permissions. Regular reviews prevent “license creep.”
Many employees don’t require full functionality. Each user moved from Advanced to Core frees up 0.8 FUE. Moving a user from Advanced to Self-Service frees up ~0.967 FUE.
Formalise what actions a Self-Service user can perform and technically enforce those limits. Create specialised roles/profiles for self-service only to reduce compliance risk.
Establish quarterly review of FUE consumption. If you have unused FUEs, deploy more users or renegotiate at renewal. If consistently at 100%, plan proactively for expansion.
Secure the ability to adjust FUE counts with pro-rated pricing. Ensure you understand rules for adding or removing users. Consider shorter terms if uncertain about future needs.
For pricing benchmarks to validate your FUE costs, see SAP S/4HANA Cloud Pricing Benchmarks.
| Category | Compliance Risk | Over-Allocation Risk | Key Watch-Out |
|---|---|---|---|
| Advanced | Low | High | Paying for full access when Limited would suffice |
| Core | Medium | Medium | Users exceeding departmental scope without detection |
| Self-Service | High | Low | Role creep allowing transactional access beyond self-service |
The safest (but most expensive) approach is over-classifying users as Advanced. The most cost-effective (but riskiest) is maximising Self-Service. The optimal strategy balances both — supported by tight role design and regular audits.
For SAP audit preparation strategies, see SAP Audit Readiness: 10-Step Strategy.
You must purchase additional FUEs. SAP typically allows mid-term expansions with pro-rated pricing. Going over your entitlement without adjustment puts you out of compliance — monitor consumption proactively.
During an active contract term, reducing committed FUEs is usually not possible. You’re locked in until renewal. This is why sizing correctly and not over-committing is crucial. At renewal, you can negotiate a lower volume.
FUEs are the cloud equivalent of named user licenses. Advanced ≈ Professional, Core ≈ Limited, Self-Service ≈ ESS. The key difference is the pooling: with FUEs, you buy a pool and allocate flexibly rather than buying fixed counts of each type.
FUE is the standard licensing metric for SAP S/4HANA Cloud (including RISE with SAP). On-premise S/4HANA still uses traditional named user licenses. If you’re moving to cloud, you’ll likely encounter the FUE model.
Our SAP licensing specialists help enterprises calculate accurate FUE counts, optimise user categorisation, and negotiate the best possible rates.
This article is part of our SAP User Types Guide pillar. Explore related topics: