
SAP S/4HANA TOOL OF CHOICE FOR MIGRATION
A Ready-to-use solution tool is a Part of SAP S/4HANA Cloud and included in licenses - embedded data load tool which supports customer with new implementations.
The most adopted method of many customers has been migration of data using staging tables and when it comes to cloud always use the standard approach. These full fills all your needs of migration and when in need you can always use custom fields to be added in your data migration objects.
Select Migration Objects
Identify which migration objects are required and are relevant for identified scope items and business scenarios. This exercise is normally part of the F2S (Fit-to-Standard) workshops and all respective work streams can list required master data & open transactional data.
Note: First rule of data migration always migrate open, cleansed data from legacy. If there’s a requirement of historical data, it’s always preferred to take past 5 years data.
Get Data
Invest time performing Data Cleansing (de-duplication, address parsing…). Data to be migrated is usually extracted from one data source (also called legacy system). In less frequent cases data comes from more than one source systems. The method of extraction depends on the source system and depends upon the customer as well.
The data received should be in the format of data migration template from S/4 Hana system with changes with respect to each object.
Map, Transform, Simulate & Migrate
3. Select migration objects -click on button, to continue with next step click on “Review”.
4. Create Project – Confirm
5. Against each object, you want to perform data migration the system proposes the actions to be performed and can also download the template to populate the data.
Note: Remember, the objects have a hierarchy and are also dependent to each other. Always plan out the data migration objects in which sequence they must uploaded. Example: First master data and then transactional data or else in Master data first profit centres. G/L accounts and then material & BP master records as they have dependencies.
6. Populate the XML Template File with Data. Default size limit for each uploaded XML or ZIP file is 100 MB.
7. Upload the file in the cockpit against the respective object and prepare the file for staging tables. This means that the data from excel will be transferred to its respective tables in SAP from which it’ll be migrated.
8. Can specify value mappings and transform values from the source system to the target system. As well as use search help for target values provides existing values in the SAP S/4HANA target system.
9. The results of each step can be monitored via “Monitoring” and can identify the issues if there are any.
10. Next simulation is performed in which the new mapped values will be simulated by replacing the legacy values and shows the results of creation of the object. If there are no errors, we get to the migration part.
11. Click on migrate and data gets migrated into system. Once migrated into system, we can not undo the process as the number range gets consumed. (Rules are same irrespective of systems)
Statistics & Reports
The app “Data Migration Status” gives the detailed statistics on instance level i.e., for all the records which are uploaded are now available. We could filter the uploaded content and their status based on key statistics such as Company Code, Country etc. Along with that option of exporting the report, including statistics to Microsoft Excel files is also feasible for reporting purposes.
Hope this makes data migration in cloud easier for self-enablement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 | |
5 |