USMM, LAW, and SAM4U: Understanding the SAP License Measurement Toolkit
SAP provides three standard tools for license measurement, each serving a distinct purpose. How they work together, what each one can and cannot do, and why ongoing use beats one-time audit preparation.
What separates license measurement from audit preparation
In practice, many organizations follow a familiar pattern: USMM gets run when SAP requests a measurement. LAW gets assembled when an Enhanced Audit is announced. SAM4U is installed, but the dashboard rarely gets opened.
That approach falls short. License measurement is not an audit event; it is a governance moment that surfaces during regular operations. The governance moment around usage asks every month: does FUE consumption match the contract? The governance moment around authorizations asks: are roles designed so that PCE metering produces the correct result?
Both governance moments only become manageable with a structured, consistent use of the right tools. The three tools have complementary functions. Organizations that use all three have a solid data foundation for audits, renewal negotiations, and internal governance reviews.
USMM: What it measures and what it misses
USMM (User and System Measurement Management) is the classic single-system measurement tool. The USMM transaction is available in every SAP system and is run by the SAP Basis administrator.
What USMM delivers
USMM measures named-user counts by license type as well as engine metrics for the respective system. The output is a measurement file that can be exported and submitted to SAP. In an on-premise context, USMM is the instrument for the Annual Measurement. In a PCE context, monthly automated metering takes over consumption measurement, but USMM remains relevant for internal self-audits and plausibility checks (source: SAP Help, License Administration Workbench).
What USMM does not do
One characteristic that frequently goes unnoticed: USMM counts every named user, regardless of whether they are active. Inactive accounts, meaning employees who have left the organization but were never removed from the system, inflate the measured license count. Duplicates from different usernames assigned to the same person do the same.
That makes USMM alone an incomplete governance instrument. It shows the raw inventory, not the optimized state. Regularly cleaning up inactive accounts after the 90-day no-login threshold is therefore a prerequisite for a reliable USMM measurement (source: Redress Compliance, SAP License Compliance Tools: USMM, LAW, SLAW, STAR).
A second blind spot: USMM measures per system. In a landscape with multiple productive SAP systems, USMM totals figures across all systems without recognizing that the same person holds user accounts in both System A and System B. That deduplication is LAW's job.
LAW: Consolidation and deduplication across all systems
LAW (License Administration Workbench, transaction code SLAW2) is the multi-system consolidation tool. Its core capability is deduplication: when the same person holds user accounts in multiple systems, LAW counts them only once in the consolidated report (source: SAP Help, License Administration Workbench).
The LAW consolidation process
The process follows a defined sequence: USMM is run in each relevant system and the measurement files are exported. Those individual files are imported into LAW. LAW then attempts to match user accounts across systems automatically, using name, email address, and user ID. Accounts that cannot be matched automatically must be maintained manually. The resulting consolidated document is the LAW report submitted to SAP.
Where LAW reaches its limits
User matching in LAW is not error-free. A common example: the same person has the username "BMAENDLE" in ECC and "bernhard.maendle" in the BW system. LAW cannot automatically recognize these accounts as identical and reports them as two separate users. The result is an artificially inflated license count in the consolidated report.
Poor data hygiene in username assignment is therefore not just an IT housekeeping issue; it directly affects the license baseline. Organizations with consistent naming conventions across all systems significantly reduce the manual rework required in LAW.
In PCE metering, LAW is a central element of the architecture: the automated metering data from the customer system is consolidated via LAW and transmitted to SAP using a secured, anonymized protocol with hashed user IDs. SAP enriches the data with contractual entitlement information and makes the result visible in the SAP for Me dashboard.
SAM4U: The new center of ongoing license measurement
SAM4U (SAP Software Asset Manager) is a free tool installed in the customer system via SAP Note 3646933. One key difference from cloud-based SAM solutions: data stays within the customer's network. There is no transmission to SAP or to third parties (source: SAP Note 3646933).
What SAM4U offers
SAM4U delivers an interactive dashboard with several functional areas that make the governance moment around usage and the governance moment around authorizations both plannable and repeatable:
Enhanced SAP Usage Tracking provides more precise and more frequent usage data than classic USMM. It captures not just who is in the system, but what is actually being used. That forms the foundation for well-informed classification decisions.
Optimized Opportunities identifies concrete reclassification candidates: users for whom a downgrade from a higher to a lower FUE type would be substantively justified because their actual usage supports the lower level. This turns an analysis tool into an active governance instrument.
Authorization Simulation (new as of Q4/2025) allows you to simulate authorization changes and assess their impact on total FUE demand before implementing them. This is especially relevant for the governance moment around authorizations: anyone who wants to know the FUE effect of a planned role optimization can now calculate it before rollout, rather than measuring after the fact.
Starting in Q1/2026, a Data API will be available to integrate SAM4U data into external reporting platforms (source: SAP Note 3646933, DSAG AK Lizenzen 11/2025). This enables integration into broader governance tools without moving data outside the customer's network. FinOptory uses this API as the data foundation for ongoing contract governance.
SAM4U and SAP for Me working together
SAP for Me (me.sap.com/consumption) is the cloud portal for entitlements and consumption overview. The relevant access right is "License Utilization for Private Cloud." In a PCE context, SAP for Me receives the LAW-consolidated, SAP-enriched metering data and makes it available as a dashboard.
SAM4U and SAP for Me complement each other: SAM4U analyzes and optimizes within the customer system, while SAP for Me visualizes the contractual entitlement and measured consumption from SAP's perspective. Organizations that use both see both the internal optimization baseline and the external consumption standing from SAP's point of view.
PCE metering: How it changes the way you use these tools
The introduction of automated PCE metering in the Private Cloud Edition has fundamentally changed the cadence of license measurement. Where on-premise customers measure once a year, SAP triggers measurement in a PCE context monthly and automatically (source: SAP cross-product compliance documentation, 2025).
That changes the requirements for tool usage in three ways:
Frequency. The governance moment around authorizations, which in an on-premise context only had to be addressed once a year, becomes a monthly governance moment in a PCE context. The PCE metering dashboard in SAP for Me should be reviewed monthly: is consumption within the expected range? Are there outliers pointing to role creep or misclassifications?
Timing. Role optimizations should be completed before the monthly metering cycle, not after. Organizations that do not know their metering date may implement technically complete optimizations in the wrong month and miss a governance moment.
Quality boundaries. In practice, PCE metering shows known quality limitations that SAP continues to address. Discrepancies between automated metering and internal analyses such as STAR Reports are documented. The recommendation: record discrepancies in writing. An undocumented gap between your own understanding of the authorization structure and the metering result can work against you in a renewal context (source: DSAG AK Lizenzen 11/2025).
Working together: which tool for which task?
The four tools have complementary functions and cover different levels of license measurement:
| Tool | Primary function | Typical use |
|---|---|---|
| USMM | Single-system measurement, named users and engines | Annually on-premise, internally as a plausibility check in a PCE context |
| LAW | Consolidation and deduplication across all systems | Annual consolidation for the Annual Measurement, ongoing in PCE metering |
| SAM4U | Ongoing analysis, optimization, simulation | Monthly, quarterly self-audit, before the PCE metering cycle |
| SAP for Me | Entitlement and consumption dashboard from SAP's perspective | Monthly in a PCE context, as a comparison baseline before renewal |
For complete license governance, the interplay between tools is what matters: USMM and LAW supply the measurement data. SAM4U analyzes and optimizes on the basis of that data plus its own usage tracking. SAP for Me shows how SAP evaluates consumption. Only organizations that know all four perspectives can identify discrepancies before they surface in an audit.
What should run continuously
A structured governance rhythm for tool usage spans three levels:
Monthly: Review the PCE metering dashboard in SAP for Me. Compare consumption against the expected range. Document discrepancies.
Quarterly: Use the SAM4U dashboard for a self-audit. Identify inactive accounts past the 90-day threshold and clean them up. Prepare role optimizations based on Enhanced Usage Tracking and Authorization Simulation, and implement them before the next metering cycle.
Annually: Run LAW consolidation across all systems. Complete a full classification review. Validate the system inventory, including non-production systems.
This rhythm is not audit preparation. It is the foundation that makes the governance moment around usage and the governance moment around authorizations consistently actionable, regardless of whether SAP is currently requesting a measurement. Organizations that measure continuously do not need reactive audit preparation. The current state is already known.
Further articles in this series
This article is part of the Pillar 6 series on SAP license management and the maturity model.
- SAP License Management: License Types, Measurement, and the Maturity Model (Hub page)
- Cluster 2: Authorizations and FUE Costs: How Role Design Determines the License Baseline
- Cluster 4: SAP Audit Readiness: What Needs to Run Continuously (coming soon)
If you want to clarify what tool usage your current SAP license governance requires: the Contract Check delivers a structured assessment of your current state within four weeks, including recommendations for your governance rhythm. Fixed price: EUR 7,900.
FAQ
What is the difference between USMM and SAM4U?
USMM is SAP's classic standard tool for single-system measurement: it counts named users and engine metrics per system and generates a measurement file for the Annual Measurement or Enhanced Audits. SAM4U goes further: it analyzes actual usage, identifies optimization opportunities for FUE classification, and as of Q4/2025 also allows simulation of authorization changes before implementation. USMM measures; SAM4U governs.
Why do I need LAW if SAM4U already consolidates?
LAW and SAM4U handle different consolidation tasks. LAW is the officially submitted consolidation document for the Annual Measurement, and in PCE metering it serves as the technical infrastructure for data transfer. SAM4U consolidates internally for optimization purposes but is not the submission document for SAP. Both are needed: LAW for the official compliance perspective, SAM4U for the internal governance perspective.
How does PCE metering change the requirements for tool usage?
In an on-premise context, once a year was the decisive measurement point. PCE metering triggers monthly and automatically. That means SAP for Me should be reviewed monthly, role optimizations should be completed before the metering cycle, and discrepancies between your own understanding and SAP's metering result should be documented on an ongoing basis. The governance moment around authorizations is not an annual topic in a PCE context; it is a monthly one.
Does SAM4U data stay within my own system?
Yes. SAM4U is not a cloud service; it is installed directly in the customer system via SAP Note 3646933. Analysis data remains within the customer's network. Starting in Q1/2026, a Data API will be available to export SAM4U data into external platforms. The export is optional and under the customer's control.
How does SAM4U differ from commercial SAM tools?
SAM4U is free and specialized in SAP license measurement. It covers FUE classification, Enhanced Usage Tracking, Optimization Opportunities, and as of Q4/2025 Authorization Simulation. Commercial Software Asset Management tools have a broader scope covering all software products, but typically lack comparable SAP-specific depth for FUE classification and authorization-based analysis. For SAP license governance, SAM4U is the purpose-built instrument, designed specifically around SAP contract and governance requirements.
Next Steps
Would you like your SAP contracts reviewed for deadlines, clause risks, and available commercial levers?
This article is part of our topic hub on SAP license management and maturity model. To have one specific contract assessed, the FinOptory Contract Check delivers a structured basis within four weeks.
Last updated: July 2026