0% found this document useful (0 votes)

2K views71 pages

Data Migration For S4Hana

The document discusses different approaches for migrating data to SAP S/4HANA using the SAP S/4HANA Migration Cockpit. It provides an overview of migration objects available for SAP S/4HANA and describes migrating from file-based and direct systems to SAP S/4HANA.

Uploaded by

Yazeed_Gh

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

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

2K views71 pages

Data Migration For S4Hana

Uploaded by

Yazeed_Gh

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

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 71

1/1/2021

Data Migration
Generated on: 2021-01-01 22:16:29 GMT+0000

SAP S/4HANA | 2020 Latest

PUBLIC

Original content: https://help.sap.com/viewer/29193bf0ebdd4583930b2176cb993268/2020.000/en-US

Warning

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

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 1/71
1/1/2021

Data Migration
SAP enables data migration to SAP S/4HANA for customers coming from any legacy system. SAP S/4HANA customers can take
advantage of reliable migration approaches built into SAP S/4HANA using the SAP S/4HANA Migration Cockpit together with a
set of prede ned data migration objects.

Product SAP Object-Related Training and Getting Started News Further SAP Community
The Assistance Best Information Education Informati
image Practice Presentati S on The SAP S/4HANA
map SAP s Migration Training on: A Migration Cockpit is
on the S/4HANA Objects for Material Migrate P SAP SAP’s recommended
left Migration Data SAP (for Your Data S Not solution for the
allows Cockpit Migratio S/4HANA customers to SAP / e migration of business
you to n to SAP and S/4HANA 4 253 data to SAP S/4HANA
explor When Find an – SAP H
S/4HAN partners 754 and SAP S/4HANA
e the implementin A from extensive S/4HANA A Cloud. The SAP
only) 9
topics g your SAP File table listing Migration N : S/4HANA Migration
of dataS/4HANA (BH5) all Video Cockpit A Coll Cockpit Community
migrat solution, you migration Library for M ecti comprises of
ion. objects Data Read this
can migrate The BH5 ig ve knowledgeable peers
Choos your master scope available for Migration to learn
r SAP and SAP experts who
e an data and SAP more
item openSAP a Not are eager to share their
eleme business S/4HANA, about the
describe Course: ti e discoveries, best
nt to together SAP
data from s data Migrating o and practices, and
see with their S/4HANA
SAP migratio Your n FAQ experiences and offers
more systems and n to SAP respective Migration
Business C for a one-stop shop for all
inform non-SAP migration Cockpit
S/4HAN Data to o SAP the most relevant
ation. systems to A for object c
SAP Intro S/4 information.
SAP documentat k
custome S/4HANA Video: SAP HA
ion.
S/4HANA. rs – New S/4HANA p NA Visit the SAP
To do this, coming Implement Migration it Mig S/4HANA Migration
you use the from any  Note – rati Cockpit Community
ation Cockpit:
SAP legacy The D on .
Scenario The Built-
S/4HANA system docume e Coc
In Tool for
Migration using a ntation v kpit
Join this Simple
Cockpit. le- for el -
free open Migration
migratio
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 2/71
1/1/2021
There are based n online Discover o File
different approac objects course to how the p /St
approaches h. for the get an SAP m agin
available to Migrate introductio S/4HANA e g
migrate yourUse the Data n to data Migration n (On
data to your following Directly migration Cockpit t Pre
SAP link to from with SAP helps N mis
S/4HANA navigate SAP S/4HANA, make data e e/
system. to the System and where migration w S4C
Data approac it ts in fast and sl OR
Use the Migratio h is with hassle-free e E)
following n to SAP currentl respect to for both tt
links to S/4HAN SAP
y only the new and e
navigate to A from Not
available different current r
the latest File e
in the transition SAP
product (BH5) G 278
system. scenarios. customers
assistance scope e 037
This course moving to
for the item on t 8
Creating a will focus SAP
respective SAP Best al :
New on the new S/4HANA.
approach: Practices l Co
Migration implement See how
Explorer t mp
Object with ation the cockpit
Migr . h osit
the scenario, comes
ation e e
Cock migration with a deep built-in
n SAP
pit Data object dive into with SAP
(Tran Migratio e Not
modeler the SAP S/4HANA
sacti w e
on n to SAP S/4HANA and SAP
LTM S/4HAN Get details s for
migration S/4HANA
C) A from on how to d SAP
cockpit and Cloud –
create your ir S/4
Trans Staging the and how it
ferrin (2Q2) own e HA
migration can bene t
g migration c NA
Data object you today.
You can object with tl Mig
to modeler.
SAP also with SAP y rati
S/4H Technical fr on
migrate migration
ANA
Usin data into object Brief: o Coc
g SAP modeler. Migrate m kpit
Stagi Your Data t
ng S/4HAN This is
SAP
Table A from available in to SAP h
Kno
s legacy the SAP S/4HANA e
wle
Quickly, d
Migr systems S/4HANA
dge
ate using a Migration Safely, and e
Data Bas
staging Cockpit. Cost- v
Direc e
tly area with Effectively el
SAP Arti
from staging o
SAP S/4HANA – cle
Discover p
Systetables as Release 273
m a source why the m
Comparison 325
for the SAP e
of Migration 3
SAP S/4HANA n
Object :
S/4HAN Migration t
Templates FAQ
A Cockpit is t
(for for
Migratio the best e
customers SAP
n way to a
and S/4
Cockpit. migrate m
partners HA
your o
only) NA
legacy f

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 3/71
1/1/2021
Use the The data to S Mig
following purpose of SAP A rati
link to this S/4HANA P on
navigate document and SAP S Coc
to the is to explain S/4HANA / kpit
Data the Cloud. See 4 -
Migratio diﬀerences how it H Tra
n to SAP between helps you A nsfe
S/4HAN the SAP when N r
A from S/4HANA installing A opti
Staging data SAP M on:
(2Q2) migration S/4HANA ig Tra
scope object for the rst r nsfe
item on templates time to a r
SAP Best of various move your ti dat
Practices releases, master o a
Explorer with the and n fro
. help of a business C m
direct data from o sta
comparison SAP or c ging
of the non-SAP k tabl
templates. software p es
systems, it
Data SAP
safely and .
Migration S/4
easily.
Template D HA
Samples SAP a NA
(for S/4HANA t Mig
customers Migration a rati
and Cockpit: M on
partners Frequently ig Coc
only) Asked r kpit
Questions a -
These
(FAQs) ti Filli
template
o ng
samples Read this
n Sta
help you in FAQ to
C ging
lling out learn the
o Tabl
the data scope of
n es
migration the
t with
templates solution
e Dat
of various and other
n a
data informatio
t Usi
migration n
D ng
objects necessary
e SAP
available in to start
v HA
the SAP and lead
el NA
S/4HANA the
o Stu
Migration migration
p dio
Cockpit. project
m :
successfull
Note that e Get
y.
the n det
templates Starter t ails
are created Blog for N on
for, and SAP e how

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 4/71
1/1/2021
tested in, S/4HANA w to
SAP Migration sl ll
S/4HANA Cockpit e sta
Cloud. They tt ging
This blog
can be e tabl
provides
loaded into r es
an entry
the SAP with
point for Fi
S/4HANA SAP
the tool n
Cloud HA
that d
system they NA
facilitates d
are built for. Stu
the e
Although dio
transfer of t
it’s not usin
business ai
possible to g
data to an ls
load them the
SAP o
into an SAP le-
S/4HANA n
S/4HANA bas
system: d
system, you ed
the SAP a
can app
S/4HANA t
manually roa
Migration a
compare ch.
Cockpit. m
these
ig For
pre lled
r furt
templates
a her
with a
ti info
template
o rma
from your
n tion
SAP
c abo
S/4HANA
o ut
system.
n em
Fixed asset t bed
(incl. e din
balances n g
and t the
transaction i SAP
s): Available n S/4
Fields per t HA
Asset Class h NA
(for e Mig
customers c rati
and o on
partners n Coc
only) t kpit
e in
This
x you
document
t r
provides a
o over
detailed
f all
explanation
S new
and listing
A imp
of asset
P lem
classes and
S ent
available
/ atio
elds per
4 n

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 5/71
1/1/2021
asset class H proj
to support A ect,
you when N refe
you ll out A r to
the data M the
migration ig Roa
template r dm
for the a ap
Fixed asset ti Vie
(incl. o wer
balances n .
and C
transaction o
s) migration c
object. k
p
Deprecated
it
Migration
.
Objects (for
M
customers
o
and
r
partners
e
only)
o
This v
document e
is intended r,
to give an t
overview of h
migration is
objects that d
have the o
suﬃx c
"deprecate u
d". You’ll m
also learn e
how to deal n
with t
deprecated li
migration s
objects. t
s
Support of n
Custom e
Fields (for w
customers K
and B
partners A
only) s,
ti
In the
p
extensibility
s,
framework,
a
certain
n
migration
d
objects are
tr

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 6/71
1/1/2021
available to ic
add custom k
elds by s.
using the
Custom
Fields and
Logic
application.
This
document
is intended
to provide
an overview
about
migration
objects
supported
by the
extensibility
framework.

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

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

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

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

Migration Cockpit (Transaction LTMC)

Context
When implementing your SAP S/4HANA solution, you can migrate your master data and business data from SAP systems and
non-SAP systems to SAP S/4HANA. To do this, you use the SAP S/4HANA migration cockpit.

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

 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 de ned purpose
and is also no longer subject to additional legal data retention requirements.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 7/71
1/1/2021
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 justi ed purpose.

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

Options for Transferring Data

There are two options for transferring data to SAP S/4HANA:

You can use les to specify the relevant data.

You can use Microsoft Excel XML les (provided by SAP) for each migration object that is relevant for the transfer. You
download the le for the migration object, specify the relevant data, and then upload the le.

You can use staging tables to specify the relevant data.

The SAP S/4HANA migration cockpit can automatically create staging tables in a staging system (running SAP HANA) for
each migration object that is relevant for your project. You can ll the staging tables with data either manually or by using
your preferred tools (for example SAP Agile Data Preparation).

Which Option is More Suitable for My Data Transfer Project?

The following general recommendations apply:

Use staging tables if you want to transfer a lot of data to SAP S/4HANA in an automated way. Staging tables are database
tables and therefore provide greater exibility than les with regard to managing data (for example sorting data, searching
for data, checking for duplicate records and so on). Staging tables are a more eﬃcient way of transferring large volumes of
data.

Use les if you want to import a small amount of data manually. This gives you the opportunity to have an overview of all
the entered data.

Note the following considerations when deciding on the most suitable approach for your project:

Consideration Files Staging Tables

Size Limit The default size limit for each uploaded XML le is 100 MB. The No Limit.
maximum permitted size is 160 MB. *

System None. Staging system uses an SAP HANA database.

Considerations

Data Enter data manually in each Microsoft Excel XML le. Fill tables manually or by using preferred tools (for
Provisioning example SAP Agile Data Preparation).

* For on-premise systems, parameter icm/HTTP/max_request_size_KB controls the size of the HTTP request. The value of
this parameter is the maximum size (in KB) of an HTTP request. This parameter has the standard value 102400 kb (100MB) but
can be changed if required. For more information, see icm/HTTP/max_request_size_KB

Transferring Data to SAP S/4HANA Using Files

Context

Important Considerations

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 8/71
1/1/2021
The SAP S/4HANA migration cockpit uses Microsoft Excel XML les. The default size limit for each uploaded le is 100 MB.
However, you can increase the size limit for each uploaded le to 160MB by changing the system parameter
icm/HTTP/max_request_size_KB, which controls the size of the http request. The value of this parameter is the maximum
size (in KB) of an HTTP request. This parameter has the standard value 102400 kb (100MB) but can be changed if required. For
more information, see icm/HTTP/max_request_size_KB

If required, you can zip several les together. Note that the combined size of all the XML les you want to add to the zip le must
not exceed 160MB. The limit for the zip le is still 160 MB with the adjusted system parameter.

Prerequisites

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

To transfer data using the SAP S/4HANA migration cockpit, role SAP_CA_DMC_MC_USER is required. To use the SAP S/4HANA
migration object modeler (transaction LTMOM), role SAP_CA_DMC_MC_DEVELOPER is required.

A role for each migration object is also required.

A test script is available for the migration process. For information about how to access the test script, see SAP Knowledge Base
Article 2577342 .

Procedure

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

1. You access the SAP S/4HANA migration cockpit by using transaction LTMC.

2. You create a migration project.

3. You open the migration objects that are relevant for your project.

 Note
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. The SAP S/4HANA migration cockpit uses the
selected Solution Scope for SAP S/4HANA to identify the migration objects that are required to transfer this data.

4. You assign one or more Microsoft Excel XML les to each migration object that is relevant for the transfer. You do this by
downloading the migration template for the migration object (a Microsoft Excel XML le), specifying the relevant data, and
uploading the le.

5. Once you have assigned a le for the migration object, you can transfer the data for that migration object to SAP
S/4HANA.

6. When the activity Transfer Data is complete, the data has been migrated to SAP S/4HANA.

7. You repeat this process for each migration object that is relevant for your project.

Creating Migration Projects

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6dd… 9/71
1/1/2021
and to monitor the status of the migration.

 Note
The SAP S/4HANA Migration Object Modeler is an application that can be used to adjust the migration objects that are used in
the SAP S/4HANA migration cockpit. If you plan to create your own migration objects in the SAP S/4HANA Migration Object
Modeler, or if you plan to adjust the migration objects delivered by SAP, then you can choose the Customer View. The
customer view allows you to easily adjust the structures and elds that are available in the corresponding template for the
migration object.

When you create a project, the system uses the default view On Premise - Enterprise Management Scope. This view is the
default view for the migration projects, and the active view for all migration objects in the project. For a migration object, you
can only download templates based on the active view. If required, you can change the active view for a speci c migration
object or change the default view for the migration project. You can change the default view for the migration project in the
Project Details screen.

Procedure
1. Open the SAP S/4HANA migration cockpit by using transaction LTMC.

2. To create a new migration project, choose Create.

 Note
The SAP S/4HANA migration cockpit uses les to transfer data to SAP S/4HANA. This is the default option for
transferring data from a source system to SAP S/4HANA. You use Microsoft Excel XML les provided by SAP to specify
the relevant data for each migration object.

3. Specify a name for the project.

4. Optional: You can specify a retention time for temporary data for the project.

When you use the SAP S/4HANA migration cockpit to transfer data to SAP S/4HANA using a le, temporary data is
created in the SAP system. This includes data from any uploaded les that is cached in the SAP system, as well as other
data used for the transfer. In the Data Retention Time eld, you can specify the length of time (in days) that this data is
kept in the system after the transfer of the le has nished. The data will be deleted from the SAP system when the data
retention time expires. If you leave this eld empty, the data will not be deleted from the system.

5. Optional: Optional: The system automatically generates a mass transfer ID that is used for your project. You can view this
mass transfer ID in the Mass Transfer ID eld.

If you want to manually transport settings from a quality system to a production system, the mass transfer ID must be
same in both systems (the mass transfer ID must also be unique in both systems). To ensure that both systems have the
same mass transfer ID, you can enter a mass transfer ID in the Mass Transfer ID eld. You can also generate a diﬀerent
mass transfer ID by choosing the button Generate New Mass Transfer ID. The system generates the next available mass
transfer ID. For more information, see Transferring a Project from One System to Another.

Additional Information About Migration Projects

When you open a migration project, the system displays the Migration Project Details screen. Here, you can view the name of the
project and the current status. The following status entries are possible for a migration project:

Not Started:

No migration objects are opened or copied to the project. All the migration objects in the project have the status Not
Started.

In Process:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 10/71
1/1/2021
There are migration objects opened and copied to the project. Not all the data for the migration objects has been
transferred. The migration objects in the project can have the status Not Started, In Process, or Finished.

Finished:

All the relevant data in the project has been transferred to the target system. The migration objects in project have either
the status Finished or Not Started.

In addition, you can view the following tabs:

Tab Description

Migration Objects On the Migration Objects tab, you can identify the migration objects that are relevant for your project.

Noti cations On this tab, you can view any messages reported for the diﬀerent activities of the migration process. You can lter
the activities according to priority (for example you can view all messages that have the priority Error), or
according to the activity type.

Settings On this tab, you can specify additional settings for the migration project.

Example: There are migration objects, for example customers, suppliers, or materials that have identi ers in the
source system that do not correspond to the identi ers in SAP S/4HANA. You can translate these source system
identi ers to the identi ers in SAP S/4HANA. For example if you have a text 'United States of America' in a country-
speci c eld, you can use the SAP S/4HANA migration cockpit to convert it to the format expected by SAP
S/4HANA, in this case 'US' (ISO code).

 Note
If you specify settings for an object, the settings will be applied to all the migration objects that use that object.
To view the migration objects that use a speci c setting, select the setting and choose Where Used. The system
displays all the migration objects that use the setting.

Transferring a Project from One System to Another

If required, you can transfer a migration project from one system to another. This allows you, for example, to transfer a migration
project from a quality system to a productive system. To do this, you create a project in the target system that has the same mass
transfer ID as the project you want to transfer. You then export the project from the rst system, and import it to the other system.

 Note
You can only transfer projects of the same type. For example, you can only transfer a migration project that uses les to
another migration project that uses les, not to a migration project that uses staging tables.

Prerequisites

A project must exist in the target system that has same mass transfer ID as the project you want to transfer.

1. Open the migration project that you want to transfer.

2. In the Migration Project Details screen, choose Export Content.

3. The system creates a zip le that contains the migration project. Save this le.

4. Open the migration cockpit in the other system, and open the migration project that has the same mass transfer ID as the
project you want to transfer.

5. In the Migration Project Details screen, choose Import Content.

6. Select the zip le that you saved in step 3.

Additional Considerations

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 11/71
1/1/2021
When transferring a project, there are considerations regarding the migration objects that are transferred. Note the following
examples:

The project that you want to transfer contains the migration objects A, B, and C. You want to transfer this project to
another system. In this system, you create a migration project that does not contain any migration objects. After you
transfer the project, the project in the target system will contain the migration objects A, B, and C from the project you
transferred.

The project that you want to transfer contains the migration objects A, B, and C. You want to transfer this project to
another system. In this system, you create a migration project that contains the migration objects A and B. After you
transfer the project, the project in the target system will contain migration objects A, B, and C from the project you
transferred (the system overwrites objects A and B).

The project that you want to transfer contains the migration objects A, B, and C. You want to transfer this project to
another system. In this system, you create a migration project that contains the migration objects A and D. It is not
possible to transfer this project to the target system as the project in the target system contains a migration object that is
not present in the project that you want to transfer.

Working with Migration Objects

A migration object describes how to migrate data for a speci c business object to SAP S/4HANA. It contains information about
the relevant source and target structures, as well as and the relationships between these structures. A migration object also
contains mapping information for the relevant elds, as well as any rules used to convert values that are migrated from source
elds to target elds. SAP provides prede ned migration objects that you can use to transfer your data.

The SAP S/4HANA migration cockpit uses the selected Solution Scope for SAP S/4HANA to identify the relevant migration
objects for your project. You can view these migration objects on the Migration Objects tab of a project.

 Note
To view a list of the migration objects delivered by SAP, see Migration Objects for SAP S/4HANA.

 Note
You can adjust migration objects if they do not meet your business requirements. It is also possible to create new objects. For
more information, see SAP Note 2481235 - SAP S/4HANA Migration Cockpit (on-premise) - restrictions and extensibility of
pre-delivered migration objects.

Procedure
1. On the Migration Objects tab of your migration project, identify the migration objects that are relevant for your project.

 Note
Detailed documentation is available for each migration object, and can support you with making this decision. To view
the documentation for a migration object, select the entry in the column Documentation.

2. Copy the relevant migration objects to your project..

To copy a migration object to your project, click the name of the migration object.

Additional Information
Filtering the List of Migration Objects

As the list of migration objects can be quite large, you can restrict the migration objects that are displayed.

On the Migration Objects tab of a project, you can use the View drop-down list to display migration objects by their status. By
default, the system displays all migration objects (standard view).

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 12/71
1/1/2021
The following status entries are possible for a migration object:

Not Started

The migration object is not opened or copied to the migration project.

In Process

The migration object has been copied to the migration project. The following are possible:

No les have been uploaded to the migration object.

Files have been uploaded to the migration object, but the data transfer has not started.

Files have been uploaded to the migration object, and the data transfer is in process.

Finished

The relevant data speci ed in les for the migration object has been transferred to the target system.

Dependent Migration Objects

Some migration objects may have a dependent migration object. In general, if a migration has a dependent object, then the
dependent object must be processed rst. After you have processed the dependent migration objects, you transfer the data
speci ed in the relevant les to SAP S/4HANA. When you have transferred all dependent objects, you process the migration
object that has the dependent objects, and transfer the data in the le to SAP S/4HANA. For a migration object, you can view
whether there is a dependent object in the column Dependent Migration Object on the Migration Objects tab of a project. Note
that the Dependent Migration Object column displays only one dependent migration object. Check the documentation of a
migration object to see whether it has multiple dependent migration objects.

 Note
If a migration object is valid for a certain period, then not only must any dependent objects be processed rst, they must also
t to the speci ed validity period.

Example

The migration object Routing has dependent migration objects, including Bill of Material (BOM) and Activity Type. The
migration object Routing is valid for a certain period; in the le for the migration object Routing, you specify the key date 10
January 2015. This means that the migration object is valid from this date onwards. You process the dependent migration
objects, including Bill of Material (BOM) and Activity Type. You ensure that the data you specify in the les for these objects is
only valid from 10 January 2015 onwards.

Support for Custom Fields and Logic App

For some supported migration objects, you can add custom elds using the Custom Fields and Logic application.

If the SAP S/4HANA migration cockpit detects such custom elds in one of the target function modules for a migration object, it
will automatically add them to the migration object so data can be entered for the elds in the Microsoft Excel les.

Assigning Files to Migration Objects

Context
You use Microsoft Excel XML les to specify the relevant data for each migration object. You must assign one or more les to each
migration object that is relevant for the transfer. SAP provides templates that you can use for each migration object.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 13/71
1/1/2021

Procedure
1. Open the relevant migration object.

2. Choose Download Template, and specify a storage location for the le.

3. Open the downloaded le using Microsoft Excel.

4. Specify the data that you want to transfer. For more information about specifying data in the Microsoft Excel XML le, see
Additional Information About Migration Templates.

5. In the migration project, choose Upload File. Upload the le that contains the data you want to transfer. You can now view
the uploaded le under Source Files.

 Note
Under Source Files, you can open the le, and check your entries. To open a le, select it and choose Open. If you open
a le that has already been transferred to SAP S/4HANA, you can view the records that have been transferred.

6. If you are satis ed that the le contains the data that you want to transfer, you can activate the le. To do this, select the
relevant row and choose Activate.

Additional Information About Migration Templates

The migration templates (Microsoft Excel XML Spreadsheet 2003 les) 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 nd information about the active view in
the Microsoft Excel XML le. In the le, navigate to File Info . You can nd the active view name under Properties Tags .

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

The Field List Sheet

The Field List sheet is one of the rst 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 elds in each sheet).

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

The name of the sheet, and whether it is mandatory or optional. Only mandatory sheets have the suﬃx 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 elds in a sheet.

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 14/71
1/1/2021
Information about the expected format of the individual elds, for example the data type and length.

 Note
In the eld list sheet, certain technical information about the elds 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 eld
belongs to. The column SAP Field is the technical name of the eld. 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 eld often
corresponds to the SAP ERP table name and eld name.

Working with Sheets

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

Mandatory sheets (orange)

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

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 eld names in SAP S/4HANA, as well as additional information such as the expected format (for
example the data type and length). Note that you must expand the row to view this additional information.

Some elds are mandatory, and some are optional. The wildcard character (ʻ*’) beside the name of a eld indicates that the eld is
mandatory.

 Note
Although an optional sheet may contain mandatory columns, if the sheet is not relevant for your project, there is no need to ll
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 eld (corresponds to row 8 - the eld 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 Diﬀerent Data Types

You can view the data type for a eld in row 8 (see Viewing Additional Information for Each Column above). Depending on the
eld, 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 elds with the data type text (usually those elds with Length: 80) to their correct SAP
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 15/71
1/1/2021
S/4HANA target values. You can do this value mapping in the SAP S/4HANA migration cockpit when you start the transfer
(in the step Convert Values).

Number

Enter numbers with decimals in the relevant country-speci c format, for example 12.34 (United States) or 12,34
(Germany). For elds 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 eld 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 your country-speci c format, for example 12/31/1998 (United States) or 31.12.1998 (Germany). Note that
Microsoft Excel automatically recognizes diﬀerent 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-speci c format followed by the time in the format HH:MM:SS, for example 12/31/1998
02:52:40 (United States) and 31.12.1998 02:52:40 (Germany). Separate the date and time with a blank space.

Copying Data to a Sheet

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

Using the Find and Replace Function

Do not use the Microsoft Excel function Find and Replace. If you change data by using this function, you may also unintentionally
change the eld 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 le. Other le 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, speci cally:

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.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 16/71
1/1/2021

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

Transferring Data to SAP S/4HANA

Prerequisites
You have assigned a le to the relevant migration object that contains the data that you want to transfer to SAP S/4HANA.

Context
In order to transfer data to SAP S/4HANA, the le for the migration object must be active. You can activate a le by selecting it and
choosing Activate. When you start the transfer process, the system will process all active les for the migration object. Files can
have the following status values:

Not Active

The initial status of an uploaded le. Files with this status will not be transferred.

Not Started

If you are satis ed that the le contains the data that you want to transfer, you can activate the le. When you select the
relevant le and choose the Activate button, the system changes the status of the le to Not Started. Note that you can
deactivate the le if required (for example if the le should not be transferred at this time). To do this choose the
Deactivate button. The system changes the status of the le to Not Active.

In Process

When you want to transfer a le to SAP S/4HANA, you choose the Start Transfer button, the system changes the status of
the le to In Process.

Finished

Once the step Execute Import is complete, you choose the Finish button. If all records have been transferred successfully,
the system changes the status of the le to Finished. If some records in the le have not been transferred successfully, the
system creates a delta le that contains all the records that were not transferred. The delta le has the status Not Active.

 Note
By default, when transferring a migration object, the migration cockpit only displays the rst 1000 instances for every
noti cation (errors, warnings, and success messages). If required, you can increase this limit. For more information, see SAP
Note 2817158 .

Procedure
1. Choose Start Transfer. The system will process all active les. The system starts the step Validate Data, and displays a
guided procedure that guides you through the transfer process.

2. Complete the steps in the guided procedure. When you have completed a step successfully, choose Next to navigate to the
next step. The guided procedure contains the following steps:

Validate Data

In the step Validate Data, the system checks the consistency of the les. You can view noti cations for the step
under Noti cations for Validations. If the system detects any inconsistent values. (for example if mandatory values
are missing), you must correct them before proceeding to the next step. During this step, the system checks

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 17/71
1/1/2021
whether the elds have the correct data type and length and also checks whether the mapping values for the object
are consistent. Note that this step can take some time.

Convert Values

Some data may need to be converted before it can be transferred to SAP S/4HANA. In this step, you can convert
the values (value mapping).

 Example
There are migration objects, for example customers, suppliers, or materials that have identi ers in the source
system that do not correspond to the identi ers in SAP S/4HANA. You can translate these source system
identi ers to the identi ers in SAP S/4HANA. For example if you have a text 'United States of America' in a
country-speci c eld, you can use the SAP S/4HANA migration cockpit to convert it to the format expected by
SAP S/4HANA, in this case 'US' (ISO code).

 Note
The migration objects used to transfer data to SAP S/4HANA use ISO codes for unit of measure (UoM) values.
This means that you need to map the unit of measure values that you have entered in the migration template or
in the staging table to a valid ISO code. During the Convert Values step, we recommend that you select a valid
ISO code by using the value help dialog for the S/4HANA Target Value eld. For more information, see SAP Note
2660271 and SAP Note 2665837 .

Simulate Import

In this step, the target system simulates the import. No data is posted to the target system. Note that this step is
optional. To skip this step, choose Skip ʻSimulate Import’ in the step Convert Values.

Execute Import

In this step, the data is posted to the target system. If required, you can return to the step Convert Values. To do
this, choose Back to 'Convert Values'.

3. Once the step Execute Import is complete, choose Finish. If all records in the le have been transferred successfully, the
system changes the status of the le to Finished. If not all records in the le have been transferred successfully, the system
creates a delta le that contains all the records that were not transferred. The delta le has the status Not Active. You can
download the delta le and then adjust the data in the le. You can then upload the delta le and start the transfer.

Transferring Multiple Files in Parallel – Improving Performance

If you have a lot of data to transfer, you can use multiple les. To save time, you can transfer the data for these les in parallel. On
the Migration Object Details screen, there is the eld Max. Data Transfer Jobs. Data transfer jobs are responsible for transferring
data to the target SAP S/4HANA system. Each active le is transferred to the SAP S/4HANA system by exactly one data transfer
job (the default number of data transfer jobs is 1.).

If you want to transfer more than one le at a time, you can increase the number of data transfer jobs. For example if you want to
transfer two les in parallel, change the value of the eld Max. Data Transfer Jobs to 2. Note that as only one job will transfer the
data for each le, specifying a value that is greater than the number of les will not improve performance. For example, if you want
to transfer 3 les in parallel, and specify 4 data transfer jobs, only 3 jobs will be scheduled.

 Note
If the data transfer is currently in process for a migration object, changing the number of data transfer jobs for that object has
no eﬀect. For your changes to take eﬀect, you can nish the transfer (button Finish) and choose the Start Transfer button
again. Alternatively, you can deactivate the le and activate it again.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 18/71
1/1/2021

Transferring Data to SAP S/4HANA Using Staging Tables

Context
The SAP S/4HANA migration cockpit can automatically create staging tables for each migration object that is relevant for your
project. You can ll the staging tables with data either manually or by using your preferred tools (for example SAP Agile Data
Preparation).

There are the following options for staging tables:

If you use the database connection Default, you can use staging tables that are located in the local ABAP schema of the
SAP S/4HANA system.

You can specify a database connection to an SAP HANA database system, and use the staging tables there.

Prerequisites

General

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

Default Database Connection

If you want to create the staging tables in the local ABAP schema of the SAP S/4HANA system, you can restrict access to
these tables by using the authorization object S_TABU_NAM.

User-De ned Database Connection

If you want to use staging tables that are located in an SAP HANA schema that is not the local ABAP schema of your SAP
S/4HANA system, you need to create a database connection between the SAP S/4HANA system and the relevant SAP
HANA database system. In the SAP S/4HANA system, you then need to manually add the database connection to table
DMC_C_WL_DBCO_OP using transaction SM30. This allows you to use the connection for the migration. This table also
ensures that only relevant connections are displayed in the SAP S/4HANA migration cockpit.

Roles

To transfer data using the SAP S/4HANA migration cockpit, role SAP_CA_DMC_MC_USER is required. To use the SAP
S/4HANA migration object modeler (transaction LTMOM), role SAP_CA_DMC_MC_DEVELOPER is required.

The corresponding role for each migration object is also required.

Procedure

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

1. You access the SAP S/4HANA migration cockpit by using transaction LTMC.

2. You create a migration project to transfer data using staging tables.

When you create a migration project, you specify a database connection to the source system database.

3. You open the migration objects that are relevant for your project.

When you open a migration object, staging tables are automatically created for the migration objects. For each source
structure of a migration object a separate staging table is created.

4. You add the data that is relevant for the migration object to the staging tables (you can ll the staging tables with data
either manually or using your preferred tools).

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 19/71
1/1/2021
5. Once you have added all the relevant data to the staging tables for the migration object, you can transfer the data for that
migration object to SAP S/4HANA.

6. When the activity Transfer Data is complete, the data has been migrated to SAP S/4HANA.

7. You repeat this process for each migration object that is relevant for your project.

Creating Migration Projects

 Note
When you create a project, the system uses the default view On Premise - Enterprise Management Scope. This view is the
default view for the migration projects, and the active view for all migration objects in the project. For a migration object, the
staging tables are based on the active view. If required, you can change the active view for a speci c migration object or change
the default view for the migration project. You can change the default view for the migration project on the Project Details
screen.

You can only change the active view for a migration object if no data exists in the associated staging tables for the migration
object. You can only change the default view for a migration project if no data exists in the associated staging tables for any
migration objects in the project.

The SAP S/4HANA Migration Object Modeler is an application that can be used to adjust the migration objects that are used in
the SAP S/4HANA migration cockpit. If you plan to create your own migration objects in the SAP S/4HANA Migration Object
Modeler, or if you plan to adjust the migration objects delivered by SAP, then you can choose the Customer View.

Procedure
1. Open the SAP S/4HANA migration cockpit by using transaction LTMC.

2. To create a new migration project, choose Create.

3. Specify a name for the project.

4. Choose Transfer Data from Staging Tables.

5. If you want to use staging tables that are located in the local ABAP schema of the SAP S/4HANA system, choose the option
Default in the Database Connection eld. If you want to use staging tables that are located in an SAP HANA schema that is
not the local ABAP schema of your SAP S/4HANA system, enter a valid database connection to the staging system in the
Database Connection eld or choose one from the search help list.

6. Optional: The system automatically generates a mass transfer ID that is used for your project. You can view this mass
transfer ID in the Mass Transfer ID eld.

 Note
You can only delete a migration project if all the staging tables in the project are empty. If you delete a migration project,
all the staging tables in the project are also deleted.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 20/71
1/1/2021

Additional Information About Migration Projects

Not Started:

No migration objects are opened or copied to the project. All the migration objects in the project have the status Not
Started.

In Process:

There are migration objects opened and copied to the project. Not all the data for the migration objects has been
transferred. The migration objects in the project can have the status Not Started, In Process, or Finished.

Finished:

All the relevant data in the project has been transferred to the target system. The migration objects in project have either
the status Finished or Not Started.

In addition, you can view the following tabs:

Tab Description

Migration Objects On the Migration Objects tab, you can identify the migration objects that are relevant for your project.

Settings On this tab, you can specify additional settings for the migration project.

Transferring a Project from One System to Another

 Note
As the staging table name for the same migration object and structure is diﬀerent in the development, quality, and productive
systems, a mapping table is provided in the same schema where the staging tables are generated. This table
(/1LT/DS_MAPPING) stores mapping information about the migration object, the source structure and the staging table name.
You can use this table to determine the staging table names after you copy a project from a quality system to a production
system, and use these names in your scripts or applications that populate the staging tables with data.

 Note
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 21/71
1/1/2021
You can only transfer projects of the same type. For example, you can only transfer a migration project that uses les to
another migration project that uses les, not to a migration project that uses staging tables.

Prerequisites

A project must exist in the target system that has same mass transfer ID as the project you want to transfer.

1. Open the migration project that you want to transfer.

2. In the Migration Project Details screen, choose Export Content.

3. The system creates a zip le that contains the migration project. Save this le.

4. Open the migration cockpit in the other system, and open the migration project that has the same mass transfer ID as the
project you want to transfer.

5. In the Migration Project Details screen, choose Import Content.

6. Select the zip le that you saved in step 3.

Additional Considerations

When transferring a project, there are considerations regarding the migration objects that are transferred. Note the following
examples:

The project that you want to transfer contains the migration objects A, B, and C. You want to transfer this project to
another system. In this system, you create a migration project that contains the migration objects A and B. After you
transfer the project, the project in the target system will contain migration objects A, B, and C from the project you
transferred (the system overwrites objects A and B).

The project that you want to transfer contains the migration objects A, B, and C. You want to transfer this project to
another system. In this system, you create a migration project that contains the migration objects A and D. It is not
possible to transfer this project to the target system as the project in the target system contains a migration object that is
not present in the project that you want to transfer.

Working with Migration Objects

 Note
To view a list of the migration objects delivered by SAP, see Migration Objects for SAP S/4HANA.

Procedure
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 22/71
1/1/2021
1. On the Migration Objects tab of your migration project, identify the migration objects that are relevant for your project.

2. Copy the relevant migration objects to your project.

To copy a migration object to your project, click the name of the migration object.

Additional Information
Filtering the List of Migration Objects

As the list of migration objects can be quite large, you can restrict the migration objects that are displayed.

On the Migration Objects tab of a project, you can use the View drop-down list to display migration objects by their status. By
default, the system displays all migration objects (standard view).

The following status entries are possible for a migration object:

Not Started

The migration object is not opened or copied to the migration project.

In Process

The migration object has been copied to the migration project.

Finished

The relevant data (speci ed in staging tables) for the migration object has been transferred to the target system.

Dependent Migration Objects

Some migration objects may have a dependent migration object. In general, if a migration object has a dependent object, then the
dependent object must be processed rst. When you have transferred all dependent objects, you process the migration object
that has the dependent objects, and transfer the data to SAP S/4HANA. For a migration object, you can view whether there is a
dependent object in the column Dependent Migration Object on the Migration Objects tab of a project. Note that the Dependent
Migration Object column displays only one dependent migration object. Check the documentation of a migration object to see
whether it has multiple dependent migration objects.

 Note
If a migration object is valid for a certain period, then not only must any dependent objects be processed rst, they must also
t to the speci ed validity period.

Support for Custom Fields and Logic App

For some supported migration objects, you can add custom elds using the Custom Fields and Logic application.

Working with Staging Tables

Context
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 23/71
1/1/2021
When you open a migration object for the rst time, the system automatically creates database tables in the source staging
system for the migration object. These database tables are called staging tables. For each migration object, the system creates
one or more staging tables. After the staging tables are created, they are listed on the Migration Object Details screen. The
staging tables have the naming convention /1LT/DS<system ID><numeric identifier>, for example
/1LT/DSQKX000928

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

Key elds

Mandatory elds

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

All other elds can contain null values.

Procedure

1. On the Migration Object Details screen, click the name of a staging table to open it and check the structure of the table.

 Note
The key elds and mandatory elds of the staging table are marked with the wildcard character (*).

2. Identify the relevant staging tables by their names in the schema speci ed in the database connection.

3. Fill the staging tables with data either manually or using your preferred tools. Make sure the key elds and mandatory
elds contain valid data.

4. When a staging table contains data, you can view the data records on the Staging Table Details screen and use the
following functions:

Filter the list of data records

Reset the status of a data record

Delete data records

Filtering the List of Data Records

On the Staging Table Details screen, you can view the data records in the table. By default, only the data records with errors are
displayed. You can use the Processing Status drop-down list to display data records of another status.

The following status entries are possible for a data record:

Processed

The data record has been transferred successfully to the target system.

Unprocessed

The data record is not transferred yet.

Error

Transfer of the data record has failed.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 24/71
1/1/2021

Resetting the Status of a Data Record

The data records that are already transferred (status Processed) cannot be transferred again. If you have updated these data
records and want to transfer them again, you must rst reset the status of the data records to Unprocessed.

For data records with status Error, if you have corrected the data records and want to transfer them again, you must also reset the
status of the data records Unprocessed.

To reset the status of a data record, select the corresponding entry and choose Reset Status on the Staging Table Details screen.

Deleting Data Records

You can delete data records directly from the Staging Table Details screen. However, you cannot edit or add data records here.

To delete certain data records, select the data records and choose Delete Selected Records. To delete all data records in the table,
choose Delete All Records. Note if you choose this option, all records will be deleted, regardless of the status (processed, error,
and unprocessed).

Support for Custom Fields and Logic App

For some supported migration objects, you can add custom elds using the Custom Fields and Logic application.

Synchronizing Staging Tables with Migration Objects

In the following situations, structures of the staging tables might need to be adjusted so that they re ect the latest version of a
migration object.

The default view of your migration project has changed.

The active view of the migration object has changed.

The migration object content has changed.

The staging tables that need to be changed have the status Synchronization Required. You must synchronize the staging tables
with changed view or changed migration object content before you can use them for data transfer.

To synchronize all the staging tables of a migration object, choose Start Synchronization on the Migration Object Details screen.

To synchronize a single staging table, choose Start Synchronization on the Staging Table Details screen of the table.

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

Key elds

Mandatory elds

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

All other elds can contain null values.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 25/71
1/1/2021

Transferring Data to SAP S/4HANA

Prerequisites
You have lled the staging tables of the relevant migration objects with the data that you want to transfer to the SAP S/4HANA
system.

Context
In order to transfer data to SAP S/4HANA , the relevant migration object must be active.

Procedure
1. For a migration object, you can start the transfer process for the data in all the staging tables. To do this, choose Start
Transfer. Note that when you choose Start Transfer, the system locks the staging tables.

2. Compete the steps in the guided procedure. When you have completed a step successfully, choose Next to navigate to the
next step. The guided procedure contains the following steps:

Validate Data

In the step Validate Data, the system checks the consistency of the les. During this step, the system checks
whether the elds have the correct data type and length and also checks whether the mapping values for the object
are consistent. Note that this step can take some time.

 Note
If the system detects any inconsistent values in the step Validate Data (for example if mandatory values are
missing), you must correct these values:

a. Go back to the Migration Object Details screen and choose Reset Data Transfer.

b. Correct the values in the staging tables.

c. After you have corrected the values, choose Start Transfer to start the data transfer again.

Convert Values

Some data may need to be converted before it can be transferred to SAP S/4HANA. In this step, you can convert
the values (value mapping).

Simulate Import

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 26/71
1/1/2021
In this step, the target system validates the data. No data is posted to the target system. To skip this step, choose
Skip 'Simulate Import' in the step Convert Values.

Execute Import

In this step, the data is posted to the target system.

3. Choose Finish to complete the data transfer. Note that the system unlocks the staging tables after you choose the Finish
button.

4. After a data transfer has completed, you can add new data to the staging tables.

 Note
If you want to add new data to the staging tables during the guided activity, you can go back to the Migration Object
Details screen, choose Restart Transfer to unlock the staging tables, and then add the new data. In this case, you have
to start from the step Validate Data again (by choosing Start Transfer again).

Improving the Performance of the Transfer

On the Migration Object Details screen, there is the eld Max. Data Transfer Jobs. Data transfer jobs are responsible for
transferring the data in the staging tables to the target SAP S/4HANA system. The default number of data transfer jobs is 1. You
should consider increasing the number of data transfer jobs in the following situations:

You have a lot of data to transfer.

The migration object is a complex object with multiple staging tables.

Using one job results in an unacceptable data transfer time.

 Note
In order to transfer data to the target SAP S/4HANA system, the system divides the content of the staging tables into portions,
which are transferred by the data transfer jobs. Depending on the amount of data across all the staging tables that belong to
the migration object, increasing the number of data transfer jobs may not have any eﬀect. The migration cockpit ensures that
the optimal number of jobs (between 1 and the maximum number of data transfer jobs) are used to transfer the portions.

 Note
For the initial phase of the Validation step, only one data transfer job will be used. Once this initial phase is complete, the
system will use the number of jobs speci ed in the Max. Data Transfer Jobs eld for the remainder of the Validation step, and
for the remaining steps.

 Note
If the system is transferring data for a migration object, changing the number of data transfer jobs has no eﬀect. For your
changes to take eﬀect, choose the Restart Transfer button Alternatively, you can nish the transfer (button Finish) and choose
the Start Transfer button again.

SAP S/4HANA Migration Object Modeler

The SAP S/4HANA migration object modeler is an application that can be used to adjust the migration objects that are used in the
SAP S/4HANA migration cockpit. You can access the SAP S/4HANA migration object modeler by using transaction LTMOM.

 Note

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 27/71
1/1/2021
The functions and features oﬀered by the SAP S/4HANA migration object modeler depend on the migration approach of your
SAP S/4HANA Migration Cockpit project. Detailed documentation for the SAP S/4HANA migration object modeler can be
accessed directly from transaction LTMOM.

Read Access Logging Con gurations in Migration Cockpit

You can use the Read Access Logging (RAL) report to con gure which read-access information to log in the system and under
which conditions.

SAP delivers sample con gurations for applications.

In the scenarios Transfer Data Using Files and Transfer Data Using Staging Tables of Migration Cockpit (CA-LT-MC), users can
read the uploaded data records. In order to identify the users who preview data, RAL logs the name of the le or staging table
(depending on the scenario) containing the data, together with the name of the user who opened this le.

In the following con gurations, elds are logged in combination with additional elds, in the following business contexts:

Channel Con guration Fields Logged Business

Description Context

Web CA / CA-LT / Migration of

Name [Migration Object Name] (DMC_WDA_MIGOBJ_HEADER00-
Dynpro RAL Template customer
DMC_WDA.FPM_FORM_UIBB_GL2_DMC_WDA_MIGOBJ_HEADER_00_-
for Migration data to SAP
V_FORM-FGL2_005056AC18A01ED4B5F40A2774026FFE-TEXT)
Cockpit S/4HANA.
Migration Project (DMC_WDA_MIGOBJ_HEADER00-
DMC_WDA.FPM_FORM_UIBB_GL2_DMC_WDA_MIGOBJ_HEADER_00_-
V_FORM-FGL2_005056AC18A01ED4B5F418B2078CD058-TEXT)

Name [File Name] (DMC_WDA_FILE_FORM00-

DMC_WDA.FPM_FORM_UIBB_GL2_DMC_WDA_FILE_FORM_00_-V_FORM-
FGL2_005056AC1D581EE58FEABF8B1CE49A06-VALUE)

File Name (DMC_WDA_MIGOBJ_DOWNLOAD_RAL00-

DMC_WDA.FPM_FORM_UIBB_GL2_DMC_WDA_MIGOBJ_DOWNLOAD_RAL_00_-
V_FORM-FGL2_40F2E9AFBE791EE8A6F7121C3734B6EF-TEXT)

Staging Table (DMC_WDA_STAGING_TABLE_FORM00-

DMC_WDA.FPM_FORM_UIBB_GL2_DMC_WDA_STAGING_TABLE_FORM_00_-
V_FORM-FGL2_40F2E9AFC5001EE795FE3BC1F7CA6E98-TEXT)

Migrate Your Data - Migration Cockpit

With this app, you can migrate business data to SAP S/4HANA. You can migrate data directly from an ERP source system, or you
can use staging tables to migrate data.

Key Features
You can use this app to:

Create migration projects to migrate data, and to monitor the status of the migration.

Select the migration objects that are relevant for your migration scenario (the app uses migration objects to identify and
transfer the relevant data).

Process any mapping tasks for the migration objects.

Simulate the migration before migrating your data to SAP S/4HANA, and monitor the status of the simulation process.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 28/71
1/1/2021
Migrate your data to SAP S/4HANA, and monitor the status of the migration.

Migrate Data Using Staging Tables

The SAP S/4HANA migration cockpit creates staging tables for the migration objects that are relevant for your project and
migrates data from these staging tables to the target SAP S/4HANA system.

Template les are provided for every migration object. You can use these template les to ll the staging tables with data.
Alternatively, you can ll the staging tables by using your preferred tools (for example SAP Data Services).

Where are the staging tables located?

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

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

 Note
Important information regarding the processing of personal data

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 justi ed purpose.

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

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

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

The Migration Process

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 29/71
1/1/2021

A more detailed description of the process is outlined below:

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

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

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

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

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

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

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

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

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

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

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

Creating Migation Projects

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

Typically, you rst create a project in a test system which is a copy of the SAP S/4HANA production system. The more the data in
the test system resembles the data in the production system, the more precise your test will be.

For each test transfer, you create a new migration project in the test system that includes any corrections or re nements identi ed
in the previous test. When you are nally ready to transfer your data to the SAP S/4HANA production system, you create a project
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 30/71
1/1/2021
in the production system.

Procedure
1. In the SAP S/4HANA system, access the SAP S/4HANA migration cockpit by choosing the Migrate Your Data - Migration
Cockpit app in the 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 rst 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 les to ll the staging tables with data, choose the option Local SAP S/4HANA Database in the Database
Connection eld. The system will generate the staging tables in the internal schema of the SAP S/4HANA system. Note
that you could also ll these staging tables with data by using your preferred tools if required. If you want to ll the staging
table with data by using your preferred tools into a diﬀerent schema in a remote HANA database, select the option Remote
SAP HANA Database and enter a valid database connection to the staging system by choosing one from the search help
list. The system will generate the staging tables there. You need to create a database connection in transaction DBCO, and
manually add it to table DMC_C_WL_DBCO_OP in the SAP S/4HANA system. Note that you can also use les to ll 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.

Using a Project in a Diﬀerent Client

You can use the SAP S/4HANA migration object modeler (transaction LTMOM) to change the settings for a project so that it can be
used in a diﬀerent client. To do this, open the relevant project and choose GoTo Use Project in Diﬀerent Client .

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

The Migration Project Screen

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

For each migration object, these steps are:

1. Uploading a template le for a migration object (if using template les to ll the staging tables with data).

2. Preparing the staging tables.

3. Processing any open mapping tasks.

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

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

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

The Migration Project screen contains the following columns:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 31/71
1/1/2021
Migration Object

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

Data

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

Mapping Tasks

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

Simulation

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

Migration

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

Migration Progress

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

Percentage of instances migrated successfully

Percentage of instances with errors

Percentage of instances not yet started

Action

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

Additional Information

Monitoring

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

Settings

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

Mapping Tasks

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 32/71
1/1/2021
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 nished 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 Oﬀ, then the project and all associated data will be kept in the system
inde nitely. If required, you can change the retention time for nished projects. To do this, open the relevant project and choose
the Settings button. You can nd the settings for retention time on the Technical Information tab.

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

Migration Project Name

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

Migration Approach

Default View

The view determines the visible elds for a migration object. There is a standard scope for SAP S/4HANA. You can also
de ne a custom scope in transaction LTMOM.

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 diﬀerent 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

Support Information

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 33/71
1/1/2021
You can also view general technical information about the project such as the object ID. If you need to contact SAP
for support, this information might be required.

Job Management
On the Job Management screen, you can adjust the maximum number of background jobs that are used for your project. The
default number of background jobs for a project is 15. If required, you can also adjust the number of background jobs for speci c
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 eﬀect on that activity.

Example 1

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

Example 2

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

Example 3

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

The Migration Object Screen

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

Documentation

You can view detailed information about the migration object.

Views

You can view the active view for the migration object.

The view determines the visible elds for a migration object. There is a standard scope for SAP S/4HANA. There is also an
adjusted scope that uses your business con guration settings to reduce the number of visible elds.

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.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 34/71
1/1/2021
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 elds exist

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

Downloading Template Files

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

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

2. The system creates a zip le that contains the template les.

3. Save the zip le locally and open the les using Microsoft Excel.

Additional Information About Migration Templates

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 35/71
1/1/2021

The Field List Sheet

The Field List sheet is one of the rst 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 elds in each sheet).

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

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

The group name for the elds in a sheet.

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

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

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

Working with Sheets

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

Mandatory sheets (orange)

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

Optional sheets (blue)

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

Viewing Additional Information for Each Column

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 36/71
1/1/2021
In row 8, you can view the eld names in SAP S/4HANA, as well as additional information such as the expected format (for
example the data type and length). Note that you must expand the row to view this additional information.

Some elds are mandatory, and some are optional. The wildcard character (ʻ*’) beside the name of a eld indicates that the eld is
mandatory.

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

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 Diﬀerent Data Types

You can view the data type for a eld in row 8 (see Viewing Additional Information for Each Column above). Depending on the
eld, 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 elds with the data type text (usually those elds with Length: 80) to their correct SAP
S/4HANA target values. You can do this value mapping in the SAP S/4HANA migration cockpit when you start the transfer
(in the step Convert Values).

Number

Date

Time

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

Date-Time

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 37/71
1/1/2021
Enter the date in your country-speci c 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

Using the Find and Replace Function

Saving the Migration Template

Ensure that you only save the migration template as a Microsoft Excel XML Spreadsheet 2003 le. Other le 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, speci cally:

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 modi ed migration templates are not supported by
the SAP S/4HANA migration cockpit.

Transferring Data to Staging Tables

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

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

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

Key elds

Mandatory elds

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

All other elds can contain null values.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 38/71
1/1/2021
There are the following options for populating the staging tables with data:

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

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

Transferring Data from Template Files to Staging Tables

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

 Note
The size limit for each le is 100 MB. You can upload multiple XML les at once by using a zip le. Note that the combined size
of all the XML les you want to add to the zip le must not exceed 160MB. The maximum permitted size of the zip le 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 les and view the status of the
validation and transfer process. To upload a le, you can either use the Upload button or use the drag and drop function.

3. The system uploads the le 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 le. 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 le you can view the relevant messages. To resolve any validation issues, you
must delete the le and adjust the data in your le accordingly. You can then upload the le and the system will start the
validation process again.

6. Once the le has been validated successfully, the system automatically starts transferring the data in the le to the staging
tables that were generated for that migration object. Once all the data in the le 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
les.

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 nd detailed information about the elds 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:

Reset Table Settings

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 39/71
1/1/2021
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 eld /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 re ect 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
re ect the latest version of the migration object provided by SAP.

Files

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

The following feature is also available:

Download Metadata

You can download metadata for all tables of a migration object. The system creates a .txt le that contains the structure of
the tables. For each eld, 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 le 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 eld as the instance to be inserted. If duplicate key errors occur, the status
of the le will change to Transfer of Data to Staging Tables Failed. You can view the relevant messages for the le by choosing
Show Messages.

There are the following options for handling duplicate key errors:

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

You can proceed with transferring the data in the le to the staging tables. To do this, you select the relevant le 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 les that contain duplicate instances.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 40/71
1/1/2021
Replace Duplicates with Instances from File

The system will transfer all data from the le 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 le. Note that if a duplicate instance has already been successfully migrated, then it will not
be deleted from the staging tables.

Example

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

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

EN 2344444 563222666

You adjust the le (or prepare a new le) so that it contains a value for the Region eld. You then upload the le. For this le, 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 le that contains a value for the Region eld.

Transferring Data to Staging Tables Using Your Preferred Tools

If the staging tables are located in a remote SAP HANA schema, you can populate the staging tables with data by using your
preferred tools (for example SAP Data Services). In this case, information such as the technical names of the staging tables as well
as the data types and lengths of the elds 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 nd detailed information about the elds in the
staging table.

You can also download metadata for all tables of a migration object. The system creates a .txt le that contains the structure of the
tables. For each eld, you can view information such as the length and data type as de ned 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
les.

The Migration Object Tables screen contains the following tabs:

Tables

On the Tables tab, the following options are possible:

Reset Table Settings

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 41/71
1/1/2021
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.

Delete All Records

Adjust Structure

Files

The following feature is also available:

Download Metadata

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 elds that have a de ned relationship and that represent a business object
instance. For example, a migration object instance for the migration object Bank comprises several elds such as:

Bank Country Key

Bank Key

Bank Branch

Bank Group

Name of Bank
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 42/71
1/1/2021

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 Instance 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 elds for the instance.

In addition, you can view the following columns:

Additional Fields

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

Source

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

Action

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

None

Simulated

Migrated

Status

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

Initial (Only relevant for the action None)

Success

Error

The following options are also available:

Deleting Migration Object Instances

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

View Messages for Migration Object Instances

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

Preparing the Staging Tables

Prerequisites

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 43/71
1/1/2021
For a migration object, you have transferred the data to the staging tables.

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

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

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

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

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

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

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

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 Con rmed) as
well as any con rmed 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 Con rmed or To be Con rmed.

Type

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

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 con rming these target values. You can then set the status
of the task to Con rmed. Once all mapping tasks for a migration object have the status Con rmed, you can proceed with the
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 44/71
1/1/2021
simulation or migration process for the migration object.

 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 con rm 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 Con rmed. 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 Con rmed or To be Con rmed.

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

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.

Description

Click the Document link to view detailed information about the task.

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

Source Value

The value of the relevant eld in the source system.

Target Value

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

Status

The status of the speci c values (either Con rmed or To be Con rmed).

Action

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

For each value that has the status To be Con rmed, you need to either enter a value in the Target Value eld 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 Con rm button. Once all the values have the status Con rmed, the system changes the status of
the task to Con rmed on the Mapping Tasks screen.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 45/71
1/1/2021

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

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

Source Company Code Target Company Code

0001 0001

Z001 ZZ99

Fixed Value Tasks

For Fixed Value tasks, you specify default values for target elds. On the Mapping Tasks screen, select the relevant xed value
task that has the status To be Con rmed. 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 con rmed for the task. You can view the following information:

Customizing

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

Status

The status of the speci c values (either Con rmed or To be Con rmed).

Action

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

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

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

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

Control Parameter Tasks

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

Example
When using the migration object Material Inspection Setup to migrate data to SAP S/4HANA, you need to process the control
parameter mapping task Take default values for inspection type to decide whether you want to use values for inspection types

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 46/71
1/1/2021
from the source le 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 les 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 les 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 le that contains the template les.

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

A template le 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 elds.

Data

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

Uploading Mapping Values

Prerequisites
You have downloaded a template le for a mapping task and lled the le 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 le by using the Upload button or the drag and drop function. You can upload single les as
well as zip les.

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 Con rming Values

To set the status of the mapping values to Con rmed, choose the option Con rm Values Automatically. Otherwise,
choose Do Not Con rm Values Automatically.

Options for Loading Values

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 47/71
1/1/2021
values from the le.

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 system. Note that no data is written to the target SAP S/4HANA system during the simulation
process, but you can view all the messages that would occur during an actual data transfer (for example information about a cost
center that does not exist).

 Note
When you simulate the migration for rst 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.

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

Context
Once you have prepared the staging tables and processed all open tasks for a migration object, you can transfer data to the target
SAP S/4HANA system. Note that we recommend that you rst 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.

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.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 48/71
1/1/2021
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 le to correct the errors. A correction le contains all the migration
object instances in the staging tables that have the status Error. You can adjust the correction le to resolve the errors, upload the
le, 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 le
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 les that can be used to
create the correction le. Select the relevant les 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 le.

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

Prerequisites
You have created a correction le to resolve errors that occurred during the migration process. You have adjusted the values in the
le 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 le. If you do not delete the instances with errors, the system will identify duplicate
key errors when uploading the correction le and display options for handling the duplicate key errors. If you can 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 le.

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, upload the correction le and view the status of
the validation and transfer process. To upload a le, you can either use the Upload button or use the drag and drop
function.

3. The system uploads the le 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 le. 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 le has been validated successfully, the system automatically starts transferring the data in the le to the staging
tables. Once all the data in the le has been transferred to the staging tables, the system displays the information Data

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 49/71
1/1/2021
Successfully Transferred to Staging Tables. You can also view information such as the number of transferred migration
object instances.

Migrate Data Directly from SAP System

Context

Overview

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

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

SAP S/4HANA systems are currently not supported as source systems.

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

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

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

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

If you are using the migration scenario SAP EWM to Decentralized EWM, the lowest supported EWM release is EWM 5.1
(SAP NetWeaver 7.0).

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

Prerequisites

General

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

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

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

Roles and Authorizations

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 50/71
1/1/2021
An RFC connection between the SAP S/4HANA system and the SAP ERP source system exists. The RFC user in SAP ERP
source system must have the role SAP_DMIS_OBT_REMOTE. For security reasons, we recommend that this RFC user is a
user of type Communication.

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

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

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

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

OBJTYPE = 'CLAS'

OBJNAME = *

P_GROUP = *

ACTVT = 01, 02, 06

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

01: Create (valid for all object types)

02: Change (valid for all object types)

06: Delete (valid for all object types)

Other

Program CNV_PE_MC_LOAD_OBJECTS has been executed in the target SAP S/4HANA system. This program loads the
migration objects delivered by SAP from client 000 to the client you are working in. Note that if you update your SAP
S/4HANA to a new release, or install a new feature package or support package in the SAP S/4HANA system, then you
need to execute this program again. For more information, see SAP Note 2870546

The Migration Process

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

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

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

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

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

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 51/71
1/1/2021
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 elds).

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

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

Creating Migration Projects

Usually, several test data migrations are required before you transfer data to the SAP S/4HANA production system. For each new
test transfer you create a new migration project in the test system that includes any corrections or re nements identi ed in the
previous test. If you have adjusted migration objects using the SAP S/4HANA migration object modeler (transaction LTMOM), the
changes need to be done again for any subsequent projects.

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

When you are nally ready to transfer your data to the SAP S/4HANA production system, you create a project in the production
system. The migration is client-speci c, so you create your project in the relevant client of the target SAP S/4HANA system.

To create a migration project, proceed as follows:

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

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

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

Name

The name of the project.

Scenario

The migration scenario. The following migration scenarios are available:

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

SAP ERP to SAP S/4HANA

SAP EWM to Decentralized EWM

SAP CRM to SAP S/4HANA for Customer Management

 Note

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 52/71
1/1/2021
Diﬀerent migration objects are relevant for diﬀerent scenarios. The system displays the relevant migration
objects based on the selected scenario.

Connection to Source System

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

Development Package

Specify a development package. If you are unsure about which option to use, we recommend contacting your
system administrator.

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

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 prede ned for each scenario. For example, the scenario SAP ERP to SAP S/4HANA uses
company codes to select data from the source system. Only data that is relevant for the speci ed organizational units
will be selected from the source system..

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

6. Choose the button Step 3.

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.

The Migration Project Screen

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

For each migration object, these steps are:

1. Selecting the data from the source system

2. Processing any open mapping tasks

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 53/71
1/1/2021
3. Simulating the migration to the target SAP S/4HANA system (optional)

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

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

The Migration Project screen contains the following columns:

Migration Object

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

Data

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

Mapping Tasks

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

Simulation

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

Migration

Migration Progress

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

Settings

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 54/71
1/1/2021
change the number of jobs that are used for the project. For more information, see Project Settings.

Mapping Tasks

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

Finishing a Project

When you 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 Oﬀ, then the project and all associated data will be kept in
the system inde nitely. If required, you can change the retention time for nished projects. To do this, open the relevant project
and choose the Settings button. You can nd the settings for retention time on the Technical Information tab.

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

The migration project name.

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

The migration scenario.

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

In addition, you can view the following sections:

Select Data

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

Migration Objects

History

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

Technical Information

Under Technical Information, you can view the following information:

Data Retention Period

The retention period is the length of time (in days) that the project and all associated data is kept in the system
after you have set the status of the project to Finished. If required, you can change the retention time for nished
projects.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 55/71
1/1/2021
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.

Example 1

Example 2

Example 3

Additional Information About Migration Objects

Description

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 56/71
1/1/2021
Data

You can view the migration object instances that have been selected from the source system for the migration object.

 Note
If required, you can simulate the migration for speci c migration object instances and migrate data for speci c
migration object instances. You can do this on the Migration Object screen by selecting the relevant migration object
instances and choosing the button Select for Simulation or Select for Migration.

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.

Selecting Data from the Source System

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

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

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

Monitoring the Status of the Selection Process

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

Viewing the Selected Data

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

Bank Country Key

Bank Key

Bank Branch

Bank Group

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 57/71
1/1/2021
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 FI-GL Bank Key migration object. On the Migration Project screen, you
choose Actions and then Select. The system updates the Data column to indicate that four instances have been successfully
selected. You click the number in the Data column, and the system displays the Migration Object Instances screen where you can
view the following data:

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

IN BANK_1 A1 YB Bank International

IN BANK_2 A2 YB Bank International

IN BANK_3 A1 YB Bank International

IN BANK_4 A1 YB Bank International

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

The Migration Object Instances Screen

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

In addition, you can view the following columns:

Additional Fields

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 58/71
1/1/2021
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 Speci c Migration Object Instances

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

Migrate Speci c Migration Object Instances

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

Exclude Migration Object Instances

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

Mass Processing of Migration Object Instances

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

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

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

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 59/71
1/1/2021

Mapping Tasks Screen

Mapping Tasks

The name of the task.

Status

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

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

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 con rming these target values. You can then set the
status of the task to Con rmed. Once all mapping tasks for a migration object have the status Con rmed, you can proceed with
the simulation or migration process for the migration object.

Value Mapping Tasks

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 Con rmed or To be Con rmed.

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

Used In

Description

Click the Document link to view detailed information about the task.

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

Source Value

The value of the relevant eld in the source system.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 60/71
1/1/2021
Target Value

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

Status

The status of the speci c values (either Con rmed or To be Con rmed).

Action

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

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

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

Fixed Value Tasks

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 con rmed for the task. You can view the following information:

Customizing

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

Status

The status of the speci c values (either Con rmed or To be Con rmed).

Action

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 61/71
1/1/2021

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

Downloading Template Files for Mapping Tasks

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 le that contains the template les.

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

A template le 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 elds.

Data

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

Uploading Mapping Values

Prerequisites
You have downloaded a template le for a mapping task and lled the le 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 le by using the Upload button or the drag and drop function. You can upload single les as
well as zip les.

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 Con rming Values

To set the status of the mapping values to Con rmed, choose the option Con rm Values Automatically. Otherwise,
choose Do Not Con rm Values Automatically.
https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 62/71
1/1/2021
Options for Loading Values

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

Simulating the Migration

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

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

All Instances

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

All Instances with Errors

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

Random 10%

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

Random 500

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

 Note
You can also simulate the migration for speci c 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 speci c migration object instances. To do this, select the relevant migration object
instances and choose the Exclude button.

Monitoring the Status of the Simulation Process

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.

Viewing Messages for Migration Object Instances

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

For migration object instances that contain errors, it is important to identify the cause of the error. You can do this by viewing
messages for the relevant migration object instance. To view the messages for a migration object instance, proceed as follows:

1. On the Migration Project screen, identify the relevant migration object.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 63/71
1/1/2021
2. In the Simulation column, the system displays the number of errors beside the text Errors:. Click this number.

3. The system opens the Migration Object Instances screen, and displays the instances that contain errors.

4. Select the migration object instance that you want to analyze, and choose the Messages button.

5. The system opens the Migration Object Instance, Messages screen.

On the Migration Object Instance, Messages screen, you can view the messages that exist for a migration object instance. For a
migration object instance, the following message types are possible:

Error

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

Warning

We recommend analyzing any warning messages, as they could be relevant for your migration project. You can continue
with the simulation without taking additional action, but note that additional action may be required in some situations.
You therefore need to analyze any warning messages and 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.

On the Migration Object Instance, Messages screen, you can view the total number of messages that exist for a migration object
instance, as well as the number of times that the message type occurred, for example 3 Error, 0 Warning, and so on. Under this
information, the system displays a list of the messages. By default, the system displays all messages of all types but you can
display messages of a speci c type if required. To view the messages of a speci c type, click the type icon, for example the Error
icon. The system will then list all the error messages only.

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.

Migrating Data to the SAP S/4HANA System

Once you have processed all open tasks for a migration object, you can transfer data to the target SAP S/4HANA system. Note
that we recommend that you rst 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:

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 64/71
1/1/2021
All Instances

The system can migrate all migration object instances.

All Instances with Errors

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

Random 10%

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

Random 500

The system can migrate a random 500 migration object instances.

All Successfully Simulated Instances

The system can migrate all simulated successfully instances.

 Note
You can also migrate speci c 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 speci c migration object instances. To do this, select the relevant migration object instances and choose
the Exclude button.

Finishing a Project

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 retention
period expires. If you set the option Data Retention Period to Oﬀ, then the project and all associated data will be kept in the
system inde nitely. If required, you can change the retention time for nished projects. To do this, open the relevant project and
choose the Settings button. You can nd the settings for retention time on the Technical Information tab.

Monitoring the Status of the Migration Process

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

Percentage of instances migrated successfully

Percentage of instances with errors

Percentage of instance not yet started

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

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

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 65/71
1/1/2021

Viewing Messages for Migration Object Instances

On the Migration Project screen, in the Migration column, you can view the number of migration object instances that have been
migrated successfully and the number of instances for which errors exist. You can also view the number of instances which have
not yet started.

1. On the Migration Project screen, identify the relevant migration object.

2. In the Migration column, the system displays the number of errors beside the text Errors:. Click this number

3. The system opens the Migration Object Instances screen, and displays the instances that contain errors.

4. Select the migration object instance that you want to analyze, and choose the Messages button.

5. The system opens the Migration Object Instance, Messages screen.

On the Migration Object Instance, Messages screen, you can view the messages that exist for a migration object instance. For a
migration object instance, the following message types are possible:

Error

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

Warning

We recommend analyzing any warning messages, as they could be relevant for your migration project. You can continue
with the migration without taking additional action, but note that additional action may be required in some situations. You
therefore need to analyze any warning messages and 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.

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 where the message occurred, for example during the
selection process or during the migration.

Date and Time

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 66/71
1/1/2021
The date and time when the message occurred.

Transferring Content from One System to Another

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

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

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

SAP S/4HANA Migration Object Modeler

 Note
The functions and features oﬀered by the SAP S/4HANA migration object modeler depend on the migration approach of your
SAP S/4HANA Migration Cockpit project. Detailed documentation for the SAP S/4HANA migration object modeler can be
accessed directly from transaction LTMOM.

Read Access Logging Con gurations in Migration Cockpit

You can use the Read Access Logging (RAL) report to con gure which read-access information to log in the system and under
which conditions.

SAP delivers sample con gurations for applications. By default, the RAL con guration is inactive.

In the scenarios Migrate Data Using Staging Tables and Migrate Data Directly from SAP System of Migration Cockpit (CA-LT-
MC), users can read the uploaded data records. In order to identify the users who preview data, RAL logs the name of the le or
staging table (depending on the scenario) containing the data, together with the name of the user who opened this le.

In the following con gurations, elds are logged in combination with additional elds, in the following business contexts:

Channel Con guration Description Fields Logged Business

Context

OData CA-LT Migration Instance ID (:Entity Migration of

(Version Types:MigrationInstance:MIGRATIONINSTANCEUUID) customer
RAL Configuration for
2.0) data to SAP
ODATA Service Table ID (:Entity Types:TableData:TABLEUUID) S/4HANA.
/LTB/MIG_MC_ODATA_SRV
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)

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 67/71
1/1/2021

Channel Con guration Description Fields Logged Business

Context

Migration Instance Title(:Entity

Types:MigrationInstance:INSTANCETITLE)

Migration Instance Item eld 1 (:Entity

Types:MigrationInstance:ITEMFIELD1)

Migration Instance Item eld 2 (:Entity

Types:MigrationInstance:ITEMFIELD2)

Migration Instance Item eld 3 (:Entity

Types:MigrationInstance:ITEMFIELD3)

Migration Instance Item eld 4 (:Entity

Types:MigrationInstance:ITEMFIELD4)

Migration Instance Item eld 5 (:Entity

Types:MigrationInstance:ITEMFIELD5)

Migration Instance Item eld 6 (:Entity

Types:MigrationInstance:ITEMFIELD6)

Migration Instance Item eld 7 (:Entity

Types:MigrationInstance:ITEMFIELD7)

Migration Instance Item eld 8 (:Entity

Types:MigrationInstance:ITEMFIELD8)

Migration Instance Item eld 9 (:Entity

Types:MigrationInstance:ITEMFIELD9)

Migration Instance Item eld 10 (:Entity

Types:MigrationInstance:ITEMFIELD10)

Migration Instance Item eld 11 (:Entity

Types:MigrationInstance:ITEMFIELD11)

Migration Instance Item eld 12 (:Entity

Types:MigrationInstance:ITEMFIELD12)

Migration Instance Item eld 13 (:Entity

Types:MigrationInstance:ITEMFIELD13)

Migration Instance Item eld 14 (:Entity

Types:MigrationInstance:ITEMFIELD14)

Migration Object ID (:Entity

Types:MigrationInstance:MIGRATIONOBJECTUUID)

Migration Project ID (:Entity

Types:MigrationInstance:MIGRATIONPROJECTUUID)

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

Migration Object Staging Table Identi er (:Entity

Types:MigrationFileContent:TABLEIDENT)

Migration Object Download Activity ID (:Entity

Types:MigrationFileTemplate:DOWNLOADACTIVITYID)

Migration Object ID (:Entity

Types:MigrationFileTemplate:MIGRATIONOBJECTUUID)

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 69/71
1/1/2021

Channel Con guration Description Fields Logged Business

Context

Migration Project ID (:Entity

Types:MigrationFileTemplate:MIGRATIONPROJECTUUID)

Migration Object File Process ID (:EntityTypes:Entity

Types:DownloadMigrationFile:MIGRATIONFILEPROC)

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.

SAP S/4HANA Migration Cockpit

The following video shows the SAP S/4HANA Migration Cockpit using the migration approach Migrate Data Using Staging Tables.

Open this video in a new window

The following video shows the SAP S/4HANA Migration Cockpit using the migration approach Migrate Data Directly from SAP
System in SAP S/4HANA 2020.

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 70/71
1/1/2021

Open this video in a new window

The following tutorial video will help you better understand how to use Transferring Data to SAP S/4HANA Using Files. It walks
you-through the steps necessary to load an object using the Migration Cockpit.

Disclaimer: The below video is not part of the SAP product documentation. Please read the legal disclaimer for video links
before viewing this video.

SAP HANA Academy - S/4HANA RIG: Migration Cockpit

The following tutorial video will show you how to use the SAP S/4HANA Migration Cockpit and SAP S/4HANA Migration Object
Modeler.

Disclaimer: The below video is not part of the SAP product documentation. Please read the legal disclaimer for video links
before viewing this video.

SAP HANA Academy - S/4HANA RIG: Migration Cockpit an…

https://help.sap.com/http.svc/dynamicpdfcontentpreview?deliverable_id=23187901&topics=a4d4119a2cc9448a98e5d17e6d… 71/71

SAP S - 4HANA Migration Cockpit - Migrate Your Data To SAP S - 4HANA
100% (4)
SAP S - 4HANA Migration Cockpit - Migrate Your Data To SAP S - 4HANA
61 pages
100 SAP S4HANA Data Migration Questions and Answers
No ratings yet
100 SAP S4HANA Data Migration Questions and Answers
102 pages
Login
27% (11)
Login
47 pages
SAP ECC Vs S4HANA Differences
100% (3)
SAP ECC Vs S4HANA Differences
58 pages
Sap Overview Sap01
0% (1)
Sap Overview Sap01
265 pages
With Holding Configuration Steps PDF
100% (1)
With Holding Configuration Steps PDF
12 pages
Data Migration To SAP S4HANA From File
No ratings yet
Data Migration To SAP S4HANA From File
36 pages
Coding Standards - Boomi
No ratings yet
Coding Standards - Boomi
8 pages
Cutover Activity Sap
100% (1)
Cutover Activity Sap
20 pages
Introduction To SAP Master Data Governance
No ratings yet
Introduction To SAP Master Data Governance
32 pages
SAP S/4HANA Migration Cockpit
100% (1)
SAP S/4HANA Migration Cockpit
28 pages
SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer
No ratings yet
SAP S - 4HANA Migration Cockpit - Deep Dive LTMOM For Direct Transfer
70 pages
LTMC For Master Data Step by Step Process
100% (1)
LTMC For Master Data Step by Step Process
14 pages
Plan For s4 Hana Finanace Migration
No ratings yet
Plan For s4 Hana Finanace Migration
4 pages
Rapid Data Migration To SAP S/4HANA
No ratings yet
Rapid Data Migration To SAP S/4HANA
40 pages
Import and Export Bank Accounts
No ratings yet
Import and Export Bank Accounts
6 pages
SAP S - 4HANA MM Mindmap by Benedict Yong
100% (1)
SAP S - 4HANA MM Mindmap by Benedict Yong
1 page
RFBIBL00 With Clearing FB05
0% (1)
RFBIBL00 With Clearing FB05
2 pages
RFBIBL00 With Clearing FB05
0% (1)
RFBIBL00 With Clearing FB05
2 pages
System Admin Notes
No ratings yet
System Admin Notes
35 pages
Unit 1: Getting Started: Week 3: SAP S/4HANA Migration Cockpit - Direct Transfer Approach
No ratings yet
Unit 1: Getting Started: Week 3: SAP S/4HANA Migration Cockpit - Direct Transfer Approach
21 pages
S4HANA MigrationCockpit
100% (3)
S4HANA MigrationCockpit
36 pages
Unit 1: Introduction To Data Migration: Week 1: SAP S/4HANA Migration Cockpit
No ratings yet
Unit 1: Introduction To Data Migration: Week 1: SAP S/4HANA Migration Cockpit
49 pages
Data Migration To SAP S/4HANA From Staging (2Q2)
No ratings yet
Data Migration To SAP S/4HANA From Staging (2Q2)
27 pages
Data Migration in S4HANA by Ugur Hasdemir
100% (3)
Data Migration in S4HANA by Ugur Hasdemir
20 pages
Part 2 - SAP S - 4HANA Migration Cockpit - Using SAP Data Services To Load Data To The Staging Tables - SAP Blogs
No ratings yet
Part 2 - SAP S - 4HANA Migration Cockpit - Using SAP Data Services To Load Data To The Staging Tables - SAP Blogs
14 pages
Data Migration Cockpit (DMC) SAP Blogs
No ratings yet
Data Migration Cockpit (DMC) SAP Blogs
7 pages
s4h Migraccion Cockpit
No ratings yet
s4h Migraccion Cockpit
45 pages
SAP Activate Methodology in a Nutshell: Activate Methodology in a Nutshell
From Everand
SAP Activate Methodology in a Nutshell: Activate Methodology in a Nutshell
Sudipta Malakar
2.5/5 (3)
SAP XI Exchange Infrastructure
From Everand
SAP XI Exchange Infrastructure
equitypress
1/5 (3)
SAP S4HANA Migration Cockpit Up To SAP S4HANA 1909
No ratings yet
SAP S4HANA Migration Cockpit Up To SAP S4HANA 1909
46 pages
S4HANA Vs ECC
100% (1)
S4HANA Vs ECC
32 pages
LSMW PDF
No ratings yet
LSMW PDF
22 pages
SAP LTMOM Migration Object Modeler
No ratings yet
SAP LTMOM Migration Object Modeler
70 pages
S/4 HANA and Its Differences With ECC
0% (1)
S/4 HANA and Its Differences With ECC
21 pages
SAP S/4 HANA Legacy Transfer Migration Cockpit
No ratings yet
SAP S/4 HANA Legacy Transfer Migration Cockpit
13 pages
Data Migration in SAP S4HANA Via Migration Cockpit PDF
No ratings yet
Data Migration in SAP S4HANA Via Migration Cockpit PDF
7 pages
DATA - Migration (With SLT Updated)
No ratings yet
DATA - Migration (With SLT Updated)
20 pages
8-DTV Data Transition Validation
No ratings yet
8-DTV Data Transition Validation
20 pages
SAP Data Migration
No ratings yet
SAP Data Migration
10 pages
Data Migration Cookbook - SAP ECC To SAP S - 4HANA
100% (2)
Data Migration Cookbook - SAP ECC To SAP S - 4HANA
42 pages
Data Migration Material Master
No ratings yet
Data Migration Material Master
19 pages
Data Migration S4hana
No ratings yet
Data Migration S4hana
16 pages
LTMC BP
100% (4)
LTMC BP
12 pages
Your Journey To SAP S - 4HANA A Practical Guide - SAP Blogs
100% (1)
Your Journey To SAP S - 4HANA A Practical Guide - SAP Blogs
11 pages
SAP Data Migration - LTMOM - LSMW Vs LTMC S/4 Hana
No ratings yet
SAP Data Migration - LTMOM - LSMW Vs LTMC S/4 Hana
10 pages
MM Data - Migration
No ratings yet
MM Data - Migration
10 pages
LSMW Migration With IDOC Method and BAPI
100% (1)
LSMW Migration With IDOC Method and BAPI
47 pages
Migration Cockpit App Step by Step
No ratings yet
Migration Cockpit App Step by Step
17 pages
LTMC - SAP S - 4 HANA Migration Cockpit (LTMC) - Activity Type Master Data Upload Step by Step Process - SAP Blogs
No ratings yet
LTMC - SAP S - 4 HANA Migration Cockpit (LTMC) - Activity Type Master Data Upload Step by Step Process - SAP Blogs
13 pages
5 Steps To Prepare Your Brownfield Migration To SAP S4HANA
50% (2)
5 Steps To Prepare Your Brownfield Migration To SAP S4HANA
4 pages
SAP Fiori For SAP S4HANA - Understanding SAP Business Roles
No ratings yet
SAP Fiori For SAP S4HANA - Understanding SAP Business Roles
36 pages
SAP S - 4HANA Migration Cockpit - Migrate Data Using Staging Tables - Transport Concept
100% (1)
SAP S - 4HANA Migration Cockpit - Migrate Data Using Staging Tables - Transport Concept
19 pages
Data Migration Cockpit in SAP S4 HANA
No ratings yet
Data Migration Cockpit in SAP S4 HANA
12 pages
Sap - Ltmom
No ratings yet
Sap - Ltmom
9 pages
Upload Process LTMC
No ratings yet
Upload Process LTMC
55 pages
SAP ECC PP Vs S4 HANA PP
No ratings yet
SAP ECC PP Vs S4 HANA PP
1 page
BSNL ERP Implementation Project: Cut Over Strategy - Transactional Data
No ratings yet
BSNL ERP Implementation Project: Cut Over Strategy - Transactional Data
29 pages
LTMC Mass Upload
No ratings yet
LTMC Mass Upload
31 pages
RICEFW
0% (1)
RICEFW
3 pages
LTMC Process SAP S
No ratings yet
LTMC Process SAP S
23 pages
LTMC
100% (1)
LTMC
22 pages
Sap S4hana Data Migration PDF
100% (2)
Sap S4hana Data Migration PDF
20 pages
Data Migration Strategy and SAP
100% (3)
Data Migration Strategy and SAP
8 pages
LTMC Steps
100% (1)
LTMC Steps
22 pages
Syniti Solution Brief
No ratings yet
Syniti Solution Brief
8 pages
SAPexperts - How To Create A Global Template To Configure SAP MM Processes in Implementations and Rollouts PDF
No ratings yet
SAPexperts - How To Create A Global Template To Configure SAP MM Processes in Implementations and Rollouts PDF
2 pages
Working With S/4 HANA Migration Cockpit (LTMC) - Some Sticky Notes
No ratings yet
Working With S/4 HANA Migration Cockpit (LTMC) - Some Sticky Notes
3 pages
Web Dynpro ABAP Complete Self-Assessment Guide
From Everand
Web Dynpro ABAP Complete Self-Assessment Guide
Gerardus Blokdyk
No ratings yet
Post Manual Activities: Creating Web Dynpro Application
No ratings yet
Post Manual Activities: Creating Web Dynpro Application
5 pages
Superstore
No ratings yet
Superstore
976 pages
BAM Post Manual Activities
No ratings yet
BAM Post Manual Activities
5 pages
Sap Document Got Attachment List Popup
No ratings yet
Sap Document Got Attachment List Popup
1 page
SAP How To Define Logical and Physical File
No ratings yet
SAP How To Define Logical and Physical File
5 pages
SAP Payment Terms Basics
No ratings yet
SAP Payment Terms Basics
5 pages
4a.implementing Customer Master Data Under Company Code
No ratings yet
4a.implementing Customer Master Data Under Company Code
16 pages
SAP - Exchange Rate Upload
100% (1)
SAP - Exchange Rate Upload
9 pages
SAP Change Field Name Text
No ratings yet
SAP Change Field Name Text
1 page
SAP - Debug F110
No ratings yet
SAP - Debug F110
1 page
SAP Currency Transactions
No ratings yet
SAP Currency Transactions
1 page
VAT Code and Percent Using BRF+
No ratings yet
VAT Code and Percent Using BRF+
8 pages
Real-Time Processing of Big Data Streams: Lifecycle, Tools, Tasks, and Challenges
No ratings yet
Real-Time Processing of Big Data Streams: Lifecycle, Tools, Tasks, and Challenges
7 pages
Nokia AirScale Ebook EN
No ratings yet
Nokia AirScale Ebook EN
15 pages
24AA00/24LC00/24C00: 128-Bit I C Bus Serial EEPROM
No ratings yet
24AA00/24LC00/24C00: 128-Bit I C Bus Serial EEPROM
34 pages
Exception Handling in Java
No ratings yet
Exception Handling in Java
18 pages
PAPB 04A EventHandling
No ratings yet
PAPB 04A EventHandling
20 pages
Worksheet 01: Software LAN Wi-Fi Attachments Virus Worm Resolves Anti
No ratings yet
Worksheet 01: Software LAN Wi-Fi Attachments Virus Worm Resolves Anti
7 pages
Chapter 4
100% (1)
Chapter 4
47 pages
ZXR10 8900 Series Terabit MPLS Routing Switch: Product Positioning
No ratings yet
ZXR10 8900 Series Terabit MPLS Routing Switch: Product Positioning
10 pages
What Is Social Networks
No ratings yet
What Is Social Networks
2 pages
Panel of Examiner Summer 2021
No ratings yet
Panel of Examiner Summer 2021
7 pages
Top 10 Best AI Websites - The Most Useful
No ratings yet
Top 10 Best AI Websites - The Most Useful
14 pages
The Search Ecosystem
No ratings yet
The Search Ecosystem
1 page
IT Chapter 6
No ratings yet
IT Chapter 6
7 pages
TCSCOL Module 3.7.2023
No ratings yet
TCSCOL Module 3.7.2023
16 pages
Unit 2
No ratings yet
Unit 2
43 pages
4.1 4-S2S-IPSecVPN-Tunnel-Router
No ratings yet
4.1 4-S2S-IPSecVPN-Tunnel-Router
6 pages
BCT Unit 3
No ratings yet
BCT Unit 3
25 pages
FINAL TEST CSC134 - Part B and Part C
No ratings yet
FINAL TEST CSC134 - Part B and Part C
7 pages
WPP Gen2 - Registration - 2017
No ratings yet
WPP Gen2 - Registration - 2017
20 pages
Chapter1-Overview of Database Concepts
No ratings yet
Chapter1-Overview of Database Concepts
19 pages
Applications To SAP: Home Quick Answers Discussions Features Community Help Articles
No ratings yet
Applications To SAP: Home Quick Answers Discussions Features Community Help Articles
15 pages
Chapter One
No ratings yet
Chapter One
22 pages
Guide To Cloud Security Management and Best Practices
No ratings yet
Guide To Cloud Security Management and Best Practices
18 pages
Peplink 5g Connectivity
No ratings yet
Peplink 5g Connectivity
26 pages
What Role Can IS Play in The Pharmaceutical Industry?
No ratings yet
What Role Can IS Play in The Pharmaceutical Industry?
4 pages
03LAB01
No ratings yet
03LAB01
3 pages
To Computer Networks: Shailendra Tiwari
No ratings yet
To Computer Networks: Shailendra Tiwari
40 pages