SAP engine licences cover specific modules and technologies measured by business metrics rather than per user: employees on payroll, annual revenue, documents created, gigabytes of HANA memory, or processor cores. Engine licences are frequently the most expensive and least understood elements of the SAP estate, and they are a primary focus of SAP licence audits.
Organisations that actively track, optimise, and negotiate their engine portfolio typically achieve 20-40% reductions in engine-related costs compared to those that manage engines reactively. Engine metrics change continuously with business growth, acquisitions, and system evolution, creating compliance exposure that accumulates silently. See also: S/4HANA Licensing Guide and SAP Audit Trends 2026.
| Metric Category | Used For | What Is Counted | Key Risk |
|---|---|---|---|
| Employee-based | HCM, Payroll, Time Management, Benefits, Talent Management. | Total employee records (workers, contractors, contingent staff) managed in SAP. Not the number of HR users who operate the software. | Scales with headcount. Organic growth, acquisitions, and contractor expansion all increase the requirement automatically. |
| Revenue and spend-based | Sales, procurement, and financial processing engines. | Annual monetary throughput: total revenue processed, total procurement spend managed, or total invoice value flowing through SAP. | Revenue growth or increased procurement centralisation directly increases the engine requirement. Pricing typically tiered by volume bands. |
| Technical capacity (memory) | SAP HANA database. | Gigabytes of memory allocated to the HANA instance. Grows as data volumes increase and modules are deployed on HANA. | Enterprise HANA deployments frequently require terabytes. Each additional GB carries licence cost that compounds rapidly. See S/4HANA Hidden Costs. |
| Technical capacity (processor) | SAP BusinessObjects, infrastructure components. | Number of server cores dedicated to the component. | Hardware upgrades or virtualisation changes can alter core counts without explicit licensing decisions. |
| Document and transaction-based | Digital Access (indirect access) and integration engines. | Number of SAP documents (orders, invoices, deliveries) created within a defined period. External systems creating SAP records via APIs/EDI count toward the threshold. | High-volume integrations generate massive document counts. See Digital Access Audit Defense. |
| Engine Category | Typical Metric | Price Range (Indicative) | Cost Driver |
|---|---|---|---|
| SAP Payroll | Employees on payroll. | $50-$150 per employee. | Total headcount including contractors. |
| SAP HANA (Runtime) | GB of memory. | $500-$1,500 per GB. | Data volume and modules running on HANA. |
| SAP HANA (Full Use) | GB of memory. | $2,000-$5,000+ per GB. | Analytics, BW, and non-ERP workloads. |
| Procurement engines | Annual spend processed. | Tiered by spend volume. | Procurement centralisation and business growth. |
| Digital Access | Documents per type. | Varies by document type and volume tier. | External system integrations creating SAP documents. See Digital Access Complete Guide. |
| BusinessObjects | Processor cores. | Per-core pricing. | Server infrastructure footprint. |
Engine pricing is always negotiable. List prices are starting points. Enterprise customers routinely negotiate discounts of 40-70% on engine licence fees, and higher discounts are achievable for very large commitments or strategic deals. See SAP Pricing Benchmarks.
Engine licences and named user licences are complementary, not alternatives. An organisation running SAP Payroll needs both the Payroll engine licence (based on employee count) and named user licences for the HR staff who operate the Payroll module. The engine covers the right to use the functionality at the specified volume; the named user licences cover the individuals who access the system.
| Scenario | Engine Cost | Named User Cost | Which Dominates |
|---|---|---|---|
| SAP Payroll (30,000 employees, 15 HR staff) | Several hundred thousand dollars (30,000 x employee rate). | ~$45K-$90K (15 users x Professional rate). | Engine cost dominates significantly. Engine optimisation has the highest ROI. |
| SAP Finance (moderate transactions, 500 finance users) | Moderate (based on revenue or transaction volume). | $1.5M-$3M (500 x Professional rate). | Named user cost dominates. User classification optimisation has the highest ROI. See FUE Licensing Explained. |
| Best Practice | What to Do |
|---|---|
| Maintain a complete engine inventory | Document every engine licence held: specific metric, licensed quantity, measurement method, and current actual usage. Update quarterly. Reconcile against SAP licence agreements. |
| Run measurement reports quarterly | Execute SAP's system measurement tools (LAW, USMM) at least quarterly. Compare values against licensed quantities. Identify engines approaching thresholds before SAP's annual request or audit. See SAP Compliance Tools Guide. |
| Set threshold alerts | Establish internal alerts at 80% and 90% of licensed capacity. At 80%, begin planning for expansion or optimisation. At 90%, escalate to procurement and initiate SAP discussions. |
| Track growth trajectories | Monitor rate of change for each metric: employee count growth, revenue trajectory, data volume expansion, document creation rates. Enables proactive budgeting rather than reactive true-ups. |
| Reconcile after business changes | Following acquisitions, divestitures, reorganisations, or system integrations, immediately reassess all engine metrics. Acquisitions can instantly push multiple engines beyond thresholds. See SAP M&A Licensing. |
| Risk | What Happens | Prevention |
|---|---|---|
| Overuse (exceeding licensed metrics) | Actual engine metric exceeds licensed quantity. SAP requires purchase of the shortfall with retroactive maintenance calculated from the point the threshold was exceeded. Can accumulate over several years. | Quarterly measurement with threshold alerts. Budget for expansion before overages accrue. See SAP Audit Survival Guide. |
| Indirect access documents | External systems creating SAP documents trigger document-based engine requirements. Volume can be very large for organisations with extensive integrations. | Quantify document volumes proactively. Adopt Digital Access licensing or negotiate DAAP. See SAP DAAP Strategy Guide. |
| Unlicensed engine usage | Using SAP functionality that requires an engine licence without holding the entitlement. Occurs when modules are activated without checking licence requirements, or when upgrades introduce new functionality requiring separate licensing. | Include engine licence review in change management processes. Verify engine requirements before activating any new SAP capability. |
| Strategy | What to Do | Typical Impact |
|---|---|---|
| Identify over-licensed engines | Find engines where licensed quantity significantly exceeds actual usage. Occurs from growth projections that did not materialise, divestitures that reduced metric volumes, or conservative initial sizing. Negotiate reductions at renewal. | Significant annual maintenance savings (17-22% of recovered licence value, compounding over remaining term). |
| Right-size HANA memory | Audit actual HANA memory consumption vs. licensed allocation. Archive unnecessary data. Consolidate HANA instances where possible. | $100K-$1M+ in licence fee reduction for enterprise deployments with over-provisioned HANA. |
| Negotiate metric structures at renewal | SAP's pricing tiers, metric definitions, and volume bands are all negotiable during major contract events (S/4HANA migration, RISE evaluation, agreement renewal). | Lower per-unit rates. More favourable volume bands. Growth buffers at minimal incremental cost. |
| Bundle engine negotiations | Consolidate multiple engine purchases or renewals into a single negotiation to maximise total deal value and leverage. | 15-30% additional discount from combined deal value. See SAP Contract Negotiation Service. |
| Negotiate growth buffers | Request 10-20% headroom above current usage at minimal incremental cost rather than purchasing exact current usage and facing full-price true-up when growth occurs. | Avoids premium-priced reactive true-ups. Provides compliance headroom during growth periods. |
Under RISE with SAP, certain engine components (including HANA database capacity and cloud infrastructure) are bundled into the subscription fee. However, the bundled nature can obscure the true cost of individual engines, making it harder to optimise specific components independently. Not all on-premises engine entitlements transfer to RISE. Some may receive migration credits under SAP's transition programmes; others require new subscription commitments.
| Engine Component | RISE Treatment | Key Consideration |
|---|---|---|
| SAP HANA database | Typically included in RISE subscription bundled with infrastructure. Memory allocation may be subject to usage-based pricing above a base threshold. | Verify the memory allocation in your RISE contract. Overages above the base threshold can be expensive. See RISE with SAP Tiers. |
| Employee-based engines (Payroll, HCM) | May transition as separate subscription line items within RISE. Metrics and pricing potentially restructured. | Model the total engine cost under both on-premises and RISE to make an informed comparison. See ECC-to-2033 Transition Option. |
| Conversion credits | Some on-premises engine licences may receive migration credits under SAP's transition programmes. | Not all engines qualify for credits. Negotiate to maximise credit value for every engine being retired. See SAP Negotiation Strategies. |
An SAP engine licence (package licence) is a licensing entitlement for a specific SAP module or component measured by a business-volume metric rather than per user. Common metrics include employee count, annual revenue, gigabytes of memory, processor cores, and document count. Engine licences are purchased in addition to named user licences. Both are required.
Named user licences are based on the number of individual people who access SAP. Engine licences are based on business-volume metrics that reflect the scale of the activity the software supports. An organisation needs both types for each module it uses. See SAP ESS License Guide.
SAP uses system measurement tools (LAW, USMM) to capture current metric values. Measured values are compared against licensed quantities. Any metric exceeding the licensed quantity generates a compliance finding requiring purchase of the shortfall, typically including retroactive annual maintenance. See SAP Compliance Tools Guide.
Yes. Engine pricing, metrics, volume bands, and measurement methodologies are all negotiable. Enterprise customers routinely negotiate 40-70% discounts on engine fees, growth buffers, metric flexibility at renewal, and contractual measurement methodology agreements. See SAP Contract Negotiation Service.
Certain engine components (notably HANA) are bundled into the RISE subscription. Not all on-premises entitlements automatically transfer. Some may receive migration credits; others require new commitments. Model total engine cost under both models before committing. See S/4HANA Licensing Guide.
Primary strategies: identify over-licensed engines and negotiate reductions, right-size HANA memory, consolidate engine negotiations for maximum leverage, negotiate growth buffers, retire unused modules to eliminate unnecessary entitlements, and time negotiations with SAP's fiscal pressure points. See SAP Licence Optimisation Services.
External systems creating SAP documents trigger document-based engine licensing requirements under SAP's Digital Access model. Organisations with extensive integrations should quantify document volumes and licence Digital Access or evaluate DAAP. See Digital Access Audit Defense.
Redress Compliance provides independent SAP engine licence assessment, optimisation, audit defence, and contract negotiation. We help enterprises identify over-licensed engines, right-size HANA memory, and negotiate favourable metric structures. Fixed-fee engagements. No SAP partnerships.
SAP Licence Optimisation ServicesIndependent engine licence assessment, HANA right-sizing, metric optimisation, and contract negotiation. Fixed-fee engagements. No vendor conflicts.