SAP LAW (License Administration Workbench) is a central license audit data consolidation tool, created by SAP in 2002 to support contractual measurement in complex environments. It aggregates and deduplicates measurement results from multiple systems, but it does not classify users by actual usage, recycle inactive licenses, or model contractual scenarios. SAP LAW supports compliance—not optimization.
This distinction defines the budget. Organizations that treat SAP Law as a license management platform reach contract renewal without knowing how much of their own environment is wasted. SAP's measurement answers one question: is the declared consumption compatible with the contract? The cost-reducing question is another: what would the correct contract be if actual usage were the basis for sizing?
What is SAP Law?
SAP itself defines the License Administration Workbench as a tool for centrally consolidating license audit data, supporting the audit process in multi-system landscapes. Developed in 2002, SAP LAW was created to solve a specific operational problem: consolidating measurement results generated individually in each SAP system into a single view.
The central function is deduplication. The same employee can exist as a user in ECC, BW, Solution Manager, and satellite systems. Without consolidation, this employee would be counted multiple times in the Named Users count. The tool cross-references identifiers—employee number, email, SAP user ID—to reduce the count to distinct individuals.
The quality of the result depends entirely on the consistency of these identifiers across systems. When each environment is provisioned with different registration standards, deduplication fails silently, and the consolidated count is higher than reality. The tool doesn't signal the problem; it simply delivers the number.
What has changed in SAP LAW 2.0?
SAP LAW 2.0, released in 2014, maintained the original objective and added landscape organization and population clipping features. Two stand out:
- Managing system data — allows you to keep non-SAP systems within the scope of consolidation and create consolidation groups aligned with the organizational structure.
- User Group — enables secondary user selection criteria, useful for segmenting the calculation by area, company, or country.
These are usability and granularity improvements, not a change in purpose. Version 2.0 remains a tool for data collection, consolidation, and reporting for contractual compliance purposes. The complexity of configuring and maintaining the landscape continues to be the main obstacle to full adoption—many organizations operate the tool with the minimum necessary to meet the annual submission requirements.
Where does SAP Law fit into the measurement chain?
Understanding SAP Law requires separating four distinct roles that are often confused into a single block called "SAP audit".
| Component | Role | Scope | What decides |
|---|---|---|---|
| USMM | Measurement in the system: classifies Named Users and measures engines. | A system by execution | Nothing — it only reports what is registered. |
| SAP Law / Law 2.0 | Consolidation and deduplication between systems | Entire SAP landscape | Nothing — it consolidates what the USMM delivered. |
| SLAW / SLAW2 | Packaging and transporting the measurement to SAP. | Contractual submission | Nothing — carries the result. |
| SAM (Software Asset Management) | Lifecycle governance: actual use, contract, risk and cost. | Contract, environment and demand | Reclassification, recycling, negotiation and sizing |
None of the first three components has the mandate to question a user's classification, release an idle license, or simulate an alternative contractual scenario. That mandate belongs to... SAM.
Why SAP Law is not a license optimization solution.
SAP Law is much more of a data collection, measurement, and reporting tool for compliance than an optimization tool. The difference is not semantic: it's about contractual purpose. Measurement exists so that SAP can identify non-conformities and propose adjustments or renewals. The commercial interest embedded in the instrument is legitimate, but it belongs to SAP—not the client.
| What SAP Law delivers | What SAP Law doesn't deliver |
|---|---|
| Consolidation of measurement from multiple systems | Classification of users by actual usage profile. |
| User deduplication by identifier | Identifying inactive, duplicate, or over-licensed users. |
| Standardized report for submission to SAP. | Recycling and reallocation of released licenses. |
| Grouping users and systems according to organizational criteria. | Indirect access perspective and exposure to Digital Access |
| Documentary record for the audit process. | Simulation of contractual scenarios and support for negotiation. |
One piece of data illustrates the asymmetry: in typical SAP contracts, the Named User metric accounts for somewhere between 40% and 70% of the total cost. This is precisely the layer where SAP LAW simply reports what is registered, without evaluating whether the classification makes sense. A user registered as Professional who only performs queries will continue to be reported as Professional — and charged as such.
Four cost areas that measurement does not cover.
Named Users Classification
Named User types—Professional, Limited Professional, Developer, Self-Service, and contractual variants—define what a user can perform and how much it costs. The classification should reflect the actual usage profile. In practice, it reflects what was assigned during provisioning, often years earlier, for administrative convenience. Reclassifying based on transactions actually executed is one of the most direct cost reduction levers in an SAP environment.
Inactive users and technical accounts
Terminated employees with active accounts, test environments in production, and technical communication users treated as Named Users inflate the calculation without generating value. The system's user classification separates Dialog (interactive human access), System (communication between SAP systems), Communication (external integrations), and Service (applications with controlled usage) profiles. Handling these categories correctly and cleaning up obsolete accounts before measurement—not after—is a matter of SAM discipline, not audit tool discipline.
Indirect Access and Digital Access
Indirect use occurs when external users or systems access, query, or trigger SAP data and functions without directly using the system interface. A CRM that queries the customer database in SAP constitutes usage and, therefore, must be licensed according to the contractual rules.
There is one recognized exception, indirect static reading, which requires three criteria to be met simultaneously: the process in SAP was initiated by a licensed user; the data is exported automatically and on a scheduled basis; and there is no real-time query, update, or direct request to SAP during the consumption of this information. If any criterion is failed, licensing is required.
Since 2018, SAP has offered the Digital Access model, which licenses documents instead of users. Nine document types are accounted for—including sales, invoice, purchase, service, manufacturing, quality, time, financial, and material—and the count occurs at the time of document creation, not on subsequent readings. Mapping integrations and estimating document volume is an architecture and contract analysis. SAP Law does not perform this task.
Hybrid environments, RISE with SAP and FUE
Migrating to SAP S/4HANA and RISE with SAP changes the scaling logic. In the S/4HANA Cloud private edition, access is organized into tiers — Advanced Use, Core Use, Self-Service Use, and Developer Access — consolidated by the FUE (Full Use Equivalent) metric. Within the same client, on-premise contracts measured by Named User coexist with cloud contracts measured by consumption. Consolidating these two logics into a single view of financial exposure is an asset governance responsibility, outside the scope of any measurement tool.
SAM lifecycle applied to the SAP environment
SAM organizes SAP license management in chained phases, each with its own deliverable:
- Plan — consolidate contracts, usage rights, and measurement history into a single, reliable database.
- Acquire — negotiate based on real usage data, not on project estimates or contractual inertia.
- Deploy — assign the correct license type to the usage profile from the provisioning stage.
- Manage — continuously monitor usage, integrations, indirect access, and classification deviations.
- Decommission and recycle — release licenses from inactive users and reallocate them before purchasing new ones.
When applied consistently, this cycle reduces acquisition and maintenance costs, supports contractual and legal compliance—including standards such as ISO/IEC 19770-1 and internal control requirements like Sarbanes-Oxley—and strengthens governance. Annual measurement ceases to be a risk event and becomes confirmation of a known state.
How to use SAP Law to your advantage
Dismissing SAP Law would be a mistake symmetrical to overestimating it. The tool is essential in the measurement process and produces useful data. The point is the order of operations.
- Perform the measurement in internal cycles throughout the year, not just when SAP requests it.
- Standardize user identifiers across systems before consolidation so that deduplication works.
- Compare the consolidated result with an independent assessment of actual usage and investigate each discrepancy.
- Cleanse accounts, reclassify profiles, and recycle licenses before submission.
- Treat the official response window as a correction period, not a preparation period.
Simply ensuring compliance, or operating with isolated analyses of fragmented solutions, is insufficient for those who need real licensing efficiency. The way forward is to integrate SAP measurement into a structured practice of... IT asset management, with reliable inventory, usage data, and contractual governance operating continuously.
The role of a specialist partner
SAP environments demand dual expertise: technical knowledge of the landscape (Basis, authorizations, integrations) and mastery of contractual licensing rules. 4MATT is a ServiceNow Elite Partner in Brazil, with over 80 certified specialists, and is the only Brazilian partner with Product Line Achievement (PLA) in Software Asset Management — recognition that validates technical capacity and a track record of delivery in SAM.
In practice, this means combining specialized SAM tools, contract analysis, and cost accounting methodology to transform measurement results into cost decisions. For the design of this initiative, the supplementary material on... SAP license management and optimization It details the steps, audit risks, and maturity criteria.
Frequently asked questions about SAP LAW
Is SAP Law a SAM tool?
No. SAP LAW is a license audit data consolidation tool. SAM is a governance practice that covers contract, actual usage, risk, and cost throughout the license lifecycle. They are distinct and complementary layers.
What is the difference between USMM and SAP LAW?
USMM performs measurement within an SAP system, classifying Named Users and measuring engines. SAP LAW consolidates the results from multiple systems into a single view and deduplicates users that exist in more than one environment.
Does SAP LAW 2.0 replace the previous version?
SAP LAW 2.0 is the evolution of the tool, with additional features for system data management and user grouping. The purpose remains the same: to consolidate measurement data for contractual compliance purposes.
Does SAP Law measure indirect access?
Not in a way that adequately addresses the decision. Exposure to indirect use and Digital Access depends on mapping integrations, the volume of documents created by external systems, and contractual analysis—work that falls outside the scope of SAP LAW.
How can I safely reduce my SAP licensing costs?
Reclassifying users based on their actual usage profile, cleaning up inactive and technical accounts, controlling integrations that generate indirect usage, and recycling licenses before new acquisitions — always with documented traceability to support the position in audits.