SAP

LTMC Step by step guide to execute for data

upload
Зміст
1. General definitions and comparison: LTMC vs LSMW...........................................3
2. Step-By-Step Process for Legacy Transfer Migration............................................5
1. General definitions and comparison: LTMC
vs LSMW
LTMC (Legacy System Migration Cockpit)
LTMC is the preferred data migration tool for SAP MDG/ S/4HANA and is part
of the newer, more modern approach for migrating data. It is designed to make data
migration more seamless and efficient, with integrated features to guide users
through the process.
Key Features of LTMC:
1. Modern Interface:
- LTMC is part of the SAP MDG/ S/4HANA suite and uses a web-based
interface via Fiori apps, making it more user-friendly and intuitive.

2. Migration Objects:
- LTMC is structured around migration objects, which are predefined
templates for different types of data (e.g., Customer, Vendor, Material
Master, etc.). These templates include the data fields necessary for
migration and automatically handle data mapping.

3. Predefined Templates:
- Provides predefined migration templates for standard data objects,
making it easier to map and transform legacy data into the SAP S/4HANA
format.

4. Real-Time Monitoring:
- LTMC allows users to track the migration progress in real-time through the
Fiori interface. You can see the status of the data migration, check for
errors, and view logs.

5. Data Validation and Simulation:

- LTMC allows for data validation before final migration, ensuring that the
data complies with SAP requirements.

6. Supported File Format:

- Migration should to be saved in the following way: Microsoft Excel®, save
the file in XML format (with .xml extension).
- If the file size is not more than 100 MB, you can leave the file as it is.
- If the file size is more than 100 MB, you must create a zipped version of
the file (with .zip extension).
- Use the migration tool (migration workbench) to upload the ZIP or XML
file.
- You can upload zipped files only up to 165 MB.
- You can upload only one zipped file at a time.

7. What can LTMC do:

- Migrate new data into SAP S/4HANA (initial loading of data such as
customer master, vendor master, material master, etc.).
- Only expanding the existing data to new Company Codes, Purchasing and
Sales Organizations, Plants, adding Basic Text (only for the language code
 for which it is missing on the material level), and assigning a
Classification.

8. What LTMC Cannot Do:

- Modify existing data in SAP S/4HANA. Once data is migrated and present
in the system, LTMC is not designed to update or change that data.
- If you need to update or modify existing data after migration, you would
typically use other SAP tools and methods, such as:
- Mass Maintenance (t-code MM17, MASS, XD99, XK99) – For modifying
master data in bulk.
- SAP Fiori Apps – Many SAP Fiori apps allow for bulk data updates or
management of master data, and they can be leveraged for maintaining
data post-migration.
- LSMW (Legacy System Migration Workbench) – Although LSMW is
primarily for data migration, it can also be used for data updates in the
SAP system.

LSMW (Legacy System Migration Workbench)

LSMW is a legacy tool that has been used for data migration in older SAP
systems, including SAP ECC. It's also available for use in SAP MDG/ S/4HANA, but it's
considered somewhat outdated compared to LTMC.
Key Features of LSMW:
1. Data Migration Process:
- LSMW follows a structured 5-step process to migrate data: Recording,
Mapping, Conversion, and Uploading the data. It provides more control
over each migration step.

2. Data Mapping and Transformation:

- LSMW allows users to define complex data mapping and data
transformation rules, making it suitable for handling complex data
migration requirements.

3. Recording Method:
- In LSMW, users can create recordings that define how data is entered into
the SAP system (this is useful for migrating transaction data). These
recordings define the structure for the migration.

4. Batch Input Method:

- LSMW typically uses Batch Input and IDOC methods for migrating data,
which means it can process data in large batches.

5. Customizability:
- LSMW is highly customizable, allowing users to handle special cases or
non-standard data migration requirements.

6. Old Interface:
- The interface of LSMW is more transactional (using SAP GUI), and it can
be more complex and harder to use compared to the modern LTMC
interface.
 7. Flexibility:
- LSMW offers greater flexibility for handling legacy data that may not fit
perfectly into the standard migration templates used by LTMC.

8. Supports Multiple Formats:

- LSMW can work with multiple data formats, including: Flat files (CSV,
TXT): Can read data from external files.
- BAPIs: Can use Business Application Programming Interfaces (BAPIs) to
migrate data programmatically.

9. Use Cases for LSMW

- Complex transformations: If the data needs complex transformations or
mapping (for example, historical transactional data), LSMW might be a
better option.
- Non-standard migration requirements: For cases where data doesn't fit
into predefined migration objects or templates, LSMW provides more
control.

2. Step-By-Step Process for Legacy Transfer

Migration

Data migration through the transaction LTMC (Legacy System Migration

Workbench) in SAP is part of the SAP MDG/ S/4HANA system, and it facilitates the
process of migrating data from legacy systems into SAP. This tool helps streamline
the migration process by providing templates, data mapping, and the ability to
monitor and validate the migration process.
The SAP S/4HANA migration cockpit uses migration objects to identify and
transfer the relevant data. A migration object describes how to migrate data for a
specific business object to SAP S/4HANA. It contains information about the relevant
source and target structures, as well as the relationships between these structures.
It also contains mapping information for the relevant fields, as well as any rules
used to convert values that are migrated from source fields to target fields. SAP
provides a predefined migration object that you can use to transfer your data.
 The list of available Migration Objects for the MDG team

Link to an example
Name Purpose Comments of the Migration
Template
Characteristic To create new or modify
Using for migration characteristic data into an SAP
existing characteristic values
system. Characteristics in SAP are attributes or
for existing characteristics, you
properties that define objects within specific classes.
can use the program
For example, characteristics can describe materials
ZMDG_CHARACT_UPLOAD.
(e.g., color, size, weight), equipment (e.g., voltage,
power rating). The Characteristic Template helps
ensure that these attributes are correctly migrated
from legacy systems or external sources into SAP,
enabling proper classification and categorization of
objects in the new system.
Class Using for migration class data into an SAP system. It is important that after
In SAP, classes are used to group objects (such as creating new classes and
materials, equipment, or products) based on shared assigning characteristics,
characteristics. The Class Template enables should be formed a formula for
businesses to migrate these class definitions, auto-naming using programs:
including the characteristics associated with them, ZMDG_CHANGE_FORMULA
from legacy systems or external data sources into S and
the SAP system efficiently. ZMDG_LOADING_FORMULA.

Class hierarchy Using for migration class hierarchies into the SAP The template has not been
system. A class hierarchy in SAP is a way of used yet, the analog of mass
organizing and grouping related classes under a class hierarchy maintaining can
common parent class, facilitating efficient be the LSMW: HIERARDEL_2
classification and management of objects like - Mass management of class
materials, equipment, or products based on shared hierarchy (deletion) and
characteristics. HIERAR_ASSIGN - Mass
management of class hierarchy
(assignment).
Object classification - General Using for migration classification data in SAP.
template Classification in SAP allows materials objects to be
assigned to different characteristics and classes for
better categorization, reporting, and processing. This
template helps in transferring classification data from
legacy systems into SAP. This template ensures that
all relevant classification data is migrated in a
structured manner.

Bank Using for migration bank master data from legacy

systems in SAP. This template ensures that accurate
bank-related information, such as bank accounts,
bank key, branch information, and other financial
details, are transferred into the SAP system. It
ensures that SAP can correctly process financial
transactions, payments, and bank-related
operations.
Customer (copy X02) - extend existing Using for extension existing customer master
record by new org lev. records to additional organizational units in SAP. For
example, if a customer is already set up in one sales
organization or company code, but needs to be
extended to additional organizational levels like other
sales organizations or distribution channels, or
company codes this template enables the smooth
extension of that data.

Supplier (copy X02) Using for migration supplier master data from legacy Initially, all Business Partners
systems in SAP. The main purpose of the Supplier (Suppliers, Customers, Trading
Template is to migrate supplier master records into Points) are created using this
SAP. This includes details such as the supplier's template, and then we should
name, address, contact information, payment terms, to use template Customer
and procurement-related data, ensuring that the SAP (copy X02) - extend existing
system is populated with essential supplier data after record by new org lev. for
the migration process. extension Customers and
Trading Points.

Supplier - extend existing record by Using for extension existing supplier master records
new org levels to additional organizational units in SAP. For
example, a supplier that is currently set up for one
 company code or purchasing organization needs to
be extended to additional company codes or
purchasing organizations. This is essential when an
organization needs to do business with a supplier at
multiple levels or locations.
Product Using for migration product master data (also It is important to note that when
referred to as material master data) in SAP. This migrating materials, Units of
includes key product details, such as product measurement are specified
descriptions, material types, pricing, procurement in ISO format. To determine
information, and other essential attributes. the ISO format for the relevant
units of measurement, use the
t-code CUNI.

Product - extend existing record by Using for extension existing product master records
new org levels to additional organizational units in SAP. For
example, a product that was originally set up for one
plant or sales organization may need to be extended
to other plants, sales organizations, or distribution
channels.
Material - extend existing record with Using for extension existing material master records You can also use this template
long text in SAP to new Basic Data Text. The template allows to change existing full names,
you to extend existing material records by adding but before doing it, you must to
long text fields that provide additional information remove the full name for the
about the materials. required language code by
using LSMW:
BASIC_TEXT_UPL - Mass
deleting data from a view Basic
data text / long text of materials
Material inspection setup Using for extension existing product master records The analog of mass inspection
to material inspection settings in SAP. This template settings for materials can be
facilitates the transfer of inspection-related the QA08 t-code (but first, if the
configuration and settings, such as quality inspection material is not expanded to the
rules, inspection types, and associated data. Quality Management
The Material Inspection Setup is crucial for perspective, it must be done in
businesses that manage and control the quality of bulk using the MM17 t-code,
materials, products, or services within SAP, technical field for the possibility
particularly in Quality Management (QM). of mass expansion to the angle
- SSQSS and add the value to
the field - 0000) after you can
use QA08.
 Below is a general step-by-step instruction on how to perform a data
migration using LTMC
Step 1: Preparation:
Before starting with LTMC, ensure the following prerequisites are met:
1. Data Migration Cockpit (LTMC) is activated and configured.
2. Identify and gather the legacy system data that needs to be migrated
(such as master data, transactional data, etc.).
3. Define the migration objects (e.g., Customer Master, Vendor Master, GL
Account, etc.) in the Migration Object Templates.
4. Verify that necessary authorizations are in place for users involved in the
data migration process.
Step 2: Access LTMC Transaction:
1. Log in to the SAP MDG system.
2. In the SAP GUI, enter the transaction code LTMC in the command field.

Step 3: Find a Migration Project:

1. In the Data Migration Cockpit, on the list of Available Migration Projects list
select the GLOBAL MIGRATION PROJECT - HAVE TO USE IT (currently this
project is used for migration).
 Step 4: Select Migration Objects:
1. After the migration project is selected, choose the appropriate migration
objects from the list of available templates. For this purpose you can use the

Search Bar (button or keyboard shortcut Ctr + F)

Step 5: Download Templates for Data:

1. For each migration object, you will need to download templates. These
templates are typically XML files that contain the necessary fields for
uploading data into SAP.
2. Click on the Download Template button for each selected migration object.
3. Complete the downloaded templates with the legacy data that you want to
migrate. Ensure the data matches the required format specified in the
template (examples of completed migration templates with relevant
information can be found in the table The list of available Migration
Objects for the MDG team).
Step 6: Upload Legacy Data
Main Actions

A. Upload File E. Convert

Values.

B. Activate F. Simulate.

C. Start Transfer G. Execute

Import.
D. Data Validate

1. After preparing the data in the templates, go back to the LTMC project and
click on Upload File.
 2. Select the migration object and click Upload to upload the completed XML
templates.
3. Review any error messages or warnings generated during the upload and
correct the data if necessary.
Step 7: Execute Migration:
Once the data has been successfully validated, you can proceed with the
actual data migration.
1. Click on the activate button and start the transfer.

2. Data will be transferred once it is done, the close button will be enabled.
3. If any error or data is missing will get the error (we will need to stop the
migration process, deactivate and then delete the file, make changes in the
migration template and go back and start from Step 6: Upload Legacy
Data) if all data in the template is good we can proceed further.

4. Click Next.
5. When we are executing for the first time a particular object in a project we
need to map fields.
6. Click each line item and do the mapping of values.

7. Select line item and click check once status turns into green light click save
so next time the system will do the mapping automatically.

8. Once all the mapping is completed and no open item click next to simulate
import.
9. Similar to upload once its completed click close to proceeding further.

10.Backed Program will execute and data is simulated. If any error go back and
fix it and repeat the same steps, if no error then click Next.
 11.If all the steps are completed without, any error then click on Finish.

Step 11: Monitoring and Reporting

1. Use SAP Fiori apps or the SAP GUI to monitor the overall status of your data
migration project.
2. You can generate migration status reports for example, using the SE16N t-
code with the selection of the necessary tables and setting up the selection
criteria.