Concept card

SAP Analytics Cloud (SAC)

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is SAP Analytics Cloud (SAC)?

The SAC-Datasphere boundary is where push-down preservation and concurrency tuning bite hardest — never expose a raw Datasphere SQL view directly to SAC, always wrap it in an Analytic Model first.

What it is and why it matters

SAP Analytics Cloud is SAP's single surface for business intelligence, planning, and predictive analytics, and it is the consumption layer that sits on top of almost every Datasphere or BDC deployment. Business users touch SAC directly; it is also, unglamorously, where most "why is the dashboard slow" tickets land, because the boundary between SAC and its data source is where architectural decisions about push-down and concurrency actually bite. Understanding that boundary, not just building stories, is what separates a senior SAC architect from someone who can only drag fields onto a canvas.

How it works: three connection modes

Why it matters

Live connections cap at roughly 200 simultaneous ad-hoc users per Analytic Model before tail latency degrades — past that threshold, Import or Hybrid becomes necessary.
Import mode trades freshness for scale (thousands of users, sub-100ms) but leaves data stale between refreshes, typically 1-24 hours — wrong for real-time governed reporting.
Skipping the Analytic Model wrapper breaks the consistency of currency conversion, restrictions, and calculated measures that SAC stories depend on.

Key points

Three modes: Live (push-down, < 200 user, real-time) · Import (cache, 1000s user, stale) · Hybrid (both).
Always wrap raw Datasphere views in an Analytic Model before exposing to SAC.
Planning is the SAP differentiator — write-back, version control, audit, top-down/bottom-up reconciliation.
Predictive: Smart Predict for citizen-data-scientist + simple; Databricks for data-scientist + complex ML.
DAC at Datasphere is the row-security source of truth — reaches SAC + Joule + Delta + OData.
Concurrency cap on Live mode: ~200 simultaneous; hybrid above that.
Joule reads SAC story metadata + Datasphere Analytic Models for natural-language Q&A with citations.
SAC bills separately from Datasphere CU (per-named-user / per-concurrent-user model).
SAP Analytics Cloud (SAC) is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

SAC Live: Connection mode where SAC stories query Datasphere/HANA Cloud directly at every render. Push-down preserved.
SAC Import: Connection mode where SAC pulls data into in-memory cache; stories query the cache. < 100 ms p50, scales to 1000s of users, stale 1-24h.
Hybrid mode: Combination of Live (volatile slice) + Import (stable historical), joined at story level. Default for Tier-1 above 200 users.
SAC Planning: Write-back planning module — forecasts, budgets, drivers with version control + audit + multi-version reconciliation.
Smart Predict: SAC's built-in predictive (forecasting, classification, regression) for citizen-data-scientist workflows.
Analytic Model: Datasphere consumption-ready object exposed to SAC. Always wrap raw views in an AM before SAC consumption.
SAC Embedded: Separately-licensed deployment for embedding SAC stories inside other applications (Salesforce, custom portals) via iframe + JS API.
Smart cache: SAC's request-level deduplication for Live mode — recognises identical queries within a short window and serves cached results.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.