PLANNING AND CONSOLIDATION

Data Migration Strategy

April 2019
Executive Summary

The purpose of this document is to define Data Migration Strategy to migrate data from existing sources into the
SAP BPC, document critical decisions made during the data work stream that impact the strategy and define how to
manage the transition period in order to “phase” BPC go-live and S/4 go-live throughout the countries.

The document include five main sections:

1. Data Migration Steps The goal is define the five steps required to deliver successful data migration

2. Data Migration The goal is define timelines for each activity defined in the strategy
Timelines

3. Roles and The goal is define data migration team, process owner, effort and responsibilities for each
Responsibilities activity defined in the strategy

4. Interim Period The goal is explain how transition period will be managed in terms of datasets and timing /
frequencies considering the specificity of each country in terms of S/4 go-live

5. Data migration The goal is explain multiple options has been assessed in order to get an agreed
scenarios for “Scenario” to migrate data for Management Consolidation and identify the main activities in
Management order to pursue chosen scenario
Consolidation
2
Overview of approach
The diagram below outlines the five steps required to deliver successful data migration.
Identify
Determine the data that is
required to load into the
Planning and Consolidation
System
It is important to determine the
amount of data (i.e. how many
periods) that is required. There is a
fine balance between what is
required for comparative /
reconciliation purposes and the
increased risk that comes with
migrating a larger data set. It is also
necessary to determine the type of
data (actual / budget / forecast) and
the sources that data will be migrated
from. All of this should be
determined in the Definition phase
and is often referred to as the “scope”
of the migration or integration. This is
outlined later in this document.
Slide 3
Preparation
Collate the source and create
the necessary tools to load it
The data migration/integration
resources will be responsible for
collating the source files for migration
and creating the necessary tools
(ETL application, Excel templates or
data entry forms, or a combination of
the three) for migration and
integration.
Mapping
Prepare the mapping tables
that convert source data into
a format that is readable/
loadable to the new system
For data to be migrated and
integrated, the first step is to create
mapping tables that will convert
source data (Excel, SAP BCS, SAP
ECC) into a format that is readable/
loadable into SAP BPC.
These mapping tables essentially
consist of columns of information -
source value, target value., attributes
of the data source extract and
specified member of the Planning
and Consolidation dimensions.
Load
Load and validate the data
into the new Planning and
Consolidation tool
This stage of the approach involves
loading and validating the data into
SAP BPC. Validating the data
ensures each source line of data has
been mapped to valid intersections
within the Planning/Consolidation
solution, for example if data is being
loaded to an intercompany sales
account, mappings exist for the
account and intercompany
dimensions. Migrated data will need
to be validated to ensure that all data
from the source applications has
been captured and accounted for
correctly in the mappings.
Reconciliation
Confirm that the number
migrated or integrated into the
new system ae accurate and
match with those in the data
sources
Typically reconciliation will only occur
at two points, after the completion of
the migration process and after the
first integration. Once the data
integration processes and mappings
have successfully passed
reconciliation it should not need to be
repeated in future integrations unless
integration parameters (data sources
and mappings) are changed.
Summary of data migration Activities
The document describes in detail the requirement of data migration, and takes the reader through what will be migrated. For
ease of understanding, the outcome of the data migration document has been summarized in the two following tables.

STATUTORY CONSOLIDATION
# Dataset
1 January to December FY19 and
monthly data required to have
entire FY19
2 Jul – Dec 2018 Full Year-End and
Monthly data
3 Dec 2017 Closing Balance and Jan
– Jun 2018 Full Year and Monthly
data
Data Migration
PLANNING
How it will be obtained Priority # Dataset How it will be obtained Priority
1 Annual Budget 2019 Migration from Excel – P&L by
High
Migration from IAS High Country
2 Current Quarterly Forecast 2019- Migration from Excel – Full P&L
2020 (by Brand, by Country, by Line
Migration from IAS High High
of Business) by month 2 years
(april version 2019)
Migration from IAS Medium 3 Monthly 2019 S&OP Migration from Excel High

MANAGEMENT CONSOLIDATION
# Dataset
1 18FY and Jan to May 2019 monthly
data, with management details
2 15FY - 17FY monthly data, with
management details
3 Jul-Dec 2018 and Jan- May 2019
monthly data for Holding
Companies
How it will be obtained Priority
To reduce the risk and the complexity of management data
Migration from Local BW High conversion and loading we will consider a phased
approach with incremental steps of data enrichment
Migration from Local BW (15FY
may not be in Local BW – High
check how it will be obtained)
Migration from IAS High

Slide 4
High level data migration architecture

Company A
Applications

Assumptions
• Source data will be extracted by respective Company A source teams and will be put in secure file location.
• The structure of landing area and staging areas will be decided based on S2T mapping and requirements
• Loading to the target applications will be decided based on the S2T mapping, data volumetric and data categorization
• *ERP Historical Data – As per reporting requirement from specific area.
• Target Applications will be modified based on selection.

Slide 5
Data Flow Summary
Mapping Staging
CONSOLIDATION Data Source Process Dimensions Dataset Environment Data Target

• Legal Entity Statutory Dataset

• Account (new CoA)
STATUTORY

IAS •
January to December FY19
Profit Centre C1 and monthly data required to
have entire FY19
• Trading Partner
• Transaction Type C2
Jul – Dec 2018 Full Year-End
and Monthly data
S/4 BPC
• Balancesheet
Dec 2017 Closing Balance
Movements and Jan – Jun 2018 Full Year
• Period C3 and Monthly data

Management
CONSOLIDATION

• Legal Entity Dataset

MANAGEMENT

• Account (new SCoA)

18FY and Jan to May BW
• Profit Centre 2019 monthly data, with
• Trading Partner
M1 management details

• SKU 15FY-17FY monthly data,

• Reporting Customer M2 with management details

• Line of Business Jul – Dec 2018 and Jan - May

IAS* • Cost Centre M3 2019 monthly data (Holding

Companies)
S/4 BPC

• Legal Entity Planning Dataset

BW
PLANNING

• Account P1 Annual Budget 2019

• Customer
• SKU / Product Current Quarterly
P2 Forecast 2019-2020
Category / Brand
• Cost Centre / Monthly 2019 S&OP
Functional Area
P3 S/4 BPC

* Holding Companies comes from IAS for Mgmt Consolidation

Slide 6 ** For Holding Companies dataset will be Legal Entity, Account (new SCoA)
Summary of current data sources/repositories

# Geographic Area SAP transactional Management Consolidation Planning Statutory Consolidation

System SAP BW System System System
1 Canada, US, LATAM, Central America Cordillera MSBI Oracle PBCS / Excel IAS
2 Europe (excl. Portugal and Greece) Sirius Finance Connect Excel IAS
3 Portugal Local SAP Portugal Local BW Excel IAS
4 Greece Local SAP for Greece Local BW Excel IAS
5 APAC U2K2 BW Excel IAS
6 Southern Asia Fusion BW Excel IAS

Slide 7
Summary of timelines – Initial migration and Interim State by Process

2019 2020

Processes Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb

Initial Historical data load

Management Consolidation
Interim Period

Initial Historical data load

Statutory Consolidation

Interim Period

Initial Historical data load

Planning
Interim Period

Slide 8
1. Data migration Steps
 Identify Preparation Mapping Load Reconciliation

1.1 Identify
Summary of data sets
The requirements for Data Migration have been summarised below for both Consolidation (Statutory and Management) and Planning
workstreams.

Statutory Consolidation Management Consolidation Planning

• •
C1 Jul – Dec 2018 Full Year-End and
Monthly data (P&L and BS), in
order to provide comparatives after
go-live
• Dec 2017 Closing Balance and Jan
Requirements
M1 18FY and Jan to May 19 monthly
data, with management details
(product, customer, profit centre,
etc.)
M2
• 15FY-17FY with management
•
P1 Annual Budget 2019, required to provide
comparatives and drive Annual Budget
2020 preparation in the new system
•
P2 Current Quarterly Forecast 2019-2020,
required to provide comparatives and

C2
– Jun 2018 Full Year and Monthly details (product, customer, profit drive Quarterly Forecast preparation in
data (P&L and BS) centre, etc.) the new system

•
C3 January to December FY19 and
monthly data required to have
entire FY19 (different for all
geographic areas)
•
M3 Jul-Dec 2018 and Jan- May 2019
monthly data (Holding Companies)
•
P3 Monthly 2019 S&OP, required to provide
comparatives and drive S&OP process in
the new system.

Legend:
S – Statutory
M – Management
P – Planning
Slide 10
 Identify Preparation Mapping Load Reconciliation

1.1 Identify
Stat Consolidation – data sets

Dataset Why it is needed How it will be migrated

C1 Jul – Dec 2018 Full Year End and Monthly data are required to be in the system Data come from IAS consolidation system and
Monthly data (P&L and BS) so that the entire FY19 will be made available in data flow has to be mapped into BPC
the new tool. The timespan actually covered
depends on the geographic area

Dec 2017 Closing Balance and Jan – Jun In order to recalculate FY18 year end in the Data come from excel who is built restating
C2
2018 Full Year and Monthly data (P&L tool, there is a need to have the opening Company A Financial Statement. Data flow has
and BS) balances (which are the closing balances of to be mapped into BPC
December 2017) available in the tool

C3 January to December FY19, monthly The Consolidation tool will go live with Data come from IAS consolidation system and
data, required to have entire FY19 in the December 2019 month end. The following data flow has to be mapped into BPC
system periods will be prepared directly in BPC, there
is a need to have December 2018 in the tool for
comparatives

Slide 11
 Identify Preparation Mapping Load Reconciliation

1.1 Identify
Management Consolidation – data sets

Dataset Why it is needed How it will be migrated

M1 18FY and Jan to May 19 monthly data, BPC need to include FY18 and 2019 data in Data comes from Local BW and data flow has
with management details (product, order to provide comparatives to be mapped into New BW
customer, profit centre, etc.)

M2 15FY - 17FY monthly data, with BPC need to include 15FY - 17FY data in order Data comes from Local BW and data flow has
management details (product, customer, to provide comparatives to be mapped into New BW
profit centre, etc.)

M3 Jul-Dec 2018 and Jan- May 2019 BPC need to include Holding Companies in Data comes from IAS and data flow has to be
monthly data (Holding Companies) Mgmt Consolidation as well in order to include mapped into New BW
all legal entities

Slide 12
 Identify Preparation Mapping Load Reconciliation

1.1 Identify
Planning – data sets

Dataset Why it is needed How it will be migrated

P1 Annual Budget 2019 Budget 2019 should be available in the system Data come from excel and data flow has to be
to provide comparatives and support the mapped into BPC
preparation of Budget 2020

P2 Current Quarterly Forecast 2019-2020 Quarterly figures for FY19 Forecast are Data come from excel and data flow has to be
required to be in the tool to provide support for mapped into BPC
the Forecast 2020

P3 Monthly 2019 S&OP All figures for S&OP 2019 by month should be Data come from excel and data flow has to be
available in the tool mapped into BPC

Slide 13
 Identify Preparation Mapping Load Reconciliation

1.2 Preparation
Stat Consolidation – What data set preparation is required?
Based on the considerations described in the previous tables, not all data requirements generate the need to migrate a data set. Some data
are for example re-built as part of the testing activities. The following tables describe, only for the dataset that need to be migrated, the
level of detail that needs to be made available

Requirements Dataset Data Source Notes

For the requirements C1, C2, C3 will need a

Jul – Dec 2018 Full Year End and dataset with the following fields (dataset #1, IAS
C1
Monthly data (P&L and BS) #2, #3):

• Legal Entity
• Account (new CoA)
• Trading Partner
• Transaction Type
Dec 2017 Closing Balance and Jan – Jun • Balancesheet Movements
Excel (Restated Company Restated
C2 2018 Full Year and Monthly data (P&L • Period
starting from UL Financial Statement is
and BS) • Closing Balance (for each entity,
Financial Statement) at Country level of
cumulated, including all consolidation
detail
journals)

January to December FY19, monthly

C3 IAS
data, required to have entire FY19 in the
system

Slide 14
 Identify Preparation Mapping Load Reconciliation

1.2 Preparation
Management Consolidation – What data set preparation is required?
Based on the considerations described in the previous tables, not all data requirements generate the need to migrate a data set. Some data
are for example re-built as part of the testing activities. The following tables describe, only for the dataset that need to be migrated, the
level of detail that needs to be made available

Requirements Dataset Data Source Notes

FY18 and Jan - May 2019 monthly 15FY - FY18 and Jan - May 2019 monthly data,
M1 with management details, with the following
data, with management details
(product, customer, cost centre, etc.) fields: Local BW (15FY has to
• Legal Entity be rebuild)
• Account (new SCoA)
15FY - 17FY monthly data, with • Trading Partner
M2
management details (product, • SKU
customer, cost centre, etc.) • Reporting Customer
• Cost Centre
• Line of Business
• Final Balance for each month in EUR

Jul-Dec 2018 and Jan- May 2019
M3
monthly data (Holding Companies)
Jul-Dec 2018 and Jan- May 2019 monthly data IAS
with the following fields:
• Legal Entity
• Account (new SCoA)
• Final Balance for each month in EUR

Slide 15
 Identify Preparation Mapping Load Reconciliation

1.2 Preparation
Planning – What data set preparation is required?
Based on the considerations described in the previous tables, not all data requirements generate the need to migrate a data set. Some data
are for example re-built as part of the testing activities. The following tables describe, only for the dataset that need to be migrated, the
level of detail that needs to be made available

Requirements Dataset Data Source Notes

P1 Annual Budget 2019 Excel

Planning requirements will need a dataset
with the following fields ( dataset #1, #2, #3,
#4):
• Legal Entity
P2 • Account
Quarterly Forecast 2019 Excel
• Customer (1)
• SKU / Product Category / Brand
• Cost Centre / Functional Area
• Line of Business
• Value in EUR
P3 Monthly S&OP 2019 Excel

Slide 16 (1)
Reporting Customer could be an acceptable level of detail
 Identify Preparation Mapping Load Reconciliation

1.3 Mapping
Data Model Details that will require mapping
Group Rate / Group
Statutory Ownership Managerial
and Planning

1 2 3
The table identifies the lowest level of detail for
each dimension that should be made available in LEGAL ENTITY Legal Entity Legal Entity R
Legal Entity

the application in order to deliver the project ACCOUNT Group Account Group Account Group Account
initiatives.
PRODUCT SKU

The use of “Reporting Customer” level of detail for CUSTOMER Reporting Customer

the Customer dimension is still to be validated.

PROFIT CENTRE Profit Centre Profit Centre Profit Centre

TIME Month Month Month

CURRENCY Local currency Local currency Local currency

INTERCOMPANY Legal Entity Legal Entity Legal Entity

CONSOLIDATION SCOPE Group Group

BALANCESHEET MOV Single Mov Single Mov

VERSION Actual Actual,Plan,Forecast Actual,Plan,Forecast

AUDIT TRAIL Input, Calc, Final Input, Calc, Final Input, Calc, Final

LINE OF BUSINESS Line of Business

COST CENTRE Cost Centre

Slide 17
 Identify Preparation Mapping Load Reconciliation

1.3 Mapping
Data Mapping Process Recap
Mapping Staging
Data Source Process Dimensions Dataset Environment Data Target
CONSOLIDATION

• Legal Entity Statutory Dataset

• Account (new CoA)
STATUTORY

IAS •
January to December FY19
Profit Centre C1 and monthly data required to
have entire FY19
• Trading Partner
• Transaction Type C2
Jul – Dec 2018 Full Year-End
and Monthly data
S/4 BPC
• Balancesheet
Dec 2017 Closing Balance
Movements and Jan – Jun 2018 Full Year
• Period C3 and Monthly data

Management
CONSOLIDATION

• Legal Entity Dataset

MANAGEMENT

• Account (new SCoA)

18FY and Jan to May BW
• Profit Centre 2019 monthly data, with
• Trading Partner
M1 management details

• SKU 15FY-17FY monthly data,

• Reporting Customer M2 with management details

• Line of Business Jul – Dec 2018 and Jan - May

IAS* • Cost Centre M3 2019 monthly data (Holding

Companies)
S/4 BPC

• Legal Entity Planning Dataset

BW
PLANNING

• Account P1 Annual Budget 2019

• Customer
• SKU / Product Current Quarterly
P2 Forecast 2019-2020
Category / Brand
• Cost Centre / Monthly 2019 S&OP
Functional Area
P3 S/4 BPC

Slide 18
 Identify Preparation Mapping Load Reconciliation

1.3 Mapping
Stat Consolidation – Dimensions to be mapped and how

DIMENSIONS SOURCE OF SIGN-OFF CREATED BY LEVEL OF DETAIL NOTES

MAPPING
Statutory
Legal Entity list in
LEGAL ENTITY IAS Group Controller Consolidation Company Code
appendix
Leader
GL Account from IAS CoA into BPC (new Excel mapping in
ACCOUNT IAS Group Controller PwC
SCoA) appendix
BALANCESHEET MOV IAS Group Controller PwC Movements level into BPC
Statutory
TRADING PARTNER IAS Group Controller Consolidation Company Code mapping
Leader
Statutory Each Company has to be mapped with Profit Centre is
New Master
PROFIT CENTRE Group Controller Consolidation related Profit Centre – Global Company will linked one-to-one
Data
Leader be spread on BPC. with Legal Entity
PERIOD Not to be mapped

Slide 19
 Identify Preparation Mapping Load Reconciliation

1.3 Mapping
Management Consolidation – Dimensions to be mapped and how
DIMENSIONS SOURCE OF SIGN-OFF CREATED BY LEVEL OF DETAIL NOTES
MAPPING
Statutory
Same mapping needed
LEGAL ENTITY IAS Group Controller Consolidation Company Code
for Stat Consolidation
Leader
GL Account from Local BW
Management
Local BW / management CoA into BPC (new
ACCOUNT (1) Group Controller Consolidation
IAS SCoA). GL Account from IAS for Holding
Leader / PwC
Companies
Management The required detail will be confirmed by
COST CENTRE Local BW Group Controller Consolidation Group finance after the first load and
Leader data checks
Master Data One to one mapping from
PRODUCT (2) Local BW Group Controller SKU level from Local BW to New BW
Leader New BW and BPC
Master Data Reporting Customer level from Local
REPORTING CUSTOMER Local BW Group Controller
Leader BW to New BW
Management
Line of Business level from Local BW to
LINE OF BUSINESS Local BW Group Controller Consolidation
New BW
Leader
Each Company has to be mapped with Profit Centre is linked
New Master Master Data
PROFIT CENTRE Group Controller related Profit Centre – Global Company one-to-one with Legal
Data Leader
will be spread on BPC. Entity
TRADING PARTNER Not to be mapped

(1)
Account: Local BW may have different CoAs to be mapped into the new SCoA
(2)
Product: check if will need “Obsolete” members for Products in the new hierarchy
Full detail for Canada. Total Product and Total Customer for RofW in first phase, and then enriched as they go-live on S/4 -
according with Scenario 2 (see detail in Section 5)
Slide 20
 Identify Preparation Mapping Load Reconciliation

1.3 Mapping
Planning – Dimensions to be mapped and how

DIMENSIONS SOURCE OF SIGN-OFF EXECUTED BY LEVEL OF DETAIL NOTES

MAPPING
Statutory
LEGAL ENTITY IAS Group Controller Consolidation Company Code Check level of detail
Leader
Management Accounts from Excel
ACCOUNT PwC
schemas into BPC
Product Category / Brand level from
Management Master Data SKU Is needed to build
PRODUCT Excel to BPC (@ same level of
Consolidation Leader Leader Company hierarchy
aggregation)
Excel
Master Data Reporting Customer level from Excel to
CUSTOMER
Leader BPC
Management The required detail will be confirmed by Check if it’s a planning
Management
COST CENTRE Consolidation Group finance after the first load and dimension for OVHs
Consolidation Leader
Leader data checks costs

Slide 21
 Identify Preparation Mapping Load Reconciliation

1.4 Loading
Loading Procedure for Planning and Consolidation
The data load into BPC will be completed using “Data Packages”. These are built on the standard data load functionality of BPC and
require two files:
• Data file – This is the actual file to be loaded
• Transformation file – This is the mapping file that explains the link between the field available in the data file and the BPC data
model
Staging Environment Target
Area
BW
BW
SAP DS SQL DB
S S Data File
Server
A A
P P
IAS Files
BW BPC BPC
D D
S S (TEST) (PROD)

Comment:
• Consider the use of BW as repository of history
• Technically also the history will be in S/4
Data will be migrated or re-built using the BPC Test system.
Reconciliation will be completed in the same system, and will then
have to be “technically” migrated to the Production System

Slide 22
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Reconciliation procedure for Planning and Consolidation
Each dataset loaded in BPC will have to be reconciled back to the original source.
Each dataset will need an owner, responsible for reviewing the outcome of the load and signing off its successful completion

It is important to note that reconciliation need to happen also for the dataset that do not require migration, for example those that will be re-
created in the system as part of the testing activities.

In order to confirm what is meant by successful reconciliation, the dataset owner will need to provide the level of detail at which the dataset
needs to reconcile back to the data source

Slide 23
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Stat Consolidation - Complexities expected when reconciling data
# Dataset Source Data BPC reconciliation Technical Business Potential issues and proposed resolution
area Responsible Responsible
1 January to IAS report BPC report System Statutory This will be migrated from the current
December FY19, Integrator Consolidation Consolidation environment. Main issues may
monthly data, Leader come form account mismatch and dimensions
required to have recreation.
entire FY19 in the • Account: one-to-many mapping from IAS
system CoA to new Company SCoA
• Build Profit Centre
2 Jul – Dec 2018 Full IAS report BPC report System Statutory This will be migrated from the current
Year End and Integrator Consolidation Consolidation environment. Main issues may
Monthly data (P&L Leader come form account mismatch and dimensions
and BS) recreation:
• Account: one-to-many mapping from IAS
CoA to new Company SCoA
• Build Profit Centre
3 Dec 2017 Closing IAS report BPC report System Statutory This will be migrated from rested excel starting
Balance and Jan – Integrator Consolidation from UL Financial Statement. Main issues may
Jun 2018 Full Year Leader come form different level of detail of new
and Monthly data consolidation system.
(P&L and BS) • Legal Entity: Detail not available in data
source (Country is available)
All datasets Data in the source is not derived from a
regular “business as usual” scenario. Potential
issues affecting reconciliation will arise when
transactions happened (e.g. acquisitions and
disposals)

Slide 24
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Management Consolidation - Complexities expected when reconciling data
# Datasets Source Data BW BPC Technical Business Potential issues and proposed
reconciliation reconciliation Responsible Responsible resolution
area area
1 18FY and Jan Local BW BW report BPC report System Regional This will be migrated from the Local
to May 19 (existing UL (new Company Integrator Performance BW. Main issues may come form:
monthly data, report) / IAS report) Manager • hierarchies recreation: LoB as new
with report dimension to build
management • reconciliation with Stat
details Consolidation: data comes from
different data flow (IAS vs Local
BW / iFinance)

2 15FY - 17FY Local BW BW report BPC report System Regional • Same as the previous point
monthly data, (existing UL (new Company Integrator Performance • 15FY recreation
with report). Source report) Manager
management TBD for 15FY
details

All datasets Regional Data in the source is not derived from

Performance a regular “business as usual”
Manager scenario. Potential issues affecting
reconciliation will arise when
transactions happened (e.g.
acquisitions and disposals)

Slide 25
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Planning - Complexities expected when reconciling data
# Dataset Source Data BPC reconciliation Technical Business Potential issues and proposed resolution
area Responsible Responsible
1 Annual Budget Excel BPC report System Regional This dataset will be re-built in BPC. Complexity
2019 Integrator Performance is expected in:
Manager • Re-create dataset from Excel
• Differences in CoA mapping
2 Quarterly Excel BPC report System Regional This dataset will be re-built in BPC. Complexity
forecast 2019- Integrator Performance is expected in:
2020 Manager • Re-create dataset from Excel
• Differences in CoA mapping
3 Monthly S&OP Excel BPC report System Regional This dataset will be re-built in BPC. Complexity
2019 Integrator Performance is expected in:
Manager • Re-create dataset from Excel
• Differences in CoA mapping

Slide 26
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Complexity on reconciliation of historical data scenarios
Follow an hypothesis to manage in BPC different scenarios in order to restate and compare date within the same consolidation scope.
The approach suggested is based on two steps:

1. Consol View to aggregate entities within the same consolidation scope in order to consider changes due to disposal / acquisition
2. Manual Journals to restate data (intercompany related to disposed / acquired entity) in order to coherently compare different periods

Example: restatement due to disposal

Year N-1 Year N

Manual Journals allows to restate data in
order to make comparable periods by Entity 001
disposal effect (e.g. equity, receivables,
payables, etc.). No restatement needed for Entity 002
product / customer hierarchies – old
hierarchies will already ready restated to the Entity 003
new structure (As Is – As Was approach)
Entity 004
Consol View 1: Allows to
represent data within the current
consolidation scope (Entity 001,
…, Entity 004)
Entity 001 Consol View 2: Allows to
represent data within the new
Entity 002 consolidation scope (Entity 001,
Entity 002, Entity 003) for both
Entity 003 Year N-1 and Year N
• Approach can be adopted to perform adjustment in order to
manage exceptional transactions as acquisitions (full, light,
phased, etc.) and disposals
• In general the approach can be adopted to perform any kind
of restatement
• Approach can be adopted for both interim and end state
period

Slide 27
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Technical Method: How Stat and Mgmt reconciliation will be performed in BPC (1/2)
Main assumptions:

• Statutory consolidation for historical data will require two different processes in BPC:
1)
1.1 Load TB from IAS into a dedicated “IAS scenario”, including “IAS only” entities.
1.2 Apply appropriate journals
1.3 Consolidate this scenario to get a Group view of IAS data in BPC (Stat Consolidation – mode 1)
2)
2.1 Load TB from managerial consolidation BPC into Actuals scenario environment (original source local BW’s then mapped)
2.2 Load “IAS Only” entities
2.3 Apply journals as requested
2.4 Consolidate this scenario to get a Group statutory view from Management Data (Stat Consolidation – mode 2)

Three different reconciliations are then needed in BPC:

1. Stat Consolidation in BPC vs historical data coming from IAS
2. Mgmt Consolidation in BPC vs historical data coming from BW
3. Stat Consolidation data built coming from then two different sources-

Note: Management Consolidation for historical data will be run in BPC loading data from BW only, so recalculation will be needed only against management data.

Slide 28
 Identify Preparation Mapping Load Reconciliation

1.5 Reconciliation
Technical Method: How Stat and Mgmt reconciliation will be performed in BPC (2/2)

1. Reconciliation process will be done in order to check stat

consolidation in BPC will match historical data from IAS:
BPC scenario “IAS View”
1 BPC – Stat
IAS
Consolidation
IAS View
Historical data
2. Reconciliation process will be done in order to check
(Legal Entity TB)
mgmt. consolidation in BPC will match and historical data
from BW (and ultimately iFinance) : BPC Scenario “BW View”

3
3. Reconciliation process will be done in order to check the
alignment between the two statutory consolidation views..
Two different actual versions will be created in BPC in order
to manage the “two way” scenarios.

2 BPC – Stat Adjustments journals will be performed in BPC (BW View) if

BW BPC – Mgmt
Consolidation needed to align it to the IAS View.
Consolidation
BW VIew
Historical data
(Mgmt detail)

Slide 29
2. Data migration timelines
2.1 Data migration timelines
Statutory Consolidation
2019

Apr May Jun Jul Aug Sep Oct Nov Dec

Activities Created by

Provide data file Company

Create mapping
Company
table Data loaded
into BPC
Load data into BPC System
(Test) Integrator

System
Integrator
Reconcile data
load (BPC)
Company

Detailed reconciliation
Mapping table Technical done by Company with
created and data reconciliation System Integrator
file provided done technical support.
Reconciliation with Mgmt
Consolidation done

Stat Conso Stat Conso Stat Conso

Deploy start parallel runs in BPC
runs
Slide 31
2.1 Data migration timelines
Statutory Consolidation - Prerequisites and Key Assumption on the timelines

Key assumptions and prerequisites

1) Company B group finance will support the following activities:

a) Perform IAS data extracts for all entities
b) Perform mapping activities for CoA translation,
c) Validate and reconcile the data where required
d) Provide significant resource support during initial historical migration and provide continued
support during the “interim” stages of migration.

2) System Integrator will support by creating and managing BPC target environments, leading migration
and do a technical reconciliation of the data from IAS into BPC

Slide 32
2.1 Data migration timelines
Management Consolidation
2019

Apr May Jun Jul

Activities Created by May 31st June 14th Jun 30th

Mapping table created
and data file provided
Provide data file Company

Create mapping table / Company

Transform data Company
Data loaded into BW

System
Load data into BW
Integrator

System
Integrator
Reconcile data load
(BW)
Company

May Mgmt P&L

ready to load in
Data migrated for all BPC
Migration on BPC
Load data into BPC System Mgmt P&L Actuals (Production) of data
(Production) Integrator up until April until April

Interim / Data
Enrichment

Data enrichment / interim will be needed in order to Readiness of

BPC environment
manage transition before S/4 go-live - canada not
included (see detail in sections 4 and 5)
Slide 33
2.1 Data migration timelines
Management Consolidation
Data Migration Plan

 June 30th  Stand up / readiness of BPC environment

 May 31st  Data migrated for all Mgmt P&L Actuals up until April. In order to meet the deadline we need:
- Data mapped and transformed System Integrator / Company by May 24 th (allowing time for technical validation & resubmission
if needed)
- Mock migration into BPC Quality system for business simulation testing between 3 rd and 7th June
- Would be preferable to get this data on 10 th May in order to use it for SIT
 June 14th  Migrate May Mgmt P&L 'Actuals' into BW / BPC
- Data mapped and transformed by System Integrator / Company by June 14 th (allowing time for technical validation &
resubmission if needed)
- Migration of this data and the actuals up to April into the BPC Production system between 24 th and 28th June
 July 1st/2nd  Trigger load of June 'Actuals' from S4 into BPC

Slide 34
2.1 Data migration timelines
Management Consolidation - Prerequisites and Key Assumption on the timeline
Scope: Migrate P&L for all Regions from Local
BWs. Full detail for Canada. Total Product
and Total Customer for RofW
Key assumptions and prerequisites
1) Performance Managers in regions will support with the following activities Canada
• Approach: Bottom Up
a) Current BW data extracts, for all countries
• Source: Local BW
b) Perform mapping activities for Local CoA translation, Product / Customer (when relevant) • Account: Full mapping to new SCoA
c) Validate and reconcile the data where required • Product: Full SKU mapping
• Customer: Local Customer
d) Provide sign off on the migrated numbers - post a review with Regional CFO.
• LoB: combination of Product and Customer
e) Provide significant resource support during initial historical migration and provide continued • Period: Priority: FY18, FY19 (until go-live)
support during the “interim” stages of migration. FY17, FY16, FY15
RofW
2) System Integrator will support by leading BW technical set up and reconciliations
• Approach: Bottom Up
a) Create and manage technical environments (Data services, target BW) • Source: Local BWs
b) Transfer BW extracted data to Data Staging Area • Account: Full mapping to new SCoA
• Product: “Total Product” level mapping
c) Transform and Load data into BW (via robust ETL using Data Services)
• Customer: “Total Customer” level mapping
d) Perform initial technical reconciliations and provide reconciliation templates • LoB: old dimension
3) System Integrator will support by creating and managing BPC target environments, leading migration • Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
and reconciling the data from BW into BPC
• Company Resource effort: High
• BW Resource effort: High
• Mapping effort / complexity: High
• Time required: > 4 months

Slide 35
2.1 Data migration timelines
Planning
2019

Apr May Jun

Activities Created by May 10th May 31st

Provide data file Company

Create mapping table /

Company
Transform data
Data mapped and
transformed – Budget
Perf.
Reconcile data and Forecast Q1
Manager

System
Integrator
Load and reconcile
data in BPC
Company as a support Migration into BPC
Company
Production system

Mock migration into

BPC Quality system

Readiness of
BPC environment
Slide 36
2.1 Data migration timelines
Quarterly Forecast
Data Migration Plan

 May 31st  Stand up / readiness of BPC environment

 May 31st  Migrated budget and Q1 forecast into BPC. In order to meet the deadline we need:
- Data mapped and transformed by May 10 th (allowing time for technical validation & resubmission if needed)
- Mock migration into BPC Quality system for business simulation testing between 20 th and 24th May
- Migration into BPC Production system between 10 th and 14th June

Slide 37
2.1 Data migration timelines
Planning - Prerequisites and Key Assumption on the timelines

Key assumptions and prerequisites

1) Company B group finance will support the following activities:

a) Review Excel templates of existing forecast
b) Perform mapping activities for CoA translation,
c) Validate and reconcile the data where required
.

2) System Integrator will support by creating and managing BPC target environments, leading migration
and do a technical reconciliation of the data from Excel into BPC

Slide 38
3. Resource plan – roles and
responsibilities
3.1 Roles and responsibilities for data migration
Data migration Team Leads
Follow team and timeframe proposed for data migration activities for Consolidation and PB&F

STATUTORY CONSOLIDATION MANAGEMENT CONSOLIDATION PB&F

ACTIVITY OWNER TIMEFRAME OWNER TIMEFRAME OWNER TIMEFRAME

Statutory Consolidation
LEAD Master Data Leader Mgmt Conso Leader
Leader
PROVIDE DATA Statutory Consolidation Master Data Leader / System
July Mgmt Conso Leader Mar
FILES Leader Integrator Mar
Local - Regional Perf Mgrs
MAPPING/ Statutory Consolidation
Aug Master Data Leader Apr
CONVERSION Leader Core - Master Data Leader /
System Integrator Apr
LOAD System Integrator Sep Local - Regional Perf Mgrs System Integrator Apr
BW Load - System Integrator
TECHNICAL Apr / May
System Integrator Sep BPC Load - System Integrator System Integrator May
RECONCILIATION
BW Load - System Integrator
FUNCTIONAL Statutory Consolidation Apr / May
Sep - Nov BPC Load - System Integrator Mgmt Conso Leader and
RECONCILIATION Leader May
Regional PM
Core – Master Data Leader /
Mgmt Conso leader Apr / May
Local - Regional Perf Mgrs

Slide 40
3.1 Roles and responsibilities for data migration
Estimated effort / timing for resources - Statutory Consolidation
ACTIVITY OWNER TIMEFRAME DATA TEAM ACTIVITY EXTRA
RESOURCE
REQUIRED

Statutory Consolidation ● Project manage activities

Lead Ongoing
Leader ● Responsible for timelines and overall sign off of data

Statutory Consolidation
Provide Data Files July ● Provide data files in supportive format to facilitate easy mapping and load into BPC
Leader

● Create mapping in required format

Statutory Consolidation
Mapping / Conversion Aug ● Mapping file for SCoA, Profit Centre, Intercompany, Legal Entity
Leader ● Work with System Integrator to align IAS code to BPC dimension code

● Work with System Integrator team to check Loaded files.

Load System Integrator Sep ● Support where values do not load, or mappings do not match.
0.2 FTE –
Statutory
● Take note of areas that do not reconcile during high level reconciliations
Consolidation
Technical Reconciliation System Integrator Sep ● Work with System Integrator to define useful Reconciliation templates - which highlight
known reconciling items Leader

0.5 FTE -
Functional Reconciliation ● Perform reconciliations for data mapped and loaded into BPC.
Additional
Statutory Consolidation ● Areas that do not reconcile - highlight the differences and get sign off on differences
/ Sign Off Sep - Nov Resource
Leader ● Perform adjustments (via agreed method) to finalise numbers in BPC - this could include
PHASE 1 MIGRATION posting journals

Functional Reconciliation
/ Sign Off Statutory Consolidation ● Perform the above activities but on an ongoing basis for all months up until BPC Goes
Nov - Go Live
PHASE 2 MIGRATION - Leader LIve
INTERIM

Estimate ● Statutory Consolidation Leader will lead Statutory Migration - 0.2 FTE
Resource ● Additional resource required - 0.5 FTE (Aug - Dec)
Slide 41
3.1 Roles and responsibilities for data migration
Estimated effort / timing for resources - Management Consolidation
ACTIVITY OWNER TIMEFRAME DATA TEAM ACTIVITY EXTRA RESOURCE
REQUIRED

● Project manage activities

Lead Master Data Leader Ongoing ● Responsible for timelines and overall sign off of data

Master Data Leader / System ● TW - provide template definition to Perf Mgrs and definitions of extracts
● Perf Mgrs - provide BW extracts in supportive format to facilitate easy mapping load
Provide Data Files Integrator Mar to BW
Local - Regional Perf Mgrs ● Interim phase - this activity will happen every month up until region is on S/4

Core - Master Data Leader /
Mapping / Conversion System Integrator
Local - Regional Perf Mgrs
BW Load - System Integrator
Load
BPC Load - System Integrator
Technical BW Load - System Integrator
Reconciliation BPC Load - System Integrator
● System Integrator - Create mapping in required format
● Perf Mgrs - update Mapping file for SCoA, Product, Customer etc for localisation
Apr ● Perf Mgrs - Work with System Integrator to align Company A old codes to new
Company B dimension code
● System Integrator - Load files into BW
Apr / May ● Perf Mgrs - Work with System Integrator team to support where values do not load,
or mappings do not match
Core - 1 FTE
● System Integrator - Perform initial high level technical reconciliation check Perf Mgrs - (0.2 FTE)
● System Integrator - develop reconciliation templates to support efficient checks Regl Support - 1 FTE
Apr / May
● Perf Mgrs - support System Integrator to define useful Reconciliation templates -
which highlight known reconciling items

Functional
Core - Master Data Leader / ● Perf Mgrs - Perform reconciliations for data mapped and loaded into BW
Reconciliation
Mgmt Conso Leader Apr / May ● Areas that do not reconcile - highlight the differences and get sign off on differences
/ Sign Off ● Perform adjustments (via agreed method) to finalise numbers in BW
Local - Regional Perf Mgrs
PHASE 1 MIGRATION

Functional
Core - 0.5 FTE
Reconciliation Core - Master Data Leader /
● Perform the above activities but on an ongoing basis for all months up until S/4 Perf Mgrs - 0.1 FTE
/ Sign Off Mgmt Conso Leader June ongoing Goes LIve for individual regions Regl Support - 0.5
PHASE 2 MIGRATION - Local - Regional Perf Mgrs
FTE
INTERIM

● Master Data Leader will lead Management P&L Migration - 0.5 FTE
Estimate ● Performance Managers - Regional Support - 0.2 FTE
Resource ● Additional Core resource required - 1 FTE (Apr - June) and 0.5 post June ongoing
Slide 42 ● Additional Regional resource to support with extracts and reconciling items - 1 FTE (Apr/ May)
3.1 Roles and responsibilities for data migration
Estimated effort / timing for resources - Planning
ACTIVITY OWNER TIMEFRAME DATA TEAM ACTIVITY EXTRA RESOURCE
REQUIRED

Management Consolidation ● Project manage activities

Lead
Leader ● Responsible for timelines and overall sign off of data

Management Consolidation
Provide Data Files Mar ● Provide data files in supportive format to facilitate easy mapping and load into BPC
Leader

● Create mapping in required format

Management Consolidation
Mapping / Conversion Apr ● Mapping file for SCoA, Profit Centre, Product, Line of Business
Leader / Master Data Leader ● Work with System Integrator to align mappings to BPC dimension code

Load System Integrator Apr

● Work with System Integrator team to check Loaded files. 0.2 FTE – Mgmt
● Support where values do not load, or mappings do not match. Conso Leader

● Take note of areas that do not reconcile during high level reconciliations 0.5 FTE - Additional
Technical
System Integrator May ● Work with System Integrator to define useful Reconciliation templates - which Resource
Reconciliation highlight known reconciling items

Functional ● Perform reconciliations for data mapped and loaded into BPC.
Reconciliation Management Consolidation ● Areas that do not reconcile - highlight the differences and get sign off on differences
May
/ Sign Off Leader and Regional PM ● Perform adjustments (via agreed method) to finalise numbers in BPC - this could
PHASE 1 MIGRATION include posting journals

● Management Consolidation Leader will lead Planning Migration - 0.2 FTE

Estimate
● Additional resource required - 0.5 FTE (Apr / May)
Resource
● System Integrator to support with extracts and reconciling items

Slide 43
3.1 Roles and responsibilities for data migration
Responsibility by dataset
# Dataset Provide data Create Load data and Reconcile Load data Reconcile data Reconcile data Overall owner
file mapping Tech. check data load into BPC load (BPC – TEST) load (BPC – PROD)
table into BW (BW)

January to December FY19, System Stat Conso Leader /

C1 Company Company N/A N/A System Integrator Group Controller
monthly data Integrator System Integrator

Jul – Dec 2018 Full Year End System Stat Conso Leader /
C2 Company Company N/A N/A System Integrator Group Controller
and Monthly data (P&L and BS) Integrator System Integrator

Dec 2017 Closing Balance and

System Stat Conso Leader /
C3 Jan – Jun 2018 Full Year and Company Company N/A N/A System Integrator Group Controller
Integrator System Integrator
Monthly data (P&L and BS)

Regional
18FY and Jan to May 19 Performance
System System
M1 monthly data, with management Company System Integrator Managers / System Integrator System Integrator Master Data Leader
Integrator Integrator
details System
Integrator
Regional
Performance
15FY - 17FY monthly data, with System System
M2 Company System Integrator Managers / System Integrator System Integrator Master Data Leader
management details Integrator Integrator
System
Integrator

Jul-Dec 2018 and Jan- May Stat Conso System

M3 Company Company System Integrator System Integrator System Integrator Master Data Leader
2019 monthly data Leader Integrator

System Regional Perf. Mgr. /

P1 Annual Budget 2019 Company Company N/A N/A System Integrator Master Data Leader
Integrator System Integrator

System Regional Perf. Mgr. /

P2 Quarterly Forecast 2019-2020 Company Company N/A N/A System Integrator Master Data Leader
Integrator System Integrator

System Regional Perf. Mgr. /

P3 Monthly S&OP 2019 Company Company N/A N/A System Integrator Master Data Leader
Integrator System Integrator

Slide 44
4. Interim period
4.1 Interim period
Introduction

Transition period has to be managed in order to “phase” BPC go-live and S/4 go-live throughout the countries.

The session explain how interim period will be managed for the following processes:
● Statutory Consolidation
● Management Consolidation
● PB&F

The following slides show both BPC and S/4 deployment plan, going in deep for each process in terms of datasets to provide and timing /
frequencies, considering the specificity of each country in terms of S/4 go-live.

Slide 46
4.1 Interim period
Recap of Future Performance Reporting Landscape

Performance Management
Reporting - Statutory Legal Entity
SAP BPC
Statutory Consolidation (STAT) Adjustments Account
Statutory Reports out of SAP Layer Optimized Management Unit
BPC and ‘Analysis for Office’ Sales Reductions Intercompany
volumes from TPM

Volumes from IBP

Performance Management
Reporting - Comparatives Management All of the above +
SAP BPC TPM for GTN in Tier 1 mkts Line of Business
Consolidation & Plan Data (MGMT
Slice and Dice Analysis Calculations Layer + Cost Centre
+PLAN)
functionality for different views PB&F Cash Up IBP Product (to SKU level)
Optimized
of data – Pre-built as well as Customer (Key accounts)
user-defined reports Actuals

Performance Management Unstructured All of the above +

Reporting – Canned feed - TBD Materials Master
Reports
Business / Data Supplier
MS Power Customer (detailed)
Custom- built reports from Warehouse Layer SAP BW
either SAP BW or Power BI, BI Product to SKU level
with views for Country as well MS Azure Blob Storage
Tax Local Reporting+
as Group Unstructured data
Actuals

Operational Performance
Reporting (Embedded Fiori
Analytics) Granular data levels for
Actuals Actuals
Standard out of the box ERP Layer
transactional reports from
Fiori/S4

Slide 47
4.1 Interim period
Statutory Consolidation overview

Main assumptions

• BPC Stat Consolidation go-live will be on January 2020

• S/4 deployment for Europe and RoW (Indonesia, Turkey, Africa, Asia and Middle East) will be respectively February 2020 and on March
2020
• Statutory Consolidation will come from IAS for all countries until BPC go-live

We need to manage interim period for Statutory Consolidation in two different way:

1. “First” interim period (until end 2019): Stat Consolidation perform in IAS. A conversion tool (ETL) needed to feed data in IAS for
countries are still in S/4
2. “Second” interim period (from Jan 2019): Stat Consolidation perform in BPC. A conversion toll (ETL) needed to feed data from IAS
to BPC for countries are still in SAP ECC

Slide 48
4.1 Interim period
Statutory Consolidation – Dataflow
«First» Interim Period: Stat Consolidation
perform in IAS. ETL transform and load data
into BPC for S/4 countries
«Second» Interim Period: Stat
All countries in S/4: Stat Consolidation
Consolidation perform in BPC. ETL transform
perform in BPC. All data comes from S/4
and load data into S/4 for non S/4 countries

Adjustments Adjustments
SAP BPC SAP BPC
(STAT) (STAT)
Optimized Optimized

IAS
Plan Data SAP BPC Plan Data SAP BPC
(MGMT) (MGMT)
Optimized Optimized

Actuals

Actuals Actuals

SAP ECC SAP BW

SAP BW

IAS *
Actuals Actuals

Actuals Actuals Actuals

Slide 49 * Dataflow for non S/4 countries

4.1 Interim period
Statutory Consolidation – Timing
2019 2020
Region Dataset May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Canada
Actual stat data Full
Year and Month to
US, LATAM Date:
• Legal Entity
• Account
Mexico • Trading Partner
• Transaction Type
Europe • Balancesheet
Movements
• Period
Indonesia, Turkey, • Closing Balance
Africa, Asia and
Middle East

Legend: Consolidation perform in BPC. For

Europe and RoW data comes from IAS
Data comes from SAP ECC for the countries who are not in S/4 (old CoA). Statutory Consolidation perform in IAS and feed into BPC. Starting from Apr
2020 all countries will be in S/4
Data comes from S/4 and Statutory Consolidation perform in IAS (new SCoA mapped into old CoA)

Data comes from S/4 and Statutory Consolidation perform in BPC (new SCoA)

Slide 50
4.1 Interim period
Management Consolidation overview
Main assumptions

• BPC Management Consolidation go-live will be at the end of June 2019

• Canada S/4 go-live will be at the end of May 2019
• All countries go-live will after BPC go-live

• Interim period will be managed for countries who are not still in S/4 (interim not needed for Canada):
○ US, LATAM → from Jun to Sep 2019
○ Mexico → from Jun to Dec 2019
○ Europe → from Jun 2019 to Jan 2020
○ Indonesia, Turkey, Africa, Asia and Middle East → from jun 2019 to Mar 2020
• During interim period data comes from Local BWs and feed into BPC (S/4 embedded BW)

Slide 51
4.1 Interim period
Management Consolidation – Dataflow
Interim Period: Mgmt Consolidation perform in BPC. ETL transform and All countries in S/4: Mgmt Consolidation perform in BPC and all
load data from Local BWs into BPC for non S/4 countries data comes from S/4

Adjustments Adjustments
SAP BPC SAP BPC
(STAT) (STAT)
Optimized Optimized

Sales Reductions Sales Reductions

volumes from TPM volumes from TPM
Plan Data SAP BPC Plan Data SAP BPC
(MGMT) TPM for GTN in Tier 1 mkts (MGMT) TPM for GTN in Tier 1 mkts
Optimized Optimized
IBP IBP

Volumes from IBP Volumes from IBP

Actuals Actuals

Local BWs

SAP BW SAP BW

Actuals

Actuals

Actuals Actuals

Slide 52
4.1 Interim period
Management Consolidation – Timing
2019 2020
Region Dataset May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Canada
Actual stat data Full
Year and Month to
US, LATAM Date:
• Legal Entity
• Account
Mexico • Trading Partner
• Transaction Type
Europe • Balancesheet
Movements
• Period
Indonesia, Turkey, • Closing Balance
Africa, Asia and
Middle East

Legend:

Data comes from Local BW and Management Consolidation perform in iFinance (current method)

Data comes from Local BW and feed to S/4 countries who are not in S/4 (old mgmt CoA mapped into the new SCoA, product / customer mapped into the new hierarchy). Management
Consolidation perform in BPC

Data comes from S/4 and Management Consolidation perform in BPC (new dimensions)

Slide 53
4.1 Interim period
Cash-up overview

• No interim period is needed for “submission” because application in BPC will be ready for all countries at the beginning
of June
• “Cash-up” offline is needed in order to manage interim period for Canada and North America due to dismissing of
current planning system (Oracle PBCS)
• Current planning system for Europe and RoW as long as S/4 go-live
• Need to train finance team of PBCS and no PBCS countries in order to perform submission on BPC

Slide 54
4.1 Interim period
Cash-up – Dataflow
- Interim Period - - Country live on S/4 -

Adjustments
SAP BPC
Local (STAT)
Optimized
planning
model
Input Data
SAP BPC Sales Reductions
(MGMT) volumes from TPM
«Cash-up» Optimized Plan Data SAP BPC
(MGMT) TPM for GTN in Tier 1 mkts
model Optimized
IBP

TPM IBP Volumes from IBP

Actuals

«Cash-up» Preparation «Cash-up» Submission

SAP BW
• Temporary “cash-up” model needed for Canada • No interim period needed for data
and US during interim period. TPM and IBP data submission
will be manually integrated • BPC feature will be ready starting
• Current local planning excel model for all other from the beginning of June
counties • Training to users would be useful Actuals
to address data submission in
BPC
Actuals

Slide 55
4.1 Interim period
Cash-up – Timing
2019 2020

Region Dataset Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Canada
Temporary excel
“Cash-up” model
US

LATAM

Mexico

Europe Local excel

planning model

Indonesia, Turkey,
Africa, Asia and
Middle East

Legend:

Submission will be ready for each countries starting from the beginning of June

Temporary “cash-up” model will be adopted by Canada and US from June to August according BPC go-live milestones

Current planning excel model will be adopted for all other countries until BPC go-live

“Cash-up” will be performd in BPC

Slide 56
5. Deep Dive on Management
Consolidation - Assessing the options
5.1 Deep Dive on Management Consolidation
Assessing the options

Multiple options has been assessed in order to get an agreed “Scenario” to migrate data for Management Consolidation.
Decisional approach has been based on trade-off between level of detail on historical data and effort to rebuild them.
Follow the main scenarios has been assessed:
● Scenario 1: Migrate P&L for all Regions from Local BWs. Full detail for Canada. Brand and Local Customer for RofW
● Scenario 2: Migrate P&L for all Regions from Local BWs. Full detail for Canada. Total Product and Total Customer for RofW
● Scenario 3: Migrate full P&L for Canada from Local BW, at SKU and Customer. Migrate RofW from iFinance
● Scenario 4: Migrate full P&L for Canada from Local BW, at SKU and Customer. Migrate RofW from iFinance

In the session all scenarios will be presented, explaining pro / cons for each of them in terms of data availability versus effort during
enrichment period.
Deep dive on chosen scenario in terms of role and responsibilities and main activities throughout the months.

Slide 58

5.1 Data migration Scenarios for Management Consolidation
Scenario 1: Migrate P&L for all Regions from
Local BWs. Full detail for Canada. Brand and
Local Customer for RofW
Canada
• Approach: Bottom Up
• Source: Local BW
• Account: Full mapping to new SCoA
• Product: Full SKU mapping
• Customer: Local Customer
• LoB: combination of Product and Customer
• Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
RofW
• Approach: Bottom Up
• Source: Local BWs
• Account: Full mapping to new SCoA
• Product: “Brand” level mapping
• Customer: Global Customer level
• LoB: old dimension
• Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
• Company Resource effort: High
• BW Resource effort: High
• Mapping effort / complexity : Very High
• Time required: > 5 months
Slide 59 Level of Risk: Very High
Scenario 2: Migrate P&L for all Regions from
Local BWs. Full detail for Canada. Total
Product and Total Customer for RofW
Canada
• Approach: Bottom Up
• Source: Local BW
• Account: Full mapping to new SCoA
• Product: Full SKU mapping
• Customer: Local Customer
• LoB: combination of Product and Customer
• Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
RofW
• Approach: Bottom Up
• Source: Local BWs
• Account: Full mapping to new SCoA
• Product: “Total Product” level mapping
• Customer: “Total Customer” level mapping
• LoB: old dimension
• Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
• Company Resource effort: High
• BW Resource effort: High
• Mapping effort / complexity: High
• Time required: > 4 months
High Medium Medium / Low
Principle: Phased enrichment of data
Scenario 3: Migrate full P&L for Canada from
Local BW, at SKU and Customer. Migrate
RofW from iFinance
Canada
• Approach: Bottom Up
• Source: Local BWs
• Account: Full mapping to new SCoA
• Product: Full SKU mapping
• Customer: Local Customer
• LoB: combination of Product and Customer
• Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
RofW
• Approach: Top Down
• Source: iFinance *
• Account: High level mapping to new SCoA
• Product: “Brand” level mapping – high level
• Customer: “Total Customer” level mapping
• LoB: old dimension
• Period: Priority: FY18, FY19 (until go-live)
• Company Resource effort: Medium
• BW Resource effort: Medium
• Mapping effort / complexity: Medium
• Time required: > 3 months
* iFinance can't map accurately and restatements
would be difficult
Scenario 4: Migrate full P&L for Canada from
Local BW, at SKU and Customer. Migrate
RofW from iFinance
Canada
• Approach: Bottom Up
• Source: Local BWs
• Account: Full mapping to new SCoA
• Product: Full SKU mapping
• Customer: Local Customer
• LoB: combination of Product and Customer
• Period: Priority: FY18, FY19 (until go-live)
RofW
• Approach: Top Down
• Source: iFinance *
• Account: High level mapping to new SCoA
• Product: “Brand” level mapping – high level
• Customer: “Total Customer” level mapping
• LoB: old dimension
• Period: Priority: FY18, FY19 (until go-live)
• Company Resource effort: Medium
• BW Resource effort: Medium
• Mapping effort / complexity: Medium
• Time required: > 3 months
5.1 Data migration Scenarios for Management Consolidation
Pro / Cons
Scenario 1: Migrate P&L for all Regions from
Local BWs. Full detail for Canada. Brand and
Local Customer for RofW
Pro
• Ability to perform in BPC comparison analysis
at least at Brand level and Global Customer
level with previous periods (5 years history) for
all countries
• Ability to perform comparison analysis with
previous period (5 years history) at account
level for all countries
• Low effort during the enrichment phase in
order to get full details for RofW in the end
state
Cons
• New Line of Business dimension not available
for RofW
• Very high initial effort in terms of performing
detailed mapping and 5 years data
reconciliation
Slide 60
Scenario 2: Migrate P&L for all Regions from
Local BWs. Full detail for Canada. Total
Product and Total Customer for RofW
Pro
• Ability to perform comparison analysis in BPC
at Total Product and Total Customer for the
RofW, throughout all historical data (5 years
history)
• Ability to perform comparison analysis with
previous period (5 years history) at account
level for all countries
• Low effort during the enrichment phase in
order to get full details for RofW in the end
state
Cons
• New Line of Business dimension not available
for RofW
• Need to get SKU / Local Customer details
from Local BWs to perform detail analysis for
RofW
Scenario 3: Migrate full P&L for Canada from
Local BW, at SKU and Customer. Migrate
RofW from iFinance
Pro
• Ability to perform in BPC full detail comparison
analysis only for Canada
• Ability to perform comparison analysis in
Ability to perform comparison analysis in BPC
at Brand level – time range 18FY and 19 (until
go-live) – for RofW
• Medium initial effort due to high level mapping
and shorter time range for RofW
Cons
• New Line of Business dimension not available
for RofW
• Need to get SKU / Local Customer / Account
details from Local BWs to perform analysis at
an high level of detail
• More effort during the enrichment phase in
order to get full details for RofW in the end
state
Scenario 4: Migrate full P&L for Canada from
Local BW, at SKU and Customer. Migrate
RofW from iFinance
Pro
• Ability to perform in BPC full detail comparison
analysis only for Canada – time range 18FY –
19 (until go-live)
• Ability to perform comparison analysis in BPC
at Brand level – time range 18FY and 19 (until
go-live) – for RofW
• Medium / Low initial effort due to high level
mapping and shorter time range for both
Canada and RofW
Cons
• New Line of Business dimension not available
for RofW
• Need to get full detail in Local BW for Canada
for
• Need to get SKU / Local Customer / Account
details from Local BWs to perform analysis at
an high level of detail
• More effort during enrichment phase in order
re build details
5.1 Data migration Scenarios for Managememt Consolidation - Scenario 2
Scenario 2: Migrate P&L for all Regions from
Local BWs. Full detail for Canada. Total Chosen Scenario 2: Migrate P&L for all Regions from Local BWs. Full detail for Canada.
Product and Total Customer for RofW
Total Product and Total Customer for RofW
Canada
• Approach: Bottom Up
• Source: Local BW This is the scenario chosen by Company B Business for Data Migration of Management P&L
• Account: Full mapping to new SCoA
Key assumptions
• Product: Full SKU mapping
• Customer: Local Customer
1) Performance Managers in regions will support with the following activities
• LoB: combination of Product and Customer a) BW data extracts,
• Period: Priority: FY18, FY19 (until go-live)
b) Perform mapping activities for Local CoA translation, Product / Customer (when relevant)
FY17, FY16, FY15
RofW
c) Validate and reconcile the data where required
• Approach: Bottom Up d) Provide sign off on the migrated numbers - post a review with Regional CFO.
• Source: Local BWs
e) Provide significant resource support during initial historical migration and provide continued
• Account: Full mapping to new SCoA
• Product: “Total Product” level mapping
support during the “interim” stages of migration.
• Customer: “Total Customer” level mapping 2) System Integrator will support by leading BW technical set up and reconciliations
• LoB: old dimension
a) Transfer BW extracted data to Data Staging Area
• Period: Priority: FY18, FY19 (until go-live)
FY17, FY16, FY15
b) Transform and Load data into BW (via robust ETL using Data Services)
c) Perform initial technical reconciliations and provide reconciliation templates
• Company Resource effort: High
• BW Resource effort: High 3) System Integrator will support by leading migration and reconcilion the data from BW into BPC
• Mapping effort / complexity: High
• Time required: > 4 months

Slide
5.2 Data migration and interim period
Activity list and time span
Data Migration Interim Period

Perform by Activity List Activity List Country Time Span

Company A
(centrally) / • Dimensions mapping • Extract data file from Local BW
Canada • Never – no interim period for Canada
Regional
Company B

• Extract data file from Local BW • Data validation

Performance
Manager • Data validation • Data reconciliation • Monthly from June to September (4 months)
US, LATAM
Regional • Data reconciliation • Data transfer to Staging
Performance • Data transfer to Staging Environment Mexico • Monthly from June to December (7 months)
Manager
Environment
Europe • Monthly from June to January (8 months)
• Load and transform data into • Load and transform data into
Integrator

Staging Environment (SAP DS) Staging Environment (SAP DS)

System

System Integrator Indonesia, Turkey,

Team • Load data into BW
• Perform technical reconciliation
• Load data into S/4 BW
Integrator
• Load data into BW Africa, Asia and • Monthly from June to March (10 months)
Middle East
• Perform technical reconciliation
• Load data into S/4 BW

• Perform technical reconciliation • Perform technical reconciliation

System

System Integrator
Team in BPC in BPC

One-off activity to be
done within the end of
June with the level of
detail define in Scenario 2
Slide 62
5.3 Enrichment Phase
Main activity
Scenario 2: Migrate P&L for all Regions from Local BWs. Full detail for Canada. Total Product and Total Customer for RofW

Country Activity List

US, APAC • Re-build SKU level stating Local BWs master data
• Re-build Local Customer level starting from Local BWs master
Europe (main)
data

Europe (other) • Re-build Line of Business as new dimension (combination of

Product and Customer)
Mexico, LATAM • Reconcile 5 years data (15FY, 16FY, 17FY, 18FY, 19 until go-live)

Africa – full detail

Slide
5.3 Enrichment phase
Hypothesis of plan
Scenario 2: Migrate P&L for all Regions from Local BWs. Full detail for Canada. Total Product and Total Customer for RofW

Follow an hypothesis of how enrichment phase will work taking North America as example

2019

Phase Jun Jul Aug Sep Oct Nov Dec

Data migration done for all

Regions from Local BWs. Full
Data Migration detail for Canada. Total Product
and Total Customer for RofW

Monthly activity need to be done

(activity detail in slide 4) in order to
Interim Period feed data into BPC as long as S/4
go-live

5 years historical data

Enrichment Phase fully detail available in
BPC for North America

In the end state BPC

End State Phase
data comes from S/4

Elapsed time to perform full Product and

Customer mapping, re-build LoB as new
dimension and reconcile 5 years data at full
detail level (detail in slide 5)
Slide 64
 Appendix

7
 Appendix - BPC go-live milestones
2019 2020
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Process
Stat consolidation Stat consolidation
Stat consolidation is
starts happening in starts happening in
ready in BPC
Stat Consolidation BPC in parallel to IAS BPC (no longer in IAS)
BPC

Mgmt consolidation happens in

Mgmt Consolidation BPC for all countries
PB&F “cash-up” PB&F “cash-up”
Core functionality process starts in BPC process starts in BPC
PB&F required for Additional features to enable “cash- for additional countries for additional countries
“submission” of up” and other PB&F automation are live on S/4. live on S/4.
PB&F. Existing tool ready. “Cash-up” process starts in
continue to be used BPC for countries live on S/4.
as needed
Region Ve
rs
io
n
Canada M
ar
20
th

US, LATAM

Mexico *
S/4

Europe

Indonesia, Turkey,
Africa, Asia and
Middle East

BPC deadline S/4 live deadline Interim Period: Stat Consolidation * Mexico (non factory) go-live will be at
Mgmt Consolidation the end of Sep-19
Slide 66
Forecast