Technical Articles

Ratul Chakraborty2
April 10, 2019 4 minute read

Working with S/4 HANA Migration Cockpit (

LTMC) – some sticky notes
Follow RSS feed Like
2 Likes 3,813 Views 3 Comments

When we talk about SAP, now a days, we talk about S/4 HANA only. S/4 HANA is the most
amazing product SAP has ever launched since it had become the greatest ERP application of all
time. As we all know, SAP will no more be supporting ECC 6.0, the previous version, after
2026, there will be big rush among the big companies all over the world to migrate from ECC to
S/4 HANA. Till that time comes, we, the SAP consultants, must be prepared with upgrading
ourselves to S/4 HANA and make the most of this opportunity to grow as an SAP S/4 HANA
consultant.

In this blog, I’m going to share with you some tips and tricks on S/4 HANA Migration Cockpit
(Transaction – LTMC). I hope that helps.

We will focus on the option – Transfer Data from File.

1. Mass transfer ID & Data retention time

Mass Transfer ID is generated automatically when a new project is created in the system. This
ID is being used to differentiate between the projects across systems. If we want to copy project
specific settings (Template customizations, value translations in convert values, duplicate check
etc.) to different systems, we need to enter a mass transfer ID that is unique across all systems.
Likewise, we can transfer project specific settings from Quality to Production.

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

2. Use the same project across all the systems

 Use of same project (same Mass transfer ID) is highly recommended to avoid:

 Duplication of efforts in terms of Template customization, Convert values etc.

 Create duplicate records in the system – same records (same key combination) cannot be
created using LTMC under the same Mass Transfer ID.
 The entire project configuration can be migrated to a new system using
IMPORT/EXPORT functionality in LTMC

3. Correct the data only in the Source file

 Get the list of errors in the simulation step & cancel the current run and delete the source file
from LTMC. Then, correct the data in the source file and re-run the simulation in LTMC.

4. Inconvenient error log

 The error log generated in any LTMC steps does not follow a proper template. The error record
number and the error descriptions are provided in 2 separate lines, and that is very difficult to
manage when you have millions of data records. You have to rework on the error log and
transform the data in such a manner that is quite easily understood by business and rectify the
data errors.

5. Avoid creating duplicate records

The concept of migration cockpit is quite similar to SLT. It does not allow the system to create
duplicate records. System keeps track of the already created records in the table
DMC_FM_RESTART. However, this table is client independent. That means the system
restricts duplicate data not only in a single client but throughout all the clients. However, there
are ways to modify the table mentioned above and reload the same records in same or different
clients.

6. Delta files do not have error details, download the errors before finishing the data
load

 After completion of the data load, MC generates a delta file with the failed records that were not
loaded. But, that file does not include the relevant errors corresponding to the data
records.Hence, you have to save the error records in your local machine before finishing the data
load job.

7. Client dependent Template customization 

SAP has provided load templates for the objects that can be migrated using MC. If required, the
templates can be customized via transaction code LTMOM (Migration object Modeler). Once
you are done with template customization, you have to SAVE & REGENERATE the object.
While re-generating the modified object, SAP creates a new program in the run time and that
program gets called when you run the data load for the object. As we all know, SAP systems
might have multiple clients for the same environment. The data load can be done (after template
customization) in the same client where the template was customized. Otherwise, LTMC will not
work, it won’t throw any error as well. But, in the back end, when you go to ST22 (ABAP
runtime errors), you will find run time error under your ID.

8. Do not provide external numbers, when the system is configured with internal
numbering 

Suppose, the system is configured as internal numbering for a particular BP group of Vendor
Master. If you put external numbers (incremental starting from 1) in the Vendor Number column,
the system will throw error that external numbering not allowed. Instead of using incremental
number starting from 1, try to put values such as A1, A2, A3 etc. 

9. List of Mandatory fields( * ) may differ in LTMC template & system configuration
perspective 

List of Mandatory fields on the template and on the S/4 screen level are different. List of
mandatory fields on the template can be customized via LTMOM and the list of mandatory fields
on the screen level can be configured via transaction SPRO. This step is mostly done by
functional consultants before MD team starts loading the data. If a field is marked as mandatory
in the template, you cannot proceed with the data load without entering any values in that
column, even though the field is not mandatory on the screen level. Template customization
should be done based on screen level configuration. 

10. No change functionality, difficult to change/correct already loaded records 

We do not have any change functionality yet in LTMC. So, once the data is loaded, you cannot
change the same using LTMC. We might have to use Mass update transaction codes (MASS &
MASSD) or ABAP program to carry out necessary changes in the data. LSMW is still available
in S/4, however this is not SAP recommended anymore. Customer can use at their own risk. 

11. Files should not contain duplicate records 

Duplicate records must be removed before running LTMC. You will not be able to load any file
to any project if the file contains duplicate records.

I hope this blog will help you with your day to day activity on Migration Cockpit. In my next
blog, I will discuss on customizing migration templates using LTMOM.