SAP S/4HANA Migration Cockpit

July, 2023

For SAP S/4HANA 2022, see:

SAP S/4HANA Migration Cockpit

Public 1
 Introduction – Your Way Recommendations
to SAP S/4HANA - Project Setup

Overview - Functions Further Information

and Process and Resources

System Setup Additional SAP Fiori Apps

in Data Migration

What´s New in 2308 Key Takeaways

Public 2
 Introduction
– Your Way to SAP S/4HANA

Public 3
Transition to SAP S/4HANA
Transition paths recap
Approach Business Driver Transition Option Target

SAP S/4HANA Cloud,

System private edition

Start rapid conversion SAP S/4HANA

REUSE modernization
with in-place conversion

versus
Hybrid SAP S/4HANA Cloud,
REENGINEERING SelectiveTransition
data private edition
with data migration
Selective business transition SAP S/4HANA
Customer tailored process optimization

SAP S/4HANA Cloud,

public edition
New
SAP S/4HANA Cloud,
Business model implementation private edition
Highly standardized, with best innovation
practices and based on a clean core
SAP S/4HANA

Public 4
Transition to SAP S/4HANA
Transition paths recap
Approach Business Driver Transition Option Target

SAP S/4HANA Cloud,

System private edition

Start rapid conversion SAP S/4HANA

REUSE modernization
with in-place conversion

versus
Hybrid SAP S/4HANA Cloud,
REENGINEERING SelectiveTransition
data private edition
with data migration
Selective business transition SAP S/4HANA
Customer tailored process optimization

SAP S/4HANA Cloud,

public edition
Highly standardized, New
SAP S/4HANA Cloud,
with best practices Business model implementation private edition
and based on a clean core innovation
SAP S/4HANA
Mapping Your Journey to SAP S/4HANA – A Practical Guide for Senior IT Leadership

Public 5
Back to Agenda
 Functions & Process
- SAP S/4HANA migration cockpit

Public 6
Facilitate Migration Projects with SAP S/4HANA Migration Cockpit
Transition scenario: new implementation

Out-of-the-box, included in SAP Guidance and simulation

S/4HANA and SAP S/4HANA Cloud for the migration process
license and shipment

Automated mapping
SAP between source & target
Preconfigured SAP S/4HANA-
specific migration content S/4HANA
Migration
Cockpit

Lower migration time and costs, no

Integrated into SAP developer skills required
Activate methodology

Migration object modeler for

custom requirements* * reduced scope for SAP S/4HANA Cloud, public edition
Public 7
Data Migration Process with SAP S/4HANA Migration Cockpit
Overview

SAP S/4HANA Cloud,

public edition

SAP S/4HANA Cloud,

private edition
Select Get data Map and transform data Simulate Migrate
migration objects SAP S/4HANA
Model and design to reflect custom
requirements*

SAP Business Suite Legacy

* Migration object modeler available for SAP S/4HANA and SAP S/4HANA Cloud, private edition.
For SAP S/4HANA Cloud, public edition limited functionality – check SAP Note 2999428.

Public 8
SAP S/4HANA Migration Cockpit
Step: select migration objects

Preconfigured SAP S/4HANA-specific migration content

What is a migration object?

▪ Represents a business entity in SAP S/4HANA, such as a customer, sales order, or invoice
▪ Encapsulates the logic to create a specific business entity through the corresponding APIs offered by SAP S/4HANA
▪ Is delivered by SAP based on SAP Best Practices configuration and is immediately ready to use
▪ Is categorized in master data and transactional data (no historical data)
▪ Contains rules how values from source to target are handled – called “mapping”

What is migration content?

▪ Migration content is the sum of all migration objects

Public 9
SAP S/4HANA Migration Cockpit
Preconfigured migration objects SAP S/4HANA Cloud

Download
migration object list

Documentation available Use filter options

Migration object list in SAP Help Portal (SAP S/4HANA Cloud)

Public 10
SAP S/4HANA Migration Cockpit
Step: map and transform

Automated mapping between source & target

What is a mapping?
▪ Data transformation or data mediation between a data source and a destination. Here, you map the source values,
which were extracted from the source system to the values and formats of the SAP S/4HANA system.
Example Source Country Key Target Country Key
Deutschland DE
USA US

▪ The migration cockpit automatically provides proposals for mapping values, if possible. 1:1 mappings and rules are
predefined by SAP.
▪ The mappings have to be maintained only once, they are used for all objects within a project.
Example You maintain the country key for migration object BANK, then all other objects in your project will use the same mapping.

Note: Check the object-related documentation for details on mapping. It is not necessary that the extracted data has to be provided how
SAP S/4HANA would expect.

Public 11
SAP S/4HANA Migration Cockpit
Step: simulate and migrate

Guidance and simulation for the migration process

▪ Data is posted to the SAP S/4HANA system via standard APIs. Therefore, data is created like it would be created
when it is entered manually in the SAP system.
▪ All logical and semantic checks are done in the API.
▪ During the simulation process, no data is written to the target SAP S/4HANA, but you can view all the messages that
would occur during an actual data transfer (for example information about a cost center that does not exist).
▪ Objects can be simulated/migrated one by one – keep dependencies in mind.
▪ There is no migration at database table level.
▪ It is possible to simulate/migrate only specific migration object instances (multiple single instances or a set of
instances).

Public 12
SAP S/4HANA Migration Cockpit

SAP Fiori App Process & content Data load

Migrate Your Data

API based

Staging

SAP S/4HANA Cloud,

public edition
Staging Tables

▪ Excel XML SAP S/4HANA Cloud, 250+

▪ CSV template files public edition 2308:
▪ ETL tools of choice

Migration objects
Public 13
SAP S/4HANA Migration Cockpit
How to fill the staging tables?

You can fill the staging tables by using:

or or

XML files* CSV files* your preferred ETL tools

* The size limit for each file is 100MB. You can upload multiple files at once by using a zip file. Note that the combined size of all the files you
want to add to the zip file must not exceed 160MB. The maximum permitted size of the zip file is 100MB. For more information see KBA
2719524

Public 14
SAP S/4HANA Migration Cockpit
XML or CSV?

XML CSV
▪ Using XML is a stable option for entering and ▪ You need to use a separate CSV file for each
editing values manually. data structure.
▪ All data is contained in one file. ▪ There is no built-in protection for data formats.

▪ It contains detailed information about the ▪ A readme file is also available for each migration
relevant data structures as well as instructions object with information about the data structures
about how to enter data in the file. as well as how to enter data in the files.

▪ Using CSV template files is an expert option.

We do not recommend using CSV files unless
you have a specific use case for doing so, for
example, if you are automating the extraction of
data from database tables.

Help Portal: Downloading template files

Public 15
SAP S/4HANA Migration Cockpit
What it is designed for (in/out of scope)

Designed for:
▪ Initial load of data
▪ Used in context of a new implementation of SAP S/4HANA

Not designed for

▪ Keep data in sync across systems*
▪ Realize a continuous exchange or flow of data*
▪ Data cleansing
▪ Migrating data directly from SAP S/4HANA or SAP S/4HANA Cloud to SAP S/4HANA is
currently not supported

* For this purpose SAP products like SAP Master Data Governance, Central Finance, Product Data Replication or SAP LT
Replication Server or SAP Data intelligence are available (list does not claim to be complete).

Public 16
 Video
Migrate Data Using Staging Tables

Video
Using CSV Files to Fill Staging Tables

Public 17
Back to Agenda
 System Setup
- SAP S/4HANA migration cockpit

Public 18
SAP S/4HANA Migration Cockpit – Migrate Data Using Staging Tables
System setup SAP S/4HANA Cloud - local SAP HANA database schema

SAP S/4HANA Select Local SAP S/4HANA

1 database schema*
migration cockpit for your migration project

Staging Staging ... Staging

table 1 table 2 table n

3 Fill Staging Tables with Staging table creation

Microsoft Excel XML or CSV for selected
templates files migration object
Application
interface
4 Read access 5 Insert/update through API

Status update of
6
record
Legacy system
SAP S/4HANA Cloud
Application data Application tables

Data source(s)

* Staging tables reside within the local ABAP schema of the SAP S/4HANA Cloud system.

Public 19
SAP S/4HANA Migration Cockpit – Migrate Data Using Staging Tables
System setup SAP S/4HANA Cloud – remote SAP HANA database schema

SAP BTP Staging table creation

SAP S/4HANA Cloud
for selected 1 Select Remote SAP HANA
migration object Database schema
for your migration project
Staging Staging ... Staging
ODBC SAP S/4HANA
table 1 table 2 table 3

Remote SAP HANA

migration cockpit
DB schema* 4 Read Access
Application
Status Update of 5 Insert / Update via API
6 Interface
Record
Cloud instance
via SAP HANA
ODBC

Application tables
3 Data extraction and fill of staging tables
via SAP or third-party tools, or
Microsoft Excel XML/CSV templates files

*Prerequisites:
Customer ▪ SAP Business Technology Platform (BTP), SAP HANA Cloud Instance
▪ Communication Arrangement (Service) SAP_COM_0678
Application data
Hint:
Follow the Setup instructions in SAP Best Practices Explorer for scope item 2Q2
https://me.sap.com/processnavigator/SolP/2Q2
Public 20
SAP S/4HANA Migration Cockpit – Migrate Data Using Staging Tables
Process – remote SAP HANA database schema

Recap

Check SAP Note 2733253 – chapter “Cloud related questions”.

1. Register for SAP Business Technology Platform (BTP), respectively SAP HANA Cloud, setup an SAP HANA Cloud
instance in the SAP BTP
2. Setup communication arrangement SAP_COM_0678

For details, go to Accelerators in SAP Signavio Process

Navigator - Data Migration to SAP S/4HANA from Staging (2Q2):
▪ Setup instructions: steps to setup the Communication
arrangement
▪ Test script incl. business roles, additional information on
manual configuration, steps within the migration cockpit
▪ Test script (SAP Cloud ALM): a template you can use to
manually upload the test script as test case in SAP Cloud
ALM. More information at SAP Note 3217691 * You have to log into SAP for Me – Process Navigator to see the section above

Public 21
Back to Agenda
 What´s New in 2308

Public 22
SAP S/4HANA Migration Cockpit – Migrate Data Using Staging Tables
What’s New in 2308

CSV templates

A readme file is available for each migration object with information

about the data structures as well as how to enter data in the files.

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

Early Adopter Care (EAC)

▪ New migration approach

"Migrate Data Directly from SAP System to SAP S/4HANA Cloud, public edition"

▪ Early Adopter Care Program in SAP S/4HANA Cloud 2308

▪ Registration page:
Influence Opportunity Homepage - Customer Influence (sap.com)

▪ More information (prerequisites and available objects):

3252723 - SAP S/4HANA Migration Cockpit - Direct Transfer for Public Cloud - SAP ONE Support
Launchpad

▪ We are looking for customers in realize phase for migrating an SAP ERP system or partners for own
tests

Public 24
Back to Agenda
 Recommendations
- Project Setup

Public 25
SAP S/4HANA Migration Cockpit – Set up Your Project
How many projects?

Use only one project Use several projects

It might seem as if one project for each application could
lead to a better progress overview for a dedicated area but:

+ ▪ Mapping values valid for all migration objects - ▪ You must keep mapping in sync across
projects which requires additional effort and
▪ Central overview and control of the migration make the process prone to unwanted errors

▪ If you use internal numbering for a migration

object, you can only upload this mapping after
it has been created

▪ Distributing migration objects across multiple

projects does not improve performance. See
KBA 3065607
Public 26
SAP S/4HANA Migration Cockpit – Enhancing Data Migration Performance
Further recommendations

Recommendations

▪ Do not start the migration of all objects in one migration project at the same time. There is a sequence for migrating objects, because
of the dependencies between objects.
▪ Parallelization is only meant for migration objects with high data migration volumes.
▪ Try not to have many people working in parallel on separate migration projects.
▪ Try to avoid users from triggering multiple activities for several projects in same data migration context.
▪ Consider that uploading multiple objects in parallel can flood the job queue.
▪ In our experience, it delivers better results to migrate one object with full number of jobs, complete the data migration and then start
the migration of the next object.
▪ Even if you assign a higher number of data transfer jobs to run in parallel, the effect in the performance depends on the overall load of
the system.
▪ Consider that there might be additional activities running in the background, that also fill the process queue.
▪ If you experience performance problems, consider executing the data migration in time periods when the system has a low workload.

KBA 2878945 and KBA 3065607 provide information on parallelization of XML file loads and improving the performance of the data
transfer

Public 27
SAP S/4HANA Migration Cockpit
Plan your project to go live

▪ Check the upgrade & maintenance schedule before migration to a productive system.
▪ To reduce errors during data migration in SAP S/4HANA Cloud using the SAP S/4HANA Migration Cockpit,
the Migrate your Data - Migration Cockpit App is available in read-only mode during SAP S/4HANA Cloud
upgrade.

2-System Landscape 3-System Landscape

Please check the upgrade schedule linked in KBA 2996675

Note: It is not possible to run a data in migration blue-green deployment. See SAP Note 3024158

Public 28
Back to Agenda
 Further Information
and Resources

Public 29
SAP Help Portal: Data Migration Landing Page for SAP S/4HANA Cloud

Public 30
SAP S/4HANA Migration Cockpit
Migration object documentation – including how to validate

Use this SAP Fiori app

to validate your data
migration status

Public 31
SAP S/4HANA migration cockpit in SAP S/4HANA Cloud, 2308
Migration Objects 300

262
249
250 243

222
▪ 249 objects in 2302 212 216

200
▪ 262 objects in 2308 175

▪ 19 new 148 149

155
150 136 141
▪ 6 removed 130
113
106
99 100
100 88
81
75
65
58
52
50 43
32 33 33
24
17

0
1511
1603
1605
1608
1611
1702
1705
1708
1711
1802
1805
1808
1811
1902
1905
1908
1911
2002
2005
2008
2011
2102
2105
2108
2111
2202
2208
2302
2308
CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE CE

Public 32
SAP S/4HANA Migration Cockpit in SAP S/4HANA Cloud 2308
Check migration object changes in release comparison

SAP S/4HANA Cloud - Release Comparison of Migration Object Templates

Public 33
 Available migration objects http://help.sap.com/S4_CE_MO
Migration object changes release comparison
Support of custom fields Staging
Link List
Migration Template Samples Staging
Further Useful
Documentation Migration of Financial Accounting Master and Transactional Data
Data Migration Status app http://help.sap.com/S4_CE_DM_STATUS
FAQ SAP S/4HANA Cloud – migration cockpit

Public 34
Back to Agenda
 Additional SAP Fiori Apps in Data
Migration

Public 35
Overview – Configuration Data Migration
Additional migration features for SAP S/4HANA Cloud
Data migration status app
▪ Check the statuses for all records after
simulation and migration, get info about all
messages
▪ See running jobs at a glance and get
notifications
▪ And many others, for more details please
check Help Portal – Data Migration Status
Public
Define Settings for Legacy Data Transfer app
▪ Set Posting Date per Company Code in the
Migration Key Date field
▪ Set Legacy Data Transfer Status
▪ For details, check KBA 2754615 –
SAP S/4HANA Migration Cockpit:
Information about Fix Posting Date
36
Additional Migration Features for SAP S/4HANA Cloud
Data migration status app

Application Help for Data Migration Status

Public 37
Additional Migration Features for SAP S/4HANA Cloud
Data migration status app – features

Real-time progress monitoring

Notification upon migration job completion
and background job status

Many filter capabilities Audit management

Ready-to-use record statistics Instance sub-structure record counts

Source record linked with migration

Extended statistics
status and internal number

Ready-made status log and no need Configure migration objects for extended
to store and distribute the log statistics logging

Export to Excel Export extended statistics

Validation by structure fields relevant for

Quick and easy failed records evaluation
value conversion

Smart data validation by navigation

to respective SAP Fiori app

Public 38
Additional Migration Features for SAP S/4HANA Cloud
Define settings for legacy data – more information

Before you go live with SAP S/4HANA, you may want to initially transfer
open balances and open postings from a legacy system to your SAP
S/4HANA Cloud system. You can transfer such data by using the SAP
S/4HANA Migration Cockpit.

To enable the cockpit to properly transfer your legacy data, enter the dates
on which you want to complete all preparatory activities for each company
code before the actual data transfer.

The date must allow you to complete the following actions:

▪ Complete all postings available up to this date in full in the source
system
▪ Reconcile and close the journals in the source system for the period
▪ Extract source data and enter it into migration templates
▪ Clean and convert data as needed
▪ Validate the imported data against your legacy system

The date chosen is usually the end of a time period (month, quarter, year)
so that it fits into the normal reconciliation cycle.

Documentation via Configuration Help button

Public 39
Options for supporting additional requirements
Key user extensibility – Custom fields support
Key user extensibility
▪ Business expert or implementation consultant can use
the Custom Fields app to create additional fields
▪ Example: Add product-related bonus to product master
data, see video
Public
SAP S/4HANA migration cockpit
▪ Some migration objects support these custom fields
– check migration object list (details next slide)
▪ If supported, custom fields will automatically be
reflected in the template of the corresponding
migration object
41
 Key Take Aways
- SAP S/4HANA migration cockpit

Public 42
Key Takeaways
SAP S/4HANA migration cockpit – the next-generation data migration software

▪ Included in SAP S/4HANA and SAP S/4HANA Cloud license Migration approach
and shipment Data Transfer

▪ Made for migrating data from SAP and non-SAP sources into
SAP S/4HANA and SAP S/4HANA Cloud
▪ Guided procedure takes users through the migration process:
Easy and safe, no programming required
▪ Flexible for integration of custom business data including data
transformations
Migrate data using Staging Tables
Predefined SAP S/4HANA-specific migration content
facilitates and accelerates your data migration
▪ Preconfigured content and mapping
▪ Automated mapping between template and target
structure
▪ Migration programs generated automatically

Public 43
Back to Agenda
SAP S/4HANA Cloud – Cookbook
SAP S/4HANA migration cockpit

Find more details on how to use SAP S/4HANA

migration cockpit in our SAP S/4HANA Cookbook

Public 44
Thank you. sap_s4hana_migration_cockpit@sap.com

Data migration landing page http://help.sap.com/S4_CE_DM

Contact information:
Standard slide deck SAP S/4HANA: Migrate Your Data to SAP S/4HANA – SAP S/4HANA Migration Cockpit
Standard slide deck SAP S/4HANA Cloud: Migrate Your Data to SAP S/4HANA Cloud – SAP S/4HANA Migration Cockpit
Video: Migrate Data Using Staging Tables
Video: Using CSV Files to Fill Staging Tables
Video: Data Migration Status
Video: Data Migration Status - Extended Statistics
Community topic page S/4HANA Migration Cockpit Community
Click through tutorials SAP S/4HANA migration cockpit

Find a comprehensive FAQ list in the SAP S/4HANA migration cockpit Community: https://community.sap.com/topics/s4hana-migration-cockpit

Public
© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences. 45
Public 46
Options for supporting additional requirements
SAP S/4HANA migration object modeler

Available for SAP S/4HANA Cloud, public edition

SAP Fiori app to enhance migration objects used in SAP S/4HANA migration cockpit
Add a standard field, which is currently not supported by the migration object, but is available in the API
Available for migration objects: Customer, Supplier, Product

Application Help: Model Your Migration Objects – Migration Object Modeler

Documentation can be accessed within the app
General Information – list of released migration objects: SAP Note 2999428
Additional role SAP_BR_ADMINISTRATOR required
Step-by-Step guide with an example in KBA 3216716

If a migration object or field is not listed in the SAP Note above, follow the procedure for feature
requests (see KBA 2676589).

Public 47
SAP S/4HANA Migration Cockpit – Migrate Data Using Staging Tables
How to fill the staging tables

How can I populate the staging tables?

To extract data from the source systems you can use either SAP tools or third-party tools. The staging tables have
to be filled in a ready-to-load data format, i.e. the format expected by SAP S/4HANA.

▪ SAP Smart Data Integration to fill staging tables from Excel files
▪ SAP Agile Data Preparation (ADP)
▪ Third-party tools to fill staging tables

Note: For SAP S/4HANA Cloud you can only use the remote SAP HANA database schema to populate the staging tables
using third-party or SAP Tools. Additional costs may apply for using when using the remote SAP HANA database schema option
and ETL Tools to fill the staging tables.

Public 49
SAP S/4HANA Migration Cockpit – Migrate Data Using Staging Tables
How to fill the staging tables – blogs in SAP community

Good to know

To fill the staging tables, you can either use an ETL tool or fill the data directly on the SAP HANA database.

There are several blog posts listed below that explain the different methods to load data into the staging tables:

▪ Migrating data using staging tables and methods for populating the staging tables
▪ Using SAP HANA Smart Data Integration (SDI) to load data to the staging tables
▪ SAP S/4HANA migration cockpit – creating and using synonyms for renaming staging tables

Public 50
Back to Agenda
Comparison of local and remote database connection

Connection Location for the staging tables Tables filled via

Local SAP S/4HANA Database Staging tables will be created in same HANA ▪ XML template files
Schema DB schema as SAP S/4HANA Cloud, public ▪ CSV template files
edition.
Standard use case

Remote SAP HANA Database Staging tables will be created in the separate ▪ 3rd party tools (staging tables can
Schema* SAP HANA Cloud instance. be accessed via DB layer)
▪ XML template files
Specific customer use case ▪ CSV template files

* SAP recommends to minimize the network latency between SAP S/4HANA Cloud and the remote SAP HANA
database, as a general increase in network latency will negatively impact the performance of a migration.
E.g. an SAP HANA Cloud instance should be located in the same data center as the SAP S/4HANA Cloud system.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 51