SAP S/4HANA Data Migration: Migrate your data using SAP’s Data Migration Cockpit.
This blog is the culmination of SAP documentation and experiences I’ve gained implementing SAP S/4HANA single-tenant and multi-tenant systems. While the approach and strategy migrating to a single or multi-tenant may be different, the one thing that is constant is the ability to use SAP’s Data Migration Cockpit. The below information is my attempt to support the SAP user community by providing simple steps that empower a user to hit the ground running when implementing SAP S/4HANA.
For more detailed information pertaining to this topic. Please refer to the links at the end of this blog. Enjoy the blog!
Migrate your data using SAP’s Data Migration Cockpit
Migration Project– The first step is to create or open migration project in the SAP Data Migration Cockpit. The migration project facilitates the transfer of data from the source system to the S/4HANA system and monitors migration status.
The migration project is always associated with ‘Transfer ID’. This transfer id is a unique identifier that facilitates the transfer of projects between different systems of the landscape. For example, if we transfer the migration project from quality to production system then project transfer id should be the same in both systems.
In the below screenshot, we are creating a new project Z_NEW_PROJECT with transfer id 006 and default view.
Migration Object– Once the migration project is created, we need to choose a migration object. Migration Objects are predefined and provided by the SAP system. We need to choose migration objects as per our requirement (The Business objects like Material, Customer, Cost Center, etc are the migration object now).
Below is a screenshot of the migration object available on a migration project.
Migration object comes with the following information:
- Status– Object can be active – available for migration, deactivate – not available for migration and started – migration has started on this object.
- Object name– It is the migration object name that is relevant to customer master or transactional data.
- 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.
- Dependent migration object– It shows a list of migration objects that must be loaded first or already present in the system. For example, before loading material master, profit center object data must be loaded or exist in the system.
For our example, we select Material Migration Object and the following screens would appear:
After selecting the migration object we need to execute the below steps.
- Download Template– When we click on the download template for the first time, the system will copy the object template into a migration project. This template will provide a list of fields that should be filled for data transfer. The template is downloaded by default in Excel format. If .xml is not given then save the file with .xml explicitly. DO NOT change template fields, type, length and always use paste ‘V’ option for copying data in the template.
- 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. More than one file can also be uploaded.
- 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.
- Activate– To take the file into the next step i.e. start transfer we need to select that file and click on the activate the button.
- Deactivate– In case of multiple files, if the user doesn’t want to transfer some file then he can choose file and deactivate them. Only the file with active status will move for transfer.
- Start Transfer– We can start data transfer for active files by clicking on the button ‘start transfer’.
The below screen will appear after you start transferring.
Following steps must be executed after starting the transfer of data:
- Data Validation– Data stored in the staging area is checked against the mandatory field, type, length.
- 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’.
- Simulation– Data stored in the staging area is processed by actual BAPIs but commit is not performed (after all it is simulation/test run). Here we can find warning and error messages.
- Execution/Finish– In this step data is actually posted to the SAP HANA system using relevant BAPI.
After executing all the above steps, press the FINISH button to commit changes to the database.
After execution it shows status as follows:
You have successfully migrated your data into SAP S/4HANA. You can leverage the same steps for other business objects (viz Business Partners, Cost Center, etc) migration. The templates would be different, but the process is the same.
Data Migration Cockpit Links:
For more information about SAP Data Management and Landscape Transformation (DMLT) see this page https://www.sap.com/services/implementation/data-mgmt-landscape-transformation.html or read the solution brief and the SAPPI Success Story. You can contact the global SAP DMLT team by email email@example.com. They provides services for Selective Data Transition, New Implementation and System Conversion that can also be delivered remotely.