Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 1: Introduction to Data Migration
Introduction to data migration
Learning objectives
Migrating Data to SAP S/4HANA Cloud, Public Edition
By the end of this week, you will understand
▪ What data migration to SAP S/4HANA Cloud, public edition
comprises
▪ The different steps in the migration process
▪ How to migrate data using staging tables with XML or CSV template
files
▪ Where to find further resources for data migration
The openSAP course “Migrating Data to SAP S/4HANA Using the Migration Cockpit” starting
27 September 2023 will take a detailed look at the SAP S/4HANA migration cockpit in SAP S/4HANA
and SAP S/4HANA Cloud, private edition.
This 3 week course deals with the functionality, including different migration approaches and modeling
environment.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Introduction to data migration
Agenda
Setting the scene:
Transition scenario – New implementation
Data migration requirements
SAP Activate methodology
Data Migration landing page
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Introduction to data migration
Transition paths recap
Approach
REUSE
with in-place conversion
Business Driver
Start rapid
modernization
Transition Option
System
conversion
Target
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
versus
REENGINEERING
with data migration
Customer tailored
Highly standardized, with
best practices and based on
a clean core
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Selective business
process optimization
Business model
innovation
Selective data
transition
New
implementation
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
SAP S/4HANA Cloud,
public edition
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
4
Introduction to data migration
Focus: new implementation
Approach
REUSE
with in-place conversion
Business Driver
Start rapid
modernization
Transition Option
System
conversion
Target
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
versus
REENGINEERING
with data migration
Customer tailored
Highly standardized,
with best practices and
based on a clean core
Selective business
process optimization
Business model
innovation
Selective data
transition
New
implementation
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
SAP S/4HANA Cloud,
public edition
SAP S/4HANA Cloud,
private edition
SAP S/4HANA
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
Introduction to data migration
Starting point
▪ You have decided to go for SAP S/4HANA Cloud, public edition.
▪ You have activated your business process content and local versions, defined the
organizational structure, and completed product-specific configuration for the SAP S/4HANA
Cloud systems using SAP Central Business Configuration (CBC).
Master data and transactional data is needed to run business processes.
Master Data
Transactional Data
Describing business objects
Describing business events
Examples:
Customer, Supplier, Product
Examples:
Bank account balance, G/L account balance
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
Introduction to data migration
Data migration requirements
What are the sources / sender systems of the data?
Number and type of source systems? Central master data management?
Which data is needed from your source to operate SAP S/4HANA the way you want?
Master data? Open items? Balances?
Migrate data “as is” or transform on the fly?
Data transformations needed? Data quality improvement necessary?
Who needs to be involved?
Decisions to be taken? Major stakeholder?
Bottom Line: Start as early as possible to ensure high quality data
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Introduction to data migration
Sources to support you in your migration process
SAP Activate Methodology
(Roadmap Viewer)
SAP Best Practices
via Process Navigator
Data Migration Landing Page
on SAP Help
▪ Access implementation guidance for your
digital transformation
▪ Access and download SAP Best
Practices content
▪ Access documentation – Application
Help
▪ View and download SAP Activate
methodology assets and accelerators
▪ Power your project with ready-to-run
business processes
▪ View additional slide decks and training
information
▪ https://go.support.sap.com/roadmapviewer/
▪ https://me.sap.com/processnavigator
▪ http://help.sap.com/S4_CE_DM
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Introduction to data migration
SAP Activate methodology
SAP Activate
▪ Develop
data
migration
approach
and
strategy
▪ Rough
overview of
required
migration
objects
sorted
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
▪ Enablement
▪ Finalize migration objects
migration
▪ Select data from legacy system
cockpit
▪ Data cleansing
▪ Specify
▪ Migrate relevant data in test system
migration
▪ Define cutover tasks and finalize
objects
data files for production system
▪ Prepare files,
mapping and
simulate data
in test system
▪ Migrate relevant
data in production
system
▪ Check migrated
objects
9
Introduction to data migration
SAP Best Practices in SAP Signavio Process Navigator
Solution Scenario: SAP Best Practices for SAP S/4HANA Cloud
Line of Business: Database and Data Management
Solution Process: Data Migration to SAP S/4HANA from Staging 2Q2
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Introduction to data migration
Data Migration landing page
SAP Help Portal:
Data Migration landing page
for SAP S/4HANA Cloud, public edition
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Introduction to data migration
Key takeaways
In this unit you have learned
▪ Why data migration in a new implementation scenario is important
▪ How the SAP Activate methodology supports you
▪ Where to find further information
DATA MIGRATION IS NECESSARY
It is one key task during the transition to SAP S/4HANA.
Unfortunately, it is often underestimated. It can’t be done just
by pressing a button.
Make sure to understand your data migration
requirements early and plan for them accordingly.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 2: The Tool of Choice: SAP S/4HANA Migration
Cockpit
The tool of choice: SAP S/4HANA migration cockpit
Agenda
Introduction to SAP S/4HANA migration cockpit
Overall migration process
Data migration objects
Mapping
Simulation/Migration
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
The tool of choice: SAP S/4HANA migration cockpit
Your way to SAP S/4HANA Cloud, public edition
Bring your business processes to the new platform
System
Conversion
SAP S/4HANA migration
SAPcockpit
ERP
system
• A complete technical in-place conversion of an existing SAP ERP
system to SAP S/4HANA
• Adopt new innovations at your speed
→ Delivery model: included in SAP S/4HANA shipment
▪ Part of SAP S/4HANA and SAP S/4HANA Cloud (included in these licenses)
▪ Supports customers with the “new implementation”
Partly scenario
re-use, partly re-implementation
migration of relevant business data from SAP ERP to SAP
▪ SAP’s tool for the migration of business data to• Covers
SAPthe
S/4HANA
Cloud, public edition
S/4HANA
Hybrid
Selective
Hybrid
Transition
Data
Transition
Transition
SAP ERP
system(s)
• Allows to combine redesign of business processes with retaining historical
data
• Realized by a combination of standard functions used for a new
implementation or system conversion together with complementing expert
functions which are not released to general availability
→ Delivery model: as a service / consulting project
New implementation
New
Implementation
SAP
or non-SAP system(s)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
▪ Reengineering and process simplification based on latest
innovations
▪ Highly standardized, fueled with best practices and based on
a clean core
▪ Implement innovative business processes with preconfigured
best practice content on an innovative platform
3
The tool of choice: SAP S/4HANA migration cockpit
Capabilities
Out-of-the-box, included in
SAP S/4HANA and SAP S/4HANA
Cloud license and shipment
Preconfigured SAP S/4HANAspecific migration content
Guidance and simulation
for the migration process
SAP S/4HANA
migration cockpit
Integrated into SAP
Activate methodology
Automated mapping
between source and target
Lower migration time and costs,
no developer skills required
Migration Object Modeler for
custom requirements*
* reduced scope for SAP S/4HANA Cloud, public edition
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
The tool of choice: SAP S/4HANA migration cockpit
What it is designed for (in/out of scope)
Designed for:
▪ Initial load of data (master data, open transactional data, no historical data)
▪ Use in the context of a new implementation of SAP S/4HANA, SAP S/4HANA Cloud,
private edition and SAP S/4HANA Cloud, public edition
▪ Ensuring full coverage with migration objects for SAP S/4HANA Cloud, public edition
because the SAP S/4HANA migration cockpit is the only option to load data
Not designed for
▪ Keeping data in sync across systems
▪ Realizing a continuous exchange or flow of data
▪ Cleansing data
▪ Migrating data directly from SAP S/4HANA or SAP S/4HANA Cloud to SAP S/4HANA
(currently not supported)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
The tool of choice: SAP S/4HANA migration cockpit
No migration of historical data
Do you remember the last time you moved house?
▪ An SAP S/4HANA Cloud, public edition implementation is by
definition a new implementation.
▪ No migration objects for historical data in migration cockpit*:
▪ Only the data necessary for a smooth business start is migrated.
▪ A comprehensive customer-specific evaluation makes sense.
Solutions like business warehouse or side-by-side extensibility
can be considered.
Examples:
▪ The migration of closed documents leads to postings which are already included in the balances; there are no open items
for those documents any more.
▪ For partially open items, only the remaining quantities or values should be migrated.
* Exception: FI – Historical balance migration object see SAP Note 2943035
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
The tool of choice: SAP S/4HANA migration cockpit
Process overview
SAP S/4HANA Cloud,
public edition
SAP S/4HANA Cloud,
private edition
Select
migration objects
Get data
SAP Business
Suite
Map and transform data
Model and design to reflect custom
requirements*
Simulate
Migrate
SAP S/4HANA
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.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
The tool of choice: 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 the specific business entities through the corresponding APIs offered by SAP S/4HANA
▪ Delivered by SAP based on SAP Best Practices configuration and ready for immediate use
▪ Categorized in master data and transactional data (no historical data)
▪ Contains rules for handling values from source to target – called “mapping”
What is migration content?
▪ Migration content is the sum of all migration objects
What about updates on migration objects?
▪ Updates are shipped automatically by SAP (e.g. a standard field was added)
▪ You are prompted to perform an update in your migration project
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
The tool of choice: SAP S/4HANA migration cockpit
Step: select migration objects – Details and documentation
Download
migration object list
Documentation available
Use filter options
Migration object list in SAP Help Portal (SAP S/4HANA Cloud) – http://help.sap.com/S4_CE_MO
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
The tool of choice: SAP S/4HANA migration cockpit
Step: map and transform
Automated mapping between source and 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.
Check the object-related documentation for details on mapping.
It is not necessary to provide the extracted data the way SAP S/4HANA would expect.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
The tool of choice: 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 using standard APIs. Therefore, data is created like it would
be created when 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 system, 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 (single instances or a set of
instances).
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
The tool of choice: SAP S/4HANA migration cockpit
Key takeaways
In this unit you have learned
▪ About the migration process in the SAP S/4HANA
migration cockpit
▪ What the migration cockpit is used for
▪ Where to find information on migration objects
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 3: Getting Started with the Migration Cockpit
Getting started with the migration cockpit
Agenda
System setup
Demo
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Getting started with the migration cockpit
SAP Fiori app “Migrate Your Data”
SAP Fiori app
Migrate Your Data *
Process & content
Data load
API-based
Staging
SAP S/4HANA Cloud,
public edition
SAP S/4HANA Cloud,
public edition 2302,
migration objects
Staging tables
240+
▪ Excel XML
▪ CSV template files
▪ ETL tools of choice
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
*Required roles:
▪ SAP_BR_CONFIG_EXPERT_DATA_MIG
▪ Corresponding business catalog for each migration object
3
Getting started with the migration cockpit
System setup – Local SAP HANA database connection
SAP S/4HANA Cloud, public edition
1 Select local SAP S/4HANA
database schema*
for your migration project
SAP S/4HANA
migration cockpit
Staging
table 1
3
Fill staging tables with
Microsoft Excel XML or
CSV template files
Legacy system
Application data
Staging table
creation for selected
migration object
4
Read access
6
Status update of
record
Staging
table 2
...
Staging
table n
Application
interface
5 Insert through
API
Application tables
Data
source(s)
* Staging tables reside within the local ABAP schema of the SAP S/4HANA Cloud system.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Getting started with the migration cockpit
Migrate banks
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
Getting started with the migration cockpit
Instance-based simulation, migration, deletion via mass processing
Mass Processing helps you to do
trigger actions on selected instances.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
Getting started with the migration cockpit
Instance-based simulation, migration, deletion via mass processing
1
2
Select from possible actions:
▪ Simulate
Use filter options to select
relevant instances
▪ Migrate
▪ Delete instances
3
Instance list based on
your selection criteria
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Get a summary and
proceed with Start
7
Getting started with the migration cockpit
Available videos
Video
Migrate Data Using Staging Tables
Video
Using CSV Files to Fill Staging Tables
Link to Click-Through-Tutorial
SAP S/4HANA migration cockpit
Learning Hub Subscription necessary (SAP Learning Hub Solution Editions)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Getting started with the migration cockpit
Functions to keep in mind
▪ Follow guided procedure
▪ Run the Prepare step whenever data is added to the
staging tables
▪ Fill staging tables with XML or CSV files
▪ Download mapping tasks/templates to hand over to
business users
▪ Check monitoring to see running jobs, access to
messages, and download files
▪ Use mass processing if you want to trigger actions
for specific instances
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Getting started with the migration cockpit
Key takeaways
In this unit you have learned
▪ How to use the SAP Fiori app Migrate Your Data to
migrate data to SAP S/4HANA Cloud, public edition
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Demo Slides – to be hidden for recording
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Getting started with the migration cockpit
Demo details
1. Open SAP Fiori app “Migrate Your Data” – user with necessary roles
2. Create migration project
– Choose the Create button → “Direct Transfer” will be handled in unit 9
– Select Local SAP S/4HANA Database Schema connection
– Choose migration object Bank
– Finish creating the migration project
3. Populate migration objects with data
– Download the template for migration object Bank
– Fill template with data manually
– Upload template and follow guided procedure
– Migrate data
4. Verify data in relevant app
NOTE: When you set the migration project to “Finished”, you can specify a retention period for the data.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Getting started with the migration cockpit
Create project – General data
Name your project
Local SAP S/4HANA Database
System will generate staging tables in the internal schema of the
SAP S/4HANA Cloud system
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
13
Getting started with the migration cockpit
Create project – Migration objects
You can use the search field
Add your migration object
via button or drag & drop
To proceed, review your entries
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
14
Getting started with the migration cockpit
Create project
Use Edit to add other
migration objects
Create your project
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
15
Getting started with the migration cockpit
Monitoring – Settings
To view a log of all activities,
choose the Monitoring button.
You can view the current settings for
your project at any time by choosing
the Settings button.
Here, you can change settings for the
project. For example, you can add
additional migration objects.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
16
Getting started with the migration cockpit
Trigger actions via dropdown list
Find the selected migration objects.
If you need to add additional ones later on, use
the Settings button.
The system proposes the next action to be performed.
For example, “Upload File” after creating the project.
Here, you start the action for one object only.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
17
Getting started with the migration cockpit
Download templates for multiple migration objects
3
1
You can download the templates for
several migration objects by selecting
them and then clicking Download
Template.
2
A messages toast appears
– check Monitoring for file download
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
18
Getting started with the migration cockpit
Mapping tasks
Certain migration objects use control parameter mapping tasks to control
specific data migration procedures – see example Product.
These mapping tasks appear before filling the staging tables with data.
Check them first before proceeding.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
19
Getting started with the migration cockpit
Mapping tasks (specify mapping values)
You can specify value
mappings and transform
values from the source
system to the target system.
Search help for target values
provides existing values in the
SAP S/4HANA Cloud target system.
Details about mapping tasks in KBAs 3003068, 3076466 and 3075948
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
20
Getting started with the migration cockpit
Migration project screen – More buttons
3
Buttons for quick access
▪ Monitoring – to view a log of all activities
▪ Mapping tasks – all mapping tasks for your project
▪ Job management – adjust number of background jobs
▪ Settings – general settings, e.g. add new migration objects
▪ Finish project
See more details in application help.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
21
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 4: Filling the Staging Tables
Filling the staging tables
Agenda
Ways to populate data
XML template
CSV template
Demo CSV upload
XML or CSV?
Other possibilities
Where to find information
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Filling the staging tables
Ways to populate data
You can fill the staging tables by using:
or
XML files*
or
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
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Filling the staging tables
Introduction to the XML template
Check the Introduction worksheet for information about how to fill the template file.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Filling the staging tables
Important information on the XML template
Important information
▪ Read the introduction and check field list before starting
filling the template
▪ Check the mandatory fields, data type, and length
▪ You can expand the SAP Structure and SAP Field
columns to check the technical names
▪ Expand and read the tooltips (line 8)
▪ Copy and paste values only using the following options:
− Within XML file: paste option + values (V)
− From notepad/text editor: paste special + Text
− From somewhere else: paste option + keep text only and
then choose Text
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
Filling the staging tables
Introduction to the CSV template
CSV template
Staging tables in migration cockpit
Help Portal: Downloading template files
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
Filling the staging tables
Introduction to the CSV template
▪ More flexible way to populate the staging tables using CSV files.
▪ Widely known and compatible format for sharing, uploading, and
migrating data.
▪ Faster file creation and modification due to the simple structure
and nature of the CSV format.
▪ Upload the CSV file that contains only the data that should be
migrated (no need to use comma to fill the empty fields)
▪ Use the naming convention during the CSV upload and the file
will be mapped to the data structure automatically, for example
S_MARA#FreeText.csv
▪ Upload several CSV files with a ZIP folder
Help Portal: Downloading CSV template files
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Filling the staging tables
Important information on the CSV template
More flexibility: you can upload a CSV file that only contains the data that should be migrated
(no need to fill the empty fields) and also change the order of the fields if required.
Cost center MO template
Cost center filled template
“Cost center”, “valid from”, and “valid to”
are the first fields in this CSV template file.
When you fill the template, you can change the
order of the fields. Do not forget to change the
order in the header row.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Filling the staging tables
Important information on the CSV template
Naming convention: use the naming convention for uploading the CSV file. The system will
automatically map* the CSV files to the relevant data structures: <data structure name>#
<optional user input>.csv
* It is about mapping the CSV file to the data structure (staging table) to fill the
staging tables. The processing mapping task is a different step and will come later.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Filling the staging tables
Important information on the CSV template
Check the CSV settings before downloading the CSV templates
In the Project Settings, check your
CSV file options.
If needed, set the field delimiter to
Semicolon or Tab (Comma is chosen
by default)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Filling the staging tables
How to fill the staging tables with CSV files
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Filling the staging tables
XML or CSV?
XML
CSV
▪ Using XML is a stable option for entering and
editing values manually.
▪ You need to use a separate CSV file for each
data structure.
▪ All data is contained in one file.
▪ There is no built-in protection for data formats.
▪ It contains detailed information about the
relevant data structures as well as instructions
about how to enter data in the file.
▪ A readme file is also available for each migration
object with information about the data structures
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
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Filling the staging tables
XML or CSV?
CSV template
XML template
The single CSV file represents one worksheet in the XML template file
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
13
Filling the staging tables
Other possibilities
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:
▪ Migrate 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
We recommend that you look at the following materials and decide how you would like
to populate the staging tables:
▪ KBA 2733253 FAQ Migrate Data Using Staging Tables
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
14
Filling the staging tables
Where to find information?
Application Help
Transferring Data from XML Template Files to Staging Tables
Transferring Data from CSV Template Files to Staging Tables
Demo videos
XML upload
CSV upload
KBAs
Additional Information about Transferring Data from CSV Template Files to Staging Tables
Migration Cockpit: How to correctly fill data into XML template
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
15
Filling the staging tables
Key takeaways
In this unit you have learned
▪ Different ways to fill the staging tables
▪ Important information on the XML and CSV templates
▪ Where to find additional information on filling the
staging tables
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
16
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 5: Issue Handling During the Migration Process
Issue handling during the migration process
Agenda
Business partner concept
Different ways to check error messages, including demo
Correction file
Handling duplicate key errors
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Issue handling during the migration process
Business partner concept
The business partner is a leading object in SAP S/4HANA. All customers and suppliers should
be migrated as business partners.
Aim: to migrate the business partners which have customer and supplier roles.
Solution:
1. First, migrate data for the Customer migration object
2. Use the migration object Supplier – extend existing record by new org levels to add the supplier data
This process is also described in KBA 2748819 – Migrate Business Partners with Supplier and
Customer roles
In case of any issues, please refer to:
KBA 2848224 – Migration Cockpit: Collective KBA for Business Partner (Customer, Supplier)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Issue handling during the migration process
Adding additional information on customer/supplier
If you want to add additional information for a customer or supplier, the following standard migration
objects are available:
Customer
Supplier
Customer – extend existing record by new org levels (*)
Supplier – extend existing record by new org levels (*)
Customer – extend existing record by multiple addresses (*)
Supplier – extend existing record by multiple addresses (*)
Customer – extend existing record by Credit Management data (*)
Supplier – extend existing record by Thailand branch code (**)
Customer – extend existing record by Thailand branch code (**)
Used APIs:
*CMD_MIG_BP_CVI_CREATE
**CMD_MIG_BRANCH_CODE_CREATE
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Issue handling during the migration process
Different ways to check error messages
View: which messages occurred for an activity?
Simulation run no. 4
Simulation run no. 1
Instance 111
Message AA123
Instance 112
Instance 113
Message BB444
View: Which
messages occurred
for one instance?
Simulation run no. 2
Simulation run no. 3
Message HJ123
Instance 114
Message UU555
Instance 115
Message ZZ333
Instance 116
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
View: Which instances
are relevant for one
message?
5
Issue handling during the migration process
Different ways to check error messages
Which messages occurred for
an activity?
Monitoring
Which instances are relevant for
one message?
Messages in the project view
(messages for the object)
Which messages occurred for
one instance?
Messages in the instances view
buttons
Which messages occurred during
a simulation/migration run for a
migration object?
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
History in the migration object
view
6
Issue handling during the migration process
Monitoring (1)
On the Monitoring screen you can see
all activities related to the project
Which messages occurred for an activity?
Select the activity and the status
“Completed with Errors” to see all
the messages containing an error
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Issue handling during the migration process
Messages in the project view (2)
In Messages you can see messages
related to the latest activity (simulation
or migration)
Select relevant migration objects –
press Messages button
Which instances are relevant
for one message?
Toggle between migration objects
Click to see the instances to
which this message applies
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Issue handling during the migration process
In Messages you can see activities
related to simulation and migration
of the particular instance
Messages in the instance view (3)
Which messages occurred for one instance?
Click on number to get a list
of all erroneous instances
All messages referring to
this single instance
Click Error to get the message for
the corresponding instance
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Issue handling during the migration process
In History you can see all activities
related to the migration project
History (4)
Which messages occurred during a simulation/migration run for a migration object?
Click on migration object
name to get details
Select History tab to view messages for
the selected migration object and action
Select Show Messages
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Issue handling during the migration process
Demo: error messages
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Issue handling during the migration process
Correction file
After the migration, you can generate a correction file that contains all the migration object instances in the
staging tables that have the status Error.
Help Portal: Creating Correction Files
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Issue handling during the migration process
Handling duplicate key errors
If duplicate key errors occur, the status of the file
will change to Transfer of Data to Staging
Tables Failed
You still can transfer data to staging tables and:
▪ Skip files with duplicates
▪ Replace duplicates with instances from file
Help Portal: Handling Duplicate Key Errors
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
13
Issue handling during the migration process
Key takeaways
In this unit you have learned
▪ How to migrate business partners
▪ The different ways to check error messages
▪ How to establish a correction file after the erroneous
data migration
▪ How to handle duplicate key errors
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
14
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 6: Best Practices and Challenges
Best practices and challenges
Agenda
Set up your project
Enhancing data migration performance
Mass change
Migration objects
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Best practices and challenges
Set up your project
Use only one project
Use several projects
It might seem that one project for each application
would lead to a better progress overview for a
dedicated area but:
+ ▪ Mapping values valid for all migration objects
▪ Central overview and control of the migration
must keep mapping in sync between
- ▪ You
the projects: additional effort and error-prone
▪ 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
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Best practices and challenges
Enhancing data migration performance
Recommendations
▪ Do not start the migration of all objects in a migration project in parallel. There is a sequence for migrating objects,
because of the dependencies between objects.
▪ Parallelization is meant for migration objects with high data migration volumes.
▪ Try to prevent many people working in parallel on separate migration projects.
▪ Try to avoid that users trigger 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 the full number of jobs, complete the data
migration, and then start migration of the next object.
▪ Even if you assign a higher number of data transfer jobs to run in parallel, the effect on performance depends on the
overall system load.
▪ Consider that additional activities might be running in the system that also fill the process queue.
▪ If you experience performance problems, consider executing the data migration at times 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
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Best practices and challenges
System types
No transport functionality is available for migration projects in SAP S/4HANA Cloud
Dev system
Test system
Production system*
▪ Create/recreate the project
▪ Fill the staging tables
▪ Process the mapping tasks
▪ Simulate
▪ Migrate
▪ Validate the migrated data
* migrated data can not be deleted from the production system
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
Best practices and challenges
Plan your project go-live
▪ Check the upgrade and maintenance schedule before migration to a production system
▪ To reduce errors throughout data migration in SAP S/4HANA Cloud use the SAP S/4HANA migration cockpit
▪ The Migrate your Data – Migration Cockpit app is available in read-only mode during SAP S/4HANA Cloud upgrades
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
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
Best practices and challenges
Mass change
The APIs used with migration cockpit are APIs to create data. The update of existing data is therefore not supported.
Mass change is available after an initial data migration. Search for “mass maintenance” to see for which object the mass
maintenance app is available
http://help.sap.com/S4_CE_MO
Check the migration object documentation, for example Customer or Product
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Best practices and challenges
Migration object updates
Content is permanently adapted and
therefore the templates used in one
release might no longer be used with
higher releases.
You can see the change overview for the
particular release or for particular migration
object.
SAP S/4HANA Cloud – Release
Comparison of Migration Object Templates
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Best practices and challenges
Migration object updates
If a migration object update is required, you will get a pop-up message when
any action is triggered (download template, simulate, migrate).
As described in the message, go to the migration object screen and start the
Update there.
Always use the latest migration object templates for your release. As the content is always updated,
the templates from previous releases may not correspond to the updated migration object structure.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Best practices and challenges
Migration object updates
Alternatively, you can go to the migration object screen and click Check for Updates
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Best practices and challenges
Object dependencies
During project creation
Predecessors are also listed in the
migration object documentation
http://help.sap.com/S4_CE_MO
In our example, the migration object
Product was used.
After adding the predecessors
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Best practices and challenges
Mapping download/upload
You can work on mapping tasks not only in the migration cockpit but also on your local computer using the
download/upload functionality.
1. Download templates/download values
2. Edit values in XML
3. Upload the XML file to the migration
cockpit
4. Confirm values automatically/
Replace existing values
Blog: Maintaining the mapping
values with download/upload
functionality – SAP S/4HANA
migration cockpit
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Best practices and challenges
Key takeaways
In this unit you have learned
▪ How to set up your project
▪ How to enhance data migration performance
▪ How to mass change the data after migration
▪ How to update the migration objects and where to
find migration object dependencies
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
13
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 7: Related Apps in the Data Migration
Process
Related apps in the data migration process
Agenda
Overview
Data Migration Status app
Define Settings for Legacy Data Transfer app
Situation Handling
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Related apps in the data migration process
Overview
Data Migration Status app
Define Settings for Legacy Data Transfer app
▪ Check the statuses for all records after
simulation and migration; get info about all
messages
▪ Set Posting Date per Company Code in the
Migration Key Date field
▪ See running jobs at a glance and get
notifications
▪ For details, check KBA 2754615 –
SAP S/4HANA Migration Cockpit:
Information about Fix Posting Date
▪ And much more. For more details, check the
Help Portal – Data Migration Status
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
▪ Set Legacy Data Transfer Status
3
Related apps in the data migration process
Data Migration Status app
Application Help for Data Migration Status
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Related apps in the data migration process
Data Migration Status app – Features
The app provides the following key features:
▪ Get an overview of your migration objects and projects in real time
▪ Use filters and change view settings to drill down into reports faster
▪ See detailed statuses for all records
▪ Get info on all messages
▪ Export reports to Microsoft Excel files
▪ Click-through Tutorial (Learning Hub Subscription necessary)
▪ KBA 2681413 FAQ for SAP S/4HANA Data Migration Status App
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
5
Related apps in the data migration process
Data Migration Status app – Features
Real-time progress monitoring and
background job status
Many filter capabilities
Notification upon completion of migration job
Audit management
Ready-to-use record statistics
Instance sub-structure record counts
Source record linked with migration status
and internal number
Extended statistics
Ready-made status log and no need to store
and distribute the log
Configure migration objects for extended
statistics logging
Export to Excel
Export extended statistics
Quick and easy failed records evaluation
Validation by structure fields relevant for
value conversion
Smart data validation by navigation to
respective SAP Fiori app
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
Related apps in the data migration process
Data Migration Status app – Statistics
▪ Filter the uploaded content by:
– migration period
– migration project
– object name
– record status (failed, imported, ready to import)
▪ Statistics for simulated and migrated records on
instance level
Indicates that 100% of records were successfully
migrated
Indicates that simulation or migration completed
with errors
Indicates that simulation completed with 100%
success and the records are ready to be imported
Blog: Data Migration – Status Monitoring
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Related apps in the data migration process
Data Migration Status app – Extended statistics
Export the report, including statistics, to Microsoft Excel files.
▪ Video: Extended Statistics in 'Data Migration Status' app
▪ Blog: Extended Statistics in 'Data Migration Status' app
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Related apps in the data migration process
Define Settings for Legacy Data Transfer app
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 transfer such data 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 for 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 period (month, quarter, year) since
this will fit into the normal reconciliation cycle.
Documentation via Configuration Help button
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Related apps in the data migration process
Situation Handling
When simulation or migration is completed, a notification is displayed that the data migration results
are available. If you click it, you will be redirected to the Data Migration Status app for more details.
“Data Migration Complete” notification is preactivated for the Data Migration Status app
Situation Handling Template: CA_DATA_MIGRATION_STEP_COMPLETED
Help portal: Situation Handling for data migration
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Related apps in the data migration process
Key takeaways
In this unit you have learned
▪ The additional apps that help you in your data migration
task
▪ The capabilities of the Data Migration Status app and
Define Settings for Legacy Data Transfer app
▪ Notification from Situation Handling
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 8: Options for Supporting Additional
Requirements
Options for supporting additional requirements
Agenda
Remote database connection
Extensibility
Migration Object Modeler
Customer influence
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Options for supporting additional requirements
Remote SAP HANA database connection
Remote SAP HANA Database Schema
▪ Select this option if you want to fill the staging table with data using your
preferred tools
▪ System will generate staging tables in a remote SAP HANA DB schema
Required Setup
1. SAP BTP Settings
− Create SAP HANA Cloud instance
− Create Communication User and assign corresponding roles
2. SAP S/4HANA Cloud Setup
− Create communication system with BTP credentials
− Create communication arrangement SAP_COM_0678
− Set up outbound communication user
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Options for supporting additional requirements
System setup – remote SAP HANA database connection
SAP BTP
Staging
table 1
Staging
table 2
via SAP HANA
Cloud instance
ODBC
3 Data extraction and fill of staging tables
via SAP or third-party tools, or
Microsoft Excel XML/CSV template files
Customer
Application data
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
SAP S/4HANA Cloud
ODBC
SAP S/4HANA
migration cockpit
Staging
table 3
...
Remote SAP HANA DB
schema*
Data Source(s)
Staging table creation
for selected
migration object
4
1 Select Remote SAP HANA
Database Schema
for your migration project
Read Access
Status Update
6
of Record
Application
interface
5 Insert / Update via API
Application tables
* Prerequisites:
▪ SAP Business Technology Platform (BTP), SAP HANA Cloud instance
▪ Communication arrangement (service) SAP_COM_0678
Hint:
Follow the setup instructions in Process Navigator for solution process 2Q2
https://me.sap.com/processnavigator/SolP/2Q2
4
Options for supporting additional requirements
Comparison of local and remote database connection
Connection
Location for the staging tables
Tables filled via
Local SAP S/4HANA Database
Schema
Staging tables will be created in same HANA
DB schema as SAP S/4HANA Cloud, public
edition.
▪ XML template files
▪ CSV template files
Staging tables will be created in the separate
SAP HANA Cloud instance.
▪ 3rd party tools (staging tables can
be accessed via DB layer)
▪ XML template files
▪ CSV template files
Standard use case
Remote SAP HANA Database
Schema*
Specific customer use case
* 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
5
Options for supporting additional requirements
Key user extensibility – Custom fields support
Key user extensibility
SAP S/4HANA migration cockpit
▪ Business expert or implementation consultant can use
the Custom Fields app to create additional fields
▪ Some migration objects support these custom fields
– check migration object list (details next slide)
▪ Example: Add product-related bonus to product master
data, see video
▪ If supported, custom fields will automatically be
reflected in the template of the corresponding
migration object
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
6
Options for supporting additional requirements
Custom fields support – Available migration objects
List of available migration objects with custom field support http://help.sap.com/S4_CE_MO
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Options for supporting additional requirements
Custom fields support – Check for Custom Fields
▪ Use Check for Custom Fields to update migration object
▪ On History tab, find detailed messages
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Options for supporting additional requirements
SAP S/4HANA migration object modeler
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
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).
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Options for supporting additional requirements
SAP Notes for migration objects – Details on which fields are available
SAP Notes for released migration objects:
▪ SAP Note 3020259: Customer
▪ SAP Note 3019787: Supplier
▪ SAP Note 3263101: Product
Only the migration objects listed in
SAP Note 2999428 are supported by the app.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Options for supporting additional requirements
SAP S/4HANA migration object modeler
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
11
Options for supporting additional requirements
Request a new feature, request a new migration object
Request any idea or feature on our Customer Influence page
Please vote for other ideas
to help us prioritize them!
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
12
Options for supporting additional requirements
Key takeaways
In this unit you have learned
▪ What the different option for database connection comprises
▪ How migration objects support custom fields
▪ What the SAP S/4HANA migration object modeler is used for
▪ What to do if you have further requests
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
13
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Migrating Data to SAP S/4HANA Cloud, Public Edition
Unit 9: Summary and Outlook
Summary and outlook
Agenda
Outlook: migrate data directly from SAP system
Data migration process in SAP S/4HANA migration
cockpit
Checklist for data migration project
Further resources
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
2
Summary and outlook
Outlook: migrate data directly from SAP system to SAP S/4HANA Cloud, public edition
▪ Migration approach now available in SAP S/4HANA Cloud, public edition
within Early Adopter Care Program as of 2302
▪ Connects via communication arrangement to SAP ERP source system
▪ Registration page:
Influence Opportunity Homepage – Customer Influence (sap.com)
▪ More information (prerequisites and available objects):
SAP Note 3252723 – SAP S/4HANA Migration Cockpit – Direct Transfer for
Public Cloud
We are looking for customers in realize phase for migrating an SAP ERP system or partners for own tests.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
3
Summary and outlook
SAP S/4HANA migration cockpit – Migration process
SAP S/4HANA Cloud,
public edition
SAP S/4HANA Cloud,
private edition
Select
migration objects
Get data
SAP Business
Suite
Map and transform data
Model and design to reflect custom
requirements*
Simulate
Migrate
SAP S/4HANA
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.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
4
Summary and outlook
SAP S/4HANA migration cockpit – Facilitate business data migration
Tool of choice for
migration to
SAP S/4HANA
Preconfigured
migration content
specific to
SAP S/4HANA
Integrated in
SAP Activate
methodology
Guided and safe
migration
Flexible and
extendable
Part of SAP S/4HANA
and SAP S/4HANA
Cloud (included in these
licenses)
Comprehensive set of
preconfigured migration
objects, such as
customers, suppliers,
and so on
Proven methodology
integrated in
SAP Activate roadmap
Step-by-step guidance
through the migration
process
Ability to use custom
field support for existing
migration objects
Best practices
Preconfigured migration
objects
Migration Object
Modeler for specific
migration objects
Ready-to-use solution
Support customers with
new implementations
Facilitate initial data load
ensuring a consistent
end user experience
and a simplified data
migration
Automated mapping
between source data
and SAP S/4HANA
target values
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Data validation to
ensure high data quality
and consistency
Lower cost, project
duration, and risk for our
customers
5
Summary and outlook
Checklist for data migration project – In a nutshell
Get an Overview
Understand
Prioritize & Focus
Simplify
Align
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
▪ Which migrations objects are relevant?
▪ How many records do we have?
▪ Do we migrate them manually or automatically?
▪ Do we have the necessary resources to prepare and migrate them?
▪ Have all required processes been discussed and set up in the system?
▪ Do I have the knowledge to do my daily business in the new system?
▪ Do I understand the concepts and processes of the new system?
▪ What are the dependencies between the migration objects?
▪ Which migration objects are really business-critical?
▪ Which records are really business-critical?
▪ What is the single most important next step?
▪ Can migration tasks be simplified or automated?
▪ Can we reduce the administrative workload?
▪ Can we reduce the business workload?
▪ Have we aligned and communicated a common project and cutover plan?
▪ Have dependent streams aligned on a migration approach and the exchange
of relevant mappings and information?
6
Summary and outlook
SAP S/4HANA migration cockpit – Resources to start with
Data Migration Landing Page
on SAP Help
SAP Community Topic Page
SAP S/4HANA Migration Cockpit
Cookbook
▪ Access documentation –
Application Help
▪ Find Frequently Asked Questions
▪ Get guidance on data migration
▪ Write a blog posts
▪ View additional slide decks and
training information
▪ Ask a question
▪ Details on how to use the Migrate
Your Data – Migration Cockpit app
▪ https://community.sap.com/topics/
s4hana-migration-cockpit/
▪ SAP S/4HANA Migration Cockpit
Cookbook
▪ http://help.sap.com/S4_CE_DM
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
7
Summary and outlook
SAP S/4HANA migration cockpit – Further resources
Standard presentation Migrate Your Data to SAP S/4HANA Cloud, public edition
Available migration objects http://help.sap.com/S4_CE_MO
Migration template samples Staging*
Link List –
Further Useful
Documentation
Migration object changes release comparison*
Migration of Financial Accounting Master and Transactional Data
Data Migration Status app http://help.sap.com/S4_CE_DM_STATUS
Video Library for data migration
Click through demo: Introducing the SAP S/4HANA Migration Cockpit**
* For customers and partners only
** A one-time registration in SAP Learning Hub, edition for SAP Enterprise Support,
is required. A detailed step-by-step guide on how to register.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
8
Summary and outlook
Bottom line
DATA MIGRATION IS NECESSARY
It is one key task during the transition to SAP S/4HANA.
Unfortunately, it is often underestimated. It is not done
just by pressing a button.
Make sure to understand your data migration
requirements early and plan for them accordingly.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
9
Summary and outlook
Key takeaways
In this unit you have learned
▪ About the outlook for migrating data directly from an SAP system
▪ The summary for the SAP S/4HANA migration cockpit
▪ Where to find further information
Thank you for participating.
The openSAP course “Migration Data to SAP S/4HANA Using the Migration Cockpit” starting 27 September
2023 will take a detailed look at the SAP S/4HANA migration cockpit in SAP S/4HANA and SAP S/4HANA
Cloud, private edition.
This 3 week course deals with the functionality, including different migration approaches and modeling
environment.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
10
Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2023 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.