SAP License Audits Contact Us
Home/White Papers/SAP Engine Metric Deep Dive

The Engine Metric Deep Dive.

A forty-six-page contractual decoding of every SAP Engine metric in active use — Order, Document, Revenue, GB, CPU, Connection, Master Record, and the twenty-plus less common metrics — with the audit-defensible measurement positions for each.

Research Paper 46 pages Published April 2026 Format: PDF Access: Gated
What You'll Learn

Six learning outcomes, drawn from engine-metric engagements.

  1. Every active SAP Engine metric, contractually defined. Order, Document, Revenue, GB, CPU, Connection, Master Record, External User, and the long tail of less common engine metrics. What each measures, what each excludes, and what each costs.
  2. The measurement-window arithmetic for each metric. Twelve-month rolling, peak month, calendar year, contract year — which window governs each metric and how to read it correctly from the source data.
  3. The inclusion-exclusion boundaries that favour the customer. The documents, transactions, records, and connections that fall outside the licensable scope under contract, even when SAP's standard scripts count them in.
  4. The audit-defensible measurement protocol per metric. The source query, the validation step, the reconciliation against the SAP measurement, and the documentation that holds the position under scrutiny.
  5. The bundle-vs-standalone interaction effect. Where engine metrics sit within bundled products and how the bundle scope changes the licensable measurement.
  6. The S/4HANA migration impact on every metric. How each engine metric is renamed, re-scoped, or restructured under S/4HANA and the FUE-based RISE model.
Table of Contents

Seven chapters. Forty-six pages.

Chapter IThe Engine metric taxonomy, decodedpg. 5
Chapter IIOrder, Document, and Revenue metricspg. 11
Chapter IIIGB, CPU, and infrastructure-tier metricspg. 18
Chapter IVConnection and integration metricspg. 25
Chapter VMeasurement-window arithmetic, annotatedpg. 30
Chapter VIInclusion-exclusion boundaries per metricpg. 36
Chapter VIIS/4HANA migration impact on every metricpg. 42
Who It's For

Four audiences. One engine-metric reference.

SAM Leaders

The SAM leader managing engine-metric compliance across the SAP estate. The chapter-by-chapter decoding is the working reference for every engine-metric position.

SAP Basis Teams

The Basis engineer running the measurement queries and reconciling them against the USMM output. The measurement-window arithmetic is the operating manual.

Audit Counsel

Counsel managing the audit response on engine-metric findings. The inclusion-exclusion boundary annotation is the source of the defensible position.

Migration Architects

The architect leading the S/4HANA conversion. The chapter VII impact analysis informs both the contract conversion and the post-migration measurement.

The auditor counted every document in the table. We documented the contractual exclusion of intercompany and reversal documents, ran the corrected query, and removed eleven million documents from the licensable count. The opening claim collapsed.

Head of SAP ComplianceGlobal Industrial Manufacturer · Closed Q1 2026
— 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.