Symptom
In a transfer posting scenario where goods movement is replicated from EWM to ERP using a movement type (eg. 303), the receiving storage location field (MSEG-UMLGO) remains unfilled. However, in direct Inventory Management postings with the same movement type, this field is populated.
Read more...
Environment
- SAP S/4HANA
- SAP ERP Central Component (ECC)
- SAP Service Parts Management (LO-SPM)
- Logistics Execution (LE)
- SAP Extended Warehouse Management (SCM-EWM)
Product
SAP ERP Central Component 6.0 ; SAP Extended Warehouse Management 5.1 ; SAP Extended Warehouse Management 7.0 ; SAP Extended Warehouse Management 9.0 ; SAP Extended Warehouse Management 9.1 ; SAP Extended Warehouse Management 9.2 ; SAP Extended Warehouse Management 9.3 ; SAP Extended Warehouse Management 9.4 ; SAP Extended Warehouse Management 9.5 ; SAP S/4HANA 1610 ; SAP S/4HANA 1709 ; SAP S/4HANA 1809 ; SAP S/4HANA 1909 ; SAP S/4HANA 2020 ; SAP S/4HANA 2021 ; SAP S/4HANA 2022 ; SAP S/4HANA 2023 ; SAP S/4HANA, on-premise edition 1511 ; SAP enhancement package 1 for SAP Extended Warehouse Management 7.0 ; SAP enhancement package 2 for SAP Extended Warehouse Management 7.0
Keywords
MSEG-UMLGO, one step, stock transfer, IMSEG, storage location, sloc, IM, MM , KBA , LO-SPM-INB , Inbound Process , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview