SAP engine licenses and packages explained. How each metric is counted, and where the cost comes down.

SAP prices engines on business volume, and the count its measurement produces usually overstates that volume. Reconcile each engine, apply the package exclusions, fence indirect access and cap the renewal uplift before SAP's own review begins.

What is an SAP engine license?

An SAP engine is a licensed capability priced on a business metric, such as revenue, documents or assets, instead of on named users. SAP sells more than 180 engines and packages, and each one carries its own metric and its own licensed quantity.

SAP licensing splits into two groups. Named user licenses cover the right of a person, or a system acting as a user, to work in SAP. Engines and packages cover the business function underneath, and they grow with volumes that never show up in the user count.

Engine or package

An engine is one licensed capability tied to one measurement metric. A package bundles several engines under a single commercial line. SAP uses the two words loosely, and the licensing mechanics are the same for both: a metric, a licensed quantity, and a count taken at measurement time.

Why SAP prices engines outside the user count

Many SAP functions grow with transaction volume while headcount stays flat. A payroll engine scales with the number of paychecks processed, however few HR users run it. A document management engine scales with the documents it holds. Pricing these by user would undercharge a high volume operation with a small team, so SAP prices the volume.

Where the metric definition lives

Each engine's metric is defined in the SAP price list and repeated in your order document. That wording decides what counts at audit time, whatever the sales deck said. General use terms sit in the SAP software use rights document, which SAP revises over time, so keep the version your contract references.

• Metrics sit outside the user count. Revenue, order lines, documents, assets, transactions, records and gigabytes all appear.
• One metric per engine. The quantity you bought is written in the order document against that metric.
• Measurement runs engine by engine. SAP collects counts every year and again before renewal, across every engine you hold.
• Some packages exclude each other's volume. Others have no exclusion, and the same work is then counted twice.

Which metrics does SAP use to price engine licenses?

SAP uses more than 30 distinct metrics across its engines. They fall into five families (revenue, transactions, documents, assets and storage), with record counts for master data on top. You need the metric for every engine you own before you can forecast what a measurement will report.

The table shows one sample engine per family. Each family covers more engines than that.

• Revenue. Sales Performance Management and selected industry solutions count the gross revenue passing through the SAP system in scope.
• Transactions. Payment processing, banking and selected logistics modules count the discrete transactions processed.
• Documents. Invoice management, contract lifecycle management and selected procurement modules count documents stored or processed.
• Assets. Plant Maintenance asset lifecycle functions and selected industry asset solutions count the discrete assets under management.
• Storage. SAP Business Warehouse, SAP HANA and selected data archive solutions count the gigabytes under management or processed.

Measured engines and self declared engines

The measurement tools read many engine counts straight from the system. Others cannot be measured technically, and SAP asks you to declare them yourself. Revenue, employee numbers and similar company figures usually fall into this group.

Self declared metrics carry more error than measured ones, because someone types the number in. It often comes from a finance report with a wider scope than the license, such as group revenue when only two divisions run the engine. HANA also has its own memory based rules, covered in our guide to HANA runtime and full use licensing.

How do SAP package combinations change the count?

Package combinations can lower your count or raise it, depending on whether they carry an exclusion rule. Some exclude volume already counted by another package. Others carry no exclusion, so the same document or transaction is counted in both.

Combinations with an exclusion rule

A contractual exclusion prevents double counting. For example, the Payment Engine bundle excludes payment transactions already counted by the Banking Treasury package. If you hold both, read the exclusion and check that the count SAP reports has actually applied it, since the tools report each engine on its own.

Combinations that overlap

Some combinations have no exclusion at all. The Contract Lifecycle Management metric and the Document Management metric count documents separately, even when the same document sits in both systems. Without a negotiated carve out, you pay twice for one contract file.

How bundle pricing works

Bundle pricing usually lands at 60 to 80 percent of the sum of the standalone engine prices, and you negotiate the bundle discount on top. The weak point is the engine list. Some bundles include engines you will rarely or never use, and a bundle only saves money if you would have bought most of its engines anyway.

Say you only need engines A and B. Buying them standalone costs $800,000, exactly what the bundle costs at the top of the range. At that price the bundle saves nothing and adds engine C, which then attracts support fees every year.

Ask for the standalone price of each engine before you compare. Our note on bundling SAP modules for discounts covers the rest of the bundle negotiation.

What triggers an SAP engine measurement or audit?

Four events trigger an engine count: the annual system measurement, the review ahead of maintenance renewal, suspected indirect access, and an acquisition. If you run your own count before SAP runs theirs, you decide which number reaches the table first.

The annual system measurement

Each year SAP asks you to run the system measurement and submit the output. Transaction USMM measures each productive system, and the License Administration Workbench (transaction LAW) consolidates the results across systems. The output records engine counts at the snapshot date, so the volume held on that day is what SAP sees.

Our guide to USMM, LAW, SLAW and STAR explains what each tool counts and where it goes wrong.

The review before maintenance renewal

SAP runs a deployment review 12 to 18 months before the maintenance renewal. It picks up engine count drift since the last measurement, and its findings tend to arrive just as renewal pricing opens.

Suspected indirect access

Suspected third party integration volume triggers a separate audit. It runs against the named user model, the digital access model or the integration license model, depending on what your contract holds.

Mergers and acquisitions

An acquisition prompts a review of the acquired entity's engine footprint. Revenue and asset metrics are hit first, because the new business lands inside the scope of engines you already license.

Which eight metric traps inflate an SAP engine audit quote?

Eight traps drive about 80 percent of a typical engine audit quote. When we reconcile a customer's count against each of them, the opening number usually drops by 30 to 60 points. Most of the traps come from indirect access or from inflation inside a single measurement category.

Why indirect access is the most expensive trap

SAP introduced the digital access model to settle indirect access claims. A Salesforce integration that creates SAP sales orders is the textbook case. Without an indirect access fence in the contract, every order that integration creates is licensable at SAP's list rate for digital access.

Why BW compression can leave the license count unchanged

SAP Business Warehouse storage metrics can count compressed data at its uncompressed equivalent. Where your metric is written that way, compression saves hardware and does nothing for the license, and the gap between physical and licensed gigabytes works as a multiplier. Read the definition in your order document before you plan a cleanup.

What have we seen in recent SAP engine and package reviews?

Across roughly 30 to 40 SAP measurement reviews we ran in 2024 and 2025, engine and package licenses drove more true up exposure than named users did. Three patterns came up repeatedly.

• Wrong base. In 7 of 10 customers, engine metrics had been measured against the wrong base, overstating consumption by 15 to 35 percent.
• Double counting. In roughly half of the reviews, package combinations counted the same workload in two engines.
• No digital access baseline. Document counts had never been baselined, so the indirect access figure SAP proposed ran 2 to 4 times what the evidence supported.

Across 45 SAP engine audit defense and renewal engagements, the median saving against SAP's opening quote was 41 percent. The lowest was 12 percent, on a deployment where indirect access exposure had never been documented. The highest was 68 percent, where the customer ran a documented S/4HANA migration onto a fresh license model.

Why we advise against licensing the raw measurement output

A common piece of advice is to license whatever SAP's measurement reports, since the system count is authoritative and arguing with it is futile. We disagree. In most of our reviews, the raw output overstated real entitlement because it counted technical artifacts, such as test documents, integration replays and duplicate records, as licensable use.

Start from business volume instead. SAP's product catalog shows what each engine is sold to do, and the agreements published through the SAP Trust Center set the use terms. Baseline each engine against real business volume under those definitions, then license the number your evidence supports.

SAP's measurement is where the conversation opens. Engine costs come down for the customer who has already counted real business volume.

How do you reduce SAP engine license costs before renewal?

Five pieces of work cut engine costs, and all of them fit inside the maintenance renewal cycle or the RISE with SAP migration window. Each one targets a metric reconciliation, an exclusion rule or the indirect access exposure.

Reconcile each engine against the actual deployment

Compare SAP's measurement output with what is actually deployed and used. This catches revenue metric inflation, document count drift and asset duplication, and it produces the evidence you need when SAP questions the lower number.

Read the package exclusion rules

Go through the price list exclusion rules for every package combination you hold. For customers running several SAP packages, applying them typically cuts the count by 5 to 15 percent.

Fence indirect access, clean the gigabytes and cap the uplift

• Indirect access fence. Document every integration that reads or writes SAP data. Then license it under digital access at a negotiated rate, or carve it out of scope in writing. Our indirect access guide covers the contract language.
• Gigabyte cleanup. Take archive data, test data and the compressed equivalent inflation out of the BW and HANA counts.
• Renewal cap clause. Hold the maintenance renewal uplift to 0 to 3 percent across the first two renewals. The clause sits in the SAP master agreement.

Worked example: what a reconciled count does to the shortfall

Say a company holds four engines, and SAP's measurement shows a shortfall on every one. The reconciliation below trims each count by roughly a sixth to a third. The effect on the shortfall is far larger, because a true up is charged only on volume above your entitlement.

Two of the four shortfalls disappear. The Payment Engine shortfall falls by 90 percent and the Master Data Governance shortfall by 70 percent. Modest count corrections removed most of each shortfall, which is why we reconcile before we discuss discount.

What will the SAP account team say, and how should you answer?

Expect the same handful of lines in most engine discussions. Each has a reply that keeps the conversation on the contract definitions.

• "The measurement is system generated, so the count is final." The tool reports what the system holds. Your order document defines what is licensable, so ask SAP to put the metric definition next to each disputed count.
• "Every integration is indirect access, so all those documents need digital access." Ask for the count by document type and by source system. Documents your licensed users create, and data that is only read, do not belong in that count.
• "The bundle is cheaper than buying the engines separately." Ask for the standalone list price of every engine in the bundle, then price only the ones you will run.
• "The extra discount only applies if you commit to S/4HANA now." Bundling engines with an S/4HANA migration can add 10 to 20 points to the discount band. Take it on the reconciled count and compare it with our benchmarking data before you accept.
• "The uplift is standard and every customer pays it." Ask for the renewal cap in writing, and treat the uplift as a price term that is still open.

Which contract terms should you ask for on SAP engines?

Ask for terms that fix how each engine is counted before the next measurement runs. These six requests cover most of the exposure we see.

1. A metric definition per engine. Attach each engine's counting basis to the order form, including what is excluded, such as superseded versions and test clients.
2. Written package exclusions. List every exclusion rule that applies to your combinations, so the next measurement applies them without a dispute.
3. A digital access addendum at signature. Name the integrations covered and fix the rate. Signing it now avoids a per integration audit later.
4. A renewal cap. Hold the uplift to a fixed ceiling for the first two renewals, written into the master agreement.
5. Engine swap or reduction rights. Ask for the right to drop or swap unused engines inside a bundle at renewal, so shelfware stops attracting support fees.
6. An agreed measurement baseline. Record the reconciled counts as the starting point, so future true ups are measured from figures both sides accepted.

Questions to ask SAP before you sign

• Which metric definition applies to each engine in this order, and which price list version does it come from?
• Which exclusion rules apply to the packages we hold together?
• Which engines in this bundle carry support fees if we never deploy them?
• Which integrations does your indirect access estimate include, and on what document counts?

When should SAP engine work start before a renewal?

Start about 18 months before the maintenance renewal, because SAP's own deployment review begins 12 to 18 months out. Work that starts after that review has to argue against numbers SAP has already put on the table.

Our Renewal Program runs this sequence over the 12 months before signature. If you want to test your SAP quote against other buyers' pricing first, the Benchmark Program is built for that comparison.

What to do next

1. Pull the paper. Get the SAP price list and your customer order documents, and read every engine metric definition.
2. Measure first. Run your own measurement before the SAP system measurement.
3. Apply the exclusions. Check the package exclusion rules across every combination you hold.
4. Clean the master data. Remove superseded, duplicate and inactive records from the count.
5. Document every integration. This is the evidence behind your indirect access fence.
6. Clean BW and HANA. Take archive and test data out of the gigabyte counts.
7. Cap the escalator. Put the renewal cap into the master agreement before you sign.
8. Get an independent review at each gate. Our Vendor Shield subscription checks your engine counts each quarter, and a Software Spend Assessment shows where SAP sits among your other vendors.

Frequently asked questions