MM procurement-volume claim, reconciled.

The MM procurement claim

The manufacturer ran SAP MM as the procurement spine for its global supply chain, with Ariba layered on for sourcing and contract management. The MM engine was licensed against a tier of 12 million annual procurement documents, covering purchase orders, goods receipts, invoice verifications, and related procurement transactions. The 2024 self-declaration produced a count of 18.4 million documents, triggering a $9.6M overage claim.

The supporting workpaper was a single output from the MM measurement utility, with no categorical breakdown. The internal procurement-systems team had treated the figure as deterministic on the basis that it was generated by SAP's own utility against the standard MM document tables.

The triggering observation was that the manufacturer's annual order volume reported in the procurement dashboard was approximately 8.5 million purchase orders, not 18.4 million. The gap between the dashboard figure and the engine declaration was over 9 million documents — the entire overage. The investigation focused on identifying what those 9 million documents were.

The opening position

SAP's opening position rested on the raw 18.4 million figure. The workpaper applied the tier overage rate to the 6.4 million excess, producing the $9.6M claim. There was no analysis of the document-type composition.

We obtained the MM document table for the measurement year and applied a deconstruction analysis. The categorical breakdown produced seven categories: 7.8 million purchase orders to external suppliers, 3.4 million intercompany stock-transfer orders, 2.6 million purchase-order revision and amendment lines, 2.1 million goods receipts against the existing purchase orders, 1.4 million invoice-verification documents posted against existing receipts, 0.8 million stock-movement documents internal to plants, and 0.3 million other.

Only the first category — 7.8 million external purchase orders — matched the contract definition under a strict reading. The next two categories — intercompany transfers and PO revisions — had documented exclusion bases. The remaining categories were either downstream postings dependent on the original PO or internal stock movements that were not procurement transactions in the contractual sense.

The defence

The defence ran on four workstreams. The first documented the categorical breakdown with source-table evidence, document-type filters, and per-category samples. The samples were drawn from each plant and each procurement type proportionally.

The second workstream addressed the intercompany stock-transfer orders — the 3.4 million category. Intercompany transfers are not external procurement transactions; they move material between the firm's own plants. The contractual engine definition referenced "procurement documents posted against external suppliers," and the intercompany transfers were demonstrably internal. The exclusion was uncontroversial once the supplier-classification field was demonstrated.

The third workstream addressed the PO revision lines — the 2.6 million category. Under standard MM behaviour, each revision to a purchase order generates a revision line in the document table. A single PO that goes through three revisions appears as four lines in the count, when contractually it is one procurement transaction. SAP's own measurement note from 2020 addressed this question and supported the net-PO counting approach.

The fourth workstream addressed the downstream postings — goods receipts, invoice verifications, and stock movements. These are not procurement transactions in the contractual sense; they are the operational consequences of the original PO. Counting them against the engine metric was double-counting the same business event. The exclusion was a contractual interpretation question, which we addressed with a written counter-position and supporting precedent. The counter-position offered a settled current-year measurement of 7.8 million external purchase orders, with a $2.8M goodwill payment to close the historical period and a renewed engine tier of 10 million annual external POs.

The settlement

Settlement closed at the proposed $2.8M figure with the proposed amendment. The current measurement was accepted at the defended 7.8 million PO count. The forward engine tier was renewed at 10 million annual external POs. The reduction against opening was 71 percent.

The amendment language was the durable outcome. The MM engine measurement methodology was now governed by an explicit contractual definition that the internal procurement-systems team could apply consistently. The Ariba integration project that the firm was planning would create additional procurement-document volume; the amendment ensured that integration didn't trigger a new engine claim.

Total elapsed time from engagement to executed settlement was nineteen weeks. The reduction against opening was 71 percent. The procurement-systems team adopted the categorical reporting in their quarterly licence-position reviews.

Five lessons for the next MM engine claim

• The MM measurement utility count is not the engine measurement. The engine measures external procurement transactions; the utility counts every MM document table row. The two figures diverge dramatically.
• Intercompany stock-transfer orders are not external procurement. The supplier-classification field distinguishes them. The exclusion is straightforward.
• Purchase-order revisions are not separate procurement transactions. SAP's own 2020 measurement note supports net-PO counting.
• Goods receipts, invoice verifications, and stock movements are downstream postings, not procurement transactions. Including them is double-counting.
• Refine the engine definition in the renewal amendment. Procurement transformations like an Ariba integration will increase document volumes; the contractual definition protects the licence position.

Further detail on the methodology behind the defence is set out in the Engine Metrics Reconciliation white paper. For the broader topic context, see the cluster pillar on Engine metrics, the cluster pillar and the deep dive on MM engine procurement volumes. The topic landing at Engine Metrics provides the broader category context.