0% found this document useful (0 votes)

168 views90 pages

SAP S - 4HANA Migration Cockpit - Cookbook - Public Edition

Uploaded by

dengxiumin

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

168 views90 pages

SAP S - 4HANA Migration Cockpit - Cookbook - Public Edition

Uploaded by

dengxiumin

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 90

PUBLIC

SAP S/4HANA Cloud

Cookbook for SAP S/4HANA migration cockpit

SAP S/4HANA Cloud Public Edition

Document History

Version Date Change

1.0 2023-07-20 Initial Version: Migrate Data Using Staging Tables

2.0 2023-10-12 Update for Staging tables approach: structure and content
improvement, adding supporting applications (Data migration status
app, SAP S/4HANA migration object modeler)

3.0 2023-12-14 Update for Staging tables approach: added information about the
release upgrade and migration object update, release comparison.

4.0 2024-02-09 New migration approach: Migrate Data Directly from SAP system

5.0 2024-08-28 Update for Migrate Data Directly from SAP System: added information
about migration object update, release comparison.

Instances within SAP S/4HANA Migration Cockpit

Contents
1. Purpose and Scope of the Document ........................................................................ 6

2. Introduction.................................................................................................................. 7

3. Migrate Data Using Staging Tables............................................................................ 8

3.1. Create Migration Project ..................................................................................................... 8
3.2. Add More Migration Objects after Creating the Project (optional) ................................. 11
3.3. Migration Object Documentation ...................................................................................... 12
3.4. Performing Actions ........................................................................................................... 13
3.5. General Remarks on XML, CSV Template Files and Staging Tables.............................. 15
3.6. Download XML/CSV Templates for Multiple Migration Objects...................................... 15
3.7. Populate the Migration Object Templates with Data ....................................................... 16
3.7.1. Populate the XML Template File with Data ............................................................................... 16

3.7.2. Populate the CSV Template File with Data ............................................................................... 18

3.7.3. XML or CSV? ................................................................................................................................ 21

3.8. Upload Files ....................................................................................................................... 22

3.8.1. Upload XML Files ......................................................................................................................... 23

3.8.2. Upload CSV Files ......................................................................................................................... 24

3.9. Mapping Tasks (Specify Mapping Values) ....................................................................... 24

3.9.1. Maintain and Confirm Mapping Values ..................................................................................... 24

3.9.2. Delete Mapping Values ............................................................................................................... 27

3.10. Simulation and Migration.............................................................................................. 28

3.11. Data validation after migration ..................................................................................... 30

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

4.7. Technical precondition and system preparation ............................................................. 31
4.7.1. Technical Precondition ............................................................................................................... 31

4.7.2. System Precondition ................................................................................................................... 31

4.8. Create Migration Project ................................................................................................... 32

4.9. Add More Migration Objects after Creating the Project (Optional) ................................ 37
4.10. Copy a Project (optional) .............................................................................................. 38
4.11. Performing Actions ....................................................................................................... 40

© 2024 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.
4.12. Selection / Reselection of Data .................................................................................... 42
4.12.1. Selection .................................................................................................................................. 42

4.12.2. Reselection of Data................................................................................................................. 44

4.13. Prepare Mapping Tasks ................................................................................................ 44

4.14. Mapping Tasks (Specify Mapping Values) .................................................................. 45
4.14.1. Maintain and Confirm Values ................................................................................................ 45

4.14.2. Delete Mapping Values ........................................................................................................... 47

4.15. Simulation and Migration.............................................................................................. 47

5. Error Handling ........................................................................................................... 49

5.1. Type of Messages .............................................................................................................. 49
5.2. Different Ways to Check Error Messages ........................................................................ 50
5.2.1. Which messages occurred for each activity? .......................................................................... 50

5.2.2. Which instances are relevant for each message? ................................................................... 51

5.2.3. Which messages occurred for 1 instance? .............................................................................. 53

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

6. Migration Objects and Additional Functionalities .................................................. 56

6.1. Migration Objects in the Migration Object Screen........................................................... 56
6.2. Migration Object Update ................................................................................................... 57
6.2.1. How to update a migration object for Migrate Data Using Staging Tables approach? ........ 57

6.2.2. What are the recommendations when the migration object has been updated? ................. 59

6.2.3. How to update a migration object for Migrate Data Directly from SAP System? ................. 59

6.3. Migration Object Tables Screen........................................................................................ 64

6.4. Migration Object Instance Screen .................................................................................... 65
6.4.1. Instances within SAP S/4HANA Migration Cockpit .................................................................. 70

6.5. Detailed View on Migration Process ................................................................................. 70

6.6. Migration Project Screen – Additional Features .............................................................. 72
6.7. Improving Performance with Job Management ............................................................... 73
6.8. Using the Mass Processing Function .............................................................................. 73
6.8.1. Mass Processing – Migrate Data Directly from SAP System .................................................. 75

6.9. Canceling the Simulation/Migration ................................................................................. 80

6.10. Transporting Projects in Test- and Production System ............................................. 80
6.11. Situation Handling ........................................................................................................ 81

© 2024 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.
7. Supporting Applications ........................................................................................... 83
7.1. Data Migration Status App ................................................................................................ 83
7.1.1. Initial Screen (Migration Object Overview Screen) .................................................................. 83

7.1.2. Data Instances View (Migration Object Overview) ................................................................... 84

7.1.3. Extended Statistics ..................................................................................................................... 85

7.1.4. Audit .............................................................................................................................................. 86

7.2. SAP S/4HANA Migration Object Modeler ......................................................................... 88

7.3. Define Settings for Legacy Data Transfer ........................................................................ 88
7.3.1. Migration Key Date (usually equals the posting date) for Financial Objects ........................ 89

7.3.2. Legacy Data Transfer Status ...................................................................................................... 90

© 2024 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.
1. Purpose and Scope of the Document
The document contains a description of the features of SAP S/4HANA migration cockpit from the creating of
the migration project till the migration. Its purpose is to show in detail the functionality of the “Migrate your
data” app along with screenshots that are not in the overview presentation.

One of the most important aspects of the migration project is error handling. In this guide, we look at 4 ways
to analyze the errors you get at different stages of a project. We also provide the description of the additional
features (f.e. Mass processing functionality) and applications (for example, Data migration status app) that
can increase the efficiency of using the migration cockpit.
The most actual information about the migration cockpit is provided in our SAP S/4HANA migration cockpit
landing page for SAP S/4HANA Cloud Public Edition: http://help.sap.com/S4_CE_DM

© 2024 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.
2. Introduction
SAP enables data migration to SAP S/4HANA Cloud Public Edition for customers coming from any legacy
system. Customers can take advantage of reliable migration approaches built into SAP S/4HANA Cloud
Public Edition using the SAP S/4HANA migration cockpit together with a set of predefined data migration
objects.

For the migration approach “Migrate Data Using Staging Tables”, 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 Cloud Public Edition.

Where are the staging tables located?

When creating a migration project, you specify a location for the staging tables. If you use the option Local
SAP S/4HANA Database Schema, the SAP S/4HANA migration cockpit will generate the staging tables in
the local ABAP schema of the SAP S/4HANA Cloud system.

If you use the option Remote SAP HANA Database Schema, you specify the relevant connection to a
remote SAP HANA schema (SAP HANA Cloud instance on SAP Business Technology Platform) and the
SAP S/4HANA migration cockpit will generate the staging tables there.

Template files are provided for every migration object. You can use these files to the fill the staging tables.
You can also use your tool of choice, for instance, SAP HANA Smart Data Integration (SDI) to fill the staging
tables. In the following screenshots you can see the examples of XML and CSV templates. More information
about the templates, you can read in section 3.6. Populate the migration object templates with data.

XML template CSV template

templates

© 2024 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.
3. Migrate Data Using Staging Tables
Click on Migrate Your Data tile to start your migration process. The project overview screen will be opened.
If it is your first time working with the migration cockpit, the list should be empty.

3.1. Create Migration Project

To create your 1st migration project, click Create.

Choose migrate data using staging tables from the drop-down menu.

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

• Name of you project (you can change it later)

• Mass transfer ID (technical project number that is assigned automatically, but you can choose your own)
• Local or remote SAP S/4HANA Database Schema.

You can use remote schema if you want to use an ETL tool (for example SDI, SAP Data Services, ADP,
etc.) A prerequisite for selecting remote database schema is to have a valid database connection (refer to
KBA 2733253).

If you press enter, or just left-click the mouse, the step 2 button will appear. To proceed, choose Step 2.

As the next step, add migration objects to your project. You can either use the arrows to get the migration
objects from the left to the right OR you can use drag and drop. The link to the documentation on the
migration objects and predecessors’ information is also available in the SAP S/4HANA migration cockpit. For
example, for Product, there are 3 predecessors (dependent migration objects, that should be migrated
before Product migration object). The predecessor information is also available in Help Portal. See chapter 6
Migration Objects and Additional Functionalities.

The migration cockpit will prompt a message to ask you to add the dependent objects (predecessors).

© 2024 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.
Note: You can also add more migration objects to the project later (using Settings, see 3.2. Add more
migration objects after creating the project), but you cannot delete the migration objects from the project.

Finally, click Create Project. It might take some time for the system to prepare your objects. The selected
pre-delivered SAP template migration objects are copied to your own project with all dependent rules and
definitions.

3.2. Add More Migration Objects after Creating the Project (optional)
On the Migration Project screen, users can see their selected migration objects. If you want to add more
objects to your project, click Settings and follow the instruction below.

© 2024 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.
3.3. 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 direct you to the migration object documentation on help.sap.com
(Application Help).

© 2024 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.
3.4. Performing Actions
After creating a migration project, the migration cockpit will propose you to perform the next step. For
example, to Download Template for the migration object Bank.

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

• Download Template
• Upload File
• Prepare
• Mapping Tasks*
• Simulate
• Migrate
• Create Correction File
*For some complex migration objects, such as Customer, Product, Supplier, etc., the migration cockpit will
propose to maintain Mapping Tasks as the 1st step instead of “Download Template”. These complex objects
contain controlling parameters or fixed values that should be handled before downloading/uploading
templates. For more information, refer to KBA 3076466

You can simultaneously perform multiple actions on several objects. You must select the objects you want
by checking their box in the first column and the needed actions accordingly. For example: Select several or
all migration objects and choose Actions. You can perform the actions Prepare, Mapping tasks, Simulate
and Migration for several migration objects.

© 2024 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.
3.5. General Remarks on XML, CSV Template Files and Staging Tables
When you add a migration object to your project, staging tables in the SAP HANA database are automatically
created. These staging tables act as a kind of container, where you put your business data for further
processing. These staging tables (containers) can be filled in various ways (XML/CSV templates, ETL Tools).

When we check e.g. migration object PRODUCT, we see the following staging tables automatically being
created.

You see the names of the staging tables, the technical names (referring to the SAP S/4HANA tables) and the
technical ID. The technical ID follows the naming convention:
/1LT/DS<system ID><numeric identifier>, for example /1LT/DSQKX000928.

Technical details on the staging tables can be found in the meta data that can be downloaded:

When you open the XML template file, you will find how the template file is linked to the staging tables:
Using CSV template files is an expert option for filling the staging tables with data. We do not recommend
using CSV files unless you have a specific use case for doing so.
The general process for uploading CSV files to the SAP S/4HANA migration cockpit is as follows:

3.6. Download XML/CSV Templates for Multiple Migration Objects

The next step after the project creation is Download template.

Option 1: You can download the template for each migration object one by one by choosing the action
Download Template.

Option 2: You can choose several migration objects and click Download Template button

3.7.1. Populate the XML Template File with Data

1) Open the XML template. In the Introduction sheet, you will find information on how to fill the XML files. In
the template, you can also see the current release of your system. In the screenshot example, the template
is for 2402 release of SAP S/4HANA Cloud Public Edition.

• The default size limit for uploading is 100 MB.

• The knowledge base article KBA 2719524 contains further information about file size limits for SAP
S/4HANA Cloud Public Edition.
2) Before filling out the template, check the mandatory fields under the Field List worksheet.

© 2024 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.
3) In the Master Record worksheet, expand row 8 to get detailed information about each field. The
mandatory fields are highlighted with the color.

Recommendations on how to fill the XML templates:

• Copy and paste values only using the following options:

− Paste option then Values (V) - within XML file.

− Paste option then keep text only - from notepad/text editor.

• Enter legacy data in generated XML file template for the selected migration object.
• Some fields are mandatory and some are optional. The wildcard character (‘*’) beside the name of a field
indicates that the field is mandatory. Moreover, the mandatory sheets have the orange color, while the
optional sheets have no color (or white).

3.7.2. 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. If you want to use another delimiter, you can change it in Settings. Please
ensure that any changes to the Settings are done before downloading the template. The downloaded
template will use the delimiter you choose in Settings.

You will get an error message if you download a template in one delimiter format, fill your data in, change the
delimiter in Settings then try to upload the template file filled with your data. SAP S/4HANA migration cockpit
expects you to upload a template formatted with the delimiter chosen in Settings.

© 2024 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.
When you open the CSV.zip template, you will see a Read-me file that contains information about the data
structure as well as how to enter data in the files.

You will also see a list of CSV files for each data structure of the migration object. The CSV file names are
structured as follows: <data structure name>#<optional user input>.csv (f.e. S_MARA#FreeText.csv).
#Freetext can be changed to your own - f.e. S_MARA#first_try.csv

When you open the file, you see the Header data with the Comma delimiter, which is a default delimiter in
the CSV Settings.

© 2024 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.
CSV template files are quite flexible when you use “First Row is Header Row” which is the standard/default
file header option in CSV File Options – Project Settings. You can insert the data that you need to migrate
(edit the header row, delete the fields that you do not need). You can change the order of the fields but
always remember to adjust the header data accordingly.

If you change the File Header Options to “No Header Row (Import All Rows)”, please stick to the same
order as staging table definition. All fields of the staging tables should be filled. For example, if you use
comma (,) as delimiter, the fields that don’t contain value, should be filled with comma (,).

The wildcard character (‘*’) beside the name of a field indicates that the field is mandatory.

© 2024 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.
The description of the fields, as well as type, length and additional comments you will find in the README
file. For additional information about using CSV files, see KBA 3210687.

*Note: If you are filling the CSV files with long texts, please use the double quotes (“). By using CSV files
upload, it is recommended to check data in the Note. As an example, see screenshot:

Please see in the screenshot below how it looks after uploading to the staging tables in the migration cockpit:

3.7.3. XML or CSV?

You may ask, in which case you would need to use an XML template or a CSV template? The answer is: if
you extract your data from the source system using ETL tool, you may prefer using CSV file format. CSV file
format allows you to store more information thanks to its structure. However, we do not recommend using
CSV file format if you have no past experience using CSV templates, unless you have a very specific use
case. It may be easier for you to opt for the XML template files.

Comparing XML template to the CSV template files, you notice that 1 CSV file equals to the 1 worksheet in
the XML template file.

3.8. Upload Files

File uploading should be performed for every migration object separately. Click Upload File.

3.8.1. Upload XML Files

Drag and drop the filled XML file from your computer to the migration cockpit or click Upload button.

After some time, the file appears with the status Data Successfully Transferred to Staging Tables.

Drag and drop the zipped CSV files (recommended). It is the easiest way to upload the CSV files.

The CSV folder will be created in the migration cockpit and if you follow the naming convention, the CSV
files will be transferred to staging tables.

3.9. 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.

3.9.1. Maintain and Confirm Mapping Values

There are 2 ways to maintain the mapping values:

1) directly in the migration cockpit

2) by using download/upload mapping values functionality.

1) Directly in the migration cockpit:

Select the mapping task in the Mapping Tasks screen and enter the needed target value.

© 2024 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.
Additionally, you can search for target values using the search help button. This function shows the existing
values in the SAP S/4HANA Cloud target system.

© 2024 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.
2) By using download/upload mapping values functionality:
You can download the mapping templates or mapping values, change the values in the template files and
upload them to your project. By uploading these mapping values, you can replace the existing mapping
values as well as confirm them.

General procedures to upload mapping values:

1. Click “Download Values” button.

2. Edit the relevant information in the XML file.
3. Upload the updated XML file.
4. Under Additional Settings, select the option Modify Values / Add Values
5. 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.

These mapping values or templates can be revised locally in Excel. When these files are done reviewing,
you can upload the updated files to migration cockpit.

© 2024 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.
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 them as values.

• You will find more details in KBA 3003068.

• Step by step guidance is provided in the blog Maintaining the mapping values with download/upload
functionality.

3.9.2. Delete Mapping Values

You can delete mapping values easily by selecting them then choosing Delete Values.

© 2024 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.
If you need the deleted mapping values, you can go back to the project view, choose Prepare action on the
desired objects, migration cockpit will then perform the mapping tasks one more time and bring back the
deleted values. Control parameters or fixed values cannot be deleted (only value mappings).

3.10. Simulation and Migration

You can simulate/migrate random 10%, random 500 items or custom selection where you specify which
instances should be simulated/migrated.

© 2024 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.
You have an option to simulate and migrate all instances with errors. Select the desired migration object,
select Actions – Simulate/Migrate – All Instances with Errors.

You can simulate/migrate several migration objects at once. Select several migration objects, then choose
Actions – Simulate/Migrate – All Instances/All instances with Errors.

Available actions for these operations:

• Simulation: selecting all instances or all instances with errors

• Migration: selecting all instances, the ones with errors or all successfully simulated instances

© 2024 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.
3.11. Data validation after migration
When the migration is completed, you can check the Migration Results list. In the Migration Project view,
choose the migration object (for example, Bank) and click Migration Results.

You will be navigated to Migration Object Instances screen. Click Download all. All the instances will be
downloaded in excel format to your local computer. You can also directly navigate to the app where the data
was created.

Additionally, the information about how to validate the data in the system after migration is provided in Help
Portal – available migration objects. Every migration object contains the information about post-processing.
For example, for Bank migration object, the posted data can be checked in the following apps:

© 2024 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.
Check also the section 5.8 Situation Handling. Once the simulation or migration is completed, you get a
notification. When you click it, you can navigate to Data migration status app. More information about Data
migration status app, you will find in section 6.1 Data Migration Status app.

4. Migrate Data Directly from SAP System

With the data migration approach “Migrate Data Directly from SAP System” you can migrate your master
data and business data directly from SAP ERP source system to SAP S/4HANA Cloud, Public Edition. A
communication arrangement connects the SAP S/4HANA migration cockpit to your SAP ERP source
system.

Like the Staging Tables 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 scenario:

• SAP ERP to SAP S/4HANA

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.7. Technical precondition and system preparation

4.7.1. Technical Precondition

The following technical preconditions must be met, depending on the source system:

• Your source system is minimum an SAP ERP (ECC 6.0) system

• Your target environment is SAP S/4HANA Cloud, public edition, three-system landscape

4.7.2. System Precondition

The following preparations need to be done before you can start using the “Migrate Data Directly from SAP
System” approach:

© 2024 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.
• Communication Arrangement (SAP_COM_0816) must be set up to connect your SAP S/4HANA
Cloud, Public Edition system to your SAP source system
o For detailed information see Solution Process Data Migration to SAP S/4HANA from SAP
(BH3) in the SAP Signavio Process Navigator
• DMIS 2011 SP25 (or higher) must be installed in your source system
o See SAP note: 1577441, 1577503 and 1648747
• Ensure required authorization role: SAP_BR_CONFIG_EXPERT_DATA_MIG has been created and
assigned using the business role template. In addition, you need to add the respective business
catalogs to your business role for the migration objects you want to use in your project.
• Check configuration: relevant configuration in the target must be available (for example,
organizational units)

4.8. Create Migration Project

Click on Migrate Your Data tile to start your migration process. The project overview screen will be opened.
If it is your first time working with the migration cockpit, the list should be empty.

To create a new migration project, you click Create.

Choose Migrate Data Directly from SAP System from the drop-down menu.

• Name of your project (you can change it later)

• Enter your connection to your SAP source system

As second step, choose one or more organization units from which selection is made. The organizational
units are preconfigured based on the migration scenario: SAP ERP to SAP S/4HANA.

Note: In the SAP S/4HANA migration cockpit, you can only restrict the selection using these criteria. The
app Model Your Migration Objects - Migration Object Modeler provides more possibilities to influence the
selection from the source system.

Note: Which migration objects are available can be found in the SAP Help Portal:
http://help.sap.com/S4_CE_MO (filter by migration approach: Direct Transfer). It is planned to increase the
number of migration objects with future releases. Be aware that we cannot provide you a migration object
roadmap. Additionally, you have the option to request missing migration object for the direct transfer
approach via the Customer Influence Portal, see : SAP S/4HANA Public Cloud Edition - Data Management
and Data Migration.

If the migration objects for the Migrate Data Directly from SAP System approach are not sufficient, please
use in addition the Migrate Data Using Staging Tables approach to migrate your data. This means you
have two create two projects: one using the direct transfer approach, one using the staging tables approach.
You have to keep the mapping in sync (download and upload mapping). For further information please see
chapter 3: Migrate Data Using Staging Tables of this document.

© 2024 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.
The link to the documentation on the migration objects and predecessors’ information is also available in
the SAP S/4HANA migration cockpit. You can either use the arrows to get the migration objects from the left
to the right OR you can use drag and drop.

When you choose migration objects, click Review.

Note: Only predecessors that are available as migration objects (for the Migrate Data Directly from SAP
System approach) are displayed. For available migration objects and detailed information please check SAP
Help Portal: Available Migration Objects

Note: If you Do Not Add any predecessor migration objects in this step, you can add more migration objects
to the project later. Please see section 4.3 Add More Migration Objects after Creating the Project (Optional)
of this document.

Note:. Neither in the SAP Fiori App Migrate your Data nor the application Model Your Migration Objects -
Migration Object Modeler it is possible to delete migration objects from a migration project.

© 2024 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.
Finally, click Create Project. It might take some time for the system to prepare your objects. The selected
pre-delivered SAP template migration objects are copied to your own project with all dependent rules and
definitions.

4.9. Add More Migration Objects after Creating the Project (Optional)
On the Migration Project screen, you can see the selected migration objects. If you want to add more objects
to your project, click Settings and follow the instruction below.

© 2024 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.
4.10. 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 New Migration Project screen specify under General Data the new name of your
migration project, and if necessary, adjust the connection to SAP Source System.

All migration objects, mapping tasks, and settings, are copied to the new migration project.
Choose Review.
Note: It is not possible to add additional migration objects when copying a project. However, after the copied
project has been created, you can add further migration objects. For more information, please see section
4.3 Add More Migration Objects after Creating the Project (Optional) of this document.
Note: Only the definition of the mapping tasks is copied to the new project. No mapping values, or fixed
values are copied.

© 2024 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.
Finally, click Copy Project. It might take some time for the system to prepare your objects. The selected
pre-delivered SAP template migration objects are copied to your own project with all dependent rules and
definitions.

4.11. Performing 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:

• multiple or all migration objects in your project at the same time.

Usually, the execution of the actions should be in the sequence as follows:

• Select data
• Prepare Mapping Tasks
• Mapping Tasks
• Simulate
• Migrate

You can also flexibly choose which steps you want to do next.

4.12.1. Selection

To select data from the source system, choose Select Data on the Migration Project Screen. As
mentioned, you can start the selection also for multiple or all migration objects if required. See section 4.5:
Performing Actions of this document.

On follow-on New Selection Screen choose Start Selection

You can monitor the selection process on the Monitoring Screen. If necessary, you can cancel the selection
process. See section 6.9 Canceling the Simulation/Migration in this document.

After the selection has been executed, the number of selected instances is displayed on the Migration
Project screen. In our case, ‘5086’ instances have been selected from the source system.

© 2024 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.
To obtain more information about the selected instances click on the ‘5086’ (number of instances). On the
Migration Objects Instances Screen you see all selected instances for this migration object. For more
information see section 6.4. Migration Object Instance Screen

For reselection, choose the action Select Data again and choose the selection according to your needs:

• New Selection: Deletes former selection and selects completely new.

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.

• Add Additional Instances: Adds new instances from the source system to already
selected instances; no update of already selected instances.

4.13. Prepare Mapping Tasks

The mapping tasks for each migration object need to be prepared before they can be processed. During
processing the mapping tasks are filled with proposal values: source value = target value.

Note: If you want to upload mapping values using Microsoft Excel (see section 4.8. Mapping Tasks (Specify
Mapping Values)), you can skip the activity Prepare Mapping Tasks.

• All Instances
• Custom selection (for detailed information see section 6.8a. Mass Processing – Migrate Data Directly
from SAP System

You can monitor the activity Prepare Mapping Tasks on the Monitoring screen. If necessary, you can
cancel the Prepare Mapping Tasks process.

4.14. Mapping Tasks (Specify Mapping Values)

On the Mapping Tasks Screen you can specify value mappings and transform values from the source
system to the target system.

4.14.1. Maintain and Confirm Values

There are 2 ways how you can maintain the mapping values:

• Directly in the migration cockpit

Select the mapping task in the Mapping Tasks screen and enter the needed target value.
o You can specify value mappings and transform values from the source system to the target
system.
o Search help provides existing values in the SAP S/4HANA Cloud, Public Edition target
system.

© 2024 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.
Note: The mapping tasks are 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(s) and upload
them back to project. During the upload you have various options, you can not only replace the existing
mapping values but also confirm them.

As a first step, you Download Mapping Templates or Download Values in the migration project.

These mapping values or templates can be revised locally in Excel. When these files are done reviewing,
you can upload the updated files to SAP S/4HANA migration cockpit.

As 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 them as values.

Note: The file(s) 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 file(s)) before uploading the
file(s) to another system.

4.14.2. Delete Mapping Values

You can delete mapping values easily by selecting them and clicking Delete Values.

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 the deleted values will appear.

Note: Fixed values cannot be deleted (only value mappings).

4.15. Simulation and Migration

On the Migration Project Screen, you can choose which migration object you want to simulate / migrate. As
with the previous activities, you can simulate / migrate individual, multiple or all migration objects at once.

If you prefer to simulate multiple or all migration objects at once you only have the option to simulate All
Instances in one step.

Use Simulate > All Instances with Errors if the previous simulation run has ended with errors, you can
simulate the instances with errors only.

Note: You can find tips on troubleshooting under chapter 5. Error Handling

• Migrate multiple or all migration objects

If you prefer to migrate multiple or all migration objects at once, you have the option to migrate All Instances
in one step or All Successfully Simulated Instances.

Use Migrate > All Instances with Errors if the previous migration run has ended with errors, you can
migrate the instances with errors only.

Note: You can find tips on troubleshooting under chapter 5. Error Handling

• Simulate / migrate single migration object

On the level of single migration object, you have the choose to simulate / migrate random 10%, random
500 items, all instances or via custom selection (for custom selection see chapter 6.8a. Mass Processing
– Migrate Data Directly from SAP System

© 2024 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.
You can monitor the activity Simulation / Migration process on the Monitoring Screen. If necessary, you
can cancel the Simulation / Migration process.

5. Error Handling

5.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 without checking the error and editing
your data.

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 message? (For any simulation/migration run)
3) Which error messages occurred for 1 instance? (For any simulation/migration run)
4) Which messages occurred during a particular simulation/migration run for a migration object?

Different Options for Checking Error Messages

5.2.1. Which messages occurred for each activity?

In Migration Project, select Monitoring. Select Activity as "All Activities” and Status as “Completed with
Errors” to see all error messages.

In Migration Project view, select relevant migration object, then click Messages. You can choose several
migration objects and toggle between the migration objects under the navigation bar.

© 2024 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.
On this screen, you can view the number of instances for each error message.
To generate a file with these error messages, click Download Details. You can select which columns to
include in the file. After the file is created, you can download it from the Monitoring section. Save it to your
local computer and open with Excel.

5.2.3. Which messages occurred for 1 instance?

To answer this question, check in the messages in the Migration Object Instances view. You can view the
messages for each instance by clicking on the instance number. However, if you have a large number of
instances, it makes sense to focus only on those with errors. Therefore, in this example, we click on the
number of errors (10) under the "Simulation" section.

You will see all the messages referring to this instance.

5.2.4. Which messages occurred during a simulation/migration run for a

migration object?

In Migration Project view, click on the name of the desired migration object to go to Migration Object view.

© 2024 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.
Select History tab to view the list of messages for the actions performed on the selected migration object.
Select Show Messages.

For all the mentioned error message screens, you can use:

• Free text search

• Grouping
• Sorting
• Downloading the file with the messages

6.1. Migration Objects in the Migration Object Screen

In the Migration Project, you can see the Predecessor Objects information. In the example below, there
are 3 migration objects that should be migrated before Product migration object. Please note, that if you did
not add the predecessor objects to your project, they will not be shown on the screen. The predecessor
objects will be offered to add by project creation. You can always check the information on the predecessors
in the Help Portal.

When you click on the name of the migration object (for example, Product), you will be redirected to the
Migration Object view. There you will find a link to the Help Portal for a specific migration object.

© 2024 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.
In the Migration Project screen, there is a progress bar that indicates the status of your single migration
object. You can drill down into numbers to get details on tables/tasks/instance level.

6.2. Migration Object Update

6.2.1. How to update a migration object for Migrate Data Using Staging Tables
approach?

After the upgrade to a new SAP S/4HANA Cloud release, you may receive a warning message that the
object update is required. That happens if you have added migration objects to the project before the
release upgrade.

If these migration objects require an update, you will get a warning message when performing an activity,
such as download templates. Click OK.

In this case, you will get a notification in the Migration Project view saying, for example, “Updates
available for 2 migration objects”. Click Display Objects.

Alternatively, you can check for the migration objects update by selecting the desired migration objects, for
example, Bank and then click Check for Updates.

6.2.2. What are the recommendations when the migration object has been
updated?

It is recommended to always use the latest version of the migration templates. If you have filled a template
file before the upgrade (update) to the new release, please use the release comparison. In here, you can
check if the changes to the migration templates affect your data.

6.2.3. How to update a migration object for Migrate Data Directly from SAP
System?

Like the staging approach, it may be necessary to update an object, for example, after an upgrade to a new
SAP S/4HANA Cloud release or a bug fix. Once a new version of a migration object is available, the status of
the object is updated accordingly.

There are two different statuses that indicate that you need to update your migration object to a new version:

• New Version Available: If the migration object has this status, it is recommended to update to the
new version. However, you can continue to use the migration object without the benefit from the
latest enhancements and/or bug fixes.

• New Mandatory Version Available: If the migration object has this status, it can no longer be used
and must be updated to a new version.

© 2024 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.
In distinction to the staging approach, it is not possible to update the migration object directly in the Migration
Cockpit. To update a migration object to a new version, you need to use the Model your Migration Objects
environment.

To do so, go the Implementation Activities app.

Follow following menu path afterwards: SAP Business Configuration > General Business Data >Data
Management > Data Migration > Data Migration to SAP S/4HANA from SAP > Model Your Migration
Objects

As soon as the application is open, enter your migration project (example see below) or the migration objects
for which you have to create a new version.

© 2024 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.
At the migration object level, the current Status and the Current Version as well as information on the New
Version are displayed under Version Details.

To add a new version of the migration object BANK to your project

1. Switch to Edit mode

2. Go to the Menu > Project > Create Migration Object > From Template

© 2024 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.
A new dialog box appears in which you must double-click on the migration object to be copied (1). Under
Specify new identifiers for the object within your project (optional) (2), you can assign a new Migration
Object Name and a Migration Object Technical Name for the new version of the migration object.

If you check the Version Details of the newly created migration object, you will notice that the Status has
been changed to Up to Date and the ID of the Current Version is displayed.

© 2024 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.
More information about all available statuses and in which case an update on a migration object is
recommended or required, see SAP Help Portal. See link: Migration Object Status

Details on the respective changes to the migration object can be found in the SAP Help Portal - Release
Comparison of Migration Objects (Direct Transfer). See link: Release Comparison - Direct Transfer

6.3. Migration Object Tables Screen

Migration Cockpit driven data operations for staging tables:

© 2024 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.
• Reset Table Settings will reset the current transfer status and 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. The system resets the number
of successfully simulated instances and the number of error instances to 0. The number of migrated
instances is not adjusted.
• Delete all records is only for deleting data from the staging tables. It is not designed to remove data
from the target system.
Note: already migrated instances will not be deleted from the staging tables. An error message will
appear in such case.
• Adjust Structure is designed to reflect the latest version of the migration object provided by SAP (for
example, if the staging tables were adjusted or dropped by error).

6.4. Migration Object Instance Screen

Note: The functionality described here is only available for the Migrate Data Directly from SAP System
approach.

If you click on Instances of the respective migration object on the Migration project screen, you will be
directed to the Migration Object Instances Screen.

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.

To have a look at the error messages select the instances for which you want to view message(s) and press
Message.

For more information about errors analysis see chapter 5. Error Handling

Single / individual instance processing

© 2024 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.
In addition, you can execute on single instances the actions prepare mapping tasks, simulate, migrate, or
exclude single / individual instances. Select the instance(s) on which you want to execute one of the
actions and press the button assigned to the relevant action.

Exclude / undo Exclude single /individual instances

It is possible to Exclude one or more instances from processing by selecting the entry(s) and pressing the
Exclude button.

Confirm in the Pop-Up with OK.

On the Migration Project Screen, you will now find one excluded item.

© 2024 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.
On the Migration Project Screen, you will now find one excluded item. The number of items to be migrated
(not started) has changed from “5086” to “5085”.

You can use the Action Undo Exclude to undo the Exclude.

Download list

To download a complete list of the instances choose Download All. You can adapt the list to your
preferences via the window that appears.

6.5. Detailed View on Migration Process

Note: The functionality described here is only available for the Migrate Data Directly from SAP System
approach.

You can use the Detailed View to get a comprehensive overview over the migration process.

The Detailed View provides you with

• 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

To navigate to the Detailed View Screen, choose Detailed View on Migration Project Screen. In the
Detailed View Screen, you can view all transfer options and transfer steps for a migration object.

The migration object Business Partner has one transfer option (one row) and one steps:

• simulate step1/ migrate step1 -> Create Business Partner

A detailed view of the migration process – More complex example

E.g. the migration object CO – Cost Center has one transfer option (one row) and two steps:

• simulate step1/ migrate step1 -> Create Cost Center

• simulate step2/ migrate step2 -> Create Cost Center Text

© 2024 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.
If you click on the arrow, a pop-up window opens. Here you can i.e., see which migration object instances
have been successfully processed and all instances that 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.

SAP Help Portal provides you with more information.

6.6. Migration Project Screen – Additional Features

• Monitoring – to view a log of all activities.

• Mapping tasks – to check all the mapping tasks for your project.

© 2024 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.
• Job management – to adjust the number of background jobs.
• Settings – to change the general settings, for example, adding new migration objects.
• Finish project – to finish the project and set a retention time.

6.7. Improving Performance with Job Management

In 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 “Migrate Data Using Staging Tables” approach, you can find more details in KBA 3066336 and KBA
3065607. Distributing migration objects across multiple projects does not improve performance.
See KBA 3065607

6.8. Using the Mass Processing Function

Steps:

1. Click on number of instances to get to detail level of migration object instances. Then choose Mass
Processing.
2. To start mass processing, select the desired action (for example Simulate) and proceed with Step 2.
3. Type in the fields of filter to select relevant instances then proceed with Step 3.
4. Review chosen instances before deletion, simulation, or migration.

© 2024 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.
© 2024 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.
6.8.1. Mass Processing – Migrate Data Directly from SAP System

The functionality differs slightly from the Staging Tables approach; therefore, this is described separately.
As for the Staging Tables approach the Mass Processing give you the possibility to trigger actions on
selected instances.

You have two option to starting Mass Processing:

• Selection a single migration object (custom selection)

The actions Prepare Mapping Tasks, Simulate and Migrate can be executed in custom selection (mass
processing). Mass processing give you the possibility to trigger the mentioned actions on selected
instances. Here showing using the mass processing for Prepare Mapping Tasks.

In 2nd step you have the option of filtering for the instances. Various filter options are available for this.

Review chosen instances before you execute the action.

• Using Mass Processing functionality on Migration Object Instance Screen

You can start the Mass Processing on Migration Object Instances Screen by choosing the Mass
Processing button.

© 2024 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.
To start Mass Processing select one of the corresponding actions (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.

Choose Start to start the mass processing.

© 2024 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.
6.9. Canceling the Simulation/Migration
Once simulation or migration is started, you will also have the option to cancel the corresponding job.

In the Migration Project view screen, click Monitoring. Click the Cancel.

6.10. Transporting Projects in Test- and Production System

Note: The functionality described here is only available for the Migrate Data Directly from SAP System
approach.

© 2024 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.
Migration projects can only be created in a development system. To be able to use these migration projects
in a test- or production-system you need to transport them using the app Export Customizing Transports.

You can find detailed information about all required steps in the SAP help portal.

6.11. Situation Handling

According to the blog Situation Handling – overview, “Situation Handling is SAP S/4HANA functionality
provided to bring certain circumstances (situations) to the attention of a relevant group of business users.
This allows for the proactive notification to the needed folks for a situation that has arisen.”

The Migrate Your Data – Migration Cockpit app uses Situation Handling to inform relevant business users
(for example, data migration experts) about matters that require their attention.

For this purpose, a predefined template is enabled that automatically informs the relevant business users
that the activities ‘Simulation’ and/or ‘Migration’ have been completed.

See example – after simulation is performed, one notification is displayed:

With following message:

Note: This notification can also be sent via e-mail, if configured in Settings.

© 2024 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.
As you select the notification by clicking ‘Just now’, you will be directed to the Data Migration Status app with
filtered results for the concerning migration project and object.

For further information, please see product assistance for Situation Handling.

7.1. Data Migration Status App

With this app, you can get an overview of your migration projects and migration objects after you've started
migrating data to your SAP S/4HANA Cloud system using the SAP S/4HANA migration cockpit staging
approach for one or more migration objects.

This app provides real-time information about:

• The number of successfully migrated data instances.

• The number of data instances that are simulated successfully.
• The number of data instances that failed to migrate or simulate.

To use the app, the business role SAP_BR_CONFIG_EXPERT_DATA_MIG must be assigned to your SAP
S/4HANA Cloud user.

7.1.1. Initial Screen (Migration Object Overview Screen)

On the initial screen of the app, the following information is displayed for each started migration objects:

1. An overview about all migration objects used across all migration projects.
2. Different searching criteria for your migration objects, which are Migration Period, Migration
Project, Object Name and Instance Status.
3. An overview of your instances (numbers of Migrated Successfully, Simulated Successfully,
Errors, the Total Instances of the migration object).
4. Your data migration progress by percentage with grey being Simulated Successfully, green being
Migrated Successfully, and red being migration Errors.
5. Extended Statistics show the number of data records provided per structure across all migrated
migration objects.
6. Possibility to Delete Instances (Failed and/or ready for import).
7. Possibility to export for local view in Microsoft Excel.

You can access the Data Instances screen by selecting the relevant migration object in the Initial Screen or

by clicking the arrow button ( ) at the end of each row.

In each Data Instances screen, following information is provided:

1. Source ID, which is the instance key you entered in the migration file/staging table.
2. Instance Status of the instance which can be migrated successfully, simulated successfully or error.
3. Description shows descriptive text of the instance you entered for the source instance (depends on
migration object).
4. For migrated successfully instance the Target ID, in SAP S/4HANA Cloud (new ID in SAP S/4HANA
Cloud system). The Target ID is displayed as a hyperlink. When you click the hyperlink, a dialog box
is displayed from which you can navigate directly to the corresponding application app.
Note: Additional authorizations may require to access these applications).

In addition, switching from Instanace view to Messages view will provide following information:

© 2024 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.
1. Different filter options for messages (all, error (error type only) and warning (warning type only)
2. Detailed view of each message + affected total instances.
3. Export instance and respective messages to Excel.
4. Total Instances gives technical information and a list of all instances concerning this message
(Source ID and project).

7.1.3. Extended Statistics

Extended Statistics showcases the number of instances per structure across all migrated objects.

Set extended statistics.

1. Possible to enable/disable logging of extended statistic per migration object.

2. Present the number of instances per structure and structure fields as category to explore across
migration object.

1. Selection on category (e.g., Sales Organization).

2. View of all value mappings for the selected category (Sales Organization).
3. Export to Excel.
4. View on corresponding instances and messages by category.

7.1.4. Audit

The Data Migration Status app provides audit functionality to help validate for your successful migrated
instances.

There are two options to select instances for auditing:

• Set Audit Status (manual assignment per instance).

• Manage Multiple Audit Status (mass assignment of instances).

Set Audit Status (manual assignment per instance) – there are 3 possible Audit Actions:

• Approved meaning instance was validated and is okay.

Manage Multiple Audit Status (mass assignment of instances)

• Assign Randomly for Auditing (select a quantity): In the dialog box, enter the quantity of instances
(unit) or define a specific percentage of successfully migrated instances for auditing.
• Download Spreadsheet gives you the option to download a spreadsheet of instances for local
auditing.
• Upload Spreadsheet gives you the option to upload the locally audited spreadsheet of your
instances.

© 2024 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.
By default, the audit authorizations are included in the standard business role template for data migration
(Configuration Expert - Data Migration, SAP_BR_CONFIG_EXPERT_DATA_MIG).

If you want to exclude the audit authorization from your general data migration user, you need to remove
the Data Migration - Audit (SAP_CA_BC_MIG_CNTNT_PC) business catalog from the role.

7.2. SAP S/4HANA Migration Object Modeler

You can enhance some of the migration object with the SAP S/4HANA migration object modeler or SAP Fiori
app “Model Your Migration Objects”. The scope is currently very limited, you can get the information on
which migration objects are available and how to use the app in the following presentation:
https://www.sap.com/documents/2022/07/9457651c-377e-0010-bca6-c68f7e60039b.html

The SAP S/4HANA migration object modeler is also available for the Migrate your data Directly from SAP
system approach via the SAP Fiori app “Implementation Activities”. You can get more information in the
SAP Help Portal and directly in the application if you choose the Information button.

7.3. Define Settings for Legacy Data Transfer

With this app, you can maintain the migration key date (usually equals the posting date) for financial objects
and/or check the legacy data transfer status of a data migration. Settings are controlled by company code.

To transfer your legacy financial transactional data properly, you need to maintain the migration key date on
which you want to complete all preparatory activities for each company code before the actual data transfer.

The migration key date allows you to:

• Fully complete all postings available up to this date in the source system.
• Reconcile and close the journals in the source system for the period.
• Extract source data and enter it into the 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) so that it will correspond with the
normal reconciliation cycle.

Please note that the migration key date is also used as the posting date when the legacy data is transferred
to your SAP S/4HANA system.

For additional information refer to SAP Knowledge Base Article 2754615

For each migration key, you can set following statuses:

• In Preparation meaning migration key date is still unclear (migration of transactional data is not
possible).
• Ongoing meaning the initial data transfer is required (migration of transactional data is possible).
• Completed is set after successfully completing the initial data transfer (migration of transactional
data is not possible).

For the following financial objects, the posting date is automatically derived by the predefined migration key
date for the corresponding company code that is maintained in the app:

• FI - Accounts payable open item

• FI - Accounts receivable open item
• FI - G/L account balance and open/line item
• Material inventory balance
• FI - Historical balance (deprecated) (migration key date is required to allow the migration of historical
balances only up until this initial transfer date)

Exception:

• For the financial object FI-CA - Open item, a field for posting date is available in the migration
template. The posting date is marked as mandatory in the template and must be provided for each
data record. The migration key date has no additional effect on the provided posting date.
• For the financial object Fixed asset - Master data, use the Make Company Code Settings - Asset
Accounting-Specific (FAA_CMP) app to specify the data transfer date, document type, and the
legacy data transfer status.

SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer
No ratings yet
SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer
79 pages
Production Order in SAP PP
No ratings yet
Production Order in SAP PP
13 pages
LSMW Logical Path & File Setup Guide
No ratings yet
LSMW Logical Path & File Setup Guide
4 pages
SCM680 Cross Application Processes in MM and SD Version 95 PDF
No ratings yet
SCM680 Cross Application Processes in MM and SD Version 95 PDF
3 pages
Loio S4
No ratings yet
Loio S4
266 pages
TCODE - XK01 Create Vendor Master
No ratings yet
TCODE - XK01 Create Vendor Master
10 pages
Mantenimiento Por Renovación Help - Sap
No ratings yet
Mantenimiento Por Renovación Help - Sap
6 pages
SAP MRP User Exit Guide
No ratings yet
SAP MRP User Exit Guide
2 pages
Material Type Configuration
No ratings yet
Material Type Configuration
5 pages
SAP MII 14 0 Configuration Guide PDF
0% (1)
SAP MII 14 0 Configuration Guide PDF
54 pages
MT940 & MT103 File Format Guide
No ratings yet
MT940 & MT103 File Format Guide
7 pages
SAP Combined Orders Guide
No ratings yet
SAP Combined Orders Guide
3 pages
How To Maintain Operating Concern in SAP
No ratings yet
How To Maintain Operating Concern in SAP
9 pages
S - ALR - 87013543 Report - Actual - Plan - Variance
No ratings yet
S - ALR - 87013543 Report - Actual - Plan - Variance
7 pages
Output Managment - OTP
No ratings yet
Output Managment - OTP
52 pages
SPRO
No ratings yet
SPRO
7 pages
Cockpit
100% (1)
Cockpit
52 pages
Automatic Creation of Asset - Equipment Master by Synchronization - S - 4HANA Plant Maintenance (Asset Management) - SAP Blogs
No ratings yet
Automatic Creation of Asset - Equipment Master by Synchronization - S - 4HANA Plant Maintenance (Asset Management) - SAP Blogs
8 pages
Fiori Roles
0% (1)
Fiori Roles
2 pages
Maintain Storage System - SPRO SAP Customizing Implementation Guide Cross
No ratings yet
Maintain Storage System - SPRO SAP Customizing Implementation Guide Cross
8 pages
84 Cómo Crear Una User Exit para Activos Fijos ANLU
No ratings yet
84 Cómo Crear Una User Exit para Activos Fijos ANLU
8 pages
The Subcon Process in SAP Purchasing Modules: Subcontracting Processing
No ratings yet
The Subcon Process in SAP Purchasing Modules: Subcontracting Processing
10 pages
IFCU-Material Document Posting: Murad Ahmed Shaikh
100% (1)
IFCU-Material Document Posting: Murad Ahmed Shaikh
7 pages
Model Config IBP
100% (1)
Model Config IBP
434 pages
SAP PS Training Manual for O&G Projects
No ratings yet
SAP PS Training Manual for O&G Projects
65 pages
Archiving Material Master - Some Simple Steps
100% (1)
Archiving Material Master - Some Simple Steps
22 pages
Archiving PP Boms (PP BD Bom)
No ratings yet
Archiving PP Boms (PP BD Bom)
8 pages
Enhancing Standard Programs Quickly and Easily Via Business Add-Ins (Badis)
No ratings yet
Enhancing Standard Programs Quickly and Easily Via Business Add-Ins (Badis)
11 pages
41z S4hana2021 BPD en Us
No ratings yet
41z S4hana2021 BPD en Us
22 pages
Transaction Variant Creation Document
No ratings yet
Transaction Variant Creation Document
3 pages
Rebate Process Configuration - SAP Blogs
No ratings yet
Rebate Process Configuration - SAP Blogs
18 pages
SAP PM BAPI and IDoc Functions List
No ratings yet
SAP PM BAPI and IDoc Functions List
2 pages
How To Find Email Address of SAP USER ID THE SMART WAY
No ratings yet
How To Find Email Address of SAP USER ID THE SMART WAY
6 pages
SAP Mill Products: "DIMP Run Simple Mill Industries"
No ratings yet
SAP Mill Products: "DIMP Run Simple Mill Industries"
7 pages
Combined Production Order Processing (DIMP) - SAP Blogs
No ratings yet
Combined Production Order Processing (DIMP) - SAP Blogs
18 pages
Maintenance Budgeting Using Maintenance Order/Internal Orders
No ratings yet
Maintenance Budgeting Using Maintenance Order/Internal Orders
7 pages
BM302, BM303, BM304
No ratings yet
BM302, BM303, BM304
1 page
SAP Warranty Management Overview
No ratings yet
SAP Warranty Management Overview
27 pages
Apps For Maintenance Management-Pdfdownload
No ratings yet
Apps For Maintenance Management-Pdfdownload
242 pages
WF-BATCH and SAP - WFRT Authorizations
No ratings yet
WF-BATCH and SAP - WFRT Authorizations
2 pages
Order Split
No ratings yet
Order Split
9 pages
SAP COPC Config T-Codes
No ratings yet
SAP COPC Config T-Codes
1 page
Outgoing Appointment Scheduling Interface
100% (1)
Outgoing Appointment Scheduling Interface
53 pages
9000 BBP V3.0 - Sil - MM - 16.04.20
No ratings yet
9000 BBP V3.0 - Sil - MM - 16.04.20
59 pages
METHOD If Ex Badi v56k Ibs Change Outbound
No ratings yet
METHOD If Ex Badi v56k Ibs Change Outbound
10 pages
How To Use SAP Scripting
No ratings yet
How To Use SAP Scripting
4 pages
SAP Query Using ABAP: Submitted by Kiran Subramaniam S
No ratings yet
SAP Query Using ABAP: Submitted by Kiran Subramaniam S
10 pages
Account Maintainance Posting
No ratings yet
Account Maintainance Posting
5 pages
SAP Blueprint for GPIL Management
100% (1)
SAP Blueprint for GPIL Management
49 pages
SAP Change Pointer Guide
No ratings yet
SAP Change Pointer Guide
4 pages
Prerequisites: PLM210 Master Data Configuration in SAP Project System
No ratings yet
Prerequisites: PLM210 Master Data Configuration in SAP Project System
1 page
Sap Gui For Java
No ratings yet
Sap Gui For Java
64 pages
Sapnote 0000116042 Memory Low
No ratings yet
Sapnote 0000116042 Memory Low
2 pages
Activation of SAP Best Practices With Solution Builder
No ratings yet
Activation of SAP Best Practices With Solution Builder
28 pages
SAP Retail Logistics Codes
No ratings yet
SAP Retail Logistics Codes
1 page
SAP S - 4HANA Cloud, Private Edition - Onprem - Migration Cockpit - Cookbook
No ratings yet
SAP S - 4HANA Cloud, Private Edition - Onprem - Migration Cockpit - Cookbook
91 pages
SAP S - 4HANA Migration Cockpit - Cookbook - Private Edition
No ratings yet
SAP S - 4HANA Migration Cockpit - Cookbook - Private Edition
94 pages
Sample Book Data Migration For SAP SAP Press
100% (1)
Sample Book Data Migration For SAP SAP Press
24 pages
GU - SAP S4 HANA - The Migration Process
No ratings yet
GU - SAP S4 HANA - The Migration Process
33 pages
SAP S/4HANA Cloud Data Migration
No ratings yet
SAP S/4HANA Cloud Data Migration
37 pages
Intern Certificate - Juejun - Huo
No ratings yet
Intern Certificate - Juejun - Huo
1 page
Csiloader Update
No ratings yet
Csiloader Update
6 pages
CR R Wang Trends Why The Cloud Best Delivers Innovation Final
No ratings yet
CR R Wang Trends Why The Cloud Best Delivers Innovation Final
12 pages
Book1 (AutoRecovered)
No ratings yet
Book1 (AutoRecovered)
3 pages
Study Guide: Exam PL-300: Microsoft Power BI Data Analyst
0% (1)
Study Guide: Exam PL-300: Microsoft Power BI Data Analyst
8 pages
What Is DBMS - Application, Types, Example, Advantages
No ratings yet
What Is DBMS - Application, Types, Example, Advantages
7 pages
Module 11 Maintaining InfoSec 211
No ratings yet
Module 11 Maintaining InfoSec 211
57 pages
How To Configuring SAP HANA Traces v178
No ratings yet
How To Configuring SAP HANA Traces v178
17 pages
Lab 11 SQL OUTER JOINS LEFT and RIGHT JOIN
No ratings yet
Lab 11 SQL OUTER JOINS LEFT and RIGHT JOIN
9 pages
Library Automation and Networking: December 2019
No ratings yet
Library Automation and Networking: December 2019
53 pages
System Design
No ratings yet
System Design
56 pages
JSP Example To Connect To MS SQL Database and Retrieve Records
No ratings yet
JSP Example To Connect To MS SQL Database and Retrieve Records
12 pages
Data Analyst - Pune
No ratings yet
Data Analyst - Pune
2 pages
ETL DataStage Developer Profile
No ratings yet
ETL DataStage Developer Profile
4 pages
GSEB Solutions Class 12 Statistics Part 1 Chapter 2 Linear Corre
No ratings yet
GSEB Solutions Class 12 Statistics Part 1 Chapter 2 Linear Corre
43 pages
T5 DNS
No ratings yet
T5 DNS
8 pages
Bda End Sem
No ratings yet
Bda End Sem
6 pages
WebLogic JMS Setup Guide
No ratings yet
WebLogic JMS Setup Guide
55 pages
Unstructured Data Classification Guide
No ratings yet
Unstructured Data Classification Guide
5 pages
Informix Instance Setup Guide
No ratings yet
Informix Instance Setup Guide
2 pages
SQLPDF
No ratings yet
SQLPDF
77 pages
Linux OSX and Windows Commands
No ratings yet
Linux OSX and Windows Commands
1 page
137BQ122019
No ratings yet
137BQ122019
2 pages
National University (BBA (Hon's) 2nd Year Exam-2023 (Will Be Held-2024/25) ) Subject Code: 222509 Subject Name: Business Statistics
No ratings yet
National University (BBA (Hon's) 2nd Year Exam-2023 (Will Be Held-2024/25) ) Subject Code: 222509 Subject Name: Business Statistics
17 pages
Materialized View
No ratings yet
Materialized View
29 pages
Features SQL Server Versions
No ratings yet
Features SQL Server Versions
6 pages
Xii Cs Preboard QP Set A Cbessc
No ratings yet
Xii Cs Preboard QP Set A Cbessc
8 pages
Dsa Heap
No ratings yet
Dsa Heap
12 pages
File Organisation and Access (Serial, Sequential and Direct) - 1
No ratings yet
File Organisation and Access (Serial, Sequential and Direct) - 1
5 pages
Partitioning and Relative Page Numbering On DB2 12
No ratings yet
Partitioning and Relative Page Numbering On DB2 12
30 pages
Only Quat
No ratings yet
Only Quat
8 pages
WIA1002 DS-Assignment-Topic2 PDF
No ratings yet
WIA1002 DS-Assignment-Topic2 PDF
11 pages
Expense Tracker Specs
No ratings yet
Expense Tracker Specs
21 pages
MAD Unit 2
No ratings yet
MAD Unit 2
14 pages