SAP Bill of Materials: How to Audit It Before Signing

What the SAP BoM Actually Is — and Why It Matters

In SAP commercial terms, the Bill of Materials (BoM) is the schedule attached to your Order Form that specifies every product, user type, quantity, and price you are agreeing to purchase. It is not a draft, an estimate, or an indicative figure. The moment you countersign the Order Form, the BoM becomes your contractual baseline — the document SAP will use to calculate your annual maintenance, measure your compliance during audits, and benchmark your position during every future renewal negotiation.

Most enterprise legal and procurement teams treat the BoM as a technical annex — something the SAP account team fills in and the finance director approves based on headline price. This is exactly what SAP's commercial model is designed to exploit. The BoM is where SAP builds its revenue. It is where your spend is set, often for the next five years. And it is where independent SAP bill of materials audit delivers its most immediate financial return.

A typical BoM for a mid-size enterprise will include 40–120 line items covering Named User licences at various tiers (Professional, Limited Professional, Employee, Developer), Engine licences measured by revenue or processing volume, Package licences for industry solutions, and cloud subscription entitlements tied to BTP credits or SAP Analytics Cloud units. Each of these line items is negotiable. Each of them can be challenged. And in almost every BoM we audit, at least 20% of the value represents licences the customer either does not need, already has, or will never consume.

Our SAP contract negotiation service starts with a forensic BoM review because that is where the money is. Not in headline discount percentages, not in list price negotiations — in the specific composition of what you are actually buying.

How SAP Inflates the BoM — The Tactics You Need to Know

SAP's account teams are incentivised on Total Contract Value (TCV). Every additional line item in your BoM, every user count increment, every bundled product inclusion increases the TCV and improves the account team's commission position. Understanding this commercial reality is the starting point for any effective SAP bill of materials audit.

Peak User Counts Instead of Average or Active Users

SAP will typically propose user quantities based on peak system access figures — the maximum number of users who logged into the system during any measurement period. This approach inflates Named User counts significantly. Enterprise Support metrics count any user who has accessed the system in the past 12 months as an active user, even if they logged in once to check a report. A robust BoM audit challenges these numbers using USMM (User System Measurement for SAP) data to establish actual active, regular users — a figure that is almost always 30–50% lower than what SAP proposes.

Upward Classification of User Types

SAP's measurement tools, particularly LAW (License Administration Workbench), apply classification logic that defaults to the highest-cost user type when in doubt. An employee who occasionally approves a purchase order in the SAP GUI may be classified as a Professional user at €2,000 per year rather than a Limited Professional at €450 per year or an Employee user at €150 per year. Across hundreds of users, this classification drift creates enormous artificial spend. Challenging user type classifications is one of the highest-value activities in any BoM audit.

Bundled Products Added Without Discussion

SAP account teams frequently add products to the BoM that were never discussed in the sales process — SAP Analytics Cloud entitlements, BTP credits, Signavio process modelling licences, Datasphere units. These appear as "complementary inclusions" or "bundled value" but carry maintenance obligations, often at 22% annually, for the life of the contract. Signing a BoM with products you did not actively request locks you into maintenance payments for software you will never deploy.

Duplicate Coverage Across Licence Types

In complex SAP landscapes where organisations have accumulated licences through acquisitions, multiple Order Forms, and previous migrations, the BoM often includes duplicate entitlements — Professional user licences that cover the same functional area as Package licences already in the estate. A pre-signature SAP BoM review cross-references all existing entitlements against proposed new acquisitions to eliminate redundancy.

The Pre-Signature Audit Process: A Step-by-Step Framework

An effective SAP bill of materials audit follows a structured sequence. The goal is to build your own view of what you actually need before SAP's view becomes contractually binding.

Step 1: Run a Clean USMM Measurement

Before any BoM discussion, run an independent USMM measurement across your entire SAP landscape. USMM (User System Measurement for SAP) is SAP's own tool for counting users and their associated licence metrics, but it can be configured and interpreted in multiple ways. Run it without SAP's involvement, analyse the output using LAW, and establish your own baseline of active users by classification. This becomes your counter-evidence to challenge every user count in SAP's proposed BoM.

Step 2: Build Your Effective Licence Position

Your Effective Licence Position (ELP) is the reconciliation between what you currently own (existing entitlements across all contracts and Order Forms) and what you actually use (active users, active engines, deployed products). The ELP tells you where you are over-licensed, where you are under-licensed, and what — if anything — you genuinely need to acquire. Most enterprises are over-licensed by 15–30% before any negotiation begins.

Step 3: Map Every BoM Line Item Against the ELP

Take SAP's proposed BoM and compare each line item against your ELP. For every proposed user count, ask: what does our USMM data show for this user type? For every proposed Engine inclusion, ask: does our current Engine capacity cover this, or is there genuine headroom required? For every bundled product, ask: is this in our technology roadmap for the next three years, and what is the maintenance cost if we never deploy it?

Step 4: Draft Your Counter-BoM

Based on this analysis, construct a counter-BoM — your own version of what the Bill of Materials should contain, with quantities derived from your actual data rather than SAP's commercial proposals. This document becomes the basis of your negotiation. SAP will push back; having evidence-based numbers removes the subjective element from the discussion.

Step 5: Negotiate Specific Line Items, Not Just Headline Price

Most enterprises negotiate SAP contracts by pushing for a bigger discount on the total. This is a mistake. SAP controls list prices and can absorb headline discounts while maintaining margins on inflated quantities. The correct approach is to negotiate individual line items — challenging quantities, reclassifying users, removing products — before any headline price discussion begins. A BoM with 30% fewer line items at the same discount percentage represents far better value than the original at a 10% higher discount.

User Types to Challenge Line by Line

SAP's Named User licence model has seven primary user types, each with dramatically different pricing. Your BoM audit should examine every user in each category and assess whether the classification is genuinely justified.

Professional User

The Professional user licence covers unrestricted access to all SAP application functionality. It is the most expensive named user licence — typically €1,500–2,500 per user per year in maintenance. SAP account teams classify users as Professional when they have access to Professional-level transactions, even if they never use them. Restricting access profiles and reclassifying users to lower tiers reduces BoM value substantially. Challenge every Professional user count by asking: which specific transactions does this user actually execute regularly?

Limited Professional User

Limited Professional licences cover specific, restricted sets of SAP functionality and cost 30–40% of a full Professional licence. If your analysis shows that a significant proportion of proposed Professional users only execute a defined set of transactions (for example, expense submission, time recording, purchase order approval up to a threshold), reclassification to Limited Professional is legitimate and contractually defensible.

Employee Self-Service (ESS) and Manager Self-Service (MSS)

ESS and MSS users are the most frequently over-classified users in SAP landscapes. Employees who access only HR self-service functions — leave requests, pay slips, personal data — qualify for the Employee licence category at a fraction of Professional cost. SAP's measurement tools often classify these users upward because their access profiles technically include Professional transactions they have never executed. This is a common and challengeable inflation in any SAP bill of materials audit.

Developer Licences

Developer licences are required for users who write or modify ABAP code or configure SAP systems. Many organisations have Developer licences assigned to IT administrators who do not develop — they use developer access for transport management and system monitoring. Reviewing Developer licence assignments and removing inappropriate allocations reduces both BoM cost and ongoing audit risk. For deeper context, our SAP licensing basics guide covers the full Named User classification framework.

Engines, Packages, and Bundled Products — The Hidden BoM Cost

Named Users represent only part of the BoM. Engine-based licences, Industry Solution Packages, and cloud product entitlements often account for 30–50% of total BoM value — and are proportionally more likely to contain inflated metrics.

SAP Engine Licences

Engine licences measure usage by a business metric rather than by user count — Order Volume, Revenue, Shipment Units, or similar. SAP's proposals for Engine licence quantities are typically based on the maximum metric value your business might reach over the contract term, rather than your current or projected figures. Challenge Engine metrics using your actual three-year business performance data, with a reasonable growth projection, to establish defensible engine quantities.

SAP Industry Solution Packages (ISPs)

ISPs bundle a set of SAP functionality for specific industries — manufacturing, utilities, financial services. They are typically priced as package licences rather than per-user, and they are frequently included in BoMs as "standard inclusions" even when the customer has not specifically requested them. If an ISP is in your BoM, confirm: do you actually use the functionality it covers? If not, removing it is straightforward and saves both licence and maintenance cost.

SAP BTP and Cloud Add-Ons

SAP Business Technology Platform (BTP) entitlements — credits, service units, professional and enterprise tier subscriptions — appear in an increasing proportion of BoMs as SAP drives cloud adoption. BTP credits are frequently proposed in quantities that far exceed what the enterprise will consume in the contract period. Understanding what gets added to the BoM after signing is equally important — ensure the contract contains provisions preventing unilateral BoM additions post-signature.

The Data You Need Before Any BoM Negotiation

Effective SAP bill of materials audit is evidence-based. SAP's commercial team will present data that supports their position. You need to present data that supports yours. The following data assets are non-negotiable for any credible pre-signature BoM challenge.

• USMM Output: Run USMM across all productive systems covering the most recent 12 months. Export the full user classification detail, not just the summary. This is your primary source of truth for Named User quantities and types.
• LAW Analysis: Run LAW (License Administration Workbench) to consolidate USMM data across a multi-system landscape and produce your system measurement. Understand which users are counted where and why.
• Access Profile Analysis: For users classified as Professional, extract their actual transaction usage logs for the past 6–12 months. Users who appear in professional access profiles but execute only a narrow set of transactions are reclassification candidates.
• Engine Usage History: For Engine-based licences, extract 24–36 months of the relevant business metric data. Calculate the actual range and growth trajectory. Use this to challenge inflated Engine proposals.
• Existing Entitlement Inventory: Compile a complete list of all SAP products you are currently entitled to under all existing contracts and Order Forms. Cross-reference this against the proposed BoM to identify duplication.
• Technology Roadmap: Document which SAP products in the proposed BoM you have an active plan to deploy within the contract period. Products with no deployment plan should be removed or deferred to an options schedule.

Enterprises that present this evidence package enter BoM negotiations from a position of strength. SAP's commercial team know that the data exists and that a well-prepared customer with independent advice can challenge every inflated figure. Our analysis of SAP BoM vs actual usage consistently shows that the gap between what SAP proposes and what customers actually need averages 28% of BoM value — representing millions in unnecessary spend on a typical enterprise deal.

If you do not have the internal capability to run and interpret USMM and LAW, or to build an ELP from scratch, our SAP licence compliance service provides the technical analysis as a standalone engagement, with results delivered before your negotiation deadline.