Analytics Legends The knowledge platform for SAP Analytics
Academy module

SAC Calculation Views

SAC Calculation Views placement decision: reused or governance-critical calcs move to the Datasphere analytic model, story-local calcs stay in SAC — architecture diagram for SAC Calculation Views, Analytics Legends Academy module M024

As of 2026-08-16

Edited by , sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

4 calc primitives: calculated measure · restricted measure · calculated dimension · variable+input. Senior placement rule: ≥ 2 stories → push to Datasphere AM (M003) for DAC + glossary + version control; story-local → SAC calc view is fine. Heavy calc dim on M+ rows = slow render; pre-compute in DSP. SAC calcs not version-controlled; governance-critical work belongs upstream.

What you will learn

  • Choose the right calculation primitive (calculated measure, restricted measure, calculated dimension, variable/input) for a given story requirement.
  • Apply the senior placement rule: push any calc reused by two or more stories, or governance-critical, up to a Datasphere analytic model for DAC, glossary, and version control.
  • Diagnose and fix slow story rendering caused by heavy calculated dimensions on large row volumes by pre-computing in Datasphere.
  • Run a cross-story calc-duplication audit and reduce drift risk by cataloguing every SAC-local calculation.

Module overview

SAC calculation views = derived measures + formulas + restricted measures + filtered dimensions defined in SAC, on top of an analytic model. They're the right place for STORY-LEVEL business logic; the wrong place for ENTERPRISE-LEVEL business logic. The senior decision: where does this calculation belong — in the Datasphere analytic model (consumed by all stories), or in this one story?

The 4 calculation primitives.

  1. Calculated measure — formula combining existing measures (e.g. margin pct = (revenue - cost) / revenue).
  2. Restricted measure — measure with embedded filter (e.g. revenue eu = revenue WHERE country IN (EU members)).
  3. Calculated dimension — derived dimension (e.g. revenue band = CASE WHEN revenue > 1M THEN 'large' ELSE 'small').
  4. Variable + input control — story-time parameter (e.g. fiscal year selector that drives all widgets).

Senior craft signal — placement. A junior puts every calculation in SAC because it's where they're working. A senior asks: "will this be reused?". If yes → push into the analytic model in Datasphere (M003), define once, consume everywhere, gain DAC + glossary. If no → SAC calc view is fine.

Prerequisites

  • Intermediate hands-on experience on SAP analytics projects
  • Review core concepts first: C019, C008, C020

Outcomes

  • Understand the core concepts behind sac calculation views
  • Apply Calculations in a typical SAP analytics engagement
  • Explain the core architecture and decision points for SAC Calculation Views
  • Apply a repeatable implementation pattern in a 15-minute lab format

Full module available to members. The full module adds: the decision framework · the end-to-end scenario walkthrough · the KPI scorecard · the anti-patterns · the code blocks · the knowledge check · the diagrams.

Open in the app →

Next in this track