A global retailer surfaced a LAW multi-system counting error that overstated the Named User population by 8,400, reset the consolidated count, and removed $4.9M from a pending SAP audit claim.
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 client is a global retailer with thirty-two production SAP system IDs spanning S/4HANA Retail, ECC, Customer Activity Repository, and Hybris commerce. A scheduled SAP audit opened with a LAW snapshot showing 47,600 Named Users across the consolidated estate against a contracted entitlement of 38,200. The audit team's opening claim modelled the 9,400 shortfall at standard list prices for a $6.1M settlement.
The Group SAM lead engaged us in week two of the audit response window with a brief to investigate whether the LAW count was structurally correct before challenging the classification or remediating the overage. The internal assumption was that the 9,400 shortfall was real and the negotiation was about pricing.
The retailer had completed a major systems-consolidation programme in the prior fiscal year, including the cutover from three legacy ECC systems into a single S/4HANA Retail tenant. The transition had left a series of CUA snapshots in inconsistent states across the LAW lookup.
The LAW consolidation rule is straightforward in principle: every named user is counted once across the consolidated systems, with classification taken from the highest-band system in which the user is assigned. In practice, the consolidation depends on the system-ID-to-user-ID matching driven by the CUA snapshots fed into the LAW lookup at measurement.
The systems-consolidation programme had created three structural problems in the LAW data: the legacy ECC system IDs were still appearing in the snapshot for fourteen weeks post-cutover; the S/4HANA Retail tenant had inherited the user-ID convention from one of the legacy systems but with a system-ID prefix change that broke the LAW matching; and the CUA central system had a partially-rebuilt mapping that was creating duplicate records for migrated users.
The combination overstated the Named User count by 8,400 users — the same person counted across the legacy and S/4 environments because the LAW could not match them to a single identity.
We rebuilt the LAW consolidation from the source CUA snapshots with a corrected matching methodology and four parallel correction tracks.
The three legacy ECC system IDs that were still appearing in the snapshot were retired from the LAW configuration with a documented cutover date. The LAW snapshot was re-run with the legacy systems excluded and the consolidation re-executed.
A deduplication rebuild was run with email, employee-ID, and personnel-number cross-references rather than relying on the user-ID prefix matching that the standard LAW logic uses. The rebuild collapsed 8,400 duplicate identities into 4,200 unique persons.
The CUA central system was rebuilt with a corrected user mapping table sourced from the HR system of record. The rebuild was tested in a controlled environment and applied to the productive CUA over a six-week phased rollout.
The corrected LAW snapshot was submitted to SAP with a methodology note documenting the systems-consolidation cause of the original overstatement and the deduplication methodology applied to correct it. The submission was accepted after one round of technical clarification.
The audit closed at $1.2M against the opening $6.1M, an eighty per cent reduction. The corrected LAW snapshot showed 39,200 Named Users against the 38,200 contracted entitlement, with the residual 1,000-user true-up settled at a negotiated unit price reflecting the small overage scale.
Contractually, we secured an agreed LAW consolidation methodology referenced in the next contract cycle, a documented sign-off on the deduplication rules with SAP's audit team, and a measurement protocol for the next systems-consolidation event that pre-defines the LAW exclusion of legacy system IDs.
The internal SAM function adopted the corrected methodology as the standing LAW consolidation approach and the CUA central rebuild was carried forward to the next measurement cycle. The retailer recovered $4.9M of audit exposure that had originated entirely in a measurement artefact.
We spent two weeks proving the count was wrong before we engaged the auditor on price. The price conversation never happened — the count correction did the work.
Consolidation methodology, LAW snapshot rebuild, and CUA central mapping correction across multi-system SAP estates.
Read the brief →End-to-end SAP audit response including measurement-artefact correction, claim modelling, and settlement negotiation.
Read the brief →Self-measurement mechanics, the LAW consolidation, and the evidence files that hold up at audit.
Twenty-eight-page reference on USMM mechanics, LAW consolidation methodology, and measurement-artefact defence.
How an oil and gas major corrected a LAW consolidation error that overstated Named Users by 5,800.
It is the opening position of a negotiation. Speak with a specialist before responding. The first conversation is at no cost and under privilege.
Contact Us →Every Wednesday. Field reports from active matters, decoded SAP communications, and what to look for in the next audit cycle. Work email only.