Concept card

SAC Stories & Dashboards

As of 2026-07-23

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 SAC Stories & Dashboards?

After Datasphere modeling wraps, 70-90% of remaining engagement time goes into Story design and stakeholder iteration — most enterprise Stories cycle 5-10 review rounds over 4-8 weeks, not the visual build itself.

What it is

SAC Stories are the consumption canvas of SAP Analytics Cloud — multi-page, interactive dashboards combining charts, tables, KPI tiles, narrative text, filters, and input controls. Every business user sees Stories; the consultant who delivers them well is the consultant invited back. After Datasphere modeling completes (companion C001), 70-90% of remaining engagement time goes into Story design, development, and refinement.

The four Story-design layers. (1) Information architecture — page count (typically 1 hero + 3-5 detail pages), navigation pattern (tab vs sidebar vs scroll), audience-page mapping. (2) Visual hierarchy — H1 KPI tile (the answer), supporting charts, drill-detail tables. (3) Interaction model — page-level filters, chart-level drilldowns, story-level input controls feeding planning models (companion C019). (4) Performance budget — render time per page (target < 2 sec), widget count cap (12 per page typical), Live vs Import mode per data source.

The five canonical Story types. (1) Executive scorecard — single-page hero KPIs + traffic-light commentary; CFO/CEO consumption, monthly cadence. (2) Operational dashboard — multi-page, role-tailored; Sales / Supply / Finance Ops daily-weekly use. (3) Variance-analysis story — actual-vs-plan-vs-forecast with narrative explaining each variance; finance close cycle. (4) Predictive story — Smart Predict outputs surfaced inline; product-management or risk-team consumption. (5) Narrative report — slide-like layout with explanatory text + charts; board package replacement.

Why it matters

Widget count above 12 per page degrades render time non-linearly — a performance budget matters as much as visual design.
Consultants overestimate visual customization complexity; the real time sink is stakeholder iteration, not chart-type variety (5-7 types cover most engagements).
Matching Story type to audience (executive scorecard vs operational dashboard vs variance-analysis) determines cadence and page depth from the outset.

Key points

Five canonical types: exec scorecard · operational · variance · predictive · narrative.
Information-architecture: 1 hero + 3-5 detail pages.
Performance: ≤ 12 widgets/page · ≤ 5 cascading filters · < 2 sec render p50.
Calculations live in Datasphere AM, not Story.
Mobile-first design for exec dashboards: +20-30% design time, real adoption uplift.
Joule integration via descriptive titles + semantic types in underlying AM.
Enterprise iteration cycle: 5-10 reviews / 4-8 weeks.
70-90% of post-Datasphere time goes into Story delivery.
SAC Stories & Dashboards 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 Story: Multi-page, interactive dashboard combining charts, tables, KPI tiles, narrative text, filters, input controls.
Information architecture: Page-count + navigation + audience-mapping design layer of a Story.
Widget count: Number of visualisations/components per page. Cap 12 per page; non-linear render degradation above.
Cascading filters: Filters where one selection updates the options of the next. Cap depth at 5 to avoid re-query latency.
Live mode: SAC connection mode pushing queries down to Datasphere/HANA. Concurrency cap ~200 users per AM.
Embedded SAC: Separate licence putting Stories inside Salesforce, Teams, custom portals via iframe + JS API.
Joule integration: Stories surface in NL answers via Joule grounding; quality depends on descriptive titles + populated semantic types.
Iteration cycle: Stakeholder review rounds during Story development. Enterprise default 5-10 rounds over 4-8 weeks.

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.

Open in the app →

Guides that answer with this page

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