Objective
SAP Analytics Cloud combines Business Intelligence, augmented and predictive analytics, and enterprise planning capabilities in one product, giving you the capability you need in order to make fast, confident decisions. To do this, you create stories in SAP Analytics Cloud that are based on data found in live or import models.
Analytic models are read-only models used strictly for data reporting and analysis. They do not have any required dimensions or measures.
Unlike the read-only analytic models, planning models allow write-back to the planning data source. Because designated planners can write data, planning models require Version and Date dimensions to designate what the written data is, and for what time frame.
In a typical workflow, the structure of the planning model is created and then actual data is imported. The actual data is typically copied to a plan version and then the data is adjusted to accommodate expected changes in the planning time frame.
Both analytic and planning models can be created as either account-based or measure-based models.
Note
A planning model integrated with SAP BPC Embedded can work with real-time (non-imported) data, but that is the only exception. Any other planning model must replicate the data into SAP Analytics Cloud.Version dimension within the model supports the creation of new (empty) versions and the deletion of existing (empty) versions. This helps to improve the administration of data versions for planning and analytics scenarios.
The measure-based model type exposes measures as single entities and lets you add and configure multiple measures with aggregation and units to fit your data. It provides plenty of flexibility; you can match the structure of an account-based model by using measures and an account dimension, or you can remove the account dimension when it is not required for your use case.
There are two types of measure-based models:
Model with Measures Only:
Model with Measures and an Account Dimension:
The measure-based model is a best of both worlds. It has multiple measures but can also use an account-type dimension. In addition, measure-based models support model-specific calculated and converted measures.
Account-based models have a single measure associated with multiple accounts.
In an account-based model, model values are stored in a single default measure, and you use the account-type dimension's structure to add calculations, specify units, set up an account hierarchy, and set aggregation types for all the data. In the preceding figure, data is broken down by Account (Discounts, Gross Sales, Quantity, and Cost of Sales), which is used to describe the values in the measure column (SignedData.) Those values represent transaction data associated with other dimensions (Product and Date).
| Feature | Account-Based Model | Measure-Based Model |
|---|---|---|
| Measures | 1 | 1 or more |
| Converted measures | Not available | Supported |
| Calculated measures | Not available | Supported |
| Account dimension | Required | Optional |
| Analytic or planning | Both | Both |
Watch this short video scenario on measure-based and account-based models. Can you help Peter with his question?
Log in to track your progress & complete quizzes