What Is SAP HANA Runtime Licensing?
SAP HANA Runtime licensing is a restricted-use entitlement. It authorises you to deploy SAP HANA solely as the underlying database engine for a specific licensed SAP application — most commonly SAP S/4HANA, SAP BW/4HANA, or another application where SAP has bundled the HANA database into the product licence.
The defining characteristic of Runtime is constraint. You acquire the right to run HANA in a precisely bounded context — as infrastructure for the named SAP application — and nothing more. Runtime does not grant rights to use HANA as a standalone database platform, to develop custom applications on HANA, or to run non-SAP workloads.
From a commercial standpoint, Runtime is significantly cheaper than Full Use. SAP bundles Runtime database rights into S/4HANA licences as part of its strategy to accelerate HANA adoption. Many organisations running S/4HANA have never bought a standalone HANA licence at all — they received Runtime rights as part of their application contract and may not even be aware of the distinction.
The practical implication: if you are running SAP S/4HANA or another HANA-native SAP application, you almost certainly have Runtime licensing. The question is whether your actual usage stays within Runtime's permitted perimeter.
What Is SAP HANA Full Use Licensing?
SAP HANA Full Use licensing grants unrestricted rights to deploy HANA as a general-purpose in-memory database and application development platform. With Full Use, organisations can:
- Develop custom ABAP or non-ABAP applications directly on the HANA platform
- Run non-SAP workloads on HANA infrastructure
- Use HANA as a sidecar analytics engine for ML, predictive analytics, and real-time reporting
- Host third-party applications on HANA databases
- Deploy HANA as a data warehousing platform independently of any SAP application
- Expose HANA data services to external applications via OData or other APIs without separate Digital Access licensing
Full Use is priced on a per-64GB-of-RAM basis for on-premise deployments, or as a capacity-based subscription in cloud environments. List price differentials between Runtime and Full Use are substantial — historically two to three times the annual licence cost on equivalent hardware configurations.
Organisations that genuinely need HANA's in-memory capabilities for custom development, advanced analytics, or multi-application environments require Full Use. The commercial challenge is that many organisations acquired Runtime as part of an application bundle and later expanded HANA usage organically — discovering the gap only when an audit arrives.
Runtime vs Full Use: The Key Differences
| Dimension | Runtime | Full Use |
|---|---|---|
| Permitted use | Database layer for a specific licensed SAP application only | Unrestricted — any application, custom development, analytics |
| Custom ABAP development | Not permitted beyond the licensed application scope | Fully permitted |
| Non-SAP workloads | Not permitted | Fully permitted |
| Third-party BI tools | Requires separate Digital Access licence in most configurations | Typically included within Full Use entitlement |
| HANA sidecar analytics | Not permitted without upgrade | Permitted |
| Relative cost (on-premise) | Bundled — low incremental cost | 2–3× Runtime equivalent pricing |
| Audit exposure | High — commonly exceeded inadvertently | Low — broad entitlement reduces risk |
Where Runtime Licences Create Compliance Risk
In our experience advising on over 500 enterprise software negotiations, SAP HANA Runtime overuse is one of the three most common audit findings in SAP licence reviews — alongside indirect access and named user type misclassification. The overuse is almost never intentional. It emerges from the natural evolution of how organisations exploit their HANA investments.
The Custom Extension Problem
SAP S/4HANA deployments routinely involve custom ABAP extensions, Fiori applications, and BTP integrations that write data to or read data from the HANA database outside the core S/4HANA application layer. Each such extension potentially triggers a Runtime compliance issue. SAP's position is that Runtime rights attach to the licensed application, not the underlying database — custom code interacting with HANA directly falls outside that scope.
The Embedded Analytics Expansion
HANA's in-memory architecture makes it compelling for embedded analytics and real-time reporting. Organisations deploying SAP Analytics Cloud, SAP Datasphere, or even simple Live Connection BI tools against a HANA instance licensed under Runtime frequently discover that their analytical usage constitutes Full Use activity. The trigger is typically the exposure of HANA data services to an application or user outside the original licensed application perimeter.
The HANA Sidecar Scenario
Some organisations deploy HANA as a "sidecar" — a secondary HANA instance running alongside their primary SAP ERP system, used for advanced analytics, machine learning models, or data replication from non-SAP sources. A sidecar deployment on Runtime licensing is a near-certain audit finding. The sidecar, by definition, operates independently of the licensed application.
The Multi-Application Consolidation
When multiple SAP applications are consolidated onto a shared HANA infrastructure, licence complexity increases significantly. If one application carries Full Use HANA rights and another carries Runtime only, the Full Use entitlement does not automatically extend to the Runtime application's workloads. SAP treats each application's HANA licence independently.
"We have audited dozens of S/4HANA environments where the client believed Runtime coverage was sufficient. In fewer than 20% of cases was their actual usage genuinely within Runtime scope. The gap is almost always the result of legitimate business decisions — analytics, integrations, extensions — made without awareness of the licence implications."
How SAP Enforces the Boundary in Audits
SAP's licence audit methodology for HANA deployments examines several technical artefacts to identify Runtime vs Full Use compliance status. Understanding what SAP's auditors look for is essential context for both compliance management and audit defence.
Tenant Database Analysis
SAP HANA supports multi-tenant database containers (MDC). In an audit, SAP's LAM (Licence Audit Management) team maps each tenant database to the applications it supports and the licence entitlement covering those applications. Tenant databases hosting non-SAP or custom workloads on Runtime licences are flagged immediately.
Schema and Repository Inspection
SAP auditors examine the HANA repository and database schema structure to identify custom development objects — tables, procedures, calculation views, and application objects — that extend beyond the licensed application's standard objects. Significant custom development on a Runtime licence is treated as Full Use activity.
Consumption Metrics and Connection Logs
For cloud-based HANA environments (particularly HANA Cloud on BTP), SAP has significantly more visibility into actual usage patterns. Connection logs, API call volumes, and compute consumption data allow SAP to identify workloads that fall outside Runtime scope with much greater precision than was historically possible in on-premise environments.
Negotiation Strategies for HANA Licences
Whether you are trying to resolve an existing Runtime compliance gap, preparing for a HANA Full Use upgrade discussion, or structuring a new S/4HANA contract that provides appropriate HANA flexibility, several principles consistently deliver better commercial outcomes.
Never Enter an Audit Without Commercial Leverage
If SAP raises a HANA Runtime compliance concern, the worst response is to immediately acknowledge the gap and ask for a remediation quote. SAP's first quote in any audit remediation scenario is structured to capture maximum value. Organisations with credible leverage — an S/4HANA migration timeline, a move-to-cloud decision, or a consolidation opportunity — consistently settle for 30–60% less than SAP's initial position.
Negotiate Full Use Upgrades at Renewal, Not Post-Audit
If you know your HANA usage has expanded beyond Runtime scope, the optimal time to address it is at contract renewal — not after receiving an audit notification. At renewal, you control the timing and have options: upgrade to Full Use, restructure application scope, or negotiate a bundled resolution as part of a broader deal. Post-audit, SAP controls the timeline and the framing.
Benchmark Full Use Pricing Aggressively
SAP HANA Full Use list pricing is rarely the starting point for serious enterprise negotiations. Discounts of 50–70% off list are achievable with proper commercial leverage — particularly when combined with S/4HANA subscription commitments, RISE with SAP discussions, or GROW with SAP transitions. Organisations that accept SAP's standard "upgrade path" pricing without benchmarking typically overpay by 40% or more.
Structure Cloud HANA Rights Carefully
In cloud environments — particularly HANA Cloud on BTP — the Runtime vs Full Use distinction manifests differently from on-premise. Consumption-based pricing means that overuse translates directly into invoice surprises rather than audit claims. When negotiating BTP committed-use agreements, ensure that HANA Cloud capacity entitlements are sized for your actual anticipated workloads, including analytics and custom applications, not just the baseline SAP application footprint.
For a comprehensive view of SAP licensing strategy, see our Complete SAP Licensing Guide. For audit-specific preparation, read our SAP Audit Defence guide. You can also download our SAP S/4HANA Migration & Licensing Guide for detailed contract frameworks.