SAP Analytics Cloud is licensed per named user across two categories — Business Intelligence and Planning — and the price gap between them is wide enough that misallocation is the dominant source of waste. A Planning Professional seat can cost three to four times a BI seat, yet most are assigned to people who only read dashboards. Add the capacity-unit model and SAP Datasphere alongside, and the optimisation becomes a reclassification and consumption-forecasting exercise. This guide maps the tiers and the lever that recovers the overspend.
SAP Analytics Cloud (SAC) is licensed per named user in two categories: Business Intelligence and Planning. A BI user can consume dashboards, stories and visualisations; a Planning user can additionally write back data, run allocations and build forecasts — and Planning is split again into Standard and Professional, with Professional granting the full modelling toolset at three to four times a BI seat. SAC is also available on a capacity-unit consumption model, and the closely related SAP Datasphere is licensed purely by capacity units. The dominant waste is Planning Professional seats handed to users who never plan.
This is a sub-page of our SAP business apps licensing pillar. SAC sits in the named-user column of the portfolio metric map, which means its lever is reclassification — distinct from Concur's transaction banding or Joule's consumption staging.
The boundary is write-back. A BI user is read-only against the model: they open stories, filter dashboards and export. A Planning user can change the numbers — entering forecasts, running allocations and version comparisons that feed the planning cycle. Planning Professional adds the modelling layer: building the data models, defining allocation logic and managing the planning process itself. The licence tiers map directly onto those capabilities, and the cost steps up sharply at each boundary.
| Tier | Can do | Cannot do | Relative cost |
|---|---|---|---|
| Business Intelligence | Consume dashboards, stories, export | Write back, model | Base (1x) |
| Planning Standard | Input data, basic planning | Build models, advanced allocation | ~2–3x BI |
| Planning Professional | Model, allocate, manage process | — | ~3–4x BI |
A feature-usage pull tells you exactly how many Planning seats belong on BI — usually a lot.
Alongside named users, SAP offers SAC on a capacity-unit (CU) model, where access is drawn from a consumption pool rather than fixed seats — useful for broad, infrequent audiences. SAP Datasphere, the data-fabric layer formerly called Data Warehouse Cloud, is licensed entirely by capacity units that meter compute and storage. With any CU model, the cost problem changes shape: it is no longer "how many seats" but "how much consumption, and is it forecast." An unwatched Datasphere pool can exhaust mid-term and trigger an unbudgeted top-up at SAP's spot rate.
| Model | Applies to | Metric | Optimisation lever |
|---|---|---|---|
| Named user | SAC BI / Planning | Assigned seats by tier | Tier reclassification |
| Capacity units | SAC (consumption) | CU pool drawn down | Consumption forecasting |
| Capacity units | SAP Datasphere | Compute + storage CUs | Capacity right-sizing |
SAC reclassification, Datasphere capacity right-sizing, Concur banding and Joule AI staging — the full portfolio model in one paper.
The lever is usage-driven reclassification. SAC records what each assigned user actually does — whether they ever write back, model or only ever open a story. Pull that feature-usage data, identify the Planning Professional and Planning Standard seats whose holders only consume, and demote them to BI. Because the price step between tiers is large, even a modest reclassification rate moves the line materially. In our 340+ engagements, a SAC reclassification typically removes 20–35% of the seat cost with no loss of capability for any user who actually plans.
The same portfolio discipline applies across the cluster: Concur by transaction-band reset and Joule AI by consumption staging. SAC, Datasphere and Joule increasingly appear inside the same SAP cloud or RISE / GROW subscription, so the reclassification is best negotiated as part of the whole portfolio rather than as an isolated line. If an SAC entitlement true-up or audit is already underway, our SAP audit defence practice runs the reconciliation, and the documented outcomes are in our case studies.
$1.8B+ documented client savings · 340+ enterprise engagements · 95% client retention · 68% average audit-claim reduction · 11 vendor practices · Gartner recognised — buyer-side only since 2016.
Weekly compliance intelligence for IT leaders.
