License Administration Workbench — LAW — is the SAP-supplied tool that consolidates USMM output files across the buyer’s system landscape into a single estate-level position. It is the artefact most directly used by SAP’s License Audit and Compliance Services group to assess the buyer’s contractual position. LAW has evolved through several major versions, each carrying different consolidation logic, different deduplication behaviour, and different reporting depth. The version differences matter to the buyer because they determine what SAP can see, what cross-checks are possible, and where the audit signal sits. Across our USMM and LAW measurement advisory engagements we work with both major versions in the field and apply a comparison framework.
The generational history
The early LAW versions, often labelled in the field as LAW 1.x, were operational tools for SAP basis teams to consolidate measurement outputs across a small landscape. The output format was simple, the deduplication logic was rudimentary, and the cross-checking against contracted entitlement was largely a manual SAP-side activity. Most estates with substantial SAP history will have run LAW 1.x at some point in their compliance cycle.
LAW 2.0 extended the consolidation logic, improved the user deduplication across systems, and added structured output formats intended to support more substantial SAP-side analytics. Most current production landscapes use LAW 2.0 as the consolidation tool of record. LAW 3.0, the more recent generation, adds further analytical depth, finer-grained deduplication, and tighter integration with the SAP-side analysis tooling that consumes the consolidated output. The LAW consolidation pitfalls piece covers the operational mechanics common to both 2.0 and 3.0.
What changed in 2.0
The principal change in LAW 2.0 was the formalisation of cross-system user deduplication. The earlier versions deduplicated users on user-ID matching across systems; LAW 2.0 introduced additional matching criteria (name, email, employee identifier where available) that allowed the consolidation to identify the same human user across systems even where the user-IDs were not identical.
Implications for the consolidated position
For estates with consistent user-ID conventions across systems, the LAW 2.0 deduplication produces a consolidated user count similar to the LAW 1.x equivalent. For estates with inconsistent conventions — common where systems were brought into the landscape through acquisitions or where user provisioning was decentralised — LAW 2.0 produces a materially lower consolidated count, because users counted multiple times in LAW 1.x are now correctly identified as single individuals. The implication for buyers is that a LAW 2.0 consolidation often produces a more favourable position than a LAW 1.x consolidation of the same data, provided the deduplication is correctly configured. The system vs client measurement piece covers the related deduplication mechanics at the client level.
What changed in 3.0
LAW 3.0 introduces additional analytical layers on top of the LAW 2.0 consolidation engine. The principal additions are: more granular reporting on engine consumption with cross-system aggregation; tighter integration with the licence-type assignment data that supports the user reclassification analysis; and improved handling of the special user populations (technical users, reference users, communication users) that the earlier versions handled inconsistently.
The version also exposes consolidation logic that supports more sophisticated SAP-side cross-checking. The SAP analyst running the consolidated output through the audit tooling can identify patterns — high-volume reference user populations, engine consumption inconsistencies across sister systems, licence-type distributions that deviate materially from comparator estates — that the earlier output formats did not surface as clearly.
What the version means to the buyer
The buyer should care about the LAW version for three reasons. First, the consolidated user count produced by different versions can differ materially for the same underlying USMM outputs, which means the SAP-reported compliance position is partly a function of which LAW version SAP used to consolidate the buyer’s data. Second, the cross-checking that SAP can apply to the consolidated output is a function of the version’s analytical depth; later versions support more cross-checks and therefore surface more findings. Third, the buyer’s own internal use of LAW — the buyer should be running LAW on its own behalf as part of pre-submission analysis — should match the version SAP uses, or risk presenting a position calibrated against a different reference dataset.
The LAW version is not a back-office detail. It is the consolidation engine through which the buyer’s estate-level position is constructed, and the version differences are large enough to shift the SAP-reported position by several percentage points on user counts alone. Knowing which version is in play is part of the audit preparation.
Cross-version compatibility
The USMM output files produced by individual systems are generally compatible with multiple LAW versions; the version difference sits on the consolidation side rather than the per-system measurement side. The implication is that the buyer can run its own LAW analysis at any supported version, regardless of which version SAP uses for the official consolidation. Where the buyer’s LAW version differs from the SAP-side version, the comparison between the two outputs requires version-aware interpretation. The USMM output analysis piece covers the per-system file inspection that feeds the consolidation.
The pre-submission use of LAW
The most useful buyer-side use of LAW is in pre-submission analysis: the buyer runs LAW on its own behalf against the USMM outputs from each system, identifies the consolidated position, identifies the user populations and engine consumptions that drive the position, and remediates the anomalies before submitting the official files to SAP. The exercise is mechanical but high-value: the consolidated view often reveals problems that the per-system view obscures (the same dormant user counted across multiple systems, the same reference-user shadow operating across the landscape, the same engine measurement script applied inconsistently across sister systems).
The remediation produced by pre-submission LAW analysis is typically the highest-value compliance work the buyer can do in the measurement cycle. The USMM and LAW measurement playbook white paper sets out the full pre-submission framework. The manufacturer USMM cleanup case file documents an estate that reduced its consolidated position by twenty-three per cent through pre-submission LAW analysis.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
The follow-through
The LAW version that SAP uses against the buyer’s submitted USMM data shapes what SAP can see and how SAP interprets it. The buyer who understands the version, runs its own LAW analysis at a comparable version, and presents a position calibrated against the same reference dataset, enters the compliance conversation on equal footing. The buyer who does not, enters the conversation interpreting outputs against a different lens than the SAP analyst is using. The license compliance topic page sets out the broader audit framework into which the LAW version fits.