SAP's Data & Analytics Products and Licensing Models
SAP HANA (In-Memory Database Platform)
SAP HANA is an in-memory, columnar RDBMS that underpins SAP's analytics and ERP solutions — powering real-time reporting for S/4HANA, BW/4HANA, and custom or third-party applications. 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.
🔒 HANA Runtime Licence
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 — essentially the total net price of SAP applications running on HANA — with SAP charging a percentage (commonly ~15%) of that value for HANA runtime rights.
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. CIOs who favour this model must ensure HANA serves only SAP's packaged applications, with no standalone development.
🔓 HANA Full-Use 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).
Full-use licences are relatively expensive with limited discounts. Costs scale with database size — flexibility to consolidate workloads on HANA, but if the memory footprint grows, licensing costs grow accordingly. SAP typically monitors HANA memory utilisation over 12 months for compliance; peak or average usage beyond purchased amounts may trigger true-up costs. 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 |
Need help choosing the right HANA licensing model?
SAP Licence Optimisation →SAP BW/4HANA (Data Warehouse)
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 BW/4HANA involves two aspects: the BW/4HANA application licence and the underlying HANA database licence.
📊 Capacity-Based (Volume) Licensing
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.
👤 User-Based Licensing
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.
📚 Related Reading
SAP Analytics Cloud (SAC)
SAC is SAP's flagship cloud analytics platform — providing BI (dashboarding, reporting), planning (budgeting & forecasting), and predictive analytics as SaaS. It represents a shift from licence-and-maintenance to subscription-based usage. SAC is available only as a cloud subscription with two primary models:
👥 User-Based Subscription
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–5 year terms. Essential to assign the correct licence type to each user — only give Planning licences to those who need planning features; others can use lower-cost BI licences.
📈 Capacity-Based Subscription
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 |
Common Licensing Pitfalls to Avoid
Several pitfalls routinely trap SAP analytics customers, leading to compliance issues or unplanned cost overruns. CIOs must be aware of these when evaluating and managing licences:
🚨 Exceeding Licensed HANA Memory (Sizing Pitfalls)
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. Mitigation: Right-size and continuously govern the HANA environment — archive cold data to cheaper storage, delete unused data (logs, traces), implement HANA's native data tiering (NSE or extension nodes). Treat HANA sizing as a licensing exercise, not just a technical one — forecast data growth and factor into licence planning.
⛔ Using Runtime HANA for Non-SAP Applications (Licence Breach)
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 and constitutes "indirect use" or "misuse." SAP audit programmes specifically target HANA runtime customers. Impact: SAP may demand a retroactive upgrade to full-use licensing plus back fees for maintenance. Mitigation: Educate all teams on HANA licence restrictions. If using runtime, ensure all data access is routed through the SAP application layer. If there is genuine business need for HANA as a general-purpose database, proactively discuss upgrade options with SAP.
🔗 Ignoring Indirect Access and Named User Licensing
Analytics tools pulling data from SAP systems and displaying to users without proper SAP user licences creates compliance risk. If a SAC dashboard displays data sourced from S/4HANA for a broad audience, do viewers require SAP named user licences? SAP's Digital Access model covers some cases (counting document events rather than users). Mitigation: 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.
💸 Overlapping and Redundant Licensing During Transitions
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. Mitigation: Always tie new deployments to a timeline for reducing old licences. Communicate internally that legacy systems will retire on schedule. 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.
Concerned about SAP licence compliance exposure?
SAP Audit Defence Service →Transition Strategies: Legacy BI to Modern SAP Analytics
From SAP BusinessObjects (BOBJ) to SAP Analytics Cloud (SAC)
SAP BusinessObjects BI platform has been a staple for on-premise reporting — Web Intelligence, Crystal Reports, Universe semantic layer, and Dashboards (Xcelsius). SAP's innovation focus has shifted to SAC, and BOBJ v4.3 is committed to maintenance support until at least 2027. CIOs have a multi-year window to execute migration.
🔎 Phase 1 — Assess, Rationalise & Extend
Audit your BusinessObjects environment. Identify heavily used vs redundant reports — many organisations find a significant portion of reports 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" — leveraging existing BOBJ data models while using SAC for modern visualisation. Continue using BusinessObjects for reports SAC cannot yet replace (complex operational reports, formatted statements). Encourage all new analytics requirements to be built in SAC.
📐 Phase 2 — Migrate Key Use Cases
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 often 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.
🏁 Phase 3 — Gradual Retirement & Cutover
Over 1–3 years, incrementally migrate remaining critical reports to SAC. Some content (high-volume batch printing) may need alternative solutions. The goal is to significantly reduce or entirely decommission the BusinessObjects environment — saving maintenance, infrastructure, and support costs. SAP offers a Private Cloud Edition (PCE) for BusinessObjects as a transitional option if you cannot retire BOBJ entirely by 2027.
From SAP BW (NetWeaver BW) to BW/4HANA or SAC
SAP BW 7.5 mainstream maintenance ends 2027, with extended maintenance (at additional cost) until 2030. CIOs must decide: upgrade to BW/4HANA, or shift to cloud-based data warehousing.
🔄 Option 1 — Migrate to SAP BW/4HANA
Direct evolution of your data warehouse. BW/4HANA 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. Can be bundled with S/4HANA digital transformation deals for better discounts. Caution: Treat as a reimplementation project, not "just an upgrade." Clean up data models and archive old data during migration to potentially reduce HANA footprint and licence costs.
☁️ Option 2 — Move to SAC & Cloud Analytics
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. Benefits: avoiding BW/4HANA licensing and infrastructure costs, simplifying the landscape. However, the data warehouse function shifts elsewhere — SAP Datasphere, cloud data lakes, or expanded S/4HANA data retention. New costs may include Datasphere subscriptions or infrastructure scaling. Best for: organisations with relatively simpler analytics needs and low-to-moderate data volumes.
🔀 Option 3 — Hybrid Approach
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. SAC can combine live data from BW with cloud sources in a single story.
Cost Optimisation Tactics for Analytics Licence Transitions
🔄 Leverage Licence Conversion and Swap Programmes
Take advantage of SAP's Cloud Extension Policy or licence swap offerings. Convert existing on-prem licence values into cloud subscriptions — e.g. convert unused BusinessObjects licences or maintenance into SAC subscriptions, or 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.
📦 Negotiate Bundled Deals
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.
📏 Rightsize Environments Before Licensing
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.
📅 Stagger Migrations to Avoid Peak Overlap
Don't 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.
🎯 Optimise SAC Licence Allocation
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.
🗑️ Retire Duplicative Tools
Once SAC is adopted, plan to fully retire at least one legacy BI tool — possibly others (Tableau, Qlik) if consolidating on SAC. Every system retired saves maintenance fees and simplifies governance. Similarly, if BW/4HANA replaces third-party ETL or database systems, retire those too. Resist keeping old systems "just in case" — have a clear decommission plan and execute it.
📋 Continuous Licence Audit & Compliance Management
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.
🎓 Training and Change Management
Invest in user training to maximise ROI on new systems. Well-trained SAC/BW/4HANA users fully utilise features, justify consolidating other tools, and are less likely to unintentionally violate licence rules (e.g. an educated user won't connect unauthorised tools to runtime HANA). Allocate budget for education to protect and maximise your software investment.
Need expert help negotiating SAP licence conversions?
SAP Contract Negotiation →Actionable Recommendations for CIOs
Map Your Analytics Landscape and Licence Position
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.
Choose HANA Licence Type Strategically
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.
Evaluate BW/4HANA Migration vs Alternative Solutions
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. Either way, archive and prune data to minimise the footprint and cost.
Plan BusinessObjects to SAC Transition in Phases
Develop a phased migration plan. Begin by integrating SAC with existing BI in hybrid mode for quick wins. 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.
Optimise SAC Licensing and Drive Adoption
Select the right model (user-based vs capacity-based) based on user count and usage patterns. Start with manageable numbers and scale. Continuously review licence assignments — 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.
Use SAP's Incentive Programmes and Negotiate
Take advantage of bundled discounts, trial periods, and flexible licensing during migration. When negotiating, bring SAP a holistic plan covering all products. Consolidating purchases yields better pricing. Seek custom terms — e.g. free development SAC tenant, temporary dual-use licence for BW and BW/4 during migration. SAP often accommodates to ensure adoption.
Tighten Governance to Avoid Surprises
Establish licence compliance governance. Track how systems are used internally. Prevent unauthorised direct access to HANA under runtime licences using technical controls. Ensure every third-party system interfacing with SAP data is licensed appropriately. Consider SAP's Digital Access document licensing if relevant. Proactively run SAP measurement tools.
Retire Legacy Systems to Harvest Savings
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. If needed, export data to cheaper storage for compliance — but shut down expensive software.
Monitor SAP's Roadmap and Adjust
SAP's analytics roadmap is evolving (SAC + Datasphere integration, "one data suite" vision). Stay informed through SAP briefings. If new licensing models or products emerge that reduce cost or improve capabilities, be ready to pivot. Maintain flexible contract structures or shorter SAC terms to preserve adaptability.
Engage Stakeholders and Build the Business Case
Communicate with CFO, Finance, and business unit leaders. Develop a clear business case quantifying cost of status quo (rising maintenance, old hardware) vs investment in new solutions with anticipated benefits (performance, agility, eventual cost reductions). Highlight business value of modern analytics — not just IT savings. A well-understood strategy eases approvals and sets expectations.
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. Proactive management turns what could be a complex licensing minefield into a genuine opportunity to optimise costs and accelerate data-driven decision-making.
📂 SAP Case Studies
🔧 SAP Advisory Services
📄 White Papers & Resources
Need Help with SAP Data & Analytics Licensing?
Whether you need guidance choosing between HANA runtime and full-use licensing, help planning a BW/4HANA migration, SAC licensing optimisation, audit readiness assessment, or contract negotiation support for SAP renewals — our independent SAP licensing specialists have the deep expertise to deliver results and save you millions.
💡 Download our SAP licensing white papers for actionable strategies
View White Papers →