SAP HANA, BW/4HANA, and SAP Analytics Cloud each carry distinct licensing models that significantly impact total cost of ownership. This playbook covers runtime vs full-use HANA licensing, BW/4HANA capacity models, SAC subscription options, common compliance pitfalls, transition strategies from legacy BI, cost optimisation tactics, and actionable CIO recommendations for cost-effective, future-proof decisions.
SAP HANA is an in-memory, columnar database that underpins SAP's analytics and ERP solutions. HANA's licensing is divided into two main categories: Runtime and Full Use. The choice between them is one of the most consequential licensing decisions CIOs face.
Restricted to use only in support of SAP applications. If HANA is deployed solely as the embedded database for SAP software (e.g. S/4HANA, BW/4HANA), a runtime licence is appropriate. Pricing typically uses the HSAV (HANA Software Application Value) metric, with SAP charging a percentage (commonly ~15%) of that value. The runtime licence is lower-cost but carries strict restrictions: you may not directly access HANA outside the SAP application's UI and APIs. Building custom applications on HANA, connecting third-party reporting tools directly to the database, or extracting data directly from HANA tables can violate the licence.
Grants unrestricted access to the database, enabling custom-built solutions, third-party software, and direct data access beyond SAP's application layer. Full-use HANA licensing is typically capacity-based, tied to the amount of memory (RAM) allocated to HANA, sold in blocks (e.g. 64 GB increments). Costs scale with database size. If the memory footprint grows, licensing costs grow accordingly. Choose full-use only if you need HANA's platform capabilities beyond SAP applications (custom data marts, multi-application database). Otherwise, runtime is far more economical.
| Factor | HANA Runtime | HANA Full-Use |
|---|---|---|
| Usage rights | SAP applications only | Any application, unrestricted |
| Pricing metric | % of HSAV (SAP application value) | Memory capacity (GB/TB blocks) |
| Relative cost | Lower, typically ~15% of app value | Higher, premium for flexibility |
| Custom development | Not permitted | Fully permitted |
| Third-party BI access | Not permitted directly | Permitted |
| Best for | Pure SAP workloads (ERP, BW) | Enterprise data hub, multi-app database |
The runtime licence dramatically lowers database costs when HANA's role is limited to SAP systems. However, the moment an organisation anticipates any non-SAP data or external applications on HANA, a full-use licence is required to stay compliant. Regardless of licence type, careful sizing is crucial. For full-use HANA, sizing directly affects cost. Regularly monitor HANA memory consumption and growth trends. Implement data tiering, archiving of cold data, and housekeeping to maintain a lean in-memory footprint.
SAP BW/4HANA is SAP's next-generation enterprise data warehouse, running exclusively on HANA. It is the successor to traditional SAP Business Warehouse (BW). Licensing involves both the BW/4HANA application licence and the underlying HANA database licence.
SAP typically licences BW/4HANA based on the size of the data warehouse, measured by HANA memory footprint, often in 64 GB blocks. The cost covers BW/4HANA software and a HANA runtime licence. This model allows unlimited users as long as data size stays within the licensed band. Ideal when BW is a core enterprise data hub with many consumers. Avoids complexity of tracking individual users. Larger tiers yield better unit pricing.
Alternatively, each BW/4HANA end-user needs a Professional Named User licence. This can be cheaper if only a small, controlled set of users accesses BW. Evaluate which model fits your usage: capacity-based for broad enterprise access, user-based for limited analyst teams.
BW/4HANA eliminates the legacy "Open Hub" licensing requirement. In SAP BW 7.x, exporting data to external systems required an additional Open Hub licence. BW/4HANA removes that constraint. Users can consume BW/4HANA data from any SAP or third-party analytics tool without extra fees. This encourages modern BI tool integration and reduces hidden integration costs.
Organisations transitioning to BW/4HANA must budget for a new licence purchase or conversion. It is not a free upgrade from SAP BW. SAP BW 7.5 mainstream maintenance ends 2027, with extended maintenance available until 2030. If BW was previously bundled with SAP Business Suite at no separate cost, you will now need to allocate budget for BW/4HANA licences, potentially a significant amount if data volumes are large.
SAC is SAP's flagship cloud analytics platform providing BI (dashboarding, reporting), planning (budgeting and forecasting), and predictive analytics as SaaS. It is available only as a cloud subscription with two primary models.
Pay a subscription fee per named SAC user (yearly or monthly). Different tiers: "SAC for Business Intelligence" covers standard analytics features. "SAC for Planning" (Planning Professional) includes planning and what-if modelling at a higher price. All SAC users are named, not concurrent by default. Contracts typically come in blocks with 1 to 5 year terms. Only give Planning licences to those who need planning features. Others should use lower-cost BI licences.
For large-scale or highly variable usage, pricing is determined by resources consumed rather than fixed user count, tied to data volume, computing resources, or system size. Any number of users can access the system within the capacity bucket. Can be transacted via SAP's Cloud Platform Enterprise Agreement (CPEA) where cloud credits are consumed based on SAC resource usage. Suitable when you have thousands of occasional dashboard viewers where per-user pricing would be inefficient. Requires careful usage monitoring to avoid overages.
| Factor | SAC User-Based | SAC Capacity-Based |
|---|---|---|
| Pricing model | Per named user (annual subscription) | Resource consumption (data/compute) |
| User limits | Fixed to purchased count | Unlimited within capacity bucket |
| Tiers | BI (lower) vs Planning Professional (higher) | Single capacity pool |
| Best for | Known, stable user base | Broad, variable, occasional access |
| Flexibility | Can add mid-term; reduce at renewal only | Scale within capacity; renegotiate at renewal |
| Risk | Over-purchasing unused licences | Overage charges if usage spikes |
Consider starting SAC with a manageable number of users and scaling as adoption increases. SAC allows adding users mid-term (at prorated cost) but reducing typically happens only at renewal. Better to slightly under-provision and expand than over-provision and waste budget. If SAC is part of RISE with SAP or other enterprise agreements, bundled discounts or credits may apply. If your company has BTP credits, these can be leveraged to consume SAC as a service.
Under full-use HANA, SAP audits check peak or average memory utilisation. Exceeding purchased capacity triggers significant back-payments or premium block purchases. Common causes: over-provisioning hardware "just in case," storing years of detailed data online, allowing data bloat. Right-size and continuously govern the HANA environment. Archive cold data to cheaper storage, delete unused data, implement HANA's native data tiering (NSE or extension nodes). Treat HANA sizing as a licensing exercise, not just a technical one.
The most dangerous pitfall: connecting third-party BI tools (Power BI, Tableau) directly to a HANA runtime system, or building custom applications on it. Such usage is not permitted under the runtime agreement. SAP audit programmes specifically target HANA runtime customers. Impact: SAP may demand a retroactive upgrade to full-use licensing plus back fees for maintenance. Educate all teams on HANA licence restrictions. If using runtime, ensure all data access is routed through the SAP application layer.
Analytics tools pulling data from SAP systems and displaying to users without proper SAP user licences creates compliance risk. SAP's Digital Access model covers some cases (counting document events rather than users). Audit and map data flows. Know who or what accesses your SAP data warehouse or ERP data. Utilise SAP's analytics front-ends (SAC) which cover SAP data access implicitly, rather than exposing data via unlicensed channels.
Moving from BusinessObjects to SAC or BW to BW/4HANA often means paying for similar functionality twice. Extended parallel runs inflate budgets and erode the business case for new systems. Always tie new deployments to a timeline for reducing old licences. Leverage SAP's licence conversion programmes to offset dual costs. The key pitfall is lack of a decommission plan. Without one, organisations end up maintaining both systems indefinitely.
Know your licence boundaries and actively manage usage against them. Diligent internal licence audits and an open dialogue with SAP can turn many of these issues into non-issues. By anticipating these pitfalls (HANA sizing overages, misuse of runtime licences, indirect usage violations, and redundant tooling), CIOs can steer clear of compliance crises and budget overruns.
Audit your BusinessObjects environment. Identify heavily used vs redundant reports. Many organisations find a significant portion is rarely used. Retire or consolidate before migration to reduce effort and SAC licence needs. Introduce SAC alongside BusinessObjects in hybrid mode. SAC can connect live to BusinessObjects universes via the "Live Universe Connector." Continue using BusinessObjects for reports SAC cannot yet replace. Encourage all new analytics requirements to be built in SAC.
Focus on fully migrating specific use cases: dashboards built in Xcelsius (Flash-based, out of support since 2020) are natural candidates for SAC. Self-service analysis currently done in WebI can be enhanced with SAC's natural language queries and ML-driven insights. Conduct pilots with power users to refine SAC stories that replace WebI report sets.
Over 1 to 3 years, incrementally migrate remaining critical reports to SAC. The goal is to significantly reduce or entirely decommission the BusinessObjects environment, saving maintenance, infrastructure, and support costs. Leverage SAP's Cloud Extension Policy to convert existing on-prem licence values into cloud subscriptions. Trade unused BusinessObjects licences and maintenance fees to offset SAC subscription costs.
Direct evolution of your data warehouse. Protects investments in BW business logic (ABAP routines, BEx queries, extractors) while modernising the platform with continued support to 2040. Requires purchasing BW/4HANA licences. SAP may offer licence conversion programmes crediting existing BW licence values. Clean up data models and archive old data during migration to potentially reduce HANA footprint and licence costs.
Retire SAP BW entirely and handle reporting through S/4HANA's embedded analytics (CDS views), SAC's modelling, and cloud data platforms for non-SAP data. Avoids BW/4HANA licensing and infrastructure costs. However, the data warehouse function shifts elsewhere: SAP Datasphere, cloud data lakes, or expanded S/4HANA data retention. Best for organisations with relatively simpler analytics needs and low-to-moderate data volumes.
Split workloads: core structured reporting (SAP financials, logistics data) goes to a lean BW/4HANA with strong governance. Experimental or rapidly changing analytics (non-SAP, big data) moves to cloud (Datasphere or other platforms) with SAC as the unifying reporting layer across both. Reduces BW/4HANA scope and cost while leveraging cloud scalability.
Take advantage of SAP's Cloud Extension Policy or licence swap offerings. Convert existing on-prem licence values into cloud subscriptions. Trade unused BusinessObjects licences or maintenance into SAC subscriptions. Swap legacy BW licences for BW/4HANA at a discount. Always ask SAP if a conversion option exists. SAP has been amenable to this as it encourages cloud adoption.
When transitioning to multiple new products (S/4HANA + BW/4HANA + SAC) as part of digital transformation, negotiate a bundled deal. Bundles like RISE with SAP sometimes include SAC or can be extended to cover BW/4HANA at attractive rates. Aligning all major purchases in a single negotiation gives you more leverage for volume discounts.
Clean up data and users before you lock in licence metrics. Archive data from HANA to shrink memory needs. Delete or consolidate unused BW objects. In BusinessObjects, eliminate inactive users and reduce concurrent user licences. The smaller and more efficient your environment, the fewer GB or users you need to licence on new systems.
Do not schedule all transitions simultaneously. This maximises overlapping licence costs. Migrate BW first one year, tackle BOBJ-to-SAC the next. Freed-up budget from the first project funds the second. During unavoidable overlap periods, keep them as short as possible with aggressive but realistic decommission timelines.
Monitor usage and adjust licence types. Not every user needs a full creator licence. Casual viewers might be served by shared static reports. Ensure each user has the correct role (BI vs Planning) to consume the right-cost licence. If utilisation is under capacity, consolidate to fewer licences at renewal. Renegotiate the model (user vs capacity) at renewal based on actual usage patterns.
Once SAC is adopted, plan to fully retire at least one legacy BI tool. Every system retired saves maintenance fees and simplifies governance. Make software asset management a continuous discipline. Use SAP's tools (Licence Administration Workbench) and third-party tools to track usage. Proactively identify under-utilisation (reduce) or approaching caps (negotiate expansion before audit penalties). Monitor indirect usage. New integrations connecting to BW should be flagged to licensing teams immediately.
Inventory all SAP analytics systems (BW, HANA, BOBJ), their versions, and current licensing status. Document non-SAP integrations. Use this baseline to identify necessary licence changes (runtime vs full HANA) and potential compliance risks.
If HANA is only used for SAP applications, stick to the cheaper runtime licence and enforce policies preventing non-SAP usage. Only invest in full-use if your strategy genuinely requires HANA as a broader data platform. Regularly monitor memory usage and clean up data to avoid unnecessary expansion.
With BW 7.x support nearing end, decide whether to migrate to BW/4HANA or shift to a cloud-based analytics stack. If BW/4HANA is required, engage SAP early on conversion terms and plan completion by 2027. If not, create a roadmap for replacing BW capabilities with SAC and other data platforms.
Develop a phased migration plan. Begin by integrating SAC with existing BI in hybrid mode. Gradually recreate high-value reports in SAC. Target a sunset date for BusinessObjects and communicate it organisation-wide. Leverage SAP's Cloud Extension Policy to convert BOBJ maintenance budget into SAC subscription value.
Select the right model (user-based vs capacity-based) based on user count and usage patterns. Start with manageable numbers and scale. Ensure expensive Planning licences are only held by those who need them. Drive user adoption through training to justify consolidating other BI tools into SAC.
Establish licence compliance governance. Track how systems are used internally. Prevent unauthorised direct access to HANA under runtime licences using technical controls. Once new platforms are in place, decommission legacy BI and BW systems on schedule. Eliminate associated licence maintenance, hardware, and support costs. Redirect savings to fund innovation on SAC and HANA.
SAP's data and analytics licensing landscape, spanning HANA runtime vs full-use, BW/4HANA capacity models, and SAC cloud subscriptions, rewards CIOs who invest in understanding their options and actively manage their positions. The combination of strategic licence model selection, phased transitions from legacy BI, continuous compliance governance, and aggressive cost optimisation through SAP's conversion programmes can deliver significant savings while modernising the analytics platform.
HANA runtime is restricted to use only in support of SAP applications and is priced as a percentage (~15%) of your SAP application value (HSAV). Full-use grants unrestricted access, enabling custom-built solutions and third-party software, and is priced by memory capacity in GB/TB blocks. Runtime is significantly cheaper but you cannot connect non-SAP tools directly to the database. Full-use is required only if you need HANA as a broader enterprise data platform.
No. BW/4HANA requires a new licence purchase or conversion from existing BW licences. SAP may offer licence conversion programmes crediting existing BW licence values, but the upgrade is not free. BW 7.5 mainstream maintenance ends 2027, with extended maintenance until 2030. If BW was previously bundled with SAP Business Suite at no separate cost, you will now need to budget separately for BW/4HANA.
User-based is better when you have a known, stable user base. Capacity-based is better for broad, variable, or occasional access scenarios (thousands of dashboard viewers). Start with user-based if your initial adoption is focused on a specific team, and consider capacity-based if you plan enterprise-wide rollout. If part of RISE with SAP or using BTP credits, bundled options may provide better economics.
Connecting third-party BI tools directly to a HANA runtime system violates the runtime agreement. SAP audit programmes specifically target HANA runtime customers for this scenario. The impact can include a retroactive upgrade to full-use licensing plus back fees for maintenance. If using runtime, ensure all data access is routed through the SAP application layer. If there is genuine business need for direct database access, proactively discuss upgrade options with SAP before an audit forces the issue.
Plan a phased transition with explicit decommission dates for legacy systems. Leverage SAP's Cloud Extension Policy to convert existing on-prem licence values (BusinessObjects maintenance) into SAC subscription credits. Stagger migrations so freed-up budget from the first retirement funds the next. The key is having a documented decommission plan with communicated dates. Without one, organisations end up maintaining both systems indefinitely.
SAP's Cloud Extension Policy allows organisations to convert existing on-prem licence values into cloud subscriptions. This means you can trade unused BusinessObjects licences and maintenance fees to offset SAC subscription costs, or swap legacy BW licences for BW/4HANA at a discount. The programme is designed to encourage cloud adoption and can significantly reduce the financial impact of transitioning from legacy to modern analytics. Always ask SAP if a conversion option exists during any licence negotiation.
Redress Compliance provides independent SAP advisory: HANA licensing strategy, BW/4HANA migration planning, SAC optimisation, licence conversion negotiations, audit defence, and compliance assessments. We help enterprises choose the right licensing models, avoid pitfalls, and reduce total cost of ownership. Complete vendor independence. No SAP partnerships, no resale commissions.
SAP Advisory ServicesIndependent SAP advisory helping enterprises choose the right HANA licensing model, plan BW/4HANA migrations, optimise SAC subscriptions, and negotiate licence conversions. Fixed-fee engagement models.