SAP FUE Licensing Explained: How to Calculate and Optimize Your User Counts

What Is the SAP FUE Metric?

Full Use Equivalent (FUE) is the aggregation method by which SAP allows customers to allocate individual users access to SAP cloud services — specifically RISE with SAP and S/4HANA cloud subscriptions — using weighted ratios assigned to different user types. Rather than purchasing a separate named user licence for every individual who accesses the system, customers purchase a total FUE quantity and then allocate those FUEs across their user population using SAP-defined conversion ratios.

FUE was introduced as part of the broader transition from SAP's traditional on-premise named user model to the RISE with SAP cloud subscription model. In the on-premise world, SAP licences were typically structured around named user types — Professional Users, Limited Professional Users, Employee Users, and so on — each with a fixed annual cost. FUE replaces this catalogue with a unified metric that allows customers to mix user types more flexibly, while giving SAP a cleaner basis for cloud subscription pricing that scales with the intensity of system usage rather than the raw count of individuals with system access.

The FUE concept is specified in SAP's Cloud Supplement and Service Description Guide documents for each RISE with SAP contract. The exact ratios and user type definitions may vary slightly by contract vintage and product scope, so always verify against your specific contract terms rather than relying solely on general guidance.

FUE User Types and Weighting Ratios

The FUE calculation is built on three primary user categories, each carrying a different weighting factor that reflects the assumed depth and breadth of system access:

Advanced User — 1.0 FUE

An Advanced User is the baseline FUE category — the "full" SAP user who has unrestricted access to the system's functional scope. Advanced Users typically include finance controllers, business analysts, HR managers, procurement specialists, and others who use SAP as a primary work tool across multiple functional areas and transactions. Each Advanced User consumes 1.0 FUE, making this the most expensive user category on a per-head basis. Advanced Users are also referred to as "power users" or "full users" in SAP documentation and some contract supplements.

Because Advanced Users carry a 1:1 FUE ratio, a user population comprised primarily of Advanced Users will have an FUE requirement equal to its headcount. Enterprises migrating from an ECC environment with a large Professional User base often find that their initial FUE requirement maps very closely to their existing Professional User count — but the FUE model creates opportunities to reclassify some users downward if their actual usage pattern is more limited than a full Advanced User profile.

Core User — 0.2 FUE

A Core User has access to a more limited set of SAP transactions and functional areas — typically those required for a defined operational role, without the breadth of access that an Advanced User needs. Core Users might include warehouse operatives who use SAP for goods receipt and inventory movements, plant maintenance technicians who log work orders, or accounts payable processors who manage a defined subset of financial transactions. Five Core Users consume 1.0 FUE — meaning a Core User licence costs 20% of an Advanced User licence in FUE terms.

The Core User classification offers substantial cost savings for enterprises with large operational workforce populations who only need limited SAP access. A manufacturing business with 2,000 production floor workers who each need to record time confirmations and goods movements in SAP could potentially classify all 2,000 as Core Users, consuming 400 FUEs rather than 2,000 FUEs — a 1,600 FUE reduction that, at typical RISE with SAP per-FUE pricing, represents millions of euros in annual cost savings.

Self-Service User — 0.033 FUE

A Self-Service User has very limited SAP access, typically restricted to employee self-service activities such as viewing payslips, requesting leave, or updating personal data. Self-Service Users are the lightest FUE category — 30 Self-Service Users consume 1.0 FUE (each being 0.033 FUE). For enterprises with large employee populations who only need ESS access, the Self-Service User category enables extremely cost-effective coverage of the full employee base without purchasing Advanced or Core user FUEs for every individual.

The distinction between Core Users and Self-Service Users is the breadth and type of transactions accessible. Self-Service is explicitly limited to employee-initiated self-service actions. Any user who needs to perform standard business transactions — even simple ones outside the self-service scope — should be classified as a Core User rather than a Self-Service User.

Developer and Other Specialist User Types

In addition to the three primary user types, SAP RISE contracts typically include categories for Developer Users and Test Users. Developer Users — those who develop, configure, or extend the SAP environment — typically carry a higher FUE weight of 2.0, reflecting the broader and more intensive system access they require. Developer access licences are often managed separately from operational user licences in the contract.

Test system users and quality assurance (QAS) environments are an area of FUE calculation that frequently creates unexpected cost exposure. Some RISE with SAP contracts include test system access within the primary FUE subscription; others require separate FUE allocation for test environments. Clarify the test environment FUE treatment explicitly in your contract before signing — a large QAS user population that must be separately licensed can add 10 to 20% to your total FUE requirement.

How S/4HANA Migration Changes Your FUE Baseline

This is the point that many organisations miss during their RISE with SAP migration planning: migrating from SAP ECC to S/4HANA via RISE fundamentally changes your licence baseline. You cannot simply map your existing ECC named user types to RISE with SAP FUE categories and assume the cost structure will be equivalent. The mapping is more complex, and the cost implications can be material in either direction.

In ECC, many enterprises had large populations of Employee Users or Limited Professional Users who accessed SAP for relatively narrow use cases — timesheet entry, travel expense submission, or specific departmental workflows. Under the FUE model, the classification of these users into Advanced, Core, or Self-Service categories requires a careful assessment of the specific transactions each user actually performs. Users that SAP maps to Advanced (1.0 FUE) may previously have been classified as lower-cost ECC user types.

Critically, SAP's initial FUE sizing proposal during a RISE with SAP migration negotiation will typically err toward the higher classification wherever there is ambiguity. SAP's mapping tools and advisory services will recommend Advanced User classification for any user with access to more than a narrow set of transactions. It is in SAP's commercial interest to maximise the FUE requirement at initial sizing.

Independent FUE baseline assessment — conducted by advisors who are not commercially incentivised toward a higher FUE count — consistently finds 10 to 25% reductions in the FUE requirement compared to SAP's initial sizing proposal. Conduct your own FUE analysis before providing SAP with access to your user data for their sizing exercise.

Strategies to Optimise Your FUE Count

FUE optimisation is not about gaming the licence rules — it is about ensuring that every user is classified at the correct level for their actual system usage, and that the system's role and authorisation structure does not unnecessarily inflate user classifications. The following strategies are the most consistently effective:

Conduct a Transaction Usage Analysis

Before any FUE classification exercise, run a transaction usage analysis on your SAP system for the past six to twelve months. This analysis identifies which transactions each named user has actually executed during the period, how frequently, and across which functional areas. Users who are theoretically entitled to Advanced User access but whose actual transaction pattern fits within the Core User scope can be reclassified — the entitlement boundary is defined by what access they are provided, but the classification is informed by actual usage patterns.

Transaction usage analysis also identifies dormant users — individuals who have system access but have not executed any transactions during the measurement period. These users should be removed from the system before any FUE sizing exercise. Dormant users included in the FUE count inflate the licence requirement without delivering any business value.

Address Role Bloat

Role bloat — the accumulation of excessive authorisations within user roles over time — is one of the primary drivers of incorrect FUE classification. In many SAP environments that have been in operation for several years, user roles have been incrementally expanded as business requirements evolved, resulting in roles that carry authorisations far beyond what the user actually needs. A production planner who originally needed access to materials management and production planning may have had financial reporting transactions added to their role over time. Under FUE classification, those financial authorisations may push the user from Core (0.2 FUE) to Advanced (1.0 FUE).

A role remediation exercise — auditing all roles against the minimum-privilege principle and removing authorisations that exceed actual job requirements — can systematically reclassify users from Advanced to Core, or from Core to Self-Service, at significant FUE savings. Tools such as SAP's SAM4U Accelerator, available on the SAP Store, support this analysis by simulating the FUE impact of different authorisation configurations before making changes to the live system.

Optimise Transaction Access Without Full Role Overhaul

Where a full role overhaul is not feasible within the migration timeline, targeted adjustments can still achieve meaningful FUE reductions. Disabling individual rarely-used transactions within existing roles — transactions that a user technically has access to but has never executed — can lower a user's effective FUE classification without requiring a complete role redesign. This is a lower-cost approach to FUE optimisation when time is limited, though it is less thorough than a full role remediation exercise.

Establish FUE Governance for New Users

FUE optimisation is not a one-time exercise — without ongoing governance, FUE counts will drift upward as new users are added at default Advanced classification and as existing roles accumulate new authorisations. Establish a governance process that defines the FUE classification for each user type at onboarding, includes periodic audits of FUE-relevant authorisation changes, and requires FUE impact assessment for any role change requests.

FUE, Indirect Access, and the DDLC Metric

FUE licensing governs access by human users to SAP S/4HANA. However, enterprises also need to manage indirect access — the use of SAP capabilities by third-party systems or applications that interact with SAP data without being SAP-licenced users. SAP measures and prices indirect access using the Digital Document Lifecycle Count (DDLC) metric, which counts documents created, substantially changed, or processed through SAP interfaces by non-SAP-licenced systems.

The DDLC metric is separate from FUE and is not resolved by purchasing more FUEs. Enterprises that assume their FUE subscription covers all system interactions — including third-party integrations — are exposed to indirect access audit claims that can generate significant additional licence costs. As part of any RISE with SAP FUE sizing exercise, conduct a parallel DDLC exposure assessment to identify all non-SAP-licenced system interactions and determine whether they require Digital Access licences under SAP's DDLC framework.

In practice, the most common DDLC exposure scenarios in S/4HANA environments include: HR systems creating or updating employee-linked financial records in SAP, CRM systems generating sales orders or customer accounts in S/4HANA via API, and e-commerce platforms creating order documents that flow into SAP ERP. Each of these scenarios should be assessed against SAP's current Digital Access pricing before finalising the RISE with SAP subscription scope.

Negotiating Your FUE Volume

Once you have established an independently verified FUE baseline, the negotiation of the FUE subscription quantity itself follows standard SAP commercial principles. Minimum purchase requirements are common — SAP typically requires a minimum FUE commitment that ensures the contract is commercially viable from its perspective. Negotiate the minimum starting point down to the lowest defensible level based on your independent assessment, and include contractual flexibility mechanisms that allow you to add FUEs during the term without triggering a complete contract renegotiation.

Within RISE with SAP, annual support costs are bundled into the subscription and sit at approximately 22% of the total contract value on a blended basis. This bundling makes it difficult to isolate the support cost component for benchmarking, but it is worth understanding that a portion of your FUE subscription fee effectively represents SAP annual support — a cost that on-premise customers pay separately and that has historically been negotiable downward in large deals.

Timing matters significantly for FUE negotiations. SAP's fiscal year ends December 31, and the Q4 window — October through December — is when SAP's account teams face maximum year-end pressure to close deals. Enterprises that initiate FUE baseline renegotiations in Q4 typically achieve better commercial outcomes than those entering discussions earlier in the year. If you are approaching a RISE with SAP contract renewal or FUE true-up, aligning the negotiation timeline to SAP's Q4 pressure window is one of the most reliable levers available to the buyer.

Conclusion

The FUE metric represents a fundamental shift in how SAP licences are structured, measured, and priced in the cloud era. Enterprises that understand the user type weightings, conduct rigorous role analysis before migration, and optimise their authorisation structures consistently achieve FUE baselines 10 to 25% below SAP's initial sizing proposal. For a large enterprise with 5,000 users, a 15% FUE reduction can represent several hundred FUEs — at typical RISE with SAP per-FUE pricing, a saving of several million euros per year in subscription cost. Independent FUE assessment, combined with complementary DDLC exposure analysis, provides the foundation for a well-priced, defensible RISE with SAP contract.

Redress Compliance provides FUE baseline assessments, DDLC exposure analysis, and RISE with SAP negotiation support. SAP commercial advisory specialists to discuss your upcoming S/4HANA migration or RISE with SAP renewal.