The SAP Quality Management engine is one of the older line items on the SAP price list, and its metric — inspection lots created per year — has a curious property: the contractually agreed number rarely matches the operational number, and the gap usually widens over time. Manufacturing process refinements, additional inspection points, expanded plant footprints, and the integration of incoming-inspection processes from acquired entities all push the metered count upward without anyone in procurement seeing the line until the next measurement window.
This piece walks through how QM is metered, the four sources of inspection-lot inflation we see most often, the S/4HANA conversion question, and the discipline that keeps the engine inside its contracted envelope.
How the engine is metered
The QM engine is licensed in tiers of inspection lots per calendar year. A typical contract bracket might license up to fifty thousand lots, with step-up tiers at one hundred thousand, two hundred and fifty thousand, and so on. The measurement is taken from transaction USMM, which counts inspection lots created in the prior measurement period in the QALS table.
What counts as an inspection lot
An inspection lot is the master record SAP creates whenever any quality inspection process is triggered. The triggers are broad: goods receipts that require incoming inspection, in-process inspections triggered by production-order operations, recurring inspections triggered by stock-period rules, source inspections triggered by purchase-order line characteristics, and customer-return inspections. Each triggered process creates a lot in QALS, and the lot is counted whether or not it ever progresses to a usage decision.
Why the metric is volatile
Inspection-lot creation is driven by master-data configuration: the inspection setup view on the material master, the inspection plan, and the inspection type configuration. Small changes to that configuration — for example, activating inspection type 01 on a previously uninspected material — multiply the lot count without changing any procurement decision or any operational SLA. The metric is highly sensitive to upstream configuration that the licence-management team rarely sees.
The four common sources of lot-count inflation
1. Inspection plan expansion during continuous-improvement cycles
Manufacturing operations that run continuous-improvement programmes routinely add inspection points to existing processes. Each added inspection point creates additional in-process lots on every production order it touches. A programme that adds two in-process inspections to an order that runs forty thousand times in a year is a quiet eighty-thousand-lot uplift. The decision is made on the manufacturing floor without any visibility to the licence-management function.
2. Goods-receipt inspection activation on previously waived materials
When a supplier quality issue arises, the standard response is to activate incoming inspection on the affected material. The activation is rarely reversed even after the supplier issue is closed, and the resulting inspection-lot creation runs at full goods-receipt frequency for years afterward. We have measured estates in which 30 to 60 per cent of incoming-inspection lots are created against materials with no recent quality issue.
3. Recurring-inspection rules on long-shelf-life stock
Recurring inspections triggered by stock-period rules create a lot every time a stock segment passes the configured interval. Materials with multiple batches, multiple storage locations, and multiple plants compound the lot count. A single material with one hundred batches across ten plants, configured for quarterly recurring inspection, creates four thousand recurring-inspection lots per year for that material alone.
4. Returns-handling inspections that never close
Customer-return inspections create lots that remain open until a usage decision is recorded. Estates with high return volumes and slow returns processing accumulate open lots in the system that continue to count against the measurement until they are closed, archived, or technically completed. Lot-volume inflation here is not real activity, but the audit position treats it as if it were.
The S/4HANA conversion question
S/4HANA preserves the QM module as part of the core ERP licence in most digital-edition price-list constructs, but the inspection-lot metric continues to apply to the on-premises retail edition and to many of the legacy ECC-conversion contracts. Customers converting to S/4HANA need to read the destination licence schedule carefully to understand whether the QM engine is being absorbed into the digital licence base or carried forward as a separate metered line.
The conversion negotiation is the right moment to address legacy lot-count inflation. SAP will accept a restated baseline that reflects the post-conversion operational reality if the customer can present a credible reduction plan with master-data hygiene and inspection-plan rationalisation steps. For background on the broader conversion mechanics, see our piece on S/4HANA engine conversion.
How an audit position is built
The SAP audit team's standard request for QM is the USMM extract plus the QALS table dump for the measurement period, together with the inspection-plan master data. The three together establish the lot count and the rationale for the rate. Where the lot count exceeds the contracted tier, the auditor proposes either a true-up to a higher tier or a one-time settlement for back-charges plus a tier upgrade.
A defensible response decomposes the lot count into the categories above and excludes from the contestable position the lots that were created by master-data inflation rather than operational expansion. The exclusion does not always succeed, but it consistently reduces the back-charge component of the settlement, which is often the larger of the two negotiation levers.
The administrative discipline
Three discipline points keep the QM engine inside the contracted envelope without compromising operational quality outcomes.
The quarterly master-data review
The quarterly review described above is the foundation. It should be calendar-driven, owned by the QM master-data steward, and reported to the licence-management function with a one-page summary of changes and lot-count trajectory.
The inspection-plan version control
Inspection plans should be version-controlled with change records, so that changes that drive lot-count growth can be traced back to the operational decision that triggered them. The change records become evidence in the audit defence position and enable the procurement team to push back on attribution of lot growth to general operational expansion.
The open-lot ageing report
A monthly ageing report on open inspection lots, with thresholds for technical completion of lots older than the operational SLA, prevents the returns-handling accumulation pattern. The report should be run on a calendar schedule and reviewed by the same steward who runs the master-data review. For the broader picture on engine metric self-declaration, see our overview of the self-declaration process.
The negotiation levers at renewal
When the QM engine entitlement comes up at renewal, three negotiation levers are worth exercising before signing. The first is a restated baseline that reflects a hygienic master-data starting point, with a written plan to maintain it. The second is a tier ladder that reflects the realistic operational trajectory rather than the worst-case inflation pattern. The third is an explicit exclusion of lots created by recurring inspection on long-shelf-life stock from the metered count, which is a negotiable carve-out under the standard contract template.
The carve-out for recurring-inspection lots is the most consistently undervalued lever. The lots in that category are routinely 20 to 50 per cent of the total inspection-lot population, and excluding them from the metered count changes the entire tier conversation. SAP will not offer the carve-out unprompted, but it is available in most contract negotiations where the customer brings the data to the table.
Where this fits in the broader engine map
The QM engine is one of several manufacturing-related engines that share data and operational drivers. The Materials Management engine, the Production Planning engine, and the Warehouse Management engine all interact with QM through goods-receipt and order-completion processes, and lot-count inflation in QM is frequently accompanied by metric inflation in those other engines. A reading of the QM position in isolation usually understates the broader engine-metric exposure on a manufacturing estate. See our piece on the MM engine metric and the S/4HANA topic page for the broader context.
The thirty-day action list
For estates with an annual QM measurement coming up inside the next ninety days, four immediate actions are worth scheduling. First, pull the QALS table for the most recent twelve months and break the lot count down by trigger category. Second, schedule the quarterly master-data review described above with the QM master-data steward, the production planning lead, and the licence-management lead. Third, identify recurring-inspection rules with intervals shorter than the operational SLA and propose interval relaxation through the operational change-control process. Fourth, technically complete or archive open inspection lots older than the operational ageing threshold. For deeper analytical background, our SAP Audit Defence Playbook includes a full engine-metric workbook, and the global manufacturer QM reduction case file shows the dollar impact of the discipline cycle. See also our service overview on SAP licence optimisation for engagement details.