11/2/24, 10:45 AM

Data Migration
Generated on: 2024-11-02 10:45:49 GMT+0000

SAP S/4HANA | 2023 Latest

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/29193bf0ebdd4583930b2176cb993268?locale=en-

US&state=PRODUCTION&version=2023.002

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not reflect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
 11/2/24, 10:45 AM

Data Migration
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.

Landing Page
The following image map gives you an overview of useful links to resources about data migration. Depending on your level of
expertise, go to the category that is relevant for you. Choose an element to follow the link to the resource. As a beginner, we
recommend that you start with the material linked in Getting Started.

Please note that image maps are not interactive in PDF output.

Quick Info

Use these SAP Help Portal aliases to access the following sections of our product assistance:

Type this in your browser... To jump to...

http://help.sap.com/S4_OP_DM this very topic: Data Migration

http://help.sap.com/S4_OP_MO the entry topic: Available Migration Objects

http://help.sap.com/S4_OP_DM_STATUS the entry topic: Data Migration Status

Note Analyzer

We recommend that you regularly check if all correction notes for the proper use of the SAP S/4HANA migration cockpit are
implemented, including the installation of add-on DMIS and the respective components in SAP S/4HANA. To check, run
transaction CNV_NA_MC. Also see SAP Note 3016862 .

License Note SAP S/4HANA

This is custom documentation. For more information, please visit the SAP Help Portal 2
 11/2/24, 10:45 AM
In addition to the standard options of using either a full-use version of SAP HANA (i.e. SAP HANA, enterprise edition) or the SAP
tools provided as Runtime Software with SAP HANA, runtime edition, it is possible to utilize a 3rd party ETL tool to populate the
staging tables for the SAP S/4HANA migration cockpit.

In this case, the staging tables will be created by the SAP S/4HANA migration cockpit in a dedicated schema, either in the same
database tenant where SAP S/4HANA is installed or a separate dedicated database tenant. Such a schema can then be configured
as a remote database connection enabling connectivity and filled by a 3rd party ETL tool solely for the purpose of consumption by
the S/4HANA migration cockpit.

For the avoidance of doubt, the tables may not be used for any kind of processing by SAP HANA outside of SAP S/4HANA
migration cockpit, including, but not limited to, calculation view modeling, custom SAP HANA Extended Application Services (XS)
applications, and other processing by SAP HANA engines. Furthermore, the use of such 3rd party tools to populate staging tables
shall be limited to the timeframe during which a migration project is active in the SAP S/4HANA system installed in the same SAP
HANA database tenant.

Migrate Your Data - Migration Cockpit

App ID: F3473

With this 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 do the following:

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.

Situation Handling
This app uses Situation Handling, which automatically informs users responsible about matters that require their attention. For
more information, see Situation Handling for Data Migration.

Related Information
Migrate Your Data in the SAP Fiori Apps Reference Library.

See the Data Migration landing page.

See the Data Migration to SAP S/4HANA from Staging (2Q2 ) test script.

Quick Info
Use these SAP Help Portal aliases to access the following sections of our product assistance:

This is custom documentation. For more information, please visit the SAP Help Portal 3
 11/2/24, 10:45 AM

Type this in your browser... To jump to...

http://help.sap.com/S4_OP_DM the entry topic: Data Migration

http://help.sap.com/S4_OP_MO the entry topic: Available Migration Objects

http://help.sap.com/S4_OP_DM_STATUS the entry topic: Data Migration Status

Supported Device Types

Desktop

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

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

If you use the option Remote SAP HANA Database Schema, you specify the relevant connection to a remote SAP HANA system
and the SAP S/4HANA migration cockpit will generate the staging tables there.

 Note
Important information regarding the processing of personal data

Customers are responsible for the data in their systems, and also responsible for complying with local laws regarding data
protection and privacy. SAP provide tools to support with this, such as data retention and read access logging.

Data protection legislation may require that personal data is deleted once the data has served its originally defined purpose
and is also no longer subject to additional legal data retention requirements.

Data protection legislation may require that personal data is deleted once the data has no longer any purpose and is also no
longer subject to additional legal data retention requirements. If data protection legislation is applicable in your case, then
migrating personal data which should have been deleted could be interpreted as the processing of personal data without any
legally justified purpose.

In this case, it is crucial to ensure that such personal data is not migrated to the target SAP S/4HANA system.

Roles and Authorizations

To transfer data using the SAP S/4HANA migration cockpit, a user with the role SAP_CA_DMC_MC_USER is required in the SAP
S/4HANA system. This user must also have the role SAP_BR_CONFIG_EXPERT_DATA_MIG for the front-end server.

This is custom documentation. For more information, please visit the SAP Help Portal 4
 11/2/24, 10:45 AM
To use the SAP S/4HANA migration object modeler (transaction LTMOM), role SAP_CA_DMC_MC_DEVELOPER is required in the
SAP S/4HANA system.

In addition, the corresponding role for each migration object is also required.

The Migration Process

The diagram below illustrates the steps involved in the migration process.

A more detailed description of the process is outlined below:

1. In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data -
Migration Cockpit app in the Fiori Launchpad.

2. You create a migration project and select the migration objects that are relevant for your project. Migration objects are
delivered by SAP and describe how to migrate data from the source system (which tables are needed and the relationships
between the tables) to SAP S/4HANA.

Note that you typically first create a project in a test system which is a copy of the production SAP S/4HANA system. For
each new test transfer, you create a new migration project that includes any corrections or refinements identified in the
previous test. When you are finally ready to transfer your data to the production SAP S/4HANA system, you can create a
project in the production system.

3. The system automatically creates staging tables for each migration object in the project. You need to decide how to fill
these staging tables with data. You can use template files, or you can fill the staging tables by using your preferred tools (for
example SAP Data Services).

4. If you use template files to populate the staging tables with data, you download a template file for a migration object and
enter the data to be migrated in the file. You then upload the completed file, and the system automatically transfers the
contents of the file to the staging tables.

5. You prepare the staging tables for each migration object so that they can be used to transfer data to SAP S/4HANA.

6. For each migration object, you process any open mapping tasks.

There are mapping tasks associated with migration objects that must be processed before the migration can proceed.
Examples of mapping tasks include Value Mapping tasks (where you specify target values for corresponding source values)
and Fixed Value tasks (where you set default values for target fields).

7. Optional: You simulate the transfer of data to the target SAP S/4HANA system.

8. You migrate the data for the migration object to the target SAP S/4HANA system.

9. Optional: You use correction files to correct any errors that may have occurred during the migration.

This is custom documentation. For more information, please visit the SAP Help Portal 5
 11/2/24, 10:45 AM

Creating Migration Projects

Context

You use migration projects to facilitate the transfer of data from a source system to SAP S/4HANA

Typically, you first create a project in a test system which is a copy of the SAP S/4HANA production system. The more the data in
the test system resembles the data in the production system, the more precise your test will be.. You use a migration project to
specify the data that you want to transfer, and to monitor the status of the migration.

. You use a migration project to specify the dataFor each test transfer, you create a new migration project in the test system that
includes any corrections or refinements identified in the previous test. When you are finally ready to transfer your data to the SAP
S/4HANA production system, you create a project in the production system.

To create a migration project, proceed as follows:

1. In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data app in
the Fiori Launchpad.

2. Choose Create and then Migrate Data Using Staging Tables. The system displays the New Migration Project screen.
Creating a project involves three steps. In the first step you specify general data for the project. In the second step you
specify a development package for your project. Finally, in the third step, you select the relevant migration objects.

3. Under General Data, you specify the following information:

Name

The name of the project.

Database Connection

If you are using files to fill the staging tables with data, choose the option Local SAP S/4HANA Database in the
Database Connection field. The system will generate the staging tables in the internal schema of the SAP S/4HANA
system. Note that you could also fill these staging tables with data by using your preferred tools if required.

If you want to fill the staging tables with data in a remote SAP HANA database, select the option Remote SAP HANA
Database and enter a valid database connection to relevant system by choosing one from the search help list. The
system will generate the staging tables in the schema of the remote database. You need to create a database
connection in transaction DBCO, and manually add it to table DMC_C_WL_DBCO_OP in the SAP S/4HANA system
using transaction SM30. Note that for this option, you can use files or your preferred tools to fill the staging tables
with data.

4. Choose the button Step 2.

5. Under Development Package, you specify a development package for your project. If you are unsure about which option to
use, we recommend contacting your system administrator.

 Note
Note that if you use a local development package ($TMP), or a development package that does not have the prefix Y or
Z, then it is not possible to transport the project to another system in your system landscape using the Change and
Transport System (CTS).

6. Choose the button Step 3.

7. Under Migration Objects, the system displays a list of available migration objects. Select the migration objects that are
relevant for your project.

This is custom documentation. For more information, please visit the SAP Help Portal 6
 11/2/24, 10:45 AM
You can view the following information for the listed migration objects:

Name

The migration object name.

Predecessor

Documentation

To view detailed documentation for the migration object, select the Documentation link.

8. Review your settings, and choose Create Project to create your project.

Copying Migration Projects

Context
You can create a new project that is a copy of an existing project, that contains all the migration objects, mapping tasks and
settings, including any custom changes. You specify a new name for the project, and can adjust the database connection and the
development package. Note that only the definition of the mapping tasks are copied to the new project.

Copying a project can make sense in the following situations:

Using templates

You can create one migration project that will act as template for other migration projects. You can then copy this project
multiple times to manage the migration in an efficient way. For example, you might copy the leading template project to a
new migration project which you would use to migrate data for a specific set of companies. You could then copy the leading
template project to another migration project which you would use to migrate data for the remaining companies.

Reusing successful projects

You want to reuse the settings of a successful project. For example, you may have successfully migrated some companies
in a migration project. Later you need to migrate data which requires a similar migration project setup. You can simply copy
the successful project and reuse it.

Creating similar migration projects in a test environment

You want to create similar migration projects in a test environment. You can copy your migration project and then just
adjust certain settings of the newly created projects for test purposes.

Transporting a project to a different system

You can copy a project so that it can be transported to another system. For example, a project might use a local
development package that cannot be transported to another system. You can copy this project and assign a development
package that can be transported. You can then transport this newly created project to a different system.

 Note
You can ignore updates for a copied migration object by using the option Ignore Updates in transaction LTMOM.

Procedure
1. On the Migration Project screen, select the project that you want to copy.

2. Choose the Copy button. The system displays the New Migration Project screen.

This is custom documentation. For more information, please visit the SAP Help Portal 7
 11/2/24, 10:45 AM
3. Specify a name for the project. If required, you can also change the database connection.

4. Choose the button Step 2.

5. Under Development Package, you can specify a different development package if required.

6. Choose the button Step 3.

7. Under Migration Objects, the system displays the migration objects that will be copied to the new project. Note that it is
not possible to add additional objects, or to remove any migration objects in this step. If required, you can add additional
migration objects to the project once it has been created. Note that any migration objects that have the status Not Ready
for Processing will not be copied to the new project.

8. Review your settings and choose Create Project to create your project.

Using a Project in a Different Client

By default, you can only view and edit projects in the client where they were created. It is only possible to use a project in one client
in the system. If you want to view and edit a project in a different client, you need to use the SAP S/4HANA migration object
modeler (transaction LTMOM) to change the settings for a project so that it can be used in that client. To do this, open the relevant
project and choose GoTo Use Project in Different Client .

Note that all mapping tasks are deleted. This means that you need to download the mapping tasks before you proceed. You can
then upload the mapping tasks in the new client.

Example
You create a migration project in client 100. You want to edit the project in client 200. In client 200, you open the project in
transaction LTMOM and choose GoTo Use Project in Different Client . In the SAP S/4HANA migration cockpit, you can now
view and edit the project in client 200. It is no longer possible to use the project in client 100.

Transferring Projects from One System to Another

If you need to transport content from one system to another, you can use the Migration Object Modeler (transaction LTMOM) to
add the relevant content to a transport request. You can add projects, migration objects, and rules to a transport request. Note
that only the definition of a rule is added to a transport request. No values, for example mapping values, are included.

If you add a project to a transport request, then all migration objects and rules in the project will also be added to the transport
request. If you add a migration object to a transport request, then all rules that are used by the migration object will also be added
to the transport request.

Detailed documentation for the SAP S/4HANA migration object modeler can be accessed directly from transaction LTMOM. For
more information about this process, refer to this documentation.

 Note
A development package is required to transport a project to another system in your system landscape. If a project is assigned
to a local development package ($TMP), it is not possible to transport the project to another system in your system landscape.
If required, you can use a report to assign a development package to a migration project. For more information, see SAP Note
3119168 .

 Note
To transport a project to another system in your system landscape, the project must be created in a system that has specific
settings. For more information, see SAP Note 3104790 .

This is custom documentation. For more information, please visit the SAP Help Portal 8
 11/2/24, 10:45 AM

The Migration Project Screen

When you open a migration project, the system displays the Migration Project screen. On the Migration Project screen, you
trigger the steps that are required to transfer the data for each migration object to the target SAP S/4HANA system.

For each migration object, these steps are:

1. Uploading a template file for a migration object (if using template files to fill the staging tables with data).

2. Preparing the staging tables.

3. Processing any open mapping tasks.

4. Simulating the migration to the target SAP S/4HANA system (optional).

5. Migrating the data for the migration object to the target SAP S/4HANA system.

These steps are relevant for each migration object that is part of your project. If a migration object has a predecessor object, the
predecessor object must be processed first. In the Migration Object column, you can view whether a migration object has a
predecessor object.

The Migration Project screen contains the following columns:

Migration Object

In this column, you can view the name of the migration object. You can also view any predecessor objects. To view detailed
information about a migration object, click a migration object name in this column. The system displays the Migration
Object screen.

Data

In this column, you can view the number of staging tables associated with each migration object. You can also view the
number of migration object instances that exist in the staging tables.

Mapping Tasks

In this column, you can view the number of open and completed mapping tasks for each migration object.

Simulation

In this column, you can view the number of migration object instances that have been simulated successfully, and the
number of instances for which errors exist.

Migration

In this column, you can view the number of migration object instances that still have to be migrated to the to the target SAP
S/4HANA system, as well as the number of migration object instances that have been migrated successfully, and the
number of instances for which errors exist.

Migration Progress

In this column, you can view the status of the migration. If the migration has not started for a migration object, the text
Migration Not Started is displayed. If the migration has started for a migration object, you can view the following
percentage values:

Percentage of instances migrated successfully

Percentage of instances with errors

Percentage of instances not yet started

This is custom documentation. For more information, please visit the SAP Help Portal 9
 11/2/24, 10:45 AM
Action

In this column, you can trigger an action for a migration object. For example, you can upload a file or start the simulation
process.

Additional Information

Monitoring

To view a log of all activities, choose the Monitoring button. The system displays the Monitoring screen. You can view the active
activities (for example Migration Started) and completed activities (for example Migration Completed).

Settings

You can view the current settings for your project at any time by choosing the Settings button. The system displays the Project
Settings screen, where you can also change settings for the project, for example you can add additional migration objects. For
more information, see Project Settings.

Mapping Tasks

You can view a list of all mapping tasks for all the migration objects in your project. For more information about tasks, see Mapping
Tasks.

Job Management

To adjust the maximum number of background jobs that are used for the migration project, choose the Job Management button.

Finishing a Project

When you have finished your migration project, you can set the status of the project to Finished. When you set the status of a
project to Finished, no further changes are possible. However, you can still view the project. To set the status of a project to
Finished, choose the Finish button.

When you set the status of a project to Finished, you can specify a data retention period. The retention period is the length of time
(in days) that the project and all associated data is kept in the system after you have set the status of the project to Finished. To do
this, set the option Data Retention Period to On. The data will be deleted from the SAP S/4HANA system when the data retention
time expires. If you set the option Data Retention Period to Off, then the project and all associated data will be kept in the system
indefinitely. If required, you can change the retention time for finished projects. To do this, open the relevant project and choose
the Settings button. You can find the settings for retention time on the Technical Information tab.

Project Settings
You can view the current settings for your project by choosing the Settings button. The system displays the Project Settings
screen, where you can view the following information:

Migration Project Name

If required, you can change the name of the migration project. To this, choose the Edit button, and enter a new name in the
Name field.

Migration Approach

Database Connection

In addition, you can view the following sections:

This is custom documentation. For more information, please visit the SAP Help Portal 10
 11/2/24, 10:45 AM
Migration Objects

Under Migration Objects, you can view the migration objects in the project. If required, you can add additional migration
objects to your project. To do this, choose the Edit button, select the relevant objects and choose Save.

History

Under History, you can view the different actions for the project (for example Project Created). You can view the user that
started the action as well as the start time and date and the end time and date. You can also view the log for each action.

CSV File Options

Under CSV File Options, you can view information about how the system processes CSV files. You can also adjust certain
settings. For more information, see CSV File Options.

Technical Information

Under Technical Information, you can view the following information:

Data Retention Period

The retention period is the length of time (in days) that the project and all associated data is kept in the system
after you have set the status of the project to Finished. If required, you can change the retention time for finished
projects.

Support Information

You can also view general technical information about the project such as the object ID. If you need to contact SAP
for support, this information might be required.

Job Management
On the Job Management screen, you can adjust the maximum number of background jobs that are used for your project. The
default number of background jobs for a project is 15. If required, you can also adjust the number of background jobs for specific
migration objects. Note that if an activity has already started for a migration object, then increasing or decreasing the number of
jobs for the migration object will have no effect on that activity.

Example 1

You specify 5 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify 1
background job for migration object A and 1 job for migration object B. Result: 1 job will run in parallel to process migration object
A, and 1 job will run in parallel to process migration object B. The additional jobs specified for your project are not used in this case.

Example 2

You specify 8 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify
8 background jobs for migration object A and 5 jobs for migration object B. Result: A maximum of 8 jobs will be used for object A,
and a maximum of 5 jobs will be used for object B. The overall number of active background jobs for the project will not exceed 8
jobs.

Example 3

You specify 3 background job for your project (in the Maximum Number of Background Jobs for Project field). You then specify 3
background jobs for migration object A and 3 jobs for migration object B. Result: 3 jobs will process migration object A and
migration object B in a round robin procedure.

This is custom documentation. For more information, please visit the SAP Help Portal 11
 11/2/24, 10:45 AM

The Migration Object Screen

The SAP S/4HANA migration cockpit uses migration objects to transfer data to the target SAP S/4HANA system. On the
Migration Project screen, the system displays the migration objects for your project. To get detailed information about a migration
object, click a migration object name in the Migration Object column. The system displays the Migration Object screen, where you
can view the following information:

Documentation

You can view detailed information about the migration object.

Views

You can view the active view for the migration object.

The view determines the visible fields for a migration object. There is a standard scope for SAP S/4HANA. There is also an
adjusted scope that uses your business configuration settings to reduce the number of visible fields. You can also define a
custom scope in transaction LTMOM.

Table Structure

You can view the relevant staging tables for the migration object.

History

You can view a history of the events for the migration object. Examples of events include Simulation Started or Simulation
Completed. You can also view a log for the events. To do this, choose the Show Messages button. The system displays the
Messages screen, where you can view messages for each event.

Dependencies

You view whether the migration object has any dependent migration objects. A migration object can have predecessor
objects (objects which must be processed before the migration object) and successor objects (objects which must be
processed after the migration object).

Technical Information

Under Technical Information, you can view general technical information about the migration object such as the object ID.
If you need to contact SAP for support, this information might be required.

The following features are also available:

View Mapping Tasks

You can navigate to the mapping tasks for a migration object by choosing the Mapping Tasks button.

View Migration Object Instances

To view the migration object instances in the staging tables, choose the Instances button.

Check for Updates

To check whether an update is available for a migration object, choose the Check for Updates button.

Update Migration Object

If an update is available for a migration object, you can update the object by choosing the Update button.

Check whether Custom fields exist

To check whether custom fields exist for a migration object, choose the Check for Custom fields button. If custom fields
exist, the system updates the migration object with the custom fields.

This is custom documentation. For more information, please visit the SAP Help Portal 12
 11/2/24, 10:45 AM

Viewing Messages
You can view the messages for the migration objects in a project at any time. On the Migration Project screen, select the relevant
migration objects and choose the Messages button. The system displays the Migration Object, Messages screen where you can
view the messages for the selected migration objects. You can view the number of migration object instances that are relevant for
each message and navigate directly to these migration object instances.

 Note
The retention period for messages is 180 days. Messages will be permanently deleted after this time.

By default, the system displays all messages that exist for the selected migration objects. You can restrict the messages to specific
migration objects if required.

You can use the following filter options to view the messages that you are interested in:

Action

The relevant action, for example Simulation or Migration. You can select an action to view the messages for that action.

Message Type

You can select a message type to view the messages of that message type. The following message types are possible:

Error

Error messages need to be processed before you can continue with the simulation or migration.

Warning

We recommend analyzing any warning messages to determine whether they are relevant for your migration project.

Success

Messages that indicate that a certain step was completed successfully. No further action is required.

Information

Messages that provide information about a certain step. No further action is required.

The system displays the following information for each message:

Type

Message

Action

The relevant action, for example Simulation or Migration.

Instances

In this column, the system displays the number of migration object instances that are relevant for the message. To view the
migration object instances, choose the number in this column.

Viewing Messages for Specific Migration Object Instances

On the Migration Project screen, you can view the number of migration object instances that have been simulated and migrated
successfully and the number of instances for which errors exist.

This is custom documentation. For more information, please visit the SAP Help Portal 13
 11/2/24, 10:45 AM
In the Simulation and Migration columns, the system displays the number of errors for a migration object. If you click this number,
the system displays the migration object instances that contain errors. Select the migration object instance that you want to
analyze, and choose the Messages button

You can view the following information for each message:

Type

The message type, for example Error or Warning.

Message

The message short text

Properties

The system displays the relevant migration object and also the event when the message occurred, for example during the
selection process or during the migration.

Date and Time

The date and time when the message occurred.

Downloading Template Files

You can use template files to fill the staging tables with data. Alternatively, you can fill the staging tables with data by using your
preferred tools (for example SAP Data Services).

Using XML template files is the default option for filling the staging tables with data. We recommend using XML template files for
the following reasons:

Using Microsoft Excel is a stable option for entering and editing values manually.

All data is contained in one file.

The XML template file contains detailed information about the relevant data structures as well as instructions about how to
enter data in the file.

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, for example if you are automating the extraction of data from database tables, CSV files
may be easier to create using database or other file handling tools. We recommend exercising caution when using CSV files for the
following reasons:

You need to use a separate CSV file for each data structure.

There is no built-in protection for data formats.

Downloading XML Template Files

Context

If you are using XML template files to populate the staging tables with data, you need download an XML template file for a
migration object and enter the data to be migrated in the file.

Procedure
This is custom documentation. For more information, please visit the SAP Help Portal 14
 11/2/24, 10:45 AM
1. On the Migration Project screen, select the relevant migration object and choose the Download Template button and then
choose the option Download XML File. You can select multiple migration objects if required.

2. The system creates a zip file that contains the template files.

3. Save the zip file locally and open the files using Microsoft Excel.

Downloading CSV Template Files

Context
If you are using CSV template files to populate the staging tables with data, you need to download the CSV template files for the
relevant migration object and enter the data to be migrated in the files.

 Note
CSV files provide a more flexible approach for uploading data. For example, you can remove columns, and change the order of
the columns. However, 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. For more information, see Downloading Template
Files.

Procedure
1. On the Migration Project screen, select the relevant migration object and choose the Download Template button and then
choose the option Download CSV Files. You can select multiple migration objects if required.

2. The system creates a zip file that contains the CSV template files. In the zip file, there is 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, for the data structure S_BNKA, the corresponding CSV template file in the zip file is
S_BNKA#FreeText.csv. For more information about naming your CSV files, see Naming Convention for CSV Files.

If the technical name of a data structure contains the forward slash character ("/"), the forward slash character will be
replaced with the characters "%2f" when you download the file.

3. Save the zip file locally and extract the files. You can then open the files using a text editor or your preferred application.

Using a spreadsheet application to open CSV files may result in formatting issues, for example leading zeros may be
deleted.

Naming Convention for CSV Files

When you download CSV files for a migration object, the system creates a zip file that contains the CSV template files. In the zip
file, there is 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, for the data structure S_BNKA, the corresponding CSV template file in the zip file is S_BNKA#FreeText.csv

This is custom documentation. For more information, please visit the SAP Help Portal 15
 11/2/24, 10:45 AM
If required, you can replace the text "FreeText" with your own text, but it is not necessary to do so. If you add your own text, it must
be preceded by the hash symbol (#). For example, S_BNKA#Test1.csv

You can also remove the string "#FreeText".

 Note
Mandatory data structures will also contain the suffix Mandatory.

 Note
If your CSV file names follow the naming convention <data structure name>#<optional user input>.csv, the
system will automatically map the CSV files to the relevant data structures. For more information, see Mapping a CSV File to a
Data Structure.

Filling XML Template Files with Data

Using XML template files is the default option for filling the staging tables with data. We recommend using XML template files for
the following reasons:

Using Microsoft Excel is a stable option for entering and editing values manually.

All data is contained in one file.

The XML template file contains detailed information about the relevant data structures as well as instructions about how to
enter data in the file.

Additional Information About XML Template Files

The migration templates (Microsoft Excel XML Spreadsheet 2003 files) consist of different sheets which are visible at the bottom
of the migration template. You use the different sheets to specify the data that belongs to different data structures. For example
the migration template for the migration object Material, contains a sheet for basic data, a sheet for plant data, and so on. Some
sheets are mandatory, and some are optional.

A migration template is based on the active view of the relevant migration object. You can find information about the active view in
the Microsoft Excel XML file. In the file, navigate to File Info . You can find the active view name under Properties Tags .

Prerequisites

In the Microsoft Excel XML Spreadsheet 2003 file, navigate to File Options Advanced . Under the option When calculating
this workbook:, ensure that the option Set precision as displayed is selected.

 Note
For Mac OS machines, navigate to Excel Preferences . Under Formulas and Lists, choose Calculation. Under the option
When calculating workbooks, ensure that the option Set precision as displayed is selected.

The Field List Sheet

The Field List sheet is one of the first sheets in the migration template. You use this sheet to get an overview of the expected
data in one central location.

This is custom documentation. For more information, please visit the SAP Help Portal 16
 11/2/24, 10:45 AM
It contains information about the mandatory and optional sheets, as well as detailed information for each sheet (for example the
expected data type and length for the fields in each sheet).

On the Field List sheet, you can view the following information for each field in the migration template:

The name of the sheet, and whether it is mandatory or optional. Only mandatory sheets have the suffix Mandatory, for
example Basic Data (Mandatory). All other sheets are optional.

 Note
You can quickly get an overview of the mandatory and optional sheets by looking at the color of the sheet names at the
bottom of the migration template. The name of the mandatory sheets have the color orange, while the optional sheets
have the color blue.

The group name for the fields in a sheet.

The individual fields in each sheet, as well as whether fields are mandatory for a sheet.

Information about the expected format of the individual fields, for example the data type and length.

 Note
In the field list sheet, certain technical information about the fields is hidden by default. The columns SAP Structure and SAP
Field (columns 8 and 9) are hidden by default. The column SAP Structure is the technical name of the structure that the field
belongs to. The column SAP Field is the technical name of the field. To unhide these columns, select the columns adjacent to
either side of the columns that you want to unhide. Right-click your selection, and choose Unhide.

If you want to extract data from SAP ERP, the technical name of structure and the technical name of the field often corresponds
to the SAP ERP table name and field name.

Working with Sheets

For each migration template, you need to specify data for the mandatory sheets, and for the optional sheets that are relevant for
your project:

Mandatory sheets (orange)

Mandatory sheets represent the minimum set of data you must provide for data migration. Fill in all mandatory fields.

Optional sheets (blue)

Use optional sheets depending on your migration scope and available legacy data.

Viewing Additional Information for Each Column

In row 8, you can view the field names in SAP S/4HANA, as well as additional information such as the expected format (for
example the data type and length). Note that you must expand the row to view this additional information.

Some fields are mandatory, and some are optional. The wildcard character (‘*’) beside the name of a field indicates that the field is
mandatory.

 Note
Although an optional sheet may contain mandatory columns, if the sheet is not relevant for your project, there is no need to fill
the mandatory columns in the sheet with data.

This is custom documentation. For more information, please visit the SAP Help Portal 17
 11/2/24, 10:45 AM

 Note
Rows 4, 5, and 6 are hidden by default. Row 4 is the technical name of the structure (corresponds to the sheet name). Row 5 is
the technical name of the field (corresponds to row 8 - the field description). Row 6 contains technical information such as the
data type and length.

To unhide these rows, select the rows adjacent to either side of the rows that you want to unhide. Right-click your selection, and
choose Unhide.

Working with Different Data Types

You can view the data type for a field in row 8 (see Viewing Additional Information for Each Column above). Depending on the
field, one of the following data types may be required:

Text

Letters, numbers, and special characters (such as ‘.’ and ‘&’) are permitted. In the SAP S/4HANA migration cockpit, you can
map the values of certain fields with the data type text (usually those fields with Length: 80) to their correct SAP S/4HANA
target values. You can do this value mapping in the SAP S/4HANA migration cockpit when you start the transfer (in the step
Convert Values).

Number

Enter numbers with decimals in the relevant country-specific format, for example 12.34 (United States) or 12,34
(Germany). For fields with decimal places, the length includes the number of decimal places (if required), for example if the
information for the column states Length: 8, Decimals: 3, then a number such as 12345.678 is permitted. Note that
decimal places are not mandatory. In is this example, you can specify a whole number up to length 8 without decimal
places, for example ‘1’. This number would be set to ‘1.000’ internally. For negative numbers, ensure that a minus sign (‘-‘)
directly precedes the number, for example ‘-100’.

Note that the maximum field length supported by Microsoft Excel is 15 digits (including decimals). If you have longer
numbers, use the option for transferring data to S/4HANA using staging tables. For more information, see SAP Knowledge
Base Article 2718516 .

Date

Enter the date in the country-specific format of your operating system, for example 12/31/1998 (United States) or
31.12.1998 (Germany). Note that Microsoft Excel automatically recognizes different date formats and transforms them
automatically to the correct XML format.

Time

Enter the time in the format HH:MM:SS, for example 02:52:40.

Date-Time

Enter the date in your country-specific format followed by the time in the format HH:MM:SS, for example 12/31/1998
02:52:40 (United States) and 31.12.1998 02:52:40 (Germany). Separate the date and time with a blank space.

Copying Data to a Sheet

When copying data to a sheet from Microsoft Excel, always right-click the relevant cell and choose the paste option Values (V).
Avoid pasting data that includes formatting and formulas into the migration template, as this will corrupt the structure of the XML
migration template.

Using the Find and Replace Function

This is custom documentation. For more information, please visit the SAP Help Portal 18
 11/2/24, 10:45 AM
Do not use the Microsoft Excel function Find and Replace. If you change data by using this function, you may also unintentionally
change the field names and corrupt the structure of the XML migration template.

Saving the Migration Template

Ensure that you only save the migration template as a Microsoft Excel XML Spreadsheet 2003 file. Other file types are not
supported by the SAP S/4HANA migration cockpit.

Important Information

Do not make any changes to the structure of the migration template, specifically:

Do not delete, rename or change the order any sheet in the migration template.

Do not change the formatting of any cells.

Do not use formulas.

Do not hide, remove, or change the order of any of the columns in the migration template.

 Note
Any changes to the sheets will result in a corrupted XML structure. Such modified migration templates are not supported by
the SAP S/4HANA migration cockpit.

Filling CSV Template Files with Data

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, for example if you are automating the extraction of data from database tables, CSV files
may be easier to create using database or other file handling tools. We recommend exercising caution when using CSV files for the
following reasons:

You need to use a separate CSV file for each data structure.

There is no built-in protection for data formats.

Additional Information About CSV Template Files

You download a CSV template file for each data structure of a migration object. In the first row of a CSV template file, you can view
the technical names of the fields.

An asterisk (*) next to a field name indicates a mandatory field. For example, the field BANKA is a mandatory field. The first row of a
CSV file containing this field would have the entry BANKA (*).

Key fields are always mandatory fields. The letter k (k) and an asterisk (*) next to the field name indicates a mandatory key field.
For example, the field BANKS is a mandatory key field. The first row of a CSV file containing this field would have the entry BANKS
(k/*).

On the Tables tab of the Migration Object Tables screen, you can view more detailed information about the fields. For example, you
can view the name of the field as well as the data type and length.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 19
 11/2/24, 10:45 AM
CSV files must comply with RFC 4180 and use UTF-8 encoding. UTF-8 with BOM is not supported. RFC 4180 defines a standard
dialect for CSV files that specifies delimiters, quoting, and line breaks. However, unlike RFC 4180, the SAP S/4HANA migration
cockpit supports different field delimiters. For more information, see CSV File Options.

For additional information about using CSV files, see SAP Knowledge Base Article 3210687 .

CSV File Options

On the Project Settings screen, under CSV File Options, you can view information about how the system processes CSV files. You
can also adjust certain settings. There are the following options:

General Options

CSV Header Options

Special Characters

General Options
Under General Options, you can adjust the values of the following fields:

Date Format

Dates in the CSV file must adhere to a specific format. The default date format is YYYYMMDD. You can select an alternative
date format from the dropdown list if required.

Time Format

Times in the CSV file must adhere to a specific format. The default time format is HHMMSS. You can select an alternative
time format from the dropdown list if required.

Decimal Notation

In the CSV file, you need to ensure that decimal numbers use the appropriate decimal notation. The default decimal
notation is 1234567.89 but you can select a decimal notation that uses thousand separators, for example 1,234,567.89

In addition, you can view the following information:

Field Value Additional Information

Character Encoding UTF-8 If you create CSV files using your own tools,
you need to ensure that they use UTF-8
character encoding.

CSV Header Options

Under File Header Options, there are the following options:

First Row is Header Row

This is the default option. The first row of a CSV template file is the header row. This row contains the technical names of
the fields. An asterisk (*) next to a field name indicates a mandatory field, while the letter k (k) and an asterisk (*) next to

This is custom documentation. For more information, please visit the SAP Help Portal 20
 11/2/24, 10:45 AM
the field name indicates a mandatory key field.

If you use the option First Row is Header Row, the first row in your CSV file must be a header row. The field names in the
header row must have the same name as the fields in the header row of the CSV template file. The system will expect values
for each mandatory field specified in the header row. In addition, the order of the values in each row must correspond to the
order of the fields in the header row. In the first row of your CSV file, you can remove the indicators next to the field names if
required.

This option also provides a more flexible approach for uploading data. For example, you can remove columns, and change
the order of the columns. Note that the mandatory fields must always be present in the header row of your CSV file.

 Note
If you want to specify empty values for fields at the start of a row, they must be separated by a delimiter. If you want to
specify empty values for fields at the end of a row, they do not need to be separated by a delimiter.

Example: The header row of a CSV file has two mandatory key fields and 2 additional fields. In the second row of the CSV
file, you want to specify values for all four fields. For the remaining rows, you want to specify values for the two
mandatory key fields only. The following example CSV file is acceptable:

Field1(k/*),Field 2(k/*),Field3,Field4

Value1,Value2,Value3,Value4

Value5,Value6

Value7,Value8

For additional information about this option, including examples, see SAP Knowledge Base Article 3210687 .

No Header Row (Import All Rows)

You can use this option if you want to create CSV files with no header rows. For example, if you use your own tools to
generate CSV files it may be easier to create CSV files without a header row.

You need to first download the relevant CSV template file to determine the relevant fields, and then create your CSV file
accordingly. If you use this option, the system will expect values for each mandatory field specified in the header row of the
CSV template file. The values in your CSV file must also be in the same order as the header row of the CSV template file. In
addition, empty values for fields must be separated by a delimiter.

 Note
Empty values for fields must be separated by a delimiter.

Example: The header row of a CSV template file has two mandatory key fields and 2 additional fields. You want to create
a CSV file that has no header row. In the first row of your CSV file, you want to specify values for all four fields. For the
remaining rows, you want to specify values for the two mandatory key fields only. The following example CSV file is
acceptable:

Value1,Value2,Value3,Value4

Value5,Value6,,

Value7,Value8,,

Number of Rows to Skip

You can use this option if you want the system to skip one or more rows in the CSV file. For example, you could include the
field descriptions in the second row as extra information. The default value of this field is 1. This means that the system will
not process first row of the CSV file. You can increase this number if required. For example, if you change this value to 2, the
system will skip the first two lines in the file.

This is custom documentation. For more information, please visit the SAP Help Portal 21
 11/2/24, 10:45 AM
You need to first download the relevant CSV template file to determine the relevant fields, and then create your CSV file
accordingly. If you use this option, the system will expect values for each mandatory field specified in the header row of the
CSV template file. The values in your CSV file must also be in the same order as the header row of the CSV template file. In
addition, empty values for fields must be separated by a delimiter.

Special Characters
Under Special Characters, you can adjust the values of the following fields:

Record Delimiter

A line break separates each row in the CSV file. The following values are possible:

Windows (CR LF)

Macintosh (CR)

Unix (LF)

Field Delimiter

The following values are possible:

Comma (,)

Semicolon (;)

Tab

In addition, you can view the following information:

Field Value Additional Information

Character Used to Enclose Fields Double Quotes (") Each field may or may not be enclosed in
double quotes. If fields are not enclosed
with double quotes, then double quotes
may not appear inside the fields.

Escape Character Double Quotes (") If double-quotes are used to enclose fields,
then a double-quote that appears inside a
field must be preceded by another double
quote. Example: "aaa","b""bb","ccc"

Transferring Data to Staging Tables

The system automatically creates database tables for each migration object in a project. These database tables are called staging
tables. For each migration object, the system creates one or more staging tables. The staging tables have the naming convention
/1LT/DS<system ID><numeric identifier>, for example /1LT/DSQKX000928.

On the Migration Projects screen, in the Data column, you can view the number of staging tables for each migration object.

 Note
When the SAP S/4HANA migration cockpit creates the staging tables, it ensures that the following fields cannot contain null
values:

This is custom documentation. For more information, please visit the SAP Help Portal 22
 11/2/24, 10:45 AM
Key fields

Mandatory fields

Fields for which the default value of the relevant ABAP data type (for example NUMC, DATE, or DECIMAL) is not empty.

All other fields can contain null values.

There are the following options for populating the staging tables with data:

Template files are provided for every migration object. You can download a template file for a migration object and enter the
data to be migrated in the file. You then upload the completed file, and the system automatically transfers the contents of
the file to the staging tables.

You can fill the staging tables with data by using your preferred tools (for example SAP Data Services).

Transferring Data from XML Template Files to Staging Tables

Context
Once you have filled the XML template file for a migration object with data, you can upload the file to the SAP S/4HANA migration
cockpit. The system then validates the data in the file and transfers the data to the staging tables that were generated for that
migration object.

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

Procedure
1. On the Migration Project screen, select the relevant migration object and choose the action Upload File.

2. The system displays the Migration Object Tables screen. On the Files tab, you upload the files and view the status of the
validation and transfer process. To upload a file, you can either use the Upload button or use the drag and drop function.

3. The system uploads the file to the SAP S/4HANA migration cockpit. On the Files tab, you can view the status of the upload.

4. The system validates the data in the file. On the Files tab, you can view the status of the validation as well as information
such as the time the process was started.

5. If there are any issues with the data in the file you can view the relevant messages. To resolve any validation issues, you
must delete the file and adjust the data in your file accordingly. You can then upload the file and the system will start the
validation process again.

If the status of the file is Validation Completed with Warnings, you need to analyze the messages before proceeding. If you
determine that the messages can be ignored, you need to transfer the data to the staging tables manually.

6. Once the file has been validated successfully (no error or warning messages), the system automatically starts transferring
the data in the file to the staging tables that were generated for that migration object. Once all the data in the file has been
transferred to the staging tables, the system displays the information Data Successfully Transferred to Staging Tables.
You can also view information such as the number of transferred migration object instances.

The Migration Object Tables Screen

On the Migration Object Tables screen, you can view the staging tables for a migration object. You can also view any uploaded
files.

This is custom documentation. For more information, please visit the SAP Help Portal 23
 11/2/24, 10:45 AM
The Migration Object Tables screen contains the following tabs:

Tables

On the Tables tab, you can view information about the staging tables such as the technical name of the staging tables and
the current status. If you click a staging table, the system displays the Migration Object Tables, Structure screen where
you can find detailed information about the fields in the staging table. To view the content of a table, click an entry in the
Rows in Staging Table column.

On the Tables tab, the following options are possible:

Consistency Check

To migrate data from staging tables, all records needs to be associated with records at a higher level in the
hierarchy. You can use this function to check whether these associations exist. This function is only relevant if you
provided data directly to the staging tables.

If you are using files to populate the staging tables with data, this check is done automatically when validating the
file.

Reset Table Settings

It is not possible to adjust the data in the staging tables while the preparation step, the migration, or the simulation
is in process. However, in certain situations it is not possible to adjust the data in the staging tables even though
none of these steps are in process. This can occur, for example, if a user cancelled jobs manually, or if an unexpected
event occurred.

You can use the option Reset Table Settings to unlock the staging tables so that you can adjust data again. To do
this, the system resets the settings for the tables.

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 exists to 0. The number of migrated instances is not adjusted. When
adjusting data in the staging table, do not update field /1LT/PROCESSED.

Delete All Records

You can use the button Delete All Records to delete all records from selected staging tables, regardless of the
status. Note that deleting records from the staging tables may result in errors or inconsistencies.

Adjust Structure

If the table has the status Adjustment Required, the system can change the structures of the selected staging
tables so that they reflect the latest version of the migration object provided by SAP. To do this, choose the button
Adjust Structures. Note that no data will be lost during this process.

For example, if the staging tables are located in a remote SAP HANA system, it is possible to adjust or even drop
staging tables. If such an action was done in error, you can use this option to adjust the staging tables so that they
reflect the latest version of the migration object provided by SAP.

Files

On the Files tab, you can upload files and view any uploaded files. You can transfer the content of a file to the staging tables
so that data can be transferred to SAP S/4HANA. If data from a file has been transferred to the staging tables, then this
data will not be deleted from the staging tables if you delete the file.

The following feature is also available:

Download Metadata

You can download metadata for all tables of a migration object. The system creates a comma-separated values (CSV) file
that contains the structure of the tables. For each field, you can view information such as the length and data type. You can

This is custom documentation. For more information, please visit the SAP Help Portal 24
 11/2/24, 10:45 AM
use this information, for example, to easily copy data to any export scripts that you might use to populate the staging
tables with data.

Handling Duplicate Key Errors

When transferring data from a file to the staging tables, duplicate key errors could occur. A duplicate key error means that there is
already an instance in the table that has the same key field as the instance to be inserted. If duplicate key errors occur, the status
of the file will change to Transfer of Data to Staging Tables Failed. You can view the relevant messages for the file by choosing
Show Messages.

There are the following options for handling duplicate key errors:

You can delete the file, for example if you know that there are values in the file that are not correct. You can then adjust the
file and upload it again.

You can proceed with transferring the data in the file to the staging tables. To do this, you select the relevant file and choose
Transfer Data to Staging Tables. The system displays the Processing Options screen where you can choose one of the
following options:

Skip Files with Duplicates

The system will not transfer any data from files that contain duplicate instances.

Replace Duplicates with Instances from File

The system will transfer all data from the file to the staging tables except for such duplicate instances. If any
duplicate instances exist in the staging tables, they will be deleted from the staging tables and then replaced with
the instances from the file. Note that if a duplicate instance has already been successfully migrated, then it will not
be deleted from the staging tables.

Example

For the migration object Bank Master, you transferred data to the staging tables but did not specify a region:

Bank Country Key Bank Key Name of Bank Region (State, Province,
Country)

EN 2344444 563222666

You adjust the file (or prepare a new file) so that it contains a value for the Region field. You then upload the file. For this file, you
choose the processing option Replace Duplicates with Instances from File. The above migration object instance will be replaced
with the new instance from the file that contains a value for the Region field.

Transferring Data from CSV Template Files to Staging Tables

Once you have filled the CSV template files for a migration object with data, you can upload the files to the SAP S/4HANA
migration cockpit. There are two options for uploading CSV files:

On the Migration Object Tables screen, you can upload a zip file that contains your CSV files. We recommend using this
option, as it is the most efficient method for uploading the CSV files for a migration object.

If the CSV files in the zip file follow a specific naming convention, the system will automatically map the CSV files to the
relevant data structures. If the there are no upload errors, the system will validate the data in the CSV files and transfer the
data to the staging tables. For more information, see Uploading a Zip File.

This is custom documentation. For more information, please visit the SAP Help Portal 25
 11/2/24, 10:45 AM
You can create a folder for your CSV files and upload them there. For more information, see Creating a Folder for Your CSV
Files.

Uploading a Zip File

Prerequisites

You have downloaded a zip file that contains CSV template files for each mandatory data structure of the migration object. You
have filled the CSV template files with data and saved the CSV files in a zip file. For more information about CSV template files, see
Additional Information About CSV Template Files.

Context

You can upload a zip file that contains your CSV files. The system will create a folder with the same name as your zip file. We
recommend using this option, as it is the most efficient method for uploading the CSV files for a migration object.

 Note
If the CSV files in the zip file follow the naming convention <data structure name>#<optional user input>.csv,
the system will automatically map the CSV files to the relevant data structures. If the there are no upload errors, the system will
validate the data in the CSV files and transfer the data to the staging tables.

 Note
If the CSV files in the zip file do not follow the naming convention <data structure name>#<optional user
input>.csv, your will need to map the CSV files to the relevant data structures. You will then need to validate the data in the
CSV files, and then transfer the data in the files to the staging tables.

Procedure
1. On the Migration Project screen, select the relevant migration object and choose the action Upload File.

2. The system displays the Migration Object Tables screen. On the Upload Files tab, you can upload the zip file that contains
your CSV files. To upload a file, you can either use the Upload button or use the drag and drop function.

3. The system creates a folder for the CSV files and uploads the CSV files to the folder. On the Upload Files tab, you can view
the folder as well as the status of the upload. The system checks the structure of the CSV files, for example the system
checks the character encoding of the CSV files and whether a header row exists.

4. If the CSV files in the zip file follow the naming convention <data structure name>#<optional user
input>.csv, the system will automatically map the CSV files to the relevant data structures. If the CSV files do not follow
this naming convention, you will need to map the CSV files to the relevant data structures. For more information, see
Mapping a CSV File to a Data Structure.

5. If required, choose the Validate Data button to validate the data in the CSV file. On the Upload Files tab, you can view the
overall status of the validation as well as information such as the time the process was started.

When validating the data in a file, the system runs multiple checks. For example, the system checks whether values have
the correct data type and length. The system also checks whether the file contains values for all key fields and for all
mandatory fields.

In the folder for the CSV files, on the Data Structures tab, you can view each uploaded CSV file as well as the corresponding
data structure of the migration object.

6. If all the CSV files in the uploaded zip file were validated successfully (no error or warning messages), the system
automatically starts transferring the data in the file to the staging tables that were generated for that migration object.
Once all the data in the file has been transferred to the staging tables, the system changes the status of the folder to Data
Successfully Transferred to Staging Tables.

This is custom documentation. For more information, please visit the SAP Help Portal 26
 11/2/24, 10:45 AM
If a CSV file does not follow the naming convention <data structure name>#<optional user input>.csv, or if
there are validation errors, you will need to transfer the data in the file to the staging tables manually. You can do this by
choosing the Transfer Data to Staging Tables button.

7. If the status of the folder for the CSV files is Validation Failed, then there is an issue with the data in at least one of the CSV
files in the folder. You can view the relevant messages by choosing the Show Messages link.

To resolve any validation issues, you need to delete the relevant file and then upload a new version of the file that contains
the corrected data. After you upload the corrected file, you need to choose Validate Data to validate the data in the CSV file.
Once the CSV file has been validated successfully (no error or warning messages), you can transfer the data in the file to
the staging tables by choosing the Transfer Data to Staging Tables button.

If the status of the folder for the CSV files is Validation Completed with Warnings, you need to analyze the relevant
messages before proceeding. If you determine that the messages can be ignored, you can transfer the data in the file to the
staging tables by choosing the Transfer Data to Staging Tables button.

Mapping a CSV File to a Data Structure

You download CSV template files for each mandatory data structure of a migration object. The downloaded CSV file names are
structured as follows:

<data structure name>#<optional user input>.csv

When you upload a CSV file, the system can map the CSV file to the relevant data structure. However, this depends on whether the
CSV file follows the naming convention. You have the following options:

If a CSV file follows the naming convention <data structure name>#<optional user input>.csv, the system
automatically maps the file to the relevant data structure. For more information, see the first example below.

If a CSV file does not follow the naming convention <data structure name>#<optional user input>.csv, you
need to map the file to the relevant data structure manually. For more information, see the second example below.

Example

The migration object Bank has one data structure called S_BNKA. You download the CSV template file for this migration object.
The downloaded file name is S_BNKA#FreeText.csv.

You fill this template file with data and save the file. When naming your file, you do not adjust the data structure name, for example
your saved file is named S_BNKA#FreeText.csv, S_BNKA.csv, or S_BNKA#Test1.csv

When you upload the file, the system will automatically map the CSV file to the data structure S_BNKA.

Example

The migration object Bank has one data structure called S_BNKA. You download the CSV template file for this migration object.
The downloaded file name is S_BNKA#FreeText.csv.

You fill this template file with data and save the file. When naming your file, you adjust the data structure name, for example your
saved file is named S_BNKA1#FreeText.csv, S_BNKA_Test.csv, or BANK_Test.csv.

On the Folder for CSV Files screen, you upload this file. On the Files tab, the status of the file is Not Mapped to Any Data
Structure. You then map the file to the relevant data structure by selecting the file and choosing the Map Files button.

This is custom documentation. For more information, please visit the SAP Help Portal 27
 11/2/24, 10:45 AM

The Migration Object Tables Screen

On the Migration Object Tables screen, you can view the staging tables for a migration object. You can also view any uploaded
files.

The Migration Object Tables screen contains the following tabs:

Tables

On the Tables tab, you can view information about the staging tables such as the technical name of the staging tables and
the current status. If you click a staging table, the system displays the Migration Object Tables, Structure screen where
you can find detailed information about the fields in the staging table. To view the content of a table, click an entry in the
Rows in Staging Table column.

On the Tables tab, the following options are possible:

Consistency Check

To migrate data from staging tables, all records needs to be associated with records at a higher level in the
hierarchy. You can use this function to check whether these associations exist. This function is only relevant if you
provided data directly to the staging tables.

If you are using files to populate the staging tables with data, this check is done automatically when validating the
file.

Reset Table Settings

It is not possible to adjust the data in the staging tables while the preparation step, the migration, or the simulation
is in process. However, in certain situations it is not possible to adjust the data in the staging tables even though
none of these steps are in process. This can occur, for example, if a user cancelled jobs manually, or if an unexpected
event occurred.

You can use the option Reset Table Settings to unlock the staging tables so that you can adjust data again. To do
this, the system resets the settings for the tables.

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 exists to 0. The number of migrated instances is not adjusted. When
adjusting data in the staging table, do not update field /1LT/PROCESSED.

Delete All Records

You can use the button Delete All Records to delete all records from selected staging tables, regardless of the
status. Note that deleting records from the staging tables may result in errors or inconsistencies.

Adjust Structure

If the table has the status Adjustment Required, the system can change the structures of the selected staging
tables so that they reflect the latest version of the migration object provided by SAP. To do this, choose the button
Adjust Structures. Note that no data will be lost during this process.

For example, if the staging tables are located in a remote SAP HANA system, it is possible to adjust or even drop
staging tables. If such an action was done in error, you can use this option to adjust the staging tables so that they
reflect the latest version of the migration object provided by SAP.

Files

On the Files tab, you can upload files and view any uploaded files. You can transfer the content of a file to the staging tables
so that data can be transferred to SAP S/4HANA. If data from a file has been transferred to the staging tables, then this
data will not be deleted from the staging tables if you delete the file.

This is custom documentation. For more information, please visit the SAP Help Portal 28
 11/2/24, 10:45 AM
The following feature is also available:

Download Metadata

You can download metadata for all tables of a migration object. The system creates a comma-separated values (CSV) file
that contains the structure of the tables. For each field, you can view information such as the length and data type. You can
use this information, for example, to easily copy data to any export scripts that you might use to populate the staging
tables with data.

Handling Duplicate Key Errors

When transferring data from a file to the staging tables, duplicate key errors could occur. A duplicate key error means that there is
already an instance in the table that has the same key field as the instance to be inserted. If duplicate key errors occur, the status
of the file will change to Transfer of Data to Staging Tables Failed. You can view the relevant messages for the file by choosing
Show Messages.

There are the following options for handling duplicate key errors:

You can delete the file, for example if you know that there are values in the file that are not correct. You can then adjust the
file and upload it again.

You can proceed with transferring the data in the file to the staging tables. To do this, you select the relevant file and choose
Transfer Data to Staging Tables. The system displays the Processing Options screen where you can choose one of the
following options:

Skip Files with Duplicates

The system will not transfer any data from files that contain duplicate instances.

Replace Duplicates with Instances from File

The system will transfer all data from the file to the staging tables except for such duplicate instances. If any
duplicate instances exist in the staging tables, they will be deleted from the staging tables and then replaced with
the instances from the file. Note that if a duplicate instance has already been successfully migrated, then it will not
be deleted from the staging tables.

Example

For the migration object Bank Master, you transferred data to the staging tables but did not specify a region:

Bank Country Key Bank Key Name of Bank Region (State, Province,
Country)

EN 2344444 563222666

You adjust the file (or prepare a new file) so that it contains a value for the Region field. You then upload the file. For this file, you
choose the processing option Replace Duplicates with Instances from File. The above migration object instance will be replaced
with the new instance from the file that contains a value for the Region field.

Creating a Folder for Your CSV Files

On the Migration Object Tables screen, you can upload your CSV files. On the Upload Files tab, you can create a folder for the CSV
files by choosing the button Create CSV Folder. You can then open your folder and either upload a zip file that contains your CSV

This is custom documentation. For more information, please visit the SAP Help Portal 29
 11/2/24, 10:45 AM
files or single CSV files. Note that the size limit for CSV folders is 100MB. You will then need to validate the data in the CSV files,
and then transfer the data in the files to the staging tables.

 Note
If the CSV files do not follow the naming convention <data structure name>#<optional user input>.csv, your will
need to map the CSV files to the relevant data structures. You will then need to validate the data in the CSV files, and then
transfer the data in the files to the staging tables. For more information, see Uploading CSV Files.

 Note
If the CSV files follow the naming convention <data structure name>#<optional user input>.csv, the system will
automatically map the CSV file to the relevant data structures. You will then need to validate the data in the CSV files, and then
transfer the data in the files to the staging tables. For more information, see Uploading CSV Files.

Uploading CSV Files

Prerequisites

You have filled a CSV template file with data. For more information about CSV template files, see Additional Information About CSV
Template Files.

A folder exists for your CSV files. You can create a folder for the CSV files on the Upload Files tab by choosing the button Create
CSV Folder.

Context
You can upload CSV files and transfer the data in the files to the staging tables that were generated for the relevant migration
object.

Procedure
1. On the Migration Object Tables screen, select the tab Upload Files.

2. Open the folder for your CSV file.

3. The system displays the Folder for CSV Files screen. On the Files tab, you can upload single CSV files or a zip file that
contains your CSV files. To upload a file, you can either use the Upload button or use the drag and drop function.

The system checks the structure of the CSV files, for example the system checks the character encoding of the CSV files
and whether a header row exists.

4. If the CSV files do not follow the naming convention <data structure name>#<optional user input>.csv, you
need to map the files to the relevant data structure. For more information, see Mapping a CSV File to a Data Structure.

5. Choose the Validate Data button to validate the data in the CSV file.

When validating the data in a file, the system runs multiple checks. For example, the system checks whether values have
the correct data type and length. The system also checks whether the file contains values for all key fields and for all
mandatory fields.

On the Data Structures tab, you can view the uploaded CSV files as well as the corresponding data structure of the
migration object.

6. If the status of the folder for the CSV files is Validation Failed, then there is an issue with the data in at least one of the CSV
files in the folder. You can view the relevant messages by choosing the Show Messages link.

This is custom documentation. For more information, please visit the SAP Help Portal 30
 11/2/24, 10:45 AM
To resolve any validation issues, you need to delete the file and then upload a new version of the file that contains the
corrected data.

If the status of the folder for the CSV files is Validation Completed with Warnings, you need to analyze the relevant
messages before proceeding. If you determine that the messages can be ignored, you can transfer the data in the file to the
staging tables by choosing the Transfer Data to Staging Tables button.

7. Once a CSV file has been validated successfully (no error or warning messages), you can transfer the data in the file to the
staging tables that were generated for that migration object. To do this, choose the Transfer Data to Staging Tables button.
Once all the data in the file has been transferred to the staging tables, the system changes the status of the folder to Data
Successfully Transferred to Staging Tables.

Mapping a CSV File to a Data Structure

You download CSV template files for each mandatory data structure of a migration object. The downloaded CSV file names are
structured as follows:

<data structure name>#<optional user input>.csv

When you upload a CSV file, the system can map the CSV file to the relevant data structure. However, this depends on whether the
CSV file follows the naming convention. You have the following options:

If a CSV file follows the naming convention <data structure name>#<optional user input>.csv, the system
automatically maps the file to the relevant data structure. For more information, see the first example below.

If a CSV file does not follow the naming convention <data structure name>#<optional user input>.csv, you
need to map the file to the relevant data structure manually. For more information, see the second example below.

Example

The migration object Bank has one data structure called S_BNKA. You download the CSV template file for this migration object.
The downloaded file name is S_BNKA#FreeText.csv.

You fill this template file with data and save the file. When naming your file, you do not adjust the data structure name, for example
your saved file is named S_BNKA#FreeText.csv, S_BNKA.csv, or S_BNKA#Test1.csv

When you upload the file, the system will automatically map the CSV file to the data structure S_BNKA.

Example

The migration object Bank has one data structure called S_BNKA. You download the CSV template file for this migration object.
The downloaded file name is S_BNKA#FreeText.csv.

You fill this template file with data and save the file. When naming your file, you adjust the data structure name, for example your
saved file is named S_BNKA1#FreeText.csv, S_BNKA_Test.csv, or BANK_Test.csv.

On the Folder for CSV Files screen, you upload this file. On the Files tab, the status of the file is Not Mapped to Any Data
Structure. You then map the file to the relevant data structure by selecting the file and choosing the Map Files button.

The Migration Object Tables Screen

On the Migration Object Tables screen, you can view the staging tables for a migration object. You can also view any uploaded
files.

This is custom documentation. For more information, please visit the SAP Help Portal 31
 11/2/24, 10:45 AM
The Migration Object Tables screen contains the following tabs:

Tables

On the Tables tab, you can view information about the staging tables such as the technical name of the staging tables and
the current status. If you click a staging table, the system displays the Migration Object Tables, Structure screen where
you can find detailed information about the fields in the staging table. To view the content of a table, click an entry in the
Rows in Staging Table column.

On the Tables tab, the following options are possible:

Consistency Check

To migrate data from staging tables, all records needs to be associated with records at a higher level in the
hierarchy. You can use this function to check whether these associations exist. This function is only relevant if you
provided data directly to the staging tables.

If you are using files to populate the staging tables with data, this check is done automatically when validating the
file.

Reset Table Settings

It is not possible to adjust the data in the staging tables while the preparation step, the migration, or the simulation
is in process. However, in certain situations it is not possible to adjust the data in the staging tables even though
none of these steps are in process. This can occur, for example, if a user cancelled jobs manually, or if an unexpected
event occurred.

You can use the option Reset Table Settings to unlock the staging tables so that you can adjust data again. To do
this, the system resets the settings for the tables.

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 exists to 0. The number of migrated instances is not adjusted. When
adjusting data in the staging table, do not update field /1LT/PROCESSED.

Delete All Records

You can use the button Delete All Records to delete all records from selected staging tables, regardless of the
status. Note that deleting records from the staging tables may result in errors or inconsistencies.

Adjust Structure

If the table has the status Adjustment Required, the system can change the structures of the selected staging
tables so that they reflect the latest version of the migration object provided by SAP. To do this, choose the button
Adjust Structures. Note that no data will be lost during this process.

For example, if the staging tables are located in a remote SAP HANA system, it is possible to adjust or even drop
staging tables. If such an action was done in error, you can use this option to adjust the staging tables so that they
reflect the latest version of the migration object provided by SAP.

Files

On the Files tab, you can upload files and view any uploaded files. You can transfer the content of a file to the staging tables
so that data can be transferred to SAP S/4HANA. If data from a file has been transferred to the staging tables, then this
data will not be deleted from the staging tables if you delete the file.

The following feature is also available:

Download Metadata

You can download metadata for all tables of a migration object. The system creates a comma-separated values (CSV) file
that contains the structure of the tables. For each field, you can view information such as the length and data type. You can
This is custom documentation. For more information, please visit the SAP Help Portal 32
 11/2/24, 10:45 AM
use this information, for example, to easily copy data to any export scripts that you might use to populate the staging
tables with data.

Handling Duplicate Key Errors

When transferring data from a file to the staging tables, duplicate key errors could occur. A duplicate key error means that there is
already an instance in the table that has the same key field as the instance to be inserted. If duplicate key errors occur, the status
of the file will change to Transfer of Data to Staging Tables Failed. You can view the relevant messages for the file by choosing
Show Messages.

There are the following options for handling duplicate key errors:

You can delete the file, for example if you know that there are values in the file that are not correct. You can then adjust the
file and upload it again.

You can proceed with transferring the data in the file to the staging tables. To do this, you select the relevant file and choose
Transfer Data to Staging Tables. The system displays the Processing Options screen where you can choose one of the
following options:

Skip Files with Duplicates

The system will not transfer any data from files that contain duplicate instances.

Replace Duplicates with Instances from File

The system will transfer all data from the file to the staging tables except for such duplicate instances. If any
duplicate instances exist in the staging tables, they will be deleted from the staging tables and then replaced with
the instances from the file. Note that if a duplicate instance has already been successfully migrated, then it will not
be deleted from the staging tables.

Example

For the migration object Bank Master, you transferred data to the staging tables but did not specify a region:

Bank Country Key Bank Key Name of Bank Region (State, Province,
Country)

EN 2344444 563222666

You adjust the file (or prepare a new file) so that it contains a value for the Region field. You then upload the file. For this file, you
choose the processing option Replace Duplicates with Instances from File. The above migration object instance will be replaced
with the new instance from the file that contains a value for the Region field.

Transferring Data to Staging Tables Using Your Preferred Tools

If the staging tables are located in a remote SAP HANA schema, you can populate the staging tables with data by using your
preferred tools (for example SAP Data Services). In this case, information such as the technical names of the staging tables as well
as the data types and lengths of the fields will be required.

 Note
For more information about populating the staging tables using tools such as SAP Data Services see SAP Note 2733253 .

This is custom documentation. For more information, please visit the SAP Help Portal 33
 11/2/24, 10:45 AM
On the Migration Object Tables screen, you can view the staging tables for a migration object. If you click a staging table, the
system displays the Migration Object Tables, Structure screen where you can find detailed information about the fields in the
staging table.

You can also download metadata for all tables of a migration object. The system creates a .txt file that contains the structure of the
tables. For each field, you can view information such as the length and data type as defined in the staging table. You can use this
information, for example, to easily copy data to any export scripts that you might use to populate the staging tables with data.

The Migration Object Tables Screen

On the Migration Object Tables screen, you can view the staging tables for a migration object. You can also view any uploaded
files.

The Migration Object Tables screen contains the following tabs:

Tables

On the Tables tab, you can view information about the staging tables such as the technical name of the staging tables and
the current status. If you click a staging table, the system displays the Migration Object Tables, Structure screen where
you can find detailed information about the fields in the staging table. To view the content of a table, click an entry in the
Rows in Staging Table column.

On the Tables tab, the following options are possible:

Consistency Check

To migrate data from staging tables, all records needs to be associated with records at a higher level in the
hierarchy. You can use this function to check whether these associations exist. This function is only relevant if you
provided data directly to the staging tables.

If you are using files to populate the staging tables with data, this check is done automatically when validating the
file.

Reset Table Settings

It is not possible to adjust the data in the staging tables while the preparation step, the migration, or the simulation
is in process. However, in certain situations it is not possible to adjust the data in the staging tables even though
none of these steps are in process. This can occur, for example, if a user cancelled jobs manually, or if an unexpected
event occurred.

You can use the option Reset Table Settings to unlock the staging tables so that you can adjust data again. To do
this, the system resets the settings for the tables.

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 exists to 0. The number of migrated instances is not adjusted. When
adjusting data in the staging table, do not update field /1LT/PROCESSED.

Delete All Records

You can use the button Delete All Records to delete all records from selected staging tables, regardless of the
status. Note that deleting records from the staging tables may result in errors or inconsistencies.

Adjust Structure

If the table has the status Adjustment Required, the system can change the structures of the selected staging
tables so that they reflect the latest version of the migration object provided by SAP. To do this, choose the button
Adjust Structures. Note that no data will be lost during this process.

This is custom documentation. For more information, please visit the SAP Help Portal 34
 11/2/24, 10:45 AM
For example, if the staging tables are located in a remote SAP HANA system, it is possible to adjust or even drop
staging tables. If such an action was done in error, you can use this option to adjust the staging tables so that they
reflect the latest version of the migration object provided by SAP.

Files

On the Files tab, you can upload files and view any uploaded files. You can transfer the content of a file to the staging tables
so that data can be transferred to SAP S/4HANA. If data from a file has been transferred to the staging tables, then this
data will not be deleted from the staging tables if you delete the file.

The following feature is also available:

Download Metadata

You can download metadata for all tables of a migration object. The system creates a comma-separated values (CSV) file
that contains the structure of the tables. For each field, you can view information such as the length and data type. You can
use this information, for example, to easily copy data to any export scripts that you might use to populate the staging
tables with data.

Viewing Migration Object Instances

Context
After you have transferred data to the staging tables, you can view the migration object instances in the staging tables.

A migration object represents a business object. For example, the migration object Bank represents the business object Bank. A
migration object instance is a set of one or more fields that have a defined relationship and that represent a business object
instance. For example, a migration object instance for the migration object Bank comprises several fields such as:

Bank Country Key

Bank Key

Bank Branch

Bank Group

Name of Bank

Procedure
On the Migration Project screen, in the Data column, you can view the number of instances in the staging tables for a migration
object. To view the instances, click the number of instances in the Data column. The system displays the Migration Object
Instances screen, where you can view the records for each instance.

The Migration Object Instances Screen

On the Migration Object Instances screen, you can view the records for each migration object instance. Each row represents one
migration object instance and contains the fields for the instance.

In addition, you can view the following columns:

Additional Fields

This is custom documentation. For more information, please visit the SAP Help Portal 35
 11/2/24, 10:45 AM
Each row can display up to five fields for a migration object instance. If a migration object instance contains more than five
fields, you can view the additional fields by choosing the Display All link in this column.

Source

If the migration object instance was transferred to the staging table using a file, the name of the file and a timestamp of the
upload is displayed in this column.

Action

The current action for the migration object instance. The following actions are possible:

None

Simulated

Migrated

Status

The status of the current action. An action can have one of the following status values:

Initial (Only relevant for the action None)

Success

Error

The following options are also available:

Deleting Migration Object Instances

If required, you can delete selected instances from the staging tables. To do this, select the relevant instances and choose
the Delete Instances button. Note that instances that have already been successfully migrated to the target system cannot
be deleted.

View Messages for Migration Object Instances

For a migration object instance, you can view messages related to the simulation and the migration. To do this, select the
relevant instances and choose the Messages button.

Preparing the Staging Tables

Prerequisites
For a migration object, you have transferred the data to the staging tables.

Context

The staging tables for each migration object need to be prepared before they can be used to transfer data to SAP S/4HANA.

 Note
This process must be repeated whenever new data is added to the staging tables.

Procedure

This is custom documentation. For more information, please visit the SAP Help Portal 36
 11/2/24, 10:45 AM
1. On the Migration Project screen, select the relevant migration object.

2. In the Action column, choose the option Prepare.

3. The system will prepare the staging tables so that they can be used to transfer data to SAP S/4HANA.

4. You can monitor the status of the preparation step in the Monitoring screen.

Mapping Tasks
You need to process any open mapping tasks for the migration object before you can proceed with the simulation or the migration.
Examples of mapping tasks include value mapping tasks (where you specify target values for corresponding source values) and
fixed value tasks (where you set default values for target fields).

On the Migration Project screen, in the Mapping Tasks column, you can view the number of open and completed tasks for each
migration object.

If a migration object has open tasks, click the relevant entry in the Mapping Tasks column. The system displays the Mapping Tasks
screen. Alternatively, you can select the relevant migration object and choose the action Mapping Tasks.

 Note
You can also display all mapping tasks for a project by choosing the Mapping Tasks button located in the top right screen area.

On the Mapping Tasks screen, you can view the open mapping tasks (open mapping tasks have the status To be Confirmed) as
well as any confirmed mapping tasks. You can also view whether any errors exist for mapping tasks. The system displays the
mapping tasks in a list. You can view the following information for each mapping task:

Mapping Tasks

The name of the task.

Status

The status of the mapping task. Mapping tasks can have the status Confirmed, To be Confirmed, or Error.

 Note
The system provides proposals for mapping values. If the system is unable to propose a meaningful mapping value, for
example if the system detects that a proposed value will result in data loss, then the systems sets the status of the
mapping value to Error. The system then sets a blank value for the target value (indicated by the text <Blank> in the
S/4HANA Target Value field). If a mapping task contains a mapping value that has the status Error, then the status of
the mapping task is also Error.

Type

The mapping task type. There are value mapping tasks (where you specify target values for corresponding source values)
and fixed value tasks (where you set default values for target fields).

Values

The number of values for the task, for example a value mapping task could involve specifying 10 target values.

You need to process the task by entering the relevant target values and confirming these target values. You can then set the status
of the task to Confirmed. Once all mapping tasks for a migration object have the status Confirmed, you can proceed with the
simulation or migration process for the migration object.

 Note
This is custom documentation. For more information, please visit the SAP Help Portal 37
 11/2/24, 10:45 AM
You can easily confirm all mapping values for a mapping task by selecting the relevant mapping task and choosing Confirm.
However, only mapping values with status To be Confirmed will be confirmed. Any mapping values that have the status Error
will not be confirmed. It is still possible to confirm mapping values that have the status Error, but this needs to be done
individually for each mapping value. You can do this by navigating to the relevant mapping value, selecting it, and choosing
Confirm.

 Note
The Mapping Tasks screen is not refreshed automatically. You may need to refresh the screen manually to view the latest
status, especially if you confirm all mapping values for a task at once.

Value Mapping Tasks

For Value Mapping tasks, you specify target values for corresponding source values. On the Mapping Tasks screen, select the
relevant value mapping task that has the status To be Confirmed. The system displays the task in a new screen. On the left-hand
side, the system displays the task and the current status.

On the right-hand side of the screen the system displays the name of the task, and the following information:

Status

The status of the task. Mapping tasks can have the status Confirmed or To be Confirmed.

Type

The type of task. There are Value Mapping tasks (where you specify target values for corresponding source values) and
Fixed Value tasks (where you set default values for target fields).

Used In

The migration object that uses the task. If the task is used by more than one migration object, the system displays a link
with the text Migration Objects. You can click this link to view the migration objects that use the task.

Documentation

To view the documentation for the mapping task, click the Show link.

On the right-hand side, under Values. the system displays the values that need to be confirmed for the task. You can view the
following information:

Source Value

The value of the relevant field in the source system.

Target Value

The value of the corresponding field in the target system. By default, the system proposes the source value as the target
value.

Status

The status of the specific values (either Confirmed or To be Confirmed).

Action

Once you have entered a target value (or accepted the proposal provided by the system) you confirm the value for the task.
To do this, you can choose the Confirm button.

This is custom documentation. For more information, please visit the SAP Help Portal 38
 11/2/24, 10:45 AM
For each value that has the status To be Confirmed, you need to either enter a value in the Target Value field or accept the
proposal provided by the system (if provided). Note that a space is also considered a valid value. You then select the checkbox for
the relevant row and choose the Confirm button. Once all the values have the status Confirmed, the system changes the status of
the task to Confirmed on the Mapping Tasks screen.

Example
There are open value mapping tasks for the migration object FI - G/L Account. One of these open value mapping tasks is the
Mapping of Company Code value mapping task. You use this task to check whether the target company codes need to be
changed, or if they should remain the same as the source system.

In this example, the company code 0001 remains the same as in the source system, but the data associated with company code
Z001 will now be assigned to company code ZZ99.

Source Company Code Target Company Code

0001 0001

Z001 ZZ99

Deleting Mapping Values

Context
You can delete the mapping values for value mapping tasks. You can delete specific mapping values for a mapping task, or you can
delete all mapping values for a mapping task. If you delete all mapping values for a mapping task, the relevant mapping task will no
longer be displayed on the Mapping Tasks screen. If you upload mapping values for the mapping task again, the mapping task will
be displayed on the Mapping Tasks screen once more. Alternatively, if you prepare the staging tables again, the mapping task will
be displayed on the Mapping Tasks screen once more.

 Note
Mapping values are required for simulating the migration and for migrating data. Deleting mapping values may cause errors or
may result in inconsistent data, especially if mapping values are used by multiple migration objects, or if mapping values were
created by the system (for example for internal numbering).

Procedure
1. On the Mapping Tasks screen, select the relevant mapping task. The system displays the mapping task in a new screen.

2. Under Values, select the relevant mapping values.

3. Choose the Delete Values button. The system will delete all the selected mapping values.

On the Mapping Tasks screen, you can delete all the mapping values for a mapping task. To do this, select the relevant
mapping task and choose the Delete Values button.

On the Monitoring screen, you can view the deleted mapping values. You can view information such as the user that deleted
the mapping values as well as the total number of mapping values that were deleted.

Fixed Value Tasks

This is custom documentation. For more information, please visit the SAP Help Portal 39
 11/2/24, 10:45 AM
For Fixed Value tasks, you specify default values for target fields. On the Mapping Tasks screen, select the relevant fixed value task
that has the status To be Confirmed. The system displays the task in a new screen.

On the left-hand side, the system displays the task and the current status. On the right-hand side, under Values. the system
displays the value that needs to be confirmed for the task. You can view the following information:

Customizing

The value of the field in the target system. In some cases, the system will propose a suitable value for the target field.

Status

The status of the specific values (either Confirmed or To be Confirmed).

Action

Once you have entered a target value (or accepted the proposal provided by the system) you confirm the value for the task.
To do this, choose the Confirm button.

For each fixed value that has the status To be Confirmed, you need to either enter a value in the Customizing field or accept the
proposal provided by the system (if provided). You then select the checkbox for the fixed value and choose the Confirm button.

Example
There are open fixed value tasks for the migration object FI - G/L account balance and open/line item. One of these open fixed
value tasks is the Fixed Value for Document Type of G/L Balance Transfer fixed value task.

You need to define a document type that is used when the balances are created in the target SAP S/4HANA system. To do this, you
enter the value SA in the Customizing field of the Document Type fixed value task.

Control Parameter Tasks

Certain migration objects use control parameter mapping tasks to control specific data migration procedures.

Example
When using the migration object Material Inspection Setup to migrate data to SAP S/4HANA, you need to process the control
parameter mapping task Take default values for inspection type to decide whether you want to use values for inspection types
from the source file or whether to let the system determine the default values according to your customizing settings for
inspection types.

Downloading Template Files for Mapping Tasks

Context
Microsoft Excel template files are available for each mapping task. If you need to specify a large number of values for a mapping
task, you can use these template files instead of specifying the values manually in the SAP S/4HANA migration cockpit.

Procedure
1. On the Mapping Tasks screen, choose Download Mapping Templates.

2. Select the relevant mapping tasks and choose the Download button.
This is custom documentation. For more information, please visit the SAP Help Portal 40
 11/2/24, 10:45 AM
3. The system creates a zip file that contains the template files.

4. Populate the template files with data and save them locally.

A template file for a mapping task contains the following sheets:

Signature

On the Signature sheet, you can view the data type and length for the source and target fields.

Data

On the Data sheet, you specify values for the target SAP S/4HANA fields.

Uploading Mapping Values

Prerequisites
You have downloaded a template file for a mapping task and filled the file with data.

Context

You can upload mapping values for a mapping task.

Procedure
1. On the Mapping Tasks screen, choose Upload Values. The system displays the Upload Mapping Values screen.

2. On the Files tab, upload the file by using the Upload button or the drag and drop function. You can upload single files as well
as zip files.

Under Additional Settings, you can specify additional options for transferring the mapping values to the SAP S/4HANA
Migration Cockpit. These options include:

Options for Confirming Values

To set the status of the mapping values to Confirmed, choose the option Confirm Values Automatically. Otherwise,
choose Do Not Confirm Values Automatically.

Options for Loading Values

To delete any existing values for the task and replace them with the values from the file, choose the option Replace
Existing Values. If you choose the option Modify Values / Add Values, any duplicate values will be replaced with the
values from the file.

3. To upload the mapping values, choose Upload Values.

Simulating the Migration

Once you have prepared the staging tables and processed all open tasks for a migration object, you can simulate the transfer of
data to the target SAP S/4HANA system. Note that no data is written to the target SAP S/4HANA system during the simulation
process, but you can view all the messages that would occur during an actual data transfer (for example information about a cost
center that does not exist).

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 41
 11/2/24, 10:45 AM
When you simulate the migration for first time, additional mapping tasks may appear. You need to process these mapping tasks
and repeat the simulation before you can proceed with the migration.

On the Migration Project screen, select the relevant migration object and choose the action Simulate. The system simulates the
migration for all migration object instances in the staging tables for the migration object.

 Note
You can also simulate the migration for specific migration object instances. You can do this on the Migration Object Instances
screen by selecting the relevant migration object instances and choosing the Simulate button.

 Note
On the Monitoring screen, you can cancel the simulation process. Under Activities, select the relevant activity, for example
Simulate Data. In the Options field, you can then choose the option Cancel.

Monitoring the Status of the Simulation

You can monitor the status of the simulation for a migration object. On the Migration Project screen, choose the button
Monitoring. The system displays the Monitoring screen, where you can view the active and completed activities, for example
Simulation Started or Simulation Completed. You can view the number of migration object instances that have been processed,
as well as the number of background jobs that are used to simulate the transfer.

On the Migration Project screen, you can view the number of migration object instances that have been simulated successfully,
and the number of migration object instances that have errors. To view the instances, click the relevant number in the Simulation
column.

If you are sure that errors for a specific activity can be ignored, you can set the status of the activity to Errors Resolved. The
activity will not be displayed when you use the filter to view the activities with errors (status Completed with Errors or Failed).

Migrating Data to SAP S/4HANA

Once you have prepared the staging tables and processed all open tasks for a migration object, you can transfer data to the target
SAP S/4HANA system. Note that we recommend that you first simulate the migration.

On the Migration Project screen, select the relevant migration object and choose the action Migrate. The system will migrate the
migration object instances in the staging tables for the migration object. Note that any instances that have already been migrated
will not be migrated again.

 Note
You can also migrate specific migration object instances. You can do this on the Migration Object Instances screen by selecting
the relevant migration object instances and choosing the button Migrate.

 Note
On the Monitoring screen, you can cancel the migration process. Under Activities, select the relevant activity, for example
Migrate Data. In the Options field, you can then choose the option Cancel.

Monitoring the Status of the Migration

This is custom documentation. For more information, please visit the SAP Help Portal 42
 11/2/24, 10:45 AM
You can monitor the status of the migration for a migration object. On the Migration Project screen, choose the button
Monitoring. The system displays the Monitoring screen, where you can view the active and completed activities, for example
Migration Started or Migration Completed. You can view the number of migration object instances that have been processed, as
well as the number of background jobs that are used for the migration.

On the Migration Project screen, you can view the number of migration object instances that have been migrated successfully,
and the number of migration object instances that have errors. To view the instances, click the relevant number in the Migration
column.

If you are sure that errors for a specific activity can be ignored, you can set the status of the activity to Errors Resolved. The
activity will not be displayed when you use the filter to view the activities with errors (status Completed with Errors or Failed).

Viewing the Migration Results

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 the Result of Step "Migration" field that contain the
migration results. In this result field, you can view the data that has been created in the SAP S/4HANA system for a migration
object instance. You can download the migration results by choosing the Download button. The system will create a text file that
contains the migration results.

You can also navigate directly to the relevant SAP Fiori app for the migration object to view the newly created data. To do this, click
an entry in the Result column. Note that there are prerequisites for accessing apps, such as required business roles. For more
information, see the documentation for the relevant migration object on the SAP Help Portal.

Creating Correction Files

Context
If errors occur during the migration, you can use a correction file to correct the errors. A correction file contains all the migration
object instances in the staging tables that have the status Error. You can adjust the correction file to resolve the errors, upload the
file, and then migrate the instances to the target system.

Procedure
1. On the Migration Object Instances screen, choose the button Create Correction File. You can also create a correction file
from the Migration Project screen by selecting the relevant migration object and choosing the action Create Correction
File.

2. The system displays the Select Source dialog. In the Select Source dialog, the system lists the files that can be used to
create the correction file. Select the relevant files and choose Create Correction File.

3. Navigate to the Monitoring screen and locate the relevant migration object.

4. When the status of the activity Generate Correction File changes to Finished, the system displays a Download File link.

5. Click the Download File link and save the file.

Transferring Data from a Correction File to SAP S/4HANA

Prerequisites

You have created a correction file to resolve errors that occurred during the migration process. You have adjusted the values in the
file to resolve these errors.
This is custom documentation. For more information, please visit the SAP Help Portal 43
 11/2/24, 10:45 AM

Context

 Note
On the Migration Object Instances screen, you can delete the instances with errors. This ensures that no duplicate key errors
will occur when uploading the correction file. If you do not delete the instances with errors, the system will identify duplicate
key errors when uploading the correction file and display options for handling the duplicate key errors. If you choose the option
Replace Duplicates with Instances from File, the system will delete the duplicate instances from the staging tables and
replace them with the instances from the correction file.

Procedure
1. On the Migration Project screen, select the relevant migration object and choose the action Upload File.

2. The system displays the Migration Object Tables screen. On the Files tab, you can upload the correction file and view the
status of the validation and transfer process. To upload a file, you can either use the Upload button or use the drag and drop
function.

3. The system uploads the file to the SAP S/4HANA migration cockpit. On the Files tab, you can view the status of the upload.

4. The system validates the data in the file. On the Files tab, you can view the status of the validation as well as information
such as the time the process was started.

5. Once the file has been validated successfully, the system automatically starts transferring the data in the file to the staging
tables. Once all the data in the file has been transferred to the staging tables, the system displays the information Data
Successfully Transferred to Staging Tables. You can also view information such as the number of transferred migration
object instances.

Migrate Data Directly from SAP System

Context

The SAP S/4HANA migration cockpit facilitates the transfer of business data from certain SAP source systems to SAP S/4HANA.
The SAP S/4HANA migration cockpit uses migration objects to identify and transfer the relevant data. A migration object
describes how to migrate data for a specific business object to SAP S/4HANA. It contains information about the relevant source
and target structures, as well as the relationships between these structures. It also contains mapping information for the relevant
fields, as well as any rules used to convert values that are migrated from source fields to target fields. SAP provide predefined
migration objects that you can use to transfer your data.

The SAP S/4HANA migration cockpit is designed for an initial load of data, specifically for the SAP S/4HANA new implementation
scenario. It is not designed to keep data in sync between systems, to realize a continuous exchange or flow of data, or to establish
an integration scenario. Other SAP products and solutions products are available for this purpose.

 Note
Important information regarding the processing of personal data

Customers are responsible for the data in their systems, and also responsible for complying with local laws regarding data
protection and privacy. SAP provide tools to support with this, such as data retention and read access logging.

Data protection legislation may require that personal data is deleted once the data has served its originally defined purpose
and is also no longer subject to additional legal data retention requirements.

Data protection legislation may require that personal data is deleted once the data has no longer any purpose and is also no
longer subject to additional legal data retention requirements. If data protection legislation is applicable in your case, then
migrating personal data which should have been deleted could be interpreted as the processing of personal data without any
legally justified purpose.

This is custom documentation. For more information, please visit the SAP Help Portal 44
 11/2/24, 10:45 AM
In this case, it is crucial to ensure that such personal data is not migrated to the target SAP S/4HANA system.

Before You Start

You use an RFC connection to connect the SAP S/4HANA migration cockpit to your source system. The SAP S/4HANA migration
cockpit selects data from the source system by using specific criteria. For example if you are using the migration scenario SAP
ERP to SAP S/4HANA, then the SAP S/4HANA migration cockpit selects data using company codes (you specify the relevant
company codes when creating a project). Note the following information for the migration scenarios:

If you are using the migration scenario SAP ERP to SAP S/4HANA, the lowest supported ERP release is ERP 6.0 (SAP
NetWeaver 7.0).

If you are using the migration scenario SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA, the supported release is
AFS 6.0.

If you are using the migration scenario SAP EWM to EWM in SAP S/4HANA, the lowest supported EWM release is EWM 5.1
(SAP NetWeaver 7.0).

If you are using the migration scenario SAP CRM to SAP S/4HANA for Customer Management, the lowest supported CRM
release is SAP CRM 7.0.

If you are using the migration scenario SAP APO SPP to SAP S/4HANA Extended Service Parts Planning (eSPP), the
lowest supported SCM release is SAP SCM 7.14.

You use a migration project to connect to one specific source system. It is not possible to change the source system in a project.
However, you can connect to a different system by creating a new project or copying an existing project. For more information, see
Creating Migration Projects.

Source systems can be non-Unicode systems. These systems are connected to the SAP S/4HANA system by means of an RFC
connection. This means that the conversion to the SAP S/4HANA data model is done automatically when loading data to the SAP
S/4HANA migration cockpit.

 Note
It is not possible to use an SAP S/4HANA system as a source system.

To check whether your source system is compatible with your target SAP S/4HANA system, see SAP Note 3209755 .

Prerequisites

You can use the report Analyze SAP Notes to check whether all necessary SAP Notes are installed. For more information,
see SAP Note 3016862 .

You have installed the add-on DMIS_2011_1 SP23 or higher in the source system. This add-on is included in the license for
SAP S/4HANA. For more information, see the SAP S/4HANA Installation Guide and SAP Note 3209755 .

To access the Fiori application, you need to install SAP Fiori. For more information, see section Installation of SAP Fiori in
the SAP S/4HANA Installation Guide.

Roles and Authorizations

SAP S/4HANA Migration Cockpit users use RFC connections to connect the SAP S/4HANA migration cockpit to the source
system, but they do not access data in the source system directly. The RFC connection contains a remote user (or RFC user) that

This is custom documentation. For more information, please visit the SAP Help Portal 45
 11/2/24, 10:45 AM
accesses the data in the source system. You can use role SAP_DMIS_MC_DT_REMOTE to restrict the activities that can be
performed in the source system by this remote user.

Note the following when creating the RFC connnection:

The RFC user in the SAP source system must have the role SAP_DMIS_MC_DT_REMOTE. Ensure that you generate the
authorization profile for the role.

For security reasons, we recommend that this RFC user is a user of type Communication.

When creating the RFC connection, ensure that the option Trust Relationship has the value No.

To transfer data using the SAP S/4HANA migration cockpit, a user with the role SAP_CA_DMC_MC_USER is required in the SAP
S/4HANA system. This user must also have the role SAP_BR_CONFIG_EXPERT_DATA_MIG for the front-end server.

In addition, the corresponding role for each migration object is also required.

To use the SAP S/4HANA migration object modeler (transaction LTMOM), role SAP_CA_DMC_MC_DEVELOPER is required in the
SAP S/4HANA system.

If you want to develop your own source code rules, additional development authorizations are required. This means that the
additional authorization object S_DEVELOP is required with the following values:

DEVCLASS = < the development package that is used for the migration project >

OBJTYPE = 'CLAS'

OBJNAME = *

P_GROUP = *

ACTVT = 01, 02, 06

The values for the field ACTVT correspond to the actions that can be performed, namely:

01: Create (valid for all object types)

02: Change (valid for all object types)

06: Delete (valid for all object types)

Planning Your Migration Projects

SAP provides predefined migration objects that you can use to transfer data to a target SAP S/4HANA system. SAP can deliver
updated versions of these migration objects to your SAP S/4HANA system during the following events:

Upgrading your SAP S/4HANA system to a new release.

Implementing a new feature package or support package in your SAP S/4HANA system.

Implementing an SAP Note transport-based correction instruction (TCI) in your SAP S/4HANA system.

If SAP delivers updated versions of migration objects to your SAP S/4HANA system during one of the events listed above, the
updated migration objects are immediately available in all clients of the SAP S/4HANA system.

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 46
 11/2/24, 10:45 AM
In older releases, SAP delivered updated versions of migration objects to client 000 only. You were then required to load the
updated migration objects from client 000 to the relevant clients.

When you add a migration object to your project, the system uses the migration object provided by SAP as a template and makes a
copy of this migration object for your project.

When SAP delivers updated versions of migration objects to your SAP S/4HANA system, the migration objects in your projects are
not updated as they are copies of the migration objects provided by SAP.

SAP will deliver all available updated versions of migration objects during one of the events listed above. It is not possible, for
example, for SAP to only deliver an updated version of one specific migration object.

To understand how updates to migration objects will affect your existing projects, consider the following examples:

Example
A migration project contains migration object A and migration object B. SAP delivers updated versions of migration objects A and
B to your SAP S/4HANA system during one of the events listed above. The migration objects in the project are not updated to
reflect the latest version of the corresponding template migration objects. This is because the migration objects in the project are
copies of the migration objects provided by SAP.

Example
A migration project contains migration object A. SAP delivers an updated version of this migration object to your SAP S/4HANA
system during one of the events listed above. The migration object in the project is not updated to reflect the latest version of the
migration object delivered by SAP. However, you can add the updated version of migration object A to your project. To do this, you
use the option Create Migration Object from Template in transaction LTMOM.

Example
SAP delivers an updated version of migration object A to your SAP S/4HANA system during one of the events listed above. You now
want to use this updated migration object to transfer data to SAP S/4HANA. You create a new migration project, and add
migration object A. This new project contains the updated version of migration object A.

Recommendation

If you upgrade you SAP S/4HANA system to a new release, we strongly recommend creating completely new migration projects as
using older projects may result in technical issues.

The Migration Process

The general process for migrating data to SAP S/4HANA is as follows:

1. In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data app in
the Fiori Launchpad.

2. You create a migration project, and select the migration objects that are relevant for your project. Migration objects are
delivered by SAP, and describe how to migrate data from the source system (which tables are needed and the relationships
between the tables) to SAP S/4HANA.

Note that you typically first create a project in a development system. You then transport the project to a test system which
is a copy of the production SAP S/4HANA system. For each new test data migration, you transport a migration project that

This is custom documentation. For more information, please visit the SAP Help Portal 47
 11/2/24, 10:45 AM
includes any corrections or refinements identified in the previous test to the new test system. When you are finally ready to
transfer your data to the production SAP S/4HANA system, you can transport the project to the production system. For
more information, see Transporting Migration Objects to the Test System

3. For each migration object, the SAP S/4HANA migration cockpit selects the relevant data from the source system. Note that
the system selects data from the source system based on specific criteria. For example if you are using the migration
scenario SAP ERP to SAP S/4HANA, then you select data using company codes (you specify the relevant company codes
when creating a project).

4. For each migration object, you prepare the mapping tasks so that they can be processed.

5. For each migration object, you process any open mapping tasks.

There are mapping tasks associated with migration objects that must be processed before the migration can proceed.
Examples of mapping tasks include Value Mapping tasks (where you specify target values for corresponding source values)
and Fixed Value tasks (where you set default values for target fields).

6. Optional: You simulate the transfer of data to the target SAP S/4HANA system.

7. You migrate data for the migration object to the target SAP S/4HANA system.

Creating Migration Projects

Context

You use migration projects to facilitate the transfer of data from a source system to SAP S/4HANA. In order to migrate data to SAP
S/4HANA, you must first create a migration project. You use a migration project to specify the data that you want to transfer, and
to monitor the status of the migration.

You typically first create a project in a development system. You then transport the project to a test system which is a copy of the
production SAP S/4HANA system. The more the data in the test system resembles the data in the production system, the more
precise your test will be.

 Note
It is only possible to create projects in systems that have specific settings. These systems are typically development systems,
not productive or quality systems. For more information about these system settings, see SAP Note 3043614 .

 Note
You may want to use a different client or even a different source system for test purposes. However, if you want to connect to a
new source system or client, you need to create a new migration project or copy an existing project.

When you create a migration project that connects the SAP S/4HANA migration cockpit to a source system, the SAP S/4HANA
migration cockpit creates objects (for example ABAP dictionary and repository objects) in the source system. These objects
allow the SAP S/4HANA migration cockpit to select data from the source system. However, if you simply change the RFC
connection that is used by a migration project, these objects are not created in the new source system or client. You therefore
need to create a new project or copy an existing project if you want to migrate data from a different system or client.

Note that if your migration project uses a source system that is refreshed with new data, you also need to create a new
migration project or copy an existing project as the objects mentioned above will not be present in the refreshed source
system.

Usually, several test data migrations are required before you transfer data to the SAP S/4HANA production system. For each new
test data migration, you transport a migration project that includes any corrections or refinements identified in the previous test to
This is custom documentation. For more information, please visit the SAP Help Portal 48
 11/2/24, 10:45 AM
the new test system. If you have adjusted migration objects using the SAP S/4HANA migration object modeler (transaction
LTMOM), the changes need to be transported for any subsequent tests.

To avoid specifying all mapping values again in your newly created project, you can download the mapping values from your
previous test and upload them to your new project.

When you are finally ready to transfer your data to the SAP S/4HANA production system, you transfer your project the production
system. The migration is client-specific, so you transfer your project to the relevant client of the target SAP S/4HANA system.

To create a migration project, proceed as follows:

1. In the SAP S/4HANA system, you access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data app in
the Fiori Launchpad.

2. Choose Create and then Migrate Data Directly from SAP System. The system displays the New Migration Project screen.
Creating a project involves three steps. In the first step you specify general data for the project. In the second step you
specify the organizational units that are used to select data from the source system. Finally, in the third step, you select the
relevant migration objects.

3. Under General Data, you specify the following information:

Name

The name of the project.

Scenario

The migration scenario. The following migration scenarios are available:

SAP Apparel and Footwear (SAP AFS) to SAP S/4HANA

SAP ERP to SAP S/4HANA

SAP EWM to Decentralized EWM

SAP CRM to SAP S/4HANA for Customer Management

 Note
Different migration objects are relevant for different scenarios. The system displays the relevant migration
objects based on the selected scenario.

Connection to Source System

The RFC connection from the SAP S/4HANA system to the source system.

4. Choose the button Step 2.

5. Under Select Data, you specify the relevant criteria that is used to select the data for the relevant migration objects.

 Note
The Migration Cockpit uses organizational units such as company codes to select data from the source system. These
organizational units are predefined for each scenario. For example, the scenario SAP ERP to SAP S/4HANA uses
company codes to select data from the source system. Only data that is relevant for the specified organizational units
will be selected from the source system..

In the SAP S/4HANA migration cockpit you can only restrict the selection by using specific criteria such as company
codes. In the SAP S/4HANA migration object modeler (transaction LTMOM), you further restrict the selection if required.

6. Choose the button Step 3.

This is custom documentation. For more information, please visit the SAP Help Portal 49
 11/2/24, 10:45 AM
7. Under Migration Objects, the system displays the relevant migration objects based on the selected migration scenario. You
select the migration objects that are relevant for your project.

You can view the following information for the listed migration objects:

Name

The migration object name.

Predecessor

You can check whether the migration object has any predecessor objects (objects which must be processed before
the migration object).

Documentation

To view detailed documentation for the migration object, select the Documentation link.

8. Review your settings, and choose Create Project to create your project.

Copying Migration Projects

Context
You can create a new project that is a copy of an existing project, that contains all the migration objects, mapping tasks and
settings, including any custom changes. You specify a new name for the project, and can adjust the connection to the source
system and the selection criteria if required. Note that only the definition of the mapping tasks are copied to the new project. No
mapping values, or fixed values are copied.

Copying a project can make sense in the following situations:

Using templates

You can create one migration project that will act as template for other migration projects. You can then copy this project
multiple times to manage the migration in an efficient way. For example, you might copy the leading template project to a
new migration project which you would use to migrate data for a specific set of companies. You could then copy the leading
template project to another migration project which you would use to migrate data for the remaining companies.

Reusing successful projects

You want to reuse the settings of a successful project. For example, you may have successfully migrated some companies
in a migration project. Later you need to migrate data which requires a similar migration project setup. You can simply copy
the successful project and reuse it.

Creating similar migration projects in a test environment

You want to create similar migration projects in a test environment. You can copy your migration project and then just
adjust certain settings of the newly created projects for test purposes.

Transporting a project to a different system

You can copy a project so that it can be transported to another system. For example, a project might use a local
development package that cannot be transported to another system. You can copy this project and assign a development
package that can be transported. You can then transport this newly created project to a different system.

Procedure
1. On the Migration Project screen, select the project that you want to copy.

This is custom documentation. For more information, please visit the SAP Help Portal 50
 11/2/24, 10:45 AM
2. Choose the Copy button. The system displays the New Migration Project screen.

3. Specify a name for the project.

4. If required, you can specify a different connection to the source system. It is not possible to change the migration scenario.

5. Choose the button Step 2.

6. Under Development Package, you can specify a different development package if required.

7. Choose the button Step 3.

8. Under Select Data, you can adjust the criteria that is used to select the data for the migration objects.

9. Choose the button Step 4.

10. Under Migration Objects, the system displays the migration objects that will be copied to the new project. Note that it is
not possible to add additional objects, or to remove any migration objects in this step. If required, you can add additional
migration objects to the project once it has been created. Note that any migration objects that have the status Not Ready
for Processing will not be copied to the new project.

11. Review your settings and choose Create Project to create your project.

Transporting Migration Objects to the Test System

The following activities are only permitted in the development system:

Creating migration projects

Adding migration objects to migration projects

Adjusting migration objects

You can use transaction LTMOM to transport migration objects from the development system to the test system. If additional
adjustments to migration objects are required, you need to adjust the relevant migration object in the development system and
then transport the migration object to the test system again. In this way, the adjusted migration object will overwrite the migration
object in the test system.

After a successful test cycle, you can reset the test system and then transport the migration project from the development system
to the test system again.

This approach ensures that the status of your migration objects remain stable for your test cycles, even if updated versions of
migration object are available in the production system. This is important as you may want to continue testing with a migration
object, even if a newer version of the migration object is available in the development system.

However, if you create a new project in the development system or add a new version of a migration object in the development
system using transaction LTMOM, then the updated version of a migration object will be used for your tests. It is important to
consider this information when planning your test cycles.

The Migration Project Screen

When you open a migration project, the system displays the 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.

For each migration object, these steps are:

1. Selecting the data from the source system

2. Preparing the mapping tasks

3. Processing any open mapping tasks

This is custom documentation. For more information, please visit the SAP Help Portal 51
 11/2/24, 10:45 AM
4. Simulating the migration to the target SAP S/4HANA system (optional)

5. Migrating the data for the migration object to the target SAP S/4HANA system

You carry out these steps for each migration object that is part of your project. If a migration object has a predecessor object, the
predecessor object must be processed first. You can view whether a migration object has a predecessor object in the Migration
Object column.

The Migration Project screen contains the following columns:

Migration Object

In this column, you can view the name of the migration object. You can also view any predecessor objects. To view detailed
information about a migration object, click a migration object name in this column. The system displays the Migration
Object screen. For more information, see Additional Information About Migration Objects.

Data

In this column, you can view the number of migration object instances that have been selected from the source system for
each migration object. You can also view the number of excluded migration object instances.

Mapping Tasks

In this column, you can view the number of open and completed mapping tasks for each migration object.

Simulation

In this column, you can view the number of migration object instances that have been simulated successfully, and the
number of instances for which errors exist.

Migration

In this column, you can view the number of migration object instances that still have to be migrated to the to the target SAP
S/4HANA system, as well as the number of migration object instances that have been migrated successfully, and the
number of instances for which errors exist.

 Note
If not all transfer steps have completed successfully, then the relevant migration object instances will have the status
Partially Processed.

Migration Progress

In this column, you can view the status of the migration. If the migration has not started for a migration object, the text
Migration Not Started is displayed. If the migration has started for a migration object, you can view the following
percentage values:

Percentage of instances migrated successfully

Percentage of instances with errors

Percentage of instances not yet started

Action

In this column, you can trigger an action for a migration object. For example, you can start the simulation process for a
migration object.

Additional Information

Monitoring

To view a log of all activities, choose the Monitoring button. The system displays the Monitoring screen. You can view the active
activities (for example Migration Started) and completed activities (for example Migration Completed).
This is custom documentation. For more information, please visit the SAP Help Portal 52
 11/2/24, 10:45 AM
Settings

You can view the current settings for your project at any time by choosing the Settings button. The system displays the Project
Settings screen, where you can also change settings for the project, for example you can add additional migration objects and
change the number of jobs that are used for the project. For more information, see Project Settings.

Mapping Tasks

You can view a list of all mapping tasks for all the migration objects in your project. For more information about tasks, see Mapping
Tasks.

Finishing a Project

When you have finished your migration project, you can set the status of the project to Finished. When you set the status of a
project to Finished, no further changes are possible. However, you can still view the project. To set the status of a project to
Finished, choose the Finish button.

When you set the status of a project to Finished, you can specify a data retention period. The retention period is the length of time
(in days) that the project and all associated data is kept in both the SAP S/4HANA system and source system after you have set
the status of the project to Finished. Note that the data in the source system includes programs used to extract the data, as well
as information about the data that was transferred. To specify a retention period, set the option Data Retention Period to On. The
data will be deleted from both the SAP S/4HANA system and the source system when the retention period expires. If you set the
option Data Retention Period to Off, then the project and all associated data will be kept in the system indefinitely. If required, you
can change the retention time for finished projects. To do this, open the relevant project and choose the Settings button. You can
find the settings for retention period on the Technical Information tab.

 Note
If the project has not been deleted after the retention period, contact your system administrator to check that the retention job
(job /LTB/RETENTION) is running. For more information, see SAP Note 2997667 .

Project Settings
You can view the current settings for your project at any time by choosing the Settings button. The system displays the Project
Settings screen, where you can view the following information:

The migration project name.

If required, you can change the name of the migration project. To do this, choose the Edit button, and enter a new name in
the Name field.

The migration scenario.

The RFC connection from the SAP S/4HANA system to the source system.

In addition, you can view the following sections:

Select Data

Under Select Data, you can view the relevant criteria that is used to select the data for the relevant migration objects.

Migration Objects

Under Migration Objects, you can view the migration objects in the project. If required, you can add additional migration
objects to your project. To do this, choose the Edit button, select the relevant objects and choose Save.

This is custom documentation. For more information, please visit the SAP Help Portal 53
 11/2/24, 10:45 AM
History

Under History, you can view the different actions for the project (for example Project Created or Simulation Failed). You
can view the user that started the action as well as the start time and date and the end time and date. You can also view the
log for each action.

Technical Information

Under Technical Information, you can view the following information:

Data Retention Period

The retention period is the length of time (in days) that the project and all associated data is kept in the SAP
S/4HANA system and in the source system after you have set the status of the project to Finished. Note that the
data in the source system includes programs used to extract the data, as well as information about the data that
was transferred. If required, you can change the retention time for finished projects.

 Note
If the project has not been deleted after the retention period, contact your system administrator to check that
the retention job (job /LTB/RETENTION) is running. For more information, see SAP Note 2997667 .

Under Technical Information, you can also view general technical information about the project such as the object ID. If you
need to contact SAP for support, this information might be required.

Job Management
On the Job Management screen, you can adjust the maximum number of background jobs that are used for your project. The
default number of background jobs for a project is 15. If required, you can also adjust the number of background jobs for specific
migration objects. Note that if an activity has already started for a migration object, then increasing or decreasing the number of
jobs for the migration object will have no effect on that activity.

Example 1

You specify 5 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify 1
background job for migration object A and 1 job for migration object B. Result: 1 job will run in parallel to process migration object
A, and 1 job will run in parallel to process migration object B. The additional jobs specified for your project are not used in this case.

Example 2

You specify 8 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify
8 background jobs for migration object A and 5 jobs for migration object B. Result: A maximum of 8 jobs will be used for object A,
and a maximum of 5 jobs will be used for object B. The overall number of active background jobs for the project will not exceed 8
jobs.

Example 3

You specify 3 background job for your project (in the Maximum Number of Background Jobs for Project field). You then specify 3
background jobs for migration object A and 3 jobs for migration object B. Result: 3 jobs will process migration object A and
migration object B in a round robin procedure.

Additional Information About Migration Objects

The SAP S/4HANA migration cockpit uses migration objects to transfer data to the target SAP S/4HANA system. On the
Migration Project screen, the system displays the migration objects for your project. To get detailed information about a migration

This is custom documentation. For more information, please visit the SAP Help Portal 54
 11/2/24, 10:45 AM
object, click a migration object name in the Migration Object column. The system displays the Migration Object screen, where you
can view the following information:

Documentation

You can view detailed information about the migration object.

Table Structure

You can view the relevant source system tables for the migration object. The system displays the source system tables in a
hierarchy.

History

You can view a history of the events for the migration object. Examples of events include Simulation Started or Simulation
Completed. You can also view a log for the events. To do this, choose the View Log button. The system displays the Event
Log, where you can view messages for each event.

Dependencies

You view whether the migration object has any dependent migration objects. A migration object can have predecessor
objects (objects which must be processed before the migration object) and successor objects (objects which must be
processed after the migration object).

Configuration Options

You can view the active configuration options for the migration object. You can use configuration options for certain
migration objects to ensure that relevant data will be selected from the source system and migrated to the target system.
You can activate and deactivate configuration options for a migration object in the SAP S/4HANA migration object modeler.

Technical Information

Under Technical Information, you can view general technical information about the migration object such as the object ID.
If you need to contact SAP for support, this information might be required.

Viewing Messages
You can view the messages for the migration objects in a project at any time. On the Migration Project screen, select the relevant
migration objects and choose the Messages button. The system displays the Migration Object, Messages screen where you can
view the messages for the selected migration objects. You can view the number of migration object instances that are relevant for
each message and navigate directly to these migration object instances.

 Note
The retention period for messages is 180 days. Messages will be permanently deleted after this time.

By default, the system displays all messages that exist for the selected migration objects. You can restrict the messages to specific
migration objects if required.

You can use the following filter options to view the messages that you are interested in:

Action

The relevant action, for example Simulation or Migration. You can select an action to view the messages for that action.

Message Type

You can select a message type to view the messages of that message type. The following message types are possible:

This is custom documentation. For more information, please visit the SAP Help Portal 55
 11/2/24, 10:45 AM
Error

Error messages need to be processed before you can continue with the simulation or migration.

Warning

We recommend analyzing any warning messages to determine whether they are relevant for your migration project.

Success

Messages that indicate that a certain step was completed successfully. No further action is required.

Information

Messages that provide information about a certain step. No further action is required.

The system displays the following information for each message:

Type

Message

Action

The relevant action, for example Simulation or Migration.

Instances

In this column, the system displays the number of migration object instances that are relevant for the message. To view the
migration object instances, choose the number in this column.

Viewing Messages for Specific Migration Object Instances

On the Migration Project screen, you can view the number of migration object instances that have been simulated and migrated
successfully and the number of instances for which errors exist.

In the Simulation and Migration columns, the system displays the number of errors for a migration object. If you click this number,
the system displays the migration object instances that contain errors. Select the migration object instance that you want to
analyze, and choose the Messages button

You can view the following information for each message:

Type

The message type, for example Error or Warning.

Message

The message short text

Properties

The system displays the relevant migration object and also the event when the message occurred, for example during the
selection process or during the migration.

Date and Time

The date and time when the message occurred.

This is custom documentation. For more information, please visit the SAP Help Portal 56
 11/2/24, 10:45 AM

Selecting Data from the Source System

The SAP S/4HANA migration cockpit uses migration objects to transfer data to the target SAP S/4HANA system. The data for the
migration objects is selected from the source system based on specific criteria such as company codes. For example if you use
company codes, only data that is relevant for the specified company codes will be selected from the source system. In this way,
you restrict the data that is transferred to the target SAP S/4HANA system for the relevant migration objects.

 Note
In the SAP S/4HANA migration cockpit you can only restrict the selection by using specific criteria such as company codes. In
the SAP S/4HANA migration object modeler (transaction LTMOM), you further restrict the selection if required.

You need to start this process for each migration object in your project. You do this on the Migration Project screen by selecting
the relevant migration object, and choosing the action Select Data. Note that you can start the selection for multiple migration
objects if required. To do this, select the relevant migration objects and choose Actions and then Select Data.

 Note
On the Monitoring screen, you can cancel the selection process. Under Activities, select the relevant activity, for example
Select Data. In the Options field, you can then choose the option Cancel.

Monitoring the Status of the Selection Process

You can monitor the status of the migration for a migration object. On the Migration Project screen, choose the button
Monitoring. The system displays the Monitoring screen, where you can view the active and completed activities, for example
Selection Started or Selection Completed.

You can also view the total number of selected migration object instances for a migration object. For more information, click the
relevant number in the Data column.

Viewing the Selected Data

Context
On the Migration Project Screen, in the Data column, you can view the number of selected instances for a migration object.

A migration object represents a business object. For example, the migration object Bank represents the business object Bank. A
migration object instance is a set of one or more fields that have a defined relationship and that represent a business object
instance. For example, a migration object instance for the migration object Bank comprises several fields such as:

Bank Country Key

Bank Key

Bank Branch

Bank Group

Name of Bank *

Procedure

This is custom documentation. For more information, please visit the SAP Help Portal 57
 11/2/24, 10:45 AM
To view the data that has been selected by the system, click an entry in the Data column. The system displays the Migration
Object Instance screen, where you can view the records selected from the source system for each instance.

Example
You want to select data from the source system for the FI-GL Bank Key migration object. On the Migration Project screen, you
choose Actions and then Select. The system updates the Data column to indicate that four instances have been successfully
selected. You click the number in the Data column, and the system displays the Migration Object Instances screen where you can
view the following data:

Bank Country Key Bank Keys Bank Branch Bank Group Name of Bank

IN BANK_1 A1 YB Bank International

IN BANK_2 A2 YB Bank International

IN BANK_3 A1 YB Bank International

IN BANK_4 A1 YB Bank International

Each row represents one migration object instance, that is, the set of records that represent the FI-GL Bank Key business object
type. You can view the source system tables for the records by clicking a row. The system displays the source system tables in a
hierarchy.

The Migration Object Instances Screen

On the Migration Object Instances screen, you can view the records for each migration object instance. Each row represents one
migration object instance and contains the fields for the instance.

In addition, you can view the following columns:

Additional Fields

Each row can display up to five fields for a migration object instance. If a migration object instance contains more than five
fields, you can view the additional fields by choosing the Display All link in this column.

Current Step

If a migration object uses more than one transfer step to migrate migration object instances to SAP S/4HANA, the system
displays the current step in the Current Step column. For information about the transfer options and transfer steps for a
specific migration object, see the documentation for the migration object on the SAP Help Portal.

Action

The current action for the migration object instance. The following actions are possible:

Select Data

Mapping Tasks

Simulate

Migrate

Status

The status of the current action. An action can have one of the following status values:

Success

This is custom documentation. For more information, please visit the SAP Help Portal 58
 11/2/24, 10:45 AM
The records of the migration object instance have been successfully selected from the source system.

Information

An information message exists for the migration object instance. To view the message, select the migration object
instance and choose the Messages button.

Warning

A warning message exists for the migration object instance. To view the message, select the migration object
instance and choose the Messages button.

Error

An error exists for this migration object instance. To view more information about the error, choose the Messages
button.

Excluded

The migration object instance has been excluded from the migration.

The following options are also available:

View Messages for Migration Object Instances

You can view messages for a migration object instance. To do this, select the relevant instances and choose the Messages
button.

Simulate the Migration for Specific Migration Object Instances

You can simulate the migration for specific migration object instances. To do this, select the relevant instances and choose
the Simulate button.

Migrate Specific Migration Object Instances

You can migrate specific migration object instances. To do this, select the relevant instances and choose the Migrate
button.

Exclude Migration Object Instances

You can exclude a migration object instance. This means that the migration object instance will not be simulated or
migrated. To do this, select the relevant instances and choose the Exclude button. You can undo this action for an instance
by choosing Exclude and then Undo Exclude.

Mass Processing of Migration Object Instances

If you want to perform an action for a very large number of migration object instances, you can use the mass processing
function. To do this, choose the Mass Processing button.

Preparing the Mapping Tasks

Prerequisites
For a migration object, you have selected data from the source system.

Context
The mapping tasks for each migration object need to be prepared before they can be processed.

This is custom documentation. For more information, please visit the SAP Help Portal 59
 11/2/24, 10:45 AM

 Note
If you want to upload mapping values using Microsoft Excel, you do not need to prepare the mapping tasks.

Procedure
1. On the Migration Project screen, select the relevant migration object.

2. In the Action column, choose the option Prepare.

3. The system will prepare the mapping tasks so that they can be processed.

4. You can monitor the status of the preparation step in the Monitoring screen.

Mapping Tasks
After the system has selected the data for a migration object from the source system, you need to process any open mapping
tasks for the migration object before you can proceed with the simulation or the migration. Examples of mapping tasks include
Value Mapping tasks (where you specify target values for corresponding source values) and Fixed Value tasks (where you set
default values for target fields).

On the Migration Project screen, in the Mapping Tasks column, you can view the number of open and completed tasks for each
migration object.

If a migration object has open tasks, click the relevant entry in the Mapping Tasks column. The system displays the Mapping Tasks
screen. Alternatively, you can select the relevant migration object and choose the Mapping Tasks button.

 Note
You can also display all mapping tasks for a project by choosing the Mapping Tasks button located in the top right screen area.

Mapping Tasks Screen

On the Mapping Tasks screen, you can view the open mapping tasks (open mapping tasks have the status To be Confirmed) as
well as any confirmed mapping tasks. The system displays the mapping tasks in a list. You can view the following information for
each mapping task:

Mapping Tasks

The name of the task.

Status

The status of the mapping task. Mapping tasks can have the status Confirmed or To be Confirmed.

Type

The type of mapping task. There are Value Mapping tasks (where you specify target values for corresponding source
values) and Fixed Value tasks (where you set default values for target fields).

Values

The number of values for the task, for example a Value Mapping task could involve specifying 10 target values.

You need to process the task by entering the relevant target values, and confirming these target values. You can then set the status
of the task to Confirmed. Once all mapping tasks for a migration object have the status Confirmed, you can proceed with the
simulation or migration process for the migration object.

This is custom documentation. For more information, please visit the SAP Help Portal 60
 11/2/24, 10:45 AM

Value Mapping Tasks

For Value Mapping tasks, you specify target values for corresponding source values. On the Mapping Tasks screen, select the
relevant value mapping task that has the status To be Confirmed. The system displays the task in a new screen. On the left-hand
side, the system displays the task and the current status.

On the right-hand side of the screen the system displays the name of the task, and the following information:

Status

The status of the task. Mapping tasks can have the status Confirmed or To be Confirmed.

Type

The type of task. There are Value Mapping tasks (where you specify target values for corresponding source values) and
Fixed Value tasks (where you set default values for target fields).

Used In

The migration object that uses the task. If the task is used by more than one migration object, the system displays a link
with the text Migration Objects. You can click this link to view the migration objects that use the task.

Documentation

To view the documentation for the mapping task, click the Show link.

On the right-hand side, under Values. the system displays the values that need to be confirmed for the task. You can view the
following information:

Source Value

The value of the relevant field in the source system.

Target Value

The value of the corresponding field in the target system. By default, the system proposes the source value as the target
value.

Status

The status of the specific values (either Confirmed or To be Confirmed).

Action

Once you have entered a target value (or accepted the proposal provided by the system) you confirm the value for the task.
To do this, you can choose the Confirm button.

For each value that has the status To be Confirmed, you need to either enter a value in the Target Value field or accept the
proposal provided by the system (if provided). Note that a space is also considered a valid value. You then select the checkbox for
the relevant row and choose the Confirm button. Once all the values have the status Confirmed, the system changes the status of
the task to Confirmed on the Mapping Tasks screen.

Example
There are open value mapping tasks for the migration object FI-GL General Ledger Account. One of these open value mapping
tasks is the Company Code value mapping task. You use this task to check whether the target company codes need to be
changed, or if they should remain the same as the source system.

This is custom documentation. For more information, please visit the SAP Help Portal 61
 11/2/24, 10:45 AM
In this example, the company code 0001 remains the same as in the source system, but the data associated with company code
Z001 will now be assigned to company code ZZ99.

Source Company Code Target Company Code

0001 0001

Z001 ZZ99

Deleting Mapping Values

Context
You can delete the mapping values for value mapping tasks. You can delete specific mapping values for a mapping task, or you can
delete all mapping values for a mapping task. If you delete all mapping values for a mapping task, the relevant mapping task will no
longer be displayed on the Mapping Tasks screen. If you upload mapping values for the mapping task again, the mapping task will
be displayed on the Mapping Tasks screen once more.

 Note
Mapping values are required for simulating the migration and for migrating data. Deleting mapping values may cause errors or
may result in inconsistent data, especially if mapping values are used by multiple migration objects, or if mapping values were
created by the system (for example for internal numbering).

Procedure
1. On the Mapping Tasks screen, select the relevant mapping task. The system displays the mapping task in a new screen.

2. Under Values, select the relevant mapping values.

3. Choose the Delete Values button. The system will delete all the selected mapping values.

On the Mapping Tasks screen, you can delete all the mapping values for a mapping task. To do this, select the relevant
mapping task and choose the Delete Values button.

On the Monitoring screen, you can view the deleted mapping values. You can view information such as the user that deleted
the mapping values as well as the total number of mapping values that were deleted.

Fixed Value Tasks

For Fixed Value tasks, you specify default values for target fields. On the Mapping Tasks screen, select the relevant fixed value task
that has the status To be Confirmed. The system displays the task in a new screen.

On the left-hand side, the system display the task and the current status. On the right-hand side, under Values. the system
displays the value that needs to be confirmed for the task. You can view the following information:

Customizing

The value of the field in the target system. In some cases, the system will propose a suitable value for the target field.

Status

The status of the specific values (either Confirmed or To be Confirmed).

This is custom documentation. For more information, please visit the SAP Help Portal 62
 11/2/24, 10:45 AM
Action

Once you have entered a target value (or accepted the proposal provided by the system) you confirm the value for the task.
To do this, choose the Confirm button.

For each fixed value that has the status To be Confirmed, you need to either enter a value in the Customizing field or accept the
proposal provided by the system (if provided). You then select the checkbox for the fixed value and choose the Confirm button.

Example
There are open fixed value tasks for the migration object FI-GL Account Balance. One of these open fixed value tasks is the
Document Type fixed value task.

You need to define a document type that is used when the balances are created in the target SAP S/4HANA system. To do this, you
enter the value SA in the Customizing field of the Document Type fixed value task.

Downloading Template Files for Mapping Tasks

Context
Microsoft Excel template files are available for each mapping task. If you need to specify a large number of values for a mapping
task, you can use these template files instead of specifying the values manually in the SAP S/4HANA migration cockpit.

Procedure
1. On the Mapping Tasks screen, choose Download Mapping Templates.

2. Select the relevant mapping tasks and choose the Download button.

3. The system creates a zip file that contains the template files.

4. Populate the template files with data and save them locally.

A template file for a mapping task contains the following sheets:

Signature

On the Signature sheet, you can view the data type and length for the source and target fields.

Data

On the Data sheet, you specify values for the target SAP S/4HANA fields.

Uploading Mapping Values

Prerequisites
You have downloaded a template file for a mapping task and filled the file with data.

Context

You can upload mapping values for a mapping task.

This is custom documentation. For more information, please visit the SAP Help Portal 63
 11/2/24, 10:45 AM

Procedure
1. On the Mapping Tasks screen, choose Upload Values. The system displays the Upload Mapping Values screen.

2. On the Files tab, upload the file by using the Upload button or the drag and drop function. You can upload single files as well
as zip files.

Under Additional Settings, you can specify additional options for transferring the mapping values to the SAP S/4HANA
Migration Cockpit. These options include:

Options for Confirming Values

To set the status of the mapping values to Confirmed, choose the option Confirm Values Automatically. Otherwise,
choose Do Not Confirm Values Automatically.

Options for Loading Values

To delete any existing values for the task and replace them with the values from the file, choose the option Replace
Existing Values. If you choose the option Modify Values / Add Values, any duplicate values will be replaced with the
values from the file.

3. To upload the mapping values, choose Upload Values.

Simulating the Migration

Once you have processed all open tasks for a migration object, you can simulate the transfer of data to the target SAP S/4HANA
system. Note that no data is written to the target SAP S/4HANA system during the simulation process, but you can view all the
messages that would occur during an actual data transfer (for example information about a cost center that does not exist).

On the Migration Project screen, select the relevant migration object and choose Actions and then Simulate. The following
options are possible:

All Instances

The system can simulate the transfer for all migration object instances.

All Instances with Errors

The system can simulate the transfer for all migration object instances that have errors.

Random 10%

The system can simulate the transfer for a random 10% of the migration object instances.

Random 500

The system can simulate the transfer for a random 500 migration object instances.

 Note
You can also simulate the migration for specific migration object instances. You can do this on the Migration Object Instances
screen by selecting the relevant migration object instances and choosing the Simulate button. On the Migration Object
Instances screen, you can also exclude specific migration object instances. To do this, select the relevant migration object
instances and choose the Exclude button.

 Note
On the Monitoring screen, you can cancel the simulation process. Under Activities, select the relevant activity, for example
Simulate Data. In the Options field, you can then choose the option Cancel.

This is custom documentation. For more information, please visit the SAP Help Portal 64
 11/2/24, 10:45 AM

Monitoring the Status of the Simulation Process

You can monitor the status of the simulation for a migration object. On the Migration Project screen, choose the button
Monitoring. The system displays the Monitoring screen, where you can view the active and completed activities, for example
Simulation Started or Simulation Completed.

In addition, for a migration object, you can view the number of migration object instances that have been simulated successfully,
and the number of migration object instances that have errors. For more information, click the relevant number in the Simulation
column.

Migrating Data to the SAP S/4HANA System

Once you have processed all open tasks for a migration object, you can transfer data to the target SAP S/4HANA system. Note
that we recommend that you first simulate the migration.

On the Migration Project screen, select the relevant migration object and choose the action Migrate.

The system displays the New Migration dialog box, where you can choose one of the following options:

All Instances

The system can migrate all migration object instances.

All Instances with Errors

The system can migrate all migration object instances that have errors.

Random 10%

The system can migrate a random 10% of the migration object instances.

Random 500

The system can migrate a random 500 migration object instances.

All Successfully Simulated Instances

The system can migrate all simulated successfully instances.

 Note
You can also migrate specific migration object instances. You can do this on the Migration Object Instances screen by selecting
the relevant migration object instances and choosing the button Migrate. On the Migration Object Instances screen, you can
also exclude specific migration object instances. To do this, select the relevant migration object instances and choose the
Exclude button.

 Note
On the Monitoring screen, you can cancel the migration process. Under Activities, select the relevant activity, for example
Migrate Data. In the Options field, you can then choose the option Cancel.

Finishing a Project

This is custom documentation. For more information, please visit the SAP Help Portal 65
 11/2/24, 10:45 AM
When you have finished your migration project, you can set the status of the project to Finished. When you set the status of a
project to Finished, no further changes are possible. However, you can still view the project. To set the status of the project to
Finished, choose the Finish button.

When you set the status of a project to Finished, you can specify a data retention period. The retention period is the length of time
(in days) that the project and all associated data is kept in both the SAP S/4HANA system and source system after you have set
the status of the project to Finished. Note that the data in the source system includes programs used to extract the data, as well
as information about the data that was transferred. To specify a retention period, set the option Data Retention Period to On. The
data will be deleted from both the SAP S/4HANA system and the source system when the retention period expires. If you set the
option Data Retention Period to Off, then the project and all associated data will be kept in the system indefinitely. If required, you
can change the retention time for finished projects. To do this, open the relevant project and choose the Settings button. You can
find the settings for retention time on the Technical Information tab.

 Note
If the project has not been deleted after the retention period, contact your system administrator to check that the retention job
(job /LTB/RETENTION) is running. For more information, see SAP Note 2997667 .

Monitoring the Status of the Migration Process

On the Migration Project screen, you can monitor the status of the migration for a migration object. If the migration has started
for a migration object, you can view the following percentage values in the Migration Progress column:

Percentage of instances migrated successfully

Percentage of instances with errors

Percentage of instance not yet started

You can also view the number of migration object instances that have been migrated successfully, and the number of migration
object instances that have errors. For more information, click the relevant number in the Migration column.

You can also view more detailed information about the status of the migration. On the Migration Project screen, choose the button
Monitoring. The system displays the Monitoring screen, where you can view the active and completed activities, for example
Migration Started or Migration Completed.

Viewing the Migration Results

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.

Migration objects can use different transfer options to migrate different types of migration object instances to SAP S/4HANA.
Most migration objects have just one transfer option, but some have more than one. A transfer option uses different transfer steps
to migrate a migration object instance to SAP S/4HANA. The number of migration result fields depends on the number of transfer
options and transfer steps that are used by the migration object.

 Note
For more information about transfer options and transfer steps, see Transfer Options and Transfer Steps. For information about
the transfer options and transfer steps for a specific migration object, see the documentation for the migration object on the
SAP Help Portal.

This is custom documentation. For more information, please visit the SAP Help Portal 66
 11/2/24, 10:45 AM
If a migration object uses a transfer option that has one transfer step, the system displays one additional field, for example Result
of Step "Create Bank".

If a migration object uses one transfer option that has more than one migration step, the system displays an additional field for
each step. For example, Result of Step 1 "Create Asset with Balances" and Result of Step 2 "Post to Asset".

If a migration object uses more than one transfer option, the system displays an additional field for each option and step
combination.

You can also navigate directly to the relevant SAP Fiori app for the migration object to view the newly created data. To do this, click
an entry in the Result column. Note that there are prerequisites for accessing apps, such as required business roles. For more
information, see the documentation for the relevant migration object on the SAP Help Portal.

Transfer Options and Transfer Steps

Migration objects can use different transfer options to migrate different types of migration object instances to SAP S/4HANA.
Most migration objects have just one transfer option, but some migration objects have more than one, for example MM - Purchase
Scheduling Agreement.

When the SAP S/4HANA migration cockpit selects a migration object instance from the source system for a migration object, it
determines the type, and assigns it to the relevant transfer option. The transfer option then uses one or more transfer steps to
migrate a migration object instance to SAP S/4HANA.

 Note
For information about the transfer options and steps for a specific migration object, see the documentation for the migration
object on the SAP Help Portal.

Example
When migrating migration object instances for the migration object Fixed Asset (Including Balances), the SAP S/4HANA
migration cockpit needs to first create the asset in the SAP S/4HANA system and then post the value of the asset to this newly
created asset. Each step uses a function module to create the migration object instance in SAP S/4HANA.

In the following table, you can view the transfer options and transfer steps for the migration object Fixed Asset (Including
Balances).

Transfer Option Condition Step 1 Step 2 Step 3

Migrate Asset The migration object Create Asset with Post to Asset N/A
instance is classified as Balances
an asset.

A Detailed View of the Migration Process

You use the Detailed View to get a more comprehensive overview of the migration process. You can control the migration process
in a more detailed way, for example you can start the simulation for the migration object instances that belong to a specific
transfer step.

You can access the Detailed View screen from the Migration Project screen. In the Migration Progress column, there is a Detailed
View link for each migration object.

This is custom documentation. For more information, please visit the SAP Help Portal 67
 11/2/24, 10:45 AM

 Note
The Detailed View screen provides an overview of the transfer options and transfer steps for a migration object. We
recommend only using this view if you are familiar with the transfer options and transfer steps for your migration object. For
more information, see Transfer Options and Transfer Steps.

The Detailed View screen is divided into the following sections:

Select Data

Under Select Data, the system displays the node Selected Instances. Here, you can view the following information:

Instances

The total number of migration object instances selected from the source system.

Not Processed

The number of migration object instances for which the action Prepare Mapping Tasks has not been started. These are the
migration object instances that will be considered if you start the Prepare Mapping Tasks action using the Detailed View.

Excluded

The number of excluded migration object instances.

Note that you start the Select Data action on the Migration Project screen.

Prepare Mapping Tasks

Under Prepare Mapping Tasks, the system displays the node Mapping Tasks Prepared for Instances.

Here, you can view the migration object instances that have successfully prepared mapping tasks, as well as any instances for
which the action Prepare Mapping Tasks ended with errors.

To prepare the mapping tasks for specific instances, choose the Process button. The system displays the Instances for Prepare
Mapping Tasks popover. Select the relevant instances and choose the Prepare Mapping Tasks button.

 Note
If the migration object has more than one transfer option, then the system displays an additional path for each transfer option.
For more information, see Transfer Options and Transfer Steps.

 Note
Before you can proceed with the simulation and migration, you need to process any open mapping tasks. You can navigate to
the open mapping tasks by choosing the button Open Mapping Tasks.

Simulate Step 1

Under Simulate Step 1, the system displays a node for transfer step 1. Here, you can view the migration object instances that
belong to transfer step 1. You can view the migration object instances that have been simulated successfully and any instances
that have errors.

To simulate the migration for specific instances that belong to transfer step 1, choose the Process button. The system displays the
Instances for Simulation popover. Select the relevant instances and choose the Simulate button.

This is custom documentation. For more information, please visit the SAP Help Portal 68
 11/2/24, 10:45 AM

 Note
If the migration object has more than one transfer option, then the system displays an additional path for each transfer option.
For more information, see Transfer Options and Transfer Steps.

 Note
For certain migration objects, it is not possible to simulate the migration of data to SAP S/4HANA. For these migration objects,
the relevant simulation step is not displayed on the Detailed View screen.

Migrate Step 1

Under Migrate Step 1, the system displays a node for transfer step 1. Here, you can view the migration object instances that belong
to transfer step 1. You can view the migration object instances that have been migrated successfully and any instances that have
errors.

To migrate specific instances, choose the Process button. The system displays the Instances for Migration popover. Select the
relevant instances and choose the Migrate button.

 Note
If the migration object has more than one transfer option, then the system displays an additional path for each transfer option.
For more information, see Transfer Options and Transfer Steps.

Simulate Step 2

If the transfer option has more than one transfer step, the system displays the section Simulate Step 2.

Under Simulate Step 2, the system displays a node for transfer step 2. Here, you can view the migration object instances that
belong to transfer step 2. You can view the migration object instances that have been simulated successfully and any instances
that have errors.

To simulate the migration for specific instances that belong to transfer step 1, choose the Process button. The system displays the
Instances for Simulation popover. Select the relevant instances and choose the Simulate button.

 Note
If the migration object has more than one transfer option, then the system displays an additional path for each transfer option.
For more information, see Transfer Options and Transfer Steps.

 Note
The simulation may result in new mapping tasks. You need to process these mapping tasks. We recommend that you then
repeat the simulation before proceeding with the migration. You can navigate to the open mapping tasks by choosing the
button Open Mapping Tasks.

Migrate Step 2

If the transfer option has more than one transfer step, the system displays the section Migrate Step 2.

Under Migrate Step 2, the system displays a node for transfer step 2. Here. you can view the migration object instances that
belong to transfer step 2. You can view the migration object instances that have been migrated successfully and any instances that
have errors.

This is custom documentation. For more information, please visit the SAP Help Portal 69
 11/2/24, 10:45 AM
To migrate specific instances, choose the Process button. The system displays the Instances for Migration popover. Select the
relevant instances and choose the Migrate button.

 Note
If the migration object has more than one transfer option, then the system displays an additional path for each transfer option.
For more information, see Transfer Options and Transfer Steps.

Simulate Step 3 / Migrate Step 3

If the transfer option has a third transfer step, the system displays the sections Simulate Step 3 and Migrate Step 3.

Migration Summary

Under Migration Summary, you can view the number of migration object instances that have been successfully migrated to SAP
S/4HANA.

Transfer Options and Transfer Steps

Migration objects can use different transfer options to migrate different types of migration object instances to SAP S/4HANA.
Most migration objects have just one transfer option, but some migration objects have more than one, for example MM - Purchase
Scheduling Agreement.

When the SAP S/4HANA migration cockpit selects a migration object instance from the source system for a migration object, it
determines the type, and assigns it to the relevant transfer option. The transfer option then uses one or more transfer steps to
migrate a migration object instance to SAP S/4HANA.

 Note
For information about the transfer options and steps for a specific migration object, see the documentation for the migration
object on the SAP Help Portal.

Example
When migrating migration object instances for the migration object Fixed Asset (Including Balances), the SAP S/4HANA
migration cockpit needs to first create the asset in the SAP S/4HANA system and then post the value of the asset to this newly
created asset. Each step uses a function module to create the migration object instance in SAP S/4HANA.

In the following table, you can view the transfer options and transfer steps for the migration object Fixed Asset (Including
Balances).

Transfer Option Condition Step 1 Step 2 Step 3

Migrate Asset The migration object Create Asset with Post to Asset N/A
instance is classified as Balances
an asset.

SAP S/4HANA Migration Object Modeler

The SAP S/4HANA migration object modeler is an application that can be used to enhance the migration objects that are used in
the SAP S/4HANA migration cockpit. You can access the SAP S/4HANA migration object modeler by using transaction LTMOM.

This is custom documentation. For more information, please visit the SAP Help Portal 70
 11/2/24, 10:45 AM

 Note
The functions and features offered by the SAP S/4HANA migration object modeler depend on the migration approach of your
SAP S/4HANA Migration Cockpit project. Detailed documentation for the SAP S/4HANA migration object modeler can be
accessed directly from transaction LTMOM.

Read Access Logging Configurations in Migration Cockpit

You can use the Read Access Logging (RAL) report to configure which read-access information to log in the system and under
which conditions.

SAP delivers sample configurations for applications. By default, the RAL configuration is inactive.

In the scenario Migrate Data Using Staging Tables of the Migration Cockpit (CA-LT-MC), users can read the uploaded data
records. In order to identify the users who preview data, RAL logs the name of the staging table or file (if files are used to upload
data) containing the data, together with the name of the user who opened this file.

In the scenario Migrate Data Directly from SAP System of the Migration Cockpit (CA-LT-MC), users can read the selected
migration object instances, uploaded mapping tasks, and migration object history. In order to identify the users who preview this
data, RAL logs the migration object instance together with the name of the user who accessed the data.

In the following configurations, fields are logged in combination with additional fields, in the following business contexts:

Channel Configuration Description Fields Logged

OData CA-LT  Note

(Version The following fields are relevant for the scenarios Migrate Data Using Staging Tables and
RAL Configuration for
2.0) Migrate Data Directly from SAP System
ODATA Service
/LTB/MIG_MC_ODATA_SRV
Migration Instance ID (:Entity
Types:MigrationInstance:MIGRATIONINSTANCEUUID)

Migration Object ID (:Entity Types:TaskItem:MIGRATIONOBJECTUUID)

Mapping Task ID (:Entity Types:TaskItem:MIGRATIONTASKUUID)

Mapping Task Status (:Entity Types:TaskItem:TASKITEMSTATUS)

Mapping Task Status ID (:Entity Types:TaskItem:TASKITEMSTATUSUUIDD)

Migration Instance Title(:Entity Types:MigrationInstance:INSTANCETITLE)

Migration Instance Item field 1 (:Entity Types:MigrationInstance:ITEMFIELD1)

Migration Instance Item field 2 (:Entity Types:MigrationInstance:ITEMFIELD2)

Migration Instance Item field 3 (:Entity Types:MigrationInstance:ITEMFIELD3)

Migration Instance Item field 4 (:Entity Types:MigrationInstance:ITEMFIELD4)

Migration Instance Item field 5 (:Entity Types:MigrationInstance:ITEMFIELD5)

Migration Instance Item field 6 (:Entity Types:MigrationInstance:ITEMFIELD6)

Migration Instance Item field 7 (:Entity Types:MigrationInstance:ITEMFIELD7)

Migration Instance Item field 8 (:Entity Types:MigrationInstance:ITEMFIELD8)

This is custom documentation. For more information, please visit the SAP Help Portal 71
 11/2/24, 10:45 AM

Channel Configuration Description Fields Logged

Migration Instance Item field 9 (:Entity Types:MigrationInstance:ITEMFIELD9)

Migration Instance Item field 10 (:Entity Types:MigrationInstance:ITEMFIELD10

Migration Instance Item field 11 (:Entity Types:MigrationInstance:ITEMFIELD11

Migration Instance Item field 12 (:Entity Types:MigrationInstance:ITEMFIELD12

Migration Instance Item field 13 (:Entity Types:MigrationInstance:ITEMFIELD13

Migration Instance Item field 14 (:Entity Types:MigrationInstance:ITEMFIELD14

Migration Object ID (:Entity Types:MigrationInstance:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity Types:MigrationInstance:MIGRATIONPROJECTUUI

Migration Object Application log number (:Entity

Types:MigrationObjectHistory:APPLLOGNR)

Migration Object History ID (:Entity

Types:MigrationObjectHistory:MIGRATIONOBJECTHISTORYUUID)

Migration Object ID (:Entity

Types:MigrationObjectHistory:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity

Types:MigrationObjectHistory:MIGRATIONPROJECTUUID)

Migration Object History Event Started by Someone (:Entity

Types:MigrationObjectHistory:STARTEDBY)

Download Mapping Task File (:Function

Imports:DownloadMappingTaskFileRALMonitor:ACTIVITYUUID)

Download Mapping Task File (:Function

Imports:DownloadMappingTaskFileRALMonitor:DOWNLOADOPTION)

Download Mapping Task File (:Function

Imports:DownloadMappingTaskFileRALMonitor:MIGRATIONPROJECTUUID)

Download Mapping Task File (:Function

Imports:DownloadMappingTaskFileRALMonitor:MIGRATIONTASKUUID)

Download Migration Object Messages File (:Function

Imports:DownloadMigrationObjectMessageRALMonitor:DOWNLOADACTIVITYID

Download Migration Object Messages File (:Function

Imports:DownloadMigrationObjectMessageRALMonitor:MIGRATIONOBJECTUUI

Download Migration Object Messages File (:Function

Imports:DownloadMigrationObjectMessageRALMonitor:MIGRATIONPROJECTUU

Download Migration Result File (:Function

Imports:DownloadMigrationResultRALMonitor:DOWNLOADACTIVITYID)

Download Migration Result File (:Function

Imports:DownloadMigrationResultRALMonitor:MIGRATIONOBJECTUUID)

Download Migration Result File (:Function

Imports:DownloadMigrationResultRALMonitor:MIGRATIONPROJECTUUID)

Migration Object Instances Message (:Function

Imports:MigrationObjectMessageRALMonitor:MIGRATIONPROJECTUUID)

This is custom documentation. For more information, please visit the SAP Help Portal 72
 11/2/24, 10:45 AM

Channel Configuration Description Fields Logged

Migration Object Instances Message (:Function

Imports:MigrationObjectMessageRALMonitor:MIGRATIONOBJECTUUID)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:APPLLOGNR)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:DISPLAYOPTION)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MIGRATIONHISTORYUUID)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MIGRATIONOBJECTUUID)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MIGRATIONPROJECTUUID)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MSGMSGID)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MSGMSGNO)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MSGMSGTY)

Download Messages (:Function

Imports:DownloadShowMessagesRALMonitor:MSGUUID)

Download Message Details (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:DISPLAYOPTION)

Download Message Details (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:MESSAGEGROUPUUID)

Download Message Details (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:MESSAGEUUID)

Download Message Details (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:MIGRATIONINSTANCEUU

Download Message Details (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:MIGRATIONOBJECTUUID

Download Message Details (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:MIGRATIONPROJECTUUI

Download Instance Message Details (:Function

Imports:DownloadInstanceMessageDetailRAL:MESSAGEGROUPUUID)

Download Instance Message Details (:Function

Imports:DownloadInstanceMessageDetailRAL:MIGRATIONOBJECTUUID)

Download Instance Message Details (:Function

Imports:DownloadInstanceMessageDetailRAL:MIGRATIONPROJECTUUID)

 Note
The following fields are only relevant for the scenario Migrate Data Using Staging Tables.

Migration Object Staging Table Contents (:Entity Types:TableData:COMBINEDCOLUM

This is custom documentation. For more information, please visit the SAP Help Portal 73
 11/2/24, 10:45 AM

Channel Configuration Description Fields Logged

Migration Object Staging Table Generated Key (:Entity

Types:TableData:GENERATEDKEY)

Migration Object Instance ID (:Entity Types:TableData:MIGRATIONINSTANCEUUID

Migration Object ID (:Entity Types:TableData:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity Types:TableData:MIGRATIONPROJECTUUID)

Migration Object File Created by Someone (:Entity Types:MigrationFile:CREATED

Migration Object File Name (:Entity Types:MigrationFile:FILENAME)

Migration Object File ID (:Entity Types:MigrationFile:MIGRATIONFILEUUID)

Migration Object ID (:Entity Types:MigrationFile:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity Types:MigrationFile:MIGRATIONPROJECTUUID)

Migration Object Correction File Name (:Entity

Types:MigrationGroupIndicator:GROUPINDICATOR)

Migration Object ID (:Entity

Types:MigrationGroupIndicator:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity

Types:MigrationGroupIndicator:MIGRATIONPROJECTUUID)

Migration Object File Content (:Entity Types:MigrationFileContent:FILECONTEN

Migration Object File ID (:Entity

Types:MigrationFileContent:MIGRATIONFILEUUID)

Migration Object ID (:Entity Types:MigrationFileContent:MIGRATIONOBJECTUU

Migration Project ID (:Entity

Types:MigrationFileContent:MIGRATIONPROJECTUUID)

Migration Object Staging Table Identifier (:Entity

Types:MigrationFileContent:TABLEIDENT)

Migration Object Download Activity ID (:Entity

Types:MigrationFileTemplate:DOWNLOADACTIVITYID)

Migration Object ID (:Entity

Types:MigrationFileTemplate:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity

Types:MigrationFileTemplate:MIGRATIONPROJECTUUID)

Migration Object File Process ID (:Entity

Types:DownloadMigrationFile:MIGRATIONFILEPROC)

Table ID (:Entity Types:TableData:TABLEUUID)

Download Correction File (:Function

Imports:DownloadCorrectionFileRALMonitor:DOWNLOADACTIVITYID)

Download Correction File (:Function

Imports:DownloadCorrectionFileRALMonitor:MIGRATIONOBJECTUUID)

Download Correction File (:Function

Imports:DownloadCorrectionFileRALMonitor:MIGRATIONPROJECTUUID)

This is custom documentation. For more information, please visit the SAP Help Portal 74
 11/2/24, 10:45 AM

Channel Configuration Description Fields Logged

Download Uploaded File (:Function

Imports:DownloadUploadedFileRALMonitor:MIGRATIONFILEPROC))

Data Migration Status

App ID: F3280

With this app, you can check the status of any simulated or migrated instances in your migration projects.

 Note
The Data Migration Status app supports only the Migrate Data Using Staging Tables migration approach.

Key Features

You can use this app to do the following:

Get an overview of your migration objects and projects in real time.

Use filters and change view settings to drill down into reports faster.

See detailed statuses for all instances.

Get info about all messages.

See running jobs at a glance and get notifications.

Log and display extended statistics.

Audit data using the built-in audit function.

Navigate to the standard SAP Fiori app directly from each instance.

Export reports to spreadsheet files.

This is custom documentation. For more information, please visit the SAP Help Portal 75
 11/2/24, 10:45 AM

Situation Handling
This app uses Situation Handling, which automatically informs users responsible about matters that require their attention. For
more information, see Situation Handling for Data Migration.

Related Information
Data Migration Status in the SAP Fiori Apps Reference Library.

See the Data Migration to SAP S/4HANA from Staging (2Q2 ) test script.

Find frequently asked questions relating to the Data Migration Status app in SAP Knowledge Base Article 2681413 .

Quick Info
Use these SAP Help Portal aliases to access the following sections of our product assistance:

Type this in your browser... To jump to...

http://help.sap.com/S4_OP_DM_STATUS this very topic: Data Migration Status

http://help.sap.com/S4_OP_DM the landing page for data migration

http://help.sap.com/S4_OP_MO the entry topic: Available Migration Objects

Supported Device Types

Desktop

Tablet

Roles and Authorizations

To use the Data Migration Status app, a user with the role SAP_CA_DMCC_APPS or SAP_CA_DMCC_AUDIT is required in the SAP
S/4HANA system. This user must also have the role SAP_BR_CONFIG_EXPERT_DATA_MIG for the front-end server.

Role Overview

Technical Role Name Role Description Authorization

SAP_CA_DMCC_APPS S/4 Migration - Content Application Data Migration Status app without audit
authorizations

SAP_CA_DMCC_AUDIT S/4 Migration - Content Status App Audit Data Migration Status app with audit
authorizations

Changing a View

Context
This is custom documentation. For more information, please visit the SAP Help Portal 76
 11/2/24, 10:45 AM
You can change the view settings for every pane. View Settings include column visibility, sorting of records, filters to include or
exclude certain records, and grouping.

Procedure
1. Choose  (Settings). The View Settings dialog box appears. This is where you can change the following settings:

Columns: Display or hide columns by selecting or deselecting the respective checkbox.

Sort: Sort a specific column in ascending or descending order.

Filter: Set filters to include or exclude specific information.

Group: Group information based on a specific characteristic.

2. Change the required settings.

3. Choose OK to save your settings.

Saving a View

Context
You can save regularly used view settings as views.

Procedure
1. Apply all View Settings that you want to save as described under Changing a View.

2. Choose the arrow right next to Standard in the header, and choose Save As.

3. Enter a name for this view and select the boxes for the settings that you want to apply, for example, Set as Default.

4. When you've finished, Save your view.

Results
You can now select the saved view by choosing the arrow right next to Standard in the header.

Extended Statistics
The Data Migration Status app provides logging of extended statistics.

This is custom documentation. For more information, please visit the SAP Help Portal 77
 11/2/24, 10:45 AM

Extended Statistics on Migration Object Level

In the Extended Statistics column in the Migration Objects overview table, three different statuses can be displayed for a
migration object:

Statistics: This means that logging of extended statistics is activated, and data are available.

Choose Statistics to find an overview of all logged statistics for a specific migration object in all available projects.

No Data: This means that logging of extended statistics is activated, and data will be available after the next migration run.

Turned off: This means that logging of extended statistics is deactivated for this migration object.

 Note
Due to the type and amount of underlying data, the extended statistics feature might not be available for all migration objects.

Extended Statistics on Instance Level

To find detailed statistics on instance level, proceed as follows.

1. Drill down on a migration object and choose the instance you're interested in.

2. A new panel opens for the instance. Use the dropdown menu and select Statistics, or scroll down to the Statistics section
manually.

Here you find detailed statistics for this instance, if available.

Turning On Logging of Extended Statistics

Context
Per default, logging of extended statistics is turned off. You can change the logging settings for extended statistics per migration
object.

Procedure
1. Choose Set Extended Statistics in the upper right corner of the screen.

2. In the Set Extended Statistics dialog box, switch the toggle button in the Log Extended Statistics column to ON for the
required migration objects.

3. Then, Save your changes.

Customizing Extended Statistics

This is custom documentation. For more information, please visit the SAP Help Portal 78
 11/2/24, 10:45 AM

Context
You can customize the categories, which are displayed for a migration object.

Procedure
1. In the Migration Objects overview table in the Extended Statistics column, choose Statistics.

2. Choose Select Categories. The Select Categories for Breakdown dialog box is displayed.

3. Select all checkboxes next to the required categories for breakdown.

4. Then, save your changes and close the Select Categories for Breakdown dialog box. The Statistics dialog box now displays
statistics for all selected categories when you open it the next time.

Exporting Extended Statistics

Context
You can export your statistics to a spreadsheet file on migration object level.

For active categories in the root structure, the exported file contains all information available.

For substructures, it only contains the number of records.

Procedure
1. In the Migration Objects overview table in the Extended Statistics column, choose Statistics.

2. In the dialog box, choose Export Statistics. The download of the file starts automatically, once it is generated.

Turning Off Logging of Extended Statistics

Context
You can change the logging settings for extended statistics per migration object.

 Caution
Switching off Log Extended Statistics not only stops new data from being logged, it also deletes previously logged data.

Procedure
1. Choose Set Extended Statistics in the upper right corner of the screen.

2. In the Set Extended Statistics dialog box, switch the toggle button in the Log Extended Statistics column to OFF for the
required migration objects.

3. Then, Save your changes.

Audit Feature
Use the audit function to audit your imported records.

This is custom documentation. For more information, please visit the SAP Help Portal 79
 11/2/24, 10:45 AM
Assigning Random Records for Auditing

Selecting Records for Auditing Manually

Setting the Audit Status in the App

Setting the Audit Status Offline in a Worklist

Assigning Random Records for Auditing

Context
To assign random imported records for auditing, proceed as follows.

Procedure
1. In the Migration Objects overview table, choose a migration object for which you want to assign random records for
auditing.

2. Then, choose Manage Multiple Audit Statuses Mass Select Records for Audit Random Selection .

3. In the dialog box, choose Units, to define a certain number of records, or %, to define a certain percentage of imported
records. Then, enter the required quantity of records to be assigned for auditing.

4. Then, choose Audit Object. This changes the Audit Status for the selected number of imported records to Pending.

 Tip
You can use the dropdown list on the left to filter for Audit Approved, Audit Rejected, or Audit Pending.

Selecting Records for Auditing Manually

Context
In addition to Assigning Random Records for Auditing, you can also choose the records for auditing manually.

Procedure
1. In the Migration Objects overview table, choose a migration object for which you want to assign records for auditing.

2. Then, choose Manage Multiple Audit Statuses Mass Select Records for Audit Manual Selection: Download
Spreadsheet .

3. Open the downloaded Auditing Template spreadsheet file.

4. Fill out the auditing template for all records that you want to add for auditing with the same values that you've already used
in the migration template that you've uploaded in the Migrate Your Data – Migration Cockpit app. Additionally, you might
need to specify the Migration Project ID in the auditing template, if you use the same migration object records in multiple
migration projects. SAP provides a Help tab in the downloaded auditing template that lists all migration project IDs that this
migration object is used in together with their description.

5. Save your changes in the spreadsheet file.

6. In the Data Migration Status app, choose Manage Multiple Audit Statuses Mass Select Records for Audit Manual
Selection: Upload Spreadsheet .

7. In the dialog box, choose Browse... to select the auditing template to upload. Then, choose Upload. This changes the Audit
Status for the selected imported records to Pending.

 Tip

This is custom documentation. For more information, please visit the SAP Help Portal 80
 11/2/24, 10:45 AM
You can use the dropdown list on the left to filter for Audit Approved, Audit Rejected, or Audit Pending.

Setting the Audit Status in the App

Procedure
1. In the Migration Objects overview table, choose a migration object for which you want to audit instances for.

2. Choose the instance you want to set the status for, and choose Set Audit Status.

3. In the dialog box, on the Action tab, you can choose one of the following statuses: Approved, Pending, or Rejected.
Moreover, you can leave a comment in the Notes text area.

4. Then, Save your changes.

 Tip
On the History tab in the dialog box, you can always check the auditing history for an instance and see all related notes.

Setting the Audit Status Offline in a Worklist

Context
You can download a worklist that includes all records with the audit status Pending for setting the audit status offline.

Procedure
1. In the Migration Objects overview table, choose a migration object for which you want to audit records for.

2. Choose Manage Multiple Audit Statuses Download Audit Worklist .

3. Open the downloaded spreadsheet file.

4. Set the audit status in the Audit Status column of the spreadsheet file. Enter 1 to set the audit status to Approved, or enter
2 to set the audit status to Rejected. Moreover, you can leave a comment in the Comment column.

5. Save your changes in the spreadsheet file.

6. In the Data Migration Status app, choose Manage Multiple Audit Statuses Upload Audit Worklist .

7. In the dialog box, choose Browse... to select the audited worklist to upload. Then, choose Upload. This changes the Audit
Status for the respective records.

Navigating to Standard SAP Fiori Apps

Context
From the Data Migration Status app, you can directly navigate to the respective standard SAP Fiori app.

Procedure
1. In the Migration Objects overview table, choose a migration object.

2. Then, choose the target ID of an imported instance. A dialog box with additional target IDs (if any) and a link to the
respective SAP Fiori app is displayed.

This is custom documentation. For more information, please visit the SAP Help Portal 81
 11/2/24, 10:45 AM

 Example
You can find the target ID for the Customer migration object in the Customer column.

3. Select the link to the SAP Fiori app. You’re redirected to the respective standard SAP Fiori app for validation.

 Note
It’s also possible that no link is displayed. There are two potential reasons:

The role needed to access the SAP Fiori app isn’t assigned to your user. Please check the respective
documentation for required business roles per migration object and assign them to your user.

For some migration objects, it’s currently not possible to link them with an app. Please access the app for
validation directly via the SAP Fiori launchpad. Find more information on apps for validation per migration object
in the related migration object documentation.

Exporting Your Data

Context
You can export every table in the Data Migration Status app to a spreadsheet file.

 Tip
Exporting the information on the Messages tab of a migration object provides you with additional information and a detailed
log in the exported spreadsheet file.

Procedure
For any table that you want to export to a spreadsheet file, choose  (Export to Spreadsheet). The download of the file starts
automatically, once it’s generated.

Analyze Your Selection Process

App ID: 7829

With this app, you can simulate the selection process for a specific migration object instance. Simulating the selection process has
no impact on any migration project – no data is changed in the source system or in the target system.

 Note
This app is only relevant for the migration approach Migrate Data Directly from SAP System.

 Note
Not all migration objects are supported. For a list of supported objects, see Available Migration Objects. Note that you will need
to first choose Hide/Show Columns, and then select the checkbox Supported by App Analyze Your Selection Process.

Key Features

This is custom documentation. For more information, please visit the SAP Help Portal 82
 11/2/24, 10:45 AM
You can use this app to do the following:

Create an analysis run for your migration project that allows you to simulate the selection process for a specific migration
object instance.

View the results of the simulation, including the reason why the migration object instance was not selected, if applicable.

Copy an analysis run to easily simulate the selection process for other migration object instances in the same project.

Supported Device Types

Desktop

Creating Analysis Runs

Context
You use analysis runs to simulate the selection process for specific migration object instances.

 Note
In the Migrate Your Data app, the selection process must be complete for the relevant migration object.

 Note
If an analysis run is in process for a migration object, and you create a new analysis run for the migration object, the status of
the existing analysis run will be set to Read-Only.

Procedure
1. In the SAP S/4HANA system, open the Analyze Your Selection Process app in the Fiori Launchpad.

2. Choose New Analysis Run. The New Analysis Run dialog opens. In the Migration Project field, enter the relevant migration
project.

In the Migrate Your Data app, the relevant migration project cannot have the status Finished, Deleted, or Read-Only.

3. In the Migration Object field, specify the name of the relevant migration object in the project.

4. Choose the Create button. The New Analysis Run screen opens.

5. Under Name and Comment, enter a name for your analysis run. You can also enter a comment.

6. Under Migration Object Instance, enter the necessary data for the migration object instance.

7. Choose Create and Start Analysis. The system will start your analysis run. For more information, see Selection Steps.

Copying an Analysis Run

Context
You can copy an analysis run to easily simulate the selection process for other migration object instances in the same project.

Procedure

This is custom documentation. For more information, please visit the SAP Help Portal 83
 11/2/24, 10:45 AM
1. On the Analyze Your Selection Process screen, select the analysis run that you want to copy.

2. Choose the Copy button. The New Analysis Run screen opens.

3. Enter a name for the analysis run. If required, you can also enter a comment.

4. Under Migration Object Instance, enter the necessary data for the migration object instance.

5. Choose Create and Start Analysis. The system will start your analysis run. For more information, see Selection Steps and
Starting a Selection Step.

Selection Steps
The system selects data from the source system using four different selection steps. You use your analysis run to repeat these
selection steps so that the system can identify the exact point in the selection process that the relevant migration object instance
was selected. The system will also attempt to determine whether the migration object instance was not selected at a specific point
in the selection process (for example because of specific selection logic for a migration object). Note that the system only
simulates these selection steps, no data is selected from the source system.

The system selects data from the source system using the following selection steps:

Step 1 - Check Whether Instance Exists in Source

This step will identify whether the relevant migration object instance exists in the source system and identify whether it can
be selected from the source system.

The system will attempt to select the relevant migration object instance from the relevant database tables in the source
system using the specified key fields. Note that the system will only attempt to select the migration object instance from
database tables in the source system, and not from any manually defined tables. The system does not use any selection
logic that is defined for the migration object to select the data.

Step 2 - Identify Data Using Selection Logic

The system will identify the relevant data for the migration object instance in the source system and restricts the selection
by using the selection logic (such as selection criteria and BAdI selection exits) that is defined for the migration object.

If the relevant migration object instance could not be selected from the source system, then the issue could relate to the
selection logic that is defined for the migration object.

Step 3 - Extract Data from Source System

The system will extract the relevant data for the migration object instance from the source system. If manually defined
tables exist in the source system for the migration object, the system will use include programs to insert data into these
tables for the migration object instance.

If the relevant migration object instance could not be selected from source system, then the issue could relate to the
include programs.

Step 4 - Create Instance List in Target System

The system will consider any source code rules that are used to exclude migration object instances from the selection.
After that, the system will create a migration object instance list in the target system. This list is required for the
subsequent migration steps such as mapping tasks, simulating the migration, and migrating data.

If the relevant migration object instance is not part of the migration object instance list in the target system, then the issue
could relate to the source code rules that are used to exclude migration object instances from the selection.

For information about how to start a selection step, see Starting a Selection Step.

This is custom documentation. For more information, please visit the SAP Help Portal 84
 11/2/24, 10:45 AM

Starting a Selection Step

When you create an analysis run, the system automatically starts the first selection step (Check Whether Instance Exists in
Source System).

If the system cannot select the migration object instance during this step, the system sets the status of the analysis run to
Finished. The system cannot simulate the selection process for a migration object instance that does not exist in the source
system.

If the migration object instance exists in the source system, you need to start the next selection step by choosing the Start Next
Step button.

If the system cannot select the migration object instance during any of the subsequent selection steps, the system sets the status
of the analysis run to Finished. You can view information about why the migration object instance could not be selected. For more
information, see Viewing the Results of a Selection Step.

If the system can select the migration object instance during any of the subsequent selection steps, you can proceed to the next
selection step by choosing the Start Next Step button. Note that there are only four selection steps.

 Note
If a selection step fails due to a technical issue, the system sets the status of the step to Error. To view more information about
the issue, choose the Show Messages button at the bottom of the screen. To restart the selection step, choose the Restart
Step button.

Viewing the Results of a Selection Step

Once a selection step is complete, you can view the results of the step including, for example, the reason why data was not
selected.

To view the results of a selection step, choose the Show Messages button at the bottom of the screen.

Situation Handling for Data Migration

Situation Handling

This app uses Situation Handling, which automatically informs users responsible about matters that require their attention. For
more information, see Situation Handling.

This is custom documentation. For more information, please visit the SAP Help Portal 85
 11/2/24, 10:45 AM

For data migration, the situation type is named Data Migration Complete (CA_DATA_MIGRATION_STEP_COMPLETED).

 Note
Situation handling is only available for business users.

Data Migration Complete

Technical Name: CA_DATA_MIGRATION_STEP_COMPLETED

Consuming App: Data Migration Status

Template used for Situation Handling that informs you when the data migration steps Simulate or Migrate are completed and
results are available.

For background information about the Situation Handling framework, see the Product Assistance for Situation Handling.

Business Value

As a configuration expert for business processes (SAP business role SAP_BR_BPC_EXPERT), you can use this template for the
following situation:

You want the data migration expert to be informed automatically when the data migration steps Simulate or Migrate are
completed and results are available.

Default Settings
The template comes with predefined settings. For the settings that aren't visible or self-explanatory, you can find information in
the following sections. For generic information about how to configure situations based on this template, refer to the
documentation of the Manage Situation Types app with which you can display and use the template.

For more information, see Manage Situation Types.

Situation Trigger Object and Anchor Object

These technical settings define for which object a situation is displayed (anchor object) and the object based on which a situation
is triggered (trigger object):

Trigger Object: I_DATAMIGRTNSTPEXTID

Anchor Object: I_DATAMIGRTNSTPEXTID

Description: Data migration results available.

Conditions

This is custom documentation. For more information, please visit the SAP Help Portal 86
 11/2/24, 10:45 AM
The Mass Transfer ID can be used as a condition in this template to get notified when a migration object in a specific migration
project is completed.

The preconfigured conditions in this template are defined for processing in this order:

Condition Condition Description

1 Mass Transfer ID: Every migration project has a unique mass transfer ID. You can use this ID as a condition for your this
situation type to be only notified when a specific migration project is completed.

For more information, see Conditions.

Situation Display

When situations occur, users are informed about them by various texts, such as in-app situation messages or notifications on SAP
Fiori launchpad. In this section, you can see all preconfigured texts.

For more information, see Situation Display.

 Note
When you copy the template and adapt it to your needs, you can define the notification settings and change all text elements in
this section. After making the changes in the original language, please remember to translate these changes into the other
languages that you want to use. The template comes with translations that can be changed directly when you copy the
template.

For more information, see Translate Situation Types.

Recipients

In this section, you see the predefined settings for determining who is responsible for a situation instance. Based on these, you can
define who receives a notification when a situation instance is triggered (if enabled) or who sees the instance in the My Situations
app.

As per default, notifications are sent to the data migration expert who performs a migration activity.

For more information, see Recipients.

Situation Monitoring

Monitor Instances: Monitoring (the tracking of changes to situation instances) isn't enabled by default for situation templates.
When you copy the template to create a situation type, you need to enable this option if you want to capture data for this situation
type and enable the creation of business situation events. You can view the data in the Monitor Situations app.

Related Information
Situation Handling
Key Concepts in Situation Handling

Video Library for Data Migration

This video library gives you quick access to videos showcasing selected apps and functions that are relevant for data migration to
SAP S/4HANA.

This is custom documentation. For more information, please visit the SAP Help Portal 87
 11/2/24, 10:45 AM

SAP S/4HANA Migration Cockpit

The following video shows the SAP S/4HANA Migration Cockpit using the migration approach Migrate Data Using Staging Tables
and XML files.

The following video shows the SAP S/4HANA Migration Cockpit using the migration approach Migrate Data Using Staging Tables
and CSV files.

The following video shows the SAP S/4HANA Migration Cockpit using the migration approach Migrate Data Directly from SAP
System in SAP S/4HANA 2022.

This is custom documentation. For more information, please visit the SAP Help Portal 88
 11/2/24, 10:45 AM

Data Migration Status

With this app, you can check the status of your migration objects and projects after you've started migrating data to your SAP
S/4HANA system.

In below video, we show you how to use the Extended Statistics feature of the Data Migration Status app.

This is custom documentation. For more information, please visit the SAP Help Portal 89
 11/2/24, 10:45 AM

Situation Handling for Data Migration

Data migration uses Situation Handling to automatically display a situation message when the data migration is completed and
results are available.

Migration Cockpit (Transaction LTMC) - Deprecated

Context
The app Migrate Your Data - Migration Cockpit is the successor of the Migration Cockpit (Transaction LTMC) app. The Migration
Cockpit (transaction LTMC) app is deprecated and can no longer be used to migrate data to SAP S/4HANA. However, you can still
view any projects that you created when using this app.

This is custom documentation. For more information, please visit the SAP Help Portal 90