SAP Knowledge Base Article - Preview

3366476 - Movement type 311 E creates inconsistency in warehouse management

Symptom

  • 311 E / 309 E transfer posting from MIGO allows source and destination sales order number with different values resulting in inconsistencies in warehouse management (WM) for the data created from the transfer order (TO)
  • System allows to enter 2 different sales order values in MIGO transaction and does not prevent the delivery creation and TO creation/confirmation and then prevents the PGI making the stock inconsistent and the process is stuck
  • Using MIGO, a delivery for 311 E / 309 E can be created with different sales order numbers for source and destination. When the transfer order is created for the delivery then the data are taken over from the delivery. It means the destination quants are updated with the new sales order number from the delivery. When the delivery is then posted, because of the movement type, in the material document the destination sales order number is replaced with the source sales order number. As a result this creates an inconsistency in the warehouse


Read more...

Environment

  • Logistics Execution (LE)
  • SAP R/3
  • SAP R/3 Enterprise 4.7
  • SAP ERP Central Component
  • SAP ERP
  • SAP Enhancement package for SAP ERP
  • SAP Enhancement package for SAP ERP, version for SAP HANA

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

309 E, 311 E, M7484, OMJJ,  , KBA , LE-WM-GF-INC , Warehouse Data Inconsistencies , MM-IM-ST , Stock Transfer / Transfer Posting , 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.