01. What Are SAP Package and Engine Licences?

SAP Package and Engine licences are metric-based licensing models that charge organisations based on measurable business activity. Unlike named-user or concurrent-user models, engine licences scale with your operational consumption—making cost predictability challenging but efficiency gains substantial.

Engine licensing applies across multiple SAP modules, each measuring different business drivers. Understanding which engines apply to your SAP estate is the foundation of cost management and compliance.

Common SAP Engine Types and Metrics

The following table outlines the primary engine types SAP uses, their associated metrics, and typical cost implications:

Each engine type is independent, meaning your organisation may be licensed on multiple engines simultaneously. For example, a manufacturing enterprise might be licensed on SAP HCM, SAP SD, and SAP HANA engines at the same time, with costs scaling against three separate metrics.

02. The Cost Pitfalls of Engine Licences

Engine licensing creates unique financial risks. Unlike predictable named-user costs, metric-based engines expose organisations to automatic cost escalation. Understanding these pitfalls is essential to preventing budget overruns.

Growth = Higher Costs Automatically

Business growth directly increases engine licence costs. An increase in headcount, sales volume, or transaction throughput automatically triggers licence cost increases. Many organisations discover that rapid growth has inadvertently exceeded their licensed capacity, resulting in true-up invoices or retrospective billing.

Difficult to Track Consumption

Most organisations lack real-time visibility into engine consumption metrics. SAP licence consumption is not always transparently reported in standard system dashboards, requiring custom monitoring, integration with SAP tools, or third-party solutions to surface consumption trends.

Shelfware Engines (Over-Purchasing)

Organisations often license engines defensively, purchasing more capacity than immediately needed to avoid future true-ups. This defensive purchasing results in "shelfware"—licensed but unused capacity that represents sunk cost and budget waste.

Binary Compliance Model

SAP engine licences operate on a binary compliance model: you are either compliant or in breach. There is no partial credit or elastic bursting. Exceeding your licensed metrics by even 1% places your organisation into audit risk and potential breach territory, with financial and reputational consequences.

03. Best Practices for Engine Licence Management

Effective engine licence management requires systematic monitoring, clear accountability, and integration with business operations. The following four practices form the foundation of robust licence management:

Practice 1: Inventory Every Engine

Create a comprehensive inventory of all licensed engines in your SAP estate. Document:

• Engine type and associated metric
• Licensed capacity (quantity or threshold)
• Current consumption (baseline measurement)
• Growth rate (trend analysis over 12+ months)
• Contract expiration and renewal dates

This inventory becomes the baseline for all subsequent management activities.

Practice 2: Set Monitoring and Alerts

Implement automated monitoring with alert thresholds. Recommended approach:

• Monitor consumption monthly or quarterly
• Set alerts at 70% of licensed capacity to trigger early investigation
• Set critical alerts at 90% to enable urgent escalation
• Document consumption trends in a shared dashboard accessible to stakeholders

Early warning systems prevent surprise true-ups and enable proactive negotiation before breach occurs.

Practice 3: Include Licence Checks in Change Processes

Make licence impact assessment part of any change request or system modification that could affect engine metrics. For example:

• Major organisational restructuring (affects HCM engines)
• New product line or revenue channel launch (affects SD engines)
• System consolidations or data migrations (affects HANA engines)
• Integration of acquired companies (affects all metrics)

This integration prevents surprise metric increases after changes are implemented.

Practice 4: Build a Licence Dashboard

Create a single source of truth for all stakeholders. An effective dashboard displays:

• Current licensed capacity vs. actual consumption for each engine
• Historical trends (12-month view)
• Projected consumption based on growth rates
• Days until projected breach (forecast accuracy depends on data quality)
• Responsible owner contact and escalation path

Dashboards improve transparency and enable proactive conversation with stakeholders.

04. Optimising Costs in Engine Licence Agreements

Effective cost optimisation requires negotiation strategy that acknowledges SAP's commercial incentives while protecting your organisation's financial interests. The following strategies are most effective:

Negotiate Scalable and Tiered Terms

Rather than a fixed-cost per unit, negotiate tiered pricing that rewards growth within contractual bounds. For example:

• Employees 0–500: $X per employee per year
• Employees 501–1,000: $X–0.05 per employee per year (volume discount)
• Employees 1,000+: $X–0.10 per employee per year

Tiered terms reduce escalation costs as you grow and incentivise continued SAP investment within your organisation.

Bundle Engines With User Licence Purchases

When negotiating user licence renewals or expansions, bundle engine licence improvements into the overall negotiation. SAP is more willing to offer favourable engine terms when they secure broader commitments.

Eliminate Shelfware and Leverage Conversions

Audit your current licensed capacity against actual consumption. Identify "shelfware" and negotiate conversion of excess capacity:

• Reduce licensed capacity to match actual consumption (reduces cost immediately)
• Convert excess capacity into options or extensions (protect future growth without current cost)
• Negotiate credits against future true-ups (build goodwill and reduce cash impact)

05. Audit Compliance for Engine Licences

SAP conducts regular audits to verify licence compliance. Understanding SAP's audit methodology and preparing defensible positions is essential to reducing audit risk and financial exposure.

How SAP Audits Engines

SAP audits typically follow this process:

• Scope Definition: SAP identifies systems in scope based on SAP instance registrations and contract documentation.
• Consumption Extraction: SAP collects consumption data directly from your systems via audit tools or manual extraction.
• Metric Measurement: SAP applies its metric definitions to your extracted data, calculating total consumption.
• Comparison to Licences: SAP compares measured consumption against your licensed capacity.
• Findings and Billing: Any identified overage results in true-up invoices or financial settlement discussions.

Audit Defence Best Practices

Prepare defensible audit positions through the following actions:

• Maintain audit-quality records: Document all licence purchases, amendments, and consumption measurements with clear provenance.
• Validate metric definitions: Ensure your contract clearly defines how each metric is calculated. Ambiguous definitions create dispute opportunity.
• Challenge SAP's data extraction: Review SAP's consumption data extraction methodology. Verify that test systems, development instances, or sandbox environments are correctly excluded.
• Negotiate measurement windows: If consumption is seasonal or peaks at specific times, negotiate using average consumption rather than peak consumption.
• Engage expert support: Consider third-party audit support to validate SAP's calculations and negotiate settlements from an informed position.

06. Complex Metric Definitions: Where Disputes Arise

Engine licence disputes most commonly centre on how specific metrics are defined and measured. The following table outlines five high-risk metric questions where SAP and customers often disagree:

To reduce dispute risk, negotiate contract language that explicitly addresses each of these questions and aligns measurement methodology with your interpretation.

07. Professional Recommendations

Based on years of advisory work with SAP customers, the Redress Compliance team recommends these six key actions for all organisations with metric-based engine licences:

1. Tie Metrics to Business KPIs

Connect engine metrics directly to business KPIs that executives monitor. For example, if your organisation tracks "monthly active customers" as a KPI, align your customer-based engine metric to the same definition. This alignment ensures business leaders understand licence implications of growth and can make informed trade-off decisions.

2. Engage Module Owners

Ensure the business owners of each SAP module (e.g., finance team for FI module, sales team for SD module) understand their associated engine licence and consumption metric. Module owners should receive monthly or quarterly consumption reports and participate in cost management planning.

3. Plan for Peaks

If your organisation experiences predictable consumption peaks (e.g., seasonal businesses, project-based work), plan licence capacity to accommodate peaks without requiring mid-year true-ups. Alternatively, negotiate measurement windows that smooth peak impact (e.g., 12-month rolling average rather than calendar month).

4. Negotiate Price Certainty

In multi-year contracts, negotiate fixed pricing or capped escalation rates. This protects your organisation from runaway costs if metrics grow faster than expected. Price certainty makes budgeting more reliable and reduces audit settlement risk.

5. Review Semi-Annually

Conduct formal engine licence reviews every six months. Review consumption data, compare against projections, validate dashboards, and escalate any concerning trends. Semi-annual reviews enable proactive renegotiation before breach occurs and demonstrate good-faith compliance management if audits arise.

6. Address Indirect Impact from Integrations

Monitor how new system integrations (e.g., third-party cloud applications, data warehouses, external API integrations) might increase engine consumption indirectly. For example, integrating a new CRM might increase customer data volume and trigger Digital Access engine consumption. Plan for these indirect impacts in integration business cases.

08. Frequently Asked Questions