Getting Started
Overview & Architecture
SAP Analytics Cloud (SAC) is a single, cloud-based solution that integrates Business Intelligence (BI), Augmented Analytics, and Enterprise Planning into one user interface.
What is SAP Analytics Cloud?
Built natively on the SAP Business Technology Platform (BTP) and powered by SAP HANA in-memory technology, SAC removes the need for standalone reporting, planning, and predictive tools. It provides a unified platform for all analytics use cases.
Core Philosophy: Discover, Visualize, Plan, and Predict in a single workflow. Instead of jumping between SAP BPC for planning, SAP Lumira/WebI for reporting, and SAP Predictive Analytics, users can do it all within an SAC Story.
Core Capability Areas
📊
Business Intelligence (BI)
Connect to live or imported data to create interactive dashboards, self-service data exploration, and formatted reporting.
Create and distribute budgets, run predictive forecasts, execute advanced allocation rules, and write data back to SAP systems.
Leverage machine learning algorithms to uncover hidden drivers (Smart Discovery), automate insights (Smart Insights), and forecast future values.
Build custom, complex analytic applications with sophisticated scripting, custom widgets, and advanced UI interactions.
Architecture & Hosting
SAC is offered purely as a Software-as-a-Service (SaaS). Customers access it via a web browser. There is no on-premise installation. Updates are pushed out by SAP automatically (either on a Fast Track or Quarterly Release Cycle).
| Layer | Technology |
| User Interface | Web Browser (HTML5/Fiori design guidelines) |
| Application Layer | SAP Analytics Cloud core services running on SAP BTP |
| Database Layer | SAP HANA Cloud (tenant database for imported data and metadata) |
| Connectivity | SAP Cloud Connector & SAP Analytics Cloud Agent (for on-premise) |
Getting Started
Live vs Import Connections
Understanding how SAC connects to data is the most critical architectural decision. SAC offers two fundamental connectivity paradigms: Live Data and Acquired (Import) Data.
Live Data Connection
In a Live connection, data never leaves the source system. SAC only retrieves metadata (to build the model) and queries the source system in real-time when a user opens a story. The heavy lifting (aggregations, calculations) is done by the source database.
- Data Privacy: Highly secure; sensitive data remains behind your corporate firewall.
- Freshness: Real-time. What you see is exactly what is in the source at that second.
- Authorization: Security roles defined in the source system (e.g., SAP BW Analysis Authorizations or HANA privileges) are strictly applied.
- Supported Sources: SAP HANA, SAP BW/4HANA, SAP S/4HANA, SAP Datasphere, SAP BPC, SAP Universe (BOBJ).
Acquired (Import) Data Connection
In an Import connection, data is physical copied (extracted) from the source system and stored securely inside SAC's internal HANA database. Data can be refreshed via scheduled jobs.
- Data Blending: Allows joining data from multiple disparate sources (e.g., SAP S/4HANA + Salesforce + flat files) inside the SAC model.
- Smart Features: Full access to Smart Predict and advanced wrangling features.
- Planning: Requires imported models (except when planning against SAP BPC live or specific Datasphere architectures).
- Supported Sources: Almost anything (OData, SQL databases, SuccessFactors, Concur, Google Drive, Excel, flat files).
Best Practice Rule of Thumb: If your data is in an SAP system (HANA, BW, Datasphere), use a Live Connection unless you specifically need robust data blending across disparate sources or require extensive machine learning/predictive workflows not supported live.
Comparison Matrix
| Capability | Live Connection | Import Connection |
| Data Storage | Remains in source system | Copied to SAC internal HANA |
| Data Freshness | Real-time | Scheduled / Manual Refresh |
| Data Volume Limit | Source system limits | SAC tenant memory limits |
| Data Security applied by | Source system | SAC (Data Access Control) |
| Data Blending | Limited (Browser-based blending) | Full capability in Data Preparation |
| Planning Workflows | Limited (BPC / Datasphere) | Fully Supported |
SAP Cloud Connector & SAC Agent
To connect to on-premise systems (both Live and Import), you must install the SAP Cloud Connector. For Import connections specifically from on-premise sources (like SQL Server or older SAP ERP), the SAP Analytics Cloud Agent is also required to facilitate data extraction.
Getting Started
Roles & Licenses
SAC uses a combination of Licenses, Roles, and Teams to control what users can do and see within the tenant.
License Types
Licenses represent the commercial entitlement. A user must be assigned a license type before they can do anything. The primary licenses are:
| License Type | Target Audience | Key Capabilities |
| Business Intelligence (BI) | Analysts, Report Consumers | View stories, create stories, data modeling, use Smart Insights. Cannot perform planning. |
| Planning Standard | Contributors | Everything in BI + execute data actions, input planning data, view public versions. |
| Planning Professional | Planners, Controllers | Everything in Standard + create planning models, configure allocations, create Value Driver Trees. |
| Analytics Hub | Consumers | Access to the centralized Analytics Hub catalog only. |
Standard Roles
While licenses grant the capability, Roles grant the actual permission to execute actions. SAC comes with standard roles, and administrators can create custom roles.
- Admin: Full access to system configuration, security, and all objects.
- Modeller: Create and maintain connections, dimensions, and models.
- Viewer: Read-only access to stories and dashboards.
- Planner: Can input data into planning models and publish versions.
License vs. Role: A user might have a Planning Professional license, but if they are only assigned a Viewer role, they will only be able to view stories. The role cannot exceed the capabilities granted by the license.
Data Modeling
Classic vs New Models
The Model is the core data foundation in SAC. It defines the structure (dimensions and measures) that stories and planning processes run on.
Datasets vs Models
Before diving into models, it's important to understand datasets:
- Dataset: A flat, unstructured table of data. Excellent for quick, ad-hoc data exploration and Smart Predict. Less rigid.
- Model: A structured star-schema. Enforces data governance, hierarchies, and planning logic. Essential for enterprise reporting and planning.
The Classic Model (Account-Based)
Historically, SAC utilized an Account-based model. In this architecture, all numeric data is stored in a single generic measure column, and an "Account" dimension dictates what that number means (e.g., Revenue, Cost, Quantity).
- Rigid structure: Always requires an Account dimension.
- Familiar to SAP BPC and Finance users.
- Currency conversion and aggregations are defined on the Account members.
The New Model (Measure-Based)
Introduced to align with modern data warehousing (like SAP Datasphere and Snowflake), the New Model allows for multiple explicit measure columns (e.g., one column for Revenue, one for Quantity, one for Discount).
Key Benefit: The New Model provides massive flexibility. You can still use an Account dimension if you want (for financial statements), but you don't have to. You can also mix Accounts and Measures.
New Model Features
| Feature | Advantage |
| Multiple Measures | Store Quantity, Amount, and Price in separate columns without needing a complex Account dimension. |
| Calculated Measures | Define complex calculations directly in the model rather than in the story. |
| Flexible Currency | Supports currency variables and converting a single base measure into multiple target currencies at runtime. |
| Data Integration | Closer alignment with SAP S/4HANA CDS views and Datasphere analytical datasets. |
Migration: SAP is actively encouraging users to migrate Classic models to the New Model type. All new SAP standard business content utilizes the New Model.
Data Modeling
Dimensions & Measures
Dimensions provide the context to your data, while measures provide the quantifiable numbers.
Dimension Types
SAC enforces specific dimension types to ensure data behaves correctly, especially for time-series charts and planning.
Crucial for time-series analysis and planning. Supports automatic generation of hierarchies (Year > Quarter > Month).
Used to represent company hierarchy (Cost Centers, Regions). Vital for planning data locking and security.
Standard dimensions like Product, Customer, or Material. Supports custom properties (attributes) and hierarchies.
Specific to planning models. Separates Actuals from Budget, Forecast, and custom simulation scenarios.
Hierarchies
Hierarchies allow users to drill down from high-level summaries to granular details. SAC supports two main types:
- Level-based Hierarchies: Defined by columns (e.g., Country Column > State Column > City Column).
- Parent-Child Hierarchies: Defined by relationships within members of a single dimension (e.g., Employee ID and Manager ID). Best for unbalanced organizational charts.
Public vs Private Dimensions
| Type | Scope | Use Case |
| Public Dimension | Can be shared across multiple models in the tenant. | Master data like Cost Centers, Accounts, or Employees that should be consistent across all dashboards. |
| Private Dimension | Exists only within a single specific model. | Model-specific categorizations (e.g., a custom grouping for a one-off marketing campaign). |
Data Modeling
Data Preparation (Wrangling)
When importing data, the Data Preparation space allows you to clean, format, and transform your data before it enters the model.
Transformations
SAC provides an Excel-like grid interface for data wrangling. Common operations include:
- Concatenate / Split: Combine First Name and Last Name, or split a composite string.
- Replace / Fill: Replace null values with a default string (e.g., "Unassigned").
- Change Data Type: Convert a string representation of a date into an actual Date format SAC can recognize.
Custom Expressions
For advanced transformations, SAC uses a formula language similar to Excel. You can create custom columns based on logic:
-- Example: Creating a Region column based on Country
IF([Country] = 'US' OR [Country] = 'CA', 'North America', 'Other')
Smart Transformations: SAC utilizes machine learning to suggest transformations. If it detects a column of dates in different formats, it will prompt a suggestion to harmonize them into a single ISO format.
Mapping to the Model
During the data import process, you map the columns from your flat file or SQL query to the Dimensions and Measures defined in your SAC Model. If a member exists in your incoming data that doesn't exist in a Public Dimension, you can configure the job to either reject the row or auto-create the new master data member.
Story Design
Optimized Design Experience
A Story is where data comes to life. It is the presentation layer consisting of charts, tables, text, and interactive elements.
Optimized Story Experience (ODE)
Historically, SAC had separate interfaces for "Stories" (BI) and "Analytic Applications" (advanced scripting). The Optimized Story Experience unifies these. ODE offers faster loading times, smoother interactions, and the ability to seamlessly transition from a standard dashboard to a highly customized scripted application.
Page Types
1
Responsive Page
Organizes content into lanes. Lanes automatically reflow and stack based on the screen size (desktop vs. tablet vs. mobile). Required for viewing on the SAC Mobile App.
2
Canvas Page
Pixel-perfect placement. You control the exact X and Y coordinates of every chart. Elements do not move or resize based on the screen. Best for strict formatting (like financial statements).
3
Grid Page
An Excel-like interface used primarily for high-volume data entry in planning scenarios or rapid tabular analysis.
Story Structure & Theming
Good story design utilizes Themes (to consistently apply corporate colors and fonts across all charts) and Templates (to ensure standardized layouts across departments).
Story Design
Charts & Tables
Choosing the right visualization is key to communicating data effectively. SAC provides a rich library of standard and advanced widgets.
Chart Types
| Category | Chart Types | Best Used For |
| Comparison | Bar, Column, Waterfall | Comparing values across categories (e.g., Sales by Region). Waterfall is excellent for showing impacts to a total. |
| Trend | Line, Area, Time Series | Showing how a measure changes over time (e.g., Revenue over 12 months). |
| Distribution | Scatter Plot, Bubble, Heat Map | Identifying correlations or outliers among many data points. |
| Indicator | Numeric Point, Bullet | Highlighting a single high-level KPI and comparing it to a target. |
Advanced Table Features
Tables in SAC are incredibly powerful, acting as more than just data grids:
- In-Cell Charts: Display micro-bar charts directly inside table cells to visualize magnitudes instantly.
- Thresholds: Apply conditional formatting (red, yellow, green) based on rules or target comparisons.
- Responsive Styling: Tables can auto-hide columns on smaller screens while preserving key data.
Variances
Instead of manually calculating differences, SAC allows you to add Variances directly to charts. You can instantly show the difference between Actuals vs. Budget (both absolute value and percentage) integrated visually into a bar chart.
Story Design
Filters & Linked Analysis
Interactivity turns a static report into an analytical tool. Filters and Linked Analysis dictate how user selections impact the data shown.
Filter Scope
Filters can be applied at different levels of the story hierarchy:
| Scope | Effect |
| Story Filter | Applies to all pages and all charts within the story. (Often placed in the top filter bar). |
| Page Filter | Applies only to the widgets on the current active page. |
| Widget Filter | Applied locally to a single chart or table. Hidden from the end-user by default. |
Linked Analysis
Linked Analysis allows widgets to interact with each other. If you click on "North America" in a pie chart, you can configure it so that a bar chart next to it automatically filters to show only North American sales.
Configuration: You can set Linked Analysis to affect: Only the selected widget (default), all widgets on the page, or only specific widgets you select manually.
Input Controls
Input controls are UI elements (like dropdowns, sliders, or radio buttons) placed directly on the canvas. They allow users to easily toggle filters or swap measures/dimensions dynamically without opening complex menus.
Story Design
Advanced Scripting
With the Optimized Story Experience, you can use JavaScript-based scripting to build custom application logic, complex navigations, and tailored user experiences.
When to use Scripting
While SAC's drag-and-drop interface is powerful, scripting is necessary when you need:
- Custom Workflows: Guiding a user through a multi-step planning process with "Next" and "Back" buttons.
- Dynamic UI Changes: Hiding/showing charts, changing colors, or swapping data sources based on a specific button click or variable state.
- Custom API Calls: Sending data to external systems or triggering BTP integration flows via REST APIs.
Scripting Environment
Scripts are attached to Events. For example, a Button widget has an onClick event. A Dropdown has an onSelect event. You write code that executes when that event fires.
-- Example: Changing a chart dimension via a dropdown selection
var selection = Dropdown_1.getSelectedKey();
Chart_1.removeDimension("Product", Feed.CategoryAxis);
Chart_1.addDimension(selection, Feed.CategoryAxis);
Custom Widgets
If SAC's standard chart library doesn't meet a specific need (e.g., a highly specific network diagram or D3.js visualization), developers can create Custom Web Components and import them into SAC to be used alongside standard charts.
Planning
Planning Basics & Versions
SAC Enterprise Planning allows organizations to collaboratively build budgets, execute advanced modeling, and write data back to the database.
Versions (Public vs Private)
Version management is central to SAC Planning. Versions allow multiple "truths" to exist simultaneously without overwriting Actuals.
| Type | Description |
| Public Version | Visible to everyone with appropriate access (e.g., Actuals, Approved Budget 2024). Changes are saved directly to the database. |
| Private Version | A personal sandbox. Created when a user starts adjusting data. Only visible to the creator until they choose to "Publish" it back to a Public Version. |
Data Entry: Users enter data directly into Tables within stories. SAC automatically handles disaggregation (e.g., if you type $12,000 for the Year, it automatically splits it into $1,000 per month based on historical weighting or equal distribution).
Data Locking & Validation
To control the planning cycle, administrators use Data Locking. You can lock specific slices of data (e.g., locking Q1 Actuals so they cannot be changed, while leaving Q2-Q4 Open for forecasting).
Validation Rules ensure data integrity (e.g., preventing users from planning Headcount expenses against a non-HR cost center).
Calendar & Tasks
The SAC Calendar is a workflow orchestration tool. Managers can create Tasks (e.g., "Complete Regional Q3 Budget"), assign them to specific planners, set deadlines, and track the progress of the entire planning cycle.
Planning
Data Actions & Formulas
Data Actions are predefined sequences of operations that execute complex planning logic, calculate values, and move data in bulk.
What is a Data Action?
A Data Action is triggered by the end-user via a button in the story. It acts as a batch processor. Common uses include:
- Copying Actuals from last year into the Budget version for next year.
- Calculating depreciation across hundreds of assets.
- Applying a blanket 5% inflation increase to all operational expenses.
Data Action Steps
A single Data Action can contain multiple sequential steps:
Simple slice-and-dice copying across versions, periods, or other dimension members.
Write custom script (similar to BPC script logic) with FOREACH loops and complex IF statements.
Execute an allocation rule (e.g., spreading IT overhead costs) as part of the sequence.
Advanced Formula Scripting
Advanced Formulas allow you to execute logic that cannot be achieved with simple visual rules.
-- Example: Increase next year's budget by a parameter variable
DATA([d/Version]="Budget", [d/Date]="2025") =
RESULTLOOKUP([d/Version]="Actuals", [d/Date]="2024") * @InflationRate
Parameters: Data actions can utilize parameters, prompting the user via a popup to select a specific variable (like the target year or an inflation percentage) before the action runs.
Planning
Allocations
Allocations are used to distribute costs or revenues from a high-level bucket down to granular dimensions based on specific drivers.
The Allocation Process
A typical scenario: The IT department has a total cost of $1,000,000 stored at a generic "Corporate" level. This cost needs to be allocated to the Sales, Marketing, and HR departments based on their respective headcount.
1
Source
Where is the money coming from? (e.g., IT Cost Center, Unassigned Product).
2
Driver
What determines the split? This can be direct (evenly split), based on another measure (Headcount, Square Footage), or based on historical actuals.
3
Target
Where does the money go? (e.g., Receiver Cost Centers, specific Product lines).
Visual Allocation Rules
SAC provides a visual designer to build these steps without scripting. You create an Allocation Process containing multiple Allocation Steps. These processes can be attached to a Data Action button so end-users can run them on demand after inputting driver data.
Planning
Value Driver Trees (VDT)
Value Driver Trees are interactive, visual models used for what-if simulations and top-down/bottom-up scenario planning.
What is a VDT?
A VDT links various business drivers mathematically in a visual flowchart. For example, a tree might show: Gross Margin = Revenue - Cost of Goods Sold. Where Revenue = Volume * Price.
Nodes in the tree represent measures and dimensions from your planning model.
Simulation & What-If Analysis
The primary use case for a VDT is rapid simulation. In an SAC Story, a user can interact with the VDT directly:
- Change the "Price" node by +5%.
- The VDT instantly calculates the ripple effect through the tree, updating Revenue and ultimately Gross Margin.
- This creates a Private Version, allowing the user to simulate multiple "what-if" scenarios (e.g., Best Case vs. Worst Case) before finalizing the plan.
YOY Nodes: VDTs support special Year-Over-Year nodes that automatically handle time-based calculations, making it easy to project growth based on historical trends without complex formulas.
Augmented Analytics
Smart Predict & Insights
SAC integrates machine learning directly into the workflow, empowering business users to leverage data science without writing code.
Smart Predict
Smart Predict creates dedicated predictive scenarios. It automatically tests multiple ML algorithms behind the scenes and selects the most accurate one for your dataset.
| Model Type | Use Case |
| Time Series Forecasting | Predicting future numeric values based on historical trends (e.g., forecasting next quarter's sales volume). Output can be written back into a planning model. |
| Classification | Predicting a binary outcome or category (e.g., Will this customer churn? Yes/No). |
| Regression | Predicting a continuous numeric value based on various independent drivers (e.g., Predicting the maintenance cost of a machine based on age, usage, and temperature). |
Smart Insights
Smart Insights works directly within a story. By clicking the "lightbulb" icon on a data point (e.g., a dip in Q2 Revenue), SAC analyzes the underlying data and generates natural language explanations and charts highlighting the top contributors to that value (e.g., "Revenue is down because Product X sales dropped 40% in Germany").
Smart Discovery
Smart Discovery automates dashboard creation. You select a target measure (e.g., Profit), and SAC runs a machine learning algorithm against the entire model to discover key influencers, outliers, and patterns. It then automatically generates a multi-page story visualizing these findings.
Administration
Security & Teams
SAC employs a robust security model combining Roles, Folders, and Data Access Controls to ensure users only see what they are authorized to see.
Folder & Object Level Security
Stories, Models, and files are organized into Folders. Access rights (View, Edit, Delete, Share) are applied to these folders. Users or Teams are granted access to the folders, inheriting the permissions for the objects inside.
Teams
Instead of assigning roles and folder access to individual users, best practice is to use Teams (e.g., "Finance Planners US"). When a new employee joins, you simply add them to the Team, and they inherit all necessary roles and folder access.
Data Access Control (DAC)
While folder security controls access to the Story, Data Access Control restricts access to the rows of data within the model.
- Enabled at the Dimension level (e.g., turning on DAC for the 'Region' dimension).
- You map users or teams to specific dimension members (e.g., User A can only see data where Region = 'North America').
- When User A opens a story, the data is automatically filtered to their authorized regions.
Live Connection Security: If you are using a Live Connection (e.g., to HANA or BW), SAC's internal DAC is usually bypassed. The data security is handled entirely by the backend system's authorizations.
Administration
Lifecycle Management
Lifecycle Management (Transporting) is the process of moving content (Models, Stories, Connections) between different SAC environments (e.g., Dev > QA > Prod).
Content Network
The Content Network is SAC's internal mechanism for transporting objects.
1
Export (Dev)
An admin bundles the Story, its underlying Model, and necessary Dimensions into an Export Package.
2
Transport
The package is published to the Content Network, making it visible to linked tenant systems.
3
Import (Prod)
An admin in the Production tenant selects the package and imports it. SAC handles object ID mapping and dependency resolution.
SAP Business Content
The Content Network is also where customers can download SAP Standard Business Content. These are free, pre-built packages created by SAP for specific industries (e.g., Retail, Banking) or Lines of Business (e.g., HR, Finance, S/4HANA integrations). They provide best-practice models, stories, and data actions out-of-the-box, significantly accelerating implementation time.