A $7.8M SolMan claim, settled at two.

The brief

The client is a European industrial manufacturer with combined revenues above eight billion euros and SAP estate spanning Germany, Sweden, the Netherlands, and the United Kingdom. The estate was an ECC 6.0 core with SAP Solution Manager 7.2 used for technical operations, change management, and incident tracking across forty-three production environments.

The trigger was an engine reassertion notification issued by SAP during the manufacturer's S/4HANA conversion planning phase. SAP's account team asserted that Solution Manager had been used outside the contracted scope of the free-of-charge enterprise edition and that the manufacturer was therefore obliged to license the engine at the diagnostic-tools tier, retroactively for the prior thirty-six months and going forward through the converted estate.

The asserted shortfall was seven point eight million dollars, comprising back licence fees, support uplift, and a re-baselined annual run-rate. The reassertion arrived two weeks before the S/4HANA conversion scope was due to be signed, in what the procurement team interpreted as a linked negotiation.

The CFO and head of IT jointly engaged outside counsel before any data was returned to SAP, and before the conversion scoping continued.

The opening claim

SAP's position was built on a usage extract from the Solution Manager system itself, supplemented by interview notes taken from a brief discovery call held two months earlier with the manufacturer's basis lead. The combination of those two sources, in SAP's view, established that Solution Manager was being used as a paid-tier diagnostic platform rather than as the bundled enterprise edition.

The seven point eight million dollar figure was broken into three lines: three point one million for thirty-six months of historical licence fees calculated against a 1,200-user basis at the diagnostic tier; two point four million for support uplift on the historical position; and a two point three million annual run-rate built into the proposed S/4HANA conversion baseline.

Critically, SAP framed the reassertion as a precondition for the S/4HANA conversion to proceed at the previously discussed conversion credit level. The procurement team treated that framing as a coupling signal and immediately moved the matter onto a written procedural footing.

The defence

1. Diagnostic-tier scope reconstruction

We reconstructed the contracted scope of the Solution Manager enterprise edition against the original ECC contract, three subsequent renewals, and the published SAP product use rights document in force at the time of execution. The reconstruction showed that the manufacturer's usage fell squarely within the bundled scope, with no element triggering the diagnostic tier.

2. User basis re-measurement

The 1,200-user basis SAP had used was drawn from total Solution Manager accounts, including service accounts, decommissioned users, and read-only roles. We re-measured the basis against active production-impacting users only, producing a count of 217. Even under SAP's pricing assumption, that count did not approach the diagnostic-tier threshold.

3. Discovery-call disqualification

The discovery-call notes SAP relied on were marked informal and held under no confidentiality framework. We disqualified them as evidence and required SAP to support the reassertion from contemporaneous system logs only. Doing so removed the principal narrative anchor SAP had used to frame the breach.

4. Conversion coupling disconnection

We documented the conversion-credit conversation history in writing and required SAP to address the SolMan reassertion as a standalone matter. Decoupling the two negotiations removed the leverage SAP had counted on and reset the conversion track to its prior commercial position.

The settlement

Settlement closed at one point nine million dollars covering a forward-looking three-year subscription to a specifically negotiated SolMan tier that matched the manufacturer's actual usage profile. The historical back-licence and support-uplift lines were dropped in full.

Three contract clauses were rewritten. The Solution Manager scope clause was rewritten to specify, by feature and by user class, what was included in the bundled tier. A definitions annex was added covering the engine metrics. And a non-coupling clause was added to the S/4HANA conversion agreement preventing the linking of future engine reassertions to the conversion economics.

Total elapsed time from the original reassertion notification to signed settlement was fourteen weeks. The S/4HANA conversion proceeded on the originally discussed conversion-credit terms.

The lessons

• Solution Manager reassertion claims are a routine SAP pre-conversion tactic. They are usually built on broad user-basis assumptions and historical interview notes rather than contemporaneous system evidence.
• The bundled SolMan enterprise edition is broader than many SAP account teams represent. The product use rights document in force at execution is the binding scope, not the current marketing material.
• Discovery calls held outside an NDA framework cannot be used as evidence in a measurement dispute. Require all such conversations to be confidential and on the record.
• Engine reassertions issued in the months before a major contract refresh should be assumed to be coupled to the larger negotiation. Decouple them in writing before responding on the merits.
• User basis counts on SolMan should be filtered to production-impacting, active accounts only. Including service accounts and decommissioned users routinely inflates the count by an order of magnitude.

Cross-reference these lessons against the firm's SAP S/4HANA topic page, the Engine Metrics Reconciliation white paper, and the broader analysis in the Engine Metrics reading cluster.