Modeling Data
Users with a modeler role can add semantic information to their entities and combine, refine, and enrich them in tightly-focused analytic models for consumption in SAP Analytics Cloud, Microsoft Excel, and other clients, apps, and tools.
Model Facts, Dimensions, Texts, and Hierarchies
-
Select a Semantic Usage of Fact to indicate that your entity contains numerical measures that can be analyzed.
In our example, Acme Sales View is a fact containing sales data.
-
Select a Semantic Usage of Dimension to indicate that your entity contains attributes that can be used to analyze and categorize measures defined in other entities.
In our example, four dimensions surround the fact, allowing us to analyze it by Salespeople, Time, Product, and Geo attributes.
-
Select a Semantic Usage of Text to indicate that your entity contains strings with language identifiers to translate text attributes in other entities.
In our example, there are four translation entities to translate time and product dimension attributes.
-
Select a Semantic Usage of Hierarchy to indicate that your entity contains parent-child relationships for members in a dimension.
In our example, the Acme Salespeople Hierarchy provides a hierarchy for the Salespeople dimension.
Identify Measures to Analyze in a Fact
-
To get started: Select a Semantic Usage of Fact to indicate that your entity contains numerical measures that can be analyzed.
-
You must identify at least one measure (see Specify Measures to Analyze).
-
You can create associations to dimensions and text entities (see Create an Association to Define a Semantic Relationship Between Entities).
-
To expose your data for consumption in SAP Analytics Cloud, add it to an analytic model (see Creating an Analytic Model).
Prepare Master Data for Grouping in a Dimension
-
To get started: Select a Semantic Usage of Dimension to indicate that your entity contains attributes that can be used to analyze and categorize measures defined in other entities.
-
You must set at least one key column (see Set Key Columns to Uniquely Identify Records).
-
You can create associations to other dimensions, text entities, and hierarchies (see Create an Association to Define a Semantic Relationship Between Entities).
-
You can add parent-child or level-based hierarchies to support drill-down (see Add a Hierarchy to a Dimension).
-
You can make your dimension time-dependent, so that its members can change over time (see Enable Time-Dependency for a Dimension or Text Entity).
Support Translations of Attributes with a Text Entity
-
To get started: Select a Semantic Usage of Text to indicate that your entity contains strings with language identifiers to translate text attributes in other entities.
-
You must specify attributes and keys to uniquely identify a master data member and a language.
-
You can make your text entity time-dependent, so that the texts it contains can change over time (see Enable Time-Dependency for a Dimension or Text Entity).
Enable Drill-Down with a Hierarchy
-
To get started: Select a Semantic Usage of Hierarchy to indicate that your entity contains parent-child relationships for members in a dimension.
-
You must specify the parent and child attributes and set the child attribute as a key.
Create Heterogeneous Hierarchies with a Hierarchy with Directory
A hierarchy with directory is an entity that contains one or more parent-child hierarchies and has an association to a directory dimension containing a list of the hierarchies. These types of hierarchy entities can include nodes from multiple dimensions (for example, country, cost center group, and cost center) and are commonly imported from SAP S/4HANA Cloud and SAP BW systems (see Create a Hierarchy with Directory).
Combine Entities for Consumption in an Analytic Model
-
To get started: In the side navigation area, select (Data Builder), select a space if necessary, and select New Analytic Model to open the editor.
-
You must add a fact as a source and can choose to copy all its measures, attributes and associated dimensions to the analytic model (see Add a Fact to an Analytic Model).
-
You can deselect measures and attributes to leave only those that are relevant to answer your particular analytic question.
-
You can create additional calculated and restricted measures (see Create a Measure in an Analytic Model).
-
You can create multiple tightly-focused analytic models from a single fact, each providing only the data needed for a particular BI context, and enriched with appropriate variables, filters, and additional measures as necessary.
Modeling Data in the Business Builder
-
Business entities - Are loosely coupled to, and consume data, from Data Builder entities. You can, at any time, switch the data source of a business entity to a different Data Builder entity to maintain stable business entities for reporting, even as your physical data sources change. See Creating a Business Entity.
-
Consumption models combine your business entities into star schemas to prepare them for consumption. See Creating a Consumption Model.
-
Perspectives provide tightly-focused, lightweight data for exposure to SAP Analytics Cloud and other BI clients, MS Excel, and other apps and tools (see Define Perspectives).
Expose Data Outside SAP Datasphere
|
Object |
SAP Analytics Cloud |
Microsoft Excel |
Other Clients, Tools, and Apps |
|---|---|---|---|
|
Analytic models (see Creating an Analytic Model) Exposed: Automatically |
Live Connection |
Live Connection (via an SAP Add-In) |
OData |
|
Perspectives (see Define Perspectives) Exposed: Automatically |
Live Connection |
Live Connection (via an SAP Add-In) |
- |
|
Views* (see Exposing Data For Consumption) Exposed: When the Expose for Consumption switch is enabled |
OData** |
- |
OData ODBC/JDBC |
|
For more information, see: |
* The workflow of consuming views with a semantic usage of Analytical Dataset in SAP Analytics Cloud and Microsoft Excel via live connection is now deprecated. We recommend that you migrate your analytical datasets to the new Fact semantic usage and expose your view data via analytic models (see Analytical Datasets (Deprecated)).
** SAP Analytics Cloud primarily uses the consumption of view data via OData for planning (see Integrate with SAP Analytics Cloud for Planning).