SAP S/4HANA Migration Cockpit provides three migration approaches, namely:
My blog explains my experiences with the third method of direct data transfer using "Migrate Your Data" Fiori App and the various stages executed to perform migration from Classical EWM 9.5 to Decentral EWM on S/4 HANA 1909.
In this blog, I have taken the example of “Storage Bin Migration” to explain various steps involved while running “Migrate Your Data” Fiori App. This migration technique posts data to the target system using standard application programming interfaces (APIs).
In this third Method of direct data transfer, you can access the source system i.e. Classical EWM system via RFC connection. It directly transfers the data from SAP ERP source system to target SAP S/4HANA system. Note that for Classical SAP EWM to Decentralized EWM, the lowest supported EWM release is EWM 5.1 (SAP Net Weaver 7.0).
Following are the main prerequisites that needs to be satisfied for using Direct Transfer Method:
To carry out the storage bin migration, assign authorization or roles to the user for the following objects:
Run /ui2/flp from the target EWM system on S/4 HANA 1909 and access the installed Fiori App.
To proceed next, one needs to first create the new migration project in the “Migrate Your Data” app, by filling name of the project and by selecting the migration scenario as “SAP EWM to Decentralized WM on S/4 HANA 1909”. RFC connection to the source system needs to be also selected while creating the project. Provide the warehouse number for which the storage bin migration should be executed.
Example shown in my blog is for the “Storage Bin Migration” project, as created below.
The migration project will typically offer following objects for the data migration:
Dependencies of one data object to another should be taken care by making sure predecessor object is selected first for migration.
Selection Criteria involves Storage Bin data, which is automatically selected for the storage bins assigned to the migration-relevant warehouse numbers.
Following is in the scope of storage bin data selection:
Following is in out of scope of the storage bin data selection:
The migration of Warehouse Stock will create all of the above.
When the action “Select Data” is performed, only those storage bins will be selected for bins would have the stock (note: Empty bins would get deleted by program before the selection of data). As shown below in the migration project created for storage bin migration, 265 instances were selected by the program.
Before you proceed with the “Simulate” action, it is mandatory to confirm "Mapping Tasks" created automatically by the migration project.
As shown in below results, 7 mapping tasks were automatically generated by the migration project for storage bin data migration. The mapping tasks requires one to confirm the mapping of values between legacy storage bin data values with target system storage bin data values. This confirmed mapping is further used in the execution of simulation run and also for the final migration run steps.
For storage bin migration, the typical mapping tasks between source EWM and target EWM system involves, mappings for storage section, warehouse number, fire containment section (if any), storage types, storage bin types, bin access type and storage bin numbers itself.
Following shows the example of mapping tasks and values created for storage section.
After all the mapping tasks between source and target EWM systems are completed, the simulation run can be executed by selecting next action “Simulate”. One can select All instances of the data in order to perform the simulation run.
Following picture shows that simulation run for all selected 265 data instances has been successful and none has gone into the error.
After selecting the next action “Migrate”, one can start the final migration run for all the previous selected & simulated data instances, as shown in the below picture.
Once the “Migrate” action is over, the error/successful/not started status would be shown by the Fiori App. In our example, it shows that all 265 storage bins were successfully migrated.
One can also perform the step of "Validate" the migrated data in the target system upon the migration run completion using below options:
Using “Migrate Your Data” Fiori App that leverages upon the direct transfer method, the data migration run is executed successfully for storage bins, from Classical EWM to new EWM system on S/4 HANA 1909.
- Transfer data using files,
- Transfer data using staging tables (as of 1709 FPS02) &
- Transfer data directly from SAP System (new with SAP S/4HANA 1909)
My blog explains my experiences with the third method of direct data transfer using "Migrate Your Data" Fiori App and the various stages executed to perform migration from Classical EWM 9.5 to Decentral EWM on S/4 HANA 1909.
In this blog, I have taken the example of “Storage Bin Migration” to explain various steps involved while running “Migrate Your Data” Fiori App. This migration technique posts data to the target system using standard application programming interfaces (APIs).
In this third Method of direct data transfer, you can access the source system i.e. Classical EWM system via RFC connection. It directly transfers the data from SAP ERP source system to target SAP S/4HANA system. Note that for Classical SAP EWM to Decentralized EWM, the lowest supported EWM release is EWM 5.1 (SAP Net Weaver 7.0).
Following are the main prerequisites that needs to be satisfied for using Direct Transfer Method:
- In the source system, the Software component: DMIS_2011 SP17 or higher should installed with application component: CA-DT-MIG-EWM (Migration Cockpit - Direct Access - EWM)
- In target system, activate "Migrate Your Data" Fiori App (note: 2815704) for SAP S/4HANA On-Premise Edition 1909
- RFC connection from EWM source to SAP S/4HANA EWM target system
- Ensure availability of required authorizations. The required composite role in the SAP source system is SAP_DMIS_OBT_REMOTE. For the SAP S/4HANA target system, a user with the role SAP_DMIS_OBT_MASTER is required. This user must also have the role SAP_BR_CONFIG_EXPERT_DATA_MIG for the front-end server. To use the migration object modeler (transaction LTMOM), role SAP_CA_DMC_MC_DEVELOPER is required in the SAP S/4HANA system.
To carry out the storage bin migration, assign authorization or roles to the user for the following objects:
- /SCWM/MIG (EWM Migration Reports)
- /SCWM/LG (EWM Storage Bin)
- C_LIME_DOC (LIME Document Check)
- C_LIME_LOC (LIME Location)
- C_LIME_HU (LIME Handling Unit)
Step 1: Access “Migrate Your Data” app from the target EWM system
Run /ui2/flp from the target EWM system on S/4 HANA 1909 and access the installed Fiori App.
Step 2: Establish Migration Project
To proceed next, one needs to first create the new migration project in the “Migrate Your Data” app, by filling name of the project and by selecting the migration scenario as “SAP EWM to Decentralized WM on S/4 HANA 1909”. RFC connection to the source system needs to be also selected while creating the project. Provide the warehouse number for which the storage bin migration should be executed.
Example shown in my blog is for the “Storage Bin Migration” project, as created below.
The migration project will typically offer following objects for the data migration:
- Warehouse Fixed Bin Assignments - This has warehouse storage bin as predecessor object
- Warehouse Product -
- Warehouse Stock - This has warehouse storage bin as predecessor object
- Warehouse Storage Bin
- Warehouse Storage Bin Sorting- This has warehouse storage bin as predecessor object
Dependencies of one data object to another should be taken care by making sure predecessor object is selected first for migration.
Step 3: Execute Select Data
Selection Criteria involves Storage Bin data, which is automatically selected for the storage bins assigned to the migration-relevant warehouse numbers.
Following is in the scope of storage bin data selection:
- General storage bin data, such as aisle, stack, level, and coordinates
- Status data, such as putaway and stock removal block
- Data related to physical inventory, such as physical inventory type and date of last inventory
- Statistics-related data, such as date and time of last movement or date and time of last bin clearing
Following is in out of scope of the storage bin data selection:
- Maximum number of handling units on bin
- Actual number of handling units on bin
The migration of Warehouse Stock will create all of the above.
- You can migrate Warehouse Storage Bins for only one warehouse at a time.
When the action “Select Data” is performed, only those storage bins will be selected for bins would have the stock (note: Empty bins would get deleted by program before the selection of data). As shown below in the migration project created for storage bin migration, 265 instances were selected by the program.
Step 4: Confirm Mapping Tasks
Before you proceed with the “Simulate” action, it is mandatory to confirm "Mapping Tasks" created automatically by the migration project.
As shown in below results, 7 mapping tasks were automatically generated by the migration project for storage bin data migration. The mapping tasks requires one to confirm the mapping of values between legacy storage bin data values with target system storage bin data values. This confirmed mapping is further used in the execution of simulation run and also for the final migration run steps.
For storage bin migration, the typical mapping tasks between source EWM and target EWM system involves, mappings for storage section, warehouse number, fire containment section (if any), storage types, storage bin types, bin access type and storage bin numbers itself.
Following shows the example of mapping tasks and values created for storage section.
Step 5: Run Simulation
After all the mapping tasks between source and target EWM systems are completed, the simulation run can be executed by selecting next action “Simulate”. One can select All instances of the data in order to perform the simulation run.
Following picture shows that simulation run for all selected 265 data instances has been successful and none has gone into the error.
Step 6: Execute Migration Run
After selecting the next action “Migrate”, one can start the final migration run for all the previous selected & simulated data instances, as shown in the below picture.
Once the “Migrate” action is over, the error/successful/not started status would be shown by the Fiori App. In our example, it shows that all 265 storage bins were successfully migrated.
One can also perform the step of "Validate" the migrated data in the target system upon the migration run completion using below options:
- Transaction /SCWM/LS03 Display Storage Bins
- Transaction /SCWM/MON Warehouse Monitor, node: Stock and Bin -> Storage Bin
- Go to Table /SCWM/LAGP and check the number of entries migrated to the target EWM system on S/4 HANA 1909 for a warehouse number in the scope.
Conclusion
Using “Migrate Your Data” Fiori App that leverages upon the direct transfer method, the data migration run is executed successfully for storage bins, from Classical EWM to new EWM system on S/4 HANA 1909.
- SAP Managed Tags:
5 Comments
