SAP USMM Measurement Guide: What It Measures and How to Prepare Your Data

Every SAP enterprise customer is required to participate in the Annual System Measurement process. SAP uses USMM — a transaction in your SAP system — to generate a licence measurement report that is then consolidated via the License Administration Workbench (LAW) and submitted to SAP. The output determines whether you have a compliance gap, and if so, how large it is.

What SAP does not tell you is that USMM's output is highly sensitive to configuration choices, measurement timing, and data quality — and that the default settings are not optimised to produce the most accurate measurement. They are optimised to produce the most complete measurement, which in licence compliance terms means the most expensive one.

Our complete SAP audit guide covers the full audit process. This guide focuses specifically on USMM: what it measures, how SAP's auditors use it, and what you need to prepare before your next measurement cycle.

What Is USMM and Why Does It Matter?

USMM (transaction code: USMM) is an SAP NetWeaver application that runs within your SAP ERP, S/4HANA, or other SAP ABAP-based system to collect licence-relevant data. It measures the number and type of users who have accessed the system during the measurement period, classifies them into SAP's predefined licence categories, and produces a consolidated licence position.

The output — called the Licence Measurement Result — is the primary input to your Annual Licence Declaration, which you are contractually obliged to submit to SAP each year. This submission becomes SAP's basis for calculating your licence compliance gap: the difference between what you have declared and what you are contracted to use.

The stakes are high. An accurate, well-prepared USMM submission that correctly reflects your actual usage minimises exposure. A poorly prepared submission that includes test users, incorrectly classified production users, and misconfigured system clients can create a gap of millions of pounds that you then have to fight to close.

What USMM Counts — and What It Misses

USMM collects data across three primary dimensions: user-based metrics, engine-based metrics, and where applicable, document-based Digital Access metrics (for customers subject to the 2023 Digital Access licensing model).

User-Based Measurement

USMM counts every user in the system's user master records who has logged on during the measurement period. The measurement period is configurable — typically the 12 months prior to submission — but the default can pull a broader window if not set correctly. Each user is assigned a licence type based on their transaction usage:

Licence Type	Classification Basis	Typical Cost
Professional	Users who ran complex business transactions (FI, CO, MM, SD, HR)	£3,000–£6,000/user/year
Limited Professional	Users limited to specific functional areas (e.g. purchase orders only)	£1,000–£2,500/user/year
Employee	Self-service users accessing ESS/MSS portals (time, expenses, payslips)	£150–£400/user/year
Developer	Users with ABAP development, debugging, or system configuration access	£4,000–£8,000/user/year
Functional	Users with read-only access to limited functional areas	£200–£600/user/year

Engine-Based Metrics

Alongside user counts, USMM also measures engine-based licences where applicable — including engines for specific products like SAP Business Warehouse (BW), SAP Process Orchestration, or industry-specific solutions. Engine metrics are based on technical system parameters rather than user activity, making them less susceptible to overcounting — but still require verification.

What USMM Does Not Capture

USMM does not capture Digital Access (document-based) metrics — these require separate measurement tooling and are typically addressed through SAP's Digital Access measurement process using either SAP's own tools or third-party products like Snow Software, Flexera, or VOQUZ. Customers on the classic Named User model should verify whether their contracts include Digital Access provisions before the measurement cycle begins.

How USMM Systematically Overcounts

The five most common sources of USMM overcounting — all of which are correctable before you submit your annual measurement:

How to Prepare Your Data Before Running USMM

A properly prepared USMM run produces a measurement that reflects your actual licence usage — not SAP's most commercially advantageous interpretation of it. Follow this preparation sequence before every measurement cycle:

1. Audit Your System Client Configuration

   Verify that only production clients are included in the USMM scope. Development, test, training, and sandbox clients must be explicitly excluded. Document your client configuration and retain the documentation — you will need it if SAP challenges your exclusion decisions.

2. Clean the User Master Data

   Lock or delete all departed employee accounts, expired contractor accounts, and inactive users. Run transaction SU10 to identify users with no logon activity in the past 90 days and validate each one against HR records. Reclassify locked accounts as technical users where appropriate. For a structured approach to this step, see our complete guide to SAP inactive user cleanup — including how to use SUIM reporting and cross-reference HR data to build a defensible user purge before any measurement.

3. Identify and Reclassify System Users

   All RFC users, interface users, batch job accounts, and background service users must be identified and set to type "System" or "Service" in the user master (transaction SU01). System and Service users are excluded from USMM Named User counts — but only if correctly configured before the measurement runs.

4. Review User Licence Type Assignments

   Compare each user's current licence type assignment against their actual transaction usage for the prior 12 months. Use transaction ST05 or your ITAM tooling to pull actual usage logs. Reclassify users whose assigned licence type exceeds what their usage pattern requires.

5. Set the Measurement Period Correctly

   Configure USMM's measurement period to reflect the contractual measurement window in your SAP Master Agreement — typically the 12 months preceding the annual declaration date. Running with the wrong period can inflate counts by including usage outside the contractual scope.

6. Run USMM in Test Mode First

   Execute USMM in simulation mode to review output before the official run. Analyse the preliminary results against your contracted licence position. Identify any users classified at an unexpectedly high level and investigate the underlying transactions that drove the classification. Remediate before the official submission.

7. Document Everything

   Retain all user master change logs, system client configuration evidence, and reclassification justifications. If SAP challenges any element of your measurement, documented evidence is the difference between a successful challenge and an expensive concession.

When SAP Runs USMM During an Audit

During a formal SAP audit, SAP's Global Licence Auditing team will request permission to run USMM directly in your production systems. There are several important considerations here that most enterprises are not aware of.

First, you have the right to be present and to observe the USMM configuration before it runs. SAP's auditors may configure measurement parameters — client scope, measurement period, user type thresholds — in ways that differ from your standard configuration. Review the configuration before execution and flag any parameters you believe are inconsistent with your contractual obligations.

Second, SAP's auditors will consolidate the USMM output via the LAW (License Administration Workbench) tool — either within your system or on SAP's own measurement infrastructure. LAW consolidates results across multiple SAP systems to produce an aggregate ELP (Effective License Position). LAW consolidation logic has its own anomalies, particularly in multi-system landscapes where the same physical user appears across multiple SAP systems. Our separate guide on SAP LAW methodology and challenges covers this in detail.

Third, if you have already run your own USMM measurement using a properly prepared dataset, you have a baseline. When SAP's figures differ materially from yours, you have documented grounds to challenge their methodology. This is why independent measurement — before SAP's auditors arrive — is the single most important preparation step you can take.

USMM in S/4HANA Environments

For customers who have migrated to SAP S/4HANA, the USMM process functions similarly to ECC — but the licensing model underlying it has changed in significant ways. S/4HANA introduces the FUE (Full Use Equivalent) metric as an alternative user-based metric, and the licence type taxonomy in S/4HANA contracts differs from the legacy ECC framework.

Customers on S/4HANA Cloud Private Edition have a different measurement and reporting mechanism entirely, driven by SAP's own cloud infrastructure reporting rather than customer-run USMM. Understanding which measurement model applies to your specific contract is critical before preparation begins.

RISE with SAP customers face particular complexity: their licensing bundles include SAP BTP credits, cloud infrastructure components, and application licences, each with their own measurement metrics. A USMM-driven user measurement addresses only the application layer — the broader RISE compliance picture requires a more comprehensive analysis.