BPC STD To SAC Migration Guide

PUBLIC
SAP Business Planning and Consolidation Standard

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

Consolidation, version for SAP NetWeaver / SAP
BW4/HANA in a Standard Configuration to SAP Analytics
Cloud for planning
Table of Contents
1 INTRODUCTION 5
2 DIMENSIONS AND MODELS 6
2.1 DIMENSIONS 6
2.1.1 Account 6
2.1.2 Version / Category 8
2.1.3 Time 9
2.1.4 Entity 9
2.1.5 Audit Trail 10
2.1.6 Generic/Other Dimensions 11
2.2 MODELS 11
2.3 CURRENCY CONVERSION 12
3 CALCULATION LOGIC 14
3.1 LOGIC SCRIPT 14
3.2 CONVERTING SAP BPC ALLOCATIONS IN SAP ANALYTICS CLOUD FOR

PLANNING 18
3.3 DIMENSION MEMBER FORMULAS 19
3.4 SAP BPC BADI’S AND CUSTOM DEVELOPMENTS 20
3.5 VALIDATION RULES 21
4 INTERFACES 22
4.1 TRANSFORMATION FILE 22
4.2 CONVERSION FILE 25
4.3 TRANSACTIONAL DATA 25

4.3.1 Flat File import of transactional data 25
2 / 41
4.3.2 Flat File export of transactional data 26
4.3.3 SAP BW import of transactional data 26
4.3.4 SAP BW export of transactional data 26
4.3.5 SAP S4/HANA import of transactional data 26
4.3.6 SAP S4/HANA export of transactional data 26
4.3.7 Import of transactional data from other sources 27
4.3.8 Import of exchange rates 27
4.4 MASTER DATA 27

4.4.1 Flat File import of master data 27
4.4.2 BW or SAP S4/HANA import of master data 27
5 INPUT FORMS AND REPORTS 28
5.1 SAP BPC WEB DASHBOARD 28
5.2 SAP BPC EPM ADD-IN 28
5.3 STORIES IN SAP ANALYTICS CLOUD FOR PLANNING 29
5.4 EXCEL REPORTING IN SAP ANALYTICS CLOUD FOR PLANNING 31
5.5 RECOMMENDATION: 31
6 WORK STATUS (DATA LOCKING) 33
7 SECURITY 35
7.1 USERS 35
7.2 TEAMS 36
7.3 TASK PROFILES 36
7.4 DATA ACCESS PROFILES 37
8 AUDIT 38
8.1 DATA AUDIT 38
3 / 41
8.2 ACTIVITY AUDIT 38
9 WORKFLOW 39
10 QUICK REFERENCE 40
4 / 41
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 a Standard Configuration
as well as
SAP Business Planning and Consolidation, version for SAP BW/4HANA in a Standard Configuration
to SAP Analytics Cloud for planning.
The focus of the 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.
Since the SAP BPC Standard configuration and SAP Analytics Cloud are similar in many ways, the assumption
is that the existing SAP BPC functionality will be re-created in SAP Analytics Cloud (technical migration). 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. As a pre-requisite, the
migration team should fully understand the SAP BPC functionality and components that should 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 an Embedded configuration to SAP
Analytics Cloud for planning
• SAP ECC as a direct source for SAP Analytics Cloud for planning
• Integration via SAP Data Warehouse Cloud (DWC)
• 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
© 2022 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.
2 Dimensions and Models
The first chapter provides an overview of how dimensions and models can be mapped and created in SAP
Analytics Cloud for planning, based on the existing SAP BPC data models. It also provides guidance on how to
convert and import existing master data from SAP BPC to SAP Analytics Cloud for planning. It is assumed that
in SAP Analytics Cloud for planning the ‘New Model Type’ will be used.
2.1 Dimensions
Dimensions in SAP BPC will be recreated in SAP Analytics Cloud for planning. Most dimension properties will
be replicated. 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 or as a public dimension. Since model specific dimensions
are not allowed to be populated via interfaces, it is recommended to design most dimensions as public
dimensions, except for dimensions 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.
Hierarchies in SAP Analytics Cloud for planning should be set up as ‘Parent Child’ so they match the SAP BPC
hierarchy concept, except for the time dimension which uses level hierarchies. Time dependent hierarchies are
not supported in SAP Analytics Cloud for planning, so they need to be set up based on the current view or
alternate hierarchies need to be created, each representing a view at a different point of time.
2.1.1 Account
The Account dimension in SAP Analytics Cloud for planning follows the same concept as in SAP BPC. It is
recommended to make this a public dimension in SAP Analytics Cloud for planning, so members and
hierarchies can be populated as needed via interfaces.
As a starting point the dimension should be manually created in SAP Analytics Cloud for planning with the
dimension type ‘Account’ and most of the existing SAP BPC properties should be re-created in SAP Analytics
Cloud for planning.
The Account hierarchies are always created as parent child, which allows the SAP BPC hierarchies to be
migrated without further conversion.
For details around SAP Analytics Cloud for planning account dimension properties; refer to the SAP help:
1bbf205892e3913d0.html#attributes-of-an-account-dimension
For details around SAP BPC account dimension properties; refer to SAP BPC help:
https://help.sap.com/docs/SAP_BUSINESS_PLANNING_AND_CONSOLIDATION,_VERSION_FOR_SAP_NET
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c2c4f6297df1ca9e10000000a42189e.html?locale=en-us
The following table lists the typical SAP BPC Account dimension properties and how to map them to a SAP
Analytics Cloud for planning Account dimension. Mandatory properties are marked with ‘(M)’.

SAP BPC Property SAP Analytics Cloud for Comment
planning Property
ID (M) Member ID (M) Map 1:1
Description (M) Description (M) Map 1:1
Hierarchy PARENTH1 Hierarchy (M) Map 1:1
Hierarchy PARENTH2 etc. Hierarchy 2 – Custom name Map 1:1
Rate Type (M) Rate Type (Mandatory if currency Map 1:1 from ‘AVG’ to ‘Average’
Conversion has been turned on at and ‘CLO’ to ‘Closing’.
model level) See currency conversion
paragraph.
Not a property, but maintained via Formula (M) Logic in Member Formulas needs
‘Member Formulas’ to be converted to SAP Analytics
Cloud for planning syntax – see
paragraph on Member Formulas.
Account Type (M) Account Type (M) Map 1:1, assuming SAP BPC uses
standard account types EXP, INC,
AST, LEQ and NFIN. Other
custom account types need to be
evaluated and potentially
converted into a custom property
leveraging measures to do a sign
flip.
Calculated On (M)
Aggregation Type (M)
Not a property, but maintained via Exception Aggregation Type (M) Logic in Member Formulas needs
‘Member Formulas’ to be converted to SAP Analytics
Cloud for planning syntax – see
paragraph on Member Formulas
Scaling (M) Scale (M) Can be optional set up. If scale in
SAP BPC is set to ‘Y’ map to the
desired SAP Analytics Cloud for
planning scaling factor ‘Thousand’,
‘Million’, ‘Billion’, ‘Percent’
Decimal Places (M) Can be custom set in SAP
Analytics Cloud for planning as
default number of decimals
displayed.
Units & Currencies (M) Leave blank or map to ‘None’,
‘Currency or enter a custom label.
See currency conversion
paragraph.

Hide (M)
Other optional properties Other optional properties Custom mapping – in many cases
1:1
2.1.2 Version / Category

SAP Analytics Cloud for planning has a different and improved version concept, in comparison to how SAP BPC
maintained the Category.
SAP Analytics Cloud for planning Versions will be created via the ‘Version management’ feature within stories
or when importing data and are then 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
For details around SAP BPC Category (Version) dimension properties; refer to SAP BPC help:
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c33574835c520d4e10000000a42189b.html?locale=en-us
The following table lists the typical SAP BPC Category dimension properties and how to map them to the /P
Version dimension. Mandatory properties are marked with ‘(M)’. SAP BPC Consolidation specific properties are
not covered in the table.

planning Property
ID (M) Member ID (M) Map 1:1, considering SAP

syntax which adds ‘public.’ in front
of a public version ID and naming
the Actual version always
‘public.Actual’.
Description (M) Description (M) In SAP Analytics Cloud for
planning, the description is the
same as the ID, but without the
‘public.’ or ‘private.’ statement in
front.
Category (M) In SAP Analytics Cloud for
planning, the Category is a
property of a version, selected via
the version management, out of
the following options: Actuals,

Budget, Planning, Forecast,
Rolling Forecast.
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 SAP
BPC), can be either user managed, or system managed. The Data 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
For details around the SAP BPC Time dimension properties, refer to SAP BPC help:
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c338c1935c520d4e10000000a42189b.html?locale=en-us
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/monthly level. Since SAP Analytics Cloud for planning generates all required Date dimension
properties, only reporting specific custom SAP BPC properties need to be added:
planning Property
ID (M) Calendar Month (M) Map 1:1. As needed adjust format
Additional mandatory properties SAP Analytics Cloud for planning No mapping 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 Entity
In SAP Analytics Cloud for planning, the equivalent of the SAP BPC dimension ‘Entity’, is the SAP Analytics
Cloud for planning dimension, ‘Organization’. Often in Financial Planning scenarios, the Company Code will be
set up as Entity/Organization dimension.

For details around the SAP Analytics Cloud for planning ‘Organization’ dimension; refer to the SAP help:
1bbf205892e3913d0.html
For details around SAP BPC Entity dimension properties; refer to the SAP BPC help:
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c336df835c520d4e10000000a42189b.html?locale=en-us

planning Property

Control Level (M) Not needed in SAP Analytics
Cloud for planning. Data entry
Bypass LC in Ctrls (M)
validation can be handled in SAP
Analytics Cloud for planning via
‘Validation Rules’.
Currency (M) Currency (M) Map 1:1
Person Responsible Person Responsible Map 1:1
1:1
Hierarchy PARENTH1 etc. Custom Parent Child Hierarchies Map 1:1
2.1.5 Audit Trail

SAP BPC uses the Audit Trail dimension of Type ‘Audit – D’ to flag the source of the data that is loaded into
SAP BPC. In SAP Analytics Cloud for planning, the Audit dimension is not a mandatory dimension and does not
have its own data type and should instead be set up as a ‘Generic’ dimension.
For details around SAP BPC Audit Trail dimension properties; refer to SAP BPC help:
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c3361cb35c520d4e10000000a42189b.html?locale=en-us

planning Property


Scaling (M) Not required in SAP Analytics
Cloud for planning. Scaling can be
set up at a report level.
1:1
2.1.6 Generic/Other Dimensions

As in SAP BPC, SAP Analytics Cloud for planning allows the addition of Generic dimensions to a SAP Analytics
Cloud for planning model. The dimensions, their properties and hierarchies can be mapped as 1:1 in most
cases.

planning Property
Scaling (M) Not required in SAP Analytics
Cloud for planning. Scaling can be
set up at a report level.
1:1
2.2 Models
The model approach in SAP Analytics Cloud for planning is very similar to the model approach in SAP BPC.
SAP BPC models need to be recreated in SAP Analytics Cloud for planning, using the dimensions that were
created in the previous steps. The dimensions that are used to build the model can either be public or private.
For details; refer to SAP help for more details:
1bbf205892e3913d0.html#public-and-private-dimensions)
This is a similar, but a more flexible approach than the concept of the SAP BPC environment. All dimensions
which are part of an environment in SAP BPC can be used in one or more models created within the
environment. With SAP Analytics Cloud for planning, all public dimensions can be re-used for any model in that
SAP Analytics Cloud instance.

SAP Analytics Cloud for planning and SAP BPC models are both created following the star schema approach.
When creating a new planning model in SAP Analytics Cloud, it is recommended to choose the ‘New Model
Type’.
For details; refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/3ee0b7055e7d400
bb08c7fda6f0f643a.html
With the New Model Type, SAP Analytics Cloud for planning provides new benefits that are not available in SAP
BPC. Using Measures, a multi key figure approach can be leveraged. This means instead of a single measure
as in SAP BPC, it is possible 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 the SAP BPC approach with a single measure
should be kept or if the architecture should be enhanced by leveraging 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 Currency Conversion

In SAP Analytics Cloud for planning, the recommended ‘New Model Type’ currency conversion set up is more
flexible and simplified compared to SAP BPC, by leveraging measures. In SAP Analytics Cloud for planning, the
currency conversion can either be done at report runtime on the fly or the converted amounts can be persistently
stored in SAP Analytics Cloud for planning via a Data Action. When doing the conversion via Data Action, SAP
Analytics Cloud for planning provides an out of the box Currency Conversion. When using currency as a
selection variable in a model, the user can enter data in any selectable currency and SAP Analytics Cloud for
planning, on the fly, converts it to the desired reporting currency.
The SAP help provides more details:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/92cab98504dc479f
b19740a2715241bd.html
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/e48c776e2c0f4cb0
9cc8b03aadd0b154.html
US/10a9f662ce5c4d05b6ba31cd4ae80668.html
SAP Analytics Cloud for planning uses Currency Conversion tables, which work like the ‘Rate’ model in SAP
BPC, where exchange rates are stored. In SAP Analytics Cloud for planning, the currency conversion table can
be manually maintained or automatically populated via FTP, SAP BPC, SAP BW or Google Drive.
US/9348d55977e94994ab27bf031389d8f2.html
The following table provides a comparison:

SAP BPC Rate application SAP Analytics Cloud for Comment
dimensions planning Currency Conversion
table fields
Category Category The SAP BPC category can be

mapped against standard SAP

categories or left blank if using a
generic exchange rate. Also
"Specific" categories can be
added, which will be further
distinguished by values
maintained in the Rate Version
field.
Input Currency Source Currency Map 1:1
Rate Account Rate Type Map 1:1
Rate Entity Not required in SAP Analytics
Cloud for planning
Amount Exchange Rate Map 1:1
Rate Version Can be used in SAP Analytics
Cloud for specific versions and
scenarios using rate versions
SAP Analytics Cloud for planning can leverage the ratetype of the Account dimension in combination with the
Currency property of the Organization dimension to determine the desired exchange rate by account and
organizational unit such as e.g., Company Code.

3 Calculation Logic
3.1 Logic Script
SAP BPC script logic and SAP Analytics Cloud for planning advanced formulas scripts are very similar in the
mechanism they follow and how to implement them.
For both SAP BPC and SAP Analytics Cloud for planning:
When the logic module is invoked, the system will:
• Read a specific data region (MemberSet section)

• Apply to the data just read, a set of user-defined formulas (Calculation expression section)
• Calculate any new/modified records and their values
• Directly post in the database as base member data
The script structure is almost the same
SAP BPC SAP Analytics Cloud for planning
• Scoping MemberSet section • Configuration Section

• Calculation expression section • MemberSet Section
• Calculation expression section
Here are some examples of common SAP BPC script expressions, with their corresponding SAP Analytics
Cloud for planning formula expressions:
SAP BPC SAP Analytics Cloud for planning Comments
Member Set definitions
*XDIM_MEMBERSET ACCOUNT MEMBERSET[d/ACCOUNT] = ("A2010") For syntax and examples click here:
= A2010
https://help.sap.com/doc/a2c49c40bbe549ef9c291537aa
561430/release/en-US/index.html#MEMBERSET
*XDIM_MEMBERSET FLOW = MEMBERSET[d/FLOW] = ("F00",”F99”)

F00,F99
Select Base members
*XDIM_MEMBERSET MEMBERSET[d/Date] = BASEMEMBER([d/Date],”2022”) For syntax and examples click here:

TIME=BAS(2022.TOTAL)
In this example we select all base members (months) of the https://help.sap.com/doc/a2c49c40bbe549ef9c291537aa
total year 2022 561430/release/en-US/index.html#BASEMEMBER

Select members via properties
*SELECT(%ACCOUNT_INC%, MEMBERSET[d/ACCOUNT].[p/accType] = "INC" The keyword [p/…] indicates the property name
“ID”, “ACCOUNT”, “[ACCTYPE] =
'INC'”) In this example we select all accounts where the property [p/accType]
value is INC
*XDIM_MEMBERSET
ACCOUNT=%ACCOUNT_INC%
Record Data
*REC DATA() For syntax and examples click here:
561430/release/en-US/index.html#DATA
Time offset
TMVL NEXT, PREVIOUS For syntax and examples for NEXT key word click here:
*REC(FACTOR=1, DATA()=RESULTLOOKUP([d/Date]=NEXT(12,"MONTH",[d https://help.sap.com/doc/a2c49c40bbe549ef9c291537aa

TIME=TMVL(12,2022.01)) /Date]="202201")) or the same result 561430/release/en-US/index.html#NEXT
DATA()=RESULTLOOKUP([d/Date]=NEXT(1,"YEAR",[d/Da
te]="202201"))
*REC(FACTOR=1, TIME=TMVL(- DATA()=RESULTLOOKUP([d/Date]=PREVIOUS(12,"MONT For syntax and examples for PREVIOUS key word click
12,2022.01)) H",[d/Date]="202201")) here:
561430/release/en-US/index.html#PREVIOUS
Conditional logics
MDX expression with *IIF in IF, THEN, ELSE, ENDIF keywords in SAP Analytics Cloud For syntax and examples click here:
SAP BPC
561430/release/en-US/index.html#IF_ELSEIF_ELSE
Loop Instructions
*FOR / NEXT FOREACH / ENDFOR For syntax and examples click here:
561430/release/en-US/index.html#FOREACH
Cross model data copy
*DESTINATION_APP A cross model data copy embedded in the data For data actions see next section
actions For DATA, RESULTLOOKUP, and LINK functions syntax
and examples click here :

Or use advanced formulas with the combination https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f
68c2e08b941f081002fd3691d86a7/812f4d02ac13401d99
of these 3 functions : DATA, RESULTLOOKUP,
0cee9b7637dcea.html
and LINK
Clear data Delete Data
*XDIM_MEMBERSET MEMBERSET [d/TIME] = "2022.01" TO "2022.12" In SAP Analytics Cloud, the records are deleted from the
TIME=BAS(2022.TOTAL) fact table.
DELETE([d/AUDIT_ID]="ALLOCATION")
*XDIM_MEMBERSET In SAP BPC, the data is cleared but not deleted. The
AUDIT_ID=ALLOCATION data is just reversed.
*WHEN AUDIT_ID
*IS ALLOCATION For syntax and examples click here:
*REC(FACTOR=0) https://help.sap.com/doc/a2c49c40bbe549ef9c291537aa
561430/release/en-US/index.html#DELETE
*ENDWHEN
For advanced calculations using script formulas, refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/766b9da1890d431
ca29927daee4811b4.html
Also, a reference guide for SAP Analytics Cloud for planning advanced formulas is available:
https://help.sap.com/doc/a2c49c40bbe549ef9c291537aa561430/release/en-US/index.html#
How to migrate a SAP BPC Data Package into SAP Analytics Cloud for planning Data actions
In SAP BPC, you need to create or use 3 types of objects to trigger calculations based on the data.
1. Process chain
2. Script file
3. Data package
When you create a Data package, you select a SAP BW Process Chain and a SAP BPC Script logic file (.lgf).
The Process chain triggers the calculations expressed in the script file.
Then, the user can open the SAP BPC Data Manager to run the package.
In SAP Analytics Cloud for planning, you use Data Actions instead of a SAP BPC data package, and your SAP
BPC package links can be replaced by Multi actions in SAP Analytics Cloud.
SAP BPC SAP Analytics Cloud for Comment

planning
Data Package Data Actions Data actions include several types of data
processes

Package link Multi Actions Multi actions embed several data actions from
different data models but also other actions like
Version Management, Data import, Predictive
and API.
SAP BPC Package Data actions/Mutli actions in Data actions or multi actions objects can be
Scheduler the Calendar scheduled via the SAP Analytics Cloud for
planning Calendar
Each Data Action consists of different steps:

Available types of data action steps:
1. Copy Operation: Copy data within the same data model (No coding needed)
2. Cross-Model Copy: Copy data between models (No coding needed)
3. Allocation: Allocate data from sender to source according to specific rules (No coding needed)
4. Embedded Data Action*: Embed another data action into the current data action (No coding needed)
5. Currency Conversion: Convert from source to target currency (No coding needed)
6. Advanced Formula: Custom logic via textual script or visual formulas
(*) Equivalent with the SAP BPC Script Logic Keyword *INCLUDE
To migrate the SAP BPC packages, (related to data copy, data calculations or data currency translation), create
corresponding SAP Analytics Cloud data actions and use the proper steps to cover all sorts of data processes.
SAP BPC standard SAP Analytics Cloud for Comment

Package planning Data Action
Copy data Data action with Copy 1:1

Operation step
Clear Data action + Advanced

formula step with DELETE
functions
Or
Use from: Modeler/Model

Structure/Delete Facts
Copy Opening Data action with Advanced 1:1

formula step using the
CARRYFORWARD functions

Currency translation Data action + currency 1:1
conversion step
Allocation Data action + Allocation step 1:1
To create data actions, refer to SAP help:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/e28c7a30978b406
aa5e24318206f6443.html
To create data actions for currency translation, refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/10a9f662ce5c4d05
b6ba31cd4ae80668.html
To create multi actions, refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/4835429d35534ad
d875bae17e93b12e1.html
3.2 Converting SAP BPC Allocations in SAP Analytics Cloud for planning
Most Planning projects need allocations. In SAP BPC, implement these calculations with the *RUN
ALLOCATION function.
Allocation helps to distribute data from a source region to a destination region using specified drivers. The basis
of the allocation is the definition of a portion or complete source value to be allocated; the means of defining the
basis is the use of a “factor”. A factor can be the value or values that can be multiplied or divided to derive a
value.
The syntax of this function is:
*RUNALLOCATION
*FACTOR=<Driver>
*DIM [Dimension1] WHAT=<source>; WHERE=<target>; USING=<distribution key>;
TOTAL=<distribution key>
*DIM [Dimension2] WHAT=<source>; WHERE=<target>; USING=<distribution key>;
TOTAL=<distribution key>
*ENDALLOCATION
To run this allocation in SAP BPC:
1. Include this function in a script logic

2. Include this script logic in a package
3. Run the package from the data manager

In SAP Analytics Cloud for planning: The standard SAP Analytics Cloud for planning Allocation engine can be
configured without the need for scripting. For more complex allocations the SAP Analytics Cloud for planning
Advanced formula logic could be used.
For the standard allocation, you select dimensions or options to design your allocation processes via settings in
different windows.
The allocation process is based around 3 different objects.
1. Create a new allocation
2. Embed this allocation in an existing or new Data action

3. Add a planning trigger object in your story, to run the Data action, as allocation is a step in that Data
action
Each allocation process can have several steps.
In a migration process, you can replicate your RUN_ALLOCATION scripts into SAP Analytics Cloud allocation
steps, when possible, or use scripts with the advanced formulas.
Refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/674398eba641490
2961dc24074776b27.html?q=allocations#loio3fe7ca5d883b4b8eb526d30b794cefe0
3.3 Dimension Member Formulas

In SAP BPC, the formulas attached to the dimension members are named dimension formulas and use MDX
statements. They can be used in every dimension. You just need to activate the formulas with the checkbox
<Allow Member Formulas>
In SAP Analytics Cloud, the formulas are attached to the dimension members in a column “Formula”, exactly like
in SAP BPC.
With this Formula column, it is possible to edit advanced formulas with the help of an editor. Formulas can be
applied only for the Account type dimension or Measures.
To define account formulas in SAP Analytics Cloud for planning; refer to SAP Analytics Cloud Help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/.html?q=Account%
20formulas
For dimensions, other than account, for which you have dimension formulas in SAP BPC, preferably use
alternative hierarchies in these dimensions, to have specific aggregation calculations.
If alternative hierarchies cannot be used, because you have more complex calculation than just aggregation, you
must use SAP Analytics Cloud advanced formulas, combined with Data actions. In this case, the calculation
won’t be executed on the fly, but triggered by the users.

Here is a mapping table between some MDX statements or key words in SAP BPC and the equivalent in SAP
Analytics Cloud.
SAP BPC SAP Analytics Cloud for planning Comments
IIF() IF()
ISEMPTY ISNULL
[A1300]+[A1500]-[A1800] [A1300]+[A1500]-[A1800] Same formula when you

calculate accounts.
Account dimension name is
optional.
[ACCOUNT].[A1300],[FLOW].[F20]+ RESULTLOOKUP([A1300] ,[d/FLOW]= "F20" To compute a combination

[ACCOUNT].[A1500],[FLOW].[F20] )+RESULTLOOKUP([A1500] ,[d/FLOW]= "F20" ) of several dimensions, use
the RESULTLOOKUP
function in the formula. It
differs from SAP BPC.
PREVMEMBER PRIOR
3.4 SAP BPC BADI’s and Custom Developments

SAP Business Add-Ins (BAdIs) are used to adapt SAP software to specific requirements. They can be inserted
into the system to accommodate user requirements that are not included in the standard delivery.
A frequently used SAP BPC BAdI, is’ BADI_UJ_CUSTOM_LOGIC’. It is used to perform complex or heavy
calculations that SAP BPC script logic is not able to handle with performance or functionality.
In SAP Analytics Cloud for planning, there is no NetWeaver platform with ABAP programing, therefore, no Badi
functionality. You can use advanced formulas, even for your more complex calculations and with Hana
technology and a good design, the performance is there.
To do custom development, you can also use Analytics Designer. With this module, you can associate plenty
of nice and friendly widgets to the classic SAP Analytics Cloud for planning stories.
For more information on how to develop with the Analytics Designer, refer to the SAP help:.
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/25a3b8d145864d7
faf7447b916e492e7.html
In addition to customizing and automating actions in SAP Analytics Cloud for planning, you can also use the APi
objects.
Refer to the API Reference guide:
https://help.sap.com/doc/958d4c11261f42e992e8d01a4c0dde25/2022.21/en-US/index.html

3.5 Validation Rules
The validations rules are used to restrict the valid dimension combinations for new data records sent to the
database. In SAP BPC and in SAP Analytics Cloud for planning, by default, all combinations are opened.
In SAP BPC, we use a SAP BW transaction, UJ_VALIDATION, to limit the possible combinations. This prevents
“invalid” records from being saved in the cube. In UJ_VALIDATION, dimension drivers must be defined.
Note: Only one single dimension driver is possible per SAP BPC model.
MODEL ID Driver Dimension 10
FINANCE Account
SALES Products
RATE
OWNERSHIP
When dimension drivers are specified, then some rules can be applied.
Note: If you leave the driver dimension empty, then no validation rules will be applied to this SAP BPC model.
The rules are attached to the dimension drivers.
The equivalent in SAP Analytics Cloud for planning is the VALIDATION RULES. They are defined and
maintained in the model settings. To be able to use that functionality, you must activate it first.
Like validations in SAP BPC, they prevent you from entering data in unexpected dimension combinations.
Restrictions in SAP Analytics Cloud for planning validations rules:
• You can create three rules for one model.

• You can define three dimensions in one rule.
• You can use the same dimension in up to 10 different rules.
• You can't choose time or version dimensions in a validation rule.
How to define the validation rules, refer to SAP help:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/e275adffd7f14151
a97721d83f4a865c.html?q=validation%20rules

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.
In SAP BPC, Data Manager performs data transformations and mapping using transformation and conversion
files.
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 Planning operates on acquired data.
4.1 Transformation file

In SAP BPC, the transformation file allows you to set rules for reading data from an external source and convert
it to the proper system format. Transformation files are Microsoft Excel files that contain one worksheet, named
Instructions. The Instructions worksheet contains the following sections:
▪ Options: contains definitions for various options that you can be set for your transformation
▪ Mapping: defines how data is mapped to the Planning and Consolidation structures
▪ Conversion: defines which conversion sheet to use with which dimensions
Options
In SAP BPC, “DELIMITER text character| SPACE | TAB” provides the option to define the single character that
is the delimiter between columns if the FORMAT option is set to DELIMITED, keywords SPACE or TAB will
delimit the columns by spaces or tabs.
In SAP Analytics Cloud for planning, when a File upload is selected, the “CSV Delimiter” provides a drop down,
with the following options to select from: Auto-detect, Space, Tab, Dot, Comma, Colon, Semicolon, Dash, Other.
If the option “Other” is selected, the type delimiter must be provided in the text box next to it.
In SAP BPC, “HEADER= YES | NO”, specifies if the data file has a header row. If this parameter is set to YES,
then the input file contains one header row that defines the fields.
In SAP Analytics Cloud for planning, there is a check box during file upload: “Use first row as column headers”. If
this is selected, the first row will be used for reference to map the fields with dimensions in the model.
Once the above two options are selected in SAP Analytics Cloud for planning, the “Import” button will take you to
the “Import Jobs” section, where the “Set Up Import” steps will take the user through the steps to prepare data,
map to target, properties, review and import of data.
Note: There are additional Options available through SAP BPC, like AMOUNTDECIMALPOINT,
CREDITNEGATIVE. While SAP BPC handles these as preset values, SAP Analytics Cloud for planning handles
them as view-based data wrangling, where a user can perform these activities in the table, like working in an
excel spreadsheet.
For SAP BPC help on Transformation File: Options, refer to:
https://help.sap.com/docs/EPM_ADDIN/ec68e48b18a44a49abb12b8ee8ae306f/f9c45de06faf1014878bae8cb0e
91070.html

Mapping
In SAP BPC, the Functions that define the column are:
*COL - a dimension for a field in the data file
FLD - column index value of the data file
The functions that define a subset value of a dimension (column) are:
P_ACCT - subset of the values of a dimension
*FCOL(A:B) - start and end positions of column
*MVAL(A:B) - for a number of consecutive columns that are based on time periods
*NEWCOL(A) - new field with the given value
*Str(string) - new text string to the members of a column
*PAD (A,B,C,D) - where, A = Field name, B = Total length, C = Padding direction, D = Padding character
For the Transformation File Mapping Function, refer to :

https://help.sap.com/docs/EPM_ADDIN/ec68e48b18a44a49abb12b8ee8ae306f/f9c4554f6faf1014878bae8cb0e
91070.html
For the SAP BPC functions mentioned above, SAP Analytics Cloud for planning provides a view-based
approach to “Prepare Data” under the Modeler Workspace → Data Management. Once the required file or data
from the data source is extracted, the user can “Prepare Data” through “Set Up Import”.
Under Prepare Data, users can select an individual column or a group of columns to perform operations like
Create transformation, Duplicate or Delete the column/s.
For preparing data using the Multiple Measures data model, refer to SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/75683f452594426
bb05cb49dc4c5af99.html#preparing-the-data
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 SAP 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 SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/8b8f9ce9952a450
ebd12b81cf5b608b7.html
4.2 Conversion file

In SAP BPC: The conversion file allows to map member names from external to internal dimension structures.
Users can set up multiple sheets in a conversion file so that many transformations can access the same
conversion workbook. Users can have one conversion file per dimension.
For further details on SAP BPC Conversion files:
https://help.sap.com/docs/EPM_ADDIN/ec68e48b18a44a49abb12b8ee8ae306f/f9c40b246faf1014878bae8cb0e
91070.html
In SAP Analytics Cloud for planning: Data conversion is performed in the same data wrangling step of “Prepare
data”.
4.3 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 SAP help link:
2beb3299cdcff7026.html
4.3.1 Flat File import of transactional data

In SAP BPC, packages allow data to move between Planning and Consolidation databases. The Import
Transaction Data package imports one or more ASCII files into the current application.
For details about Data Management Packages (for file import), refer to:
https://help.sap.com/docs/EPM_ADDIN/ec68e48b18a44a49abb12b8ee8ae306f/f9c67b536faf1014878bae8cb0e
91070.html
In SAP Analytics Cloud, a step-by-step process to upload a flat file; refer to::
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
A SAP Analytics Cloud agent must be installed as a pre-requisite. The steps to install SAP Analytics Cloud
Agent, refer to:

https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/7c35129451f5432
194773adac7f89598.html
4.3.2 Flat File export of transactional data

In SAP BPC, to download transactional data, run download data under the Data Manager; refer to SAP help:
https://help.sap.com/docs/EPM_ADDIN/ec68e48b18a44a49abb12b8ee8ae306f/f9c488f56faf1014878bae8cb0e
91070.html
For SAP Analytics Cloud for planning, the data from a model can be exported to a flat file; refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/be55df472f9d4a31
b94f5dda47300e81.html#concept_u1q_wjy_stb__section_ycl_rly_stb
Note: Data from a SAP Analytics Cloud for planning table can also be downloaded to a flat file; refer to the SAP
help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/ff5f1e052b5e400d
a990dad8408604da.html
4.3.3 SAP BW import of transactional data

For steps to import SAP BW data to a SAP Analytics Cloud for planning model, refer to the SAP help:
18f3712cb10ac3cdc.html#concept_jbd_ztv_ktb__section_rsv_13w_ktb
4.3.4 SAP BW export of transactional data

For steps to export SAP Analytics Cloud for planning data toSAP BW andSAP BW/4HANA, refer to the SAP
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
4.3.5 SAP S4/HANA import of transactional data

For steps to import SAP S/4HANA data to a SAP Analytics Cloud for planning model, refer to SAP help:
18f3712cb10ac3cdc.html#concept_mv1_ztv_ktb__section_psv_13w_ktb
4.3.6 SAP S4/HANA export of transactional data

For steps to export SAP Analytics Cloud for planning data to SAP S/4HANA, refer to the SAP 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
help:

https://help.sap.com/docs/SAP_S4HANA_ON-
PREMISE/48f4b4785b8e45938ac44a67be8032d9/15447e5bda934be28f3b16cfb456fb23.html
4.3.7 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 detailed list of available systems (as of date) from which data can be sourced, and the steps to import
data, refer to the SAP help:
18f3712cb10ac3cdc.html
4.3.8 Import of exchange rates

Steps to import currency conversion data for SAP Analytics Cloud for planning, refer to SAP 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
4.4 Master data
4.4.1 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 SAP help:
2beb3299cdcff7026.html#import-data-into-public-dimensions
4.4.2 BW or SAP S4/HANA import of master data

For SAP BW or SAP S4/HANA import of master data to SAP Analytics Cloud, follow the same steps as for the
load of data for a public dimension from flat file, however since the source are different, when selecting the step
to import data, select the connection created for SAP BW or SAP S4/HANA 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:
https://help.sap.com/docs/SAP_S4HANA_ON-
PREMISE/48f4b4785b8e45938ac44a67be8032d9/9965a647179a4e5a95e081f3e93c89b4.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 SAP BPC Web Dashboard

In SAP BPC, business users can input data via Web input forms (SAP BPC dashboard) or via Excel input
schedules with the SAP EPM Add-in.
Web input forms can be used for basic data entry like FX rates, Consolidation rates or other simple financial
data. The design options are limited as well as the layout. Advanced input forms including some calculations are
not possible. SAP BPC web forms allow only data retrieve and sending data. For example, adding formulas to
display simple variances between Actuals and Budget data is not possible.
For Web Input forms and reports, refer to the SAP BPC help :
WEAVER/a2049170bfeb4178ace32222842c3ec1/a93ed440d508483690862bda0e961080.html?q=Web%20for
ms
For creating web reports and input forms, refer to the SAP BPC Help:
WEAVER/a2049170bfeb4178ace32222842c3ec1/cd8906d6ff224496ae2b5c979455592b.html?q=Web%20forms
5.2 SAP BPC EPM Add-in

In most SAP BPC projects, the data input is performed via EPM Add-in Input Schedules. With this Excel Add-in,
SAP BPC users can easily retrieve data or send data and mix EPM functions with Excel formulas to develop
advanced and complex reports or input schedules.
For creating reports and input form, refer to the EPM help:
https://help.sap.com/docs/EPM_ADDIN/ec68e48b18a44a49abb12b8ee8ae306f/f9bed6696faf1014878bae8cb0e
91070.html
Input forms are EPM reports with options to use them as input forms.
Their design must follow some golden rules:
• Limit and filter the scope of data on expected combinations of dimensions. Because technically all
combinations are opened in SAP BPC, the input form must secure the data sent by the users. The data
validations rules cannot handle all valid combinations. There are often too many of them and this is most
of the time shared between input forms and data validations.
• The size of the report must be controlled to keep performance when the data is sent and when the
report is refreshed to display the data. Avoid too many columns or rows.
• The dimension members selection must be clear and intuitive for the users.
• The data currency, the data scale, the time period and versions must be clearly identified and displayed
in the report.
The same golden rules must be followed for SAP Analytics Cloud for planning.

5.3 Stories in SAP Analytics Cloud for planning
In SAP Analytics Cloud for planning, input forms and reports are developed via the stories.
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
SAP BPC EPM Add-in SAP Analytics Cloud for planning Comments / Links
EPM Report Story/Table
EPM Input Schedule Story/Table Activate planning option in the SAP

Analytics Cloud model settings to be
able to input data.
EPM Chart (Excel Chart) Story/Chart
Report Editor/Layout Edit/Designer/Builder/Table Structure
Report Editor/Options Edit/Designer/Builder/Property
Report Editor/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_ANAL
YTICS_CLOUD/00f68c2e08b941f081
002fd3691d86a7/a0426a71d5c94aba
882a852b3e4ddec7.html?q=Sort
Sheet options Edit/Designer/Builder/Property
Context options Edit/Designer/Builder/Filters

EPM formatting Edit/Designer/Styling For Story Preferences, refer to the
SAP help:
Story Preferences
https://help.sap.com/docs/SAP_ANAL
002fd3691d86a7/d1ab3f5e52284e149
da16a0aff691fbc.html
Local Member to display a Custom Calculation Custom calculations are local member
calculation calculations that are executed at run-
time.
For custom calculations, refer to the

SAP help:
https://help.sap.com/docs/SAP_ANAL
002fd3691d86a7/ef59af374b494b66a
7659d267b0b8bd8.html
Local Member to display Property selection from the Simply select in SAP Analytics Cloud
dimension property values Dimension the dimension property to display it in
the report
Advanced developments
In 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 the 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

5.4 Excel Reporting 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
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.5 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

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 SAP 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 SAP BPC, refer to SAP BPC help:
WEAVER/a2049170bfeb4178ace32222842c3ec1/4c335371ad165792e10000000a15822b.html
In SAP Analytics Cloud for planning, Data Locking provides the same purpose as work status in SAP 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 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 SAP Analytics
Cloud link:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/91fa3cbbd46d457
ab04f9ef3c7901655.html

7 Security
SAP Analytics Cloud uses licenses, roles, and permissions to manage application security and capabilities.
▪ Licenses determine which features are available for users.
▪ Roles are collection of permissions that allow system admins to control available features by users (or
teams).
▪ 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 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, 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:
https://help.sap.com/doc/39f2c058d4694603b3ba2d06bd9e7e7e/10.1/en-
US/loiob97bd24be39e4f18931b06ff8acf463e.pdf
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 are 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.2 Teams
A Team consists of one or more users. Associating Teams (instead of individual users) to roles makes
maintenance of security more manageable. The admin can maintain the users in a team, instead of having to
maintain the task and data access profiles (in SAP BPC) for individual users.
Teams can be associated to:
▪ For SAP Analytics Cloud: Role. A team can be associated to one or more roles.
▪ For SAP BPC: 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
The Manage Security task is required to modify, create, or delete Teams.
In SAP BPC
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 additional information on setting up the SAP BPC teams, refer to the Security guide:
To setup Teams , refer to the SAP BPC help:
BPC_VERSION_BW4HANA/300caea1895f48dcb1de720be2720731/47c47db5036846a087d0f4948a5097e8.ht
ml
To create Teams in SAP Analytics Cloud, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/77eaf049d6dd4b7
9965981117eedd905.html
For SAP BPC teams: id, description, Users (number of users), Task Profiles and Data Access Profiles are
maintained.
For SAP Analytics Cloud teams: Team name (new team can be created), Team members, Created, Last
Changed can be viewed under Teams page.
7.3 Task Profiles

In SAP BPC
Tasks: Specific application-level access right/permissions. Example: Manage Environments, View Environments,
Manage Security.
Task Profile: A collection of granted tasks. A Task Profile determines what type of activities or tasks a user or
team can perform in SAP BPC.
For more information on Task Profiles in SAP BPC, refer to the SAP BPC security guide;

To setup Task Profile, refer to the SAP BPC: help:https://help.sap.com/docs/SAP_SAP
BPC_VERSION_BW4HANA/300caea1895f48dcb1de720be2720731/d39aa9789e3f4217bbf64c59ab1c7f02.html
In SAP Analytics Cloud for planning, Roles are associated with Teams (and Users). Each Role contains the
Permissions by object.
To create a Role in SAP Analytics Cloud for planning, refer to the SAP help:
https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/184b5d5493bb491
9b06e60947868433a.html
7.4 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:
To setup Data Access Profiles, refer to the SAP BPC help:
BPC_VERSION_BW4HANA/300caea1895f48dcb1de720be2720731/f2fa1c89fd044c4baf41e8c67dc01e23.html
Dimension based data access control (DAC) in SAP Analytics Cloud (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

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 Category.
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 an easier and more familiar calendar interface to view and schedule, through
calendar events. 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
This chapter provides a quick reference on how to map SAP BPC functionality to SAP Analytics Cloud.
SAP BPC Object SAP Analytics Cloud for planning Counterpart

Dimensions Dimensions (Public/Private)
Account Account
Version / Category Version
Time Date (recommended to use custom time format)
Entity Organization
Audit Trail Audit Trail as Generic dimension
Generic/Other Dimensions Generic/Other Dimensions
Model
Model (recommended to use New Model Type with Measures)
Rates Model Currency Conversion Table

For on the fly: Currency Conversion Measure in new
Model Type;
For persisting data: Currency Conversion step as part of
Currency Conversion (Business Rule) Data Action
Data Actions (Advanced Formulas, Copy Step, Allocation

Logic Scripts Step, Cross-model Copy Step)
Advanced Formulas as part of Data Actions

BADI (or as needed Analytics designer calling e.g., API)
Allocation (RUNALLOCATION Script) Allocations or Advanced Formulas
Data Manager Package Data Action
Package Link Multi Action
Dimension Member Formula (MDX) Account Formula
Validation Rule Validation Rule
Transactional data import or export Data Management section of Model
Master Data import Data Management section of a Public Dimension
Transformation file Data Wrangling
Conversion file Data Wrangling
SAP S4/HANA import usingSAP BW Extractor, Data Management:
import into SAP BPC via Data Manager Package Connect to APIs / CDS views
Data Management:
Manual load from CSV/Excel;
Flat File import Automated load from FTP or Google Sheets

Import from other source systems usingSAP BW
extractors, import into SAP BPC via Data Manager Data Management:
Package Load data via supported Connections
Export of transactional Data via BADI orSAP BW Data Management section of Model (Export to File
functionality Server, IBP, ACDOCP etc.)
Data Management, Calendar tasks in combination with
Scheduling of interfaces (Packages / Package Links) Multi Actions
Stories
(Web Based, Analytics Designer, SAP Analytics Cloud
Reports and Input Forms (EPM Excel Add-In) Excel Add-In)
Work Status (Data Locking) Data Locks at Model level
Security (Users, Teams, Task Profiles, Data Access
Profiles) Users, Teams, Roles
Data Audit Data Changes
Activity Audit Activities
Workflow (Business Process Flow) Calendar tasks


BPC STD To SAC 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

BPC STD To SAC Migration Guide

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Business Planning and Consolidation Standard

How to migrate from SAP Business Planning and

2 DIMENSIONS AND MODELS 6

2.3 CURRENCY CONVERSION 12

3.1 LOGIC SCRIPT 14

3.2 CONVERTING SAP BPC ALLOCATIONS IN SAP ANALYTICS CLOUD FOR

3.3 DIMENSION MEMBER FORMULAS 19

3.4 SAP BPC BADI’S AND CUSTOM DEVELOPMENTS 20

3.5 VALIDATION RULES 21

4.1 TRANSFORMATION FILE 22

4.2 CONVERSION FILE 25

4.3 TRANSACTIONAL DATA 25

4.4 MASTER DATA 27

5 INPUT FORMS AND REPORTS 28

5.1 SAP BPC WEB DASHBOARD 28

5.2 SAP BPC EPM ADD-IN 28

5.3 STORIES IN SAP ANALYTICS CLOUD FOR PLANNING 29

5.4 EXCEL REPORTING IN SAP ANALYTICS CLOUD FOR PLANNING 31

6 WORK STATUS (DATA LOCKING) 33

7.3 TASK PROFILES 36

7.4 DATA ACCESS PROFILES 37

8.1 DATA AUDIT 38

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

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

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

2.1.2 Version / Category

SAP BPC Property SAP Analytics Cloud for Comment

ID (M) Member ID (M) Map 1:1, considering SAP

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

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

SAP BPC Property SAP Analytics Cloud for Comment

ID (M) Member ID (M) Map 1:1

2.1.5 Audit Trail

SAP BPC Property SAP Analytics Cloud for Comment

ID (M) Member ID (M) Map 1:1

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

2.1.6 Generic/Other Dimensions

SAP BPC Property SAP Analytics Cloud for Comment

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

2.3 Currency Conversion

The following table provides a comparison:

Category Category The SAP BPC category can be

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

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

3.1 Logic Script

When the logic module is invoked, the system will:

• Read a specific data region (MemberSet section)

The script structure is almost the same

SAP BPC SAP Analytics Cloud for planning

• Scoping MemberSet section • Configuration Section

SAP BPC SAP Analytics Cloud for planning Comments

Member Set definitions

*XDIM_MEMBERSET FLOW = MEMBERSET[d/FLOW] = ("F00",”F99”)

Select Base members

*XDIM_MEMBERSET MEMBERSET[d/Date] = BASEMEMBER([d/Date],”2022”) For syntax and examples click here:

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

*REC DATA() For syntax and examples click here:

*REC(FACTOR=1, DATA()=RESULTLOOKUP([d/Date]=NEXT(12,"MONTH",[d https://help.sap.com/doc/a2c49c40bbe549ef9c291537aa

Cross model data copy

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

Clear data Delete Data

*IS ALLOCATION For syntax and examples click here: