SAC Models
SAC Models are the foundational metadata layer in SAP Analytics Cloud that define dimensions, measures, hierarchies, and data connections used by stories, dashboards, and planning applications. This topic covers analytic and planning model types, dimension and account structures, live versus imported data acquisition, currency conversion, and how models integrate with SAP Datasphere and other source systems to deliver governed, reusable data foundations across an SAC tenant.
Overview
SAC Models are the foundational metadata layer in SAP Analytics Cloud that define dimensions, measures, hierarchies, and data connections used by stories, dashboards, and planning applications. This topic covers analytic and planning model types, dimension and account structures, live versus imported data acquisition, currency conversion, and how models integrate with SAP Datasphere and other source systems to deliver governed, reusable data foundations across an SAC tenant.
Lessons in this topic
- SAP SAC Models Tutorial (Part 1)Introduces what an SAC model is, why it exists as a separate layer from stories, and the fundamental differences between analytic and planning models, dimensions, measures, and data acquisition modes.
- Designing SAC Model Structures: Dimensions, Accounts, Currency, and Version Management (Part 2)Covers practical design decisions for building robust SAC models, including dimension types, the Account dimension in planning models, currency conversion setup, version handling, and validation before rollout.
- Calculated Measures, Restricted Measures, and Currency Conversion in SAC Models (Part 3)Learn how to extend an SAC model's analytical power using calculated measures, restricted measures, and currency conversion so business users get correct, reusable metrics without duplicating logic in every story.
- Advanced SAC Models: Architecture, Integration and Production Design (Part 4)Advanced capstone for SAC Models, connecting the existing lesson areas: Understanding SAC Models: Purpose, Types, and Core Building Blocks; Designing SAC Model Structures: Dimensions, Accounts, Currency, and Version Management; Calculated Measures, Restricted Measures, and Currency Conversion in SAC Models. The goal is to move from feature knowledge to architecture, integration, production support and governance decisions.
Interview questions covered
- What are the core concepts of SAC Models, and how would you explain them clearly in an SAP interview?
- How would you apply SAC Models in a real SAP project? Walk through the design or implementation approach.
- A production issue is reported in SAC Models. What would you check first, and how would you troubleshoot it systematically?
- What are the most important design decisions, trade-offs, and best practices in SAC Models?
- Suppose you inherit an existing SAC Models solution. How would you review it before making a change?
- A senior architect is reviewing SAC Models. The project situation is: A retail analytics team was asked to build a sales performance dashboard. What design changes, validation evidence and production controls would you require before approving the solution?
- Using this SAP project situation — A retail analytics team was asked to build a sales performance dashboard — explain Understanding SAC Models: Purpose, Types, and Core Building Blocks. What should happen, which concepts or process steps matter, and what common mistake would you avoid?
- A project encounters this situation while working on Designing SAC Model Structures: Dimensions, Accounts, Currency, and Version Management: During a financial planning rollout, a consultant built a planning model with an Account dimension containing over 200 GL-mapped accounts and a Version dimension with Actual, Budget, and multiple Forecast cycles. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.
- A project encounters this situation while working on Calculated Measures, Restricted Measures, and Currency Conversion in SAC Models: A retail client's finance team needed a single SAC model to support both regional profitability dashboards and a monthly plan-vs-actual review. Walk through how you would analyze the requirement or issue, what you would validate, and how you would test the solution before release.