SAP BPC Embedded Configuration To SAP Analytics Cloud For Planning Migration Guide

PUBLIC
SAP Business Planning and Consolidation Embedded

Configuration to SAP Analytics Cloud for planning
Migration Guide
How to migrate from SAP Business Planning and

Consolidation, version for SAP NetWeaver / SAP
BW/4HANA in an Embedded Configuration to SAP
Analytics Cloud for planning
1 INTRODUCTION 4
2 DIMENSIONS AND MODELS 6
2.1 InfoObjects 6
2.1.1 Characteristics 6
2.1.2 Version 7
2.1.3 Time 8
2.1.4 Key Figures 8
2.2 InfoProviders 9
2.2.1 MultiProvider or CompositeProvider 9
2.2.2 InfoCube or Advanced DataStore Object (DSO), and Models 9
2.3 Aggregation levels 10
2.4 Planning Filters 10
2.5 Characteristic Relationships 10
2.6 Comments 11
2.7 BPC Embedded environment 11
3 CALCULATION LOGIC 12
3.1 Planning Function 12
3.2 Planning Sequence 14
3.3 Formula Extension (FOX) formulas 15
3.4 Exit functions 15
3.5 Currency Conversion 16
4 INTERFACES 17
4.1 Transformation 17
4.2 Process Chains 20
4.3 Master data 20
4.4 Transactional data 21
2 / 38
5 INPUT FORMS AND REPORTS 24
5.1 Query Designer 24
5.2 Analysis for Office 24
5.3 Other front-end 25
5.4 Stories in SAP Analytics Cloud for planning 25
5.5 Excel Planning and Analysis in SAP Analytics Cloud for planning 28
5.6 Recommendation 28
6 WORK STATUS (DATA LOCKING) 30
7 SECURITY 32
7.1 Analysis authorizations 32
7.2 Data Access Profiles 33
7.3 Users 33
7.4 Teams / Roles 34
8 AUDIT 35
8.1 Data Audit 35
8.2 Activity Audit 35
9 WORKFLOW 36
10 QUICK REFERENCE 37
3 / 38
1 Introduction
The purpose of this document is to provide a guideline on how to migrate from all currently supported versions of
SAP Business Planning and Consolidation, version for SAP NetWeaver in an Embedded Configuration
as well as
SAP Business Planning and Consolidation, version for SAP BW/4HANA in an Embedded Configuration
to SAP Analytics Cloud for planning.
The focus of this guide is on Planning and not Consolidation. This document also provides guidance on how to
integrate SAP Analytics Cloud with SAP S/4HANA and SAP BW.
The guide provides a breakdown of the various SAP BPC components and provides details on how to convert
them over to SAP Analytics Cloud for planning.
No specific migration tools are required since the migration will be done manually. Before starting the migration
process, it is important for the team to have a good understanding of the SAP BPC functionality and components
that need to be migrated. The target audience for this document are consultants responsible for the migration to
SAP Analytics Cloud for planning and familiar with both SAP BPC and SAP Analytics Cloud for planning.
The following scenarios are not covered in this guide:
Migration from SAP Business Planning and Consolidation in a Standard configuration to SAP Analytics
Cloud for planning
SAP ECC as a direct source for SAP Analytics Cloud for planning
Integration via SAP Datasphere
Consolidation and migration to SAP S/4HANA CLOUD for group reporting
Hybrid Planning between SAP Analytics Cloud for planning and SAP BPC is out of scope – assumption
is SAP BPC will be fully migrated to SAP Analytics Cloud for planning
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

See Legal Notice on www.sap.com/legal-notice for use terms,
disclaimers, disclosures, or restrictions related to SAP Materials
for general audiences.
This document provides information on migrating from SAP Integrated Planning (Planning Application Kit –
PAK), SAP BPC for BW/4HANA, and SAP BPC for S/4HANA (Optimized) systems to SAP Analytics Cloud for
planning.
The SAP BW - Integrated Planning system is an application that integrates planning capabilities with the SAP
Business Warehouse (SAP BW) system, powered by SAP HANA. While the initial version of the SAP BW
Integrated Planning system was launched in 2006, some of its concepts remain relevant, and the later SAP
BW/4HANA-based planning systems refer to them. The Planning Application Kit (PAK) is a tool provided by SAP
allowing the execution of the planning functions in HANA. SAP Note 1637199 provides information on using
PAK.
SAP BPC for BW/4HANA uses the SAP BW/4HANA system for storing and transforming plan data.
SAP BPC on S/4HANA (Optimized) leverages the embedded BW in S/4HANA to enhance and store planning
data. This system is designed to utilize real-time objects, including both master and transactional data, which are
created and maintained in the SAP S/4HANA system. However, it also utilizes the embedded BW system in
SAP S/4HANA to persist plan and master data as required. For further information on Embedded Business
Warehouse system refer to the link here:
https://help.sap.com/docs/SAP_S4HANA_ON-
PREMISE/029944e4a3b74446a9099e8971c752b9/5417f5bf899c4af19b159631c722373d.html
SAP BPC for BW/4HANA (Embedded) SAP BPC on S/4HANA (Optimized)
Planning application is part of BW/4HANA landscape. The planning system is embedded as part of S/4HANA
system.
BW/4HANA instance enables both real-time (making
use of HANA views) and persisted data for planning. Embedded BW is part of S/4HANA system landscape.
Supports both Finance and Operational planning Real-Time data access is using S/4HANA tables and
needs. HANA views (ACDOCA, ACDOCC, ACDOCP).
SAP note: 3228347 provides the release information SAP note: 2421749 provides documentation on the
for SAP BW/4HANA. planning system.
SAP note: 2343286 provides information on using SAP note: 2773652 provides documentation on the
Planning on BW/4HANA. Embedded SAP BW system.

2 Dimensions and Models
This chapter provides an overview of how dimensions and models can be created and mapped in SAP Analytics
Cloud for planning based on existing SAP BPC data models. It also provides guidance on how to convert the
objects from SAP BPC to comparable objects in SAP Analytics Cloud for planning. It is assumed that in SAP
Analytics Cloud for planning the ‘New Model’ type will be used.
2.1 InfoObjects
SAP BPC and BW InfoObjects are broadly divided into Characteristics and Key Figures (Units, time
characteristics and technical characteristics are the other InfoObjects). InfoObjects are the smallest units in BW.
They are used to depict information in a structured form required for creating InfoProviders (like Advanced
DataStore Objects).
For additional information on InfoObjects, refer to the help on BW/4HANA:
https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/cf15411fec1c4d069821e8e6
714a857f.html
2.1.1 Characteristics
Characteristics in SAP BPC will be re-created as Dimensions in SAP Analytics Cloud for planning. Characteristic
attributes will be re-created as Dimension properties. Special consideration needs to be taken for the Time and
Version, since the concept for these dimensions is different in SAP Analytics Cloud for planning. For all other
dimensions, it needs to be decided if the dimension should be set up as model specific dimension or as a public
dimension. It is recommended to design most dimensions as public dimensions, except for dimensions in which
the members are manually maintained or not shared across models (e.g., Audit Trail), refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/60ecbe219c89426
1bbf205892e3913d0.html#public-and-private-dimensions.
Note: There is a new Data Import API planned for Q2 2023 providing a generic API to push data into both fact
tables (public versions) and local dimension master data. With this addition, the local dimension can be used in
more scenarios.
Hierarchies in SAP Analytics Cloud for planning have to be set up as ‘Parent Child’ so they match the SAP BPC
hierarchy concept except for the time (Date) dimension which uses level-based hierarchy.
Time dependent master data are not currently supported in SAP Analytics Cloud for planning, however by
making use of alternate hierarchies, and dimension properties like start date and end date (in date format)
relevant use cases can be addressed.
Compounded InfoObjects are not directly supported, however by making use of concatenation properties during
data wrangling (to merge Dimensions), and by the use of validation rules, relevant use cases for Compounded
InfoObjects can be addressed.
For the Date dimension, hierarchies are predefined, based on the model granularity, and whether you've
enabled fiscal time for the model. You can specify a default hierarchy (level-based) in the settings for the Date
dimension.

The Version dimension does not have a hierarchy, since different versions are separate and don't have parent-
child relationships.
Note: Level-based hierarchy (like for dimension with Geographic information) can also be created for
Dimensions.
For additional details on SAP Analytics Cloud for planning hierarchies, refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/a5af17fec4f14281
88ea185a526873c0.html#parents-based-hierarchies
2.1.2 Version
SAP Analytics Cloud for planning has a different and improved version concept, in comparison to how BPC
maintained the Category.
SAP Analytics Cloud for planning Versions will be created via the ‘Version management’ feature within stories or
when importing data. Then they are displayed as members in the SAP Analytics Cloud for planning dimension.
Besides public versions, SAP Analytics Cloud for planning also allows the creation of private versions.
How to create versions in SAP Analytics Cloud for planning; refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/9d9056a13b764ad
3aca8fef2630fcc00.html
The following table lists the typical BPC Category dimension properties and how to map them to the SAP
Analytics Cloud for planning Version dimension. Mandatory properties are marked with ‘(M)’.
BPC Property SAP Analytics Cloud for Comment

planning Property
ID (M) Member ID (M) Map 1:1
SAP Analytics Cloud for planning
syntax adds “public” in front of a
public version ID, and Actual
version is called “public.Actual”.
Description (M) Description (M) In SAP Analytics Cloud for
planning, the description is the
same as the ID, but without the
word “public” in front.
Category (M) In SAP Analytics Cloud for
planning, the Category is a
property of a version, selected via
the version management, from the
following options: Actuals, Budget,
Planning, Forecast, Rolling
Forecast.
Other optional properties Other optional properties Custom mapping – in many cases
1:1. Version properties can be

added in SAP Analytics Cloud for
planning via the Modeler.
Hierarchy N/A Grouping of versions via
hierarchies is not supported in
SAP Analytics Cloud for planning.
2.1.3 Time
In SAP Analytics Cloud for planning, the Date dimension (which is the equivalent of the Time dimension in BPC),
can be either user managed, or system managed. The Date dimension is a model specific dimension in SAP
Analytics Cloud for planning and will be generated when the model is created.
For details, refer to SAP help:
https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/2022.23/en-
US/6a22f9081ab540acb9e2cdbe4112ee11.html
It is recommended to set the Date dimension as user defined. It gives more flexibility and allows the addition of
custom properties and custom hierarchies which can be used for reporting. For both the user managed or
system managed setting, SAP Analytics Cloud for planning will generate dimension members, properties and
hierarchies, so they don’t need to be manually created.
The mapping table below shows the mapping for the most common planning scenarios, when planning on a
periodic or monthly level. Since SAP Analytics Cloud for planning generates all required Date dimension
properties, only reporting specific custom BPC properties need to be added:
BPC Property SAP Analytics Cloud for Comment

planning Property
ID (M) Calendar Month (M) Map 1:1. As needed adjust format

Additional mandatory properties SAP Analytics Cloud for planning No mapping is needed since SAP
system generated properties Analytics Cloud for planning
generates all required properties.
Custom properties for reporting Custom properties for reporting Re-create and map as needed
2.1.4 Key Figures

Like Key Figures in SAP BPC, a Measure in SAP Analytics Cloud for planning is a dimension that represents
transactional data. A measure by itself does not make the information complete, but with other Dimensions in a
table it provides the information like what is being measured (Amount, Quantity).
Measures are exposed as single entities, and you can add and configure multiple measures with aggregation
and units to fit your data.
Like re-creating a Characteristic, a Key Figure in BPC will have to be re-created as a Measure in SAP Analytics
Cloud for planning.
For additional information on Dimensions and Measure, refer to SAP help:

1bbf205892e3913d0.html
2.2 InfoProviders
In BPC, InfoProvider are generic objects from which data can be queried through Query designer or Business
Explorer (BEx) tools.
2.2.1 MultiProvider or CompositeProvider

A MultiProvider combines data coming from different InfoProviders: InfoCubes (can be virtual providers also),
Datastore objects, InfoObjects, InfoSets, Aggregation levels.
A CompositeProvider is an InfoProvider which combines data from SAP HANA views or from other InfoProviders
(like aDSO) and makes the data available for reporting and analysis.
These are virtual objects, meaning that they do not persist the data from its underlying objects (InfoProviders
and/or SAP HANA views). They act as a view to connect two or more sets of data for reporting.
In SAP Analytics Cloud for Planning, there is no direct comparable object to a CompositeProvider. In SAP
Analytics Cloud for Planning, models host data, and two models can be linked and analyzed through “Blend
data” or used in formulas through “Link formulas”.
Refer SAP help link for Data blending
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/7b9defa34dc34c08
81dee863e6b4e5c5.html
For linking Dimensions across Multiple Models, refer to SAP help link
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/8c8691c24ade40d
580a4b2017e67110d.html
Refer SAP help link for “Link formulas”

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/c921b1cb94d146e
6abd996286d0e0bf7.html
2.2.2 InfoCube or Advanced DataStore Object (DSO), and Models

An InfoCube or DataStore Object (DSO) are multi-dimensional objects in SAP BPC that are used for planning
and reporting. InfoCube is based on extended star-schema design and was used extensively for data analysis in
SAP BW systems before HANA. It contains Characteristics (under separate Dimensions) and Key Figures.
An InfoCube or DataStore Object in SAP BPC that contains Characteristics and Key Figures is similar to a
Model that contains Dimensions and Measures in SAP Analytics Cloud for planning.
SAP BPC DataStore Object needs to be re-created as a Model in SAP Analytics Cloud for planning using
dimensions and measures. The dimensions that are used to build the model can either be public or private. For
details refer to SAP help link:

1bbf205892e3913d0.html#public-and-private-dimensions
The method employed in SAP Analytics Cloud for planning has resemblance to the SAP BPC approach. In SAP
BPC, Characteristics and Key Figures can be used in one or more DataStore Objects. In the case of SAP
Analytics Cloud for planning, Public Dimensions can be used across multiple models
When creating a new planning model in SAP Analytics Cloud, it is recommended to choose the ‘New Model
Type’. For details on how to create a new model refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/3ee0b7055e7d400
bb08c7fda6f0f643a.html
Similar to how a BPC DataStore Object can contain multiple key figures, the New Model type in SAP Analytics
Cloud for planning can also contain multiple Measures. This provides the option to add and configure multiple
Measures with aggregations and units to better fit the data.
When migrating from SAP BPC, it needs to be decided if a single Measure should be used or if the architecture
should leverage multiple Measures. For the benefits of this approach, refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/22af95d0151c494
6b132d4e904b1e32a.html
2.3 Aggregation levels

These are virtual layers created as data subsets on top of an InfoProvider (CompositeProvider, MultiProvider) to
enable planning. This contains a subset of Dimensions and Key Figures from its underlying InfoProvider.
There is no equivalent for this in SAP Analytics Cloud for planning, since the planning tables, charts and data
actions are directly created on top of a Model.
2.4 Planning Filters

Planning Filters are used to restrict data from Aggregation level by making use of specific Master data level
filters or Variables. These filters can be applied for building a query or for building a planning function.
In SAP Analytics Cloud for planning, planning table filters are applied in the Designer Builder panel after the
Rows and Columns section.
For a Data Action, Filters can be used to restrict members or parameters for a Dimension. For Advanced
Formulas, the filters are under the Context section of the visual editor or can be added in the script.
2.5 Characteristic Relationships

You can use characteristic relationships to define rules to check permitted combinations of characteristic values
for each real-time InfoCube or each DataStore object for direct updates in planning mode. You can also define
rules for the system to use to derive values from one characteristic to another.
There are 4 types of characteristic relationship settings in BPC: 1) Attribute, 2) Hierarchy, 3) DataStoreObject, 4)
Exit
Validation Rules in SAP Analytics Cloud for planning, provide similar dimension based relational data validation.

There are two types of Validation Rules in SAP Analytics Cloud for planning: Validation Rules with Existing
Attributes and Validation Rules by Combining Dimension Members. The first type is similar to the BPC
characteristic relationship of type attribute. The second type is comparable to the BPC characteristic relationship
of type DataStoreObject, with the exception that only combinations from three characteristics can be utilized,
and those combinations are saved in the model rather than in a separate DSO. A notable advantage in SAC is
that the valid combinations can be specified with reference to hierarchy nodes.
For defining a valid member combination for planning using Validation Rules and to create a new Validation
Rule refer to the below SAP help link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/e275adffd7f14151
a97721d83f4a865c.html
2.6 Comments
There is more than one way to create comments in BPC Embedded: a new DSO to host comments can be
created or a new Document Store can be created to store comments.
In SAP Analytics Cloud for Planning, adding comments to a data cell does not require any additional
configuration. The SAP help link below provides the method to add a comment to the data cell.
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b6cd7dfffb9c4ac7b
fe6739b22ff45ce.html
The comments can also be displayed and edited like a dimension in a table. For more information on how to
enable this, refer to the SAC help link.
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/ee4c734f5c104f34
9009f176973273f7.html
In addition, a Comment widget can also be created. This will enable you to add comments related to your data
and also display data point comments through the widget as demonstrated in the SAC help link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/28fbd6a2eccc46f9
96778240aaef0a2e.html
2.7 BPC Embedded environment

Environment is like a base area created which does not contain physical data records. Models and Dimensions
can be created from the Environment. This can be accessed through the web-client of BPC.
In SAP Analytics Cloud for Planning, there is no direct correlation to these components. The Model Dimensions
are created from the SAC Analytics Cloud for planning web interface as mentioned in the above sections.

3 Calculation Logic
This chapter goes over the back-end calculations that are used in BPC and how they can be effectively
replaced in SAP Analytics Cloud for planning. SAP Analytics Cloud for planning leverages dimensionalized,
easy to create models along with calculations that can be used to copy data, allocate or to run custom logic
through scripting. Through design (model and functionality-based approach) and through the application of data
actions, BPC calculations can be re-created in SAP Analytics Cloud for planning.
3.1 Planning Function

Planning functions in BPC enable system-supported editing and generating of plan data. There are different
types of standard planning function types available. For a detailed list of the types of Planning functions and how
they can be used refer to the help link below.
https://help.sap.com/docs/SAP_BW4HANA/ee8f1a1acc9f46f39b7c79eef625ada2/4cae4fd8dd6e3b9ee10000000
a42189b.html
In SAP Analytics Cloud for Planning, Data Actions perform the edit and update of plan data. Here is an overview
of core data action features available in SAP Analytics Cloud for Planning:
Feature Description
Copy Steps Lets you copy values from one part of a model to another based on a set of filters,
aggregation settings, and copy rules.
Cross-Model Copy Lets you copy data from one model to another based on a set of filters and automatic
Steps or manual mapping between dimension members.
Allocation Step Lets you run an allocation step as part of your data action.
Embedded Data Lets you run another data action as a step in your data action.
Action Step
Conversion Step Lets you copy data while applying currency conversion in a model with measures.
Advanced Formulas Lets you create a script of transformations and calculations to apply to the model
Step data. You can use either a script editor or a visual designer.
Parameters Lets you replace members, measures, or numeric values in your data action. There
are two types:
Fixed parameters let you quickly change a value that appears in multiple
places.
Dynamic parameters let you set a value when running the data action or
when setting it up to run.
Data Action Triggers Allows to run the data action from a story, and optionally publish the target version.

Feature Description
Automatic Data Allows you to define the start time or schedule a recurrence for data actions to run
Action Tasks automatically.
The following are the general steps available to set-up and run a data action.
Copy step: This type of step copies data within a model based on a set of rules, filters, and aggregation settings.
For example, you can use it to copy data from 2022 to 2023. To learn how to create a copy step refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b5720be6f2ed411
78762973df9e4af16.html
Cross-model copy step: With this type of step, you can copy data from a different source planning model based
on a set of filters and automatic or manual mapping between dimension members. For example, you can bring
together data from headcount and expense planning models into a central finance model. To learn how to create
a cross-model copy step refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/694a8e81205245a
19d78d8b1acdffbba.html
Allocation step: This type of step lets you run an allocation step as part of your data action. It allocates values
from a source dimension to a target dimension by driver values, or by direct assignment. For example, an
allocation step can help allocate overhead costs to different departments. To learn how to add an allocation step
to data actions, refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/87a9cca86cb546bf
99b6b43131934d50.html
Embedded data action step: With this step, you can run another data action as a step in your data action. For
example, you can quickly reuse a common set of steps in several different data actions, or multiple times within
a single data action. (Multi actions are also available to run multiple data actions in sequence, along with
predictive and publishing steps.) To learn how to create an embedded data action step refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/121b544d5e2440a
4b2ef3bd09d6a7fa8.html
Conversion step: For models with measures, conversion steps let you copy between measures while applying
currency conversion. To learn how to create a currency conversion step refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/10a9f662ce5c4d05
b6ba31cd4ae80668.html
Advanced formulas step: Each step lets you create a script of transformations and calculations to apply to the
data within defined scopes of the target model. They let you carry out planning and simple consolidation tasks

like cash flow planning, accounts receivable planning, and carry forward operations. You can build simple
advanced formulas using the visual editor or get full control using a script editor. To learn how to create an
advanced formula step refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/4af8f5afbaf541f58
21107eb772a5224.html
Data actions can be triggered either in an SAP Analytics Cloud story or analytic application, from a calendar task
or as part of a multi action. Once triggered the data actions can be monitored to see if it ran successfully or not.
For information more data action execution and monitoring details refer to the link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/1f389f2c67054a7c
926ea28b2fa89833.html
3.2 Planning Sequence

In BPC, Planning functions can be grouped in a specific sequence to perform data calculations in the required
order. You use this function to automate the sequential processing of a user-defined number of planning
functions that you have defined. This is useful if you want to regularly carry out certain complex operations on
your data.
In SAP Analytics Cloud for planning, Multi action can be effectively used to accomplish this. Multi actions
provides a way to run multiple data actions in sequence from a story (or analytics designer) through a Planning
trigger. The below SAP help link provides the steps to add Multi action.
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b1a98c566bc64ce
78871ee3c0b559d6f.html#get-to-know-multi-actions
You can also use an Embedded data action to replace a Planning sequence. Embedded data actions will also
let you run multiple data actions with different parameter values. But unlike multi actions, they only work on a
single version and model at a time, and they can only publish that version at the end of the operation.
When a planning trigger is selected, there will be options to configure a Data Action or a Multi Action or to run a
Planning sequence directly from a BPC live data connection.

3.3 Formula Extension (FOX) formulas
FOX calculations are user friendly simple scripts in BPC that are used for data calculations or transformations to
apply within the defined scope of plan data. Example: Rate times Volume for Sales. In addition to the formula
operators, the FOX formulas offer you the possibility to make statements dependent on conditions and to run
through loops.
In SAP Analytics Cloud for planning, Advanced Formulas from Data Action can be used to accomplish similar
calculations. To learn how to add an advanced formula step to your data action refer to link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/4af8f5afbaf541f58
21107eb772a5224.html
Advanced formula step provides two different ways of creating the formulas: Visual and Script. The visual format
provides a way to drag and drop graphic elements to create the formulas. Script provides an option to use
simple coding to create formulas for the data action step.
The below link provides easy to follow steps with examples for advanced formula:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/afe93e3cf1414a7b
8419baad11cc066e.html#loioafe93e3cf1414a7b8419baad11cc066e
3.4 Exit functions

Exit functions are created with ABAP programming language (Function modules). They help with advanced
calculations in BPC and to use data from outside the InfoProvider (tables, other InfoProviders) for calculations.
In SAP Analytics Cloud for planning, there is no direct equivalent for an ABAP Exit, however calculations can be
accomplished by making use of design approach - simplified multiple models, Advanced formula step and if
needed by making use of Analytics Designer.
For detailed information on Analytics Designer refer to link:
https://d.dam.sap.com/a/3Y16uka/DeveloperHandbookSACAnalyticsDesigner_v12.1_final.pdf
For complex data calculations on large volumes of data, SAP Analytics Cloud for planning allows bi-directional
integration with SAP PaPM (Profitability and Performance Management) and with SAP Datasphere.
SAP Profitability and Performance Management maintains and executes complex calculations, rules, and
simulations. As of 2022.Q4, SAP Analytics Cloud introduced a new feature called API step in Multi Actions.
Through this feature you can make use of SAP PaPM Cloud’s configured process directly from SAC Story. Refer
link for details on SAP Analytics Cloud and SAP PaPM integration.
https://blogs.sap.com/2022/12/05/sac-and-sap-papm-cloud-integration-in-a-nutshell/
SAP Datasphere is the next generation SAP Data Warehouse Cloud that helps with harmonizing heterogeneous
data into business semantic models. For information on bi-directional integration of SAP Datasphere and SAP
Analytics Cloud for planning, refer to the link:
https://help.sap.com/docs/SAP_DATASPHERE/c8a54ee704e94e15926551293243fd1d/f589cdea41674badaecf
a1bf02571b6f.html

3.5 Currency Conversion
In BPC, Currency conversion can be achieved by making use of the standard planning function type. In addition
to this, exchange rates can be maintained in BPC and using additional planning functions, impacts due to
currency translation can be analyzed. For example: Impact due to inflation, comparison between Plan rate and
Actuals rate.
For further details on Currency translation through the BPC planning function type refer to link:
https://help.sap.com/docs/SAP_BW4HANA/ee8f1a1acc9f46f39b7c79eef625ada2/4cadb958d5943b9de1000000
0a42189b.html
In SAP Analytics Cloud for planning, you can use two methods to convert currency data:
1) Conversion measures that recalculate values from a base measure. In this case, entering data on one
measure changes the other.
2) Conversion steps in data actions that copy data from a base measure, convert it, and paste it to a target
member. In this case, the data is stored separately.
Refer to the below link for detailed information on currency conversion:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/92cab98504dc479f
b19740a2715241bd.html

4 Interfaces
Interfaces enable movement and transformation of external data from other systems to the Planning system.
Data transformation structures allow you to format and map source data to planning data structures.
There are functional similarities and some differences in how different SAP BPC systems interface (and
transform) data. In essence SAP BPC systems use the underlying SAP BW application to source, transform and
enhance the data.
4.1 Transformation
In SAP BPC, BW system acts as the system to host data, integrate from various sources, and transform.
Depending on the data warehousing strategy, you can extract and transform the data from the source and load it
into the SAP NetWeaver BW system, or directly access the data in the source for reporting and analysis. The
process of physical data acquisition is known as Extraction, Transformation and Loading (ETL).
In SAP Analytics Cloud for planning, data wrangling allows you to perform the transformation and mapping of
external data that is loaded to the Model or to the Dimensions. Two types of connections are possible in SAP
Analytics Cloud: Live data connection and Acquired data connection. SAP Analytics Cloud for planning operates
on acquired data.
This section covers the different transformation aspects of SAP BPC. SAP BW/4HANA is used here for
reference, but the concepts are same across SAP BW systems.
Data preparation using BW/4HANA
Source systems
Different data sources are connected with the SAP BW/4HANA using Source systems. Source systems in SAP
BW/4HANA enable the connection to a source for the data transfer. This provides the interface for extracting
and transferring data from many sources.
For information on Working with Source Systems, refer to the BW4Hana help link:
https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/aefee5c9097e4b1480ef3d0
df80dc336.html
DataSources
To access data from a source, and to transfer the data to the SAP BW/4HANA system - the metadata of the
source object must be available in the system in the form of a DataSource. You can create and edit
DataSources through BW Modeling tools.
For information on Working with DataSources, refer to the BW4Hana help link:
https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/06018b8447844e499e2a3b
a2dcf1aa59.html
Transformation
Transformations are used in the data transformation process to consolidate, clean, and integrate the data.
Through Transformation data can be semantically integrated from various sources. You create a transformation

between a source and a target. When data is loaded from an SAP BW/4HANA object or virtual object to a target
SAP BW/4HANA object, the data passes through a transformation. A transformation converts the fields of the
source into the format of the target.
For additional information on Transformation, refer to the BW4Hana help link:
https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/4a1df3235c171b40e100000
00a42189c.html
Data Transfer Process
A Data Transfer Process (DTP) is an object that determines how data is transferred between two persistent
objects (source and target). Transformations and filters control this process (mapping, data filters). You can
create a transformation between the source and the target of the data transfer process.
For additional information on Data Transfer Process, refer to the BW4Hana help link:
https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/4a28032afa9147dbe100000
00a42189c.html
SAP Analytics Cloud for planning data preparation
There are four main steps in the import process: creating an import job, preparing the data, mapping the data,
running the import.
Data can be imported from either a file or a data source. If importing data from a data source, make sure to
select an existing connection, or create a new one. For more information on how to import data to a model, refer
to the SAC help link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/a8435da6970041d
2beb3299cdcff7026.html#loioa8435da6970041d2beb3299cdcff7026
The data preparation task is where data quality issues are resolved and data transformation is updated, before
the mapping task.
For transformation, the context-sensitive editing features can be used to edit data in a cell, column, or card
format. When selecting a column, a cell, or content in a cell, a menu will appear with options for performing
transforms. This menu is two-fold:
Choose the “ Quick Actions” option to perform actions such as duplicate column, trim whitespace,
hide columns, or delete columns or rows. The table below lists all the available actions.
Select the “ Smart Transformations” icon to list suggested transformations to apply to the column,
such as replacing the value in a cell with a suggested value. The transformation bar is used to edit and
create transformations.

Transformation Description
Delete Rows Delete rows in the data, either by selecting individual members, or by specifying a
range (not possible for text columns; only numerical and Date columns).
Trim Whitespace Remove spaces, including non-printing characters, from the start and end of strings.
Duplicate Column Create a copy of an existing column.
Delete Column Delete a column. Use the Shift key to select and then delete multiple columns.
Remove duplicate Remove duplicate rows when creating or adding data to a model.
rows
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.
Extract Use this transform to extract a block of text specified as numbers, words, or targeted
values within a column to a new column.
Change Change a column to uppercase, lowercase, or title case.
Replace Replaces either an entire cell or content that could be found in multiple different
cells.
A calculated column can be prepared based on another column, through the application of a formula expression.
Click from the menu toolbar and use the Create Calculated Column interactive dialog to build a calculated
column. This can be created through either selecting an entry from Formula Functions (from the right panel) as a
starting point or typing “[" to view all the available columns. Press Ctrl + Space or Cmd + Space to view all the
available functions and columns.
If necessary, this can be edited later by clicking Edit Formula in the Designer panel.
For a listing of Supported Functions for Calculated Columns, refer to SAC help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/8b8f9ce9952a450
ebd12b81cf5b608b7.html

4.2 Process Chains
A process chain is a sequence of processes that are scheduled in the background for an event. Some of these
processes trigger a separate event that can, in turn, start other processes. In SAP BW/4HANA system, process
chains help with:
automating the complex process flows through event-controlled processing

visualize processes using network graphics
centrally control and monitor processes
Process chains are typically used to sequence a data load and data transformation job process and schedule it.
For further information on Process chains, refer to the BW4Hana help link:
https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/6713843b74f7be0fe100000
00a114084.html
In SAP Analytics Cloud for planning, data import to a model can also be scheduled. To schedule a data import
job to a model, refer to the SAC link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/75683f452594426
bb05cb49dc4c5af99.html#loioccd43f59f3c140948b67534668001b79
In SAP Analytics Cloud for planning, there are calendar functions through which a job can be scheduled. Data
Actions and Multi Actions can be used to transform the data in the SAP Analytics Cloud for planning models.
Data Actions are a flexible planning tool for making structured changes to model data in SAP Analytics Cloud for
planning, including copying data from one model to another. The SAC link provides the method to schedule a
Data Action:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/de944ce1189543e
5858798036d576094.html
Multi Actions link together a sequence of steps such as data loads, data actions, version management steps,
and predictive steps, which all run from a single planning trigger. They can be scheduled to run at specific
periods. The SAC link provides the method to schedule a Multi Action.
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b4d2b021719f4d9
58afd0922ac7de8d1.html
4.3 Master data
Flat File import of master data
In SAP Analytics Cloud for planning, a model can contain public or private dimensions. A private dimension can
have the data uploaded during uploading the data in the model or by directly adding it through copy/paste from
another spreadsheet in the dimension maintenance screen.
Master data for a public dimension can be imported from a flat file; refer to SAC help:
2beb3299cdcff7026.html#import-data-into-public-dimensions

Import of master data from SAP BW or SAP S/4HANA
For SAP BW or SAP S/4HANA, the import of master data to SAP Analytics Cloud follows the same steps as the
load of data for a public dimension from flat file. Since the source is different, when selecting the step to import
data, select the connection created for SAP BW or SAP S/4HANA and assign it to the query (like the data import
to a model).
For a list of available OData services from SAP S/4HANA system, refer to the link:
PREMISE/48f4b4785b8e45938ac44a67be8032d9/9965a647179a4e5a95e081f3e93c89b4.html
4.4 Transactional data

Data can be imported from flat files, SAP data sources and certain non-SAP data sources.
For a detailed list of the data sources that can be imported and the methods to import, refer to the SAC help link:
2beb3299cdcff7026.html
Flat File import of transactional data
In SAP Analytics Cloud, a step-by-step process to upload a flat file; refer to the SAC help link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/4c002a6b954d43f
18f3712cb10ac3cdc.html#concept_n2m_ytv_ktb__section_jqd_32w_ktb
If the file will be imported from a file server, refer to:
2beb3299cdcff7026.html#loio64d1902675ea45868c4e1127788d578c
An SAP Analytics Cloud agent must be installed as a pre-requisite to install SAP Analytics Cloud Agent, refer to:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/7c35129451f5432
194773adac7f89598.html
Flat File export of transactional data
For SAP Analytics Cloud for planning, the data from a model can be exported to a flat file; refer to the SAC help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/be55df472f9d4a31
b94f5dda47300e81.html#concept_u1q_wjy_stb__section_ycl_rly_stb
Note: Data from an SAP Analytics Cloud for planning table can also be downloaded to a flat file; refer to the
SAC help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/ff5f1e052b5e400d
a990dad8408604da.html
Import of transactional data from SAP BW
For steps to import SAP BW data to an SAP Analytics Cloud for planning model, refer to the SAC help:

18f3712cb10ac3cdc.html#concept_jbd_ztv_ktb__section_rsv_13w_ktb
Export of transactional data to SAP BW
For steps to export SAP Analytics Cloud for planning data to SAP BW and SAP BW/4HANA, refer to the SAC
help:
b94f5dda47300e81.html#concept_dwb_bly_stb__section_gkk_wly_stb
The writeback method is also detailed in the SAP note 2838883:
https://launchpad.support.sap.com/#/notes/2838883
Import of transactional data from SAP S/4HANA
For steps to import SAP S/4HANA data to an SAP Analytics Cloud for planning model, refer to SAC help:
18f3712cb10ac3cdc.html#concept_mv1_ztv_ktb__section_psv_13w_ktb
Export of transactional data to SAP S/4HANA
For steps to export SAP Analytics Cloud for planning data to SAP S/4HANA, refer to the SAC help:
b94f5dda47300e81.html#concept_lnj_xjy_stb__section_i1g_vly_stb
The delivered OData services for exporting data from SAP Analytics Cloud to SAP S/4HANA, refer to the SAP
S/4HANA help:
PREMISE/48f4b4785b8e45938ac44a67be8032d9/15447e5bda934be28f3b16cfb456fb23.html
Import of transactional data from other sources
There are several other data sources from which data can be imported to SAP Analytics Cloud for planning
models.
For a list of available systems from which data can be sourced, and the steps to import data, refer to the SAC
help:
18f3712cb10ac3cdc.html
Import of exchange rates
Steps to import currency conversion data for SAP Analytics Cloud for planning, refer to SAC help:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/62b4e4d19daa4f0
4b92d2e89812df4ed.html
The supported data sources for the currency conversion table are provided in the SAP note 2960126:
https://launchpad.support.sap.com/#/notes/2960126
Note: There is also a Data Export Service API that enables data export from SAP Analytics Cloud to other SAP
and non-SAP systems. For more information, check out the documentation on the API from the link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/14cac91febef464dbb1efce20e3f1613/db62fd76514b48f8b
71d695360320f4a.html

5 Input Forms and Reports
Input forms are user interfaces for data entry processes. They enable data collection via manual data entry. On
financial planning projects, the input forms are mainly used to enter budget, plan or forecast data or to adjust
data previously loaded or inputted.
Reports are the final data visualization after loading, input, calculations, and adjustment processes. They
retrieve the scope of data needed for the financial presentation books.
5.1 Query Designer

In BPC, reports and input forms are based on BW queries. BW queries, depending on the underlying BW
version on which BPC runs, can be created in BEx Query Designer or in the Query Designer of the BW
Modeling Tools in Eclipse. Both tools operate on the same metadata and have almost the same features.
A query is the formal definition of a multidimensional query. You use analytic queries to analyze the data in the
SAP BPC.
For input forms, the queries must be input-ready, and the key figures need to be marked as input enabled as
well.
For creating queries in general, refer to the SAP BPC help:
https://help.sap.com/docs/SAP_BW4HANA/ee8f1a1acc9f46f39b7c79eef625ada2/638178abd28c4b84a3a7541d
c152a13d.html
For creating input-ready queries, refer to the SAP BPC help:
https://help.sap.com/docs/SAP_BW4HANA/ee8f1a1acc9f46f39b7c79eef625ada2/54080d6ad0e74bfc89071c1cc
6451f52.html
Using query designer global reusable query objects, like the calculated and restricted key figures can be created
and made use of in multiple queries. In SAP Analytics Cloud for planning, formulas and calculations can be
created, and used. For further information on Formulas and Calculations, refer to the link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/8fb861fb93184337
8190469759d25f39.html
5.2 Analysis for Office

In the context of SAP BPC, Analysis for Office is an add-in for Microsoft Excel that allows users to access and
analyze data stored in BPC systems. Specifically, in the embedded configuration of SAP BPC, Analysis for
Office can be used to create reports and perform analysis on data that is stored in BPC by consuming directly
infoproviders and aggregation levels.
With Analysis for Office, users can connect to BPC data models and build complex reports that include charts,
tables, and other visualizations. Users can also use the add-in to perform what-if analysis, scenario planning,
and other modeling related tasks (for example control the workstatus of a data region).
Overall, Analysis for Office is a powerful tool for SAP BPC users who need to work with data stored in BPC and
perform complex analysis and reporting tasks within Excel.
For creating reports and input templates with Analysis for Office, refer to the SAP help:
https://help.sap.com/docs/SAP_BUSINESSOBJECTS_ANALYSIS_OFFICE/ca9c58444d64420d99d6c136a3207
632/ebf198667aa54740b9049d9da804a901.html

5.3 Other front-end
There are several reporting tools available for generating reports and input templates on SAP BW-IP, BPC
embedded, and BPC optimized, including both newer and older tools. Here are some of the commonly used
reporting tools:
Bex Analyzer: It is a Microsoft Excel-based tool that allows users to create reports and input templates
using SAP BW data. Bex Analyzer is one of the oldest and most used reporting tools in the SAP BW
environment, and it can be used with both BW-IP and BPC.
Web Application Designer: It is a web-based tool used for designing and developing custom web-based
applications using data from SAP BW-IP, BPC embedded, and BPC optimized. It can be used to create
interactive dashboards, reports, and input templates using various data sources.
SAP Analysis for Microsoft Office: It is a Microsoft Excel-based tool that allows users to interact with
data in SAP BW-IP, BPC embedded, and BPC optimized. With this tool, users can create reports, input
templates, and data slices using Excel functions.
SAP BusinessObjects Analysis for Office: This tool is similar to SAP Analysis for Microsoft Office and
provides same functionality. However, it is a standalone application that does not require Microsoft
Excel.
SAP Lumira: It is a self-service data visualization tool that can be used to create interactive dashboards
and reports. It can be integrated with SAP BW-IP, BPC embedded, and BPC optimized to extract data
and generate visualizations.
SAP Web Intelligence: It is a web-based reporting tool that allows users to create interactive reports and
dashboards. It can be integrated with SAP BW-IP, BPC embedded, and BPC optimized to extract data
and generate reports.
SAP Design Studio: It is a web-based application for creating interactive dashboards and applications. It
can be integrated with SAP BW-IP, BPC embedded, and BPC optimized to extract data and generate
visualizations.
SAP Analytics Cloud: It is a cloud-based analytics tool that allows users to create interactive dashboards
and reports. It can be integrated with SAP BW-IP, BPC embedded, and BPC optimized to extract data
and generate visualizations. The use of SAC as a front-end client against a BPC embedded back-end is
often referred to as a hybrid scenario.
5.4 Stories in SAP Analytics Cloud for planning

In SAP Analytics Cloud for planning, input forms and reports are developed via the stories. There is no
segregation between tools to create queries and tools to visualize as it is in BPC. The story concept fulfills both
aspects.
A story is a presentation-style document available with the web front end of SAP Analytics Cloud for planning. It
looks like a workbook with several sheets, it helps to visualize and analyze data, and enter data as well.
Many types of objects can be inserted in story pages:
Tables (This object is used to develop data reports or input forms)

Charts
Input Control (object to select dimension members)
Geo Map
Image
Shape
Text

Planning Trigger (to run Data Actions)
….
For creating stories, refer to the SAP Analytics Cloud Help:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/29e0feaf17584e11
8ef30e6102008224.html
Find below a mapping table of design capabilities in both tools
Query Designer/Analysis for SAP Analytics Cloud for planning Comments / Links
Office (AFO)
Query Edit/Designer/Builder/Table The Builder, in story edit mode, is

Structure the closest concept to a query
Edit/Designer/Builder/Property
Query element properties
Input Schedule Story/Table Activate planning option in the SAP
Analytics Cloud model settings to be
able to input data.
Story/Table
Report
AFO Dynamic Chart Story/Chart
AFO Info Fields Dynamic Texts
Query Designer/Sort Select a dimension cell in a table Refer to the SAP Analytics Cloud
Help to sort value:
Right-click and then select Sort
Options Value Sorting https://help.sap.com/docs/SAP_ANA
LYTICS_CLOUD/00f68c2e08b941f0
81002fd3691d86a7/a0426a71d5c94
aba882a852b3e4ddec7.html?q=Sort
AFO Components properties Edit/Designer/Builder/Property
AFO Filter Edit/Designer/Builder/Filters
AFO Styles Edit/Designer/Styling For Story Preferences, refer to the

SAP help:
Story Preferences
https://help.sap.com/docs/SAP_ANA
81002fd3691d86a7/d1ab3f5e52284e
149da16a0aff691fbc.html

AFO Calculations Custom Calculation Custom calculations are local
member calculations that are
executed at run-time.
For custom calculations, refer to the

SAP help:
https://help.sap.com/docs/SAP_ANA
81002fd3691d86a7/ef59af374b494b
66a7659d267b0b8bd8.html
Infoobject attribute Property selection from the Simply select in SAP Analytics Cloud
Dimension the dimension property to display it
in the report
Advanced developments
SAP BPC custom development for reports or input schedules are generally implemented using VBA Excel
macros because EPM Add-in is an Excel Add-in.
To personalize the user interface in SAP Analytics Cloud for planning, use Analytic Designer. This module helps
to turn the stories into real applications.
Analytics designer can help build modular, user friendly and custom-tailored applications and facilitate the end-
user navigation:
Combine convenient story features with comprehensive scripting capabilities
Create advanced applications for data entry using input forms
Guide users through self-explaining applications
Integrate calendar task management into planning applications
Trigger data actions based on events
Enable responsive planning applications on mobile devices
For Analytic Applications and Analytics Designer, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/25a3b8d145864d7
faf7447b916e492e7.html
The new Optimized Story Experience unifies story and analytic applications to provide a more sophisticated
story with guided dashboard and planning applications. This is in General Availability with wave 2023.3.
For details refer to the blog:
https://blogs.sap.com/2023/02/15/unifying-story-and-analytic-application-with-the-new-optimized-story-
experience-in-sap-analytics-cloud/

5.5 Excel Planning and Analysis in SAP Analytics Cloud for planning
Because spreadsheet interfaces remain the most popular FP&A tool, SAP developed an SAP Analytics Cloud
add-in for Microsoft Office.
SAP Analytics Cloud Excel Add-in helps to:
▪ Retrieve SAP Analytics Cloud versions
▪ Plan data to SAP Analytics Cloud models with a familiar Excel and SAP Analytics Cloud user experience in
real time
▪ Publish/revert data for public versions
▪ Support mass data entry mode
▪ Business logic execution via Data Actions
A new SAP Analytics Cloud for planning Add-in function has been released to retrieve data at the cell level.
SAP.GETDATA
Returns the data value for the specified dimension and member combinations
To know more about SAP Analytics Cloud Excel Add-in, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD_OFFICE
SAP Analysis for Microsoft Office (also known as AO):

Continues to be an important add-in for multiple data sources like SAP BW, SAP BPC, SAP S/4HANA, SAP
S/4HANA Cloud for group reporting. It is designed for financial analysts who require advanced capabilities in
Microsoft Excel. It can also be used with SAP Analytics Cloud.
However, most enhancements for an add-in connecting to SAP Analytics Cloud will be delivered on SAP
Analytics Cloud for planning, add-in for MS Office.
5.6 Recommendation
Various front ends for planning and analysis exist for SAP Analytics Cloud.
For this need: Use this front end:
Ad hoc analysis and planning SAP Analytics Cloud add-in Excel / Analysis for
One or few users involved Office
Excel integration is key for many users
Executing the planning process SAP Analytics Cloud Story

Multiple users entering & collaborating in the planning LoB & Corporate owned solution
process

Guided planning solution SAP Analytics Cloud, analytics designer or Story 2.0
When specific use cases require a high degree of Highly customizable for end-user guidance
customization Implementation effort

6 Work Status (Data locking)
Work status in BPC facilitates better information management by controlling plan data entry and locking data
entry at required cross-sections of a model. Work status helps with preventing unwanted data changes (locking)
once the data entry is finalized.
Purpose of work status:
Allows seamless tracking of processes during planning.

Eliminates the need for complex security models to lock the data once the data is finalized.
Work status can be enabled or viewed by Data Lock settings. To enable or modify work status for a model,
select the model and choose Edit. Data locking can be enabled, and dimensions selected to lock the process
context, or disable data locking.
For further information on work status for BPC, refer to BPC help:
https://help.sap.com/docs/SAP_BUSINESS_PLANNING_AND_CONSOLIDATION,_VERSION_FOR_SAP_NET
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c335371ad165792e10000000a15822b.html
In SAP Analytics Cloud for planning, Data Locking provides the same purpose as work status in BPC.
A planner with appropriate permissions to work with data locking can set up data locking and specify areas of a
model data to lock, restrict, and unlock, and can also delegate ownership of data locks to other planners.
For the data locking feature in a model to be enabled, the Data Locking setting must be enabled through the flip
switch. This can be found under the Model preferences (the wrench icon in the toolbar) under Access and
Privacy.
Once the data locking feature is enabled, the Configure Data Locks icon will become available under the Data
section of the top toolbar for a Model.
To enable data locking by model, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/e07d46e950794d5
a928a9b16d1394de6.html
For an example scenario for lock setting; refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/0743b75a496447e
190bac00f5e075002.html
Scheduling data locks in the Calendar
SAP Analytics Cloud for planning provides a built-in calendar to enhance the planning process.
Users can:
Create tasks, assign them to users, set due dates, and monitor the progress.
Create processes and add tasks or other processes to them.
o A process is an aggregation of all the events that it contains, these can be tasks or other
processes. The process gives a high-level view of how much work is completed and how much
remains.
Schedule automatic tasks for system activities like data locking, data actions, or multi actions.

Data locking can be scheduled in a calendar.
For the context, procedure and prerequisites to set up data locking in a calendar, refer to the SAC link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/91fa3cbbd46d457
ab04f9ef3c7901655.html

7 Security
SAP Analytics Cloud uses users, roles, teams, tasks, licenses to manage application security and capabilities.
Roles are collection of tasks permissions that allow system admins to control available features by users
(or teams).
The roles given to an user or to a team the user belongs to determine which are the features available
for users.
Depending on the specific tasks in a role, a type of license will be used when a user having that role
uses the system
Permissions are authorizations that can be granted to resources, or individual objects. There are two
types of permissions:
o Object Type Permissions: For most SAP Analytics Cloud objects, permissions apply to all
objects of a particular type. For example, if a user is granted the Read permission for Digital
Boardroom objects, that user can open and view any Digital Boardroom presentations that have
been shared with them.
o Individual Type Permissions: Grant these permissions “only” for objects that users already own.
For example, if users are granted Delete permission for dimension objects, those users can
delete any dimensions they own.
SAP BPC Security is comparable to SAP Analytics Cloud security at a conceptual level. The below breakdown
of different Security objects will help to correlate the Security between SAP BPC and SAP Analytics Cloud.
7.1 Analysis authorizations

In SAP BPC Analysis authorizations are defined centrally in the BW backend system. The data access is
controlled independently from other data access tools. This type of authorization is defined in transaction
RSECADMIN and is assigned to a user (directly or via a BW backend role).
SAP BPC Analysis Authorization intersects with the SAP BPC Data Access Profile and is a common practice to
keep one or the other wide open and focus the data access control on a single concept.
To setup SAP BPC Analysis Authorizations reffer to the SAP BPC help:
https://help.sap.com/docs/SAP_BPC_VERSION_BW4HANA/dd104a87ab9249968e6279e61378ff66/4c65fcd82f
841f3ce10000000a42189c.html?version=11.0
In SAP Analytics Cloud for planning, the data access control also can be obtained via two concurrent concepts.
There is the “Model Data Privacy” and there is the “Data Access Control” in Dimensions (covered in the next
section).
The Model Data Privacy is enabled via Model Preferences / Access and Privacy/ Model Data Privacy toggle.
When enabled, only the owner of the model and users with roles that are granted access in Security/Roles can
access the data (facts) of a model.
To create a Role in SAP Analytics Cloud for planning, refer to the SAP help. Step 7 describes where you add
rules to explicitly grant permission to models:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/184b5d5493bb491
9b06e60947868433a.html

7.2 Data Access Profiles
In SAP BPC, member access rights established for secured dimensions of a model are called Data Access
Profile. This determines the read, writes, or no-access at dimension level. If no profile is defined for a secured
dimension in a model, the users assigned to the profile will not have access to that model. Data access profiles
are assigned to users as needed.
For more information on Data Access Profiles in SAP BPC, refer to the SAP BPC security guide:
https://help.sap.com/doc/39f2c058d4694603b3ba2d06bd9e7e7e/10.1/en-
US/loiob97bd24be39e4f18931b06ff8acf463e.pdf
To setup Data Access Profiles, refer to the SAP BPC help:

https://help.sap.com/docs/SAP_BPC_VERSION_BW4HANA/22b7cf3842074145818abb62fe10f5a4/a3bcf8f52aa
c4815b4320ef089665c6d.html?
Dimension based data access control (DAC) in SAP Analytics Cloud is used to control and limit which users or
teams can see specific dimension members and data.
The SAP Note 3167189 provides concept and common issues with the application of Data Access Control in
SAP Analytics Cloud: https://launchpad.support.sap.com/#/notes/3167189
To setup Data Access Control, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b46f2f74aea04c39
9ccb5c9b1bcc225e.html
7.3 Users
To create a new SAP BPC user, the user id will have to be first created in the ABAP (BW) back-end. To add new
users (for web related part), go to SAP BPC weblink, Administration and under the Security section, choose
Users. In the Users view, select Add. In the Add User assistant, select one or more users to add in the
environment and assign one or more teams to the users.
For additional information on setting up the SAP BPC users, refer to the Security guide:
To setup Users, refer to the SAP BPC help: link:
https://help.sap.com/docs/SAP_SAP
BPC_VERSION_BW4HANA/300caea1895f48dcb1de720be2720731/7c8d7c90cbf644bb913cd4934d9547ec.htm
l
To create users, refer to the SAP help:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/b385d1af93444e9f
bc6439d2c6b3c1a7.html
For SAP BPC users: system id, name and email (optional) are maintained for each user.

For SAP Analytics Cloud users: id, name, email is maintained. In addition: Manager (optional), Roles (can be
changed) and Licenses (inherited by the user) can be viewed under the same User maintenance screen. Email
is a mandatory field.
7.4 Teams / Roles

A Team consists of one or more users. Associating Teams (instead of individual users) to roles makes
maintenance of security more manageable.
In SAP BPC, teams can be associated to:
Task and member access profile. A team can contain one or more task profiles and member access
profiles. SAP BPC has “Admin” team by default. Any team member can be identified as a Team Lead,
which provides management access to the Team’s Folder
Role. A team and/or user can be associated to one or more roles.
The Manage Security task is required to modify, create, or delete Teams.
To create a new team, go to Administration (SAP BPC web) and under the Security section, choose
Teams. In the Teams view, select New. In the Add Team assistant, enter an ID and a description for the
team and assign one or more users to it.
For SAP BPC teams: id, description, Users (number of users), Task Profiles and Data Access Profiles are
maintained.
For additional information on setting up the SAP BPC teams, refer to the Security guide:
To setup Teams , refer to the SAP BPC help:
https://help.sap.com/docs/SAP_SAP
BPC_VERSION_BW4HANA/300caea1895f48dcb1de720be2720731/47c47db5036846a087d0f4948a5097e8.ht
ml
In SAP BPC Embedded Roles are defined centrally in the BW backend system.
In SAP Analytics Cloud, a team can be associated to one or more roles.

For SAP Analytics Cloud teams: Team name (new team can be created), Team members, Created, Last
Changed can be viewed under Teams page.
To create Teams in SAP Analytics Cloud, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/77eaf049d6dd4b7
9965981117eedd905.html

8 Audit
Both SAP BPC and SAP Analytics Cloud for planning are highly auditable systems. Changes in the system are
captured under the audit activity. They are sub-grouped under:
Data Changes – for changes in data captured by user id, time stamp details
Administration activity – for changes in objects captured by user, type of change to the object, time
stamp
8.1 Data Audit

In SAP BPC, to turn on the Data Audit, go to SAP BPC weblink, Administration and under the Audit, go to Data
Changes - here the user can turn on the system tracking of data changes by Info-Providers.
In SAP Analytics Cloud for planning, data changes can be tracked by setting the Data Audit ‘On’ under Access
and Privacy of Model preference (wrench icon). For further details on this and steps to activate, refer to the SAP
help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/82b86653fbb1414
0afd1e25f73dfefcf.html
8.2 Activity Audit

In SAP BPC, to capture user activity tracking, go to SAP BPC weblink, Administration and under the Audit, to the
Administration Activity. Here the user can turn on the system tracking of user activities.
In SAP Analytics Cloud, users making changes to the system objects can be recorded by activating the Track
User Activities setting. This feature can be found under the Security from the left tool palette. For further details
on this and steps to activate, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/8f02122ccdda4c14
a1bdaee5a5cf4c9b.html

9 Workflow
In SAP BPC, Workflow is accomplished through the usage of Business Process Flows. To access and enable
the business process flow, go to Administration in SAP BPC weblink, this will open the Business Process Flow
tab. Under this there will be two subsections
▪Process templates – to create templates that structure a business process
▪Process Instances – to create instances of processes that assign activities to users
SAP Analytics Cloud provides a calendar interface to view and schedule as calendar events. SAP Analytics
Cloud Calendar offers the option to generate workflow tasks automatically using a driving dimension
(characteristic), same as BPC embedded. Processes are defined tasks that can be scheduled. SAP Analytics
Cloud provides two different interfaces to work on processes: Gantt chart or a regular calendar format. The list of
processes or tasks can also be viewed as a list through the list view format. For detailed information, and steps
to set up workflows with example scenarios, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/6019a3530ff744a7
894a050340febba9.html

10 Quick Reference
SAP BPC Object SAP Analytics Cloud for planning Counterpart

Dimensions (BW InfoObjects/Characteristics) Dimensions (Public/Private)
Account Account
Version / Category Version
Time (Period) Date
Entity (often Company Code) Organization
Audit Trail/Data Source Audit Trail as Generic dimension
Other Characteristics Generic/Other Dimensions
Key Figures Measures (as part of New Model Type)

Model
(recommended to use New Model Type with
InfoProvider (DSO, Infocube etc.) Measures)
Exchange rates (Table TCURR) Currency Conversion Table

For on the fly: Currency Conversion Measure in new
Model Type;
For persisting data: Currency Conversion step as part
Currency Conversion (planning function type) of Data Action
Planning Function (incl. Formula Extension Data Actions (Advanced Formulas, Copy Step,
(FOX) formulas) Allocation Step, Cross-model Copy Step)
Advanced Formulas as part of Data Actions

ABAP enhancement (Exit function) (or as needed Analytics designer custom logic)
Planning Sequence, Process Chain Multi Action
Characteristic Relationships Validation Rule
Aggregation level Not required
Planning Filter Story filter
Data Management and Data Wrangling:
Extraction, Transformation and Loading (ETL) Load data via supported Connections
Transactional data import or export via ETL Data Management section of Model
Master Data import via ETL Data Management section of a Public Dimension
Data Management:
SAP S/4HANA import using SAP BW Extractor Connect to SAP S/4HANA APIs / CDS views
Flat File import via ETL Data Management:

Manual load from CSV/Excel;
Automated load from FTP or Google Sheets
Export of transactional Data via BADI or SAP Data Management section of Model (Export to File
BW functionality Server, IBP, ACDOCP etc.)
Scheduling of interfaces (Planning Sequences, Data Management, Calendar tasks in combination
Process Chains) with Multi Actions
Stories
Reports and Input Forms (SAP Analysis for (Web Based, Analytics Designer, SAP Analytics
Office Excel Add-In) Cloud Excel Add-In)
Data Slices, Work Status Data Locks at Model level
Security (Analysis authorizations, Users, Users, Teams, Roles, Data Access Control at
Teams, Data Access Profiles) dimension level
Data Audit Data Changes
Activity Audit Activities
Comments (via separate DSO or Document
Store) Comments (built in functionality)
Workflow (Business Process Flow) Calendar tasks


SAP BPC Embedded Configuration To SAP Analytics Cloud For Planning Migration Guide

Uploaded by

Copyright:

Available Formats

SAP BPC Embedded Configuration To SAP Analytics Cloud For Planning Migration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP BPC Embedded Configuration To SAP Analytics Cloud For Planning Migration Guide

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Business Planning and Consolidation Embedded

How to migrate from SAP Business Planning and

2 DIMENSIONS AND MODELS 6

2.3 Aggregation levels 10

2.4 Planning Filters 10

2.5 Characteristic Relationships 10

2.7 BPC Embedded environment 11

3.1 Planning Function 12

3.2 Planning Sequence 14

3.3 Formula Extension (FOX) formulas 15

3.4 Exit functions 15

3.5 Currency Conversion 16

4.2 Process Chains 20

4.3 Master data 20

4.4 Transactional data 21

5.1 Query Designer 24

5.2 Analysis for Office 24

5.3 Other front-end 25

5.4 Stories in SAP Analytics Cloud for planning 25

6 WORK STATUS (DATA LOCKING) 30

7.1 Analysis authorizations 32

7.2 Data Access Profiles 33

7.4 Teams / Roles 34

8.1 Data Audit 35

8.2 Activity Audit 35

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

SAP BPC for BW/4HANA (Embedded) SAP BPC on S/4HANA (Optimized)

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

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

BPC Property SAP Analytics Cloud for Comment

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

BPC Property SAP Analytics Cloud for Comment

ID (M) Calendar Month (M) Map 1:1. As needed adjust format

2.1.4 Key Figures

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

2.2.1 MultiProvider or CompositeProvider

Refer SAP help link for “Link formulas”

2.2.2 InfoCube or Advanced DataStore Object (DSO), and Models

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

2.3 Aggregation levels

2.4 Planning Filters

2.5 Characteristic Relationships

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

2.7 BPC Embedded environment

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

3.1 Planning Function

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

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

3.2 Planning Sequence

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

3.4 Exit functions

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

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

Data preparation using BW/4HANA

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

For additional information on Transformation, refer to the BW4Hana help link:

Data Transfer Process

SAP Analytics Cloud for planning data preparation