- SAP Managed Tags
The SAP S/4HANA Migration Cockpit provides a user-friendly interface to migrate master and transactional data, such as initial stock, into an SAP S/4HANA system. This document outlines the step-by-step process to upload initial stock using the Migration Cockpit with the "Staging Table" approach.
Prerequisite:
Scope ID to be activate: 2Q2 - Data Migration to SAP S/4HANA from Staging
Business role activation: SAP_BR_BPC_EXPERT- Configuration Expert - Business Process Configuration.
Create a Project
- Navigate to App: Migrate Your Data. App ID: F3473
- Click on Create to start a new project and select Migrate data using staging table.
- Enter the project name (e.g., Initial_Stock_Upload).
Enter the project name, and mass transfer ID is system generated ID for each project and it is used to differentiate the projects across the system. When working on the extension template, fill in the mass transfer ID in the run ID column for identification.
In the database connection, select the local SAP S/4HANA database since this is not a remote migration. Click on this and proceed to step 2. Select the relevant template based on your project activity. Here, you need to pick the material inventory balance template for Initial Stack Upload project.
On the left side, you will see a list of available templates. Choose the template you want and move it to the right side. Then, click on review and create the project.
The project has been created, but it hasn't started yet. When you start the project, the status changes to in progress. After you finish the project, you mark it as finished and choose how long to keep the data. Once this period ends, the project disappears from the list. However, the data you uploaded will still be available in the system.
After you create the project, there are some important details to know before starting.
First, there are stage-wise data validations. In this migration object how many tables are involving and how many instances going to create in the system.
Next mapping tasks table you can get the information during mapping task process, like errors and successful same you will get during simulation and migration.
- Download the template
- Upload the prepared (data filled) template
- Prepare the data
- Mapping tasks
- Simulation
- Migration
- Correction file
The above the steps involved in the migration process. If you completed the each process next process with move automatically you need to just execute the process. Incase any error in the current process it won't proceed to next process you need to resolve the error and move to next process. Correction file will not generate for all the process. Incase migration completed with error you need to generate correction file and in that file only failed line items are available. You should correct it and reupload and reprocess the steps again.
Download & Upload.
Download the Template in XML format, file the relevant data, and upload the template.
Prepare.
The staging tables need to be prepared before they can be used to transfer data to SAP S/4HANA.
You can also run a consistency check for the data in the staging tables. All records need to be associated with records at a higher level in the hierarchy of staging tables. The consistency check checks whether these associations exist.
Note that if you have transferred data to the staging tables using template files, the system has already performed the consistency check.
However, if you have transferred data to the staging tables using your preferred tools, we recommend performing the consistency check now.
Mapping Task.
Mapping tasks are essential for ensuring accurate data transfer by specifying how source fields in a legacy system are related to target fields in the SAP system.
Mapping tasks help the system understand how to connect the values in your upload file with the values already defined in SAP.
For example, in your file, you might write the full state name like "Karnataka", but SAP uses a short code like "KA". Instead of changing all values in the file, you can simply create a mapping that tells SAP:
"Whenever you see Karnataka, use KA."
This is important for fields like:
Document Type (e.g., "Standard" → "NB")
Country (e.g., "India" → "IN")
Region (e.g., "Tamil Nadu" → "TN")
These values are fixed in SAP and can’t be overwritten. Mapping helps make sure your data fits SAP’s format without changing your original template.
Simulation.
Run Simulation to validate consistency and completeness.
Check logs for errors or warnings.
Migration.
After a successful simulation, start the Migration.
SAP creates Material Documents using movement type 561.
Migration Result.
Review Log Files for confirmation.
Verify stocks using Display Material Document, Stock Overview (MMBE), or Monitor Material Stocks.
If errors occur, refer to the logs, create the correction file and correct the data, then reprocess.
This completes the initial stock upload using the SAP S/4HANA Migration Cockpit in public cloud.
Note: upload file template should be below 100MB
And this activity is only for material stock upload. There is no option to maintain posting period in the migration template. For this use “Define Settings for Legacy Data Transfer” and maintain the posting period and keep the status as ongoing once activity completed switch to in preparation or completed. SAP Note: 2914088 - Migration Error: Posting period &1 YYYY is not open. - SAP for Me
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
