SAP LAW Measurement: What It Reveals

What LAW is and is not

License Administration Workbench, abbreviated as LAW, is the technical tool that SAP customers use to consolidate user and engine measurement data across multiple SAP systems before the data is transmitted to SAP. LAW pulls data from USMM, the per system measurement tool, and produces a consolidated report at the enterprise level.

LAW is a measurement consolidation tool. It is not an audit. The audit is the contractual review and the commercial negotiation that follow the measurement. Customers who treat the LAW output as the audit finding have already lost the position that an audit is a contractual negotiation. The framework that sits behind this article is in our SAP license audit complete guide and our audit defense expertise page.

What LAW measures

LAW measures three categories of license consumption. Named user counts by user type, engine metric consumption by engine, and the consolidated indirect access related figures where SAP applies them. The named user portion is the most material in most engagements because it carries the largest aggregate license value across the typical estate.

The user portion is classified per the user type field in SU01 and per the contractually defined user types in the customer contract. The engine portion is measured per engine specific metrics that depend on the engine. PAYE for payroll, FTE for HR, line items for financial transactions, and similar metric definitions. The detail by engine is in our engine based licensing guide.

What LAW does not see

LAW measures what is recorded in the SAP system. LAW does not see indirect access from surrounding systems unless a Digital Access estimator or a comparable mechanism has been deployed. LAW does not see usage patterns. LAW does not see authorization that is granted but not exercised. LAW does not see business purpose. LAW does not see contractual user type bundling that the customer is entitled to.

Customers who treat the LAW output as the complete picture of license consumption are over reporting. The complete picture requires LAW output to be reconciled against authorization data, against business process documentation, and against contractual entitlements. Cross reference our named user license types guide and the indirect access explainer.

The LAW measurement is the input to the audit, not the output. Customers who reconcile the LAW data against authorization and entitlements before transmission to SAP typically reduce reported consumption by 15 to 30 percent without changing any underlying user license.

User misclassification patterns

The most material LAW finding pattern is user misclassification. SU01 user type fields drift over time. Users who were configured as a Professional user when initially provisioned remain Professional users even after their role changes to a Limited Professional or an Employee user. The reclassification of these users to the correct user type per contractual definitions is the single highest impact action that customers take before audit submission.

The reclassification follows three patterns. Authorization based reclassification, where the user is reclassified based on the authorization actually granted. Activity based reclassification, where the user is reclassified based on the transactions actually executed. And bundle based reclassification, where the user is reclassified based on the contractual bundle that includes the user type. Our named user reclassification guide explains each pattern with worked examples.

The measurement defense posture

The measurement defense posture is the set of customer positions that govern the LAW measurement. Three positions matter most. The user classification reflects authorization and entitlement, not historical configuration. The engine measurements reflect the contractual metric definitions, not SAP standard metric definitions when they differ. The indirect access estimator results, where used, reflect contractually defined trigger transactions, not the broader transaction set that SAP estimators default to.

The defense posture is established before LAW is run, recorded in writing, and applied during measurement. Customers who establish the posture after seeing the LAW results have lost the ability to influence the measurement. Cross reference our audit evidence pack guide and the audit readiness assessment.

Reconciling LAW against authorization

The reconciliation of LAW output against authorization data is the highest impact preparation activity. The reconciliation compares each user type in the LAW report against the authorization actually granted to the user. Where the authorization is narrower than the user type, the user is reclassified to the narrower user type. Where the authorization indicates a different user type, the user is reclassified to the indicated user type.

The reconciliation is run inside the customer environment using customer data. The reconciliation outputs feed into the LAW submission to SAP. The reconciliation does not require any change in production authorization. The reconciliation requires only a documented analysis that supports the user type assignment in LAW. Our authorization to license mapping guide includes the standard reconciliation framework.

Challenging LAW results

LAW results are not final. The contract typically provides that the LAW measurement is subject to customer review and reconciliation before the audit finding is established. Customers who file a written reconciliation response within the contractual review window typically reduce the LAW based finding by 25 to 45 percent. Customers who do not file a written reconciliation accept the LAW output as the audit finding.

The reconciliation response includes the user reclassification list with supporting authorization analysis, the engine metric corrections with supporting transaction analysis, and the indirect access estimator adjustments with supporting contractual analysis. The detail is in our audit findings dispute guide and our license optimization expertise.

LAW as a continuous tool

LAW is a continuous license management tool, not an annual audit tool. Customers who run LAW quarterly or monthly inside the internal license management cycle catch user drift before audit transmission, identify engine consumption changes before they become material findings, and maintain a continuous view of license posture that supports both audit defense and license optimization.

The continuous LAW cadence requires a defined internal owner, a documented reconciliation process, and a quarterly executive review of license posture. The investment is modest relative to the savings. Most Fortune 500 customers recover the investment within one audit cycle. Cross reference our SAP license optimization pillar, the license consulting service, and the license optimization expertise.