Chapter I · The Brief
The opening claim
The client is a global discrete-manufacturing group with twenty-three plants across the United States, Germany, Mexico, and China, producing components for the automotive and industrial-machinery markets. SAP S/4HANA 2021 supports manufacturing, quality, and finance functions across all plants. Eight engine licences sit on top of the named-user base, including Quality Management, Plant Maintenance, Production Planning, and Process Orchestration.
SAP's audit function issued a focused engine-measurement notification on Quality Management, with a stated concern that the actual inspection-lot volume materially exceeded the contracted entitlement. The opening position quoted five million six hundred thousand dollars, sized against an inspection-lot volume of 11.4 million annually across all plants.
The internal SAM team's review confirmed that the QM engine measurement output from the standard self-measurement was approximately the volume SAP had quoted, but flagged that the measurement counted every quality-inspection lot and every inspection-result record as a separate chargeable event. The contract definition of the QM engine metric was, on its face, the inspection-lot count only.
External advice was instructed to reconstruct the measurement against the contract definition.
Chapter II · The Defence
The defence
The first workstream was a forensic review of the QM engine measurement output. We extracted the raw measurement data for the trailing twelve-month period and reconstructed it against the contract definition of "inspection lot" as set out in the active engine measurement schedule.
The standard SAP self-measurement output for Quality Management counts every record in the inspection-lot table plus every result-recording transaction plus every defect record. The contract definition counted inspection lots only. The corrected measurement against the contract definition produced an inspection-lot volume of 2.6 million annually, against the 11.4 million in the opening claim. The difference was: 4.8 million inspection-result records double-counted; 2.7 million defect records counted as separate lots; and 1.3 million records arising from inspection lot copies during multi-stage quality routes.
The corrected position was then run against the contracted engine entitlement, producing a final residual exposure of approximately $1.2M, against the $5.6M opening.
A subsidiary workstream identified that approximately one hundred and forty production plants in the SAP system were inactive shells from prior reorganisations that had never been deactivated. These accounted for approximately fourteen per cent of the false-positive inspection-lot count. We recommended their deactivation as part of the post-audit remediation.
Chapter III · The Settlement
The settlement
Settlement closed at one million two hundred thousand dollars, against the five point six million opening claim. The reduction was approximately seventy-nine per cent. No additional QM engine capacity was purchased; the corrected baseline fell within the existing contracted entitlement after the post-measurement remediation of the inactive plant codes.
Two contract clauses were rewritten in the release. The engine measurement clause for Quality Management was redefined to reference the inspection-lot count explicitly and to exclude inspection-result records, defect records, and lot copies arising from multi-stage routes. And a settlement-as-release clause closed any further claim on the audited period.
Elapsed time from the audit notification to closure was eight weeks. The focused scope of the engine-measurement matter, and the clarity of the contract definition once the measurement was reconstructed, allowed the negotiation to compress sharply.
Chapter IV · Lessons for Other Estates
The broader read
The matter closed under privilege and the specifics are confidential, but the methodology applies to most SAP estates of comparable size. The pattern is repeatable across the manufacturing sector and beyond.
Three observations applicable to other estates
- SAP's standard engine self-measurement outputs frequently include records that are not chargeable under the contract definition. The Quality Management engine in particular over-counts by a factor of four to five against most active engine schedules.
- Inactive plant codes, sales organisations, and company codes in S/4HANA systems are the most under-rated source of false positives in engine measurements. Deactivate them as part of a standing housekeeping discipline.
- Focused single-engine matters close faster than multi-line audits. Where SAP opens a focused position, resist any attempt to broaden the scope mid-negotiation.
For the firm's full procedural sequence on matters of this kind, see the SAP Engine Metric Deep Dive and the related working notes in the the sap engine metrics cluster.
