LTMC - SAP S/4 HANA Migration Cockpit
  • 25 Mar 2024
  • 5 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

LTMC - SAP S/4 HANA Migration Cockpit

  • Dark
    Light
  • PDF

Article summary

This topic relates to the following sections:

Overview

The SAP S/4HANA Migration cockpit allows users to migrate Asset Balances, Exchange Rates and GL Balances with the LTMC (Legacy Transfer Migration Cockpit) XML template. The transaction code within SAP S/4HANA is  LTMC. As of S/4HANA Cloud 2008 and SAP S/4HANA 2020 onwards, LTMC has been replaced by the Fiori application Migrate Your Data. LTMC can still be used to execute existing migration projects, but in read-only.

Migration Cockpit / Migrate Your Data still largely only supports initial record creation, meaning the use of IDOC and/or BAPIs using LSWM or Data Services may be required to support update activity.

Note

LSMW is not formally supported or recommended by SAP.

There are two ways to import data to the SAP S/4HANA system - by File or by Staging table. Transferring by file takes much longer to process, so it is suggested that data be loaded using the Staging tables supplied by the LTMC. The following information was derived through the SAP Help Portal:

Transferring Data to SAP S/4HANA Using Staging Tables

Context

The SAP S/4HANA migration cockpit automatically creates staging tables for each migration object that is relevant for the project. Fill the staging tables with data by using Syniti Migrate as the staging system. This process adds a few extra steps to the translation and replaces standard practice for loading by LSMW using BAPI, IDOC, or Recordings. The Extract and Translation of the data remains largely the same, while the Loading of the data is performed using tables in a HANA Database to SAP S/4HANA system.

During the execution of the Data Services job, the system, as part of the Export process, transfers the rows of data from the conversion database (Ex: Oracle or SQL Server) to the SAP HANA database system tables that have been created as part of the migration cockpit steps. Once the target data has been loaded into the SAP HANA DB Staging table(s), loading of the data is run through the LTMC in SAP S/4HANA system.

Prerequisites

The Syniti Migrate application extracts and transforms the data using either SQL Server or Oracle as the database staging system (if HANA DB is selected in this case as the data must reside in HANA DB to load to SAP S/4HANA system). There is an SAP HANA DB connection between the SAP S/4HANA system and the Syniti Migrate staging system.

Procedure for Conversion of Data in Migration using LTMC

Once the Project is set to use S/4HANA as the target system, the project team must apply LTMC related steps to the overall conversion development.

  • Create xAppLTMC Datasource

    The xAppLTMC datasource is used in the scripting of XML when using LTMC Staging as the Load Type. This datasource is created with a Datasource Purpose of Migrate so that it uses the Migration Working Server. Refer to section Administer > Setup >Environments > Adding & Editing a Migrate Datasource for details of this process. If this datasource is not available at time of XML build, the LTMC section of the XML will not produce as expected.

  • Dataset Design > Maintain Dataset

While developing the conversion object Dataset within Syniti Migrate, the user selects LTMC Staging as the Load Type. By selecting this option, the system prepares to generate the Dataset XML scripting to include extra steps. See example below:

null

Dataset: Edit: Load Type of LTMC Staging

Refer to section Catalog > Dataset Design > Create & Maintain Datasets  for details of the process of Creating and Maintaining a Dataset.

  • Mapping > Dataset > Build XML

Within Syniti Migrate Mapping, as the Dataset XML Scripting is generated, the build adds a Workflow, Dataflow, and Query for LTMC Staging as well

null

Mapping: Dataset: View XML for LTMC Export table

Refer to section Migrate > Mapping > Create & Maintain Dataset XML  for details of the process of Creating and Maintaining a XML scripting for a DATASET.

  • Manually Create the xAppLTMC Datastore within Data Services

Create a Datastore within Data Services that serves as the datasource for the HANA DB used to store the LTMC Staging tables. This Datastore is named xAppLTMC and it is a connection to the HANA DB with Schema of the LTMC Staging tables.

null

Data Services: Datastore: xAppLTMC

During the import of XML file(s) for the Dataset, the Export section of the project reflects a table to template table transfer of rows where the Template table is the object staging table in HANA DB.

  • Data Services Export Table Data Transfer

Data Services transfers the target table rows from the Staging database to HANA DB. So, instead of building out a file in the export, the system passes the data to a table stored in the HANA DB for use in loading to SAP S/4HANA.

This HANA DB table is also built as a TEMPLATE table so that each time the table changes, this template table allows for changes in Data Services. Each time the user in SAP S/4HANA updates the Staging Table, the Data Services table needs to also change to reflect the same information. That is why a TEMPLATE table is necessary.

As shown below, the conversion target table is set up to insert the relevant records to the HANA DB LTMC Staging table (Created as a TEMPLATE Table).

null

Data Services: Datastore: Target table

null

Data Services: Project Workflow: Exports

Procedure for Migrating Data to SAP S/4HANA

Steps for migrating of data to SAP S/4HANA:

  • Access the SAP S/4HANA migration cockpit by using transaction LTMC.

  • Create a migration project to transfer data using staging tables and specify a database connection to the source system database (HANA DB)

  • Open the migration objects that are relevant for the project.

  • For each source structure of a migration object a separate staging table is created automatically.

  • Add the data that is relevant for the migration object to the staging tables using the Migration application.

Once the relevant data has been transferred to the staging tables for the migration object, transfer the data for that migration object to SAP S/4HANA. When the activity Transfer Data is complete, the data has been migrated to SAP S/4HANA.


Was this article helpful?

ESC

Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence