Decommissioned-system claim, defeated.

The retroactive engine claim

The manufacturer ran a global ECC instance with eleven licensed SAP engines spanning FI, MM, SD, BW, PM, QM, PI, and four industry-specific modules. Between 2021 and 2023 the firm executed a programme to retire six of the eleven engines as the underlying business processes were either decommissioned or migrated to non-SAP platforms. The decommissioning was tracked in the internal SAM register but not formally communicated to SAP.

The 2025 audit notification opened a measurement window covering 2022 through 2024 inclusive. The first measurement run captured all eleven engines as licensed and in-scope, and applied historical volume figures to engines that had been technically retired but were still represented in the licence administration workbench. The headline claim from SAP was $6.8M in cumulative overage across the three-year window.

The internal team was prepared to settle around $4.5M based on the assumption that the retired engines had no formal SAP-side documentation and therefore no contractual basis for exclusion. The procurement leadership engaged us with a brief to reconstruct the retirement paper trail and test whether the exclusion was defensible.

The opening position

SAP's opening position counted all eleven engines as in-scope for the full three-year measurement window. The supporting workpaper applied each engine's contracted licence-base price to a measured volume figure derived from the licence administration workbench. The volume figures for the retired engines were extrapolated from the last recorded measurement before retirement, not from actual transaction data, because no transactions had occurred since retirement.

The contractual question was whether engines with zero transaction activity over the measurement window were subject to the engine metric at all. SAP's position was that until a formal retirement was logged and acknowledged, the engine remained licensed and the volume continued to accrue at the historical rate. Our position was that the contractual engine metric measured productive use, not licence-administration state, and zero productive use produced a zero measurement regardless of registration status.

Two of the six retired engines had been migrated to non-SAP successor systems with formal cutover documentation. Three had been retired internally with no successor. One had been replaced by a S/4HANA-native module under a separate licence. Each retirement had different evidentiary characteristics that needed separate treatment in the defence.

The defence

The defence ran on five evidentiary workstreams. The first was the formal decommissioning paper trail for each engine: cutover documents, IT change-management records, basis-team retirement notes, and where applicable, the SAP-acknowledged retirement correspondence. For three of the six engines, the documentation was already in place. For two, the documentation needed reconstruction from project records.

The second workstream was the transaction-activity baseline for each engine across the measurement window. The SAP basis team produced the per-engine transaction logs showing zero productive activity for the six retired engines from their respective retirement dates through the end of the measurement window. The logs were timestamped and cryptographically signed under the firm's standard basis procedures.

The third workstream addressed the contractual engine definition. The contract referenced "engines actively measured under the licence administration workbench for productive business use." The two qualifiers — "actively measured" and "productive business use" — were both demonstrable in the negative for the six retired engines, on the basis of the transaction logs.

The fourth workstream was the contractual carry-over exclusion. The contract included a clause specifying that engines retired with documented cutover were excluded from the metric prospectively. The clause had not been invoked by the firm because the internal team did not realise it existed. We reconstructed the clause-applicability for each engine, with the retirement dates and the documented cutover evidence aligned to each. The fifth workstream was a formal counter-position submission documenting the per-engine exclusion case, the supporting evidence, and proposing a goodwill settlement of $400,000 to close the historical period and a contract amendment removing the six retired engines from the licence base prospectively, with an automatic-retirement protocol triggered by twelve consecutive months of zero transaction activity.

The settlement

Settlement closed at the proposed $400,000 figure. The six retired engines were removed from the licence base by amendment. The automatic-retirement protocol was incorporated into the contract on a forward basis, with the twelve-month zero-activity threshold as the trigger. The reduction against opening was 94 percent.

The automatic-retirement protocol was the strategic outcome. The internal team no longer had to maintain a manual retirement register or remember to notify SAP when a system was retired. The contract itself triggered the exclusion based on observable usage. The protocol was applicable to future engine retirements as well as the historical six.

Total elapsed time from engagement to executed settlement was fourteen weeks. The audit window was closed with no further measurement obligation. The contract amendment was signed alongside the renewal that followed in the next quarter.

Five lessons for the next decommissioned-engine claim

• Retiring an engine internally is not the same as retiring it contractually. The internal cutover is a starting point; the contractual retirement requires documented evidence applied against the right clause.
• Zero transaction activity over a measurement window is the strongest evidence available. The basis logs are timestamped and verifiable. SAP cannot argue with a clean zero.
• The contractual engine definition almost always includes language around "productive use" or "active measurement." Both are demonstrable in the negative when the engine has been retired.
• Reconstruct the cutover paper trail before the audit, not after. The change-management records, the basis retirement notes, and the project closure documents are easier to assemble while still fresh.
• Negotiate an automatic-retirement protocol into the contract. The protocol removes the need for manual retirement declarations and protects against future versions of the same claim.

Further detail on the methodology behind the defence is set out in the Engine Metric Defence Guide white paper. For the broader topic context, see the cluster pillar on Engine metrics, the cluster pillar and the deep dive on Decommissioned-system engine handling. The topic landing at Engine Metrics provides the broader category context.