Contents
SAP “engine” or package licences refer to modular software components (SAP HANA, SAP Payroll, SAP Warehouse Management, etc.) that are licensed based on specific metrics — users, employees, transactions, hardware size, and more. This article guides CIOs, ITAM, and SAP admins on maintaining SAP licence compliance with these metric-based licences. We explain engine licences, illustrate common metrics and pitfalls, and provide best practices for tracking usage, optimising licence deployment, and avoiding audit surprises. Effective management of these specialised licences ensures you get the most value from SAP while avoiding compliance issues.
Related: SAP Licence Compliance: Best Practices for Cloud and Hybrid Environments
1. What Are SAP Engine/Package Licences?
Beyond standard user licences, SAP software includes many add-on products or modules, often called engines or packages. Unlike named user licences (which are per individual), engines are licensed by a measurable unit — essentially a usage metric.
Examples include:
SAP HANA Database — licensed by memory size (e.g., 256 GB of HANA memory). SAP Payroll — licensed for a number of employees to be processed. SAP Warehouse Management — licensed by the number of warehouses managed or the throughput of transactions. Industry Solutions (e.g., IS-Retail, IS-Utilities) — may be licensed by revenue, number of customers, or other business metrics. SAP Procurement (SRM) — might be based on the number of documents or spend value.
These licences are typically one-time purchases with an allowance (the metric amount) and then monitored for usage. Compliance means your actual usage of that metric stays at or below what you’ve licensed. If you use more (e.g., you have 1,200 employees on SAP Payroll but are only licensed for 1,000), you are under-licensed for that engine and need to rectify it. Engines are often some of the most expensive SAP components, so maintaining compliance is critical to avoid a costly true-up.
2. Tracking and Measuring Your Usage
Measuring engine metrics can be challenging — it’s not always as straightforward as counting users. Best practices for tracking include:
Leverage SAP Tools
Some engines have specific SAP transactions or reports to measure usage. For instance, SAP provides measurement programs for certain modules during system measurement (LAW/SLAW processes). You can check the HANA studio or cockpit to see memory usage. For employee counts (for HR/Payroll engines), pulling a report of active employee records in the system or payroll runs gives the number. Identify the tool or method for each metric you have.
Assign Metric Owners
For each metric, assign a responsible owner in the organisation. For example, HR should own tracking of employee counts for HR-related licences, the IT infrastructure team for database size metrics, finance for revenue-related metrics, etc. These owners should know the licensing limits and report current usage periodically. This decentralises monitoring to subject matter experts who understand the data.
Regular Internal Checks
Include engine metrics in quarterly or biannual internal licence audits. Don’t skip them because SAP’s user measurement tools sometimes focus on user licences. Manually collect the data if needed. For example, ask HR for a count of active employees versus your licence cap every quarter, or run a transaction count if you have something like “number of orders” licensed. Keeping a simple spreadsheet of “licensed metric vs actual usage” updated quarterly for all engines gives great visibility.
Plan for Growth
If your business metric is growing (often a good thing for the business), anticipate the licensing impact. For instance, if you project adding 200 employees next year and you’re near your Payroll user limit, you either need to budget for more licences or discuss alternatives with SAP ahead of time. Growth can trigger non-compliance if not planned for.
3. Common Metrics and Potential Pitfalls
Different engines have different quirks. Here are the most common metrics and how to avoid pitfalls with each:
These apply to modules like SAP HR/PY (Payroll) and SAP SuccessFactors Employee Central. Pitfall: Companies may forget to include contractors or part-time workers if the metric counts them, or they may not realise that every unique employee with a record counts, even if inactive in the system (depending on the contract). Best Practice: Clarify whether the metric is “maximum active employees processed per year” or “current employees,” and always keep HR data tidy. Conduct periodic true-downs by archiving old records if your contract permits.
HANA licences often cap the database’s memory across instances. Pitfall: Systems tend to grow — new modules, more data, etc., can cause memory usage to exceed what’s licensed. HANA will technically still run, but you’ll be out of compliance. Best Practice: Monitor HANA memory usage closely. If you’re at 90% of licensed capacity (e.g., 230GB used out of 256GB licensed), that’s a red flag. SAP also offers HANA runtime vs full use licences — ensure you’re compliant with the type (runtime is cheaper but only for SAP apps usage, not custom dev).
Transactional/Throughput Metrics
Some engines count the number of documents (orders, invoices) or throughput (e.g., SAP PI might count the number of messages per CPU). Pitfall: Usage spikes can occur (end-of-quarter transactions surging, for example), pushing you over the licensed amount unexpectedly. Best Practice: Set internal alerts or thresholds. If a metric like “documents per year” is licensed and you have an exceptional business event (like a promotional spike in orders), keep track monthly so as not to exceed annual limits. If you see a risk of exceeding, negotiate a one-time extension or purchase additional volume from SAP proactively rather than after the fact.
Revenue or Financial Metrics
Some industry solutions are licensed based on company revenue or specific sales volume. Pitfall: You may owe more if your company grows revenue beyond the licensed band. These are tricky because they’re somewhat external to the system. Best Practice: Know the revenue bands in your contract. For example, you licensed SAP for Utilities assuming $500M annual revenue; if your revenue exceeds $600M, check if that breaches a tier requiring a licence uplift. Work with finance to be aware of growth relative to those bands.
Need Expert SAP Licensing Guidance?
Redress Compliance provides independent SAP licensing advisory services — fixed-fee, no vendor affiliations. Our specialists have helped enterprises save millions through strategic licence optimization, Digital Access negotiation, and contract restructuring.
Explore SAP Advisory Services →4. Optimising and Staying Compliant
Staying compliant with engine licences isn’t just defensive — you can optimise to potentially save money or delay purchases:
Licence Recycling (Engines)
Similar to user licence recycling, see if any metric usage can be reduced. For instance, can you retire some processes if you have an engine for a module you’re not fully utilising? Or if a part of your business that drove a metric is divested, ensure you adjust the licence (you might reduce maintenance or negotiate a lower metric band in a renewal if your usage legitimately drops).
Data Management
Good data hygiene helps with metrics like database size or the number of data objects. Archiving old transactions, purging obsolete records, and housekeeping can keep usage within limits. For example, if an engine counts active products in a catalogue and you discontinue some products, remove them from the system if they count towards your licence.
Negotiation of Buffers
In some cases, you can negotiate a cushion. SAP might allow 10% overuse on an engine metric without immediate breach to be trued up at renewal. Or they might structure a licence as tiered (you pay more when you cross a tier). Try to include such flexibility in contracts. E.g., licence 1,000 employees but allow a temporary spike to 1,100 with notice.
Third-Party Alternatives
In some situations, extremely expensive engines might have third-party alternatives or might be candidates for moving to a different platform. For instance, if a particular engine’s metric is hard to control and costs millions, consider whether a non-SAP solution could replace that functionality more cheaply (considering integration costs). This is a strategic decision, but part of optimisation — sometimes negotiating with SAP is easier if they know you have alternatives.
5. Preparing for Audits Involving Engines
When SAP audits you, they will ask for the usage of your engines and packages. Be ready by:
Documenting Metric Definitions
Have a clear document for each engine metric in plain language — “We are licensed for X (metric) and currently using Y.” Also note how you measured Y. If SAP’s audit scripts measure differently, you want to reconcile quickly. For example, SAP might run its measurement for an engine; compare it to your internal count to ensure alignment.
Avoiding Last-Minute Scrambles
If you know an audit is coming (or annually, regardless), do a special check on all engines. If any metric is over the limit, address it immediately — either reduce usage (if possible, like disable some users or clean data) or reach out to SAP to procure additional capacity. It’s far better to buy additional licences voluntarily than to be caught. SAP might be more amenable to giving a reasonable price if you come forward versus during an audit when you have little leverage.
Using the LAW Report Wisely
The Licence Administration Workbench (LAW) combines systems for user counting, but for engines, sometimes LAW will include some data or at least list engines in scope. Make sure all your engines in use are known to SAP. Proactively declare them in the audit submission with current usage stats. Full transparency can actually help negotiations, because you demonstrate control and honesty, possibly avoiding punitive penalties.
6. Recommendations
Maintain a Metrics Inventory: List all your SAP engine/package licences along with their metrics and current usage. Update this inventory regularly.
Assign Ownership: Designate specific owners in business or IT for each metric who will track usage.
Quarterly Metric Audits: Don’t wait for SAP’s audit — check your engine usage at least quarterly using system reports or manual methods.
Set Alert Thresholds: Define each metric’s internal thresholds (e.g., 85% of licensed capacity). If usage exceeds that, trigger an internal alert or review.
Clarify Contract Terms: Ensure you understand exactly how each engine’s usage is defined in your contract. If anything is unclear, get clarification from SAP in writing.
Optimise Before Buying More: If you’re nearing a limit, see if there are optimisation steps to slow growth. Only invest in more licences when you truly need to.
Keep Evidence of Compliance: Save reports or screenshots that show usage levels at key points. This creates an evidence trail in case of disagreements with SAP’s measurements.
Engage SAP Early if Overuse Looms: Don’t hide an overuse; engage SAP proactively. Early engagement can lead to better commercial terms than dealing with it under audit pressure.
Review Engine Use vs Need: Periodically review if you still need all the engine licences you own. If some module isn’t delivering value, consider consolidating or terminating maintenance.
Stay Educated: SAP introduces new metrics and changes old ones (especially with S/4HANA). Stay updated through SAP notes, user groups, or licensing webinars.
7. FAQ
What is an SAP “engine” licence exactly?
It’s a licence for a specific SAP product or module measured by something other than a named user. Instead of buying per user, you buy a quantity of a metric. For example, SAP Extended Warehouse Management might be an engine licensed per warehouse or per transaction. If you licence five warehouses, you pay for that, and using a sixth would mean you’re out of compliance.
How do I find out which engines my company is licensed for?
Check your SAP licence contract/order forms — they will list products and metrics. Also, when you run SAP’s measurement (USMM), it asks about certain engines/modules. Additionally, your SAP Entitlement System (available through the SAP Support Portal) may show your licensed products. Having a clear list is important because engines might not be obvious just by looking in the SAP GUI.
Does SAP’s audit tool automatically measure engine usage?
Not for all. SAP’s LAW and USMM focus primarily on user counts and a few technical metrics. Some engines require manual measurement or separate scripts. For instance, LAW might prompt you to enter how many employees you have for an HR engine, rather than pulling it itself. You should not rely on SAP’s default audit program to catch everything — you might be asked to provide usage evidence.
What if my usage briefly exceeds the licensed metric and then goes down?
Technically, if you exceeded the licensed amount at any point, you were out of compliance during that time. SAP auditors might still flag that. However, if you can show it was a temporary spike and is now back within limits, SAP might not demand a full new licence. It’s best to discuss with SAP; sometimes contracts allow brief peaks. To be safe, try to licence for the peak or manage operations to avoid crossing the line.
Can I partially use an engine and pay less?
Generally, no — you pay for metric blocks. For instance, if the smallest licence for a module is up to 1,000 employees and you use 200, you still buy the 1,000-employee licence. Some metrics have tiers, so you buy the tier that covers your size. SAP doesn’t offer per-use pricing for engines in traditional licensing (cloud products are different). It’s usually chunked licensing.
What happens if I’m out of compliance on an engine during an audit?
SAP will likely require you to purchase additional licences to cover the excess usage, often immediately. They may calculate how many units you were over and present a quote, plus back maintenance (if you’ve been over for a year, they might add 22% of the licence cost for that year as maintenance). You might lose any volume discount leverage since it’s under audit conditions, meaning you could pay list price. That’s why catching it yourself and negotiating a normal purchase is better.
Are engine licences affected by moving to S/4HANA?
Yes. With S/4HANA, SAP changed some licensing. Some engines became part of the S/4 bundle (certain formerly separate components are included if you licence S/4HANA Enterprise). Others remain separate or have new metrics. If you transition to S/4, you’ll likely go through a contract conversion. At that time, carefully map your old engine licences to the new scheme. During migration, ensure you don’t inadvertently run old and new engines beyond the allowances given by SAP.
Can I temporarily licence extra engine capacity for a project?
SAP typically sells perpetual engine licences, not short-term ones. However, you could try to negotiate a temporary licence if you have a one-time project spike. This isn’t standard, but SAP might offer a short-term licence or cloud-based extension. In general, plan engine capacity as a long-term need. If a temporary spike is part of your operations (like seasonal each year), it might make sense to licence for the peak.
How do I negotiate engine licences effectively?
Bundle purchases if you can (if you need additional capacity for multiple engines, negotiate them together for better discounts). Use benchmark data (if you know typical discount rates from user groups, aim for that). Highlight future growth to get a better deal now. And always explore whether a third-party SAP licensing adviser can help you structure the negotiation more effectively.
Redress Compliance helps enterprises manage, optimise, and defend their SAP licensing positions. Whether you’re preparing for an SAP audit, approaching a renewal, or migrating to S/4HANA, our independent advisory team can help you avoid costly mistakes. Learn more about our SAP Licence Optimisation Services →