Key Takeaways
- Most enterprises have never independently verified their FUE position — they rely entirely on SAP's USMM output, which routinely overcounts by 20–40%.
- Building an independent FUE position requires pulling data from three sources: your SAP contract, your USMM output, and your HR/identity management system.
- The most common FUE overcount sources are misclassified Professional users, stale accounts, and included contractors who should be excluded under contract definitions.
- Engine metric accuracy requires cross-referencing SAP's headcount count against your actual HR system — the delta is often 10–20% for global enterprises.
- A practical FUE analysis can be completed in 3–6 weeks internally; independent validation typically adds another 2–3 weeks and provides audit-defensible documentation.
Why Independent FUE Analysis Is Essential
SAP's USMM transaction generates the measurement file that determines your audit exposure. Most organisations run USMM, look at the output, and assume it represents their actual licence position. It does not. USMM measures what is in your system — active accounts, role assignments, and access logs — but it does not apply your contract's governing definitions to determine what actually should count.
The gap between what USMM counts and what your contract requires you to licence is your FUE overcount. In a practical SAP FUE enterprise analysis, you establish this gap systematically and document the grounds for challenge. For most organisations with 2,000+ SAP users, this is a six-figure to seven-figure exercise.
The full context for FUE and engine metric fundamentals is covered in our complete SAP FUE enterprise guide. This article focuses on the practical execution steps.
Step 1: Extract and Parse Your Contract Definitions
Locate the Governing FUE and Engine Metric Definitions
Pull your SAP Master Agreement, all Order Forms, and the General Terms and Conditions. FUE definitions are typically in the Licence Metric Schedule or a supplementary appendix. Look specifically for: the FUE conversion ratio table (Professional, Limited Professional, Employee, ESS user types), the definition of "Licensee" or "Affiliate" entities included in measurement, the engine metric formula (for HCM, what constitutes an "employee"), and the measurement period and timing provisions.
Document every ambiguous term. "Employee" is commonly defined differently across SAP products and contract vintages — some definitions include contractors and temporary workers, others explicitly exclude them. "Active employee" is frequently undefined, giving you grounds to apply the narrowest reasonable interpretation.
Pay close attention to the entity schedule. Many enterprise groups have subsidiaries that are listed in the contract's covered entity schedule but contribute a small fraction of total SAP usage. If the contract provides for entity exclusions or tiered coverage, document which entities you believe should be measured separately.
Step 2: Run USMM and Export the Raw Data
Generate USMM Output Without Sending to SAP
Run transaction USMM in your SAP system and export the full measurement output — including the detailed user list, not just the summary totals. Do not generate a LAW file or transmit any data to SAP at this stage. You are gathering raw data for independent analysis, not initiating a measurement submission.
The USMM output includes a classification table showing each user ID, their assigned licence type, the last activity date, and the licence metric they contribute to. Export this to a spreadsheet. This is your baseline data set for the FUE analysis.
Key fields to review in the USMM user list: the licence type classification (which drives the FUE conversion), the last logon date (users inactive for 12+ months are candidates for exclusion), the user group and system client assignment (relevant for multi-client landscapes), and any flagged system users or service accounts (these should not appear in Named User counts but sometimes do).
Step 3: Cross-Reference Against HR and Identity Data
Pull Active Employee and User Population Data from HR Systems
Extract the current active employee list from your HR system (SAP HCM, SuccessFactors, or your HRIS), your identity management system (Active Directory, Okta, etc.), and your SAP user administration records. The goal is to identify every user in the USMM output who should not be counted under your contract's definitions.
Compare the USMM user list against your HR active employee data. Common mismatches that drive FUE overcount include: terminated employees whose SAP accounts were not disabled promptly (these should be zero-cost but appear as active users in USMM), contractors and agency workers whose status under the FUE definition is contractually excludable, users from subsidiaries or affiliates that are outside the measurement scope, and service accounts and system integration users that should be classified as technical users, not Named Users.
For engine metrics in SAP HCM specifically, pull the total employee count from your HCM master data and compare it against your HR system's active headcount. The HCM count typically includes historical employees in inactive status — these may inflate your engine metric count if your contract's definition of "employee" is based on what's in HCM rather than what's actively employed. This is one of the most contested areas in SAP audit defence engagements.
Step 4: Reclassify Users by Actual Activity
Apply Actual-Use Classification Logic
For each user classified as Professional in the USMM output, analyse their actual SAP usage. Pull the activity log (SM20 or USER_ACCOUNT workload data) for the last 12 months. Users who only perform read-only transactions, run standard reports, or access a narrow set of functions may qualify for Limited Professional — which carries a 0.4 FUE contribution versus 1.0 for Professional. The savings per reclassified user are significant at scale.
The reclassification analysis requires mapping user activity to the licence type definitions in your contract. SAP's definitions of Professional versus Limited Professional have evolved over successive contract generations — newer agreements tend to use function-based definitions that are more challengeable than the older role-based definitions. If your contract is more than 5 years old, the definitions may be significantly more favourable than what SAP's current measurement team will try to apply.
📋 Typical FUE Reduction Sources
- Inactive/terminated user accounts: 5–15% of user population in poorly governed landscapes
- Professional → Limited Professional reclassification: 10–25% of Professional-classified users
- Contractor exclusion (if contractually supported): 3–10% depending on workforce composition
- Subsidiary/affiliate exclusion: 5–20% depending on entity schedule
- Service/system account cleanup: 2–5% of total user count
- HCM employee count correction: 8–20% for global enterprises with legacy HCM data
Step 5: Build Your Independent ELP
Construct the Effective Licence Position
An Effective Licence Position (ELP) is the number of licences you actually need under your contract's governing definitions, applying the correct FUE conversion ratios to the corrected user population. Once built, the ELP becomes your negotiating basis for any audit discussion, renewal commercial, or back-licence claim from SAP.
Structure your ELP documentation to show: the raw USMM user count by licence type, each category of adjustment with the contractual or factual basis (terminated employees, out-of-scope entities, misclassified users), the adjusted user count by licence type, the FUE conversion calculation applied to the adjusted counts, and the resulting FUE total compared with your licenced position.
This document needs to be defensible in a commercial discussion with SAP. Every adjustment should reference either a specific contract clause, a factual record (HR termination data, subsidiary exclusion schedule), or a standard interpretation of the licence type definition. Vague adjustments will not survive SAP's challenge.
Our SAP licence optimisation advisers prepare ELP documentation as the foundation of every audit defence and renewal optimisation engagement. An independently validated ELP is significantly more credible with SAP's measurement team than an internally produced analysis.
Step 6: Validate Engine Metric Counts
Cross-Check Engine Metrics Against Actual Business Data
For every engine metric in your contract — HCM employee count, payroll units, Ariba spend volume — validate SAP's measurement against your actual business data. Request the raw count from SAP's measurement and reconcile it line by line against your HR, payroll, and ERP records. Discrepancies of 5–20% are common and entirely challengeable.
For HCM employee metrics specifically, insist on understanding exactly which employee groups SAP is including in its count. Common areas of dispute include: seasonal and casual workers with intermittent employment, employees in countries where SAP HCM is deployed but the country is not in the contract's scope, employees in divested entities who remain in the HCM system post-divestiture, and redundant or duplicate employee records created during HR system migrations.
If your contract uses payroll run units rather than headcount, the analysis is more technical — requiring a review of payroll configuration to verify that the unit count in the LAW file matches your actual payroll processing cycles. Misconfigured payroll systems can overcount run units significantly.
When to Engage Independent Advisers
A practical FUE analysis of the type described here can be started internally, but reaches limits quickly. The contract interpretation questions — particularly around ambiguous definitions, multi-entity structures, and the application of older contract language — require specialist knowledge that most internal SAP CoE teams do not have. The risk of accepting SAP's interpretation without challenge is typically measured in hundreds of thousands to millions of pounds in excess licence cost.
Engage independent advisers when: you are within 12 months of a major renewal, you have received an SAP audit letter or measurement request, your USMM output shows a compliance gap with your current licence position, you are planning a RISE with SAP migration, or you are completing an M&A transaction that involves SAP licence transfers. Our SAP licensing experts work exclusively on the buyer side and provide the contract expertise and negotiation experience that internal teams cannot replicate.
For a structured overview of the risks involved in FUE management, see our detailed guide on SAP FUE key risks and mitigation strategies. For specific cost reduction tactics, read our SAP FUE cost reduction guide.
Need help building an independent FUE position? Our advisers have run FUE analyses for enterprises across financial services, manufacturing, healthcare, and retail. Book a free consultation to discuss your FUE exposure and the most effective path to cost reduction.
Get Your FUE Position Reviewed →Frequently Asked Questions
Can I run USMM without SAP knowing?
Yes. USMM runs within your SAP system and you can generate the measurement output locally without transmitting any data to SAP. The LAW file is only sent when you choose to submit it. Running USMM for internal analysis — without generating or submitting a LAW file — does not trigger any SAP notification. Always complete your independent FUE analysis before any measurement submission.
How long does a practical FUE analysis take?
An initial internal analysis — pulling USMM data, cross-referencing HR records, and identifying obvious adjustment categories — typically takes 3–6 weeks with a dedicated ITAM resource. A fully documented, audit-defensible ELP with contractual analysis typically takes 6–10 weeks including external adviser involvement. The investment is almost always justified given the cost savings identified.
What if SAP disputes our FUE reclassification?
SAP's measurement team will challenge FUE reductions that are not supported by contractual evidence. This is why documentation quality matters. Each adjustment to the USMM baseline must reference a specific clause, an entity exclusion, or a documented factual basis. Adjustments backed by clear contractual language and factual evidence are difficult for SAP to sustain a challenge against. Where the contract language is ambiguous, SAP and the customer often negotiate a commercially reasonable settlement.
Should we clean up user accounts before a measurement?
Yes — account hygiene should be an ongoing process, not a pre-audit sprint. Disabling accounts for terminated employees and contractors promptly is best practice and reduces your FUE count legitimately. However, do not make any changes to user roles or classifications immediately before a measurement in a way that could appear reactive to an audit — this can create credibility issues. Focus on systemic improvements through your normal access governance processes.