SAP S - 4HANA Cloud, Private Edition - Onprem - Migration Cockpit - Cookbook

PUBLIC
SAP S/4HANA migration cockpit

SAP S/4HANA, SAP S/4HANA Cloud, private cloud
1 / 91
Table of contents
1 Purpose and Scope of the document ............................................................................................................ 4
2 Introduction – Data Migration Using the Migrate Your Data - Migration Cockpit App ......... 4
2.1 Your Way to SAP S/4HANA ........................................................................................................................................................ 5
2.2 Introduction to Data Migration.................................................................................................................................................. 7
2.3 SAP S/4HANA Migration Cockpit at a Glance..................................................................................................................................... 8
2.4 Migration Approaches ....................................................................................................................................................................................... 9
2.5 Migrate Data Using Staging Tables ............................................................................................................................................................ 9
2.6 Migrate Data Directly from SAP System (Direct Transfer) ........................................................................................................... 9
2.7 SAP S/4HANA Migration Cockpit – Comparison of Migration Approaches ..................................................................... 9
3 Migrate Data Using Staging Tables................................................................................................................ 10

3.1 Process Flow ........................................................................................................................................................................................................ 10
3.2 Creating Migration Project ........................................................................................................................................................................... 10
3.3 Creating new migration project ................................................................................................................................................................. 10
3.4 Add more migration objects after creating the project (optional) ...................................................................................... 15
3.5 Copy a project (optional) .............................................................................................................................................................................. 16
3.6 Migration object documentation.............................................................................................................................................................. 18
3.7 Migration project screen................................................................................................................................................................................ 18
3.8 Migration object screen – overview ....................................................................................................................................................... 19
3.9 Migration Object Tables Screen ............................................................................................................................................................... 20
3.10 Choosing Actions ............................................................................................................................................................................................. 20
3.11 Download XML Templates for Multiple Migration Objects .................................................................................................. 23
3.12 Populate the migration object template with data .................................................................................................................... 23
3.13 Populate the CSV Template File with Data ..................................................................................................................................... 25
3.14 Upload Files........................................................................................................................................................................................................ 27
3.15 Prepare Mapping Tasks............................................................................................................................................................................... 30
3.16 Mapping Tasks (Specify Mapping Values) ...................................................................................................................................... 31
3.17 Mapping Values (Uploading Values / Deleting Values) .......................................................................................................... 32
3.18 Migration Object Update ............................................................................................................................................................................ 34
3.19 Using the Mass Processing Function................................................................................................................................................... 35
3.20 Simulation / Migration .................................................................................................................................................................................. 37
3.21 Canceling the Simulation / Migration .................................................................................................................................................. 39
3.22 Error Handling ................................................................................................................................................................................................... 39
3.23 Transport functionality ................................................................................................................................................................................ 45
3.23.1 Basic facts ........................................................................................................................................................................................................ 45
3.23.2 Concept ............................................................................................................................................................................................................. 45
4 Migrate Data Directly from SAP System ..................................................................................................... 46

4.1 Process Flow ........................................................................................................................................................................................................ 46
4.2 Technical preconditions and system preparation ....................................................................................................................... 46
4.3 Creating Migration Project ........................................................................................................................................................................... 48
4.3.1 Create new migration project ................................................................................................................................................................. 48
4.3.2 Add more migration objects after creating the project (optional) .................................................................................. 52
2 / 91
4.3.3 Copy a project (optional) .......................................................................................................................................................................... 54
4.4 Migration object documentation.............................................................................................................................................................. 55
4.5 Migration project screen................................................................................................................................................................................ 56
4.6 Migration object screen – overview ....................................................................................................................................................... 56
4.7 Choosing Actions................................................................................................................................................................................................ 57
4.8 Selection/Reselection of data ................................................................................................................................................................... 58
4.9 Prepare Mapping Tasks ................................................................................................................................................................................. 59
4.10 Mapping Tasks (Specify Mapping Values) ...................................................................................................................................... 60
4.11 Deleting mapping values ............................................................................................................................................................................ 62
4.12 Migration object instances list................................................................................................................................................................. 63
4.13 Migration object instances list - migration results view ........................................................................................................... 63
4.14 Detailed view of the migration process............................................................................................................................................. 64
4.15 Single instance processing ........................................................................................................................................................................ 66
4.16 Using Mass Process Function .................................................................................................................................................................. 69
4.17 Simulation / migration .................................................................................................................................................................................. 73
4.18 Cancelling the Simulation/Migration ................................................................................................................................................... 74
4.19 Error handling ................................................................................................................................................................................................... 75
4.19.1 Type of Messages........................................................................................................................................................................................ 75
4.19.2 Different ways to check error messages ....................................................................................................................................... 75
4.20 Transport functionality ................................................................................................................................................................................ 80
4.21 SAP S/4HANA Migration object modeler ........................................................................................................................................ 81
4.22 Migrate Data Directly from SAP System – Further Migration Scenarios ...................................................................... 82
4.22.1 SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA................................................................................................... 82
4.22.2 SAP EWM to EWM Based on SAP S/4HANA ............................................................................................................................... 82
4.22.3 SAP SCM (APO/ SPP) to eSPP Based on SAP S/4HANA .................................................................................................... 83
4.22.4 SAP CRM to SAP S/4HANA for Customer Management ..................................................................................................... 84
5 Migration Content............................................................................................................................................................................................. 85
5.1 Migration Object ................................................................................................................................................................................................. 85
5.2 Migration Object Updates ............................................................................................................................................................................ 86
5.3 Complex migration objects.......................................................................................................................................................................... 89
5.4 SAP S/4HANA - Release Comparison of Migration Object Templates ............................................................................ 90
6 Tipps and Tricks ................................................................................................................................................................................................. 91
3 / 91
1 Purpose and Scope of the document
This document is intended as guidance on data migration using the SAP S/4HANA migration cockpit in SAP
S/4HANA and/or SAP S/4HANA Cloud, private edition. This document provides users with more details on
how to use the Migrate your Data – Migration Cockpit app and other relevant information.
2 Introduction – Data Migration Using the Migrate Your Data -

Migration Cockpit App
SAP enables data migration to SAP S/4HANA for customers coming from any legacy system. SAP S/4HANA
customers can take advantage of reliable migration approaches built into SAP S/4HANA using the SAP
S/4HANA Migration Cockpit together with a set of predefined data migration objects.
With the Migrate Your Data - Migration Cockpit app, you can migrate business data to SAP S/4HANA. You can
migrate data directly from certain SAP source systems, or you can use staging tables to migrate data.
Key Features
You can use this app to:
• Create migration projects to migrate data, and to monitor the status of the migration.
• Select the migration objects that are relevant for your migration scenario (the app uses migration
objects to identify and transfer the relevant data).
• Process any mapping tasks for the migration objects.
• Simulate the migration before migrating your data to SAP S/4HANA and monitor the status of the
simulation process.
• Migrate your data to SAP S/4HANA and monitor the status of the migration.
2.1 Your Way to SAP S/4HANA
● System Conversion
• Bring your business processes to the new platform

• 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
● Selective Data Transition
• Partly re-use, partly re-implementation

• Covers the migration of relevant business data from SAP ERP to SAP S/4HANA
• 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/re-implementation
• Reengineering and process simplification based on latest innovations

• Highly standardized, fueled with best practices & based on a clean core
• Implement innovative business processes with preconfigured best practice content on an innovative
platform
• Migrate your master data and retire old landscape
→ Delivery model: included in SAP S/4HANA shipment
© 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 this material. 5 / 91
• Supports the New Implementation transition path

• Part of SAP S/4HANA and SAP S/4HANA Cloud (included in these licenses)
• Supports customers with the “New Implementation” scenario
• SAP’s recommended approach for the migration of business data to SAP S/4HANA and SAP
S/4HANa Cloud
2.2 Introduction to Data Migration
Your SAP S/4HANA migration requirements
• Migrate data from SAP systems and non-SAP systems to SAP S/4HANA and SAP S/4HANA Cloud
• Provide a comprehensive migration solution with no programming required by the customer
• Include mapped data structures between source and target systems
• Reduce test effort
• Make the migration solution auditable
2.3 SAP S/4HANA Migration Cockpit at a Glance
Data migration to SAP S/4HANA: Easy, safe, and accelerated
In detail: Preconfigured migration content

Key benefits
• Content (= migration objects) covers all best practice migration objects

for master data and transactional data*
• Automated mapping between source and target structure
• Migration programs are automatically generated – no programming required
by the customer
• Standard APIs are used to post the data to SAP S/4HANA system
In detail: Migration object modeler

Flexible and extendable
• Customer-specific enhancements to SAP standard objects delivered with the

o Easily adjust input structure
o Map structures and fields
o Add or change migration object selection criteria (Direct Transfer)
• Integration of newly created objects
o Custom objects
o SAP standard objects that are not yet in the scope of the SAP S/4HANA migration cockpit
o Use standard APIs or code your function module
2.4 Migration Approaches
For the SAP S/4HANA migration cockpit there are two different migration approaches, depending on the source
system:
2.5 Migrate Data Using Staging Tables

• Staging tables are created automatically in SAP HANA DB (either locally or in a remote system)
• Populate these staging tables with business data using:
• XML template files
• CSV template files
• SAP or third-party ETL tools
2.6 Migrate Data Directly from SAP System (Direct Transfer)

• Connect source system (ABAP-based SAP source systems) via RFC connection
• Selection
o Based on predefined selection criteria (for example company code for ERP source system)
and selected migration objects
o Can be adapted with the SAP S/4HANA migration object modeler
• Supports data migration scenarios from SAP ERP, SAP AFS, SAP APO SPP, SAP CRM, SAP EWM
2.7 SAP S/4HANA Migration Cockpit – Comparison of Migration Approaches
3 Migrate Data Using Staging Tables
3.1 Process Flow

The SAP S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for your
project and migrates data from these staging tables to the target SAP S/4HANA system.
Template files are provided for every migration object. You can use these template files to fill the staging
tables with data. Alternatively, you can fill the staging tables by using your preferred tools (for example SAP
Data Services).
3.2 Creating Migration Project

Start your migration process by clicking Migrate Your Data tile.
The project overview screen will be opened. If it is your first time working with the migration cockpit, the list
should be empty.
3.3 Creating new migration project

To create your migration project, you click Create.
The Fiori App includes both migration approaches: Migrate Data Using Staging Stables and Migrate Data
Directly from SAP System. Choose Migrate Data Using Staging Tables.
When you create a project, you need to fill as 1st on General Data screen the fields:
• Name (you can change it later)
• Mass transfer ID (assigned automatically, but you can choose your own)
• Local or remote SAP S/4HANA Database Schema.
There are two options for the database connection:
a) Local SAP S/4HANA database

• The system will generate the staging tables in the internal schema of the SAP S/4HANA system
• Use this option if you only want to use XML template files to fill the staging tables with data
b) Remote SAP HANA database

• The system will generate the staging Tables in a remote SAP HANA DB schema
• Prerequisite: a valid database connection (please refer to KBA 2733253)
• Select this option if you want to fill the staging table with data by using your preferred tools
As 2nd step, you specify on Development Package screen the details for your migration project. Enter a
development package, so that you can transport your project to another system.
Note: If you enter $TMP you will not be able to add your project to a transport request. This means that the
project is only available locally in the client and system where you created the project.
As the 3rd step, on Migration Objects screen add migration objects to your project. The link to the
documentation on the migration objects and predecessors’ information is also available in the migration
cockpit.
When you choose migration objects, the migration cockpit proposes you to add the dependent objects
(predecessors).
Note: You can also add more migration objects to the project later, but you cannot delete a migration object
from the project in SAP Fiori.
You can delete a migration object from your project by using the Migration Object Modeler (LTMOM).
Note: If data has already been selected in the SAP S/4HANA Migration Cockpit, and at least one migration
object instance exists, the migration object cannot be deleted in the Migration Object Modeler.
Finally, you click Create Project. It takes some time for the system to prepare your objects.
3.4 Add more migration objects after creating the project (optional)
On the Migration Project screen, users can see their selected migration objects. In case you need to add
additional ones later, you can use the Settings button.
3.5 Copy a project (optional)
To copy an existing migration project, select on Migration Projects screen the migration project that you want
to copy and press Copy button. On the follow-on Copy Project screen specify under General Data screen a
new name for your migration project, and if necessary, adjust the data base connection and development
package.
All migration objects, mapping tasks, and settings, including any custom changes, are copied to the new
migration project.
Note that only the definition of the mapping tasks are copied to the new project. No mapping values, or fixed
values are copied.
3.6 Migration object documentation

To get detailed information about a migration object, you can click the migration object name in the Migration
Object column. This link will directly forward you to the migration object documentation on help.sap.com
(Application Help)
3.7 Migration project screen

On the Migration Project screen, the progress bar indicates the status of your single migration object. You
can drill down into numbers to get details on tables/tasks/instance level.
In addition, you trigger all the steps that are required to transfer the data for each migration object to the
target SAP S/4HANA system.
In addition, you can quickly access additional information and tasks such as:
• Monitoring – to view a log of all activities

• Mappings tasks – all mapping tasks for your project
• Job management – adjust number of background jobs
• Settings – general settings for example add new migration objects
• Finish project
See more details in application help.
3.8 Migration object screen – overview
On the Migration Object screen, you get detailed information about a migration object. To get detailed
information about a migration object, click the migration object name in the migration object column.
The system displays the migration object screen, where you can view the following information:
• Link to SAP Help Portal Documentation
• View
• Table structure
• History of events, including logs
• Dependencies to other migration objects
• Technical information (relevant for support)
3.9 Migration Object Tables Screen
Migration Cockpit driven data operations for staging tables
• Reset Table Settings. the current transfer status will be reset. Also, to unlock the staging tables so
that you can adjust data again (freeze triggers will be deleted). You can do this, for example, to
unlock the tables after a user cancelled jobs manually, or if an unexpected event occurred. On the
Migration Project screen, the system resets the number of instances that have been simulated
successfully and the number of instances for which errors exist to 0. The number of migrated
instances is not adjusted. (See more details in Tips & tricks section)
• Delete all records. Note: already migrated instances will not be deleted from the staging tables. An
error message will appear in such case.
• Adjust Structure. To reflect the latest version of the migration object provided by SAP (for example,
if the staging tables were adjusted or dropped by error)
More details about mapping tasks can be found in the following KBAs 3003068, 3076466, and 3075948. Commented [A1]: Prüfen ob noch aktuell
3.10 Choosing Actions
After creating a migration project, the migration cockpit guides you through the various steps of the data
migration.
Under Actions, the system proposes the next action to be performed. You can choose whether you want to
perform the actions for individual, multiple, or all migration objects in your project at the same time.
Under Actions, the system proposes the next action to be performed.
Usually, it should be in the following order:

• Download Template
• Upload File
• Prepare
• Mapping Tasks*
• Simulate
• Migrate
• Create Correction File
You can also flexibly choose which steps you want to do next.
*For some complex migration objects (such as Customer, Product, Supplier), the migration cockpit will
propose to maintain Mapping Tasks as a 1st step (and not “download template”). These complex objects
contain controlling parameters or fixed values that should be handled before downloading/uploading
template. For more information, refer to KBA 3076466.
You can perform all the actions for several object simultaneously. You need to choose several objects from
the list and click the needed action. For example, you can download templates for several migration objects:
select several migration objects and choose Download Template.
Another example: select several migration objects and choose Actions. You can perform the actions: Prepare,
Mapping tasks, Simulate and Migration for several migration objects.
3.11 Download XML Templates for Multiple Migration Objects
The next step after the project creation is Download template.
Option 1: You can download the template for every migration object separately by choosing action
Download Template
Option 2: You can choose several migration objects and click Download Template button
3.12 Populate the migration object template with data

1) Open the XML template. In the Introduction sheet, you will find information on how to fill the XML files.
The default size limit for each uploaded XML or zip file is 100 MB.
The knowledge base article KBA 2719524 contains further information about file size limits for SAP S/4HANA
(On-Premise-Version) and S/4HANA Cloud.
2) Before starting to fill the template, check the mandatory fields under the Field List worksheet.
3) In the Master Record worksheet, expand the row 8 to get detailed information about each field.
Recommendations on how to fill the XML templates:
• Copy and paste values only using the following options:

o Paste option then Values (V) - within XML file
o Paste special and then choose Text - from somewhere else
o Paste option then keep text only - from notepad/text editor
• Enter legacy data in generated XML file template for the selected migration object
3.13 Populate the CSV Template File with Data

You can populate the CSV templates with the field delimiter:
• Comma
• Semicolon
• Tab
The default delimiter is Comma. You need to set in the Settings which field delimiter you want to use before
downloading the template
When you open the CSV.zip template, you see a CSV file for each data structure of the migration object. The
CSV file names are structured as follows: <data structure name >#<optional user input>.csv
For example: S_MARA#FreeText.csv (where #Freetext can be changed to your own)
When you open the file, you see the Header data with the Comma delimiter, which is a default delimiter in
the CSV Settings.
CSV template files are quite flexible, you can insert only the data that you need to migrate. You can change
the order of the fields. Do not forget to adjust the header structure in this case.
For additional information about using CSV files, see KBA 3296020.
3.14 Upload Files

The file upload should be performed for every migration object separately. Click Upload File.
Upload XML files
The process is different for XML and for CSV files.
Upload XML files
Drag and drop the filled XML file from your computer to the migration cockpit or use Upload button.
After some time, the file appears with the status Data Successfully Transferred to Staging Tables.
Upload CSV files
Drag and drop the zipped CSV files (recommended). It is the easiest way to upload the CSV files.
3.15 Prepare Mapping Tasks
The staging tables for each migration object need to be prepared before they can be used to transfer data to
SAP S/4HANA. Choose the option Prepare.
Note: This process must be repeated whenever new data is added to the staging tables.
3.16 Mapping Tasks (Specify Mapping Values)
On the Mapping Tasks screen, users can specify value mappings and transform values from the source
system to the target system.
There are 2 ways how you can maintain the mapping values: directly in the migration cockpit or by using
download/upload mapping values functionality.
Additionally, you can search for target values using the search help button. This function shows the existing
values in the SAP S/4HANA target system.
3.17 Mapping Values (Uploading Values / Deleting Values)
Uploading Values
You can download the mapping templates or mapping values, change the values in the file and upload them
back to project. By the upload you can not only replace the existing mapping values but also confirm them.
General Procedure for uploading mapping values:

1) Click “Download Values” button
2) Edit the relevant information in the XML file
3) Upload the XML file again
4) Under Additional Settings, select the option Modify Values / Add Values
Note: Any duplicate values will be replaced with the values from the file.
As a first step, you download empty Mapping Templates or Download Values in the migration project.
You maintain your mappings in the excel on your local computer. Then you can upload the file with the
mapping values to the migration cockpit.
In this next step, you can choose if you would like to confirm all your uploaded mapping values automatically
and if you want to replace existing values or add values.
You can find more details in KBA 3003068.
Step by step guidance is provided in the blog: Maintaining the mapping values with download/upload
functionality
Deleting Mapping Values
You can delete mapping values easily by selecting them and clicking Delete.
If you need the deleted mapping values, you can go back to the project view and use Prepare action, so the
migration cockpit prepares the mapping tasks one more time and deleted values will appear. Control
parameters or fixed values cannot be deleted (only value mappings).
3.18 Migration Object Update

On the Migration Project screen, the progress bar indicates the status of your single migration object.
You can drill down into numbers to get details on tables/tasks/instance level.
If the migration objects require the update with the content from SAP, you will get a message by performing
activity, such as download templates. Click OK.
For example, in the Migration Project view you get a notification “Updates available for 2 migration
objects”. Click Display Objects.
In the pop-up message, you can select all the objects needed update and click Update.
Alternatively, you can check for the migration objects update by clicking on the migration object name. for
example, Bank and then Check for Updates.
If the object needs to be updated, you get a notification.
3.19 Using the Mass Processing Function

Steps:
1) Click on number of instances to get to detail level of migration object instances

2) Choose the button Mass Processing
3) To start mass processing select corresponding action (for example Simulate) and choose the button
Step2
4) Use filter options to select relevant instances
5) Review chosen instances before deletion, simulation, or migration
3.20 Simulation / Migration
You can simulate/migrate random 10%, random 500 items or custom selection where you specify which
instances should be simulated/migrated.
You also have an option to simulate and migrate all instances with errors.
Choose the migration object,
• select Actions – Simulate – selecting all instances or all instances with errors
• select Actions - Migrate – selecting all instances, all instances with errors or all successfully simulated
instances
3.21 Canceling the Simulation / Migration
Once you have started simulation or migration, you have the possibility to cancel the corresponding process.
On the Migration Project view screen, click Monitoring. Click the Cancel button.
3.22 Error Handling
There are different possibilities to analyze (error) messages depending on what you want to check
1) Which messages occurred for an activity?

2) Which instances are relevant for 1 error message? (for the last simulation/migration run)
3) Which error messages occurred for 1 instance? (for the last simulation/migration run)
4) Which messages occurred during a particular simulation/migration run for a migration object
Which messages occurred for an activity?
See the Monitoring screen. Select the activity and the status “Completed with Errors” to see all the messages
containing error.
Which instances are relevant for 1 message?
Check in the messages in the project view. Select relevant migration objects – press Messages button.
Toggle between the migration objects. Click on the number of the instances concerned by this message.
Which messages occurred for 1 instance?
Check in the messages in the instances view. Click on number to get a list of all erroneous instances.
Click on Error to get the message for the corresponding instance.
You will see all the messages referring to this instance.
Which messages occurred during a simulation/migration run for a migration object?
Click on the migration object name to get details.
Select History tab to view messages for the selected migration object and action. Select Show Messages
For all the mentioned error message screens, you can use:
• Free text search

• Group
• Sort
• Download the file with the messages
3.23 Transport functionality
3.23.1 Basic facts

▪ The transport functionality used in the migration cockpit is designed to transport content from
one system to another.
▪ The functionality is available with SAP S/4HANA 2021 onwards for the approach Migrate Data Using
Staging Tables.
▪ You assign a development package while creating a project (SAP Fiori app). This assignment cannot
be changed later.
▪ You can add projects, migration objects, and rules to a transport request in transaction LTMOM.
▪ It is not possible to create or edit projects in non-modifiable systems, they can only be executed.
Usually, non-modifiable systems are quality and production systems. For more information about
non-modifiable systems, see slide 12 in Transport Concept - Migrate Data Using Staging Tables.
▪ More details can be found in SAP Note 3104790
Note that instances already uploaded to the staging tables will not be transported.
Only the definition of a rule, fixed value, translation object or variable is added to a transport request
and transported. No values, for example mapping values, are included.
3.23.2 Concept
4 Migrate Data Directly from SAP System
4.1 Process Flow

With the data migration approach “Migrate Data Directly from SAP System” you can migrate your master data
and business data directly from SAP source system and non to SAP S/4HANA.
An RFC connection connects the SAP S/4HANA migration cockpit to your SAP ERP source system.
Like the staging approach, the “Migrate Data Directly from SAP System” uses migration objects to identify and
transfer the relevant data.
Currently, this migration approach supports the following migration scenarios:

• SAP ERP to SAP S/4HANA
• SAP Apparel and Footwear to SAP S/4HANA
• SAP EWM to EWM in SAP S/4HANA
• SAP CRM to SAP S/4HANA for Customer Management
• SAP APO SPP to SAP S/4HANA Extended Service Parts Planning (eSPP)
Note: The SAP S/4HANA Migration Cockpit does not support the migration of data from SAP S/4HANA
systems to other SAP S/4HANA systems. SAP S/4HANA Finance systems (previously known as SAP Simple
Finance) are classified as SAP S/4HANA systems.
4.2 Technical preconditions and system preparation
Technical preconditions
The following technical preconditions must be met, depending on the source system:
▪ SAP ERP to SAP S/4HANA, the lowest supported ERP release is ERP 6.0 (SAP NetWeaver 7.0),
▪ SAP Apparel and Footwear to SAP S/4HANA, the supported release is AFS 6.0,
▪ SAP EWM to EWM in SAP S/4HANA, the lowest supported EWM release is EWM 5.1 (SAP NetWeaver
7.0).
▪ SAP CRM to SAP S/4HANA for Customer Management, lowest supported release is SAP CRM 7.0
▪ SAP APO SPP to SAP S/4HANA Extended Service Parts Planning (eSPP), recommended source
system release is SCM 7.14
System preparation
The following preparations need to be done in the system landscape before you can start using the SAP
S/4HANA migration cockpit:
▪ SAP Fiori must be set up as prerequisite. See SAP Fiori Apps Reference Library (search for SAP Fiori
app Migrate Your Data) and SAP Note 3039598
▪ The relevant add-on DMIS must be installed in the source system. See SAP Note 2747566
▪ RFC connection between SAP S/4HANA system and SAP source system must be available.
▪ All necessary notes must be implemented: see SAP Note 2747566. You can also use the SAP Note
analyzer to check if all relevant SAP Notes have been implemented. See SAP Note 3016862
▪ The program CNV_PE_MC_LOAD_OBJECTS must be run in the SAP S/4HANA target system. See SAP
Note 2870546
▪ In addition:
▪ Check customizing: relevant customizing in the target must be available (for example,
organizational units, define document type for migration, define accounts for migration,
remove account blocks)
▪ Ensure availability of required authorizations
▪ For required roles, please check the installation guide (see below)
Steps are also described in the SAP S/4HANA Installation Guide (chapter 7). Please see:
▪ Installation Guide for SAP S/4HANA 1909: link

4.3 Creating Migration Project
Start your migration process by clicking Migrate Your Data tile.
The project overview screen will be opened. If it is your first time working with the migration cockpit, the list
should be empty.
4.3.1 Create new migration project

To create your migration project, you click Create.
and choose Migrate Data Directly from SAP System.
When you create a project, you need to fill the fields:

• Name (you can change it later)
• Select relevant scenario. As mentioned above the following migration scenarios are currently available:
• SAP ERP to SAP S/4HANA
• SAP Apparel and Footwear to SAP S/4HANA
• SAP EWM to EWM in SAP S/4HANA
• SAP CRM to SAP S/4HANA for Customer Management
• SAP APO SPP to SAP S/4HANA Extended Service Parts Planning (eSPP)
• Enter your RFC connection to the SAP source system
As the next step, choose one or more organization units from which selection is made. The organization units
are preconfigured data based on key organization units, depending on migration scenario, for example,
company codes for SAP ERP to SAP S/4HANA.
In the SAP S/4HANA migration cockpit, you can only restrict the selection using certain criteria, such as
company codes (depending on the selected scenario.
The modelling environment (transaction LTMOM in the S/4 backend) provides more possibilities to influence
the selection from the source system.
You can find more information

• in LTMOM slide deck and BAdI details in KBA 3092921 and
• in KBA 3249988 you can find further details on how to influence the selection process
In addition, you can adjust the selection criteria after you create the project (e.g. additional organizational
unit), but only if no migration object instances have been selected or migrated. In addition, it is not possible to
adjust the selection criteria if the activity "Select Data" is in process.
Note that you can delete migration object instances by using report CNV_PE_MC_DEL_ITEMS as described
in SAP Note 2857598.
In step 3, you can add migration objects to your project. The link to the documentation on the migration
objects and predecessors’ information is also available in the migration cockpit.
When you choose migration objects, the migration cockpit proposes you to add the dependent objects
(predecessors).
Note: You can also add more migration objects to the project later, but you cannot delete a migration object
from the project in SAP Fiori.
You can delete a migration object from your project by using the Migration Object Modeler (LTMOM).
Note:
If data has already been selected in the SAP S/4HANA Migration Cockpit, and at least one migration object
instance exists, the migration object cannot be deleted in the Migration Object Modeler. In this case, you can
use the report CNV_PE_MC_DEL_ITEMS to delete the migration object instances as described in SAP Note
2857598.
Finally, you click Create Project. It takes some time for the system to prepare your objects.
4.3.2 Add more migration objects after creating the project (optional)
On the Migration Project screen, users can see their selected migration objects. In case you need to add
additional ones later, you can use the Settings button.
4.3.3 Copy a project (optional)
To copy an existing migration project, select on Migration Projects screen the migration project that you want
to copy and press Copy button. On the follow-on Copy Project screen specify under General Data screen a
new name for your migration project, and if necessary, adjust the RFC connection.
All migration objects, mapping tasks, and settings, including any custom changes, are copied to the new
migration project.
Note that only the definition of the mapping tasks are copied to the new project. No mapping values, or fixed
values are copied.
4.4 Migration object documentation
To get detailed information about a migration object, you can click the migration object name in the Migration
Object column. This link will directly forward you to the migration object documentation on help.sap.com
(Application Help)
4.5 Migration project screen
On the Migration Project screen, you trigger all the steps that are required to transfer the data for each
migration object to the target SAP S/4HANA system.
In addition, you can quickly access additional information and tasks such as:
• Monitoring – to view a log of all activities

• Mappings tasks – all mapping tasks for your project
• Job management – adjust number of background jobs
• Settings – general settings for example add new migration objects
• Finish project
See more details in application help.
4.6 Migration object screen – overview
On the Migration Object screen, you get detailed information about a migration object. To get detailed
information about a migration object, click the migration object name in the migration object column.
The system displays the migration object screen, where you can view the following information:
• Link to SAP Help Portal Documentation
• Table structure
• History of events, including logs
• Dependencies to other migration objects
• Technical information (relevant for support)
4.7 Choosing Actions
After creating a migration project, the migration cockpit guides you through the various steps of the data
migration.
Under Actions, the system proposes the next action to be performed. You can choose whether you want to
perform the actions for individual, multiple, or all migration objects in your project at the same time.
Usually, it should be in the following order:
• Select data
• Prepare Mapping Tasks
• Mapping Tasks
• Simulate
• Migrate
You can also flexibly choose which steps you want to do next.
4.8 Selection/Reselection of data
To select data from the source system, click Actions and choose Select Data on the Migration Project
screen. As mentioned in chapter 6.10, you can start the selection for multiple migration objects if required.
If you have already selected data and choose the selection button again, you have the possibility to reselect
the data.
Reselection of data
▪ New Selection: Deletes former selection and selects completely new (available as of SAP S/4HANA
2020).
▪ Add Additional Instances: Adds new instances from the source system to already selected instances
(available since SAP S/4HANA 1909 – default behavior); no update of already selected instances.
Note: If you have changed data in the source, use the new selection button to delete the formerly selected
instances and start a completely new selection.
If you work with SAP S/4HANA 1909, you can use the report mentioned in the following SAP Note 2857598 to
delete the former selection and repeat the select of data.
4.9 Prepare Mapping Tasks
The Action step Prepare Mapping Tasks has been introduced with SAP S/4HANA 2021. The Action Select
Data has been split into two steps:
• Select Data: creates the migration object instances

• Prepare Mapping Tasks: fills the mapping tasks with proposal values: source value = target value
Why is this separate step introduced?

▪ Optimized downtime. If you want to upload mapping values using Microsoft Excel, you can skip the
activity Prepare Mapping Tasks.
▪ More flexibility in the setup phase when fine-tuning the data selection and finding the right
selection criteria, or when developing your own mapping rules. Select Data now only selects the
data.
▪ More transparency about the activity that the system is currently running.
Note: Up to release 2020, the step Select Data always executed the step Prepare Mapping Tasks implicitly.
4.10 Mapping Tasks (Specify Mapping Values)
On the Mapping Tasks screen, users can specify value mappings and transform values from the source
system to the target system.
There are 2 ways how you can maintain the mapping values:
• Directly in the migration cockpit
• You can specify value mappings and transform values from the source system to the target system.
• Search help provides existing values in the SAP S/4HANA target system.
Note: The mapping tasks will be filled with values only after the system has selected the data from the
source system and you have executed the action prepare mapping tasks. Without these steps, the mapping
tasks will be empty.
• By using download/upload mapping values functionality
You can download the mapping templates or mapping values, change the values in the file and upload them
back to project. By the upload you can not only replace the existing mapping values but also confirm them.
As a first step, you download empty Mapping Templates or Download Values in the migration project.
You maintain your mappings in the excel on your local computer. Then you can upload the file with the
mapping values to the migration cockpit.
In this next step, you can choose if you would like to confirm all your uploaded mapping values automatically
and if you want to replace existing values or add values.
Note: Any duplicate values will be replaced with the values from the file.
Note: The files may contain target values that were created automatically (for example internal numbering).
Ensure that you adjust the target values (or remove them completely in the files) before uploading the file to
another system.
If you work with SAP S/4HANA 1909, you can download/upload mappings only in transaction LTMOM.
4.11 Deleting mapping values
You can delete mapping values easily by selecting them and clicking Delete.
If you deleted mapping values by mistake or for other reasons, you can go back to the project view and
execute the action Prepare mapping tasks again, so that the migration cockpit prepares the mapping tasks
again and deleted values will appear. Fixed values cannot be deleted (only value mappings).
4.12 Migration object instances list
On the Migration Object Instances screen, you can view the records for each migration object instance.
1. The system offers various possibilities to search and filter the list.
2. Use the gear wheel to select the columns to be displayed.
3. Click the arrow to view the migration object instance details.
Note: Instances download is possible with 2021 FPS01 (via the migration results view)
4.13 Migration object instances list - migration results view
On the Migration Object Instances screen, you can view the migration results for migration object instances by
switching to the Migration Results view. When you choose this view, the system displays one or more fields
that contain the migration results. In these migration result fields, you can view the data that has been created
in the SAP S/4HANA system for a migration object instance.
• New tab: Migration Results

This view displays document no. or master data key of the newly created data record
• Clicking the link opens the relevant app where you can access the record, e.g. the activity type ZA in
controlling area 0001
4.14 Detailed view of the migration process
The detailed view of the migration progress gives more control over the migration process.
The Detailed View provides

▪ A more detailed representation of the migration process in form of a process flow graph
▪ The ability to execute actions for specific transfer steps, for example, execute only one migration
step of a multistep migration object
In the Detailed View, you can view all transfer options and transfer steps for an object. The migration
object (MM – Purchase scheduling agreement) has one transfer option (one row) and one step (simulate step
1/ migrate step1)
Dotted line = optional activity

Solid line = mandatory activity
By Clicking on the arrow opens a popup. You view object instances that have been processed successfully as
well as any instances which ended with errors in the previous activities.
Note: An instance can only have one status at a time. This means, for example, if an instance has been
simulated successfully, it no longer appears under Mapping Tasks Prepared Successfully.
A detailed view of the migration process – More complex example
The migration object (CO – Cost Center) has one transfer option (one row) and two step (simulate step 1/
migrate step 1 = Create Cost Center and simulate step 2/ migrate step 2 = Update Cost Center Text).
Dotted line = optional activity

Solid line = mandatory activity
4.15 Single instance processing

On the Migration Object Instances list you can prepare mapping tasks, simulate, migrate or exclude single
instances or have a look at the error messages.
To exclude a single instance, mark the entry, and press the Exclude button.
On the migration project screen, you will now find one excluded item. The number of items to be migrated
(not started) has changed from “31” to “30”.
4.16 Using Mass Process Function
Mass Processing give you the possibility to trigger actions on selected instances. You can start the Mass
Processing on Migration Object Instances screen by choosing the Mass Processing button.
To start mass processing select one of the corresponding action (Prepare Mapping Tasks, Simulate, Migrate
Next Steps, Migrate All Steps, Exclude, Undo Exclude) and choose the button Step2.
Use filter options to select relevant instances and choose the button Step3.
Review chosen instances before you execute the action.
Execute the action by choosing Start.
In addition, you can execute mass processing by selecting a single object. For example, choose action
Migrate.
In the pop up New Migration choose Custom Selection.
The action for mass processing is displayed, in our example Migrate. Choose the Step2.
Use filter options to select relevant instances and choose the button Step3.
Review chosen instances before you execute the action.
Execute the action by chossing the Start.
4.17 Simulation / migration
On the Migration Project screen, you can choose, which items you want to simulate / migrate.
You can simulate/migrate several migration objects at once
• Simulation: selecting all instances or all instances with errors

• Migration: selecting all instances, the ones with errors or all successfully simulated instances
Or you can simulate/migrate only one migration object and choose different options. Here you can
• simulate/migrate random 10%

• random 500 items
• all instances
• custom selection (see mass processing)
4.18 Cancelling the Simulation/Migration
Once you have started simulation or migration, you have the possibility to cancel the corresponding process.
On the Migration Project view screen, click Monitoring. Click the Cancel button.
4.19 Error handling
4.19.1 Type of Messages
There are different types of messages: Error, Warning, Success, Information. Error and Warning should be
differentiated. If you get a warning, you still can proceed with the migration process. If you get an error, you
cannot proceed with the migration progress and need to check the error first and edit your data.
4.19.2 Different ways to check error messages
There are different possibilities to analyze (error) messages depending on what you want to check
1) Which messages occurred for an activity?

2) Which instances are relevant for 1 error message? (for the last simulation/migration run)
3) Which error messages occurred for 1 instance? (for the last simulation/migration run)
4) Which messages occurred during a particular simulation/migration run for a migration object?
Which messages occurred for an activity?
See the Monitoring screen. Select the activity and the status “Completed with Errors” to see all the messages
containing error.
Which instances are relevant for 1 message?
Check in the messages in the project view. Select relevant migration objects – press Messages button. Toggle
between the migration objects. Click on the number of the instances concerned by this message.
Which messages occurred for 1 instance?
Check in the messages in the instances view. Click on number to get a list of all erroneous instances.
Click on Error to get the message for the corresponding instance.
You will see all the messages referring to this instance.
Which messages occurred during a simulation/migration run for a migration object?
Click on the migration object name to get details.
Select History tab to view messages for the selected migration object and action. Select Show Messages.
For all the mentioned error message screens, you can use:
• Free text search

• Group
• Sort
• Download the file with the messages
4.20 Transport functionality
Basic facts
• The transport functionality used in the migration cockpit is designed to transport from one system to
another.
• Introduced with SAP S/4HANA 2020.
• You assign a development package while creating a project (SAP Fiori app). Note that it is not possible to
change this assignment later.
• You have the possibility to add projects, migration objects, and rules to a transport request in transaction
LTMOM.
• It is not possible to create or edit projects in non-modifiable systems, they can only be executed. Usually,
non-modifiable systems are quality and production systems.
For more information about non-modifiable systems, see slide 10 in Transport concept - Migrate Data
Directly from SAP System and SAP Note 3043614
• For information about how to transport from client to client within one system, see slide 8 in Transport
concept - Migrate Data Directly from SAP System.
Note that selected instances and mapping values are not transported!
Separation between design time and execution time activities
4.21 SAP S/4HANA Migration object modeler
You start the SAP S/4HANA migration object modeler using transaction: LTMOM
The SAP S/4HANA migration object modeler provides flexibility and extendibility for the SAP S/4HANA
migration cockpit. With the migration object modeler, you can:
▪ Create user defined migration objects using a wizard

▪ Add customer tables or fields to a standard migration object or to a new migration object
▪ Add or change selection criteria of standard migration objects or user defined migration objects
▪ Possibility to add projects, migration objects, and rules (mapping tasks) to a transport request
▪ Debug the transformation and/or the posting process
▪ Use standard APIs or code your function module
▪ Copy migration objects
▪ Create or edit transformation rules
You can find more details in the Deep dive slides:

• SAP S/4HANA Migration Object Modeler (Direct Transfer)
4.22 Migrate Data Directly from SAP System – Further Migration Scenarios
In total 5 migration scenarios are available for the Migrate Data Directly from SAP System approach. The
ERP to SAP S/4HANA scenario is explained in detail in the above chapters. The same migration process
steps apply to the scenarios mentioned below.
Different migration objects are relevant for different scenarios. The system displays the relevant
migration objects based on the selected scenario.
The data selection is predefined on specific criteria (organizational units). These organizational units are
predefined for each scenario. Examples:
▪ EWM in S/4HANA: Warehouse number

▪ CRM in S/4HANA Service: Sales organization
Migration projects can cover only one migration scenario.
Note: As a prerequisite, check the technical preconditions and system preparation described in chapter 6.2
4.22.1 SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA
Key Points:
• Migrate data directly from SAP System
• Selection of data from SAP source system through RFC
• Data Selection based on company code
• Capability to derive complex selection criteria automatically from company code
• Pre-defined AFS specific migration objects are supported
See: Migration object list in SAP Help Portal (SAP S/4HANA)
4.22.2 SAP EWM to EWM Based on SAP S/4HANA
Key Points:
• Migrate data directly from SAP system
• Data Selection based on warehouse number
• Pre-defined EWM specific migration objects are supported
4.22.3 SAP SCM (APO/ SPP) to eSPP Based on SAP S/4HANA
Key Points:

• Data Selection based on plant
• Pre-defined APO specific migration objects are supported
4.22.4 SAP CRM to SAP S/4HANA for Customer Management

• Data Selection based on Sales Organization
• Pre-defined CRM specific migration objects are supported
5 Migration Content
Migration content is built for initial migration of your data to your SAP S/4HANA. This means that you can
create data with a migration object, but you can't change or update existing data with it.
5.1 Migration Object
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 are ready for immediate use
• Categorized in master data and transactional data (no historical data)
• Contains rules how values from source to target are handled – called “mapping”
• Can be extended or newly created with the SAP S/4HANA migration object modeler
What is migration content?
• Migration content is the sum of all migration objects
What about updates on migration objects delivered by SAP?
• Updates are shipped by SAP (e.g. a standard field was added) with a new Release or via TCI notes
You can find the migration object list in the SAP Help Portal here: Migration object list in SAP Help Portal (SAP
S/4HANA)
In the SAP Help Portal:

• See the documentation available
• Download migration object list
• Filter for migration approach/ scenario
Starting with SAP S/4HANA 1610 FPS2, you can enhance customer projects based on these delivered
standard migration objects or you can create your own objects using the SAP S/4HANA migration object
modeler (transaction LTMOM).
For further information, please see SAP Note 248123 Information published on SAP site.
5.2 Migration Object Updates
Direct Transfer
Note: Avoid upgrading to a newer release during a migration project if possible!
Note: Avoid upgrading to a newer release

during a migration project if possible!
1) What is the impact of upgrading to a newer release during a migration project using the Direct
Transfer approach?
Though SAP tries to avoid incompatible changes between releases, it cannot be guaranteed that migration
objects delivered by SAP work after the upgrade.
Same applies to migration objects adapted or created by the customer.
Recommendation
• Projects need to be created and executed within the same release, or in other words:
Do not execute projects which have been created before the system was upgraded
• If you upgrade your SAP S/4HANA system to a new release, we recommend creating completely new
migration projects
• Custom MOs or extended MOs need to be created in the higher release again
2) Migration object updates, implemented due to critical enhancements or corrections, will not be
reflected in your running migration project:
 Updates for migration content will be installed via TCI note
 TCI notes will be listed in a composite note (release based)
 SAP Note 3266284 - SAP S/4HANA On-Premise 2022 Migration Cockpit: Central
Note for Transfer Data Directly from SAP System – SAP ERP or SAP AFS to SAP
S/4HANA
 Content is imported into client 000 (note: only a copy of the migration object is used in your
migration project)
 Load content into work client with report CNV_PE_MC_LOAD_OBJECTS. (See SAP Note
2870546 – Release 2022 and lower.
3) You will only have the latest version of a migration object in your project when you
 create a new migration project or
 add the migration object to the project for the first time or
 add an actual version of the migration object via the modeler (as of release 2021)
Note: It’s essential to follow the instruction for TCI note handling!
4) Migration object situation

Migration object updates are triggered not only by corrections, but also by new requirements reported by our
customers and partners:
▪ Please be aware that if a new object is planned, it can only be delivered with the next release at the
earliest!
▪ In case of small questions, write to: sap_s4hana_migration_cockpit@sap.com
▪ Suspecting an error, open a ticket on component CA-LT-MC.
▪ Describe a reproduceable example
▪ Chose the correct priority (in case it is urgent, chose “high”)
5.3 Complex migration objects
There are several migration objects, which require a special preparation due to its complexity. These objects
need special attention not only from the business point of view, but also from the migration procedure:
• Read the object documentation and focus on the necessary steps described
• Be aware of object dependencies and/or special sequences of dependent objects to be considered
• Check necessary upfront decision like numbering, mapping requirements
• Use additional documentation / deep dive materials (if available)
Example: Customer Vendor Integration (CVI)
• SAP S/4HANA Migration Cockpit - Direct Transfer - Customer Vendor Integration CVI
• 2748819 - Migrate Business Partners with Supplier and Customer roles
Example: Migration of Financial Accounting Master Data and Transactional Data
• Migration of Financial Data
5.4 SAP S/4HANA - Release Comparison of Migration Object Templates
The release comparison of migration object templates helps you to see what has changed and what is new
for the different releases. You can find this on the SAP Help Portal under:
• SAP S/4HANA – Release Comparison of Migration Object Templates
Note: The release comparison is currently available for File/Staging only.
6 Tipps and Tricks
On the Job Management screen, you can adjust the maximum number of background jobs used for your
project. You can also adjust the maximum number of jobs to be used per migration object. For more details
see KBA 3066336 and KBA 3065607.
www.sap.com

SAP S - 4HANA Cloud, Private Edition - Onprem - Migration Cockpit - Cookbook

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP S - 4HANA Cloud, Private Edition - Onprem - Migration Cockpit - Cookbook

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP S/4HANA migration cockpit

3 Migrate Data Using Staging Tables................................................................................................................ 10

4 Migrate Data Directly from SAP System ..................................................................................................... 46

2 Introduction – Data Migration Using the Migrate Your Data -

You can use this app to:

• Bring your business processes to the new platform

● Selective Data Transition

• Partly re-use, partly re-implementation

• Reengineering and process simplification based on latest innovations

• Supports the New Implementation transition path

In detail: Preconfigured migration content

• Content (= migration objects) covers all best practice migration objects

In detail: Migration object modeler

• Customer-specific enhancements to SAP standard objects delivered with the

2.5 Migrate Data Using Staging Tables

2.6 Migrate Data Directly from SAP System (Direct Transfer)

2.7 SAP S/4HANA Migration Cockpit – Comparison of Migration Approaches

3.1 Process Flow

3.2 Creating Migration Project

3.3 Creating new migration project

a) Local SAP S/4HANA database

b) Remote SAP HANA database

3.6 Migration object documentation

3.7 Migration project screen

• Monitoring – to view a log of all activities

3.8 Migration object screen – overview

3.9 Migration Object Tables Screen

Migration Cockpit driven data operations for staging tables

3.10 Choosing Actions

Under Actions, the system proposes the next action to be performed.

Usually, it should be in the following order:

3.12 Populate the migration object template with data

• Copy and paste values only using the following options:

3.13 Populate the CSV Template File with Data

For example: S_MARA#FreeText.csv (where #Freetext can be changed to your own)

3.14 Upload Files

The process is different for XML and for CSV files.

Upload XML files

General Procedure for uploading mapping values:

You can find more details in KBA 3003068.

Deleting Mapping Values

3.18 Migration Object Update

If the object needs to be updated, you get a notification.

3.19 Using the Mass Processing Function

1) Click on number of instances to get to detail level of migration object instances

Choose the migration object,

3.22 Error Handling

1) Which messages occurred for an activity?

Click on Error to get the message for the corresponding instance.

Which messages occurred during a simulation/migration run for a migration object?

Click on the migration object name to get details.

• Free text search

3.23.1 Basic facts

4.1 Process Flow

Currently, this migration approach supports the following migration scenarios:

4.2 Technical preconditions and system preparation

▪ Installation Guide for SAP S/4HANA 1909: link

4.3.1 Create new migration project

and choose Migrate Data Directly from SAP System.

When you create a project, you need to fill the fields:

You can find more information

• Monitoring – to view a log of all activities