How Are Staging Tables Created in SAP Data Migration Cockpit (DMC)? in Fiori App

[blkanth77]

Hello SAP Experts,

I am currently working on SAP Data Migration Cockpit (DMC) and trying to understand how staging tables and temporary storage structures are created in the system. While I am aware that staging tables are automatically generated when a migration object is activated in LTMOM (Migration Object Modeler), I would like to gain a deeper understanding of the underlying logic and process.

•    I have observed that staging tables typically follow the /1LT/<6-digit object ID> pattern

Specific Question:

How does SAP determine the structure of a staging table?

• What fields are considered, and how does SAP map them from source to target?

  • Where exactly are these tables stored in the HANA database?  

  • Is there a way to manually create or modify staging table structures? Are there specific rules for defining primary keys or mandatory fields

  • What is the reference objects SAP is considering for creating the staging tables?   

Any insights, documentation references, or practical experiences on this topic would be greatly appreciated!

Thanks in advance for your help.

Best regards,

[IreneLiu]

Hi blkanth77, 

You may find details for using tags in Blog below:

https://community.sap.com/t5/enterprise-resource-planning-blogs-by-sap/q-amp-a-for-sap-s-4hana-cloud...

[IreneLiu]

Hi blkanth77, As the question is related to data migration and the migration cockpit tool, remain the Data Migration tag here for better searchability.  Best regards. Irene

[blkanth77]

Requirement Statement:

We are exploring options to extract data from SAP S/4HANA in the Data Migration Cockpit (DMC) staging table format. The intent is to leverage this extracted data for footprint data moves, such as:

• Modifying Product Plant data
• Changing the plant assignment and reloading the data into S/4HANA
• Transforming the data into a legacy system format (e.g., ECC) for loading into that system

While we understand that custom ABAP programs can be developed to extract and generate files in the DMC staging table structure (which can then be adapted as needed), we would like to explore whether there are standard tools available in SAP S/4HANA that can support this process with minimal maintenance overhead.

In particular, we are interested in evaluating the feasibility of using:

• CDS Views
• HANA SQL Procedures
• Other standard S/4HANA toolsets that can support data extraction in a DMC-compatible format

We are looking for best-practice recommendations and efficient methods to achieve this with the tools and capabilities provided within the S/4HANA system itself.

[IreneLiu]

Hi @blkanth77 

Here is very comprehensive FAQ document mentioning the staging tables approach in Migration Cockpit tool.
KBA 2733253 - FAQ for SAP S/4HANA migration cockpit. Migration approach: Transfer / Migrate data using staging tables

Hope this helps.
Best regards,
Irene

[blkanth77]

For example, if I consider the migration object as Bank Master, it shows the reference structure S_BNKA for creating staging tables. How can I check whether this structure exists in SE11 or elsewhere? Also, I would like to understand how the staging table is being generated and what is the logic behind it..

[IreneLiu]

Hi @blkanth77, the quickest way to check the mapping between Structure and table is clicking on the number of Tables in Migrate Your Data app. You will find the technical name for structure (S_*) and technical ID for staging table (/1LT/DS<system ID><numeric identifier>).

Of course you can check the value entered in backend by searching this table or you can just open Migrate Object Instance screen to check the value.

All of the information mentioned above can be found in: 

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.

KBA 2733253 - FAQ for SAP S/4HANA migration cockpit. Migration approach: Transfer / Migrate data using staging tables

Regards,
Irene

[blkanth77]

We are looking at an option to extract data from S/4 Hana in Data migration Cockpit staging tables format. We would like to use this data for footprint data moves e.g. Modify the product Plant data, change the plant and load again into S/4 or transform the data in to legacy system format (e.g. ECC) and load there. I understand we could write ABAP programs to generate files in DMC staging tables format and then modify the files according to our need. However, I would like to explore if other tools provided by S/4 HANA for e.g. CDS views, Hana SQL procedures, or any other tools set delivered with S/4 Hana with little maintenance We do not have Data Services.