11/21/25, 3:20 AM

Data Migration
Generated on: 2025-11-21 03:20:28 GMT+0000

SAP S/4HANA Cloud Public Edition | 2502 Latest

Public

Original content: [Link]

US&state=PRODUCTION&version=2502.500

Warning

This document has been generated from 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 SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.

For more information, please visit [Link]

This is custom documentation. For more information, please visit SAP Help Portal. 1
 11/21/25, 3:20 AM

Data Migration
You can migrate your business data to SAP S/4HANA Cloud Public Edition with the SAP S/4HANA migration cockpit. There are two
migration approaches: Migrate Data with Staging Tables and Migrate Data Directly from SAP System.

Landing Page
In the following image map, you can find 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 outputs.

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

[Link] this very topic: Data Migration

[Link] the entry topic: Available Migration Objects

[Link] the entry topic: Data Migration Status

Migrate Your Data - Migration Cockpit

App ID: F3473

With this app, you can migrate business data to SAP S/4HANA Cloud Public Edition. You can migrate data directly from certain
SAP source systems, or you can use staging tables to migrate data.

This is custom documentation. For more information, please visit SAP Help Portal. 2
 11/21/25, 3:20 AM

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 Cloud Public Edition, and monitor the status of the
simulation process.

Migrate your data to SAP S/4HANA Cloud Public Edition, 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. If a
matching situation type is enabled, situations will be displayed directly in this app. For your convenience, a situation type has
automatically been enabled for this app. If you don't want to use this feature, you can disable or delete the enabled situation type
in the Manage Situation Types app. 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 also 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:

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

[Link] the entry topic: Data Migration

[Link] the entry topic: Available Migration Objects

[Link] the entry topic: Data Migration Status

Supported Device Types

Desktop

What Data Can Be Migrated?

You can use the SAP S/4HANA migration cockpit to migrate the initial set of data that is required to start business operations. This
data includes:

Master data such as customer master data, supplier master data, and so on.

This is custom documentation. For more information, please visit SAP Help Portal. 3
 11/21/25, 3:20 AM
Open transactional data. This includes open items, open sales and purchase orders, as well as other open transactions.

Balances such as material inventory balances, bank account balances, G/L account balances, and so on. You can also
migrate historical account balances.

Open documents need to be processed in the source system before the migration. Freeze periods for changes or double
maintenance might be required for some master data objects during the cutover period. For example, partially delivered sales
orders must be closed in the source system. Partially open purchase orders must either be closed or cancelled in the source
system.

 Note
Historical data cannot be migrated. Historical data (transactional data that has been created in the past and relates to long-
running or closed processes) cannot be migrated.

 Note
Orders (for example purchase orders, sales orders, and production orders) that have follow-on documents in their document
flow cannot be migrated.

Migrate Data Using Staging Tables

The SAP S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for your project and
migrates data from these staging tables to the target SAP S/4HANA Cloud Public Edition 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 Cloud Public Edition system.

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

 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 SAP Help Portal. 4
 11/21/25, 3:20 AM
In this case, it is crucial to ensure that such personal data is not migrated to the target SAP S/4HANA Cloud Public Edition
system.

 Note
For SAP S/4HANA Cloud Public Edition, the following business role is required:

SAP_BR_CONFIG_EXPERT_DATA_MIG

You create and assign the required business role for data migration using the business role template and adjust it to the user's
requirements.

To create a business role for your data migration user, you need to know the migration objects that they want to use in their
migration project. You then need to add the respective business catalogs to their business role. For detailed information about
this process, see the test script for the 2Q2 scope item. Navigate to the Data Migration to SAP S/4HANA from Staging (2Q2 )
solution process on SAP Signavio Process Navigator.

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 Cloud Public Edition system, you access the SAP S/4HANA migration cockpit by choosing the
Migrate Your Data - Migration Cockpit app on the SAP 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 Cloud Public Edition.

Note that you typically first create a project in a test system which is a copy of the production SAP S/4HANA Cloud Public
Edition 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 Cloud
Public Edition 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.

This is custom documentation. For more information, please visit SAP Help Portal. 5
 11/21/25, 3:20 AM
5. You prepare the staging tables for each migration object so that they can be used to transfer data to SAP S/4HANA Cloud
Public Edition.

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 Cloud Public Edition system.

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

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

Creating Migration Projects

Context
You use migration projects to facilitate the transfer of data from a source system to SAP S/4HANA Cloud Public Edition. You use a
migration project to specify the data that you want to transfer, and to monitor the status of the migration.

Typically, you first create a project in a test system. The more the data in the test system resembles the data in the production
system, the more precise your test will be.

For 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 Cloud Public Edition production system,
you create a project in the production system.

Procedure
1. In the SAP S/4HANA Cloud Public Edition system, access the SAP S/4HANA migration cockpit by choosing the Migrate
Your Data - Migration Cockpit app on the SAP Fiori launchpad.

2. The Migration Project screen opens. Choose Create. The system displays the New Migration Project screen. Creating a
project involves two steps. In the first step you specify general data for the project. In the second step you select the
relevant migration objects.

3. Specify a name for the project.

4. 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 Cloud Public
Edition system. If you want to fill the staging table with data by using your preferred tools, select the option Remote SAP
HANA Database and enter a valid database connection to the remote SAP HANA schema (SAP HANA Cloud instance on
SAP Business Technology Platform) or choose one from the search help list. The system will generate the staging tables
there. You need to create a database connection by creating a communication arrangement for communication scenario
SAP_COM_0678 (Migration Cockpit Integration). You can do this by using the Communication Arrangements Fiori app.
Note that you can also use files to fill the staging tables with data if you choose this option.

5. Choose the button Step 2.

6. Under Available Migration Objects, the system displays a list of available migration objects. Select the objects that are
relevant for your project and choose the button Move to Selected Migration Objects. The system moves the object to the
Selected Migration Objects area. To remove objects from the Selected Migration Objects area, select the migration
objects you want to remove and choose the button Move to Available Migration Objects.

7. Choose Review to review your project settings.

8. Choose Create Project to create your migration project.

Copying Migration Projects

This is custom documentation. For more information, please visit SAP Help Portal. 6
 11/21/25, 3:20 AM

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. You specify a new name for the project, and can adjust the database connection 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.

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.

3. Specify a name for the project.

4. If required, you can specify a different database connection.

5. Choose the button Step 2.

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

7. Review your settings and choose Copy Project to create your project.

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 Cloud Public Edition
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 Cloud Public Edition system (optional).

This is custom documentation. For more information, please visit SAP Help Portal. 7
 11/21/25, 3:20 AM
5. Migrating the data for the migration object to the target SAP S/4HANA Cloud Public Edition 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 Cloud Public Edition 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

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

This is custom documentation. For more information, please visit SAP Help Portal. 8
 11/21/25, 3:20 AM
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.
Note that the default number of background jobs for a project is 8. By default, the jobs are distributed equally among the migration
objects.

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.

Views

The following views are provided:

Standard

Migration objects are ordered by name.

Sequence Information

As you will need to process migration objects in a specific order, the Sequence Information view can guide you on how to
transfer data to the target system to ensure data integrity and consistency. In this view, the system places the migration
objects in your project in different groups.

The migration objects in the Project-Specific Goup have dependencies to each other. The sequence in which these objects
are processed is project-specific. You need to analyze the migration objects in this group to determine the correct sequence
for migrating data according to your business requirements. Note that if your migration project does not contain any
migration objects that are relevant for this group, the Project-Specific Group is not displayed.

You can then migrate the data for the migration objects in group 1. After completing this, migrate the data for the migration
objects in group 2. You can then migrate the data for the migration objects in group 3, and so on.

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:

This is custom documentation. For more information, please visit SAP Help Portal. 9
 11/21/25, 3:20 AM
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:

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 8. One job is reserved by the scheduling process and is not used by any
migration objects. The remaining jobs are distributed equally among the migration objects. If required, you can also adjust the
number of background jobs for specific migration objects.

Example 1

You specify 8 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify
4 background jobs for migration object A and 4 jobs for migration object B. As one job is reserved by the scheduling process, a
maximum of seven jobs will be used to process the two migration objects.

Example 2

You specify 8 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify 7
background jobs for migration object A and 5 jobs for migration object B. A maximum of 7 jobs will be used for object A, and a

This is custom documentation. For more information, please visit SAP Help Portal. 10
 11/21/25, 3:20 AM
maximum of 5 jobs will be used for object B. The overall number of active background jobs for the project will not exceed 7 jobs.

Example 3

You specify 4 background jobs 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. As one job is reserved by the scheduling process, 3 jobs
will process migration object A and migration object B in a round robin procedure.

The Migration Object Screen

The SAP S/4HANA migration cockpit uses migration objects to transfer data to SAP S/4HANA Cloud Public Edition. 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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 11
 11/21/25, 3:20 AM
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.

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.

This is custom documentation. For more information, please visit SAP Help Portal. 12
 11/21/25, 3:20 AM

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.

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
This is custom documentation. For more information, please visit SAP Help Portal. 13
 11/21/25, 3:20 AM
If you are using XML template files to populate the staging tables with data, you need to download an XML template file for the
relevant migration object and enter the data to be migrated in the file.

Procedure
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#[Link]. 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:

This is custom documentation. For more information, please visit SAP Help Portal. 14
 11/21/25, 3:20 AM
<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#[Link]

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#[Link]

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.

This is custom documentation. For more information, please visit SAP Help Portal. 15
 11/21/25, 3:20 AM

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.

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. Also, the SAP Release Note (2568909) for SAP S/4HANA
Cloud Public Edition data migration content uses the technical names of the structures and fields.

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 Cloud Public Edition, 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.

This is custom documentation. For more information, please visit SAP Help Portal. 16
 11/21/25, 3:20 AM

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

 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
Cloud Public Edition 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

This is custom documentation. For more information, please visit SAP Help Portal. 17
 11/21/25, 3:20 AM
migration template.

Using the Find and Replace Function

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

This is custom documentation. For more information, please visit SAP Help Portal. 18
 11/21/25, 3:20 AM
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
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:

This is custom documentation. For more information, please visit SAP Help Portal. 19
 11/21/25, 3:20 AM
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
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

This is custom documentation. For more information, please visit SAP Help Portal. 20
 11/21/25, 3:20 AM
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.

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.

This is custom documentation. For more information, please visit SAP Help Portal. 21
 11/21/25, 3:20 AM

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

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.

Microsoft Excel follows the IEEE Standard for Floating-Point Arithmetic (IEEE 754) for storing decimal numbers in binary
format. This means that most decimal numbers will be stored with an additional number of decimal places in Microsoft
Excel.

This is custom documentation. For more information, please visit SAP Help Portal. 22
 11/21/25, 3:20 AM
When you upload the file that contains a decimal number, the number of decimal places will be truncated based on the
number of decimal places defined by the migration object.

The system displays a warning message in this case explaining that the number of decimal places will be truncated. This
message can usually be ignored as the value in the staging table will contain an acceptable number of decimal places as
defined by the migration object (usually the exact decimal number that was specified in the template file).

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.

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
This is custom documentation. For more information, please visit SAP Help Portal. 23
 11/21/25, 3:20 AM
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 Cloud Public Edition. 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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 24
 11/21/25, 3:20 AM
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.

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
This is custom documentation. For more information, please visit SAP Help Portal. 25
 11/21/25, 3:20 AM
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.

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#[Link].

This is custom documentation. For more information, please visit SAP Help Portal. 26
 11/21/25, 3:20 AM
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#[Link], S_BNKA.csv, or S_BNKA#[Link]

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#[Link].

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#[Link], 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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 27
 11/21/25, 3:20 AM
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 Cloud Public Edition. 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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 28
 11/21/25, 3:20 AM
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
files or single CSV files. Note that the size limit for CSV folders is 100 MB. 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.

This is custom documentation. For more information, please visit SAP Help Portal. 29
 11/21/25, 3:20 AM
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.

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#[Link].

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#[Link], S_BNKA.csv, or S_BNKA#[Link]

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

This is custom documentation. For more information, please visit SAP Help Portal. 30
 11/21/25, 3:20 AM

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#[Link].

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#[Link], 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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 31
 11/21/25, 3:20 AM
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 Cloud Public Edition. 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.

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:

This is custom documentation. For more information, please visit SAP Help Portal. 32
 11/21/25, 3:20 AM

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 a remote SAP HANA schema (SAP HANA Cloud instance on SAP Business Technology
Platform), 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 .

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

This is custom documentation. For more information, please visit SAP Help Portal. 33
 11/21/25, 3:20 AM
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 Cloud Public Edition. 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

This is custom documentation. For more information, please visit SAP Help Portal. 34
 11/21/25, 3:20 AM
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

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

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

This is custom documentation. For more information, please visit SAP Help Portal. 35
 11/21/25, 3:20 AM

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 Cloud
Public Edition.

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

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 staging tables so that they can be used to transfer data to SAP S/4HANA Cloud Public Edition.

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

This is custom documentation. For more information, please visit SAP Help Portal. 36
 11/21/25, 3:20 AM
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
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

This is custom documentation. For more information, please visit SAP Help Portal. 37
 11/21/25, 3:20 AM
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 Fixed asset - Master data. 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

This is custom documentation. For more information, please visit SAP Help Portal. 38
 11/21/25, 3:20 AM
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 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 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 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 Cloud Public Edition
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.

This is custom documentation. For more information, please visit SAP Help Portal. 39
 11/21/25, 3:20 AM

Example
When using the migration object Material Inspection Setup to migrate data to SAP S/4HANA Cloud Public Edition, 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.

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 Cloud Public Edition 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

This is custom documentation. For more information, please visit SAP Help Portal. 40
 11/21/25, 3:20 AM
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

Context
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 Cloud Public Edition system. Note that no data is written to the target SAP S/4HANA Cloud
Public Edition 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
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.

Procedure

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.

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

Migrating Data to SAP S/4HANA Cloud Public Edition

Context
This is custom documentation. For more information, please visit SAP Help Portal. 41
 11/21/25, 3:20 AM
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 Cloud Public Edition system. Note that we recommend that you first simulate the migration.

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

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 Migrate button.

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

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.

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 Cloud

Public Edition

This is custom documentation. For more information, please visit SAP Help Portal. 42
 11/21/25, 3:20 AM

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.

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.

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 Cloud Public Edition 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.

Migrate Data Directly from SAP System

The SAP S/4HANA migration cockpit facilitates the transfer of business data from certain SAP source systems to SAP S/4HANA
Cloud Public Edition. 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 Cloud Public Edition. 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.

This is custom documentation. For more information, please visit SAP Help Portal. 43
 11/21/25, 3:20 AM
The SAP S/4HANA migration cockpit is designed for an initial load of data, specifically for the SAP S/4HANA Cloud Public Edition
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.

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

Before You Start

The SAP S/4HANA migration cockpit selects data from the source system by using specific criteria. For the migration scenario
SAP ERP to SAP S/4HANA Cloud Public Edition, the SAP S/4HANA migration cockpit selects data using company codes (you
specify the relevant company codes when creating a project).

Note that the lowest supported release is ECC 6.0 (SAP NetWeaver 7.0).

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 Cloud Public Edition system by
means of a communication arrangement. This means that the conversion to the SAP S/4HANA Cloud Public Edition 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, an SAP S/4HANA Cloud Private Edition system, or an SAP S/4HANA Cloud
Public Edition system as a source system.

Prerequisites
Your SAP S/4HANA Cloud Public Edition is based on a 3-system landscape. For more information, see System Landscapes
in SAP S/4HANA Cloud Public Edition.

You have created a communication arrangement for the communication scenario Migration Cockpit Direct Transfer
Integration (SAP_COM_0816). For more information see the document Set-Up Instructions for Implementing a Scope Item
(Data Migration to SAP S/4HANA from SAP). Navigate to the Data Migration to SAP S/4HANA from SAP (BH3 ) solution
process on SAP Signavio Process Navigator, and download the document from the Accelerators section.

You have installed the DMIS 2011 add-on in the source system. Make sure you install the latest available support package
version. This add-on is included in the license for SAP S/4HANA Cloud Public Edition. For more information, see SAP Notes
This is custom documentation. For more information, please visit SAP Help Portal. 44
 11/21/25, 3:20 AM
1577441 , 1577503 , and 1648747 .

Roles and Authorizations

SAP S/4HANA Migration Cockpit users use a communication arrangement to connect the SAP S/4HANA migration cockpit to the
source system, but they do not access data in the source system directly. The communication arrangement contains an outbound
communication user that accesses the data in the source system. This user requires the role SAP_DMIS_MC_DT_REMOTE.

To use the Migrate Your Data app, the following business role is required:

SAP_BR_CONFIG_EXPERT_DATA_MIG

You create and assign the required business role for data migration using the business role template and adjust it to the user's
requirements.

To create a business role for your data migration user, you need to know the migration objects that they want to use in your
migration project. You then need to add the respective business catalogs to your business role.

You can find detailed information about this process in the test script for the solution process. Navigate to the Data Migration to
SAP S/4HANA from SAP (BH3 ) solution process on SAP Signavio Process Navigator, and download the test script from the
Accelerators section.

Planning Your Migration Projects

SAP delivers predefined migration objects that you can use to transfer data to a target SAP S/4HANA Cloud Public Edition system.
SAP can deliver updated versions of the migration objects to your SAP S/4HANA Cloud Public Edition system with each new
release.

When you add a migration object to a project, the system uses the predefined migration object delivered by SAP as a template and
makes a copy of the object for your project. When SAP delivers updated versions of migration objects to your SAP S/4HANA Cloud
Public Edition system, these copies of the migration objects in the projects are not updated.

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

Example
A project exists with migration object A and B. SAP delivers updated versions of migration objects A and B to your SAP S/4HANA
Cloud Public Edition system with a new release. The migration objects in the project are not updated to reflect the latest version of
the migration objects. This is because the migration objects in the project are copies of the migration objects provided by SAP.

Example
A project exists with migration object A and B. SAP delivers an updated version of migration object A to your SAP S/4HANA Cloud
Public Edition system with a new release. Migration object A in the project is not updated to reflect the latest version of the
migration objects. 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 the SAP S/4HANA migration object modeler. The project will now contain the updated
version of the migration object.

Example

This is custom documentation. For more information, please visit SAP Help Portal. 45
 11/21/25, 3:20 AM
SAP delivers updated versions of migration object A to your SAP S/4HANA Cloud Public Edition system with a new release. You
now want to use this updated migration object to transfer data to SAP S/4HANA Cloud Public Edition. You create a new migration
project, and add migration object A. This new project contains the updated version of the migration object A.

Recommendation

If you upgrade your SAP S/4HANA Cloud Public Edition 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 Cloud Public Edition is as follows:

1. In the SAP S/4HANA Cloud Public Edition system, you access the SAP S/4HANA migration cockpit by choosing the
Migrate Your Data app on the SAP 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 Cloud Public Edition.

3. Note that you typically first create a project in a test 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 Cloud Public Edition system, you can create a project in the production system.

4. 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 Cloud Public Edition, then you select data using company codes (you specify the
relevant company codes when creating a project).

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

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 Cloud Public Edition system.

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

Creating Migration Projects

Context
You use migration projects to facilitate the transfer of data from a source system to SAP S/4HANA Cloud Public Edition. In order to
migrate data to SAP S/4HANA Cloud Public Edition, 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 first create a project in the development system and then transport the project to the test system and perform a test
migration there. If the test migration is successful in the test system, you can then transport the project to the production system.

If your mapping values from the previous test have not changed, you can download them and upload them to your new project.

This is custom documentation. For more information, please visit SAP Help Portal. 46
 11/21/25, 3:20 AM

 Note
It is only possible to create projects in development systems, not production or test systems.

 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
communication arrangement 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.

To create a migration project, proceed as follows:

1. In the SAP S/4HANA Cloud Public Edition system, you access the SAP S/4HANA migration cockpit by choosing the
Migrate Your Data app on the SAP 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. Only the migration scenario SAP ERP to SAP S/4HANA Cloud Public Edition is available.

Connection to Source System

The communication arrangement used to connect the SAP S/4HANA Cloud Public Edition 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. The scenario SAP ERP to SAP S/4HANA Cloud Public Edition 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, you further restrict the selection if required.

This is custom documentation. For more information, please visit SAP Help Portal. 47
 11/21/25, 3:20 AM
6. Choose the button Step 3.

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

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.

3. Specify a name for the project.

This is custom documentation. For more information, please visit SAP Help Portal. 48
 11/21/25, 3:20 AM
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 Data Selection, you can adjust the criteria that is used to select the data for the migration objects.

7. Choose the button Step 3.

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

9. Review your settings and choose Copy Project to create your project.

Transporting Projects to the Test System

Usually, depending on authorizations and system settings, the following activities are only permitted in the development system:

Creating migration projects

Adding migration objects to migration projects

Adjusting migration projects and objects

You can transport a migration project from the development system to the test system by using the app Export Customizing
Transports. If additional adjustments to migration objects are required, you need to adjust the relevant migration object in the
development system using the migration object modeler, 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.

To transport a project to the test system, proceed as follows:

1. Create a customizing request using the app Export Customizing Transports.

2. In the Migration Object Modeler, add the relevant project to a transport request by using the function Add to Transport
Request. Note that it is also possible to add migration objects to a transport request.

 Note
In the Migration Object Modeler, you can add your migration project to a transport request by using the option Add to
Transport Request. Note that if you change the configuration of your migration project, for example if you create a new
transformation rule, you need to add the relevant object to the relevant transport request by using the option Add to
Transport Request in the Migration Object Modeler.

3. In the app Export Customizing Transports, release the customizing request.

4. Note that the request is not imported automatically. In the test system, use the Import Collection app to import the
project. Once the project has been imported successfully, the project will have the status Imported in the test system.

5. In the Migrate Your Data app, specify the data connection and the relevant company codes for the project.

You first create a project in the development system and then transport the project to the test system and perform a test
migration there. If the test migration is successful in the test system, you can then transport the project to the production system.

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 the Migration Object Modeler, 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.

This is custom documentation. For more information, please visit SAP Help Portal. 49
 11/21/25, 3:20 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 all the steps that are required to transfer the data for each migration object to SAP S/4HANA Cloud Public Edition.

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

4. Simulating the migration to SAP S/4HANA Cloud Public Edition (optional)

5. Migrating the data for the migration object to SAP S/4HANA Cloud Public Edition

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.

You can also view the status of the migration object in this column. For more information see Migration Object Status.

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 SAP S/4HANA Cloud
Public Edition, 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

This is custom documentation. For more information, please visit SAP Help Portal. 50
 11/21/25, 3:20 AM
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).

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. For more information, see Migrating Data to SAP S/4HANA Cloud Public Edition.

Views

The following views are provided:

Standard

Migration objects are ordered by name.

Sequence Information

As you will need to process migration objects in a specific order, the Sequence Information view can guide you on how to
transfer data to the target system to ensure data integrity and consistency. In this view, the system places the migration
objects in your project in different groups.

The migration objects in the Project-Specific Goup have dependencies to each other. The sequence in which these objects
are processed is project-specific. You need to analyze the migration objects in this group to determine the correct sequence

This is custom documentation. For more information, please visit SAP Help Portal. 51
 11/21/25, 3:20 AM
for migrating data according to your business requirements. Note that if your migration project does not contain any
migration objects that are relevant for this group, the Project-Specific Group is not displayed.

You can then migrate the data for the migration objects in group 1. After completing this, migrate the data for the migration
objects in group 2. You can then migrate the data for the migration objects in group 3, and so on.

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:

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

The migration approach.

The migration scenario.

The connection to the source system.

The communication arrangement used to connect the SAP S/4HANA Cloud Public Edition 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.

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.

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 Cloud Public Edition 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.

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 8. One job is reserved by the scheduling process and is not used by any

This is custom documentation. For more information, please visit SAP Help Portal. 52
 11/21/25, 3:20 AM
migration objects. The remaining jobs are distributed equally among the migration objects. 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
You specify 8 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify
4 background jobs for migration object A and 4 jobs for migration object B. As one job is reserved by the scheduling process, a
maximum of seven jobs will be used to process the two migration objects.

Example
You specify 8 background jobs for your project (in the Maximum Number of Background Jobs for Project field). You then specify 7
background jobs for migration object A and 5 jobs for migration object B. A maximum of 7 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 7 jobs.

Example
You specify 4 background jobs 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. As one job is reserved by the scheduling process, 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 SAP S/4HANA Cloud Public Edition 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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 53
 11/21/25, 3:20 AM
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.

Migration Object Status

SAP can deliver updated versions of migration objects to SAP S/4HANA Cloud Public Edition. If an update is available for a
migration object in your project, the system will update the status of the migration object to inform you that a new version is
available. While new versions of migration objects will contain new features or bug fixes, migration objects can also be deprecated
or retired. The system will update the status of such migration objects to inform you that they will be unavailable in future releases.

SAP can apply the following status values to migration objects in your project:

New Version Available​

A new version of the migration object is available. SAP always recommends using the new version of the migration object to
migrate data, especially after upgrading to the latest release. Using the latest version of the migration object ensures that
you benefit from the latest enhancements and bug fixes. You can use the Migration Object Modeler to add the new version
of the migration object to your project.

New Mandatory Version Available​

A new mandatory version of the migration object is available. ​It is no longer possible to use the current version of the
migration object to migrate data. You can use the Migration Object Modeler to add the new version of the migration object
to your project.

Deprecated​

The migration object is deprecated and will not be available in the near future. However, it is still possible to migrate data
using this migration object.​​For information about when the migration object will be deleted, see the documentation for the
migration object on the SAP Help Portal.

Deprecated (New Version Available)​

A new version of this migration object is available. Although it is still possible to migrate data using this migration object,
deprecated objects will not be available in the near future. You can use the Migration Object Modeler to add the new version
of the migration object to your project.

Deprecated (New Mandatory Version Available)​​

A new mandatory version of this migration object is available. It is no longer possible to use this version of the migration
object to migrate data. Deprecated objects will be deleted in the near future.​You can use the Migration Object Modeler to
add the new version of the migration object to your project.

Retired​

The migration object is retired and can no longer be used to migrate data. In some cases, a successor migration object will
be available. For more information, see the documentation for the migration object on the SAP Help Portal.

Viewing Messages

This is custom documentation. For more information, please visit SAP Help Portal. 54
 11/21/25, 3:20 AM
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 SAP Help Portal. 55
 11/21/25, 3:20 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.

Selecting Data from the Source System

The SAP S/4HANA migration cockpit uses migration objects to transfer data to the SAP S/4HANA Cloud Public Edition 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 Cloud Public Edition 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, 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.

This is custom documentation. For more information, please visit SAP Help Portal. 56
 11/21/25, 3:20 AM

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
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 Example_Bank 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 Example_Bank 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

This is custom documentation. For more information, please visit SAP Help Portal. 57
 11/21/25, 3:20 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.

Current Step

If a migration object uses more than one transfer step to migrate migration object instances to SAP S/4HANA Cloud Public
Edition, 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

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.

This is custom documentation. For more information, please visit SAP Help Portal. 58
 11/21/25, 3:20 AM
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.

 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 on 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

This is custom documentation. For more information, please visit SAP Help Portal. 59
 11/21/25, 3:20 AM
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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 60
 11/21/25, 3:20 AM
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 example migration object Fixed Asset - Master Data. 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.

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

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.

This is custom documentation. For more information, please visit SAP Help Portal. 61
 11/21/25, 3:20 AM
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).

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 Example 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 SAP S/4HANA Cloud Public Edition. To do this,
you enter the value SA in the Customizing field of the Document Type fixed value task.

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.

This is custom documentation. For more information, please visit SAP Help Portal. 62
 11/21/25, 3:20 AM
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.

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 Cloud Public Edition fields.

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
Cloud Public Edition system. Note that no data is written to the target SAP S/4HANA Cloud Public Edition 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

This is custom documentation. For more information, please visit SAP Help Portal. 63
 11/21/25, 3:20 AM
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.

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 SAP S/4HANA Cloud Public Edition

Once you have processed all open tasks for a migration object, you can transfer data to the target SAP S/4HANA Cloud Public
Edition 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.

This is custom documentation. For more information, please visit SAP Help Portal. 64
 11/21/25, 3:20 AM
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

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 Cloud Public Edition 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 specifty a retention period, set the option Data Retention
Period to On. The data will be deleted from both the SAP S/4HANA Cloud Public Edition 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

This is custom documentation. For more information, please visit SAP Help Portal. 65
 11/21/25, 3:20 AM
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 Cloud Public Edition 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
Cloud Public Edition. 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 Cloud Public Edition. 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.

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
Cloud Public Edition. 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 Cloud Public Edition.

 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

This is custom documentation. For more information, please visit SAP Help Portal. 66
 11/21/25, 3:20 AM
When migrating migration object instances for the example migration object Asset, the SAP S/4HANA migration cockpit needs to
first create the asset in the SAP S/4HANA Cloud Public Edition 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 Cloud Public Edition.

In the following table, you can view the transfer options and transfer steps for the example migration object Asset.

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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 67
 11/21/25, 3:20 AM
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.

 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 Cloud Public Edition. 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.

This is custom documentation. For more information, please visit SAP Help Portal. 68
 11/21/25, 3:20 AM
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.

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 Cloud Public Edition.

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.

Accessing the SAP S/4HANA migration object modeler depends on the migration approach. For more information, see Migrate
Data Using Staging Tables and Migrate Data Directly from SAP System.

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.

This is custom documentation. For more information, please visit SAP Help Portal. 69
 11/21/25, 3:20 AM
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 Cloud Public Edition system.

Migrate Data Using Staging Tables

For the migration approach Migrate Data Using Staging Tables, use the Model Your Migration Objects – Migration Object
Modeler app to access the SAP S/4HANA migration object modeler. Note that it is only possible to enhance certain migration
objects that are released by SAP. There is an SAP Note for each migration object that details the structures and fields that can be
enhanced for that specific migration object. These SAP Notes can be accessed from SAP Note 2999428 .

You can access detailed documentation about how to use the application by using the Information button in the application.

For more information about using the SAP S/4HANA migration object modeler, see SAP Knowledge Base Article 3216716 .

 Note
The business role SAP_BR_ADMINISTRATOR is required to use the SAP S/4HANA migration object modeler.

Related Information
Training Material

Migrate Data Directly from SAP System

You use the Implementation Activities app to access the SAP S/4HANA migration object modeler. When you open the
Implementation Activities app, the system displays the SAP Business Configuration structure. You can find the activity Model
Your Migration Objects under General Business Data Data Management Data Migration Data Migration to SAP
S/4HANA .

You can access detailed documentation about how to use the application by using the Information button in the application.

 Note
The business role SAP_BR_BPC_EXPERT is required to use the SAP S/4HANA migration object modeler.

Read Access Logging Configurations in Migration Cockpit

In Read Access Logging (RAL), you can configure which read-access information to log and under which conditions.

SAP delivers template configurations for applications. By default, the RAL configuration is inactive.

In the scenario Migrate Data Using Staging Tables of Migration Cockpit, 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

This is custom documentation. For more information, please visit SAP Help Portal. 70
 11/21/25, 3:20 AM
data, together with the name of the user who opened this file.

In the following configurations, fields are logged in combination with additional fields, in the following business context.

Channel Configuration Description Fields Logged Bu

Co

OData CA-LT Migration File Process ID (:Entity Types:DownloadMigrationFile: Mi

(Version MIGRATIONFILEPROC) of
RAL Configuration for
2.0) cu
ODATA Service Migration Object File Created By Someone (:Entity Types:MigrationFile:
da
/LTB/MIG_MC_ODATA_SRV CREATEDBY)
SA
Migration Object File Name (:Entity Types:MigrationFile: FILENAME) S/
Clo
Migration Object File ID (:Entity Types:MigrationFile: Pu
MIGRATIONFILEUUID) Ed

Migration Object ID (:Entity Types:MigrationFile:

MIGRATIONOBJECTUUID)

Migration Project ID (:Entity Types:MigrationFile:

MIGRATIONPROJECTUUID)

Migration Object File Content (:Entity

Types:MigrationFileContent:FILECONTENT)

Migration Object File ID (:Entity

Types:MigrationFileContent:MIGRATIONFILEUUID)

Migration Object ID (:Entity

Types:MigrationFileContent:MIGRATIONOBJECTUUID)

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 Correction File Name (:Entity

Types:MigrationGroupIndicator:GROUPINDICATOR)

Migration Object ID (:Entity

Types:MigrationGroupIndicator:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity

Types:MigrationGroupIndicator:MIGRATIONPROJECTUUID)

Migration Instance Title (:Entity

Types:MigrationInstance:INSTANCETITLE)

Migration Instance Item field 1 (:Entity

Types:MigrationInstance:ITEMFIELD1)

This is custom documentation. For more information, please visit SAP Help Portal. 71
 11/21/25, 3:20 AM

Channel Configuration Description Fields Logged Bu

Co

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)

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:MIGRATIONPROJECTUUID)

Migration Instance ID (:Entity Types:MigrationInstance:

MIGRATIONINSTANCEUUID)

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)

This is custom documentation. For more information, please visit SAP Help Portal. 72
 11/21/25, 3:20 AM

Channel Configuration Description Fields Logged Bu

Co

Migration Object Staging Table Contents (:Entity

Types:TableData:COMBINEDCOLUMNS)

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 Staging Table ID (:Entity Types:TableData: TABLEUUID)

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)

Message Group ID (:Function

Imports:DownloadInstanceMessageDetailRAL: MESSAGEGROUPUUID)

Migration Object ID (:Function

Imports:DownloadInstanceMessageDetailRAL: MIGRATIONOBJECTUUID)

Migration Project ID (:Function

Imports:DownloadInstanceMessageDetailRAL: MIGRATIONPROJECTUUID)

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 Message Overview Detail (:Function

Imports:DownloadMessageOverviewDetailRALMonitor: DISPLAYOPTION)

Download Message Overview Detail (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:
MESSAGEGROUPUUID)

Download Message Overview Detail (:Function

Imports:DownloadMessageOverviewDetailRALMonitor: MESSAGEUUID)

Download Message Overview Detail (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:
MIGRATIONINSTANCEUUID)

Download Message Overview Detail (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:
MIGRATIONOBJECTUUID)

Download Message Overview Detail (:Function

Imports:DownloadMessageOverviewDetailRALMonitor:

This is custom documentation. For more information, please visit SAP Help Portal. 73
 11/21/25, 3:20 AM

Channel Configuration Description Fields Logged Bu

Co

MIGRATIONPROJECTUUID)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: APPLLOGNR)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: DISPLAYOPTION)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MIGRATIONHISTORYUUID)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MIGRATIONOBJECTUUID)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MIGRATIONPROJECTUUID)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MSGMSGID)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MSGMSGNO)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MSGMSGTY)

Download Show Messages (:Function

Imports:DownloadShowMessagesRALMonitor: MSGUUID)

Download Migration Object Messages (:Function

Imports:MigrationObjectMessageRALMonitor: MIGRATIONOBJECTUUID)

Download Migration Object Messages (:Function

Imports:MigrationObjectMessageRALMonitor: MIGRATIONPROJECTUUID)

Related Information
Read Access Logging

Available Migration Objects

You can use the following table to gain an overview of all migration objects available for SAP S/4HANA Cloud Public Edition. It’s
sorted in alphabetical order by Migration Object Name. Choose a migration object name to navigate to the documentation for the
migration object.

 Tip
Filter the Migration Approach column to only see migration objects relevant for you. Therefore, choose Filter in the respective
column, and select the required approach, Direct Transfer or Staging Table.

If you want to see less or more information, choose Hide/Show Columns, and select the respective checkboxes for the
columns you would like to hide or show, for example, the Predecessor Object or Scope Item column.

This is custom documentation. For more information, please visit SAP Help Portal. 74
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Bank Master data SAP_CA_BC_BNK_PC Direct Not Supported FI N

(Deprecated) Transfer applicable ap

Bank Master data SAP_CA_BC_BNK_PC Direct Not Supported FI N

Transfer applicable ap

Business partner Master data SAP_TC_CMD_BP_COMMON Direct Not Supported AP-MD-BP N

Transfer applicable ap

Characteristic Master data SAP_PLM_BC_CLF_MC Direct Not Supported CA-CL N

Transfer applicable ap

Class Master data SAP_LO_BC_VC_MODELING Direct Not Supported CA-CL N

Transfer applicable ap

CO - Cost center Master data SAP_FIN_BC_OH_MD_CCA_PC Direct Not Supported CO N

(Deprecated) Transfer applicable ap

CO - Cost center Master data SAP_FIN_BC_OH_MD_CCA_PC Direct Not Supported CO N

Transfer applicable ap

CO - Profit center Master data SAP_FIN_BC_OH_MD_PCA_PC Direct Not Not CO N

Transfer applicable supported ap

Customer Master data SAP_CMD_BC_CUST_MAINT_PC Direct Not Supported LO-MD- N

Transfer applicable BP-CM ap

This is custom documentation. For more information, please visit SAP Help Portal. 75
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

ECM - Change Master data SAP_PLM_BC_CM_MC Direct Not Supported PLM-WUI- N

master Transfer applicable OBJ-ECN ap

MM - Purchase Transactional SAP_MM_BC_SA_PROCESS_MC Direct Not Supported MM-PUR N

scheduling data Transfer applicable ap
agreement

MM - Purchasing Master data SAP_MM_BC_IR_PROCESS_PC Direct Not Supported MM-PUR N

info record Transfer applicable ap

Object Master data SAP_PLM_BC_CLF_MC Direct Not Supported CA-CL N

classification Transfer applicable ap
(general template)

PM - Functional Master data SAP_EAM_BC_TO_MC Direct Not Supported PM N

location Transfer applicable ap

PM - General Master data SAP_BR_MAINTENANCE_PLANNER Direct Not Supported PM N

maintenance task Transfer applicable ap
list

PP - Material BOM Master data SAP_PLM_BC_MBOM Direct Not Supported PP-BD N

Transfer applicable ap

PP - Production Transactional SAP_SCM_BC_PRODN_ORD_CTRL_MC Direct Not Supported PP-SFC- N

order data Transfer applicable 2CL ap

PP - Production Master data SAP_TC_SCM_PP_COMMON Direct Not Supported PP-SFC N

version Transfer applicable ap

Pricing condition Master data SAP_SD_BC_PRICE_MANAGE_MC Direct Not Supported SD N

(sales) Transfer applicable ap

PP - Routing Master data SAP_TC_SCM_PP_BE_APPS Direct Not Supported PP-BD- N

Transfer applicable RTG ap

PP - Work center Master data SAP_SCM_BC_PROC_ENG_MC Direct Not Supported PP-BD- N

Transfer applicable WKC ap

Product Master data SAP_CMD_BC_PR_MAINT Direct Not Supported LO-MD N

Transfer applicable ap

QM - Master Master data SAP_QM_BC_MSTR_INSP_CHARC_PC Direct Not Supported QM N

inspection Transfer applicable ap
characteristic

SD - Sales Transactional SAP_SD_BC_CONTR_PROC_OP Direct Not Supported SD N

contract data Transfer applicable ap

Supplier Master data SAP_CMD_BC_SUPP_MAINT_PC Direct Not Supported LO-MD- N

Transfer applicable BP-VM ap

Supplier - extend Master data SAP_CMD_BC_SUPP_MAINT_PC Staging Not Not TM-MD-BP N

existing record by Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 76
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

carrier role

Real estate - Master data SAP_FIN_BC_RECM_RENTALOBJ_PC Staging Not Not RE-FX-BD N

Usable object Table applicable applicable ap
(new)

EHS - Emitted Master data SAP_EHS_BC_ENV_MNG_CSCEN_PC Staging Not Not EHS-SUS- N

substance Table applicable applicable EM ap

EHS - Sampling Master data SAP_EHS_BC_ENV_MNG_CSCEN_PC Staging Not Not EHS-SUS- N

definition Table applicable applicable EM ap

Warehouse stock Transactional SAP_SCM_BC_EWM_MD_WHSE_PC Staging Not Not SCM-EWM Ye

(new) data Table applicable applicable
SAP_SCM_BC_EWM_MON_PC

MM - Purchasing Master data SAP_MM_BC_SOS_PROCESS_PC Staging Not Not MM-PUR N

quota Table applicable applicable ap
arrangement

This is custom documentation. For more information, please visit SAP Help Portal. 77
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Material BOM Master data SAP_PLM_BC_MBOM_PC Staging Not Not PP-BD Ye

Table applicable applicable

QM - Quality level Master data SAP_QM_BC_QUALITY_CONTROL_PC Staging Not Not QM-QC N

Table applicable applicable ap

Real estate - Master data SAP_FIN_BC_RECM_RENTALOBJ_PC Staging Not Not RE-FX-BD N

Usable object Table applicable applicable ap

In-house banking Master data SAP_FIN_BC_PF_IHB_PC Staging Not Not FIN- N

condition (new) Table applicable applicable FSCM-PF- ap
IHB

Configurable BOM Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-MD- N

links Table applicable applicable BOM ap

This is custom documentation. For more information, please visit SAP Help Portal. 78
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Routing (new) Master data SAP_SCM_BC_PROC_ENG_MC Staging Not Not PP Ye

Table applicable applicable

PC - Toxicological Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

information Table applicable applicable FND-PC ap
SAP_PSS_BC_PC_FND_RMON_PC

SAP_PSS_BC_PC_SUBST_MAN_PC

In-house banking Master data SAP_FIN_BC_PF_IHB_PC Staging Not Not FIN- N

account (new) Table applicable applicable FSCM-PF- ap
IHB

Asset to control Transactional SAP_FIN_BC_GL_TAX_CC_AA_BR_PC Staging Not Not FI-LOC- Ye

tax credits (Brazil) data Table applicable applicable FI-BR

EHS - Control Master data SAP_EHS_BC_HS_CTRL_MDATA_PC Staging Not Not EHS-SUS- N

Table applicable applicable HS ap

Business solution Transactional SAP_PS_BC_PROJ_CONTRL_MC Staging Yes Not CRM-S4- N

order (new) data Table applicable SOL-SLO ap
SAP_S4CRM_BC_SOLN_ORD_PROC_PC

This is custom documentation. For more information, please visit SAP Help Portal. 79
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

CO - Cost center Master data SAP_FIN_BC_OH_MD_CCA_PC Staging Yes Not CO N

(new) Table applicable ap

EHS - Job Master data SAP_EHS_BC_HS_MNG_JOB_PC Staging Not Not EHS-SUS- N

Table applicable applicable HS ap

Bank Master data SAP_CA_BC_BNK_PC Staging Not Not FI Ye

Table applicable applicable

This is custom documentation. For more information, please visit SAP Help Portal. 80
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

JVA - Joint venture Master data SAP_FIN_BC_JVA_CMD_PC Staging Not Not CA-JVA N
master data Table applicable applicable ap

HUM - Master data SAP_LO_BC_DR_MANAGE_PC Staging Not Not LO-HU N

Determination Table applicable applicable ap
record for packing
instruction

EHS - Business Master data SAP_CMD_BC_BP_MAINT_PC Staging Not Not EHS-SUS- N

partner for waste Table applicable applicable WA ap
transporters and
disposers

EHS - Waste Master data SAP_EHS_BC_ENV_MDSP_CHNNLS_PC Staging Not Not EHS-SUS- N

disposal channel Table applicable applicable WA ap

EHS - Waste Master data SAP_EHS_BC_ENV_WST_STRM_PC Staging Not Not EHS-SUS- N

stream Table applicable applicable WA ap

EHS - Waste type Master data SAP_EHS_BC_ENV_MNG_CHEM_PC Staging Not Not EHS-SUS- N
and waste codes Table applicable applicable FND-PC ap

HUM - Packing Master data SAP_LO_BC_PI_MANAGE_PC Staging Not Not LO-HU N

instruction Table applicable applicable ap

PC - Ecological Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

information Table applicable applicable FND-PC ap
SAP_PSS_BC_PC_FND_RMON_PC

SAP_PSS_BC_PC_SUBST_MAN_PC

This is custom documentation. For more information, please visit SAP Help Portal. 81
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

EHS - Waste Master data SAP_EHS_BC_ENV_WST_PART_PC Staging Not Not EHS-SUS- N

transporter and Table applicable applicable WA ap
disposer

PC - Use Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

Table applicable applicable FND ap

Asset retirement Master data SAP_FIN_BC_ARO_MANAGE Staging Not Not CA-ARO N

obligation - Master Table applicable applicable ap
data

Asset retirement Transactional SAP_FIN_BC_ARO_MANAGE Staging Not Not CA-ARO N

obligation - data Table applicable applicable ap
Postings

AVC - Variant table Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N
structure Table applicable applicable ap

Condition record Master data SAP_SCM_BC_IM_BATCH_SEARCH_PC Staging Not Not LO-BM N

for batch Table applicable applicable ap
SAP_SCM_BC_PO_BATCH_SEARCH_PC
determination (for
all areas) SAP_SCM_BC_SD_BATCH_SEARCH_PC

Batch unique at Master data SAP_SCM_BC_BATCH_MGMT_MC Staging Not Not LO-BM N

material and client Table applicable applicable ap
level

Material BOM Master data SAP_PLM_BC_MBOM_PC Staging Not Not PP-BD Ye

(deprecated) Table applicable applicable

This is custom documentation. For more information, please visit SAP Help Portal. 82
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

FI-CA - Cash Transactional SAP_FICA_BC_SCRTY_DEP_PROC_PC Staging Not Not FI-CA N

security deposit data Table applicable applicable ap

ECM - Change Master data SAP_PLM_BC_CM_MC Staging Not Not PLM-WUI- N

master Table applicable applicable OBJ-ECN ap

Characteristic Master data SAP_PLM_BC_CLF_MC Staging Not Not CA-CL Ye

Table applicable applicable

This is custom documentation. For more information, please visit SAP Help Portal. 83
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

AVC - Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

Characteristics Table applicable applicable ap
group

Class Master data SAP_PLM_BC_CLF_MC Staging Not Not CA-CL N

Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 84
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Class hierarchy Master data SAP_PLM_BC_CLF_MC Staging Not Not CA-CL N

Table applicable applicable ap

Object Master data SAP_PLM_BC_DIR_EXTD_MC Staging Not Not CA-CL N

classification - Table applicable applicable ap
Document
(DRAW)

Object Master data SAP_MM_BC_IR_PROCESS_PC Staging Not Not CA-CL N

classification - Table applicable applicable ap
SAP_PLM_BC_CLF_MC
Purchasing info
record (EINA)

Object Master data SAP_CMD_BC_PR_MAINT_PC Staging Not Not CA-CL Ye

classification - Table applicable applicable
Material (MARA)

This is custom documentation. For more information, please visit SAP Help Portal. 85
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Object Master data SAP_CMD_BC_CUST_MAINT_PC Staging Not Not CA-CL Ye

classification - Table applicable applicable
SAP_CMD_BC_PR_MAINT_PC
General template
SAP_CMD_BC_SUPP_MAINT_PC

SAP_EAM_BC_MPLAN_MC

SAP_EAM_BC_TO_MC

SAP_MM_BC_IR_PROCESS_PC

SAP_PLM_BC_CLF_MC

SAP_PLM_BC_CM_MC

SAP_PLM_BC_DIR_EXTD_MC

SAP_QM_BC_BASIC_DATA_PC

SAP_QM_BC_INSP_METHODS_PC

SAP_QM_BC_MSTR_INSP_CHARC_PC

SAP_RFM_BC_SITE_MNGGRP_PC

SAP_SCM_BC_BATCH_MGMT_MC

SAP_SCM_BC_PROC_ENG_MC

SAP_SD_BC_MD_MANAGE_MC

Object Master data SAP_QM_BC_INSP_METHODS_PC Staging Not Not CA-CL N

classification - Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 86
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Inspection method
(QMTB)

Object Master data SAP_QM_BC_BASIC_DATA_PC Staging Not Not CA-CL N

classification - Table applicable applicable ap
Selected set
(QPAM)

Object Master data SAP_QM_BC_BASIC_DATA_PC Staging Not Not CA-CL Ye

classification - Table applicable applicable
Code group
(QPGR)

Object Master data SAP_QM_BC_MSTR_INSP_CHARC_PC Staging Not Not CA-CL N

classification - Table applicable applicable ap
Inspection
characteristic
(QPMK)

CO - Statistical Transactional SAP_FIN_BC_OH_MD_CCA_PC Staging Not Not CO N

key figure data Table applicable applicable ap

Condition contract Master data SAP_MM_BC_CC_CRTE_PC Staging Not Not LO-AB N

Table applicable applicable ap
SAP_MM_BC_CC_MAN_PC

SAP_SD_BC_CC_CRTE_PC

SAP_SD_BC_CC_EC_CRTE_PC

SAP_SD_BC_CC_EC_MNG_PC

SAP_SD_BC_CC_IC_CRTE_PC

SAP_SD_BC_CC_IC_MNG_PC

SAP_SD_BC_CC_MAN_PC

SAP_SD_BC_CC_RS_CRTE_PC

This is custom documentation. For more information, please visit SAP Help Portal. 87
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

SAP_SD_BC_CC_RS_MNG_PC

Condition record Master data SAP_CMD_BC_BP_DISP_PC Staging Not Not SD Ye

for pricing Table applicable applicable
SAP_MM_BC_PRCG_PROCESS_PC
(general template)
SAP_PSP_BC_CUSTOMER_PROJ_PC

SAP_SD_BC_PRICE_MANAGE_MC

AVC - Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

Configuration Table applicable applicable ap
profile (restricted)

This is custom documentation. For more information, please visit SAP Help Portal. 88
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Consent Transactional SAP_CA_BC_CONSENT_MGMT_PC Staging Not Not CA-GTF- N

data Table applicable applicable CON ap

AVC - Constraint Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

Table applicable applicable ap

MM - Purchase Transactional Not applicable Staging Not Not MM-PUR N

contract data Table applicable applicable ap

Customer - extend Master data SAP_CMD_BC_CUST_MAINT_PC Staging Not Not SD N

existing record by Table applicable applicable ap
multiple addresses

This is custom documentation. For more information, please visit SAP Help Portal. 89
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

This is custom documentation. For more information, please visit SAP Help Portal. 90
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Customer - extend Master data SAP_CMD_BC_CUST_MAINT_PC Staging Yes Not SD N

existing record by Table applicable ap
new org levels

This is custom documentation. For more information, please visit SAP Help Portal. 91
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Customer - extend Master data SAP_CMD_BC_CUST_MAINT_PC Staging Not Not SD N

existing record by Table applicable applicable ap
Thailand branch
code

This is custom documentation. For more information, please visit SAP Help Portal. 92
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

This is custom documentation. For more information, please visit SAP Help Portal. 93
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Customer - extend Master data SAP_FIN_BC_CR_CRED_ACC_PC Staging Not Not SD N

existing record by Table applicable applicable ap
credit
management data

This is custom documentation. For more information, please visit SAP Help Portal. 94
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

SD - Customer Master data SAP_SD_BC_MD_MANAGE_MC Staging Yes Not SD N

Material Table applicable ap

Customer Master data SAP_CMD_BC_CUST_MAINT_PC Staging Yes Not SD Ye

Table applicable

This is custom documentation. For more information, please visit SAP Help Portal. 95
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

This is custom documentation. For more information, please visit SAP Help Portal. 96
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

FI-CA - Direct Master data SAP_FIN_BC_AR_DDM_PROC_PC Staging Not Not FI N

debit mandate Table applicable applicable ap

AVC - Object Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

dependencies Table applicable applicable ap

AVC - Dependency Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

net Table applicable applicable ap

DG - Assessment Transactional SAP_PSS_BC_PC_UPKG_DG_MGMT_PC Staging Not Not EHS-SUS- N

for unpackaged data Table applicable applicable DG ap
product (content-
based)

DG - Assessment Master data SAP_PSS_BC_PC_PKG_DG_MGMT_PC Staging Not Not EHS-SUS- N

for packaged Table applicable applicable DG ap
product

DG - Technical Master data SAP_PSS_BC_PC_TECH_NAMES_PC Staging Not Not EHS-SUS- N

names for Table applicable applicable DG ap
substance

DG - Assessment Master data SAP_PSS_BC_PC_UPKG_DG_MGMT_PC Staging Not Not EHS-SUS- N

for unpackaged Table applicable applicable DG ap
product (text-
based)

Document info Master data SAP_PLM_BC_DIR_PC Staging Not Not CA-DMS N

record Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 97
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

FI-CA - Dunning Transactional SAP_FICA_BC_DUN_MASS_PC Staging Not Not FI-CA N

history data Table applicable applicable ap

PM - Master data SAP_EAM_BC_MEADOC_MC Staging Not Not PM N

Measurement Table applicable applicable ap
document

PM - Measuring Master data SAP_EAM_BC_MEAPT_MC Staging Not Not PM Ye

point Table applicable applicable
SAP_EAM_BC_MESP_MNG_PC

PM - Maintenance Transactional SAP_EAM_BC_NTF_MC Staging Yes Not PM N

notification data Table applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 98
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

EFD - Reinf report Transactional SAP_FIN_BC_GL_REPORTING_BR_PC Staging Not Not FI-LOC- N

(Brazil) data Table applicable applicable FI ap

EHS - Location Master data SAP_EHS_BC_ENV_MNG_CSCEN_PC Staging Not Not EHS-SUS- N

aggregation Table applicable applicable EM ap

EHS - Data Master data SAP_EHS_BC_ENV_DT_CLS_MNG_PC Staging Not Not EHS-SUS- N

classifier Table applicable applicable EM ap

EHS - Calculation Master data SAP_EHS_BC_ENV_MNG_CSCEN_PC Staging Not Not EHS-SUS- N

definition Table applicable applicable EM ap

EHS - Location Master data SAP_EHS_BC_ENV_MNG_LOCCL_PC Staging Not Not EHS-SUS- N

classifier Table applicable applicable CI ap

EHS - Deviation Transactional SAP_EHS_BC_ENV_MNG_DEV_PC Staging Not Not EHS-SUS- N

incident data Table applicable applicable EM ap

EHS - Location Master data SAP_EHS_BC_ENV_MNG_LOC_PC Staging Not Not EHS-SUS- N

hierarchy Table applicable applicable FND ap

This is custom documentation. For more information, please visit SAP Help Portal. 99
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

EHS - Location Master data SAP_EHS_BC_IM_MNG_LOC_PC Staging Not Not EHS-SUS- N

Table applicable applicable FND ap

EHS - Data Master data SAP_EHS_BC_ENV_OPR_DATACOL_PC Staging Not Not EHS-SUS- N

collection Table applicable applicable EM ap

EHS - Master data SAP_EHS_BC_ENV_MNG_CHPHYS_PC Staging Not Not EHS-SUS- N

Chemical/Physical Table applicable applicable FND ap
property

PC - Raw material Master data SAP_PSS_BC_PC_FND_RMON_PC Staging Not Not EHS-SUS- N

compliance info Table applicable applicable FND ap

EHS - Compliance Master data SAP_EHS_BC_ENV_MNG_CMPLREQ_PC Staging Not Not EHS-SUS- N

requirement Table applicable applicable CI ap

EHS - Compliance Master data SAP_EHS_BC_ENV_MNG_CSCEN_PC Staging Not Not EHS-SUS- N

scenario Table applicable applicable EM ap

This is custom documentation. For more information, please visit SAP Help Portal. 100
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

EHS - Task Master data SAP_EHS_BC_ENV_TASK_MON_PC Staging Not Not EHS-SUS- N

Table applicable applicable EM ap

PC - Product Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

compliance info Table applicable applicable FND ap

PM - Equipment Master data SAP_EAM_BC_TO_MC Staging Not Not PM N

BOM Table applicable applicable ap
SAP_EAM_BC_TO_MNG_PC

PM - Equipment Master data SAP_EAM_BC_TL_MC Staging Not Not PM N

task list Table applicable applicable ap
SAP_EAM_BC_TSKL_MNG_PC

This is custom documentation. For more information, please visit SAP Help Portal. 101
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

PM - Equipment Master data SAP_EAM_BC_TO_MC Staging Yes Not PM N

Table applicable ap
SAP_EAM_BC_TO_MNG_PC

Warehouse Master data SAP_SCM_BC_EWM_MD_WHSE_PC Staging Not Not SCM-EWM Ye

storage bin Table applicable applicable
SAP_SCM_BC_EWM_MON_PC

Warehouse fixed Master data SAP_SCM_BC_EWM_MD_WHSE_PC Staging Not Not SCM-EWM N

bin assignment Table applicable applicable ap
SAP_SCM_BC_EWM_MON_PC

Warehouse Master data SAP_SCM_BC_EWM_MD_WHSE_PC Staging Not Not SCM-EWM Ye

storage bin sorting Table applicable applicable
SAP_SCM_BC_EWM_MON_PC

Warehouse stock Transactional SAP_SCM_BC_EWM_MD_WHSE_PC Staging Not Not SCM-EWM Ye

(deprecated) data Table applicable applicable
SAP_SCM_BC_EWM_MON_PC

Exchange rate Master data SAP_FIN_BC_CA_CURR_PC Staging Not Not FI Ye

Table applicable applicable

This is custom documentation. For more information, please visit SAP Help Portal. 102
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

FI - Historical Transactional SAP_FIN_BC_GL_JE_PROC_PC Staging Not Not FI Ye

balance data Table applicable applicable

FI-CA - Contract Master data SAP_CMD_BC_BP_MAINT_PC Staging Yes Not FI-CA N

partner Table applicable ap

FI-CA - Contract Master data SAP_FICA_BC_MD_CA_MAINT_PC Staging Yes Not FI-CA N

account Table applicable ap

FI-CA - Installment Transactional SAP_FICA_BC_INSTPL_PROC_PC Staging Not Not FI-CA N

plan data Table applicable applicable ap

FI-CA - Open item Transactional SAP_FICA_BC_DOC_POST_PC Staging Yes Not FI-CA N

data Table applicable ap

FI-CA - Promise to Transactional SAP_FICA_BC_PRMS2P_MAINT_PC Staging Not Not FI-CA N

pay data Table applicable applicable ap

FI-CA - Payment Transactional SAP_FICA_BC_DOC_POST_PC Staging Yes Not FI-CA N

data Table applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 103
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

FI-CA - Provider Master data SAP_FICA_BC_MD_PC_MAINT_PC Staging Yes Not FI-CA N

contract Table applicable ap

Revenue Transactional SAP_FIN_BC_FARR_RAIPRC_PC Staging Not Not FI-RA N

accounting data Table applicable applicable ap
contract

Contract number Transactional SAP_FIN_BC_APAR_OPER_PR_RU_PC Staging Not Not FI-LOC- N

in accounting data Table applicable applicable FI-RU ap
documents
(Russia)

Import customs Transactional SAP_FIN_BC_AP_IMPORT_RU_PC Staging Not Not FI-LOC- N

declaration data Table applicable applicable FI-RU ap
(Russia)

This is custom documentation. For more information, please visit SAP Help Portal. 104
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

RNPT - Traceability Master data SAP_FIN_BC_AP_IMPORT_RU_PC Staging Not Not FI-LOC- N

of goods (Russia) Table applicable applicable FI-RU ap

Fixed asset - Transactional SAP_FIN_BC_AA_DOC_PROC_PC Staging Not Not FI-AA Ye

Postings data Table applicable applicable

Fixed asset - Master data SAP_FIN_BC_AA_MDAT_LDT_PC Staging Yes Not FI-AA Ye

Master data Table applicable
SAP_FIN_BC_AA_MDAT_REG_PC

This is custom documentation. For more information, please visit SAP Help Portal. 105
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Fixed asset - Transactional SAP_FIN_BC_AA_MDAT_USE_OBJ_PC Staging Not Not FI-AA N

Usage object data Table applicable applicable ap

Field Logistics - Master data SAP_OIL_BC_FLOG_CTNMSTR_PC Staging Yes Not CA-FL-SG N

Container Table applicable ap
(restricted)

Field logistics - Transactional SAP_OIL_BC_FLOG_SUPLRITEM_PC Staging Yes Not CA-FL- N

Supplier item data Table applicable SRV ap

PM - Functional Master data SAP_EAM_BC_TL_MC Staging Not Not PM N

location task list Table applicable applicable ap
SAP_EAM_BC_TSKL_MNG_PC

This is custom documentation. For more information, please visit SAP Help Portal. 106
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

PM - Functional Master data SAP_EAM_BC_TO_MC Staging Not Not PM N

location BOM Table applicable applicable ap
SAP_EAM_BC_TO_MNG_PC

PM - Functional Master data SAP_EAM_BC_TO_MC Staging Yes Not PM Ye

location Table applicable
SAP_EAM_BC_TO_MNG_PC

PM - General Master data SAP_EAM_BC_TL_MC Staging Not Not PM N

maintenance task Table applicable applicable ap
SAP_EAM_BC_TSKL_MNG_PC
list

FI - G/L account Transactional SAP_FIN_BC_GL_JE_PROC_PC Staging Yes Not FI Ye

balance and data Table applicable
open/line item

This is custom documentation. For more information, please visit SAP Help Portal. 107
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

HUM - Handling Master data SAP_LO_BC_HU_MANAGE_PC Staging Not Not LO-HU-BF N

unit Table applicable applicable ap

QM - Inspection Master data SAP_QM_BC_INSP_METHODS_PC Staging Not Not QM N

method Table applicable applicable ap

QM - Inspection Master data SAP_QM_BC_INSP_PLANNING_PC Staging Not Not QM N

plan Table applicable applicable ap

FI-CA - Interest Transactional SAP_FICA_BC_INTRST_PROC_PC Staging Not Not FI-CA N

history data Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 108
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

CO - Internal order Transactional SAP_FIN_BC_OH_MD_OPA_PC Staging Not Not CO N

(restricted) data Table applicable applicable ap

Material inventory Transactional SAP_MM_BC_IM_MAT_DOC_API_PC Staging Not Not MM-IM Ye

balance data Table applicable applicable

This is custom documentation. For more information, please visit SAP Help Portal. 109
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

JVA - Joint Master data SAP_FIN_BC_JVA_CMD_PC Staging Not Not CA-JVA N

operating Table applicable applicable ap
agreement

JVA - Joint venture Master data SAP_FIN_BC_JVA_CMD_PC Staging Not Not CA-JVA N
partner Table applicable applicable ap

JVA - Cost center Master data SAP_FIN_BC_JVA_CMD_PC Staging Not Not CA-JVA N
suspense Table applicable applicable ap

JVA - Venture Master data SAP_FIN_BC_JVA_CMD_PC Staging Not Not CA-JVA N

suspense Table applicable applicable ap

JVA - Project Master data SAP_FIN_BC_JVA_CMD_PC Staging Not Not CA-JVA N

suspense Table applicable applicable ap

CO - Cost center Master data SAP_FIN_BC_OH_MD_CCA_PC Staging Not Not CO N

(deprecated) Table applicable applicable ap

Legal document Transactional SAP_LCM_BC_ADMINISTRATOR_PC Staging Yes Not CM-GF Ye

data Table applicable

Legal transaction Transactional SAP_LCM_BC_ADMINISTRATOR_PC Staging Yes Not CM-GF N

data Table applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 110
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Material listing Master data SAP_SD_BC_MD_MANAGE_MC Staging Not Not SD N

and exclusion Table applicable applicable ap

CO - Activity type Master data SAP_FIN_BC_OH_MD_CCA_PC Staging Not Not CO N

Table applicable applicable ap

PM - Maintenance Master data SAP_EAM_BC_MNTITEM_MNG_PC Staging Yes Not PM N

item Table applicable ap
SAP_EAM_BC_MPLANIT_MC

PM - Maintenance Master data SAP_EAM_BC_MPLAN_MC Staging Yes Not PM N

plan Table applicable ap
SAP_EAM_BC_MP_MNG_PC

This is custom documentation. For more information, please visit SAP Help Portal. 111
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Product Master data SAP_SLL_BC_CLS_CMMDTYCODE_PC Staging Not Not FT-ITR- N

classification - Table applicable applicable CLS ap
Commodity code

Material - Forecast Master data SAP_CMD_BC_PR_MAINT_PC Staging Not Not MM N

planning Table applicable applicable ap

Product Master data SAP_SLL_BC_CLS_LEGCTRL_PC Staging Not Not FT-ITR- N

classification - Table applicable applicable CLS ap
Legal control

AVC - Material Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

variant Table applicable applicable ap

SD - Condition Master data SAP_SD_BC_MD_MANAGE_MC Staging Not Not SD N

Record for Table applicable applicable ap
Material
determination

FI - Cash memo Transactional SAP_FIN_BC_CM_OPS_BASIC_PC Staging Not Not FIN- N

record data Table applicable applicable FSCM-CLM ap

EHS - Incident Transactional SAP_EHS_BC_IM_INC_MGMT_PC Staging Not Not EHS-SUS- N

data Table applicable applicable IM ap

Condition record Master data SAP_MM_BC_PRCG_PROCESS_PC Staging Not Not MM-PUR Ye

for pricing in Table applicable applicable
purchasing
(restricted)

Change request Master data SAP_EHS_BC_MOC_CREQ_MNG_PC Staging Not Not CA-IAM- N

and activity for Table applicable applicable MOC ap
SAP Management
of Change

This is custom documentation. For more information, please visit SAP Help Portal. 112
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

QM - Master Master data SAP_QM_BC_MSTR_INSP_CHARC_PC Staging Not Not QM Ye

inspection Table applicable applicable
characteristic

JIT - Customer Master data SAP_LE_BC_JIT_CUST_MAINT_PC Staging Not Not LE-JIT- N

Table applicable applicable S2C ap

JIT - Packing Master data SAP_LE_BC_JIT_CUST_MAINT_PC Staging Not Not LE-JIT- N

group Table applicable applicable S2C ap
specification

JIT - Supply Master data SAP_LE_BC_JIT_CUST_MAINT_PC Staging Not Not LE-JIT- N

control Table applicable applicable S2C ap

FI - Accounts Transactional SAP_FIN_BC_GL_JE_PROC_PC Staging Not Not FI-AP Ye

payable open item data Table applicable applicable

FI - Accounts Transactional SAP_FIN_BC_GL_JE_PROC_PC Staging Not Not FI-AR Ye

receivable open data Table applicable applicable
item

Order BOM Master data SAP_PLM_BC_MBOM_PC Staging Not Not PP-BD N

Table applicable applicable ap
SAP_PLM_BC_SALES_ORDER_BOM_PC

This is custom documentation. For more information, please visit SAP Help Portal. 113
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

PMA - Customer Master data SAP_PSS_BC_PC_CCM_CRR_MON_PC Staging Not Not EHS-SUS- N

compliance Table applicable applicable PMA ap
SAP_PSS_BC_PC_CCM_MAN_PC
assessment

SAP_PSS_BC_PC_FND_PMON_PC

SAP_PSS_BC_PC_PMA_ANALYZE_PC

SAP_PSS_BC_PC_PROD_CRR_MON_PC

PMA - Simple Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

compliance Table applicable applicable PMA ap
SAP_PSS_BC_PC_FND_RMON_PC
assessment

SAP_PSS_BC_PC_FND_SMMON_PC

SAP_PSS_BC_PC_PMA_ANALYZE_PC

SAP_PSS_BC_PC_PROD_CRR_MON_PC

SAP_PSS_BC_PC_RM_CRR_MON_PC

PMA - Supplier Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

information Table applicable applicable PMA ap
SAP_PSS_BC_PC_FND_RMON_PC
assessment
SAP_PSS_BC_PC_FND_SMMON_PC

SAP_PSS_BC_PC_PMA_ANALYZE_PC

SAP_PSS_BC_PC_PROD_CRR_MON_PC

SAP_PSS_BC_PC_RM_CRR_MON_PC

PC - Material- Transactional SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

based data Table applicable applicable FND ap
composition

This is custom documentation. For more information, please visit SAP Help Portal. 114
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

PC - Physical- Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

chemical property Table applicable applicable FND ap
SAP_PSS_BC_PC_FND_RMON_PC

SAP_PSS_BC_PC_SUBST_MAN_PC

PC - Analytical Transactional SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

composition data Table applicable applicable FND ap
SAP_PSS_BC_PC_FND_RMON_PC

PC - Confidential Transactional SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

business data Table applicable applicable FND ap
information

PC - Polymer Transactional SAP_PSS_BC_PC_SUBST_MAN_PC Staging Not Not EHS-SUS- N

composition data Table applicable applicable FND ap

This is custom documentation. For more information, please visit SAP Help Portal. 115
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

SDS - Assessment Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

for unpackaged Table applicable applicable SDS ap
SAP_PSS_BC_PC_FND_RMON_PC
product

SDS - Shipment Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

history Table applicable applicable SDS ap

PC - Safety- Master data SAP_PSS_BC_PC_FND_PMON_PC Staging Not Not EHS-SUS- N

related property Table applicable applicable FND ap
SAP_PSS_BC_PC_FND_RMON_PC

SAP_PSS_BC_PC_SUBST_MAN_PC

PM - Maintenance Transactional SAP_EAM_BC_MP_ORD_DSP_PC Staging Yes Not PM N

order data Table applicable ap
SAP_EAM_BC_ORD_MNG_PC

This is custom documentation. For more information, please visit SAP Help Portal. 116
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Master recipe Master data SAP_SCM_BC_PPROC_ENG_MC Staging Not Not PP-PI Ye

Table applicable applicable

PP - Process order Transactional SAP_SCM_BC_PROC_ORD_MGMT_MC Staging Not Not PP-PI- N

(only open PO) data Table applicable applicable POR ap

This is custom documentation. For more information, please visit SAP Help Portal. 117
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

PP - Production Transactional SAP_SCM_BC_PRODN_ORD_MPLN_MC Staging Not Not PP-SFC N

order (only open data Table applicable applicable ap
PO)

PP-KAB - Master data SAP_SCM_BC_KNBN_CTRLC_MGMT_MC Staging Yes Not PP-KAB N

Production supply Table applicable ap
area

Enterprise project Master data SAP_PS_BC_PROJ_CONTRL_MC Staging Yes Not PPM-SCL- N

Table applicable STR ap

CO - Profit center Master data SAP_FIN_BC_OH_MD_PCA_PC Staging Not Not CO N

Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 118
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Product Transactional SAP_CMD_BC_PR_MAINT_PC Staging Not Not MM N

consumption data Table applicable applicable ap

Product - extend Master data SAP_CMD_BC_PR_MAINT_PC Staging Yes Not LO-MD-MM N

existing record by Table applicable ap
new org levels

Product hierarchy Master data SAP_CMD_BC_PR_MAINT_PC Staging Not Not LO N

Table applicable applicable ap

Product hierarchy Master data SAP_CMD_BC_PR_MAINT_PC Staging Not Not LO N

assignment Table applicable applicable ap

Product - extend Master data SAP_CMD_BC_PR_MAINT_PC Staging Not Not LO N

existing record Table applicable applicable ap
with long text

This is custom documentation. For more information, please visit SAP Help Portal. 119
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Service product Master data SAP_CMD_BC_PR_MAINT_PC Staging Yes Not LO N

Table applicable ap

Product Master data SAP_CMD_BC_PR_MAINT_PC Staging Yes Not LO-MD-MM Ye

Table applicable

Production version Master data SAP_SCM_BC_PPROC_ENG_MC Staging Not Not PP Ye

Table applicable applicable
SAP_SCM_BC_PROC_ENG_MC

This is custom documentation. For more information, please visit SAP Help Portal. 120
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Commercial Master data SAP_PSP_BC_MIG_PROFNL_PROJ_PC Staging Yes Not CA-CPD- Ye

project Table applicable SS

PP-KAB - Kanban Master data SAP_SCM_BC_KNBN_CTRLC_MGMT_MC Staging Not Not PP-KAB N

control cycle Table applicable applicable ap

PSM - Earmarked Transactional SAP_PSM_BC_EMRKFNDS_API_PC Staging Not Not PSM-FM N

funds data Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 121
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

PSM - Functional Master data SAP_PSM_BC_MD_BDGTSP_PC Staging Not Not PSM-FM- N

area Table applicable applicable MD ap

PSM - Fund Master data SAP_PSM_BC_MD_BDGTSP_PC Staging Yes Not PSM-FM N

Table applicable ap

PSM - Grant Master data SAP_PSM_BC_MD_GRNTSP_PC Staging Yes Not PSM-GM- N

Table applicable GTE-MD ap

PSM - Sponsored Master data SAP_PSM_BC_MD_GRNTSP_PC Staging Not Not PSM-GM- N

class Table applicable applicable GTE-MD ap

PSM - Sponsored Master data SAP_PSM_BC_MD_GRNTSP_PC Staging Not Not PSM-GM- N

program Table applicable applicable GTE-MD ap

PSM - Sponsor Master data SAP_PSM_BC_MD_GRNTSP_PC Staging Not Not PSM-GM- N

Table applicable applicable GTE-MD ap

MM - Purchasing Master data SAP_MM_BC_IR_PROCESS_PC Staging Yes Not MM-PUR N

info record- extend Table applicable ap
existing record

MM - Model Master data SAP_MM_BC_MPS_PROCESS_PC Staging Yes Not MM-PUR- N

product Table applicable MPS ap
specification

MM - Purchase Transactional SAP_MM_BC_PO_MANAGE_PC Staging Yes Not MM-PUR N

order (only open data Table applicable ap
SAP_MM_BC_PURCH_DOC_DSP_PC
PO)
SAP_PS_BC_PROJ_FIN_ANLYTC_MC

This is custom documentation. For more information, please visit SAP Help Portal. 122
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

MM - Purchasing Master data SAP_MM_BC_IR_PROCESS_PC Staging Yes Not MM-PUR Ye

info record with Table applicable
conditions

QM - Certificate Master data SAP_QM_BC_CERTIFICATE_PLNG_PC Staging Not Not QM N

profile incl. Table applicable applicable ap
assignment

QM/PM - Catalog Master data SAP_QM_BC_BASIC_DATA_PC Staging Not Not QM N

code group/code Table applicable applicable ap

QM - Quality info Master data SAP_QM_BC_QM_PROCUREMENT_PC Staging Not Not QM N

record Table applicable applicable ap

Real estate Transactional SAP_FIN_BC_RECM_CONTRACT_PC Staging Yes Not RE-FX Ye

contract data Table applicable

This is custom documentation. For more information, please visit SAP Help Portal. 123
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Real estate - Master data SAP_FIN_BC_REIP_LOCATION_PC Staging Yes Not RE-FX N

Usage enablement Table applicable ap
group

Real estate - Master data SAP_FIN_BC_REIP_LOCATION_PC Staging Yes Not RE-FX N

Occupancy group Table applicable ap

RFM - Assortment Master data SAP_RFM_BC_ASSTMT_MAINT_PC Staging Not Not LO-RFM- N

module Table applicable applicable MD-LST ap

RFM - Master data SAP_RFM_BC_MRCHDSCAT_MNTN_PC Staging Not Not LO-RFM- N

Merchandise Table applicable applicable MD-MC ap
category

RFM - Master data SAP_RFM_BC_MRCHDSCAT_MNTN_PC Staging Not Not LO-RFM- N

Merchandise Table applicable applicable MD-MC ap

This is custom documentation. For more information, please visit SAP Help Portal. 124
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

category
characteristic
value restriction

RFM - Master data SAP_RFM_BC_MRCHDSCAT_MNTN_PC Staging Not Not LO-RFM- N

Merchandise Table applicable applicable MD-MC ap
category hierarchy
node

RFM - Master data SAP_RFM_BC_MRCHDSCAT_MNTN_PC Staging Not Not LO-RFM- N

Merchandise Table applicable applicable MD-MC ap
category hierarchy
node assignment

RFM - MCHN Master data SAP_RFM_BC_MRCHDSCAT_MNTN_PC Staging Not Not LO-RFM- N

Characteristic Table applicable applicable MD-MC ap
value restriction

RFM - Master data SAP_RFM_BC_MRCHDSCAT_MNTN_PC Staging Not Not LO-RFM- N

Merchandise Table applicable applicable MD-MC ap
category reference
article

RFM - Product Master data SAP_RFM_BC_ASSTMT_MAINT_PC Staging Yes Not LO-RFM- N

assignment to Table applicable MD-LST ap
distribution center

RFM - Site master Master data SAP_RFM_BC_SITE_MAINT_PC Staging Not Not LO-RFM- N
Table applicable applicable MD-SIT ap

RFM - Supplying Master data SAP_RFM_BC_SITE_MAINT_PC Staging Not Not LO-RFM- N

site Table applicable applicable MD-SIT ap

MM - Purchase Transactional SAP_MM_BC_SA_PROCESS_MC Staging Not Not MM-PUR N

scheduling data Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 125
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

agreement

Condition record Master data SAP_PSP_BC_CUSTOMER_PROJ_PC Staging Not Not SD Ye

for pricing in sales Table applicable applicable
SAP_SD_BC_PRICE_MANAGE_MC
(restricted)

This is custom documentation. For more information, please visit SAP Help Portal. 126
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

SD - Sales Transactional SAP_SD_BC_CONTR_PROC_MC Staging Not Not SD N

contract data Table applicable applicable ap

SD - Condition Master data SAP_SD_BC_MD_MANAGE_MC Staging Not Not SD N

record for free Table applicable applicable ap
goods

SD - Sales Transactional SAP_SD_BC_SLS_SCHEDULE_PC Staging Not Not SD-SLS N

scheduling data Table applicable applicable ap
agreement

QM - Selected set Master data SAP_QM_BC_BASIC_DATA_PC Staging Not Not QM N

Table applicable applicable ap

QM - Selected set Master data SAP_QM_BC_BASIC_DATA_PC Staging Not Not QM N

code Table applicable applicable ap
SAP_QM_BC_INSP_PLANNING_PC

This is custom documentation. For more information, please visit SAP Help Portal. 127
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

FI - SEPA mandate Master data SAP_FIN_BC_AR_SEPA_EDIT_PC Staging Not Not FI N

Table applicable applicable ap

SD - Sales order Transactional SAP_SD_BC_SO_PROC_MC Staging Yes Not SD Ye

(only open SO) data Table applicable

MM - Source list Master data Not applicable Staging Not Not MM-PUR N
Table applicable applicable ap

This is custom documentation. For more information, please visit SAP Help Portal. 128
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Service contract Transactional SAP_S4CRM_BC_SERV_CONTR_PC Staging Yes Not CRM-S4- Ye

data Table applicable SRV-CTR

Service order Transactional SAP_CRM_BC_SERV_PROCORDER_PC Staging Yes Not CRM-S4- N

(only open SRVO) data Table applicable SRV-SVO ap

PC - Substance Master data SAP_PSS_BC_PC_SUBST_MAN_PC Staging Not Not EHS-SUS- N

Table applicable applicable FND ap

TRM - Bank Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- Ye

guarantee data Table applicable applicable FSCM-TRM

TRM - Commercial Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- N

paper data Table applicable applicable FSCM- ap
TRM-TM

TRM - FX option Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- N

data Table applicable applicable FSCM- ap
TRM-TM

This is custom documentation. For more information, please visit SAP Help Portal. 129
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

TRM - Foreign Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- Ye

exchange collar - data Table applicable applicable FSCM-TRM
contract

TRM - Foreign Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- Ye

exchange swap - data Table applicable applicable FSCM-
contract TRM-TM

TRM - Foreign Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- Ye

exchange data Table applicable applicable FSCM-
spot/forward TRM-TM
transaction -
contract

TRM - Interest rate Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- N

instrument data Table applicable applicable FSCM-TRM ap

TRM - Interest rate Transactional SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- N

swap data Table applicable applicable FSCM- ap
TRM-TM

TRM - Letter of Master data SAP_FIN_BC_TRM_MFT1_PC Staging Not Not FIN- N

credit Table applicable applicable FSCM- ap
TRM-TM-
TF

TRM - Position Transactional SAP_FIN_BC_TRM_LGCYDT_PC Staging Not Not FIN- Ye

value data Table applicable applicable FSCM-
TRM-TM

This is custom documentation. For more information, please visit SAP Help Portal. 130
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

AVC - Assign Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

global dependency Table applicable applicable ap
to characteristic

AVC - Assign Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N

global dependency Table applicable applicable ap
to characteristic
value

AVC - Variant table Master data SAP_LO_BC_VC_MODELING_PC Staging Not Not LO-VCH N
entry Table applicable applicable ap

Supplier - extend Master data SAP_CMD_BC_SUPP_MAINT_PC Staging Not Not MM N

existing record by Table applicable applicable ap
multiple addresses

This is custom documentation. For more information, please visit SAP Help Portal. 131
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Supplier - extend Master data SAP_CMD_BC_SUPP_MAINT_PC Staging Yes Not MM N

existing record by Table applicable ap
new org levels

Supplier - extend Master data SAP_CMD_BC_SUPP_MAINT_PC Staging Not Not MM N

existing record by Table applicable applicable ap
Thailand branch
code

This is custom documentation. For more information, please visit SAP Help Portal. 132
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Supplier Master data SAP_CMD_BC_SUPP_MAINT_PC Staging Yes Not MM Ye

Table applicable

This is custom documentation. For more information, please visit SAP Help Portal. 133
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Work Master data SAP_SCM_BC_PPROC_ENG_MC Staging Not Not PP N

center/Resource Table applicable applicable ap
SAP_SCM_BC_PROC_ENG_MC

This is custom documentation. For more information, please visit SAP Help Portal. 134
 11/21/25, 3:20 AM

Migration Object Business Business Catalog Migration Custom Supported Component S

Name Object Type Approach Field by App D
Support "Analyze
Your
Selection
Process"

Warranty claim Transactional SAP_LO_BC_WTY_MANAGECLAIM_PC Staging Yes Not LO-WTY- N

data Table applicable FIO ap

 Caution
Data protection legislation may require that personal data be deleted after the data has served its originally defined 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 that should have been deleted could be interpreted as the processing of personal data
without any legally justified purpose.

 Note
For some migration objects, there are additions to the migration object name. These additions include "restricted" and
"deprecated". Restricted means that not all fields and structures of the relevant business processes are covered by this
migration object. Deprecated means that there’s a newer version of this migration object available. Deprecated objects will be
deleted after a couple of releases. Make sure that you always read the migration object documentation for these objects
carefully. Also see SAP Note 2698032 for more details on deprecated migration objects.

 Note
Migration objects are built for initial migration of your data to your SAP S/4HANA Cloud Public Editionsystem. This means that
you can create data with a migration object, but you can't change or update existing data with it.

Further Information

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

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

[Link] this very topic: Available Migration Objects

[Link] the landing page for data migration

[Link] the entry topic: Data Migration Status

If you want to view information about the differences between the current release and the previous release, see SAP
S/4HANA Cloud Public Edition – Release Comparison of Migration Object Templates (for customers and partners only).

If you want to migrate historical financial transactions into your SAP S/4HANA Cloud Public Edition using the SAP
S/4HANA migration cockpit, see SAP Note 2943035 .

For information regarding mapping of unit of measures, see SAP Knowledge Base Article 2907822 .

This is custom documentation. For more information, please visit SAP Help Portal. 135
 11/21/25, 3:20 AM

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.

Situation Handling

This app uses Situation Handling, which automatically informs users responsible about matters that require their attention. If a
matching situation type is enabled, situations will be displayed directly in this app. For your convenience, a situation type has

This is custom documentation. For more information, please visit SAP Help Portal. 136
 11/21/25, 3:20 AM
automatically been enabled for this app. If you don't want to use this feature, you can disable or delete the enabled situation type
in the Manage Situation Types app. For more information, see Situation Handling for Data Migration.

Related Information

Data Migration Status in the SAP Fiori Apps Reference Library.

See also 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...

[Link] this very topic: Data Migration Status

[Link] the landing page for data migration

[Link] the entry topic: Available Migration Objects

Supported Device Types

Desktop

Tablet

Changing a View

Context

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
This is custom documentation. For more information, please visit SAP Help Portal. 137
 11/21/25, 3:20 AM

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.

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.

This is custom documentation. For more information, please visit SAP Help Portal. 138
 11/21/25, 3:20 AM

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

Customizing Extended Statistics

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

This is custom documentation. For more information, please visit SAP Help Portal. 139
 11/21/25, 3:20 AM
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.

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

Audit Authorizations
Per default, the audit authorizations are included in the standard business role template for data migration (Configuration Expert
- Data Migration, SAP_BR_CONFIG_EXPERT_DATA_MIG).

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

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

This is custom documentation. For more information, please visit SAP Help Portal. 140
 11/21/25, 3:20 AM
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
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.

This is custom documentation. For more information, please visit SAP Help Portal. 141
 11/21/25, 3:20 AM

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.

 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

This is custom documentation. For more information, please visit SAP Help Portal. 142
 11/21/25, 3:20 AM
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
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.

This is custom documentation. For more information, please visit SAP Help Portal. 143
 11/21/25, 3:20 AM

 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 SAP S/4HANA Cloud Public Edition, open the Analyze Your Selection Process app on the SAP 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
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.

This is custom documentation. For more information, please visit SAP Help Portal. 144
 11/21/25, 3:20 AM
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.

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

This is custom documentation. For more information, please visit SAP Help Portal. 145
 11/21/25, 3:20 AM
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. If a
matching situation type is enabled, situations will be displayed directly in this app. For your convenience, a situation type has
automatically been enabled for this app. If you don't want to use this feature, you can disable or delete the enabled situation type
in the Manage Situation Types app. For more information, see Situation Handling.

For data migration, the automatically enabled situation type is named Data Migration Complete
(CA_DATA_MIGRATION_STEP_COMPLETED).

 Note
This situation type is only enabled automatically if no situation type from the standard template previously exists in your SAP
S/4HANA Cloud Public Edition system.

Once you’ve disabled or deleted the automatically enabled situation type, it won’t be reactivated or recreated by the shipment
of the next SAP S/4HANA Cloud Public Edition version.

This is custom documentation. For more information, please visit SAP Help Portal. 146
 11/21/25, 3:20 AM

 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

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:

This is custom documentation. For more information, please visit SAP Help Portal. 147
 11/21/25, 3:20 AM

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 Cloud Public Edition.

SAP S/4HANA Migration Cockpit

The following tutorial videos help you better understand how to use the SAP S/4HANA Migration Cockpit.

This is custom documentation. For more information, please visit SAP Help Portal. 148
 11/21/25, 3:20 AM
This video walks you through the steps to load an object using XML files in the migration cockpit.

This video walks you through the steps to load an object using CSV files in the migration cockpit.

This video walks you through the steps to directly migrate data from an SAP system in the migration cockpit.

This is custom documentation. For more information, please visit SAP Help Portal. 149
 11/21/25, 3:20 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 Cloud Public Edition 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 SAP Help Portal. 150
 11/21/25, 3:20 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.

Migrate Your Data - Migration Cockpit (Old) - Deprecated

The app Migrate Your Data - Migration Cockpit is the successor of the Migrate Your Data - Migration Cockpit (Old) app. The
Migrate Your Data - Migration Cockpit (Old) app is deprecated and will be deleted from the SAP Fiori launchpad in an upcoming
release.

It is not possible to use the Migrate Your Data - Migration Cockpit (Old) app to migrate data to SAP S/4HANA Cloud Public
Edition. However, you can still view any projects that you created when using this app.

This is custom documentation. For more information, please visit SAP Help Portal. 151