Most engine over licensing came from counting test, archive, and interface generated objects as billable units
Engines do not price on users. They price on work orders, documents, assets, and transactions, and the definition of each unit lives in a price list rather than in the system that generates them. Those two counts are almost never the same number.
Prepared by Redress Compliance · August 16, 2026 · SAP advisory.
Executive summary
Engines meter on objects, not on named users. Work orders, documents, assets, and transactions carry the price, which makes the seat conversation irrelevant to this part of the bill.
The price list definition rarely matches the business definition. The same object is counted differently by the contract and by the operation that produces it, and the gap is where over licensing lives.
Test, archive, and interface generated objects are the main source of over count. They are indistinguishable from real ones in a raw measurement, and nobody excludes them unless someone asks.
You can baseline yourself before SAP does. Engine measurement runs through the SAP measurement program and USMM, and running it first turns a disputed number into a prepared one.
How engine metering actually works
EAM and industry engines price on metered units rather than on named users, which means the entire seat discipline that governs the rest of an SAP estate does nothing here.
| What is metered | Where the count comes from | Where the over count hides |
|---|---|---|
| Work orders | Maintenance and operations transactions | Test orders and training environments |
| Documents | Created records of a defined type | Interface generated records nobody reads |
| Assets | Registered equipment or objects | Archived and decommissioned assets still on file |
| Transactions | Posted business events | Reversals, duplicates, and system generated postings |
The definition in the price list rarely matches how your business counts the same object. An operation that talks about work orders in one sense and a contract that defines them in another will produce two different numbers from the same system, and only one of them is the billable figure. Establishing which definition applies, in writing, before a measurement runs, is the single highest value action available on an engine licence, and it is available to any buyer who asks.
The measurement is accurate and the number is still wrong
Engine over licensing is rarely caused by inaccurate measurement. The measurement program counts what it is told to count, correctly. The problem is that what it is told to count is defined in a price list, and the objects flowing through a production SAP system were created for operational reasons that have nothing to do with that definition. Test orders raised to validate a process, archive records retained for compliance, and interface generated documents created by an integration are all objects. In a raw count they are indistinguishable from the ones that represent real business activity.
That distinction has to be argued rather than discovered, which is why it usually is not. A measurement result arrives as a number, the number is large, and the conversation becomes about the commercial response to it. By that point the definitional question, which of these objects is a billable unit under the agreement, has been skipped entirely and the burden has quietly shifted from the vendor demonstrating what is billable to the buyer explaining why something should not be. Those are very different positions, and the difference is decided by who counts first.
Running the measurement yourself is therefore not a defensive move but a definitional one. Engine measurement runs through the SAP measurement program and USMM, both of which are available to you, and baselining before SAP asks converts the exercise from a disputed number into a prepared position. It also surfaces the exclusions while there is still time to implement them, since removing test objects from a billable count is an operational change as much as a contractual argument, and operational changes take longer than negotiations do.
One layer sits above all of this and needs separating rather than absorbing. Indirect and digital access can add document charges on top of the engine meter, so the same business event can be counted once by the engine and again by digital access. Establishing which mechanism prices which event, before either is measured, prevents the double count that neither party notices until both invoices exist. The digital access mechanics sit in the digital access guide, and the wider library in the SAP practice.
- Your agreements decoded into plain English before the auditor interprets them for you
- Engine meters mapped against real object volumes, with exclusions identified
- A defensible position paper generated in minutes, not weeks
What to exclude, and how to evidence it
- Test and training objects, which exist to validate a process rather than to record a business event, and which are usually separable by client or by environment.
- Archive and decommissioned records, retained for compliance reasons and no longer representing active work, but still present in a raw count.
- Interface generated documents, created by an integration rather than by a user, and often produced in volumes nobody has ever looked at.
- Reversals and duplicates, where a single business event produced more than one posted object through ordinary correction.
- Agree the definition in writing before measuring, since a definitional argument made after a number exists is a different and weaker argument.
- Separate digital access from the engine meter, so a single business event is not counted by both mechanisms without anyone noticing.
Where the over count actually comes from
The pattern across engine licensing reviews is consistent, and it is definitional rather than technical:
Test, archive, and interface generated objects counted as billable units, indistinguishable from real ones in a raw measurement.
The price list definition and the business definition of a work order, document, or asset, producing different numbers from one system.
Engine measurement runs through the SAP measurement program and USMM, which you can baseline yourself first. Doing so converts a disputed number into a prepared position and surfaces the exclusions while there is still time to implement them operationally.
Indirect and digital access can layer document charges on top of the engine meter, so establish which mechanism prices which business event before either is measured.
Watch the briefing · 3:455 Tips That Work in SAP NegotiationsWhat moves an SAP number once the measurement position is prepared rather than received.
Your first five moves
- Read the meter definition in the price list and write down how your operation counts the same object, then compare the two.
- Run USMM and the measurement program yourself before SAP asks, so the first number in the conversation is one you produced.
- Identify and separate test, archive, and interface generated objects, by client or environment where the system allows it.
- Agree the billable definition in writing before any measurement is submitted, because the argument is weaker once a number exists.
- Map digital access against the engine meter so no business event is priced twice. The SAP practice runs the baseline with you.
Frequently asked questions
How are SAP EAM and industry engines licensed?
On metered units such as work orders, documents, assets, or transactions rather than on named users. That means the seat discipline governing the rest of an SAP estate does nothing for this part of the bill.
Why does the meter produce the wrong number?
Not through inaccurate measurement. The program counts what it is told to count, correctly. The issue is that the definition lives in a price list while the objects were created for operational reasons that have nothing to do with that definition.
Which objects cause most over licensing?
Test, archive, and interface generated objects. In a raw count they are indistinguishable from records representing real business activity, and nobody excludes them unless somebody asks the definitional question first.
Can we run the measurement ourselves?
Yes. Engine measurement runs through the SAP measurement program and USMM, both available to you. Baselining before SAP asks converts a disputed number into a prepared position and surfaces exclusions while there is still time to act on them.
Why does counting first matter so much?
Because it decides who carries the burden. If the vendor number arrives first, the buyer is explaining why something should not be billable. If your number arrives first, the definitional question is on the table before the commercial one.
What should be excluded from a billable count?
Test and training objects, archive and decommissioned records, interface generated documents, and reversals or duplicates from ordinary correction. Each is separable, usually by client or environment, but only if identified before measurement.
Does digital access interact with the engine meter?
Yes, and it can double count. Indirect and digital access may add document charges on top of the engine meter, so the same business event can be priced by both mechanisms unless you establish which prices what before either is measured.
When should the definition be agreed?
Before measuring. A definitional argument made after a number exists is a weaker argument, because the conversation has already become commercial and the number has become the anchor.
Is excluding test objects a contractual or operational fix?
Both, and the operational half takes longer. Separating test objects by client or environment is a system change, which is why identifying the exclusions early matters more than arguing them well later.
Does the seat count affect engine licensing at all?
No. Engines price on objects, documents, and transactions. An estate can have perfect named user discipline and still be significantly over licensed on engines, because the two mechanisms measure entirely different things.
The Meters: BTP Credits and AI Units
Session 8 of the SAP RISE Migration Series. Committed BTP balances ran 30 to 45 percent above consumption and the true up reset the baseline upward in seven of ten renewals. AI Units meter per action at $0.08 to $0.18 overage, and the platform credit pool triples on documented use cases.
