SACM21

SAP Analytics Cloud: Modeling and

Data Transformation

.
.
PARTICIPANT HANDBOOK
INSTRUCTOR-LED TRAINING
.
Course Version: 41
Course Duration: 2 Days
SAP Copyrights, Trademarks and
Disclaimers

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see https://www.sap.com/corporate/en/legal/copyright.html for additional
trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials may have been machine translated and may contain grammatical errors or
inaccuracies.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only,
without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate
company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an
additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business
outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’
strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any
reason without notice. The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking statements are subject to
various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making purchasing decisions.

© Copyright. All rights reserved. iii

Typographic Conventions

American English is the standard used in this handbook.

The following typographic conventions are also used.

This information is displayed in the instructor’s presentation

Demonstration

Procedure

Warning or Caution

Hint

Related or Additional Information

Facilitated Discussion

User interface control Example text

Window title Example text

iv © Copyright. All rights reserved.

Contents

vii Course Overview

1 Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

3 Lesson: Describing Data Modeling Basics

5 Lesson: Identifying the Differences Between Model Types
9 Lesson: Explaining Where the Data Comes From
13 Lesson: Creating Datasets

21 Unit 2: Designing and Creating Dimensions

23 Lesson: Defining Dimensions

27 Lesson: Identifying Dimension Types
31 Lesson: Describing Properties
35 Lesson: Designing and Creating Hierarchies
39 Lesson: Importing and Preparing Master Data for a Dimension

51 Unit 3: Creating Import Models

53 Lesson: Creating an Import Model

59 Lesson: Importing and Preparing Transaction Data in a Model
69 Lesson: Scheduling Data Imports
71 Lesson: Creating Formulas and Calculations
75 Lesson: Translating Currency
81 Lesson: Designing and Creating Time Hierarchies

91 Unit 4: Working With Live Models

93 Lesson: Using Data Analyzer to Preview Your Live Data Structure

95 Lesson: Creating Live Models
101 Lesson: Working with SAP Datasphere

111 Unit 5: Working with Geographic Data

113 Lesson: Configuring Geographic Data in a Model

119 Unit 6: Defining Data Security

121 Lesson: Defining Data Access

© Copyright. All rights reserved. v

vi © Copyright. All rights reserved.
Course Overview

TARGET AUDIENCE
This course is intended for the following audiences:
● Data Manager
● Data Consultant
● Industry / Business Analyst Consultant
● Database Administrator
● System Architect

© Copyright. All rights reserved. vii

viii © Copyright. All rights reserved.
 UNIT 1 Explaining the Basics of Data
Structures in SAP Analytics
Cloud

Lesson 1
Describing Data Modeling Basics 3

Lesson 2
Identifying the Differences Between Model Types 5

Lesson 3
Explaining Where the Data Comes From 9

Lesson 4
Creating Datasets 13

UNIT OBJECTIVES

● Describe the foundational concepts for data modeling.

● Identify the different model types.
● Describe the data source options.
● Explain the types of datasets and the difference between datasets and models.
● Create a dataset.

© Copyright. All rights reserved. 1

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

2 © Copyright. All rights reserved.

 Unit 1
Lesson 1
Describing Data Modeling Basics

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe the foundational concepts for data modeling.

SAP Analytics Cloud Modeling

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 need information from SAP Analytics Cloud
stories that are based on real time or import models. You can use pre-defined Business
Content or you can create your own, but in order to so, you need modeling skills.

Figure 1: SAP Analytics Cloud Modeler

LESSON SUMMARY
You should now be able to:
● Describe the foundational concepts for data modeling.

© Copyright. All rights reserved. 3

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

4 © Copyright. All rights reserved.

 Unit 1
Lesson 2
Identifying the Differences Between Model
Types

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Identify the different model types.

Analytic Models
Analytic models are read-only models used strictly for data reporting and analysis. They do
not have any required dimensions or measures.

Figure 2: Planning Disabled in the Model

Planning Models
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.

Figure 3: Planning Enabled in the Model

© Copyright. All rights reserved. 5

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

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

Measure-Based Models
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 and no account dimension
● Model with measures and an account dimension

Figure 4: Model with Measures Only

Figure 5: 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.

6 © Copyright. All rights reserved.

 Lesson: Identifying the Differences Between Model Types

Account-Based Models
Account-based models have a single measure associated with multiple accounts.

Figure 6: Data Table for an Account-Based Model

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

Table 1: Model Comparison

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

LESSON SUMMARY
You should now be able to:
● Identify the different model types.

© Copyright. All rights reserved. 7

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

8 © Copyright. All rights reserved.

 Unit 1
Lesson 3
Explaining Where the Data Comes From

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Describe the data source options.

Connection Types
SAP Analytics Cloud enables access to both on-premise and cloud data sources via either live
or import connectivity – two ways of accessing your data located anywhere in your
information-system landscape.
Depending on your environment, there are different requirements for establishing live and
import data connections to SAP Analytics Cloud. For more information, see the System
Requirements and Technical Prerequisites Guide
You must decide which connection type your organization needs, based on your user
requirements. As you evaluate which connection type to use, consider the following criteria:
● Functional needs
● Data privacy constraints
● Data volume constraints

It is possible that you will need a combination of both live and import connections, and SAP
Analytics Cloud makes satisfying that requirement very easy to support and manage.

Connection Screen
On the Connection screen, an administrator creates and maintains data source system
connections. Connections are categorized as either a live connection or an acquired data
connection. It is also possible to filter the list of available connections by data source type or
by category.
The following figure shows the connection screen in SAP Analytics Cloud.

© Copyright. All rights reserved. 9

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

Figure 7: Connection Creation in SAP Analytics Cloud

Live Data
You can create models from data sources in on-premise or cloud systems without any data
replication. Live data models do not support any data transformations or model-based
calculations. However, creating calculations in a story that uses a live model is possible. Live
models are typically used when:
● You need data in a story that is real-time.
● You do not need to transform or calculate the data in SAP Analytics Cloud.
● You cannot have data on the cloud due to security or privacy considerations.

Data access for the model is controlled by the source system security, not SAP Analytics
Cloud security.
Currently, the data sources for live models are limited to SAP systems and include:
● SAP BPC Embedded - Connect to a configuration model.
● SAP BW - Connect to a BW query.
● SAP HANA - Connect to a HANA view.
● SAP S/4HANA - Connect to a query or CDS view.
● SAP Universe or WebI document - Create a universe query or connect to an existing Web
Intelligence document.

10 © Copyright. All rights reserved.

 Lesson: Explaining Where the Data Comes From

Figure 8: Live Model Data Sources

Acquired Data
As with live models, you can create models from data sources in on-premise or cloud
systems; however, with acquired data, the data is imported (copied) to SAP Analytics Cloud
from the source system. This replication allows the imported data to be transformed/
manipulated and/or additional calculations created. Import models are typically used when:
● Data in stories does not need to be real-time.
● Source system performance issues preclude the use of live models.
● You need to transform data.
● You need to combine data from multiple source systems.
● You need model-dependent calculated measures.
● You need to submit planning data.

One very important consideration is that changes made to the data in the source system do
not affect the imported data. Because of this fact, imports from sources systems can be, and
typically are, scheduled to occur on a regular basis. However, if data is imported from a file
into a model, the import cannot be scheduled.
Data access for the model is controlled by SAP Analytics Cloud security.
There are many data sources for imported models, both SAP and non-SAP.

© Copyright. All rights reserved. 11

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

Figure 9: Import Data Connections

LESSON SUMMARY
You should now be able to:
● Describe the data source options.

12 © Copyright. All rights reserved.

 Unit 1
Lesson 4
Creating Datasets

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the types of datasets and the difference between datasets and models.
● Create a dataset.

Datasets
A dataset is a simple collection of data, usually presented in a table. You can use a dataset as
the basis for your story, and as a data source for Smart Predict. Datasets are a good choice
when you want to create stories quickly and do not want to get into structure definition or
when development does not demand IT governance.
For the most part, datasets acquire data via import connections. The only exception is that a
dataset can be built based on a live connection to a HANA data repository.

Public and Embedded Datasets

Access the Datasets menu option from the SAP Analytics Cloud navigation bar. From there,
you can create public datasets based on a file or an import data source.

Figure 10: Create Datasets

Public Datasets
Public datasets are data sources that can be used in multiple stories by any users who have
access to them. They can be created directly from the vertical toolbar and can also be used
for Smart Predict.

© Copyright. All rights reserved. 13

Unit 1: Explaining the Basics of Data Structures in SAP Analytics Cloud

Embedded Datasets
Embedded datasets are created in and exist in only a single story, and cannot be shared or
used in other stories or with Smart Predict. However, if you need others to be able to use this
dataset, you can convert it to a public dataset.

Note:
A shareable live dataset can be created for SAP HANA. Live datasets can also be
created from a story based on SAP Datasphere.

Datasets are intended to supplement models and be used only for ad-hoc, ungoverned data
analysis.

Table 2: Datasets versus Models

Characteristics Datasets Live Models Import Models
Purpose Ad-hoc/Smart pre- Planning (BPC Em- Planning and Analysis
dict bedded only)
Scheduled imports No No Yes
available
Public or embedded Both Public Public
Table 1 data table Dimensions and data Dimensions and data
tables tables
Calculated measures No No Yes
Data Security in SAP No No Yes
Anlaytics Cloud

LESSON SUMMARY
You should now be able to:
● Explain the types of datasets and the difference between datasets and models.
● Create a dataset.

14 © Copyright. All rights reserved.

 Unit 1

Learning Assessment

1. From where can stories access data?

Choose the correct answers.

X A InfoCubes

X B Import models

X C Datasets

X D Universes

X E Calculation Views

2. The account-based model only has one measure.

Determine whether this statement is true or false.

X True

X False

3. A planning model requires which dimensions?

Choose the correct answers.

X A Version

X B Organization

X C Generic

X D Date

4. The account-based model does not support:

Choose the correct answers.

X A Calculated measures

X B Story calculations

X C Converted measures

X D Table formulas

© Copyright. All rights reserved. 15

Unit 1: Learning Assessment

5. How many measures can you have in a measure-based model?

Choose the correct answer.

X A One

X B Unlimited

X C No more than five

6. Models always contain data.

Determine whether this statement is true or false.

X True

X False

7. In a live model, where is data access controlled?

Choose the correct answer.

X A The source system

X B The model

X C SAP Analytics Cloud

8. What supports scheduled data uploads?

Choose the correct answer.

X A Data set

X B Live model

X C Import model

9. Embedded datasets are user-specific.

Determine whether this statement is true or false.

X True

X False

16 © Copyright. All rights reserved.

 Unit 1

Learning Assessment - Answers

1. From where can stories access data?

Choose the correct answers.

X A InfoCubes

X B Import models

X C Datasets

X D Universes

X E Calculation Views

Stories access data from datasets, import models, and live data models.

2. The account-based model only has one measure.

Determine whether this statement is true or false.

X True

X False

A typical account-based model only has one measure.

3. A planning model requires which dimensions?

Choose the correct answers.

X A Version

X B Organization

X C Generic

X D Date

A planning model requires Version and Date dimensions.

© Copyright. All rights reserved. 17

Unit 1: Learning Assessment - Answers

4. The account-based model does not support:

Choose the correct answers.

X A Calculated measures

X B Story calculations

X C Converted measures

X D Table formulas

You cannot create calculated measures or converted measures in an account-based

model.

5. How many measures can you have in a measure-based model?

Choose the correct answer.

X A One

X B Unlimited

X C No more than five

You can have as many measures as you need in a measure-based model.

6. Models always contain data.

Determine whether this statement is true or false.

X True

X False

Live models do not contain data.

7. In a live model, where is data access controlled?

Choose the correct answer.

X A The source system

X B The model

X C SAP Analytics Cloud

In a live model, data access is controlled in the source system for the model.

18 © Copyright. All rights reserved.

 Unit 1: Learning Assessment - Answers

8. What supports scheduled data uploads?

Choose the correct answer.

X A Data set

X B Live model

X C Import model

Only import models support scheduled data uploads.

9. Embedded datasets are user-specific.

Determine whether this statement is true or false.

X True

X False

Embedded datasets are story specific.

© Copyright. All rights reserved. 19

Unit 1: Learning Assessment - Answers

20 © Copyright. All rights reserved.

 UNIT 2 Designing and Creating
Dimensions

Lesson 1
Defining Dimensions 23

Lesson 2
Identifying Dimension Types 27

Lesson 3
Describing Properties 31

Lesson 4
Designing and Creating Hierarchies 35

Lesson 5
Importing and Preparing Master Data for a Dimension 39

UNIT OBJECTIVES

● Explain the difference between dimensions and measures, and private and public
dimensions.
● Explain account, organization, generic, data and version data types.
● Explain the unique properties for dimension types.
● Explain the prerequisites required for creating hierarchies.
● Create a dimension and hierarchy.
● Import and prepare data in a dimension.

© Copyright. All rights reserved. 21

Unit 2: Designing and Creating Dimensions

22 © Copyright. All rights reserved.

 Unit 2
Lesson 1
Defining Dimensions

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the difference between dimensions and measures, and private and public
dimensions.

Dimensions and Measures

In SAP Analytics Cloud, dimensions usually represent qualitative master data. Product, cost
center, and employee are all examples of dimensions. A model can, and typically does, have
several dimensions.
A measure represents transactional or quantitative data; for example, price, revenue, number
of customers. Measures are distinct from dimensions, so you can add and configure multiple
measures with aggregation and units to fit your data.
In an account-based model, all the numeric values are stored in a single default dimension
usually named Account, and you use the financial account structure to determine what each
value represents. You can also add calculations, specify units, and set aggregation types for
those values. Semantically, an Account dimension type may be referred to as a measure
because it fulfills a similar purpose; however, it is really a dimension.

Figure 11: Data in a Model

Note:
A measure-based model also supports the account-based single measure
dimension, but you can add other measures to the model as well. With the
account-based model, you are limited to the single account-type dimension to
represent measures.

Private and Public Dimensions

Dimensions can be private or public.

© Copyright. All rights reserved. 23

Unit 2: Designing and Creating Dimensions

Public Dimensions
Public dimensions are stand-alone entities that are created independently and can be shared
among multiple models. If a model that contains a public dimension is deleted, the public
dimension remains intact because it is not dependent on the model. If you copy a model that
contains public dimensions, those dimensions are not duplicated, again, because they are not
dependent on the model.
Typically, the values for the dimension members are imported into the dimension. Because
the data is imported, it is often scheduled to repeat the import process on a regular basis to
ensure that the dimension always reflect accurate information.

Private Dimensions
Private dimensions are created directly in a model, so they are model-specific and cannot be
shared among other models. If the model containing the private dimension is deleted, the
dimension is also deleted because it is part of the model. The same is true if you copy the
model; the private dimension is duplicated in the copy.
Since the dimension is created during the model creation process, the data values for the
dimension members are not populated until the data for the entire model structure is
imported into it. And while data imports into models can be scheduled, the private dimension
cannot be singled out for its own scheduled import.

When to Use Public and Private Dimensions

Public dimensions are used much more frequently in SAP Analytics Cloud modeling than
private dimensions simply because of their versatility. As independent entities, they can be
managed and used much more easily than private dimensions.
Private dimensions, however, are excellent choices for single- or infrequent-use situations.

Figure 12: Public versus Private Dimension Creation

24 © Copyright. All rights reserved.

 Lesson: Defining Dimensions

LESSON SUMMARY
You should now be able to:
● Explain the difference between dimensions and measures, and private and public
dimensions.

© Copyright. All rights reserved. 25

Unit 2: Designing and Creating Dimensions

26 © Copyright. All rights reserved.

 Unit 2
Lesson 2
Identifying Dimension Types

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain account, organization, generic, data and version data types.

Dimension Types
Dimensions are always qualified as a specific type. This Type qualification gives SAP Analytics
Cloud information on how the dimension should function within the system. Depending on the
type selected, you can configure various properties and possibly create hierarchies for the
dimension.

Figure 13: Dimension Types

When creating a public dimension, you can select the Generic, Organization, or Account type.
There are two other dimension types required by planning models that the system creates
automatically for every planning model: Version and Date.

Organization Dimension Type

The Organization dimension type represents an organizational structure, such as Cost
Centers, Profit Centers, or Business Units.
Pertinent Information
● Properties: Currency and Person Responsible are system-generated, and more can be
added
● Hierarchies: as many as needed
● Optional in a model

© Copyright. All rights reserved. 27

Unit 2: Designing and Creating Dimensions

● Only one per model

Account Dimension Type

The Account dimension type typically conforms to financial-type accounts or accounting-
related data such as utility costs or number of product returns.
Pertinent Information
● Properties: There are several system-generated properties, and more can be added
● Hierarchies: The default hierarchy is system generated, and more can be added
● Mandatory in an account-based model but optional in a measure-based model
● Only one per model

Version Dimension Type

The Version dimension type is system-generated for all planning models and defines the data
versions for planning activities: Planning, Actual, Forecast, etc.
Pertinent Information
● Properties: added as needed
● Hierarchies: Not Applicable
● Mandatory (system-generated) in all planning models; not applicable for analytic models
● Only one per model

Date Dimension Type

The Date dimension type is a system-generated dimension that defines the start and end
dates of the model's time frame and specifies the granularity of time used in the model (years,
quarters, months, weeks, or days).
Pertinent Information
● Properties:
- Account-based model: system-generated only
- Measure-based model: added as needed, but only when user-managed
● Hierarchies:
- Account-based model: system-generated only based on calendar time but can be
changed to fiscal time
- Measure-based model: added as needed, but only when user-managed
● Mandatory (system-generated) in all planning models; optional for analytic models
● More than one per model allowed, helpful if you need to compare dates for different
scenarios, such as Order Date versus Shipping Date
● New model only:
- 4-4-5 | 4-5-4 | 5-4-4 | 13x4 week patterns available
- 53 week support

28 © Copyright. All rights reserved.

 Lesson: Identifying Dimension Types

Generic Dimension Type

The Generic dimension type is used for any data that logically cannot be qualified as any other
dimension type. You can also use the Generic dimension type if you need more than one of the
other dimensions types in your model. For example, your model may need multiple
dimensions related to an organizational structure, but since a model can have only one
Organization dimension type, all the other organization-related dimensions can be qualified as
Generic.
Pertinent Information
● Properties: added as needed
● Hierarchies: as many as needed
● Optional in a model
● More than one per model allowed

LESSON SUMMARY
You should now be able to:
● Explain account, organization, generic, data and version data types.

© Copyright. All rights reserved. 29

Unit 2: Designing and Creating Dimensions

30 © Copyright. All rights reserved.

 Unit 2
Lesson 3
Describing Properties

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the unique properties for dimension types.

Dimension Properties
Dimension properties have many uses in SAP Analytics Cloud. In stories, they can be used to
sort and filter data or for currency translation calculations. They can also be displayed to
provide additional information or clarity to the story.
The following example displays the Stores dimension with its properties.

Figure 14: Examples of Dimension Properties

Unique Properties for Dimension Types

Each dimension type has unique properties that are system-generated, and depending on the
dimension type, you can easily add as many custom properties as you need.
The following example displays properties for the Organization and Account dimension types.

© Copyright. All rights reserved. 31

Unit 2: Designing and Creating Dimensions

Figure 15: Organization and Account Properties

Note:
Member ID, Description, and Hierarchy appear as a columns in the member sheet,
but they are not properties.

Organization Dimension Type

The following properties are system-generated:
● Currency
● Person Responsible

These properties are used for currency conversion, data access control, data locking
ownership, and to hide unauthorized hierarchy nodes.

Account Dimension Type

The following properties are system-generated:
● Formula - used to calculate values such as Gross Margin %
● Account Type - used to allow sign reversal from positive to negative
● Calculated On
● Aggregation Type*
● Exception Aggregation*
● Scale
● Decimal Places
● Units and Currencies
● Hide

These properties are used for currency conversion, data access control, data locking
ownership, and to hide unauthorized hierarchy nodes.

32 © Copyright. All rights reserved.

 Lesson: Describing Properties

Note:
* There are many aggregation types available in SAP Analytics Cloud: average,
last, first, rank, sum, etc. Aggregation behavior can be specified in account
dimensions, calculated measures in stories, as well as a measure-based model.

Version Dimension Type

The Category property is system-generated.
This property is used for data access control and data locking ownership.

Date Dimension Type

There are many system-generated properties related to time such as Day, Week, Month, Day
Name, and more.
These properties are used for time hierarchies and data mapping.

Generic Dimension Type

There are no system-generated properties, but you can add any that you need, and they can
be used for currency conversion, data access control, data locking ownership, and to hide
unauthorized hierarchy nodes.

LESSON SUMMARY
You should now be able to:
● Explain the unique properties for dimension types.

© Copyright. All rights reserved. 33

Unit 2: Designing and Creating Dimensions

34 © Copyright. All rights reserved.

 Unit 2
Lesson 4
Designing and Creating Hierarchies

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the prerequisites required for creating hierarchies.
● Create a dimension and hierarchy.

Hierarchies
A hierarchy is used to establish parent-child relationships within your data. For example,
suppose you have sales data for the following:
● Worldwide
● Region
● Country
● State/Province
● City

A hierarchy allows you to organize these geographic areas into logical levels (also called
nodes), from the largest area to the most granular.
The hierarchy column in a dimension is used to store the parent-child values. You can add
hierarchies by selecting +Add Hierarchy on the toolbar. When you choose this option, a new
hierarchy column is inserted into the dimension, and you must enter the name of the new
hierarchy.
The hierarchy is visualized in the Preview panel in the dimension. You can use drag-and-drop
in the Preview panel to arrange the members and build the relationships. If more than one
hierarchy has been defined, you can select the one you want to display in the preview from the
drop-down list.

General Information about Hierarchies

Dimension types that allow more than one hierarchy can have either one or more level-based
hierarchies or one or more parent-child hierarchies, but not a combination of both.
In an account-based model, the Account dimension type has only one system-generated
parent-child hierarchy, but in a measure-based model, multiple account hierarchies are
allowed.
For the Date dimension type, hierarchies are predefined based on the model granularity, and
whether you have enabled fiscal time for the model. You can specify a default hierarchy in the
settings for the date dimension. In a measure-based model, additional custom hierarchies
may be added. We will cover custom time hierarchies in more detail later in the course.

© Copyright. All rights reserved. 35

Unit 2: Designing and Creating Dimensions

The Version dimension type does not have a hierarchy, because different versions are
independent from one another and do not have parent-child relationships.

Types of Hierarchies
Two types of hierarchy are available:

1. Level-based hierarchy: A level-based hierarchy organizes multiple dimensions or

properties into levels, such as country, state, and city.

2. Parent-child hierarchy: A parent-child hierarchy organizes the members of a single

dimension into a set of parent-child relationships.

Level-based hierarchy
The following figure shows dimensions with a level-based hierarchy.

Figure 16: Example of a level-based hierarchy

Parent-child hierarchy
The following figure shows dimensions with a parent-child hierarchy.

36 © Copyright. All rights reserved.

 Lesson: Designing and Creating Hierarchies

Figure 17: Example of a parent-child hierarchy

Parent-child hierarchies can be maintained manually in SAP Analytics Cloud or imported from
files or SAP systems.

Note:
When working with parent-child hierarchies for a planning model, avoid situations
where data can be booked directly to a parent node.
These situations include the following:
● Structuring two or more hierarchies so that a member is a leaf node in one
hierarchy and a parent node in a different hierarchy.
● Updating a hierarchy so that a leaf node that has a value booked to it is
changed to a parent node.

LESSON SUMMARY
You should now be able to:
● Explain the prerequisites required for creating hierarchies.
● Create a dimension and hierarchy.

© Copyright. All rights reserved. 37

Unit 2: Designing and Creating Dimensions

38 © Copyright. All rights reserved.

 Unit 2
Lesson 5
Importing and Preparing Master Data for a
Dimension

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Import and prepare data in a dimension.

Import Master Data

Master data can be imported from SAP source systems or files, including the member IDs,
descriptions, hierarchies, and properties. Data can also be imported from non-SAP systems.
The following example shows the process of importing master data into three different public
dimensions.

Figure 18: Import Data into Dimensions

Prepare Master Data

Sometimes you may need to change the master data before importing it into your dimension.
The data preparation area allows you to view the data and perform any necessary
transformations.

© Copyright. All rights reserved. 39

Unit 2: Designing and Creating Dimensions

Figure 19: Data Wrangling Area for Master Data

For example, you may need to concatenate columns when dimension members are non-
unique, such as the same city name used in multiple states. In this situation, concatenating
City and State creates a single, more meaningful dimension.

Smart Transformations
The Smart Transformations list suggested transformations to apply to the column, such as
replacing the value in a cell with a suggested value. There are many transformation options,
including but not limited to:
● Trim White Space: Remove spaces, including non-printing characters, from the start and
end of strings.
● Duplicate Column: Create a copy of an existing column.
● Concatenate: Combine two or more columns into one. An optional value can be entered to
separate the column values.
● Split: Split a text column on a chosen delimiter, starting from left to right. The number of
splits can be chosen by the user.
● Change: Change a column to uppercase, lowercase, or title case.

Custom Expression Editor

You can also use the custom expression editor to use more complex logic for your
transformations. The custom expression editor features include:
● The ability to create formulas to perform more complicated transformations.
● Being available for new model and dataset imports.
● Auto-complete and in-line help while writing the expression.

The figure Smart Transformations and Custom Expression Editor Examples shows examples
of each transformation option.

40 © Copyright. All rights reserved.

 Lesson: Importing and Preparing Master Data for a Dimension

Figure 20: Smart Transformations and Custom Expression Editor Examples

Import Master Data - Summary

File Data Source SAP Source System

Go to Data Management. Go to Data Management.
Choose Import Data → File. Choose Import Data → Data Source.
Select the source file. Select the Source System and Connection.
Wrangle the data if needed. Choose the Source System source.
Map the file columns to the dimension col- Select the fields to be imported.
umns.
Run the import then read the log. Add filters if needed.
If records fail, debug and re-import. Wrangle the data if needed.
In order to run another import, repeat the Map the source columns to the dimension
process manually. columns.
Run the import then read the log.
If records fail, debug and re-import.
In order to run another import, schedule the
import.

LESSON SUMMARY
You should now be able to:
● Import and prepare data in a dimension.

© Copyright. All rights reserved. 41

Unit 2: Designing and Creating Dimensions

42 © Copyright. All rights reserved.

 Unit 2

Learning Assessment

1. Measure values are stored in models.

Determine whether this statement is true or false.

X True

X False

2. Which are valid dimensions?

Choose the correct answers.

X A Imported

X B Live

X C Public

X D Private

3. Which dimension cannot be shared among models?

Choose the correct answer.

X A Imported

X B Live

X C Public

X D Private

4. You can create public date dimensions.

Determine whether this statement is true or false.

X True

X False

© Copyright. All rights reserved. 43

Unit 2: Learning Assessment

5. What dimension types can you add when you create a model in SAP Analytics Cloud?
Choose the correct answers.

X A Account

X B Version

X C Generic

X D Organization

X E Time

6. A model can contain multiples of which dimension type?

Choose the correct answers.

X A Account

X B Generic

X C Date

X D Version

X E Organization

7. A Person Responsible property can be created in a Generic dimension.

Determine whether this statement is true or false.

X True

X False

8. What is a type of hierarchy?

Choose the correct answers.

X A Level-based

X B Branched tree

X C Parent-Child

X D Star schema

44 © Copyright. All rights reserved.

 Unit 2: Learning Assessment

9. Hierarchies are available in every dimension type.

Determine whether this statement is true or false.

X True

X False

10. Data preparation involves manipulating the data to make it accurate and to match your
business needs.
Determine whether this statement is true or false.

X True

X False

11. You can add calculated columns when importing into a dimension.
Determine whether this statement is true or false.

X True

X False

12. What can you use to prepare master data?

Choose the correct answers.

X A Calculation Editor

X B Custom Expression Editor

X C Smart Transformations

X D Formula Editor

© Copyright. All rights reserved. 45

 Unit 2

Learning Assessment - Answers

1. Measure values are stored in models.

Determine whether this statement is true or false.

X True

X False

Measure values are stored in models.

2. Which are valid dimensions?

Choose the correct answers.

X A Imported

X B Live

X C Public

X D Private

The valid dimensions are Public and Private.

3. Which dimension cannot be shared among models?

Choose the correct answer.

X A Imported

X B Live

X C Public

X D Private

A Private dimension cannot be shared among models because it exists only in the model
where it was created.

46 © Copyright. All rights reserved.

 Unit 2: Learning Assessment - Answers

4. You can create public date dimensions.

Determine whether this statement is true or false.

X True

X False

The system creates date dimensions. They are model-specific.

5. What dimension types can you add when you create a model in SAP Analytics Cloud?
Choose the correct answers.

X A Account

X B Version

X C Generic

X D Organization

X E Time

When creating a model, you can add Account, Generic, Date, and Organization dimension
types. The Version dimension is are added by the system.

6. A model can contain multiples of which dimension type?

Choose the correct answers.

X A Account

X B Generic

X C Date

X D Version

X E Organization

A model can contain multiple Date and Generic dimension types.

7. A Person Responsible property can be created in a Generic dimension.

Determine whether this statement is true or false.

X True

X False

A Person Responsible property can be enabled in a Generic dimension.

© Copyright. All rights reserved. 47

Unit 2: Learning Assessment - Answers

8. What is a type of hierarchy?

Choose the correct answers.

X A Level-based

X B Branched tree

X C Parent-Child

X D Star schema

The types of hierarchies are level-based and parent-child.

9. Hierarchies are available in every dimension type.

Determine whether this statement is true or false.

X True

X False

Hierarchies are not available for the Version dimension type.

10. Data preparation involves manipulating the data to make it accurate and to match your
business needs.
Determine whether this statement is true or false.

X True

X False

Data preparation involves manipulating the data to make it accurate and to match your
business needs.

11. You can add calculated columns when importing into a dimension.
Determine whether this statement is true or false.

X True

X False

You can add calculated columns when importing into a dimension.

48 © Copyright. All rights reserved.

 Unit 2: Learning Assessment - Answers

12. What can you use to prepare master data?

Choose the correct answers.

X A Calculation Editor

X B Custom Expression Editor

X C Smart Transformations

X D Formula Editor

To prepare master data, you can use the Calculation Editor and Smart Transformations.

© Copyright. All rights reserved. 49

Unit 2: Learning Assessment - Answers

50 © Copyright. All rights reserved.

 UNIT 3 Creating Import Models

Lesson 1
Creating an Import Model 53

Lesson 2
Importing and Preparing Transaction Data in a Model 59

Lesson 3
Scheduling Data Imports 69

Lesson 4
Creating Formulas and Calculations 71

Lesson 5
Translating Currency 75

Lesson 6
Designing and Creating Time Hierarchies 81

UNIT OBJECTIVES

● Create an import model.

● Explain data transformation functions in an import model.
● Import data into a model.
● Schedule data import.
● Explain calculations created for import models.
● Create calculated measures in a model.
● Configure and translate currencies.
● Explain the prerequisites required for creating hierarchies.
● Build custom time hierarchies.

© Copyright. All rights reserved. 51

Unit 3: Creating Import Models

52 © Copyright. All rights reserved.

 Unit 3
Lesson 1
Creating an Import Model

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create an import model.

The Basics of Creating an Import Model

Import models include both analytic and planning models. You have two options when
creating import models:
● Start with data

1. Select the import connection to use

2. Select dimensions and measures for the model

3. Prepare and map the data

Note:
All dimensions are private in this case.

● Start with an empty model

1. Add public dimensions

2. Create private dimensions if needed

3. Prepare and map the data

Creating an Import Model

Typically, you will create your import model by choosing the Model option and then selecting
the appropriate way to populate the model with data.

© Copyright. All rights reserved. 53

Unit 3: Creating Import Models

Figure 21: Options to Create Models

If you choose to Start with an empty model, you will follow these basic steps:

1. Add existing public dimensions.

2. Create at least one measure. Currency related measures can either use a default currency
or can be derived from a dimension with the currency property.
When you add a measure to the model, the aggregation type will default to sum. The
exception aggregation type can be used to manipulate aggregation. For example, a
headcount measure could be set to an exception aggregation type of Last and an
exception aggregation dimension of Date so that the model always reflects the headcount
for a specific date, rather than the sum for all time.
In the measure-based model, you can also create calculated measures based on the
existing measures in your model. Measure values are stored in the model; however,
calculated and converted measures are refreshed when used and are not stored.

For either an empty model or starting with data, you will:

1. Set the model preferences if needed, especially to define the model as Planning or not
(Analytic). When you create a blank model, the default is the Planning model type, and
Date and Version dimensions are included by the system. If you turn off the Planning
preference to create an Analytic model, the Version dimension goes away, and the Date
dimension becomes optional.

2. Select the time range. When creating a measure-based model, the default time range is
from the current year to the current year plus one. For example, if the current year is
2024, the default time range will allow data for 2024 and 2025. But you can change the
default range to meet your modeling requirements and match the data you will import into
the model.

3. Save the model. The model is ready for data imports.

54 © Copyright. All rights reserved.

 Lesson: Creating an Import Model

Note:
A typical model has a Date dimension, Organization dimension, several Generic
dimensions, and several Measures. It may also have an Account dimension, but in
the measure-based model, that dimension type is not required.

A Completed Analytic Model

Completed model:

1. Model structure workspace: Where you can view the meta data

2. Measures: Where the measure values are stored in the model

3. Public dimensions: Represented by a globe icon

Model Preferences
Preferences are set by default when the model is created and rarely changed except to
specify an Analytic rather than a Planning model.
The following image shows the model preferences options.

Figure 22: Model Preferences

© Copyright. All rights reserved. 55

Unit 3: Creating Import Models

Model Preferences
General Settings
Select the model type, either Planning or not (Analytic).
Language
Request language translation.
Access and Privacy
Set data access and other controls.
Date Settings
Enable weekly based if needed and set the date to calendar year or fiscal year.
Planning
Set disaggregation behavior for planning models.
Currency
Enable currency conversion.
Structure Priority
Set the tie breaker for data intersections for account and measure formulas.
Data and Performance
Configure settings to optimize performance for analytics and planning.

Viewing Options
When creating a model, you can view the structure of the model, the data in the model, or
both. Simply use the Toggle Data Foundation View button in the View area of the ribbon to
choose your preference.

Figure 23: Model Structure and Data Foundation Views

The upper half is the model structure, listing the measures and dimensions in the model. The
lower half is the data foundation view, showing the data values and members for the
measures and dimensions.
In planning models, you can switch among the different public versions of your data in the
data foundation view. For example, you may want to see if data exists for a specific version.
The default version is Actual.

56 © Copyright. All rights reserved.

 Lesson: Creating an Import Model

LESSON SUMMARY
You should now be able to:
● Create an import model.

© Copyright. All rights reserved. 57

Unit 3: Creating Import Models

58 © Copyright. All rights reserved.

 Unit 3
Lesson 2
Importing and Preparing Transaction Data in a
Model

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain data transformation functions in an import model.
● Import data into a model.

Import Transaction Data

Just as with public dimensions, data can be imported into models from files as well as source
systems. However, note that the Date and Version dimension data is system-generated;
therefore, there is no import option.
Master data is normally imported before transaction data is imported into the model. When
transaction data is imported, it is stored in the model’s fact table. A model can receive data
from one or several source systems depending on the scenario.
The work flow for importing transaction data into the model is similar to importing master
data into a dimension. One key difference is the Set Up Import activity. The Set Up Import
process is made up of four work steps.
The following figure shows the workflow for importing transaction data into the model.

Figure 24: Import Data Workflow

© Copyright. All rights reserved. 59

Unit 3: Creating Import Models

Data Import Workflow

The workflow below describe the import process for a measure-based model, not an account-
based model.

Workflow to Import Transaction Data from a SAP Source System

When you import data into a model from an SAP source system, you will need to select the
fields to import. In addition, you can set a filter for the import.

1. In the model, choose the Data Management workspace.

2. Choose Import Data → Data Source.

3. Select the Source System and then the Connection.

4. Choose the data source.

5. Select fields to be imported; add filter(s) if necessary. When the import is created, it
appears in the data management workspace of the model with a hyperlink: Set Up Import.
The following figure illustrates how you select the data to import into the model structure.

a. Available data: The source system fields are shown on the left side of the dialog. You
can scroll through the list or search for specific fields that are required.

b. Selected data: The fields that have been selected to be imported are displayed here.

c. Filters: Filter the data where needed. In the example, week 53 is not required so the
filter is set to Less than or equal to 52.

Figure 25: Model Import Query

6. Set up the import:

a. Prepare the data.

b. Map the source to the target.

60 © Copyright. All rights reserved.

 Lesson: Importing and Preparing Transaction Data in a Model

c. Map properties.

d. Review the import.

7. Run the import and read the log. If records fail, debug and re-import.

In order to run another import, repeat the process manually or schedule it to repeat on a
regular basis.

Prepare Transaction Data

As we have already seen, data used in SAP Analytics Cloud models may need to be modified
for reporting and analysis purposes. For example, data from a source system that is imported
into a model may have multiple columns for employee names - First Name and Last Name.
But for stories and analytic applications, designers may want only one column that combines
both First and Last names.
In the Prepare Data step, you can do quality checks, perform simple and complex
transformations, and change the job settings.

Custom Expression Editor

Just as when importing data into a dimension, when importing into a new model, simple
transformations are available via the smart transformation and quick actions. If more
complex transformations are needed, the custom expression editor is available.
In the figure Custom Expression Editor and Results the Before data table shows that the
source data contains year and week as separate columns. SAP Analytics Cloud requires
weeks 1-9 in two-digit format, using 08 instead of 8 as seen below.
The solution is to:

1. use the Custom Expression editor to add a 0 if the week is less than 10.

2. use the Transformation Bar to concatenate the Year and Week values with no separator
into the required YYYYWK format.

These results are shown in the After data table.

© Copyright. All rights reserved. 61

Unit 3: Creating Import Models

Figure 26: Custom Expression Editor and Results

Job Settings
During the import process, the Job Settings can be maintained:
● Import method: These selections are important when importing data again for the same
data region.
● Reverse sign by account type: If the source system stores revenue, equity, and liabilities
with positive values, then they can be reversed based on the account type property in the
account dimension.
● Update local dimensions with new members: If the model contains a private dimension,
then its members can be updated with new members during the model import.
● Conditional validation: This is used to validate members to make sure they are not parent
members in a hierarchy.

Figure 27: Job Settings

62 © Copyright. All rights reserved.

 Lesson: Importing and Preparing Transaction Data in a Model

Map to Target
In the figure Map to Target, the system will map fields automatically where possible. If the
source and target fields names are different, then the mapping can be completed using drag-
and-drop. When importing from an SAP source system, the mapping can be edited if needed.

Figure 28: Map to Target

1. Source fields.

2. Unmapped target fields. You can:

● Map to source fields.

● Set to a constant.

● Set to unassigned (#).

3. Mapped fields.

Map Properties
The Map Properties step can be used to map properties of both public and private
dimensions, if there are any. The only way to import into a private dimension is during the
model import. Also, when importing into an analytic model, the Map Properties step indicates
that all records have been assigned to the public actual version.

Note:
All target fields must either be mapped or use a default value or Unassigned. Some
source fields may be unmapped if they are not needed.

Review Import
Before you complete the import, you must review any issues. In the Review Import step, if
there are no issues the Dimension Restrictions area will be blank. If you have any issues,
choose the Prepare Dataset workspace, correct the issues, re-map if necessary, and return to
the Review Import workspace.

© Copyright. All rights reserved. 63

Unit 3: Creating Import Models

For example, in the following image you can see the issue that requires review. The U00
Stores dimension does not include e-Fashion in the store name, so the imported data does not
match the model dimension's data.

Figure 29: Review Import Step

Import Query Options

After the import process is complete, there are several important options in the Data
Management workspace:
● Edit allows you to change the import query.
● Schedule is where you can set up the import query to run periodically (e.g. daily).
● Select import method is used to change the import method (for example, from Update to
Clean and Replace).
● Refresh is used to run the import again.

Combine Data from Two Sources: Account-Based Model Only

In an account-based model you can combine data from two sources. For example, you may
have a data source that contains a dimension for Entity and another one with the same Entity
and a Profit Center dimension. You can combine both data sources into one model so that all
the members for both Entity dimensions use the same Profit Center.

64 © Copyright. All rights reserved.

 Lesson: Importing and Preparing Transaction Data in a Model

Update Methods
When data must be imported regularly into SAP Analytics Cloud models, you can use import
method options to prevent data duplication. In addition, when importing from SAP systems,
the import is typically filtered to the current period.
A choice of four import methods are available:

Import Method Description

Update Updates the existing data and adds new entries to the target model.
The scope of this update is based on a combination of all dimen-
sions in the target model.
For a more refined scope, use either the Clean and replace selected
version data or Clean and replace subset of data update options.

Append Leaves the existing data unchanged and adds only new entries to
the target model. When using append there are two options:

1. Reject duplicated records in the model.

2. Aggregate duplicated rows in the model.

Clean and replace se- Deletes the existing data and adds new entries to the target model
lected version data only for the versions that you specify in the import. You can choose
to use either the existing version or specify a new version under Ver-
sion.
For example, if you specify to import data for the Actual version, on-
ly the data in the Actual version is cleaned and replaced. Other ver-
sions, for example Planning, are not affected.

Clean and replace Replaces existing data and adds new entries to the target model for
subset of data a defined subset of the data based on a scope of selected versions
using either the Existing Version or New Version buttons. You can al-
so limit the scope to specific dimensions. To define a scope based
on a combination of dimensions, select + Add Scope and use the Se-
lect a dimension field to specify a dimension.
When a Date dimension is defined in the scope, the time range in the
source data (calculated based on the target model's granularity)
combined with other dimensions in the scope will determine what
existing data is cleaned and replaced.
If, for example, Date and Region dimensions are defined as part of a
scope, only entries that fall within the time range and match Region
from the source data will be replaced in the target model. Existing
data that does not match the scope will be kept unchanged.

© Copyright. All rights reserved. 65

Unit 3: Creating Import Models

Figure 30: Import Method Comparison

Debug Transaction Data

When some incoming records are correct but others have issues, the good records are
imported and the bad records are identified in the rejection summary which will appear in the
data management workspace.

Note:
If there is an issue with a scheduled import, the schedule status log can be
accessed via Connections in the navigation bar.

In the figure Rejected Records 1,116 rows were rejected. The rejection summary shows that
the dimension member does not exist. You must update the dimension and refresh the data
into the model.

Figure 31: Rejected Records

66 © Copyright. All rights reserved.

 Lesson: Importing and Preparing Transaction Data in a Model

LESSON SUMMARY
You should now be able to:
● Explain data transformation functions in an import model.
● Import data into a model.

© Copyright. All rights reserved. 67

Unit 3: Creating Import Models

68 © Copyright. All rights reserved.

 Unit 3
Lesson 3
Scheduling Data Imports

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Schedule data import.

Schedule Data Imports

You can import data from multiple data sources into a model, and each of these imports can
be separately scheduled. If you want to run multiple Import data jobs together, in a specified
order, create a source grouping. A grouping can include jobs from public dimensions as well
as the model. Running the grouping refreshes the public dimensions and model together.
The figure Schedule and Sequence Imports shows various scheduler settings.

Figure 32: Schedule and Sequence Imports

Scheduled jobs can also be viewed, deleted, and refreshed via: Navigation Bar →
Connections → Schedule Status.
If any rows in the dataset are rejected, you can select Download rejected rows to save the
rejected rows as a .csv file. You can then examine this file to see which data was rejected. You
can either correct the data in the .csv file and then import the .csv file into the model using the
Import Data workflow, or correct the data in the source system and re-import the data.

© Copyright. All rights reserved. 69

Unit 3: Creating Import Models

LESSON SUMMARY
You should now be able to:
● Schedule data import.

70 © Copyright. All rights reserved.

 Unit 3
Lesson 4
Creating Formulas and Calculations

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain calculations created for import models.
● Create calculated measures in a model.

Dimension Member Formulas

In account-based models, Dimension Member Formulas are configured in the Account
dimension type to perform calculations using existing dimension members, such as Labor as
a Percent of Cost (calculated using the Labor and Cost dimension members.
The figure Dimension Formula Example shows calculating labor as percentage of cost in the
model, and then displaying the results in a table in a story.

Figure 33: Dimension Formula Example

You can use dimension member formulas to calculate account values that are restricted to
other dimension member values such as Prior Year Revenue. A dimension formula is available
in any story that uses a model that contains the account dimension with a formula.
An account dimension formula can be used as it was created in the dimension, or it can be
modified in specific models. In this scenario, the model can contain its own version of the
dimension formula.

© Copyright. All rights reserved. 71

Unit 3: Creating Import Models

Calculated Measures
Calculated Measures are similar to Dimension Member Formulas, but are created in the
Calculations workspace for measure-based models. They do not appear in the Data
Foundation view because, like Dimension Member Formulas, the results are not stored in the
model. They are calculated only when used in the story.
The figure Calculated Measures outlines how to create a calculated measure:

1. Go to the Calculations Workspace.

2. Add the Calculated Measure.

3. Create the Formula.

4. Preview the results.

Figure 34: Calculated Measures

Calculated Measure Exception Aggregation Settings

Calculated measure exception aggregation settings allow you to incorporate dimensions into
the calculated values. For example, if you have a model with Store and Product Line
dimensions and a Revenue measure, you may want to create a measure that counts the
number of product lines sold by each store.
With Exception Aggregation, you can specify that you want the Revenue value to be counted
by each Product Line and Store.

72 © Copyright. All rights reserved.

 Lesson: Creating Formulas and Calculations

Figure 35: Exception Aggregation

In the figure Exception Aggregation, the weekly counts of product lines are counted per store.
The monthly amount is not a total (which would be inaccurate) but rather reflects the total
number of unique product lines sold in that store for that month.
Exception Aggregation can be quite complex, but may be necessary to ensure that the final
result of a calculation is correct. For a more detailed explanation and examples of its use with
SAP Analytics Cloud models (and stories), refer to this blog.

LESSON SUMMARY
You should now be able to:
● Explain calculations created for import models.
● Create calculated measures in a model.

© Copyright. All rights reserved. 73

Unit 3: Creating Import Models

74 © Copyright. All rights reserved.

 Unit 3
Lesson 5
Translating Currency

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Configure and translate currencies.

Currency Translation Overview

SAP Analytics Cloud analytic models can easily handle most currency scenarios without a
separate currency dimension. To accomplish this, you can either use the model settings or
story currency conversion measures.

Note:
In a measure-based model, you can enable a currency variable in the model
Preferences to set a default target currency for conversions measures.

Exchange rates are stored in the SAP Analytics Cloud currency translation rates table.
Exchange rates originate from financial institutions and are automatically or manually
updated into the table. If a currency conversion is added and there are no exchange rates, the
system will direct you to the currency table to add the missing rates.
With currency conversion, there are several terms to be aware of:
● Local Currency (LC): The functional or operating currency of a company; for example, a
company in the US has a local currency of USD.
● Group Currency: The corporate level currency; for example, a company in the US that has
a German parent has a group currency of EUR.
● Translation: Used interchangeably with conversion.

Note:
The concepts in this lesson concern planning concepts only, not month-end
closing currency translation.

Currency Translation Results in a Story

In the figure Currency Examples in a Story:

1. The local currency property value for Store02 is EUR.

Displaying the local currency property in the columns is optional and not required for the
currency conversion to occur.

© Copyright. All rights reserved. 75

Unit 3: Creating Import Models

2. The local currency is EUR. This value is stored in the database.

3. Group Currency is USD. This value is stored in the database.

4. Alternative Currency CAD is calculated but not stored. This is a model currency
conversion measure.

5. Simulated_CUR is a story calculated measure.

Figure 36: Currency Examples in a Story

Currency Translation Table

Currency conversion tables are defined independently of models. You can apply a selected
table to any model you create. Currency tables are listed on a separate Currency Conversion
page, where you can add, copy, and delete currency tables as required.

Figure 37: Currency Translation Table

In the figure Currency Translation Table, note the following:

1. CAD values will be translated to EUR values at an exchange rate of 0.65 for accounts that
have the Average rate type for postings that occur on 2020.01.01 or later.

2. Category is used to assign rates to a specific planning version such as Actual or Forecast.
Leave this setting blank to create a generic conversion rate.

3. Rate Version is used to create a rate for specific planning Versions and other scenarios.
Set the Category to Specific and then type a name for the Rate Version.

4. Rate Type allows you to define whether the exchange rate is an average for the month or
whether it is the month-end closing rate. Income statement accounts use Average and
balance sheet accounts use Closing.

5. Check the conversion error log, if needed.

76 © Copyright. All rights reserved.

 Lesson: Translating Currency

Currency tables can be updated via flat files, SAP BPC rate models, and SAP BW queries. For
more information, see the Currency Conversion Tables documentation.

Model and Dimension Currency Settings

Model Preferences: Currency
Enable currency conversion from the model Preferences using the following steps:

1. Activate Currency Conversion using the toggle.

When currency conversion is activated for the model, the rate type and currency
properties are added to the account dimension.

2. Select the source currency table using the Currency Rates Table drop down.

3. Select the date dimension for the date determination.

4. Activate the currency variable (optional) by selecting Create Currency Variable in the
currency variable settings.
The currency variable can be used to determine the target currency dynamically when the
story is opened.

Measures can also be added to the model that calculate currency values with each data
refresh.

Dimension Settings: Currency

You can enable currency conversion for a dimension. When you do, the Currency property
column, is added. Using three-character currency codes, this column identifies the source
currency for data that belongs to each member. The Currency column is enabled by default
for the Organization dimension type, and can also be added to generic dimensions.
To enable currency translation for a dimension:

1. Use the Enable Currency toggle to enable currency translation for the dimension. This
option can be for any dimension that has a currency property, not just Organization type
dimensions.

2. Change the name of the currency property (for display in the story) by selecting the pencil
icon.

© Copyright. All rights reserved. 77

Unit 3: Creating Import Models

3. LC is the local (or operating) currency of the entities; for example, a store in Canada has a
local currency of CAD.

For each converted measure in the model, a dimension (any dimension with currency
enabled) is set as the currency dimension.

Account Dimension Settings: Currency

In the Account dimension type, the Rate Type property column is added when you enable
currency conversion in the model Preferences. Set the Rate Type to Average for INC and EXP
accounts, and to Closing for AST and LEQ accounts. This setting corresponds to the rate type
for exchange rates in your currency table and allows you to distinguish between the average
exchange rate over a period and the closing rate at the end of the period.

Note:
Only the average and closing rate types are possible. Custom rate types are not
possible.

In the example below:

1. The EXP and INC account types use the Average rate type. LEQ and AST use the Closing
rate type.

2. The Units & Currencies property must be set to Currency.

Currency Conversion Examples

Forecast versus Actual Exchange Rates
If needed, you can compare values that use exchange rates for different categories. This
feature is useful for what-if scenarios.
In the figure Version-Specific Exchange Rates you can see the following steps:

78 © Copyright. All rights reserved.

 Lesson: Translating Currency

1. Add Account and Forecast exchange rates.

2. Add currency conversion in the input form for Actual.

3. Add currency conversion in the input form for Forecast.

4. View the results in the output.

Figure 38: Version-Specific Exchange Rates

Constant Currency Analysis

Constant currencies are exchange rates used by international companies to eliminate the
effects of foreign currency fluctuations in financial statements. For example, you may want to
see annual growth in a model currency (such as USD) but choose to use January's average
exchange rate for all months of the year to minimize fluctuations in the monthly values.

Figure 39: Constant Currency Analysis

In the figure Constant Currency Analysis:

© Copyright. All rights reserved. 79

Unit 3: Creating Import Models

● The Default Currency (USD) values are translated with the monthly average exchange
rates for 2020. For example:
- January: 11,655.9 x 1.1 = 12,821.5
- February: 17,302.5 x 1.15 = 19,897.9
● The USD in Constant ER (USD) values are translated with the January average exchange
rate for 2020 only. For example:
- January: 11,655.9 x 1.1 = 12,821.5
- February: 17,302.5 x 1.1 = 19,032.7

LESSON SUMMARY
You should now be able to:
● Configure and translate currencies.

80 © Copyright. All rights reserved.

 Unit 3
Lesson 6
Designing and Creating Time Hierarchies

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Explain the prerequisites required for creating hierarchies.
● Build custom time hierarchies.

Build a Custom Time Hierarchy

Time Hierarchy Overview
The Date dimension defines the start and end dates of the model's time frame. It also
specifies the granularity of the time units used in the model (year, quarter, month, week, or
day).
It can be maintained either manually and automatically by the system. Leaving the
management to the system means that the dimension member values are generated from the
parameters within the Dimension Settings panel in the Modeler, and in the model Preferences.
Conversely, maintaining the Date dimension manually allows you to edit the master data and
manage all dimension members and hierarchies freely.
You can specify a default time hierarchy to display in stories, and optionally configure the date
dimension to organize data by fiscal year instead of calendar year. A model can contain more
than one date dimension if needed.

Weekly Time Patterns

Since there are, on average, 52 weeks in a year, but each quarter may contain only partial
weeks, SAP Analytics Cloud gives you options for determining how many weeks are in each
month of a quarter. The supported weekly time patterns per month in each quarter are:
● 4-4-5
● 4-5-4
● 5-4-4
● 13x4 (dividing 52 weeks by 4 quarters)

Custom Time Hierarchy

Custom time hierarchies help you plan and analyze data using one or more hierarchies. They
also allow for company-specific fiscal year periods.
To create a custom time hierarchy, you must first set the Dimension Details for the Date
dimension type to User-Managed. Then you can add your own custom time hierarchies and
edit the predefined hierarchies that come with the time granularity applied to the dimension.

© Copyright. All rights reserved. 81

Unit 3: Creating Import Models

Time hierarchies are level-based, based on properties of the Date dimension. If you need a
custom hierarchy you must add properties first.

Semantic Types
Each property you create is assigned to a Semantic Type, which is a time unit assigned to a
property within the hierarchy. The Semantic Type options are:
● Year
● Half-Year
● Quarter
● Month
● Period
● Week
● Day
● Other

The semantic type Other is reserved for custom properties that you want to attach to other
properties as linked descriptions.
Once the properties have a Semantic Type assigned, you can add them as levels within the
hierarchy.
Make sure to follow these guidelines:
● The hierarchy has the mandatory Year semantic type as the highest level.
● The semantic types within the hierarchy are ordered from the largest to the smallest time
unit. For example, Month must be below Quarter and above Week.
● Each semantic type within the hierarchy is used only once, except for the Other semantic
type.
● If the hierarchy uses the semantic type Month, do not include the semantic type Period,
and vice versa.
● The lowest level of the hierarchy is the ID property if there is one. Otherwise, it must be a
unique property.
● Description properties cannot be used in the hierarchy.

In the example below, the hierarchy has 3 levels:

● Level 3: Season
● Level 2: Holiday
● Level 1: Week

To create a new hierarchy from the Hierarchy Builder, simply click + Create New Hierarchy
and then drag and drop the required levels into the custom time hierarchy.

82 © Copyright. All rights reserved.

 Lesson: Designing and Creating Time Hierarchies

Figure 40: Bar Chart with a Custom Time Hierarchy

The figure Bar Chart with Custom Time Hierarchy is one example of a custom time hierarchy
displaying sales values for each season and then drilled down to the Easter Season.

LESSON SUMMARY
You should now be able to:
● Explain the prerequisites required for creating hierarchies.
● Build custom time hierarchies.

© Copyright. All rights reserved. 83

Unit 3: Creating Import Models

84 © Copyright. All rights reserved.

 Unit 3

Learning Assessment

1. What happens when you turn off the Planning option in Model Preferences?
Choose the correct answer.

X A Data can't be written to the model

X B Currency conversion is possible

X C The Version dimension goes away

X D The Date dimension is added

2. When importing data into a model, which dimension has no import option?
Choose the correct answers.

X A Version

X B Account

X C Date

X D Organization

3. Model imports settings allow you stop an import job if one step fails.
Determine whether this statement is true or false.

X True

X False

4. Dimension member formulas are only available for the account type dimension.
Determine whether this statement is true or false.

X True

X False

© Copyright. All rights reserved. 85

Unit 3: Learning Assessment

5. Where does SAP Analytics Cloud store exchange rates?

Choose the correct answer.

X A In a dataset

X B In a currency table

X C In a model

X D In a dimension

6. How can the currency table be updated?

Choose the correct answers.

X A SAP BPC rate model

X B Flat File

X C FTP

X D SAP BW query

X E Internet download

7. What time pattern is supported for the Date dimension?

Choose the correct answer.

X A 4-4-4

X B 4-5-5

X C 13x4

X D 12x4

8. How is the model's time unit granularity defined?

Choose the correct answer.

X A By the model preferences

X B By the imported data

X C By the date dimension

X D By the import query

86 © Copyright. All rights reserved.

 Unit 3: Learning Assessment

9. What is a prerequisite for creating a custom time hierarchy?

Choose the correct answer.

X A Add the hierarchy to the source system

X B Add time-related properties to the date dimension

X C Change the date dimension to organize date by fiscal year

© Copyright. All rights reserved. 87

 Unit 3

Learning Assessment - Answers

1. What happens when you turn off the Planning option in Model Preferences?
Choose the correct answer.

X A Data can't be written to the model

X B Currency conversion is possible

X C The Version dimension goes away

X D The Date dimension is added

When the planning option is disabled in the Model Preferences, it is no longer possible to
write data to the model.

2. When importing data into a model, which dimension has no import option?
Choose the correct answers.

X A Version

X B Account

X C Date

X D Organization

The Version and Date dimensions are system-generated so have no import option.

3. Model imports settings allow you stop an import job if one step fails.
Determine whether this statement is true or false.

X True

X False

The Stop if any query fails setting stops group processing if any import job fails. The Skip
any failed query setting allows a failed import job to be skipped and the remaining jobs are
still processed.

88 © Copyright. All rights reserved.

 Unit 3: Learning Assessment - Answers

4. Dimension member formulas are only available for the account type dimension.
Determine whether this statement is true or false.

X True

X False

Dimension member formulas are only available for the account type dimension.

5. Where does SAP Analytics Cloud store exchange rates?

Choose the correct answer.

X A In a dataset

X B In a currency table

X C In a model

X D In a dimension

Exchange rates are stored in a separate currency table.

6. How can the currency table be updated?

Choose the correct answers.

X A SAP BPC rate model

X B Flat File

X C FTP

X D SAP BW query

X E Internet download

The currency table can be updated via flat file, SAP BPC rate model, or BW query.

7. What time pattern is supported for the Date dimension?

Choose the correct answer.

X A 4-4-4

X B 4-5-5

X C 13x4

X D 12x4

The supported weekly time patterns are: 4-4-5, 4-5-4, 5-4-4, 13x4.

© Copyright. All rights reserved. 89

Unit 3: Learning Assessment - Answers

8. How is the model's time unit granularity defined?

Choose the correct answer.

X A By the model preferences

X B By the imported data

X C By the date dimension

X D By the import query

The model's time unit granularity is defined by the date dimension.

9. What is a prerequisite for creating a custom time hierarchy?

Choose the correct answer.

X A Add the hierarchy to the source system

X B Add time-related properties to the date dimension

X C Change the date dimension to organize date by fiscal year

Because time hierarchies are parent-child, you must add time-related properties to the
date dimension.

90 © Copyright. All rights reserved.

 UNIT 4 Working With Live Models

Lesson 1
Using Data Analyzer to Preview Your Live Data Structure 93

Lesson 2
Creating Live Models 95

Lesson 3
Working with SAP Datasphere 101

UNIT OBJECTIVES

● Access data for your model with the data analyzer.

● Create a live model with SAP S/4HANA data.
● Create a live model with SAP HANA data.
● Create a live model with SAP Business Warehouse data.
● Create a live model with SAP BusinessObjects data.
● Create a story using an SAP Datasphere model as the data source.

© Copyright. All rights reserved. 91

Unit 4: Working With Live Models

92 © Copyright. All rights reserved.

 Unit 4
Lesson 1
Using Data Analyzer to Preview Your Live Data
Structure

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Access data for your model with the data analyzer.

Data Structures for Data Analyzer

You can access the data from a live connection without creating a model by using Data
Analyzer. Data Analyzer is a predefined ready-to-run service for SAP Business Warehouse
(SAP BW) queries, SAP HANA Live views, SAP Datasphere models, and SAP Analytics Cloud
models for ad-hoc analysis.
All SAP BW queries, SAP HANA Live views and models can be accessed directly in the Select
Data Source. You can use Data Analyzer to preview your live data before creating a live data
model.
Data Analyzer contains a table/chart area, a filter area, and a builder panel with navigation
capabilities to add and remove dimensions and measures from the table/chart. In addition,
you find a menu bar with a Refresh option and an Edit Prompts dialog.

Figure 41: Data Analyzer

LESSON SUMMARY
You should now be able to:
● Access data for your model with the data analyzer.

© Copyright. All rights reserved. 93

Unit 4: Working With Live Models

94 © Copyright. All rights reserved.

 Unit 4
Lesson 2
Creating Live Models

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create a live model with SAP S/4HANA data.
● Create a live model with SAP HANA data.
● Create a live model with SAP Business Warehouse data.
● Create a live model with SAP BusinessObjects data.

Overview
Live models are created with SAP data and are created in the same way, regardless of the
SAP system. The only difference is the System Type, Connection, and Data Source you select
in the dialog when you begin the creation process.
Your SAP Analytics Cloud system administrator typically creates the Connection, while your
SAP source system team creates the Data Sources.

Figure 42: Create Live Model Dialog

SAP S/4HANA
SAP S/4HANA Integration
The integration with an S/4HANA system can be done in two ways:
● As a live data connection: No data is stored on SAP Analytics Cloud.
● As an import data connection: Data is stored on SAP Analytics Cloud and updated
periodically. When using SAP Analytics Cloud as the interface for planning activities, data
must be imported from S/4HANA.

© Copyright. All rights reserved. 95

Unit 4: Working With Live Models

SAP S/4HANA Data Sources for Live Models

You can create live data models to SAP S/4HANA Core Data Services Views or Queries.

SAP HANA
SAP HANA Integration
SAP Analytics Cloud is integrated with SAP HANA in two ways:
● As a live data connection: Available for SAP HANA and SAP HANA Cloud.
● As an import data connection: Available for SAP HANA.

SAP HANA Data Sources for Live Models

In SAP Analytics Cloud, you can create live models using HANA Calculation Views as a data
source. Calculation Views allow definition of more advanced slices on the data available in the
SAP HANA database. Live models based on SAP HANA Calculation Views can improve story
performance by delegating and moving data-intensive calculations to SAP HANA Cloud.
When working with live models for SAP HANA, there are three unique features:

1. You can declare a Time Dimension, allowing for the use of automatic time determination
features in stories.

2. In the Measures tab, the aggregation settings can be adjusted in the live model.

3. In the Dimension tab, dimensions can be renamed, grouped, or hidden.

Live models in SAP HANA: Below, you can see a story table with time determination options
for an SAP HANA live model. It allows for automatic time determination in stories.

96 © Copyright. All rights reserved.

 Lesson: Creating Live Models

SAP Business Warehouse

SAP Business Warehouse Integration
The Integration of an SAP Business Warehouse can be done in two ways:
● As a live data connection: Available for SAP BW and SAP BW/4HANA.
● As an import data connection: Available for SAP BW and SAP BW/4HANA.

SAP BW Data Sources for Live Models

You can create live data models to SAP BW Queries.

Supported SAP BW Query Elements in Live Models

The following SAP BW query elements are supported in SAP Analytics Cloud models:
● Conditions
● Time-dependent hierarchies.
● SAP BW variables.
● SAP BW variants and personalization.
● SAP BW structures.
● Parallel processing of SAP BW queries.

BW Hierarchy Support
● Time dependent hierarchies are supported.
● Time dependent hierarchy structures are supported.

BW Variable Support
● Exit and authorization variables are supported.
● Show booked values in the search help based on the setting in the BW query.
● Merge/unmerge Prompts.

Parallel Processing Support

● Only use where performance improvement is absolutely required.
● Manage BW server resources carefully.

© Copyright. All rights reserved. 97

Unit 4: Working With Live Models

Measure/Dimension Support
For measures, you can change the following:
● Descriptions.
● Scale to be displayed as default (thousands, millions, etc.).
● The decimal place defaults: This is preferable at the model level if measure reporting has a
specific universal format (as in financial reporting), as opposed to always changing scale
and decimals at the story level.

For dimensions, you can change the following:

● Descriptions.
● Create semantic groups of dimensions for easier navigation during story creation. This is
advantageous in the case of SAP BW queries that have a large number of dimensions to
choose from.

Note:
Display and navigation attributes are not fully supported. You must manually
change the attribute column in as a property classification.

SAP BusinessObjects
SAP BusinessObjects Integration
The Integration with SAP BusinessObjects can be done in two ways:
● As a live data connection: Available for SAP BusinessObjects Universes and Web
Intelligence documents.
● As an import data connection: Available for SAP BusinessObjects Universes.

SAP BusinessObjects Data Sources for Live Models

Live models can connect to a SAP Business Objects Universe and to Web Intelligence
documents, including any document variables (formulas).

Note:
Web Intelligence Variables are not to be confused with SAP BW Variables. SAP BW
Variables often render as prompts. Web Intelligence variables are simply
calculations and formulas that have been defined with a name and will not prompt
the user for any information.

LESSON SUMMARY
You should now be able to:
● Create a live model with SAP S/4HANA data.
● Create a live model with SAP HANA data.
● Create a live model with SAP Business Warehouse data.

98 © Copyright. All rights reserved.

 Lesson: Creating Live Models

● Create a live model with SAP BusinessObjects data.

© Copyright. All rights reserved. 99

Unit 4: Working With Live Models

100 © Copyright. All rights reserved.

 Unit 4
Lesson 3
Working with SAP Datasphere

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Create a story using an SAP Datasphere model as the data source.

SAP Datasphere
The advantages of using an SAP Datasphere model in an SAP Analytics Cloud story include:
● More analytical capabilities or calculation for complex business requests
● Reusable objects
● Output control
● Optimized performance
● Optimized integration for SAP Business Warehouse
● Reusing data security of the source (supported by SSO)
● Analytical previews
● Self-service analytics strategies are supported - users can create their own models

Add Trusted Origins and Tenant Links

System administrators must first set SAP Analytics Cloud and SAP Datasphere as trusted
origins to each other. This means a security-based trusted relationship is created between the
two platforms.
It provides:
● Secure communication
● Secure data transfer/exchange
● Authentication
● Authorization

It is also recommended to establish tenant links between SAP Analytics Cloud and SAP
Datasphere. This enables a better and more efficient collaboration between the two cloud
platforms. It helps to provide data very easily and for users to navigate between the
connected tenants using the Product Switch menu option.

© Copyright. All rights reserved. 101

Unit 4: Working With Live Models

Figure 43: Add SAP Datasphere and SAP Analytics Cloud as Trusted Origins and Enable Product Switch

Create a Live Connection

Administrators create a live data connection from SAP Analytics Cloud to SAP Datasphere,
allowing SAP Analytics Cloud users to consume data that has been modeled in SAP
Datasphere. A story can be created in SAP Analytics Cloud using an SAP Datasphere model
as a data source with no additional effort.

Figure 44: Add Live Connection

Note:
The use of the different data structures in SAP Datasphere belongs to the Data
Security and User Permissions settings in SAP Datasphere.

SAP Datasphere Analytic Model

SAP Analytics Cloud is able to directly consume an SAP Datasphere analytic model. For this
reason, there is no need to create live model in SAP Analytics Cloud. The model is created in

102 © Copyright. All rights reserved.

 Lesson: Working with SAP Datasphere

SAP Datasphere and changes to the SAP Datasphere data model can only performed in SAP
Datasphere Data Builder. SAP Analytics Cloud cannot be used to update the model.
This simplifies story creation as the user can use the data for analyzing without having to
create or maintain a data model in SAP Analytics Cloud.
To use SAP Datasphere as a data source, you must start off with an SAP Datasphere space.
Spaces are created in the Data Builder by administrators and are virtual work environments
with their own databases. It is in the space that models created in SAP Datasphere are stored.

1. SAP Datasphere Data Builder

2. SAP Datasphere space

3. SAP Datasphere model

Figure 45: SAP Datasphere Data Builder

Note:
Spaces in SAP Datasphere and its data are used according to the Data Security
and Permission settings in SAP Datasphere.

View the Model

Modelers can update the model in SAP Datasphere. In the example below, you can see an SAP
Datasphere analytic model.

1. Impact and Lineage and Generate OData Request tools.

2. Single fact source

3. Toggle between Model and Preview.

4. When you open a model in SAP Datasphere, you can see if it has been deployed or not. A
model can only be used as a data source in SAP Analytics Cloud if it has been deployed.

5. Measures are taken from fact source. Calculated and restricted measures can be added.

© Copyright. All rights reserved. 103

Unit 4: Working With Live Models

6. Dimensions, including nested dimensions. Text associations and hierarchies are

automatically resolved.

7. Variables for different use cases. For example, input parameter push-down, restricted
measure variables.

Figure 46: SAP Datasphere Analytic Model

Note:
Data Analyzer in can be used to preview data in SAP Analytics Cloud

Use the SAP Datasphere Analytic Model as a Data Source in an SAP Analytics Cloud Story
To use a model created in SAP Datasphere, you first have to create an Optimized Design
Experience story in SAP Analytics Cloud using the model that was created and deployed in
SAP Datasphere.

1. In the Select Dataset or Model dialog, select the SAP Datasphere tenant.

2. Select the SAP Datasphere space.

3. Select the SAP Datasphere model.

104 © Copyright. All rights reserved.

 Lesson: Working with SAP Datasphere

Figure 47: Using an SAP Datasphere Model in a Story.

The SAP Datasphere model appears in the SAP Analytics Cloud story Builder panel as the
story's data source.

Figure 48: SAP Datasphere Model in an SAP Analytics Cloud Story.

Unsupported Features
To view unsupported features with SAP Datasphere live connections in SAP Analytics Cloud
go to SAP Note: 2832606.

LESSON SUMMARY
You should now be able to:
● Create a story using an SAP Datasphere model as the data source.

© Copyright. All rights reserved. 105

Unit 4: Working With Live Models

106 © Copyright. All rights reserved.

 Unit 4

Learning Assessment

1. Data Analyzer can use import connections.

Determine whether this statement is true or false.

X True

X False

2. When accessing data from SAP S/4HANA, what is a possible data source?
Choose the correct answers.

X A Query

X B Core Data Services View

X C Calculation View

X D InfoProvider

3. What is the source when acquiring data from SAP HANA Cloud into SAP Analytics Cloud?
Choose the correct answer.

X A Core Data Services View

X B Calculation View

X C Composite View

X D Responsive View

4. Which SAP BW elements are supported in an SAP Analytics Cloud model?

Choose the correct answers.

X A Exception

X B Structure

X C Variable

X D Condition

© Copyright. All rights reserved. 107

Unit 4: Learning Assessment

5. When using a WebI document as a data source, Web Intelligence variables are not
accessible.
Determine whether this statement is true or false.

X True

X False

6. Which of the following statements is false?

Choose the correct answer.

X A To use a model created in SAP Analytics Cloud, you must expose the model to SAP
Datasphere.

X B To use a model created in SAP Analytics Cloud, you must select SAP Datasphere
as the data source.

X C To update a model created in SAP Analytics Cloud, you must make the changes in
SAP Datasphere.

108 © Copyright. All rights reserved.

 Unit 4

Learning Assessment - Answers

1. Data Analyzer can use import connections.

Determine whether this statement is true or false.

X True

X False

The data analyzer can use live connections.

2. When accessing data from SAP S/4HANA, what is a possible data source?
Choose the correct answers.

X A Query

X B Core Data Services View

X C Calculation View

X D InfoProvider

Data sources for SAP S/4HANA are CDS Views and Queries.

3. What is the source when acquiring data from SAP HANA Cloud into SAP Analytics Cloud?
Choose the correct answer.

X A Core Data Services View

X B Calculation View

X C Composite View

X D Responsive View

Calculation Views in SAP HANA Cloud are used to provide data to SAP Analytics Cloud.

© Copyright. All rights reserved. 109

Unit 4: Learning Assessment - Answers

4. Which SAP BW elements are supported in an SAP Analytics Cloud model?

Choose the correct answers.

X A Exception

X B Structure

X C Variable

X D Condition

Structures, variables, and conditions are supported SAP BW elements, along with time-
dependent hierarchies, variants and personalization, and parallel processing of queries.

5. When using a WebI document as a data source, Web Intelligence variables are not
accessible.
Determine whether this statement is true or false.

X True

X False

Your SAP Analytics Cloud live model has access to variables defined in the Web
Intelligence document.

6. Which of the following statements is false?

Choose the correct answer.

X A To use a model created in SAP Analytics Cloud, you must expose the model to SAP
Datasphere.

X B To use a model created in SAP Analytics Cloud, you must select SAP Datasphere
as the data source.

X C To update a model created in SAP Analytics Cloud, you must make the changes in
SAP Datasphere.

Models created in SAP Analytics Cloud must be updated in SAP Analytics Cloud. Models
created in SAP Datasphere must be updated in the SAP Datasphere Data Builder.

110 © Copyright. All rights reserved.

 UNIT 5 Working with Geographic Data

Lesson 1
Configuring Geographic Data in a Model 113

UNIT OBJECTIVES

● Configure data for a geo map.

© Copyright. All rights reserved. 111

Unit 5: Working with Geographic Data

112 © Copyright. All rights reserved.

 Unit 5
Lesson 1
Configuring Geographic Data in a Model

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Configure data for a geo map.

Geo Enrich Your Data

Before you perform geospatial analysis in stories, you must first add coordinate data and
enrich it in the modeler. This process creates a new column in the data view with an enriched
format of concatenated latitude and longitude coordinates.

Note:
Geo enriching is available for both live and replicated data scenarios; however, in
this course we’re focusing on the replicated use case.

As a prerequisite, you must have an XLSX or CSV file with a location ID column that contains
unique data, and latitude and longitude columns.
A Location dimension is created in the modeler using location data. This acts as the
foundation for the map in your story. There are two ways to geo-enrich your data:

1. By coordinates: Geo-enriching your data by coordinates enables you to use longitude and
latitude coordinates. Your data may already include this information, but you can also
enter it manually in a file.

2. By area name: During the creation of the Location dimension you can download all the
currently supported countries, regions, and sub-regions. This option does not support an
area enrichment with mixed granularity. For example, if enriching an area that has
locations in both Country A and Country B, but Country A does not go down do the Sub-
Region level, then the enrichment can only be created to the Region level at the lowest.

The figure Geo Enrich Data by Coordinates shows how you can enrich your data by
coordinates.

© Copyright. All rights reserved. 113

Unit 5: Working with Geographic Data

Figure 49: Geo Enrich Your Data by Coordinates

Points of Interest
Points of interest are sets of geographical data that you can add to a geo map and analyze
with reference to data from a model.
You can add point of interest data from an Esri shapefile, Excel or a CSV file, or from a SAP
HANA model with a geographical dimension.
If you have a CSV or Excel file with clearly distinguishable names for latitude and longitude
columns, you can simply drag and drop the file directly into your geo map.

Note:
Points of Interest will disappear soon. To prevent disruption, please use geo
enriched dimensions instead.

Figure 50: Point of interest

SAP Analytics Cloud supports a finite number of spatial reference IDs. To avoid incorrectly
displayed data or error messages, you should know the spatial reference identifier (SRID)
used in your shapefile. Publicly available tools can help you recognize the shape identifier and
thus determine the shapefile format.

114 © Copyright. All rights reserved.

 Lesson: Configuring Geographic Data in a Model

You can view and maintain point of interest data in the Files list where you can filter on the
Points of Interest file type to view the files. You can add or search points of interest, or select
points of interest to delete.
You can set access permissions for point of interest data using the Share icon in the toolbar.

Additional Information
From the Esri website you can access Esri location data, such as Points of Interest.

LESSON SUMMARY
You should now be able to:
● Configure data for a geo map.

© Copyright. All rights reserved. 115

Unit 5: Working with Geographic Data

116 © Copyright. All rights reserved.

 Unit 5

Learning Assessment

1. When you geo-enrich data, the system concatenates the latitude and longitude columns.
Determine whether this statement is true or false.

X True

X False

2. Which dimension is automatically created when you geo-enrich the data?

Choose the correct answer.

X A Region

X B Area

X C Geo Reference

X D Location

3. Where can you get Point of Interest data?

Choose the correct answers.

X A .xlsx or .csv file

X B SAP HANA model

X C Internet download

X D Esri shapefile

X E Geo table

© Copyright. All rights reserved. 117

 Unit 5

Learning Assessment - Answers

1. When you geo-enrich data, the system concatenates the latitude and longitude columns.
Determine whether this statement is true or false.

X True

X False

When you geo-enrich data, the system concatenates the latitude and longitude columns.

2. Which dimension is automatically created when you geo-enrich the data?

Choose the correct answer.

X A Region

X B Area

X C Geo Reference

X D Location

The Location dimension is created when you geo-enrich the data.

3. Where can you get Point of Interest data?

Choose the correct answers.

X A .xlsx or .csv file

X B SAP HANA model

X C Internet download

X D Esri shapefile

X E Geo table

You can get Point of Interest data from .xlsx or .csv files, SAP HANA models, and Esri
shapefiles.

118 © Copyright. All rights reserved.

 UNIT 6 Defining Data Security

Lesson 1
Defining Data Access 121

UNIT OBJECTIVES

● Apply data access control.

© Copyright. All rights reserved. 119

Unit 6: Defining Data Security

120 © Copyright. All rights reserved.

 Unit 6
Lesson 1
Defining Data Access

LESSON OBJECTIVES
After completing this lesson, you will be able to:
● Apply data access control.

Securing Data
General SAP Analytics Cloud Security
Security in SAP Analytics Cloud is used to control access to data and also access to objects. It
is carried out in the following ways:

1. Controlling access to objects, or who can create a model, is accomplished via roles.

2. Controlling data access, or who can view what data and how they can interact with it, is
accomplished primarily via data access control in dimensions; however, it can also be
carried out via roles.

Roles
A role represents the main tasks that a user performs in SAP Analytics Cloud. SAP Analytics
Cloud is delivered with several standard application roles; however, the roles you see will
depend on the licenses included in your subscription.
Roles are used mainly to control activities in the system. In this context, roles are also object
oriented, for example, user X can update dimension Y.

Basic Permissions
● Create: Permits creating new objects. Users need this permission to create files and
folders or upload data to an object, such as models, stories, point of interest, and others.
● Read: Permits opening and viewing an item and its content.
● Update Permits editing and updating existing items, including the structure of models and
dimensions.
● Delete: Permits deletion of an item.
● Execute: Permits executing the item to run a process, for example, running a simulation
using a Value Driver Tree, or acquiring data from a data source.
● Maintain: Permits the maintenance of data values, for example adding records to a model,
without allowing changes to the actual data structure.
● Share: Permits the sharing of the selected item type.
● Manage: This permission lets users manage content; for example, deleting content for any
users, and resharing, copying, and moving content.

© Copyright. All rights reserved. 121

Unit 6: Defining Data Security

Visit SAP Help for additional information on permissions.

Example of Security Permissions

Assignments are typically team-based with users assigned to teams and then roles assigned
those teams. Roles are not typically assigned directly to users.

Name Create/ Execute Maintain Notes

Read/ Up-
date/ De-
lete
Dimension X X Set the Maintain permission to permit
adding members to a dimension with-
out being able to change the actual
definition. Set Update to allow chang-
ing the dimension itself.
Currency X
Planning X X X Set the Maintain permission to permit
Model adding records of data without being
able to change the actual structure.
Set Update to allow changing the mod-
el structure itself. Set Execute to ena-
ble planning features.

Model Access and Privacy

In the following example, you can see the two options to secure data from the model
preferences:

1. Model Data Privacy: Model Data Privacy determines whether the model is visible to users
other than the owner. If you switch on Model Data Privacy, only the owner of the model
and user roles that have specifically been granted access can see the data. Disable this
switch if you want the model and data to be public. Member IDs and properties can be
used when defining which roles can access which models.

2. Data Access Control in Dimensions: If you activate the Data Access Control switch for any
dimension, you can then specify the data access in the dimension's setting.

122 © Copyright. All rights reserved.

 Lesson: Defining Data Access

Figure 51: Model Data Privacy and Data Access Control

Data Access Control in Dimensions

After the Data Access Control switch has been activated in the model for specific dimension,
you can restrict access to data in stories by setting read and write permissions for individual
members.

Special Considerations
For the Version dimension, a Delete column is added as well as Read and Write columns to
control which users can delete each public version. Users who have read-only permission for
public versions can still copy data to a private version that they can edit.
When Data Access Control is used with hierarchical data, you can switch on Hide Parents to
restrict which dimension members can be seen in the Modeler. If this option is enabled, users
will see only the members that they have at least read access to.
If you grant write access to a user, that user automatically receives permission to read the
data. Likewise, if you grant a user delete permission for a member of the Version dimension,
they also receive read and write permissions for it.

© Copyright. All rights reserved. 123

Unit 6: Defining Data Security

Figure 52: Data Access Control Example

Note:
In the preceding example, the user can change values for Pacific and Southwest
but they cannot publish.

Additional Information
Visit SAP Help for additional information on Data Access Control for dimensions.

LESSON SUMMARY
You should now be able to:
● Apply data access control.

124 © Copyright. All rights reserved.

 Unit 6

Learning Assessment

1. How is access to objects controlled?

Choose the correct answer.

X A via Roles

X B via Teams

X C In the object

2. With data access control, what permission can you set for dimension members?
Choose the correct answers.

X A Update

X B Read

X C Write

X D Manage

© Copyright. All rights reserved. 125

 Unit 6

Learning Assessment - Answers

1. How is access to objects controlled?

Choose the correct answer.

X A via Roles

X B via Teams

X C In the object

Access to objects is controlled via Roles.

2. With data access control, what permission can you set for dimension members?
Choose the correct answers.

X A Update

X B Read

X C Write

X D Manage

Dimension members can have Read or Write access set for them with data access control.

126 © Copyright. All rights reserved.