In SAP FUE licensing, instead of purchasing fixed seats for each user role, you buy a pool of Full-Use Equivalents (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. This guide covers the three user categories, FUE weightings, worked calculation examples, optimisation strategies, and compliance risks.
The FUE 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 and allocate users flexibly across Advanced, Core, and Self-Service categories. An Advanced user "costs" 30 times more in licence terms than a Self-Service user. Proper categorisation in a typical 450-user deployment can reduce the FUE requirement by over 80%. See also: SAP Named User Types Guide and S/4HANA Licensing Types Explained.
| 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. Finance, procurement, HR administration, supply chain management. |
| Core (Limited Access) | 0.2 FUE/user | 5 users = 1 FUE. | Departmental or routine tasks. Restricted scope in specific functions. Sales clerks, warehouse operators, limited reporting. |
| Self-Service (Occasional) | ~0.033 FUE/user | 30 users = 1 FUE. | Very light use. Self-service portal, time entry, leave requests, payslip viewing, personal data updates only. |
| Developer | 2.0 FUE/user | 1 user = 2 FUEs. | ABAP development, debugging, and system configuration. Typically a small population but consumes double FUE weight. |
FUEs are the cloud equivalent of named user licences. Advanced is approximately equivalent to Professional, Core to Limited Professional, and Self-Service to ESS. The key difference is pooling: with FUEs, you buy a pool and allocate flexibly rather than buying fixed counts of each type. See SAP ESS License Guide.
The formula is straightforward: Total FUEs = (Advanced users x 1.0) + (Core users x 0.2) + (Self-Service users x 0.033), rounded up to the nearest whole number.
| Category | Users | FUE Weight | FUE Consumed |
|---|---|---|---|
| Advanced | 50 | x 1.0 | 50 FUE |
| Core | 100 | x 0.2 | 20 FUE |
| Self-Service | 300 | x 0.033 | 10 FUE |
| Total required | 450 users | 80 FUE |
Compare this to 450 users all classified as Advanced = 450 FUE. Proper categorisation reduced the FUE requirement by over 80%. 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.
Account for future expansion by including a buffer of extra FUEs. But avoid padding too much, which leads to overbuying. During an active contract term, reducing committed FUEs is usually not possible. You are locked in until renewal. SAP often has minimum FUE purchase requirements (e.g., 40 FUEs for RISE private edition). See S/4HANA Cloud Pricing Benchmarks.
| # | Strategy | What to Do | FUE Impact |
|---|---|---|---|
| 1 | Align roles to licence types | 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 "licence creep." | Prevents over-consumption. Maintains compliance. |
| 2 | Avoid the "all-Advanced" trap | Many employees do not require full functionality. Audit actual transaction usage. Users who only run reports, view data, or perform limited departmental tasks are Core or Self-Service candidates. | Each downgrade from Advanced to Core frees 0.8 FUE. Advanced to Self-Service frees ~0.967 FUE. |
| 3 | Use Self-Service prudently | Formalise what actions a Self-Service user can perform and technically enforce those limits. Create specialised roles/profiles for self-service only. Any user performing approvals or cross-functional transactions must be upgraded. | Maximises FUE efficiency. Reduces compliance risk from role creep. See SAP ESS License Guide. |
| 4 | Monitor and true-up regularly | 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 before overages accrue. | Ensures ongoing right-sizing. Prevents waste and compliance gaps. |
| 5 | Negotiate flexibility | Secure the ability to adjust FUE counts with pro-rated pricing. Understand rules for adding or removing users. Consider shorter terms if uncertain about future needs. See SAP Contract Negotiation Service. | Reduces lock-in risk. Enables mid-term adjustments. |
| Category | Compliance Risk | Over-Allocation Risk | Key Watch-Out |
|---|---|---|---|
| Advanced | Low. Users have full access by design. | High. Paying for full access when Limited would suffice. Common source of wasted FUE capacity. | Audit actual transaction usage. Many "Advanced" users perform only Core-level tasks. |
| Core | Medium. Users may exceed departmental scope without detection. | Medium. Some over-allocation acceptable as buffer. | Monitor for transactions outside the Core scope. Users who start approving cross-functional documents need upgrading. See Named User Optimisation Playbook. |
| Self-Service | High. Role creep allowing transactional access beyond self-service. | Low. These users consume minimal FUE. | A single Self-Service user reclassified to Advanced consumes 33x more FUE. At scale, unmanaged role creep can exhaust your FUE pool. |
| Developer | Low. Typically well-controlled. | Medium. Each developer consumes 2.0 FUE. | Small population but high FUE weight. Ensure only active developers hold this classification. Deactivate promptly when projects complete. |
| Tactic | What to Do |
|---|---|
| Size accurately before negotiation | Analyse your workforce and actual SAP usage before engaging SAP. Map every user to the correct FUE category. Present SAP with your own sizing rather than accepting their proposal. Over-estimation locks you into higher costs for the full term. |
| Leverage the Self-Service ratio | Showing SAP that you know ESS users count as ~0.03 FUE gives you a negotiation edge. If SAP proposes FUE counts that assume more Advanced users than you actually need, challenge with your own user classification data. |
| Negotiate mid-term adjustment rights | Standard FUE contracts lock you in for the term. Negotiate the ability to adjust FUE counts annually with pro-rated pricing. Include rights to convert between user categories without penalty. See SAP Negotiation Strategies. |
| Benchmark FUE pricing | FUE pricing varies significantly between customers based on deal size, timing, and negotiation skill. SAP's initial proposals are typically 20-40% above achievable rates. Independent benchmarking data is essential. See SAP Discount and Pricing Benchmarks. |
| Address minimum commitments | SAP often has minimum FUE purchase requirements (e.g., 40 FUEs for RISE private edition). Understand these minimums and factor them into your sizing. If your actual requirement is below the minimum, negotiate the gap or evaluate whether cloud is the right model. |
| Plan for the ECC-to-FUE conversion | If migrating from on-premise ECC (named users) to S/4HANA Cloud (FUEs), the conversion from legacy licence types to FUE categories is a critical negotiation point. Each legacy Professional user does not necessarily become an Advanced FUE. See ECC-to-2033 Transition Option. |
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 and plan expansion before exceeding your pool.
During an active contract term, reducing committed FUEs is usually not possible. You are locked in until renewal. This is why sizing correctly and not over-committing is crucial. At renewal, you can negotiate a lower volume based on actual usage data.
FUEs are the cloud equivalent of named user licences. Advanced is approximately equivalent to Professional, Core to Limited Professional, and Self-Service to ESS. The key difference is pooling: with FUEs, you buy a pool and allocate flexibly rather than buying fixed counts of each type. See SAP Named User Types Guide.
FUE is the standard licensing metric for SAP S/4HANA Cloud (including RISE with SAP). On-premise S/4HANA still uses traditional named user licences. If you are moving to cloud, you will encounter the FUE model. See RISE with SAP Tiers.
Developer users are typically counted at 2.0 FUE each, consuming double the FUE weight of an Advanced user. While the developer population is usually small, each active developer has a significant impact on your FUE pool. Ensure only active developers hold this classification and deactivate promptly when projects complete.
Moving users from Advanced to the correct lower category. Each user moved from Advanced to Core frees 0.8 FUE. From Advanced to Self-Service frees ~0.967 FUE. In a typical deployment, 30-50% of users classified as Advanced are actually performing only Core or Self-Service level tasks. A user classification audit before RISE negotiation consistently identifies significant FUE savings. See SAP Licence Optimisation Services.
Redress Compliance provides independent SAP FUE sizing, user classification audits, RISE negotiation support with pricing benchmarks, and ongoing licence governance. Fixed-fee engagements. 100% vendor-independent.
SAP Licence Optimisation ServicesIndependent FUE sizing, user classification audits, RISE negotiation support, and pricing benchmarks. Fixed-fee engagements. No vendor conflicts.