Prepare todays BPC stand-alone planning

projects for a future migration to SAP Simple

Finance in S/4 HANA

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Table of Contents
Introduction and Terminology: S/4 HANA, SAP Simple Finance and SAP BPC optimized for S/4HANA
Finance .................................................................................................................................................... 3
Overview ................................................................................................................................................. 3
Outline of the Concept ............................................................................................................................. 4
BPC stand-alone planning vs. SAP BPC optimized for S/4HANA Finance.................................................... 5
The migration concept ............................................................................................................................. 6
Phase 1 (now): Preparation steps before the BPC implementation starts ................................................. 7
Phase 2 (future): Migration concept for the migration to S/4 HANA ....................................................... 11
Object Migration ................................................................................................................................ 11
Data Migration................................................................................................................................... 12
Maintain Master Data .................................................................................................................... 12
Transactional Data migration ......................................................................................................... 12
Manual Activities ................................................................................................................................... 12
Technical Pre-Requisites ........................................................................................................................ 14

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Introduction and Terminology: S/4 HANA, SAP Simple Finance and SAP
BPC optimized for S/4HANA Finance
SAP S/4 HANA is SAPs next generation business suite and includes SAP Simple Finance as part of the onpremise edition. SAP Business Planning and Consolidation, version for SAP NetWeaver Optimized for
S/4HANA Finance (SAP BPC optimized for S/4HANA Finance) is in turn one of the components of SAP
Simple Finance and provides for the ability to perform real time planning without data replication within
SAP Simple Finance. The model in S/4HANA Finance is based on the SAP Business Planning and
Consolidation Embedded modeling type. The model in S/4HANA Finance also delivers content
(templates, queries and planning functions) not available with a traditional deployment.

Overview
This document describes how to prepare todays BPC stand-alone planning projects for a future
migration to SAP Simple Finance in S/4 HANA. It is important to understand that this is only relevant for
operational financial planning scenarios that are based on ERP FI-CO data (example Cost center-GL
Planning). This document is NOT relevant for any other planning scenarios using BPC. If you have doubts
about that, please first make yourself familiar with the scenario SAP BPC optimized for S/4HANA Finance
is covering.
While no full automatic migration will be possible, a concept is outlined to reduce manual migration
efforts. Expert knowledge and a thorough understanding about BPC 10.1 planning, SAP BW, S/4 HANA
and SAP BPC optimized for S/4HANA Finance concepts are expected. The concept will focus on the
general guidelines of the migration and has to be adapted to the individual project situation. The
concept also only covers the migration of the models, but no data migration aspects in detail.
It is important to note that this document assumes that the SAP BW NW 10.1 embedded planning model
will be used in the creation of planning applications within SAP BPC stand-alone. This document does not
address moving from an SAP BPC Standard model to Integrated Business Planning for finance within
S/4HANA.

This note describes

the necessary steps that have to be carried out before the BPC implementation starts
3

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

how to create compatible content in the BPC stand-alone system

the future migration steps to Integrated Business Planning for finance once the S/4 HANA system
is technically available

Outline of the Concept

Two phases exist, when aiming for a migration:
1.) Things to be considered when creating the solution today in a BPC NW 10.1 stand-alone system:
The key concept is to use in the BPC stand-alone implementation the InfoObjects which are
delivered with SAP BPC optimized for S/4HANA Finance in SAP Simple Finance. Using these
InfoObjects ensures that the content developed today will be compatible with the SAP BPC
optimized for S/4HANA Finance content in the future. These InfoObjects will be included in note
2235568 as transport request B74K900151 (InfoObjects BPC for S/4 HANA) which needs to be
imported into the BPC stand-alone system. Use these InfoObjects in your BPC project today to
be able to migrate most of your models, planning related objects like aggregation level or
planning functions, queries, BPFs etc. using a standard transport request in the future.
2.) Future actions, once a migration is planned:
After a complete S/4 HANA implementation including the activation of the SAP BPC optimized
for S/4HANA Finance content, the InfoObjects will exist in the SAP Simple Finance target system,
as well as standard time and unit InfoObjects such as 0CALMONTH, 0FISCPER or 0UNIT.
Consequently there is no need to transport these Info-Objects from the BPC stand-alone system
to the SAP Simple Finance system.
For the migration from BPC stand-alone to SAP Simple Finance at least two transport requests
need to exist in the BPC stand-alone system:
a. One transport that includes all the /ERP/* and 0 InfoObjects.
b. One or more transports with the objects that should be transported to the SAP Simple
Finance system (i.e. data models, planning functions, queries etc.). Basic BW transport
concepts and best practices also apply hear.
You can use standard transports or use transport of copies in the stand-alone BPC system.

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Remark: If you need to migrate data from BPC stand-alone to SAP Simple Finance you need to
ensure, that the master data is available.

BPC stand-alone planning vs. SAP BPC optimized for S/4HANA Finance
The key differences between a standard BPC planning project in a stand-alone BW system (BPC standalone) and the embedded BPC in S/4 HANA (S/4 HANA) are:

InfoObjects
o BPC stand-alone: 0-namespace and/or customer namespace,
master data filled by replication and stored redundantly
o S/4 HANA: /ERP/-namespace,
master data read from SAP HANA Views during runtime

Acquisition of transactional data

o BPC stand-alone: Objects in 0-namespace and/or customer namespace,
transactional data replicated and stored redundantly
o S/4 HANA:
/ERP/-namespace,
transactional data read from a virtual provider connected to a SAP HANA View

Because all data models, planning functions and query definitions are based on InfoObjects, usage of
different InfoObjects effectively prevents an easy migration from a BPC stand-alone system to an SAP

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Simple Finance system.

This is true even if the same master data can be guaranteed.

The migration concept

The given differences between a BPC-embedded model application in the stand alone scenario and an
S/4 HANA system with SAP BPC optimized for S/4HANA Finance result in the following concept: it is
crucial to use the SAP BPC optimized for S/4HANA Finance InfoObjects already in the creation of BPC
stand-alone scenario if a migration is aimed for.
The following picture visualizes this approach:

Using the same InfoObjects in the BPC stand-alone system will greatly facilitate future migration:
Because all data models, planning functions and query definitions are based on the same InfoObjects,
which will be used in the SAP Simple Finance system, a compatible data model will be created. The
objects excluding the InfoObjects can simply be transported into the SAP Simple Finance system at a
later point in time.
Of course, in the BPC stand-alone system the InfoObjects cannot access SAP Simple Finance views and
therefore master data still needs to be replicated and stored and the same is true for the transactional

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

data.

Phase 1 (now): Preparation steps before the BPC implementation starts

Carry out all steps described in this note in a BPC 10.1 development system.
1. Create the namespace /ERP/ and the namespace /B631/ for the generated objects
Use Transaction SE03 Administration Display/Change Namespaces:
Namespace
Namespace Role
Repair License
SCCR Popup
SAP Standard
Gen. Objs Only

/ERP/
C
<license key>
_
_
_

(Recipient)
(see below)
(do not check)
(do not check)
(do not check)

Namespace
Namespace Role
Repair License
SCCR Popup

/B631/
C
<license key>
_

(Recipient)
(see below)
(do not check)
7

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

SAP Standard
Gen. Objs Only

_
_

(do not check)

(do not check)

The repair license keys for the namespaces can be found in note 2235568.
2. Use Transaction SM30 and Maintenance View RSNSPACE to create the connection:
BW Applic.

BW

Item

<any number> (choose a free number)

Namespace

/ERP/

NS GenObj.

/B631/

Actv.

(check)

3. Use transaction SE03 Set System Change Option to set the namespaces /ERP/ and /B631/ to
Modifiable.
4. Use Transaction SE80 to create a new package with the technical name ZSAP_BPC_S4HANA.
Later on the InfoObjects will be imported into this package. The name has to be identical
otherwise the import will fail.
Leave application component and superpackage open.
Choose a suitable software component.
Switch on Record Object Changes in Transport Requests.
5. Download the files of transport B74K900151 from note 2235568 and put it in the import queue
of your BPC 10.1 stand-alone development system.
Import the transport.

Please use the following settings for the import:

8

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

This creates the SAP BPC optimized for S/4HANA Finance InfoObjects in the /ERP/ namespace.
The generated objects lie in the /B631/ namespace.
Check the import log to verify that the after import method has successfully generated the
InfoObjects.
The SAP BPC optimized for S/4HANA Finance InfoObjects will be created in the package
ZSAP_BPC_S4HANA. Do not use this package except for the import of the S/4 HANA InfoObjects.
6. The following enhancements to the InfoObjects are supported:
You may create additional hierarchies.
You may add additional attributes.
Remark: Changes to the InfoObjects have to be carried out in S/4 HANA as well, BEFORE any
transport is done into the S/4 HANA system.
Notice that in contrast to the S/4 HANA system the Master Data Read Access of all the
InfoObjects has been set to Default. This means that master data tables have been generated.
All master data needs to be maintained manually or uploaded. Do not change this setting.
In the S/4 HANA system, the InfoObjects are based on a SAP HANA View. The Master Data
Read Access does not influence the usage of the InfoObjects for modelling.
Thus, as long as only the Master Data Read Access changes, BW/Planning objects built based
upon these InfoObjects can later be transported to the S/4 HANA system.

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Technically this means, that while the InfoObjects carry the same technical name in both
systems, they are different in the way they access master data: standard SAP BW access (BPC
stand-alone) vs. access from a SAP HANA view (SAP BPC optimized for S/4HANA Finance).
7. Build your data models, planning functions and queries as well as all other objects using the SAP
BPC optimized for S/4HANA Finance InfoObjects. These objects will belong to the customer
namespace.
In case additional InfoObjects are required that are not included in transport request
B74K900151, create them manually. The SAP BPC optimized for S/4HANA Finance InfoObjects
can combined with other BW InfoObjects, e.g. 0-namespace or customer namespace. They can
be used in all BW objects.
Often, InfoObjects in the 0-namespace may exist (if they have been activated) that correspond to
the same business entities as the SAP BPC optimized for S/4HANA Finance InfoObjects.
Example Data Model SAP BPC optimized for S/4HANA Finance: Financials Actuals via Hana
(/ERP/SFIN_V01)

10

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Phase 2 (future): Migration concept for the migration to S/4 HANA

Understand that this note describes a concept for the migration. It builds on the principle of identical
InfoObjects in both source and target systems.
Basically, the idea is to transport all BW and BPC objects such as data models, planning functions, queries
and BPFs but excluding the SAP BPC optimized for S/4HANA Finance InfoObjects from the BPC standalone system to the S/4 HANA development system.
If an import into the S/4 HANA system fails and cannot be solved, the affected objects need to be
created manually. After the objects have all been created in the S/4 HANA system, data can be migrated
if necessary. Details below.

Object Migration
1. First ensure that all SAP BPC optimized for S/4HANA Finance InfoObjects (search for namespace
/ERP/) and 0-InfoObjetcs of dimension time (e.g. 0CALDAY, 0CALMONTH, 0FISCPER, 0FISCVARNT),
unit (e.g. 0UNIT, 0CURRENCY) and BPC Audit Dimension objects (0ATIMSTMP, 0AUSER, 0AMODE,
0ASOURCE) used in your current BPC stand-alone implementation belong to a valid package and a
transport request. Use transaction RSA1 Transport Connection to collect all relevant objects in
case these objects do not yet belong to a package and request.
This transport will NOT be transported into the target S/4 HANA development system. A valid
package and transport request assignment is advised so that while collecting the relevant objects to
be transported no InfoObject named above will make it accidentally on a transport request. This
could cause errors and inconstancies in the S/4 HANA system as these objects will already exist.
2. Second: Create one or more transports for all the other objects of your current planning scenario,
excluding the InfoObjects already included in the first transport, such as InfoProviders, Planning
Functions, Queries, BPFs, etc..
3. Import these transports created in step 2 into the S/4 HANA development system.
This creates the BW objects that already exist in the BPC stand-alone system.
Check the import log to verify that the after import method has successfully generated the
InfoObjects.
You have now re-created the planning scenario in the S/4 HANA system.
11

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Remark:
Typically, planning scenarios are built based on actual data. If you extract data from one or more
Business Suite systems into the BPC stand-alone system, the data acquisition scenarios are likely to
change in the SAP Simple Finance case: Data replication is no longer necessary because the actual data is
available real-time in the embedded BPC. The InfoProvider holding the actual data in the BPC standalone system has then to be substituted in the target system by an InfoProvider that accesses the S/4
HANA transaction data by means of an SAP HANA view.

Data Migration
In case, data has to be migrated, proceed in two steps:
1. Maintain Master Data in SAP Simple Finance
2. Afterwards migrate Transactional Data
Maintain Master Data
Master data has to be maintained only, if the BPC stand-alone transactional data contains additional
master data not yet available in the SAP Simple Finance system. This has to be decided separately for
each InfoObject.
In case you enhanced the planning models in the BPC stand-alone system by additional InfoObjects
in the customer namespace, their master data has to be replicated in any case.

Transactional Data migration

Once the master data is available in the SAP Simple Finance system, transaction data can be migrated
using standard BW techniques.

Manual Activities
The key figure /ERP/AL_RATIO (Allocation Ratio) has not been included in the transport B74K900151. The
key figure requires a dedicated Domain with an extended length compared to the standard length of the
Data Type DEC. If you need this key figure please create it manually.

12

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

Please use the attached screenshots to create the key figure and take the note 460652 - Extending key
figures in BW into consideration. The screenshots are taken from an S/4 system, thus the domain name
(FCOM_ALLOCATION_RATIO) lies within the SAP Namespace. Please use a different name when creating
the domain in the BPC stand-alone system: e.g. add a prefix like Z: ZFCOM_ALLOCATION_RATIO.
1.) Key figure definition:

2.) Domain definition:

13

PREPARE TODAYS BPC STAND-ALONE PLANNING PROJECTS FOR A FUTURE MIGRATION TO SAP
SIMPLE FINANCE IN S/4 HANA

3.) Data element definition:

Technical Pre-Requisites
Please ensure that the SAP BW System and the SAP Simple Finance system (once you start migrating
content from a BPC standalone system) is at least on the following release/support package:
For SAP Simple Finance 1503 and SAP BW 7.40: SAP Netweaver 7.40 SP11
For SAP Simple Finance 1602 and SAP BW 7.50: SAP Netweaver 7.50 SP04
SAP HANA: SP10 Rev. 102 or newer

14