Objective
The purpose of this blog is to give you some insights about the required configuration and manual steps if you change the ERP system connected to EWM.
Business Case
If you use a Decentralized EWM system, the database should be connected to an ERP system. It can be an SAP or non-SAP system.
Recently, I worked on a migration project. We changed the ERP system from SAP PXX to SAP PYY.
I mentioned below the required configuration points and manual steps for this case.
/!\ There are some Basis setup like the queues which should be done. I will mention only the functional settings.
EWM Configuration
Table /SAPAPO/V_SYSLST
You define a new BSG for the new ERP system PYY
- Assign logical system to BSG
Table /SAPAPO/V_BSGSET
Assign the ERP and EWM systems to the new BSG
- Update recipient depedent control of processes
Table /SCWM/TCTRLPROCS
- Update the warehouse number mapping
Table /SCWM/TMAPWHNUM
Table /SCWM/TMAPROUTE
- Update storage location mapping
/SCWM/V_TMAPSTLO
SPRO > Extended Warehouse Management > Interfaces > ERP Integration > Delivery Processing
Check and update the delivery mapping if you are using the ERP system as an entry
For us, the ERP system is defined for the delivery types and item mapping
SPRO > Extended Warehouse Management > Interfaces > ERP Integration > Production
Check and update the production mapping if you are using the ERP system as an entry
SPRO > Extended Warehouse Management > Interfaces > ERP Integration > Transportation
Check and update the transportation mapping if you are using the ERP system as an entry
ERP configuration
T-code = /SPE/OL19
Run the distribution model generation for each ERP warehouse number
EWM Manual steps
In the ship-to tables, the system stores the source ERP system.
Field = Responsible institution --> It should be updated by the new ERP system
Transaction MASS
Run it for all BP
Transaction WE20
Define the inbound and outbound Idocs for the new ERP system
You have to create also the new receiving port
- Mass change BSG for products and locations
As for the BP, the BSG is stored in products (/sapapo/matmap) and location table (/sapapo/locmap)
You have to replace it by the new BSG. For this, there is a program which can be used to mass update it.
You have to implement it by the OSS note 213109
Program = Z_CHANGE_LOGQS
ERP Manual steps
Transaction WE20
Create the EWM partner profile in the new ERP system
Batch class and characteristics
We have the class and char numbers in EWM and ERP.
In EWM, the system stores the class and char number coming from the ERP (like the BSG for products and BP).
--> We have to
- CIF the class and char
- Update the class and char in EWM table with the new class and numbers of the new ERP system
- Check the EWM class table
- Check the char EWM table
- Initial CIF of batches
Transaction CFM1 and CFM2
- Update the EWM class and char table
Program /SAPAPO/CHECK_INCON_TCL_CL_CHR
/!\ Normally this program should update the class and char EWM tables. However, when we used it, it updated only the class table.
EWM class table = TCL_CLINT_IDENT
ERP class table = KLAH
KLAH-CLINT should be equal to TCL_CLINT_IDENT-CLINT
EWM char table = TCL_ATINN_IDENT
ERP class table = CABN
CABN-CLINT should be equal to TCL_ATINN_IDENT-CLINT
/!\ In our case, I updated the table TCL_ATINN_IDENT manually via SE16 in debug mode.
SAP recommended to run the program RIMODINI for the first CIF of batches
Conclusion
I hope this can help other consultant in case they are working on such project.
Don’t hesitate to comment this blog.
Cheers
Foued B.
You can follow my profile for other EWM topics