What Are Engine-Based and Package Licences?
SAP's licensing model has two primary dimensions. The first — and most familiar — is named user licensing: each person who accesses SAP is licensed as a specific user type (Professional, Limited Professional, Employee, etc.). The second dimension is engine or package licensing: certain SAP capabilities are not measured by user count but by the technical scale of deployment — processing power, memory allocation, transaction volume, or installed capacity.
Engine-based licences exist because some SAP capabilities operate without direct human interaction — batch processing engines, optimisation algorithms, analytics compute, and automated integration functions. For these capabilities, a per-user metric doesn't reflect the economic value or scale of use. SAP instead defines technical metrics that scale with the computational workload.
Package licences are a related concept: pre-bundled combinations of named user and engine entitlements sold as a unit, often targeted at specific industries or deployment scenarios. They simplify procurement but can obscure individual component pricing and create overpayment when some components go unused.
Why this matters for compliance: Engine and package licence violations are among the costliest audit findings because they're rarely self-identified. Unlike named user counts — which appear directly in USMM — engine deployment is often measured through technical probes that enterprises don't independently track. SAP's audit team uses specialist measurement tools to assess engine usage, and their initial findings routinely exceed actual deployment by significant margins.
Key SAP Engine and Package Licence Types
SAP HANA In-Memory Database
SAP HANA is licensed based on the amount of RAM allocated to the HANA instance — not the amount actually used at peak. If you've provisioned 2TB of RAM for your HANA deployment, your licence must cover 2TB, regardless of whether workloads ever consume it. This creates systematic over-licensing when infrastructure teams provision headroom without considering licence implications.
The key challenge: virtualisation and dynamic resource allocation can change the effective memory allocation HANA operates against. When infrastructure teams resize instances for performance reasons, they may inadvertently create licence exposure. See our SAP HANA licensing guide for detailed analysis of HANA metric management.
Common Audit Risk
SAP measures HANA RAM allocation at the time of USMM measurement. If your infrastructure was temporarily scaled up before measurement — for a batch run, a year-end process, or a performance test — you may be measured at a higher licence requirement than your normal operational state. Measurement timing is a contestable parameter.
SAP NetWeaver / Application Server
SAP NetWeaver itself is not typically separately licensed in modern contracts — it is bundled with the SAP application suite licences. However, older contracts may contain specific NetWeaver engine licences measured by processor or installation unit. If you have pre-2015 contracts in your portfolio, checking whether you carry any separate NetWeaver engine entitlement is worth confirming against current deployment.
SAP Predictive Analytics and Machine Learning Engines
SAP's machine learning and predictive analytics capabilities — whether embedded in S/4HANA or delivered via SAP BTP — can be subject to processor-core-based or service-unit-based licensing depending on deployment model and contract vintage. On-premise ML engine deployment is measured differently from BTP-delivered analytics, and the contract term may not clearly distinguish between the two as deployment evolves.
As enterprises expand AI usage via SAP Joule and embedded analytics, the engine licence perimeter needs to be tracked against contract definitions. For BTP-delivered services, SAP Joule and AI licensing has its own BTP consumption implications.
SAP Advanced Planning and Optimisation (APO) / Integrated Business Planning
Legacy SAP APO deployments may carry engine-based licences measured by processor unit. The transition from APO to SAP IBP (Integrated Business Planning) — the current cloud-based planning platform — changes the metric model significantly. IBP is typically user-subscription-based, while legacy APO may be processor-based. Mixed environments create metric complexity that frequently surfaces as an audit finding.
Industry-Specific Package Licences
SAP's industry solution portfolio — IS-Retail, IS-Utilities, IS-Banking, IS-Oil, and others — includes package licences that bundle specific functional components at a negotiated package price. The package price typically assumes a certain usage profile. Deviation from that profile — particularly if usage exceeds the package threshold — can create compliance exposure at a rate significantly above package pricing.
Industry package compliance requires mapping the package's included capabilities against your actual system configuration. It's common to find activated functionality within industry packages that is not actually used — but is still counted against the package licence threshold by SAP's measurement tools.
Engine Licence Metrics at a Glance
| Engine / Product | Primary Metric | Measurement Tool | Key Risk |
|---|---|---|---|
| SAP HANA | RAM (GB allocated) | USMM + HANA Studio | Over-provisioned infrastructure; dynamic scaling |
| SAP BTP (Consumption) | Service credits / units | BTP Cockpit | Unexpected service consumption; credit burn |
| SAP IBP | Named users (subscription) | IBP Admin Console | Legacy APO-to-IBP metric transition gaps |
| Industry Packages | Package threshold units | USMM + package-specific | Unused activated functionality triggering overage |
| SAP Datasphere | Capacity units (CU) | Datasphere Cockpit | Rapid data growth exceeding contracted CU |
Where Engine Licences Create Overpayment — and How to Challenge It
Over-Provisioned Infrastructure
The most common source of engine licence overspend is infrastructure over-provisioning. When SAP BASIS or infrastructure teams size servers for peak performance, they allocate resources — particularly HANA RAM — that exceed what SAP licences cover. Since SAP measures based on allocated (provisioned) capacity rather than peak utilisation, any allocation above the licensed threshold creates a compliance gap immediately.
The fix is governance: infrastructure changes that affect SAP resource allocation should require a licence impact review before implementation. Our SAP licence compliance service includes landscape change governance as a core component.
Unused Activated Functionality in Industry Packages
Industry solution packages often include more SAP functionality than is actively used. However, in many cases, functionality that was activated during implementation — but never actually deployed for production use — registers as "in scope" for measurement purposes. Deactivating unused functionality reduces the measured package usage, but only if done correctly and with documentation before measurement.
Measurement Timing and Normalisation
Engine metrics that scale with workload — memory usage, service credits — can vary significantly over time. SAP's audit measurement captures a point-in-time state. Understanding when measurement will occur and ensuring that point-in-time state reflects normal operating conditions — not a temporary peak — is a legitimate and important part of compliance management.
If you're facing an audit that has identified engine licence exposure, challenge the measurement methodology: when was it measured, under what operational conditions, and is the measurement representative of normal operations? Our SAP audit defence team routinely challenges measurement parameters as part of audit settlement negotiation.
Legacy Engine Licences in Modernised Landscapes
As SAP landscapes modernise — migrating from on-premise to RISE, replacing legacy products with cloud equivalents — legacy engine licence entitlements may remain on the ELP without corresponding deployment. This creates potential shelfware, but more importantly, it can create ambiguity about whether legacy licences cover new deployment methods. Getting explicit contractual clarity on this during RISE or S/4HANA migration negotiations is essential.
Do You Have Engine Licence Exposure You Haven't Measured?
Most enterprises with complex SAP landscapes have never systematically mapped their engine licence entitlements against actual technical deployment. Our SAP licence optimisation team includes technical specialists who assess engine licence positions across HANA, BTP, and industry package deployments. The findings consistently identify both compliance risk and overspend opportunities.
Book a Free Consultation →Frequently Asked Questions
Does SAP have access to our infrastructure metrics for engine licence measurement?
During a formal audit, SAP's measurement team runs USMM and may deploy additional technical measurement scripts to assess specific engine metrics like HANA RAM allocation. You are not obligated to provide SAP direct access to infrastructure systems — all measurement data should be provided as curated outputs, reviewed by your team and independent advisors before submission. Never allow SAP unilateral access to run measurement tools without oversight.
How does engine licensing change with RISE with SAP?
RISE with SAP moves much of the infrastructure management to SAP, which also changes the engine licence model. For RISE customers, HANA RAM allocation is managed by SAP as part of the RISE service — but the licenced capacity is still defined in the commercial terms. If your RISE contract includes insufficient capacity for your actual workload, SAP will charge for overage. This makes RISE capacity planning a commercial, not just technical, exercise. Our RISE advisory team reviews capacity terms as part of all RISE commercial assessments.
Can engine licence entitlements be transferred between products?
Generally no — engine licence entitlements are product-specific and cannot be transferred without SAP's agreement and a formal contract amendment. However, in ELA structures and during RISE negotiations, unused engine entitlements can sometimes be credited against new capacity commitments. This requires explicit negotiation and is not an automatic right.
Want an Independent View of Your SAP Position?
Our advisors are former SAP insiders who now work exclusively for enterprise buyers. A free 30-minute discovery call will tell you whether independent advisory would materially change your commercial outcome.
Book a Free Consultation → Download Free SAP Audit Guide →Independent SAP Licensing Advisory
We are former SAP insiders working exclusively for enterprise buyers. Our advisory services cover audit defence, contract negotiation, licence optimisation, RISE advisory, and S/4HANA migration — all buyer-side, no SAP affiliation.
Book a Free Consultation →