SAP License Audits Contact Us
Home · Case Studies · Case File 063 · S/4HANA Cloud Conversion

A baseline reset, $8.6M of conversion cost recovered.

A global CPG group challenged its S/4HANA Cloud conversion baseline, retired shelfware entitlements across nine country deployments, and removed $8.6M from the opening conversion commitment.

Consumer goods manufacturing line
Industry
Consumer Goods · Food & Beverage
Geography
Global · EMEA · APAC · Americas
SAP Estate
ECC → S/4HANA Public Cloud
In Scope
9,400 named users · 7 engines
— Case File 063 · S/4HANA Cloud Conversion

The headline numbers, on the record.

Every result on this site is anonymised at the client's request. Specific figures are real and verifiable through a confidentiality-protected reference call arranged on request. The firm's cumulative record stands at $180M+ in savings across 500+ engagements, with an average audit-claim reduction of 68% over 20+ years.

Opening claim
$33.4M
S/4HANA Cloud conversion commit
Settled value
$24.8M
after baseline rebuild
Reduction
26%
off opening
Duration
20wk
to closed conversion
Section I · The Brief

The client brief

The CPG group operated an ECC estate across nine country deployments — North America, UK, France, Germany, Italy, Spain, Brazil, Japan, and Australia — with 9,400 Named Users plus seven engine charges covering MM, SD, PP, FI/CO, HCM, BW and Solution Manager. The entitlement structure had grown unevenly across the country deployments with significant shelfware in three of the nine markets.

The board had approved an S/4HANA Public Cloud Edition conversion with a phased country-by-country rollout scheduled across the next twenty-four months. SAP's account team had quoted the conversion at $33.4M of incremental licence value across the 36-month conversion window.

The Group SAP Programme Director engaged us with a brief reflecting the CPG group's typical SAM maturity — the conversion needed to clean up the existing entitlement before crystallising it into the new contract. The team had visibility on the shelfware but lacked the documentation discipline to defend a reduction without external support.

Section II · The Opening Claim

SAP's opening position

SAP's opening proposal carried a country-by-country FUE allocation that summed to 11,200 FUEs across the nine markets. The allocation was built from the existing Named User and engine entitlements at SAP's published one-to-one conversion ratios, with no adjustment for the documented shelfware in the three under-utilised markets.

The headline figure included approximately $24M of FUE conversion value, $5.4M of HANA database extension across the country deployments, and $4M of new module add-ons including SAP IBP for supply-chain planning, SAP Concur for expense management, and an SAP Analytics Cloud subscription that had been proposed across the group during the prior fiscal year.

The framing positioned the country-by-country allocation as a contractual reconciliation of the existing fragmented estate. The implication was that the conversion would consolidate the entitlement into a cleaner structure — an implication that was directionally correct but commercially inflated against the actual usage population.

Section III · The Defence

The defence tactics

We worked the conversion as a country-by-country rebuild. Four reconstructions carried most of the reduction across the nine markets.

Per-country Named User audit

We rebuilt the Named User population against twelve months of transaction evidence in each country. The cumulative chargeable population was 7,800 against the reported 9,400. The three under-utilised markets — Italy, Spain, and Australia — carried the largest reductions, with combined shelfware of approximately 950 Named Users across the three.

Engine measurement reconciliation

The seven engine measurements were reconciled against country-specific usage. The MM engine was over-reported by approximately fifteen per cent against actual purchase-order volume. The HCM engine carried an active-employee count that included long-term inactive contractors. The combined engine reduction removed approximately 1,400 FUEs from the conversion baseline.

HANA footprint per-country measurement

The HANA database extension was quoted on a country-by-country projection that assumed full-scope production deployment in each market. We rebuilt the projection against measured database footprint and reduced the extension cost by approximately thirty-eight per cent.

Module add-on rationalisation

The proposed module add-ons were reviewed against deployment scope. SAP IBP was retained at a reduced subscription tied to the three markets where supply-chain planning was scoped. SAP Concur was retired — the group operated an existing expense system. SAP Analytics Cloud was retained at a reduced subscription matching the actual analyst population.

Section IV · The Settlement

The settled position

The S/4HANA Cloud conversion closed at $24.8M against the opening $33.4M, a twenty-six per cent reduction. The country-by-country FUE allocation was rebuilt against the reclassified populations, with each country carrying its own measurement schedule.

Contractually, we secured per-country FUE allocations with annual reconciliation rights, a HANA database extension priced on measured footprint per country, and a module add-on schedule tied to deployment scope rather than group-wide entitlement.

The group's SAM function adopted a per-country measurement cadence with quarterly reconciliation against the contractual baselines. The country-level governance is now the standing operating model rather than the previous group-wide aggregation.

Section V · Lessons Applicable

Five takeaways

  1. Multi-country CPG estates routinely carry uneven shelfware across the country deployments. The per-country rebuild reveals the variance that group-wide aggregation conceals.
  2. Engine measurements in MM and HCM are particularly susceptible to over-reporting through master-data drift. The country-level reconciliation removes one to two per cent of conversion value in most CPG estates.
  3. HANA footprint projections in country-by-country conversions assume full-scope production. The measured-footprint rebuild reduces the extension by thirty to fifty per cent.
  4. Module add-ons in CPG conversion proposals tend to assume group-wide deployment. The scope review typically retires one to two of the proposed add-ons entirely.
  5. Per-country contractual structures are negotiable. The country-level governance survives the conversion and provides ongoing reconciliation discipline.

Nine country deployments meant nine sub-conversions, not one. The work was to rebuild each one against actual usage, then aggregate up to the master agreement.

Group SAP Programme DirectorGlobal CPG Group · Q4 2025
Continue with the firm

The two services this matter drew on.

VIII.

S/4HANA Migration Compliance

Country-by-country conversion governance, per-country FUE audits, and engine reconciliation for global CPG estates.

Read the brief →
VII.

License Optimization

Continuous per-country Named User and engine right-sizing across multi-market SAP estates.

Read the brief →
Related reading

From the research desk.

— S/4HANA

SAP S/4HANA licensing, decoded

Conversion economics, country-level allocation and per-country measurement discipline.

Topic · Pillar
— White Paper

S/4HANA Migration Compliance

Pre-conversion reference on country-by-country FUE allocation and per-country measurement schedules.

Read the white paper
— Case Studies

Consumer goods engine metric reconciliation

How a consumer goods firm rebuilt its engine measurements across six markets and recovered $4.2M from a pending audit claim.

Case file
— Blog Pillar

S/4HANA: the conversion playbook

Cluster pillar on conversion economics and country-level measurement governance.

Pillar essay

Speak with a specialist.

An audit notification is not an invoice; a conversion proposal is not a contract. Both are opening positions. Speak with a specialist before responding. The first conversation is at no cost and under privilege.

Contact Us →
— Subscribe

SAP Audit Alerts · The weekly briefing

Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.