SAP HANA's licensing model is straightforward only until you look at where HANA sits inside the broader SAP estate. Runtime versus Full Use, embedded HANA in S/4HANA and BW/4HANA, GB-based pricing, and the entitlement boundaries that determine what queries you can run — each is a discrete negotiation lever. This guide walks through the actual metrics and the leverage points across 340+ SAP engagements.
SAP HANA is licensed in two distinct modes: Runtime and Full Use. Runtime licences allow HANA to function as the database underneath specific SAP applications (S/4HANA, Business Suite, BW/4HANA) but restrict access to the HANA platform itself — no custom applications, no third-party reporting tools, no native HANA modelling. Full Use licences remove those restrictions but price at materially higher GB rates. The choice is binary at acquisition; converting Runtime to Full Use mid-term is a re-licensing event, not a metric flip.
Runtime HANA is sold as part of an SAP application licence — most commonly S/4HANA, BW/4HANA, or SAP Business Suite on HANA. The contractual position is that HANA is licensed only for queries originating from the SAP application; any non-SAP query (Tableau, Power BI, custom Python connector, third-party ETL writing or reading directly) constitutes Full Use and triggers a re-licensing requirement. SAP audits HANA query origin through system tables; the audit position has been consistent since 2017.
Full Use HANA is licensed by GB of memory-resident data, priced per 64GB block. The pricing tiers down at scale (250GB, 1TB, 5TB tiers), but the base unit is the 64GB block. The metric is measured at peak; SAP's measurement scripts capture the largest in-memory footprint over a defined period and assign licences at that peak, not at the steady state. Customers running data-loading or quarter-end peaks regularly carry licence counts 30-40% higher than steady-state utilization.
The licensing structure decisions made now compound across the next 5-7 years of SAP commercial position.
In S/4HANA Cloud Private Edition (formerly HANA Enterprise Cloud), HANA is licensed under the broader S/4HANA Cloud agreement at a per-SAPS or per-user metric, with the database GB allocation built into the bundle. In S/4HANA Cloud Public Edition (RISE with SAP), HANA is fully abstracted — the customer never sees a HANA licence line. The price difference between the two editions captures part of the embedded HANA cost, but the visibility on what is actually licensed differs substantially.
BW/4HANA includes a Runtime HANA entitlement scoped to BW workloads — schemas owned by BW, queries originating from BW, ETL workflows orchestrated by BW. Direct queries from non-BW tools into BW-owned HANA schemas are Full Use, and SAP audit teams flag this specifically through query-origin telemetry. Customers running self-service analytics on top of BW/4HANA need to confirm the entitlement model before connecting Tableau, Power BI or any other front-end tool.
SAP HANA licensing is measured at peak memory consumption, not average. The standard measurement script (LMDB / SLAW / GLAS depending on contract vintage) samples HANA memory at intervals over a defined period — typically the 90 days preceding the measurement — and reports the largest sustained in-memory footprint. Customers running ETL bursts, quarter-end consolidations, or peak operational windows accrue licence requirements at peak, even when the steady state is materially lower.
HANA compresses data at column-store level by a typical 5-7x factor; some workloads compress higher. The licensable GB is post-compression — the in-memory footprint, not the raw source-system size. SAP customers regularly overestimate their HANA sizing by working from raw ECC database sizes, leading to over-licensing. The right baseline is the actual HANA memory utilization, measured over a representative period including peaks.
HANA's multi-tenant database container (MDC) architecture allows multiple tenant DBs to share a system DB. The licensable footprint is the total memory across all tenants in the MDC, not the largest single tenant. This is a frequent over-licensing trap for customers running consolidated SAP estates — and conversely, an under-licensing risk for customers using MDC to share infrastructure across legal entities without contractual support.
Customers migrating from Business Suite on HANA to S/4HANA face a re-licensing event for HANA — the entitlement framework changes from the legacy SAP NetWeaver model to the S/4HANA-specific Runtime entitlement. SAP's standard migration commercial offers credit the existing HANA spend against the S/4HANA package, but the credit structure leaves the buyer with a higher base HANA commitment than the original licence required. The negotiable position is to anchor the credit at the GB equivalent, not the spend equivalent.
Under RISE with SAP, HANA is no longer a separately quoted line; it is bundled into the per-FUE (Full Use Equivalent) price for S/4HANA Cloud Public Edition. The opacity is intentional — SAP captures more value when the HANA cost is not separately visible — and it complicates renewal benchmarking. The defence is to maintain a parallel calculation of the implied HANA cost as a sanity check on the RISE bundle price.
The 2026 guide covering S/4HANA, RISE with SAP, indirect access and HANA licensing.
Our consultants are former SAP licensing and audit leadership. We have audited HANA contracts at every tier.
Our SAP practice is led by former SAP licensing and indirect-access leadership. We work for buyers, not SAP.
Weekly compliance intelligence for IT leaders.