With the release of decentral SAP EWM on SAP S/4HANA Platform, the migration to SAP EWM on SAP S/4HANA has become a top priority for existing SAP EWM customers. However, the move to SAP EWM on SAP S/4HANA can be quite challenging as unlike an upgrade this will be a greenfield migration. The two main challenges are:
- Migration of custom code
- Handling of documents which cannot be closed during the cutover to SAP S/4HANA (transactional documents cannot be migrated due to changed GUIDs for products and business partners)
In this blog post, I will address the 1st challenge and provide 10 steps for setting up the SAP S/4HANA decentral EWM system based on the legacy SAP EWM system.
Setting up the SAP S/4HANA decentral EWM system
- Setup of SAP S/4HANA system for decentral SAP EWM deployment (Note 2840129 contains a How-to-guide)
- RFC Connection to SAP ERP and Legacy SAP EWM systems
- Setup ALE distribution model from SAP ERP to SAP S/4HANA decentral EWM System as described in the setup guide
- Migration of custom code and custom DDIC objects
- Transport/Import Custom code from legacy SAP EWM system (ABAP Transport)
- Run ATC checks for SAP HANA readiness
- Resolve conflicts due to changed Standard Routines
- Adapt code which uses obsolete or no more supported functionalities (see below EWM Simplification List)
- Migration of common customizing from SAP ERP System
- Currencies, Units of Measure, Countries, Regions, Factory Calendar, etc.
- Material Master related customizing like Material Types etc.
- Number ranges for Business Partners, Customers and Vendors (these should be as external in SAP S/4HANA EWM System)
- Incoterms, Shipping Conditions, HU types etc. (see below EWM Simplification List)
- Migration of customizing from legacy SAP EWM System
- Cross Warehouse customizing settings (SCM Basis)
- Warehouse specific settings (Extended Warehouse Management)
- Initial Data Transfer of Master Data from SAP ERP to SAP S/4HANA EWM System
- Material
- Batches
- Customers
- Vendors
- Quality Inspection Rules
- HAZMAT Master Data
- Migrate SCM Routes, Packaging Specifications from Legacy SAP EWM System (Distribution Model)
- Migrate warehouse specific master data from Legacy SAP EWM System
- SCU
- Bins, Bin Sorting & Fixed Bin Assignments (SAP provides content in Data Migration Cockpit)
- Warehouse Products (SAP provides content in Data Migration Cockpit)
- QIE Setup, QIE Inspection Rules
- Production Integration, Production Control Cycles
- Resources
- Work Center Settings
- Physical Inventory
- MFS Settings
- Shipping & Receiving Settings
- Wave Templates and Condition for determination
- PPF Actions Scheduling Conditions
- Assign User to Exception Code Profile (/SCWM/EXCUSERID)
- Assignments: Warehouse Numbers/ business Partners (/SCWM/LGNP)
- Assign Warehouse Number / Party Authorized to Custom ID (/SCWM/GTS_MAPWH)
- Maintain Goods Movement bin Determination (/SCWM/GMBIN_DET)
- Determine Algorithm Profiles for Cartonization Planning (/SCWM/CAPPDET)
- Assign Packaging Materials to Products
- Specify Packaging Materials for Collective HUs (/SCWM/PMATCOHU)
- Set Up Control Parameters for Warehouse Order Creation (/SCWM/WOLOG)
- Warehouse Billing: Settings for SNAPSHOTS (/SCWM/WB_SNAP_SET)
- Migrate Warehouse independent settings
- Configure Log for SAP ERP Messages ( /SCWM/ERPLOG)
- Set Default Owner of Transportation Units and Vehicles (/SCWM/MTR_DO)
- Link Between Packaging Material (TU) and Means of Transport (/SCWM/PM_MTR)
- Set Up Printer and Form Determination (/SCWM/SR_PRINT)
- Migrate Printer settings, Users and User Parameters
- Migrate custom Z-Tables (non transactional data only)
EWM Simplification List (Refactoring Needed)
| Sub Area | Topic | Change Type | Long Description |
| Master Data | Business Partners | Interface | The following BAdIs must be replaced by equivalent IDOC processing: 1. /SAPAPO/CIF_BSG_BP 2. /SAPAPO/CIF_ENHANCE_BP 3./SAPAPO/CIF_ENHANCE_ERRHDL 4.SMOD_APOCF038 |
| DB design |
The DB table BUT0ID (additional identifiers) is NOT used in SAP S/4HANA stack. In EWM on N/W stack IDTYPE CRM010 etc. were used for storing external keys of customer/vendor etc. In SAP S/4HANA stack the CVI link tables assign a system internal customer/vendor to BP. Optionally there can be an UKMS data of assignment of external KUNNR/LIFNR of remote SAP ERP system (UKMS only available if BP is distributed with DRF and not using IDOCs DEBMAS/CREMAS, see latest version of integration guide forSAP S/4HANA 1909 decentral EWM) Any custom code using the old CRM010 BUT0ID logic will no more work. |
||
| DB design |
Entitled BP assignment to a plant in EWM on N/W stack is done with DB BUT0ID IDTYPE ‘CRM011’. Because DB table BUT0ID is no more used in SAP S/4HANA stack, a new dedicated DB table /SCWM/TMAPPLANT is used (Application View /SCWM/VTMAPPLANT). Note: The entries are not transportable but shown in the IMG tree and not in the SAP reference menu tree) to assign an Entitled to a plant. Any custom code using the old CRM011 BUT0ID logic will no more work. |
||
| Products | Interface | The following BAdIs must be replaced by equivalent IDOC processing: 1. /SAPAPO/DM_MATLOC 2. SMOD_APOCF005 3. /SAPAPO/CIF_ENHANCE_ERRHDLNote: Automatic Activation of Product Warehouse view using the BADI SMOD_APOCF005 is no longer possible. (mass creation possible in Warehouse Monitor: Product Master Data à Warehouse Attributes) |
|
| DB design |
The following DB tables are replaced by standard Material Master DB tables like MARA, MARC, MARD, MARM, etc. (any custom extensions made need to be adapted accordingly): 1. /SAPAPO/MATEXEC 2. /SAPAPO/MATLOC 3. /SAPAPO/MATPACK 4. /SAPAPO/MATGROUP 5. /SAPAPO/MATTXT
All the above Product master data tables and the /SAPAPO/MATKEY are only read-only in SAP S/4HANA. Any custom code making an insert or update on the above tables will cause a dump. (CDS redirect proxy to MARA etc. are in place in SAP S/4HANA for the above DB tables). Changes made to below DB tables have no impact: 1. /SAPAPO/MATLWH |
||
| Batches | Interface |
The following BADIs must be replaced by equivalent IDOC processing: 1. /SAPAPO/CIF_ENHANCE_BATCH 2. /SAPAPO/CIF_ENHANCE_ERRHDL |
|
| DB design | The custom extensions made to DB table /SAPAPO/VERSKEY for storing custom data, needs to be remapped to MCHA and MCHB tables. | ||
| Functional restriction |
The DB table to control local creation of batches i.e. /SCWM/TBATCHUPD does not exist anymore. Any custom code accessing these DB tables must be also adjusted. Note: The creation of local batches by using the batch master transaction/apps is not supported as the batches are not replicated to the connected SAP ERP system. |
||
| Design |
In SAP S/4HANA it is mandatory to provide the parameter “entitled to dispose” when reading batch master data |
||
| Classes and Character- istics | Interface | The following BADIs must be replaced by equivalent IDOC processing:
In SAP S/4HANA stack class types 22/23 are used (instead of class types 220/230 used in EWM on N/W stack) |
|
| Customizing | Catch Weight | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables:
Any custom code accessing these DB tables must be also adjusted. |
| Handling Units | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCWM/THUTYP (THUTYP)2. /SCWM/THUTYPT (THUTYPT)Any custom code accessing these DB tables must be also adjusted. |
|
| Whse. Storage Condition | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCMB/TWHSTC (TWHSTC)2. /SCMB/TWHSTCT (TWHSTCT)Any custom code accessing these DB tables must be also adjusted. |
|
| Quality Inspection | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCWM/TQGRP (TQGRP) 2. /SCWM/TQGRPT (TQGRPT)Any custom code accessing these DB tables must be also adjusted. |
|
| Serial Number | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCWM/TSERIAL (TSERIAL) 2./SCWM/TSERIALT (TSERIALT)Any custom code accessing these DB tables must be also adjusted. |
|
| Handling Indicator | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: /SCMB/THNDLCD (THNDLCD) /SCMB/THNDLCDT (THNDLCDT) Any custom code accessing these DB tables must be also adjusted. |
|
| Delivery Priority | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCDL/TDLVPRIO (TPRIO) 2./SCDL/TDLVPRIOT (TPRIT)Any custom code accessing these DB tables must be also adjusted. |
|
| Shipping Conditions | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: /SCDL/TSRVLVL (TVSB) /SCDL/TSRVLVLT (TVSBT) Any custom code accessing these DB tables must be also adjusted. |
|
| Incoterms | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCMB/TSINC (TINC) 2. /SCMB/TSINCT (TINCT)#Any custom code accessing these DB tables must be also adjusted. |
|
| Trans. Group | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SAPAPO/TTGR (TTGR) 2. /SAPAPO/TTGR_TXT (TTGRT)Any custom code accessing these DB tables must be also adjusted. |
|
| Packing Data | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCWM/TPACKGR (TVEGR) 2. /SCWM/TPACKGRT (TVEGRT) Any custom code accessing these DB tables must be also adjusted. Note: Packing Mat. Types and mapping to Packing Groups are unchanged |
|
| Whse. Material Group | DB design | The following tables are no longer used. The data needs to mapped to the SAP S/4HANA tables: 1. /SCMB/TWHMATGR (TWHMATGR) 2. /SCMB/TWHMATGRT (TWHMATGRT) Any custom code accessing these DB tables must be also adjusted. |
|
| ERP Version Control | Function Restriction | DB Table /SCWM/TCTRLPROCS: If in the N/W stack, the contents of this table have the field ERPRELEASE “600”, “500”, “470” or “46C” this is no more allowed in SAP S/4HANA stack. | |
| Comm, to ERP | Functional Restriction | SAP S/4HANA decentral EWM does not support IDOC based Delivery/GM interface. Thus, the setting QTYPE (Queue Type) = “N” (No Queue) in /SCWM/TWMEQUEUE is NOT allowed. | |
| Quality Inspection Engine | Functional Restriction | Preliminary inbound delivery inspections (IOT 1) is not supported in SAP S/4HANA decentral EWM. Hence if the DB table /SCWM/QIOTWM has entries with IOT = ‘1’ this will not work, and the processes have to be adapted. |
|
| Shipping & Receiving | Freight Order Mgmt. | Functional Restriction | The following BAdIs cannot be used: 1. /SCWM/MAP_HU_SHP_SAP 2. /SCWM/MAP_DLV_SHP All FOM functionalities used need to be mapped to basic/advanced TM |
| Add-On | AR Warehouse Picker App | The Add-On “SAP AR Warehouse Picker 1.0 Add-On SPxx” (Add-on Software component NWMQC01) is no more supported in SAP S/4HANA. |
Conclusion:
The above steps are not a comprehensive list; however, they provide a good guidance for customers/partners/consultants intending to start an SAP EWM migration project. The migration is not simple, yet undeniably achievable – we have already a few customers who have migrated to SAP S/4HANA EWM (both decentral and embedded).
All the best and I wish you all success in the your project.
Original Article:
https://blogs.sap.com/2020/06/18/10-steps-for-migrating-to-sap-ewm-on-sap-s-4hana-platform/