SAP BoM vs What You Actually Use: The Licence Gap Analysis

The BoM-Usage Gap: How It Develops and Why It Persists

The gap between what is in your SAP BoM and what you actually use is not accidental. It is the predictable outcome of three converging forces: SAP's sales incentives favour larger BoMs; enterprise procurement processes lack the SAP-specific expertise to challenge inflated proposals; and the complexity of SAP's licence model makes it difficult for customers to independently verify their true requirements.

The gap develops at signature — when SAP proposes user counts based on peak access figures, engine metrics based on worst-case business volumes, and product inclusions that have no deployment plan. It then widens during the contract term as business conditions change, user populations evolve, and technology choices shift, while the BoM remains static. A SAP BoM usage analysis conducted three years into a five-year contract will typically show that the gap has grown from the already-inflated starting point.

Understanding this gap matters for several reasons. First, the direct financial cost: maintenance is charged at 22% of the TNLV annually, so every €1M of over-licenced BoM value costs €220,000 per year in unnecessary maintenance. Second, the compliance risk: over-licenced areas can mask under-licenced areas that are invisible until an audit. Third, and most importantly for renewal planning, the gap represents negotiating leverage. An enterprise that can demonstrate — with evidence — that 30% of its BoM is unutilised enters renewal discussions from a fundamentally different position than one negotiating on list price and discount alone.

Our SAP licence optimisation service is built around a systematic gap analysis that quantifies over-licensing across every BoM component — giving enterprises the evidence base they need to negotiate from a position of documented fact rather than commercial aspiration. The complete SAP BoM review guide provides the broader framework for this analysis.

Measuring Actual Named User Consumption

Named Users represent the largest single component of most SAP BoMs, and they are the area where the usage gap is most consistently significant. Measuring actual Named User consumption against BoM entitlements requires three specific data sources.

USMM Active User Analysis

USMM (User System Measurement for SAP) measures every user who has accessed the system within the measurement period. The default SAP approach is to count all users with any system access in the past 12 months. An independent SAP BoM usage analysis goes deeper: extracting the transaction logs for each user type and identifying the frequency, recency, and depth of actual system interaction.

The distinction between a user who accesses SAP weekly to execute complex procurement workflows and a user who logged in once eight months ago to view a report is commercially significant. SAP's measurement counts both as active Professional users. An independent analysis distinguishes between genuinely active users and occasional or legacy users — generating a defensible reduction in the active Named User count.

Access Profile vs Transaction Usage Analysis

The second layer of Named User gap analysis examines the relationship between what users are authorised to do (access profiles) and what they actually do (transaction execution logs). This analysis consistently reveals a population of users who are authorised for Professional-level transactions but whose actual usage is limited to a subset that would justify a lower-cost user classification.

A warehouse supervisor authorised for the full MM (Materials Management) module but who only executes goods receipt transactions falls into this category. Reclassifying such users from Professional to Limited Professional is supported by their actual usage evidence and represents a legitimate, contractually defensible reduction in BoM value. Our SAP licensing basics guide provides the full Named User classification framework for reference.

Inactive and Ghost Users

Most large SAP landscapes contain a population of user accounts that were created for employees who have since left the organisation, contractors whose engagements ended, or system users who are no longer needed. These accounts remain licensed in the BoM if they have not been explicitly deactivated and removed from the measurement. A ghost user cleanup — identifying and deactivating accounts that have had no system access in the past six months — typically reduces Named User counts by 5–15% on its own, representing immediate maintenance savings.

Engine and Product Usage Gaps: The Less Visible Over-Licensing

Named User over-licensing is visible and measurable through USMM. Engine and product usage gaps are harder to quantify but often represent equally large — or larger — financial exposure.

Engine Metric Analysis

Engine licences are measured by a business metric — Revenue, Order Volume, Shipment Units, or similar — that is specific to the product and agreed in the contract. The BoM specifies the maximum metric value covered by the Engine licence. A SAP BoM usage analysis for Engine licences compares the contracted metric ceiling against actual business performance over the measurement period.

For most enterprises, the Engine metric in the BoM was set based on SAP's projection of peak business volumes, with a margin added for growth. If business volumes have been lower than projected — due to market conditions, operational changes, or simply conservative over-provisioning — the Engine licence may be significantly larger than required. Documenting actual engine consumption over 24–36 months establishes the evidence base for renegotiating engine metrics at renewal to reflect actual business reality.

Undeployed Products

Industry surveys consistently show that 40–50% of SAP customers have at least one product in their BoM that has never been fully deployed. These products generate maintenance obligations from day one — at 22% of list value annually — without generating any business value. Common candidates include SAP Analytics Cloud entitlements included as deal sweeteners, SAP Signavio licences proposed in anticipation of a process improvement programme that never launched, and legacy industry solution packages that remain in the BoM from a previous contract cycle.

Identifying undeployed products requires a straightforward system deployment audit: for each product in the BoM, is there an active system installation, active users, and evidence of business value creation? Products where the answer is no are candidates for BoM removal or deferral to an options schedule. Even where SAP resists outright BoM removal, converting active licence obligations to deferred options (which carry no maintenance until activated) is often achievable.

Cloud Entitlement Consumption Analysis

For enterprises on RISE with SAP or with significant BTP entitlements, cloud usage analysis adds a critical dimension to the BoM gap picture. Cloud entitlements — BTP credits, SAP Analytics Cloud sessions, Integration Suite API calls — are consumption-based metrics that are frequently over-provisioned in the initial BoM.

SAP's RISE and BTP entitlement reviews typically focus on identifying over-consumption (which generates additional charges) rather than under-consumption (which represents wasted spend). An independent cloud consumption analysis examines both dimensions. Under-consumed cloud entitlements are a significant cost opportunity — not through direct refund, which SAP does not offer, but through negotiated credit mechanisms at renewal that apply unused entitlements against future obligations or reduce the renewal commitment requirement.

The analysis also examines consumption patterns across BTP services. Many enterprises activate BTP service subscriptions for proof-of-concept projects that never reach production. Active subscriptions generate consumption-based charges even when usage is minimal. Deactivating unused BTP service subscriptions reduces cloud cost without affecting business operations.

For a comprehensive view of your current post-signature BoM exposure, our analysis of SAP BoM hidden items added after signing is essential reading alongside this usage analysis framework.

Turning the BoM-Usage Gap Into Negotiating Leverage

Documentation of the BoM-usage gap is valuable not just as a record of over-payment, but as strategic preparation for renewal negotiations. An enterprise that enters renewal with a detailed, evidence-based SAP BoM usage analysis is in a fundamentally different negotiating position than one relying on internal gut feel or headline budget targets.

The practical application of gap analysis in renewal negotiations follows a defined sequence. First, present the gap data early — before SAP's account team presents their renewal proposal. Establish the over-licensing picture as the starting point for commercial discussion rather than allowing SAP to anchor the conversation on a proposed renewal value that assumes the current BoM is appropriate baseline.

Second, use the gap analysis to construct a right-sized BoM counter-proposal that reflects actual usage data. This is the SAP BoM counter-proposal process — building your own version of what the contract should contain before SAP presents theirs. The counter-proposal anchors the negotiation on your evidence rather than SAP's commercial interest.

Third, explicitly connect maintenance savings to contract extension decisions. SAP's commercial team have significant flexibility on maintenance rates — including Enterprise Support credits, maintenance rate reductions, and EarlyWatch-based adjustments — particularly when the customer is actively evaluating alternatives or considering deployment changes. A well-documented usage gap gives your team the standing to demand maintenance adjustments as a condition of renewal.

Right-Sizing the BoM at Renewal: What to Expect

The practical outcome of a successful SAP BoM usage analysis applied to renewal negotiations is a right-sized BoM — a Bill of Materials that reflects your actual requirements plus appropriate growth headroom, rather than SAP's commercial aspirations.

Right-sizing outcomes vary by BoM component. Named User reductions of 20–35% from the original BoM are achievable with strong usage evidence. Engine metric reductions of 15–25% are achievable where actual business performance can be documented below the contracted metric ceiling. Product removals and conversions to deferred options are achievable in 40–60% of cases where products have no active deployment plan.

The aggregate financial impact of right-sizing can be substantial. On a €3M BoM with typical over-licensing levels, a thorough usage analysis and renewal negotiation frequently delivers €600,000–1,000,000 in reduced annual maintenance commitments — compounding over a multi-year contract term.

What right-sizing does not do is make SAP happy. SAP's account teams are measured on renewal TCV maintenance or growth — a right-sized renewal that reduces BoM value is a commercial loss for the account team. Expect significant resistance, escalations, and alternative proposals designed to maintain BoM value through different mechanisms (new product additions, cloud bundle upgrades, RISE migration incentives). Having independent advisors from our SAP contract negotiation team present during these negotiations ensures the usage evidence remains central to the discussion rather than being displaced by SAP's commercial counter-narratives.