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

Use the Semantic Usage property to indicate the type of data contained in your entity:
  • 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

Facts are entities that contain numerical measures that can be analyzed and are the principal type of object that is consumed by BI clients (see Create a Fact to Contain Measurable Data).

Prepare Master Data for Grouping in a Dimension

Dimensions are entities that contain master data that categorize and group the numerical data contained in your measures (see Create a Dimension to Categorize Data).

Support Translations of Attributes with a Text Entity

Text entities are entities that contain data to store strings in multiple languages for translating attributes in other entities (see Create a Text Entity for Attribute Translation).
  • 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

External hierarchies are entities that contain data to define parent-child relationships for a dimension (see Create an External Hierarchy for Drill-Down).
  • 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

Once your fact is ready for use, create an analytic model from it to consume its data in SAP Analytics Cloud (see Creating 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

You can alternatively use the objects in the Business Builder to model and expose your data:
  • 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

Data can be exposed as analytic models, perspectives, and views, which are accessible to clients, tools, and apps as follows:

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).