SAP's annual measurement cycle produces one USMM file per year. The file is the point-in-time view of the licensed estate. The point-in-time view is the input to compliance but not the input to defence. The defensive view is the trend: how the user counts have moved, how the classification distribution has moved, how the engine consumption has moved, and what those movements reveal about the operational reality of the estate. The estates that defend audits best treat the year-over-year comparison as a structured deliverable, not as a post-hoc analysis. This article walks through the comparison structure, the trend lines that matter, and the defensive value at the next audit. It is one of the patterns underneath our USMM and LAW advisory service.
What the auditor looks for
SAP's auditor reads year-over-year trends with three questions. Are the user counts moving in a direction that matches the operational reality (acquisitions up, divestitures down, growth phases up, restructuring down)? Are the classification distributions stable, or has the buyer reclassified users without changing their actual entitlement? Are the engine and package metrics moving in a direction that matches the operational deployment, or is the buyer flat-lining consumption that should be growing?
Where the trends do not match the operational reality, the auditor's hypothesis is that the buyer has manipulated the measurement to reduce the chargeable position. The hypothesis is rebuttable but only with evidence; without evidence, the auditor's hypothesis is the operative one. The evidence-pack article covers the rebuttal mechanism.
The three trend lines
Three trends are worth tracking from one measurement to the next.
User-population trend
The user-population trend captures the count of named users by classification, year over year. The trend should match the operational reality: hiring, acquisitions, organisational restructuring. Where the trend diverges from the operational reality, the divergence should be explainable: a dormancy cleanup, a classification rebuild, a contractor population shift. The explanation should be documented at the measurement, not constructed at the audit.
Classification-distribution trend
The classification distribution captures the proportion of users in each licence type. The trend signals the buyer's optimisation pattern: a falling Professional proportion and a rising Employee proportion typically indicates a deliberate optimisation programme; the opposite typically indicates uncontrolled classification drift. SAP's auditor reads both directions, with different concerns. Optimisation programmes attract the question of whether the reclassification reflects actual entitlement change; classification drift attracts the question of whether the prior classification was right.
Engine-metric trend
Engine and package metrics — HANA memory, BPC users, payroll-region counts, output-management documents — should trend with the underlying business volume. Flat engine metrics against growing transaction volumes are a flag. The flag may be explainable (archiving, business-process change, deduplication) but the explanation should be in the measurement notes. The engine-metrics topic page covers the metric definitions.
The baseline discipline
The baseline discipline is to capture, at each measurement, the data that supports the trend analysis at the next measurement. The discipline has three components.
The measurement snapshot
The USMM file alone is insufficient for trend analysis. The snapshot should include the underlying user-master extract, the role-to-licence mapping in force at the measurement, the engine-metric source data, and the configuration of the LAW consolidation. Together these form the measurement state that the next measurement compares against.
The operational reconciliation
The operational reconciliation maps the measurement state to the operational reality at the measurement date. It includes the HR headcount, the contractor population, the active project list, the integration inventory, and any organisational events (acquisitions, divestitures, restructuring). The reconciliation is the bridge from the measurement to the operational narrative.
The narrative document
The narrative document records the changes since the prior measurement and the reasons for them. Acquisitions add users; dormancy cleanups remove them; reclassification programmes shift the distribution; engine deployments change the consumption. The narrative answers the auditor's "what changed and why" question before the auditor asks it.
Estates that maintain the baseline discipline answer the year-over-year audit question in hours rather than weeks. Estates that do not maintain it spend the audit reconstructing two years of operational history under time pressure.
The three-year view
The most defensive trend view is the three-year rolling comparison. A single year-on-year change can be explained by a one-time event; a three-year trend tells the operational story. The auditor's hypothesis-building is harder against a coherent three-year trend than against a single-year delta. The discipline of maintaining the trend across three measurements compounds the defensive value.
The acquisition exception
Acquisitions create the most challenging year-over-year discontinuities. The acquired estate adds users, systems, and engine consumption in a single measurement step. The trend defence requires the acquisition documentation: the transaction date, the integration plan, the in-scope and out-of-scope systems, and the licensing position of the acquired estate. Without this documentation, the year-over-year jump appears to the auditor as uncontrolled growth. The LAW-consolidation article covers the acquisition-integration patterns.
The case-file reference
The media-company USMM/LAW cleanup case file documents a three-cycle baseline rebuild and the audit-defence value at the third cycle. The pattern is the working reference for the baseline-discipline approach.
The white-paper reference
Our USMM and LAW checklist white paper sets out the baseline-discipline section structure and the trend-line templates.
Where to start
Start with the prior two measurements. Build the three trend lines from the existing data, document the changes between them, and identify the gaps that would not survive an audit question. The exercise produces both the trend deliverable and the baseline-discipline framework for future cycles.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.