SAP engine licenses and package licenses each carry a distinct measurement rule. The audit pulls the count from the system measurement program. The buyer side that does not rehearse the measurement carries an inflated bill at every renewal cycle.
SAP runs license measurement through two transactions. USMM reads each individual SAP system. LAW aggregates the readings across the global landscape. The output is the audit position. The buyer side that does not rehearse the measurement before the official run carries an inflated position into the renewal cycle.
Engine licenses price on usage units. Package licenses price on user count. Each metric has a measurement rule and an aggregation rule. The cleansing motion removes dormant users, recovers retired engine usage, and reconciles the certificate inventory. The motion captures 15 to 30 percent at the renewal.
SAP licenses split into two categories. Engine licenses price on usage. Package licenses price on user count. Each category has distinct measurement and aggregation rules. The buyer side reads both at every renewal.
Sales documents, purchase orders, contracts, payroll lines, materials, and transactions all serve as engine metrics. Each engine has a defined unit and a measurement window.
Professional User, Limited Professional, Employee Self Service, Developer Access, and the application specific user types. Each user type carries a price and a usage scope.
Indirect access runs as a separate position. The customer elects either document based pricing or named user pricing under the 2018 SAP licensing changes.
USMM stands for User and System Measurement. The transaction runs per SAP system. LAW stands for License Administration Workbench. The transaction aggregates USMM readings across the landscape into a single global position.
USMM reads the user master, the role assignments, the engine usage tables, and the relevant transaction logs. The output is the per system measurement.
LAW consolidates USMM outputs from every SAP system. The aggregation prevents double counting for users that exist in multiple systems. The output is the global position.
The LAW output is transmitted to SAP through the System Landscape Directory. The transmission is the official audit position.
| Transaction | Scope | Output | Buyer side use |
|---|---|---|---|
| USMM | Single SAP system | Per system count | Rehearsal at any time |
| LAW | Global landscape | Aggregated count | Final pre transmission |
| SLAW | Global landscape with consolidation rules | Cleansed aggregation | Optimization layer |
| Customer Center | Online portal | Transmitted position | Audit submission record |
Five traps appear in nearly every SAP audit. Each inflates the measurement. Each has a documented mitigation pattern.
Users that have not signed in for ninety days remain classified at the highest user type. The mitigation is dormant user reclassification before USMM runs.
A user assigned a Professional role for a one off task carries that classification across the audit period. The mitigation is the role rationalization motion.
Retired transactions remain in the engine measurement until the table is cleared. The mitigation is the engine reset before USMM runs.
New third party systems that integrate with SAP increase the indirect access surface. The mitigation is the integration audit before renewal.
Test users that hold production system access count as production users. The mitigation is the system separation review.
The rehearsal motion runs USMM and LAW against the production landscape before the official measurement window. The output identifies the gaps and the optimization opportunities. The rehearsal runs ninety days before the official run.
The cleansing motion has four steps. Each step removes a specific source of measurement inflation. The motion runs in the ninety day window between the rehearsal and the official measurement.
The audit runs on the LAW transmission. The buyer side response holds three artefacts. The order document inventory. The certificate inventory. The cleansed measurement record. These artefacts are the audit defense.
Every SAP order document from the initial purchase through every subsequent amendment. Each document carries an engine list, a user count, and a usage right scope.
Every SAP license certificate matched to the corresponding order document. The certificate is the entitlement evidence.
The USMM and LAW output after the cleansing motion. The record demonstrates the buyer side measurement discipline.
The standard advice is to wait for the SAP measurement request, run USMM and LAW, and submit whatever the system reports. We disagree. In nearly every review we ran, the unrehearsed position landed 15 to 30 percent above the entitled count, because dormant users, stale engine usage, and undocumented indirect access all report as consumption. The buyer side move is to rehearse the measurement ninety days early, cleanse the position, and only then submit, the same discipline that protects a RISE with SAP renewal. The system reports what the buyer never cleaned.
The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.
USMM is the User and System Measurement transaction, and it runs inside each individual SAP system. It reads the user master, the role assignments, the engine usage tables, and the transaction logs to produce the per system count.
That count feeds the LAW aggregation. USMM is also the rehearsal point for a buyer that wants to optimize the position before the official run.
LAW is the License Administration Workbench, and it aggregates the USMM outputs from every SAP system in the landscape. The aggregation removes duplicate counting for users that exist in more than one system.
The LAW output is the global position transmitted to SAP. USMM is per system, while LAW is the consolidated global view.
SAP measures users by named user type. Professional User, Limited Professional, Employee Self Service, Developer Access, and the application specific types each carry a different price and usage scope. The role assignments in the user master drive the classification, so the buyer side optimizes assignments to land each user at the lowest viable type.
Engine licenses price on usage units that vary by engine, such as sales documents, purchase orders, contracts, payroll lines, and materials. USMM reads the engine usage from the relevant tables, and the audit position is the measured usage against the contracted quantity.
Indirect access covers third party systems that interact with SAP without a direct human sign in. The customer elects either document based pricing or named user pricing, and the election sits in the order document.
Document every third party integration and confirm the chosen pricing model at each renewal cycle, or the position stays untested.
A ninety day rehearsal cut the measured position by around 22 percent on average across the SAP reviews we completed. The cut came from four motions: dormant user reclassification, role rationalization, engine usage reset, and an indirect access audit. It held into the official run without any user losing required access.
Three artefacts hold the audit position. The order document inventory covers every SAP order from the initial purchase through every amendment. The certificate inventory matches each entitlement to its order document. The cleansed USMM and LAW record demonstrates the measurement discipline.
Redress runs the certificate inventory, the USMM rehearsal, the LAW aggregation, the four cleansing motions, and the official submission inside the Vendor Shield subscription and the Renewal Program. The work includes the contract review, the user master analysis, the role rationalization plan, and the indirect access audit.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the SAP service line, and the Software Spend Assessment.
Read the related SAP Intelligent Spend Group licensing, the SAP Knowledge Hub, the benchmarking service, and the Benchmark Program.
The companion playbook covers the RISE with SAP commercial frame, the conversion math from on premises maintenance, the FUE counting rule, and the buyer side moves that hold the discount band.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →Source: Redress Compliance advisory engagement file, 2024 to 2025.
The SAP audit reads what the system reports. The system reports what the buyer side does not clean. Ninety days of rehearsal cuts the measurement by twenty two percent without losing a single user.
Nine SAP compliance reviews completed with median twenty two percent measurement reduction. Every engagement starts with one conversation.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
