SAP engines are the licensed software components that operate behind the named-user layer and that measure their own consumption through metrics specific to each engine. The PI/PO message broker measures messages-per-day. The HANA database measures memory and CPU utilisation. The BW analytics engine measures users, queries, and data volume. The Solution Manager engine measures monitored objects. Each engine carries a contracted quantity and a consumption-based audit flag that triggers a licence-quantity question when the measured consumption exceeds the contracted quantity. The audit flag is the most common single-engine finding in our 500+ engagements, and the underlying drift is the most actionable optimisation target available outside the named-user layer. This article sets out the quarterly review routine, the four engines that most frequently produce findings, and the corrective actions that hold consumption within the contracted band. The full engine review methodology is in our license optimisation service.
Why engine consumption drifts
Engine consumption drifts because the application-layer changes that drive consumption are typically not visible to the engine-management process. A new integration message flow added to the PI/PO broker is an application-layer decision. The consequent message-per-day increase is an engine-consumption event. The two are typically owned by different teams and rarely coordinate. The drift accumulates quietly through the year and surfaces only when the annual measurement extracts the engine metric.
The mitigation is a quarterly review that brings the application-layer change record and the engine-metric extract into the same conversation. The review identifies the consumption trajectory, projects it forward against the contracted quantity, and triggers a corrective action when the projected end-of-year position approaches the contracted ceiling. The review is light when established and saves substantial audit exposure compared to an annual-only cadence.
The four high-drift engines
Across our practice the four highest-drift engines are PI/PO, BW, HANA, and Solution Manager. The pattern is consistent across industries and estate sizes. Each engine drifts for a different reason and requires a different corrective action.
PI/PO — message volume drift
The PI/PO broker is licensed in messages-per-day quantities. The drift driver is the addition of new interface flows over the contract term, typically driven by point-to-point integrations that should have been routed through an event-driven pattern instead. The corrective is a message-flow inventory and an architectural review that consolidates duplicate flows and routes high-volume flows through more efficient patterns.
BW — user and query drift
The BW engine is licensed across multiple dimensions including users, queries, and data volume. The drift driver is the addition of analytical users with broad query rights, frequently provisioned from a security-team perspective rather than a licence perspective. The corrective is a query-user inventory and a reclassification of users to the appropriate BW band based on actual query activity. The corrective is structurally similar to the named-user reclassification work in the application layer.
HANA — database memory drift
The HANA engine is licensed in memory quantities. The drift driver is the data-volume growth of the underlying transactional and analytical data, which is more or less unavoidable in a growing business. The corrective is a data-management programme that archives historical data outside the in-memory footprint, partitions large tables to support memory tiering, and applies data compression to the high-volume tables. The corrective is technical rather than commercial and requires the basis team’s involvement.
Solution Manager — monitored-object drift
The Solution Manager engine is licensed by monitored-object count. The drift driver is the automatic registration of new objects as the estate grows. The corrective is a monitored-object inventory and a deregistration of objects that no longer require monitoring — decommissioned systems, retired interfaces, archived business processes. The corrective is procedurally light and is the highest-yield activity per hour invested across the four engines.
The four engines together account for approximately seventy per cent of the engine-consumption findings we observe at audit. A quarterly review focused on these four catches the bulk of the exposure with limited effort.
The quarterly review structure
The quarterly review has four steps. Step one is the metric extract, pulling the current consumption figure for each engine in scope. Step two is the trajectory calculation, comparing the current figure against the same quarter prior year and projecting the trajectory to the end of the measurement year. Step three is the contracted-ceiling comparison, identifying the engines for which the projected end-of-year consumption approaches the contracted ceiling. Step four is the corrective-action commissioning, opening a remediation track for the engines flagged in step three.
The review takes between three and five working days for a mid-sized estate when the metric extracts are pre-configured. The bulk of the time is in the corrective-action commissioning rather than in the extract or the calculation. Estates that have run the quarterly review for two or more cycles develop a standing set of corrective actions that can be triggered without re-design each quarter.
The data sources
The metric extracts come from engine-specific data sources. The PI/PO consumption is extracted from the message-monitoring tables in the PI/PO platform. The BW consumption is extracted from the BW administration cockpit and the underlying analytical-system tables. The HANA consumption is extracted from the HANA studio and the M_HOST_RESOURCE_UTILIZATION tables. The Solution Manager consumption is extracted from the technical-monitoring configuration in Solution Manager itself. Each extract is technically straightforward but requires the appropriate authorisation in the source system. See the engine metrics topic page for the data-source detail per engine.
The contractual levers
When the corrective action cannot bring consumption within the contracted ceiling — typically because the consumption drift is structural to the business rather than the result of mismanagement — the response is contractual rather than technical. The contractual lever is a quantity increase, ideally negotiated at the same time as the broader contract cycle to maintain the discount position. A quantity increase negotiated as a standalone event, outside the contract cycle, typically attracts a higher per-unit cost. Anticipating the quantity increase six to nine months before signature preserves the negotiating leverage. See the engine metrics pillar for the contractual negotiation patterns.
The audit documentation
The engine consumption review produces an audit-ready record by design. The quarterly extract, the trajectory calculation, the corrective-action commissioning, and the corrective-action outcome are documented per engine and per cycle. The documentation is the response to the audit team’s engine-consumption probe and converts the conversation from a defensive posture to a managed-program presentation. Estates with a documented quarterly review survive engine probes with substantially less friction than estates without. See the engine metrics pillar and the utility engine licensing audit case file for the documentation pattern in practice.
The S/4HANA implications
The S/4HANA bundle includes some engines that were separately licensed in the classical ECC estate. The HANA database is included by definition. The BW component varies by edition. The Solution Manager component is included. The PI/PO component is replaced by the Integration Suite, which is licensed differently. The engine inventory for the S/4HANA estate is therefore different from the inventory for the ECC estate, and the review routine adjusts accordingly. The transition is the natural moment to retire the engines that are bundled into the S/4HANA subscription and to establish the review routine against the engines that remain separately licensed. The S/4HANA migration compliance pillar covers the engine treatment in the transition.
The realistic recovery range
The engine consumption review typically recovers between four and nine per cent of the engine-licensed cost annually, plus the avoidance of the audit-quantity findings that the review prevents. The recovery is structurally smaller than the named-user cleanup because the engine cost base is smaller in most estates, but the audit-avoidance value is large enough that the programme economics are favourable in nearly every estate. The engine licensing decoded white paper sets out the recovery range per engine.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
Where to start
If your engine consumption has not been reviewed quarterly and your contractual ceilings have not been compared against the current trajectory, the standing routine is the most productive optimisation activity outside the named-user layer. Our license optimisation service brief covers the review cadence.