SAP system measurement runs through USMM at the system level, LAW at the consolidation level and SLAW at the group level. The Admodum read on the protocol, the measurement window, the categories of evidence and the buyer-side preparation discipline.
The SAP system measurement runs through three transactions. USMM (the User and System Measurement transaction) executes at the individual SAP system level: it reads the SU01 user-master record, classifies each user against the contracted licence categories, and produces the per-system measurement output. LAW (the License Administration Workbench, transaction SLAW2) executes at the consolidation level: it pulls in the USMM outputs from each connected SAP system, deduplicates the users where the same person carries accounts on multiple systems, and produces the consolidated measurement against the corporate user inventory. SLAW (the System Landscape Audit Workbench, the modern successor to the earlier LAW for the larger SAP estates) executes at the group level: it consolidates across the wider corporate group, including the cross-affiliate user populations and the affiliate-shared engine metrics.
The wider named-user recategorisation spoke reads the user-category surface against which the measurement output is built. The wider Digital Access explained spoke reads the indirect-access mechanic that runs in parallel with the named-user measurement.
The annual system measurement is a contractual obligation under the SAP enterprise agreement. The contract obliges the buyer to run the measurement at least once per contract year, to retain the measurement output, and to make the output available to SAP on request. The measurement window is either published in the contract (a fixed annual date) or vendor-defined (an SAP-requested measurement window with notice). The measurement output is the basis for the annual licence reconciliation: it is the input to the annual true-up and the input to any audit reading.
The contractual obligation is unconditional. The buyer cannot decline to run the measurement; the buyer can only control the preparation that runs ahead of it. The wider SAP renewal cycle spoke reads the renewal-side reconciliation of the measurement output against the renewal contract.
The measurement reads three categories of evidence. The first is the named-user inventory: the SU01 entries against the licensed user categories, with each user reading against the contracted category at the contracted price. The second is the engine-metric consumption: the package-and-engine measurement against the contracted metrics (the Order metric on SD, the PO line metric on MM, the patient-day metric on IS-H and so on). The third is the connected-system inventory: the documents-and-data flowing from non-SAP systems into the SAP digital core against the Digital Access metric (the nine-document-type read).
The three categories are independent: a buyer with a clean named-user position may still carry an engine-metric exposure; a buyer with a clean engine-metric position may still carry a Digital Access exposure. The reconciliation must run across all three. The wider indirect access history spoke reads the historical evolution of the connected-system reading.
The buyer-side preparation discipline runs the measurement against a private rehearsal first. The rehearsal executes the same USMM and LAW transactions, against the same user inventory, at a point ahead of the published measurement window. The rehearsal output is the buyer-side position: the position the buyer will present at the published measurement window, with the recategorisations, the cleared inactive accounts and the reconciled engine-metric readings already applied. The published measurement output then reads against the rehearsal output, not the other way around.
The rehearsal typically runs four to six weeks ahead of the published window. The rehearsal reveals the position-of-record: the surplus where the buyer holds more licence than the rehearsed measurement supports, and the deficit where the buyer holds less. The surplus becomes the renewal-side reduction lever; the deficit becomes the remediation work that runs ahead of the published measurement. The wider SAP audit defence spoke reads the audit-side framework against which the rehearsal output is presented.
The remediation window is the period between the rehearsal output and the published measurement window. The remediation work runs four streams in parallel. The first is the named-user remediation: the inactive-account clearance (the SM04-and-ST03N read for the dormant accounts, against the contractual retention period), the over-classified user recategorisation (the activity-based recategorisation against the licensed category set), the duplicate-account consolidation (the LAW consolidation against the same-person test). The second is the engine-metric remediation: the metric-base correction (the Order-count against the chargeable-order definition, the PO-line count against the chargeable-line definition). The third is the Digital Access remediation: the connected-system review against the nine-document-type classification.
The fourth is the contract-side remediation: the published-price-list-versus-contracted-price reconciliation (the buyer's contracted price is the position-of-record, not the publisher's published list); the contracted-category-versus-published-category reconciliation (the buyer's contracted category list is the position-of-record, not the publisher's current category list). The remediation output is the buyer-side measurement that runs at the published window.
At the published measurement window, the buyer presents the rehearsed-and-remediated measurement output. The output is the buyer-side position-of-record; the publisher-side measurement output reads against the buyer-side position, not against the unprepared estate. The annual licence reconciliation runs on the buyer-side output: the surplus is reduced at renewal (or held as shelfware credit); the deficit is closed at the contracted price (not at the publisher's current list price), with the published terms applying to the closure.
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The user-category surface against which the USMM output is built.
The audit-side framework against which the rehearsed measurement output is presented.
The connected-system inventory that runs in parallel with the named-user measurement.
A senior Admodum SAP advisor will read your USMM and LAW output, your rehearsal-versus-published delta and your remediation surface on a private call. Active renewal moments route to Renewal Programme; active audit moments route to Audit Defence.