US$600 million.
That was the amount SAP sought in damages in its licensing dispute with AB InBev. [Source: https://www.bizjournals.com/stlouis/news/2017/06/06/a-b-inbev-in-600-million-software-license-dispute.html] The case involved allegations of direct and indirect use of SAP systems and data without the appropriate licenses. The dispute was eventually settled between both the parties.
A similar situation came up in the Diageo case. [UK High Court judgment - SAP v. Diageo - https://www.bailii.org/ew/cases/EWHC/TCC/2017/189.html] SAP sought approximately £54.5 million in additional license and maintenance fees, arguing that third-party applications were indirectly accessing SAP ERP. The UK High Court ultimately ruled in SAP's favour on the key licensing issue.
These weren't companies that had suddenly decided not to pay for SAP. The problem was much more complicated.
SAP environments had grown over time. So had the integrations, users, interfaces, connected applications, custom developments, and everything else around them. As the landscape became more complex, it became increasingly difficult to see the gap between what the business was actually using and what it was licensed for.
The evaluation mechanisms weren't always clear either, and many customers raised this as a concern.
At the same time, this created a sweet spot for a new category of companies. SAP licensing became a much bigger concern for customers, and companies started offering tools specifically for SAP License Management and Optimization. Some tools promised ~40% savings. Others promised automatic license adjustments and optimization.
Organizations started investing heavily in these SAP licensing optimization tools.
But in April 2018, SAP changed the conversation by formally introducing the Digital Access approach for indirect access.
https://news.sap.com/wp-content/blogs.dir/1/files/Indirect_Access_Guide_for_SAP_Installed_Base.pdf
Later, SAP also released and embedded Digital Access evaluation capabilities for SAP ECC and SAP S/4HANA. The relevant SAP Notes & links are included below:
- SAP Note 2992090 – Completely revised digital access estimation report 2 for ECC
- SAP Note 2738406 - Digital Access: Central Technical Guidelines
- SAP Note 2999672 – Completely revised digital access estimation report 2 for S/4H
- https://support.sap.com/en/my-support/systems-installations/glac/digital-access-evaluation-service.html?isu_page=1&anchorId=section_948331799
But that still left another important part of the licensing equation: named-user licensing.
With the introduction of the SAP S/4HANA Enterprise Management licensing model, and later the FUE-based model adopted by many cloud customers, SAP licensing became a little more structured - and, in some ways, simpler to evaluate.
And this is where the question becomes interesting:
Do you still need to invest in a SAP License Management tool?
Or has SAP itself already provided enough capabilities to help you understand what you are using, what you are paying for, and where the actual optimization opportunities are?
Before investing in yet another tool, there is a more important question to ask:
Do you really need a SAP License Management tool, and what exactly should it be managing?
The market for SAP license management tools is built on a single anxiety: that SAP licensing is too complex to govern without buying outside help. The anxiety is real. The conclusion drawn from it is frequently wrong.
SAP licensing is genuinely intricate. Named user types, engine metrics, digital access documents, and the shift to S/4HANA classification all create room for expensive error. That complexity has supported a healthy market of license management tools for SAP, most promising the same three things. What has changed, quietly and materially, is that SAP now ships much of that same capability inside the system an organization already owns.
The Promise on the table - What the pitch usually says
A familiar message circulates across the SAP license optimization market. It promises 100 percent automation of SAP license management across the entire landscape, guaranteed savings of 40 to 50 percent on SAP license costs, and a trusted solution that protects the SAP investment. The language is polished and the arithmetic is seductive.
The claims are not dishonest. Real savings do exist inside most SAP landscape, usually from over-classified users sitting on the expensive Professional/Advanced metric. The open question is not whether savings exist. It is whether an organization needs to buy a third-party platform to capture them.
What SAP Already Provides - The native stack, and how far it now reaches
SAP provides a connected set of measurement and analysis tools. Most SAP customers meet them only reactively, at the point of an audit request. Used proactively, they cover the core of what the commercial tools advertise.
- USMM: The System Measurement transaction. It counts named users by license type and measures engine consumption on each SAP system. It is the foundation every other tool, whether native or third-party, builds on.
- LAW / SLAW2: The License Administration Workbench. It consolidates USMM results across multiple systems, de-duplicates users who appear in more than one, and produces the single combined position SAP works from.
- STAR: The S/4HANA Trusted Authorization Review ruleset. Lifesaver to many today! It analyses authorizations to model how users would classify under the S/4HANA license model, which is exactly the analysis the ECC-to-S/4HANA transition requires.
- SAM4U: SAP’s current-generation tool, first shown at Sapphire in June 2024. It is deployed into the customer landscape through SAP notes, presents license inventory through Fiori dashboards, runs the STAR authorization analysis, flags over-classified users, and simulates the S/4HANA mapping. It is offered as a complementary tool, at no additional license charge.
The measurement engine, the consolidation layer, and now an optimization and simulation dashboard are all available inside SAP, at no extra license cost. For a large share of organizations, that is the capability a third-party contract was going to be signed to obtain.
Six facts that you must understand before a licensing tool contract
1. The measurement backbone already ships with the system.
USMM, LAW, and SLAW2 are standard SAP transactions. Run internally on a schedule, they let an organization rehearse the exact measurement SAP will perform, and correct classification before SAP ever sees the data. No purchase is required to run them. When coupled with STAR and SAM4U, they can give many dimensions. You may not need another solution.
2. SAP now provides the optimization layer too.
The historic gap in the native tools was analysis: the old measurement transactions reported compliance but did little to help right-size it. SAM4U closes much of that gap. It surfaces users parked on the costly Professional/advanced metric who could sit on a cheaper type, and it does so using SAP’s own ruleset.
3. SAP’s evaluation basis is SAP’s own, and it is the only basis that settles an audit.
Whatever number a third-party tool produces, the figure that governs an audit outcome is the one SAP measures through their analysis. An outside estimate can inform a negotiation. It cannot override the measurement SAP itself performs. Put plainly, the only license numbers that hold at the table are the ones produced on SAP’s own basis.
4. No external provider can define the entitlement rules.
The definition of what each license type permits, and the ruleset that maps activity to a classification, belong to SAP. A third-party vendor can model, benchmark, and advise, but it cannot rewrite the rules SAP will apply. That is a structural limit on how far any external tool’s number can be trusted in isolation.
5. The native analysis can be extended to custom development.
A common argument for third-party tooling is coverage of custom Z-transactions and bespoke roles. In practice the authorization-based analysis can be configured to include custom transactions and roles, so a modest customization effort extends the evaluation across the bespoke estate rather than only standard SAP.
6. 100 percent automation is a claim, not a reality.
License classification depends on human judgement about how a user actually works, and about how ambiguous activity should be interpreted. Independent SAP licensing advisers are consistent on this point: measurement can be automated, but correct classification and audit defence are not shelf exercises. A headline of full automation should be read as a marketing figure, not an operational guarantee.
The Honest Counterpoint - Where a specialist still earns its place
The SAP native tools handles steady-state compliance well. They does not cover every situation, and there are moments when a formal or independent licensing evaluation is a sound investment rather than an avoidable one; when the licensing basis itself is changing, and when exposure is genuinely hard to measure.
- S/4HANA conversion or a RISE with SAP move - the model shifts from classic named users to Full User Equivalents, every user is reclassified, and the conversion contract is the one chance to right-size before commitments are locked in.
- Contract renewal, a true-up, or a major purchase - an independent evaluation and benchmark strengthens the organization’s position against SAP’s own figures at the point leverage actually exists.
- Mergers, acquisitions, divestitures, or carve-outs - entitlements have to be split, transferred, or consolidated across combined estates, and transitional service periods create real exposure.
- No reliable baseline exists - where licensing has never been measured properly, a one-time evaluation establishes a clean, defensible position to manage from.
- Exposure is genuinely hard to measure. These are structural complexities the native tools surface but do not fully resolve.
- Indirect and digital access - third-party systems, interfaces, bots, and storefronts that generate documents drive document-based licensing, the area most easily miscounted and the one SAP audits most actively.
- Engine and metric-based licenses - entitlements measured on non-user metrics such as documents, orders, records, or HANA memory are difficult to interpret and defend without specialist input.
- Large, fragmented, multi-entity landscapes - many systems across many countries with de-centralized administration, where continuous monitoring exceeds what native consolidation runs comfortably.
- An active SAP audit or formal measurement request - particularly where a shortfall is suspected, independent analysis supports both defence and negotiation.
What this means for SAP licensing costs
For most organizations, the sequence that reduces SAP license cost is not a purchase. It is a process. Run the native measurement internally and often. Clean and correctly classify users before SAP does. Use SAM4U to find the over-classified Professional users and the unused entitlements. Treat any third-party tool as a decision to make after that baseline exists, not before, and only where scale, indirect access, or negotiation genuinely justifies it.
Software license optimization for SAP starts with disciplined use of what SAP already provides. Third-party spend is justified by the gap that remains, not by the anxiety that sold it.
Closing Perspective
SAP licensing is complex enough to make outside help feel necessary. For a growing share of organizations, it no longer is. The measurement, consolidation, and now the optimization and simulation capability all ship inside the system, at no additional license cost.
The disciplined question is not which SAP license management tool to buy. It is whether the organization has first used what it already owns. Most that ask it honestly find the answer changes the size of the cheque, or removes the need for one.
