SAP S/4 HANA Data Migration : How to migrate your data using SAP’s Data Migration Cockpit -

SAP S/4 HANA Data Migration : How to migrate your data using SAP’s Data Migration Cockpit  -

A step by step to help a user to hit the ground running when implementing SAP S/4 HANA.

Prerequisites: How to migrate your data using SAP’s Data Migration Cockpit : 

1).Migration Project -This is the first step to create / open migration project in the SAP Data Migration Cockpit. So the migration project facilitates the transfer of data from the source system to the S/4HANA system & monitors migration status & the migration project is always associated with "Transfer ID" & the transfer id is a unique identifier that facilitate the transfer of projects between different system of the landscape.Example: if you transfer the migration project from quality to the production system then project transfer id should be the same in both the system.

So in the below screenshot we are creating a new project Z_NEW_PROJECT with transfer id 006 and default view.

   

Press Create.

2).Migration Object: Once the migration project is created, we need to choose a migration object and the migration objects are predefined & provided by the SAP system. So we need to choose migration objects as per our requirement [The Business objects like Material, Customer, Cost Center, etc are the migration object now].

In below screenshot, the migration object available on a migration project :

   

Migration object comes with the following information:

• 1).Status: Object can be active - available for migration, deactivate - not available for migration & started - migration has started on this object.
• 2).Object name: It is the migration object name that is relevant to customer master / transactional data.
• 3).Documentation: Once we click on documentation it will open a new window where we can find all information on migration objects like required structure, fields, uses.
• 4).Dependent migration object: It shows a list of migration objects that must be loaded first / already present in the system.For example: before loading material master & profit center object data must be loaded / exist in the system.

For our example: if we select Material Migration Object & the following screens would appear -

   

So after selecting the migration object you need to execute the below steps:

• 1).Download Template - When we click on the download template for the first time, the system will copy the object template into a migration project and this template will provide a list of fields that should be filled for data transfer & the template is downloaded by default in Excel format. So if a .xml is not given then save the file with .xml explicitly. DO NOT change template field, type, length and always use paste ‘V’ option for copying data in the template.
• 2).Upload file - We can fill legacy data into the downloaded template and then can upload the.XML file in the SAP Data Migration Cockpit for migration. So more than one file can also be uploaded.
• 3).View and Edit - Once the file has uploaded, we can view data by clicking on the name of the file and if required we can edit data in the file by clicking on the edit button.
• 4).Activate - To take the file into the next step i.e. start transfer we need to select that file & click on the activate the button.
• 5).Deactivate - In case of multiple files, if the user doesn’t want to transfer some file then he can choose file and deactivate them. So only the file with active status will move for transfer.
• 6).Start Transfer - We can start data transfer for active files by clicking on the button ‘start transfer’.

In the below screen will appear after you start transferring.

    

These steps must be executed after starting the transfer of data:

• 1).Data Validation - Data stored in the staging area is checked against the mandatory field, type, length.
• 2).Value Conversion - Mapping rules can be defined between the source to the target system.For example, the country code ‘USA’ is set in the source system but in the target system, it should be mapped to ‘US’.
• 3).Simulation - Data stored in the staging area is processed by actual BAPIs but commit is not performed (after all it is simulation/test run). So here we can find warning and error messages.
• 4).Execution/Finish - In this step data is actually posted to the SAP HANA system using relevant BAPI and after executing all the above steps, press the FINISH button to commit changes to the database.

  

 

So after execution it shows status as follows:

   

We have successfully migrated our data into SAP S/4 HANA & we can leverage the same steps for other business objects [viz Business Partners, Cost Center, etc.,] migration & the template would be different but the process is the same.

Hope this help, Thank you everyone.