SAP Analytics Cloud (SAC) Licensing: The Complete Guide for 2026

SAP Analytics Cloud (SAC) is SAP's answer to the modern analytics and planning market — combining Business Intelligence (BI), Enterprise Planning, and Predictive Analytics in a single cloud platform. It is also SAP's intended replacement for a fragmented legacy analytics landscape that includes BusinessObjects (BO), Analysis for Office, and Planning and Consolidation (BPC). If you are running any of these products, SAP is actively pushing you toward SAC — and the commercial terms on offer are not always as straightforward as the product pitch suggests.

This guide — produced by independent SAP licensing experts — breaks down the complete SAP Analytics Cloud licensing model: user types, capacity units, embedded vs. standalone licensing, migration paths from legacy products, and a clear negotiation framework for enterprise buyers. Whether you are evaluating SAC for the first time or renegotiating an existing subscription, this guide gives you the commercial intelligence you need.

How SAP Analytics Cloud Licensing Works

SAP Analytics Cloud is licensed as a cloud subscription with two primary dimensions: user-based licensing for named individuals who consume analytics or planning content, and capacity-based licensing for the compute and storage resources the platform consumes. Both dimensions must be sized and negotiated correctly — and SAP's default sizing proposals almost always favour SAP's revenue over the customer's actual requirements.

SAC is available in two deployment scenarios: as a standalone product licensed directly, and as an embedded capability bundled within S/4HANA Cloud or RISE with SAP agreements. The pricing and licensing rules differ meaningfully between these two scenarios, and understanding which route applies to your organisation — and which route is commercially advantageous — is essential before any negotiation begins.

SAP has positioned SAC as the long-term replacement for its entire legacy analytics portfolio. This creates both an opportunity and a risk for enterprise buyers. The opportunity: migration conversations give you genuine leverage to negotiate favourable SAC pricing in exchange for committing to the migration. The risk: SAP's migration incentive programmes often come with contractual strings that limit your flexibility in ways that are not obvious at signing.

SAC User Types: BI, Planning, and Beyond

SAP Analytics Cloud has multiple distinct user types, each licensed at a different price point and each carrying specific access rights. Confusing the user types — either through over-specification or under-specification — is one of the most common and most costly SAC licensing mistakes.

BI Consumer (View Only)

The lowest-cost SAC user type. BI Consumers can view and interact with dashboards, stories, and analytical applications — but cannot create or edit content. This user type is appropriate for operational managers, finance teams, and business users who consume analytics output but do not build reports. A critical trap: many organisations license BI Consumer users when their requirements actually demand BI Creator access, leading to adoption problems when users discover they cannot perform basic data exploration. The reverse is also common: organisations licence BI Creator for users who only ever view content, paying a substantial premium unnecessarily.

BI Creator (Full Analytics)

Full analytics authoring access. BI Creators can build stories (SAC's term for dashboards and reports), create and manage data connections, run data analysis, and publish content for Consumer access. This is the appropriate licence for analytics developers, finance controllers building management reporting, and any business user who needs to create or modify analytical content. BI Creator is typically 3–5x the cost of BI Consumer — making correct classification critically important.

Planning Professional and Planning Standard

SAC's planning user types cover the Enterprise Planning capability — budget modelling, financial consolidation, driver-based planning, and scenario analysis. Planning Professional is the full planning licence, covering model creation, data input, and plan publication. Planning Standard provides a lower-cost option for users who need to contribute data to planning models but not build or administer them. The Planning user types are licensed separately from BI user types — a user who needs both analytics and planning access requires a combined licence, and SAP does not automatically offer the most cost-effective combination. Always audit your mixed-use users before accepting SAP's default bundling.

Embedded Analytics (SAP Analytics Hub)

A distinct category for users accessing SAC analytics capabilities embedded directly within S/4HANA Fiori applications. These users consume pre-built SAP analytical apps within the ERP interface — they are not accessing the standalone SAC platform. The licensing for Embedded Analytics users is typically included within the S/4HANA licence entitlements, which means organisations running SAC standalone may be duplicating costs for users who could be served through the embedded route.

Capacity Units and Resource Consumption

Alongside user-based licensing, SAP Analytics Cloud charges for Capacity Units — a consumption-based measure of the compute and storage resources consumed by the SAC tenant. Capacity Units cover data model storage, data replication volumes, predictive scenario runs, and other platform-intensive operations.

SAP provides a base capacity allocation with each subscription tier, and organisations that exceed their committed Capacity Units face overage charges. The challenge for enterprise buyers is that Capacity Unit consumption is difficult to predict accurately at contract signing — it depends on the number and complexity of data models, the frequency of data replication jobs, and the number of predictive scenarios run by analytics users. SAP's pre-sales estimates of Capacity Unit requirements are typically conservative, meaning many customers exhaust their allocation faster than expected and incur unbudgeted overages.

The correct approach is to request SAP's Capacity Estimator tool output as part of the commercial proposal process — and then apply a 25–40% buffer to the estimate, which reflects typical real-world consumption variance. Lock in an overage rate in the contract before signing; this is a standard negotiating point that SAP will accept, but rarely offers proactively.

Embedded SAC vs. Standalone SAC

One of the most commercially important questions in SAC licensing is whether your organisation should license SAC as a standalone product or access it through an embedded entitlement within S/4HANA Cloud or RISE with SAP. The answer is not always straightforward, but the cost implications are significant.

Embedded SAC — accessed through S/4HANA Cloud Private Edition or RISE with SAP — includes a base set of SAC capabilities as part of the S/4HANA subscription. The precise scope of embedded SAC entitlements varies by S/4HANA edition and contract configuration, but typically covers Embedded Analytics (the Fiori-based analytics), a limited number of BI Consumer licences, and access to pre-built SAP analytical applications. Planning and advanced BI Creator capabilities are generally not included in embedded entitlements.

Standalone SAC provides the full SAC platform — BI, Planning, Predictive, and all authoring capabilities — but requires a separate subscription in addition to any S/4HANA licence. For organisations whose analytics requirements go beyond the embedded scope, standalone SAC is necessary. The risk is paying twice: buying standalone SAC for capabilities that are already included in an embedded entitlement for a subset of users.

Our SAP license optimisation advisory routinely maps S/4HANA embedded SAC entitlements against actual usage before recommending any standalone SAC investment. The duplication we find is common — and expensive.

Migrating from BusinessObjects, BPC, and Analysis for Office

For the majority of large SAP installations, the SAC conversation is not a greenfield decision — it is a migration question. Organisations running SAP BusinessObjects (BO) for reporting, SAP BPC (Business Planning and Consolidation) for financial planning, or Analysis for Office for self-service analytics are all in SAP's migration crosshairs. Understanding the commercial dynamics of these migrations is essential.

BusinessObjects to SAC

SAP has reduced investment in the BusinessObjects portfolio significantly and is pushing all BI customers toward SAC. SAP offers migration incentive pricing — discounted SAC subscriptions for customers who agree to de-commission BO deployments. The incentive pricing looks attractive on paper; the commercial strings it comes with are not always visible. Migration incentive contracts typically include accelerated BO support end dates, minimum SAC user commitments that exceed actual requirements, and limited flexibility to adjust user counts during the incentive period. Get an independent review before accepting any BO migration offer from SAP.

BPC to SAC Planning

SAP BPC customers are in an increasingly difficult position. SAP has significantly reduced BPC investment and the product's roadmap is limited. SAC Planning is the intended replacement, but the migration is technically complex — BPC data models and planning sequences do not map cleanly to SAC Planning constructs, and the functional equivalence between the two products is still evolving. Enterprise buyers evaluating the BPC-to-SAC migration should commission an independent functional gap assessment before committing to a migration timeline.

Analysis for Office to SAC

Analysis for Office (AfO) — SAP's Excel-based OLAP reporting tool — remains widely used for financial analysis and management reporting. SAP is pushing its replacement with SAC's Live Data Connection to SAP BW/BW4HANA, but AfO's Excel-native experience has a high user preference that SAC's browser-based interface does not fully replicate. Be cautious of SAP migration incentives that include large SAC Consumer or Creator counts to replace AfO users who may resist adoption.

Hidden Costs and Licensing Traps

Data Integration and BTP Consumption

Loading data into SAC from non-SAP sources — or from SAP BW — typically requires SAP Integration Suite or SAP Datasphere (formerly SAP Data Warehouse Cloud). Both of these carry separate licensing costs. Organisations building comprehensive analytics solutions on SAC often find that the total platform cost — SAC plus Datasphere plus Integration Suite — is substantially higher than the headline SAC subscription suggested. Model the complete data architecture cost before committing.

Predictive Analytics Capacity

SAC's Predictive Analytics (formerly Smart Predict) is one of the platform's genuinely differentiated capabilities, but it is Capacity Unit-intensive. Running complex predictive scenarios on large datasets consumes Capacity Units at a rate that is difficult to predict accurately. If Predictive Analytics is central to your use case, model Capacity Unit consumption separately and negotiate a dedicated capacity allocation for predictive workloads.

Custom Application Development

SAC's Analytic Application capability allows developers to build custom front-end applications on top of SAC data models. This is powerful functionality — but it requires BI Creator licences for the developers, plus significant development and maintenance effort. Ensure your total cost model includes ongoing application maintenance as well as initial build cost.

How to Negotiate Your SAP Analytics Cloud Contract

SAC negotiations share characteristics with other SAP cloud product negotiations — SaaS model, annual subscription, multi-year commitments with escalators — but also have specific dynamics driven by SAP's legacy migration agenda. Buyers who understand these dynamics negotiate significantly better deals.

Leverage SAP's Migration Urgency

SAP needs to migrate its BusinessObjects and BPC customers to SAC. This migration agenda creates genuine leverage for enterprise buyers: SAP's commercial teams are incentivised to close migration deals, and they have pricing flexibility to do so. Use this leverage explicitly — make clear that your migration timeline and commitment volume are contingent on commercial terms that reflect your actual requirements, not SAP's sizing estimates.

Negotiate User Type Mix Flexibility

SAP's standard SAC contracts fix the allocation of user types at signing. If your actual usage pattern differs from your initial estimate — which it almost always will — you are locked into a suboptimal mix until renewal. Push for contractual flexibility to rebalance user types (e.g., converting Creator licences to Consumer licences, or Standard Planning to Professional Planning) without requiring a full contract amendment. This is achievable — SAP includes it in some enterprise agreements — but it must be negotiated proactively.

Address Capacity Units Before Signing

Secure a minimum Capacity Unit allocation that includes a reasonable buffer above SAP's estimate, and negotiate a maximum overage rate that limits your exposure if consumption exceeds the allocation. Request SAP's Capacity Estimator output and challenge the assumptions in it — particularly around data replication frequency and predictive scenario volumes.

Benchmark Against Competitive Alternatives

SAP Analytics Cloud competes with Microsoft Power BI, Tableau, Qlik, and Workday Adaptive (for planning). All four have been gaining enterprise market share in areas where SAC underperforms — particularly in self-service BI ease of use and Excel-native planning. Having documented competitive pricing and a credible evaluation process gives you leverage that pure-play SAP organisations rarely deploy effectively. Our SAP contract negotiation advisors build competitive benchmarks as a standard part of every SAC engagement.

Key Takeaways

Related Articles