Overdeliveries in SAP WM Intermediate WM Movement Type
1. In the configuration of the mobility type at the WM level of the SAP WM module, there is a tag called Overdeliveries, as shown below:
Tick it, and when a removal scenario related to this type of movement occurs, the system will remove all the inventory in the corresponding storage bin, regardless of the number of removals this time.
Even if the Full stk rmvl reqmt act. flag is not checked in the configuration of the corresponding storage type. As shown above.
2, Material No. 806 is used for this presentation.
Its listing and delisting identifiers are both 005, which means that it will be delisted from 005 storage type or listed to storage type 005.
The current inventory data of the material in the 005 storage type is as follows:
Lot No. 0000000503 under Storage type 005 has a stock quantity of 99 EA.
3, Execute transaction code MIGO, movement type 201, issue to cost center, quantity is 1.
Save, the system automatically turns to the transaction code LT06 interface, press Enter directly, and enter the following interface,
Save directly, the system generates TO order 99, as shown below:
It can be seen that the quantity in TO is not 1 EA, but all the inventory (99 EA) in the storage bin FIX-001-02 under storage type 005 is removed from the shelves.
Query the inventory of the material again, and find that there are 98 EAs left in the temporary storage area 911, as shown below:
Generally speaking, the Overdeliveries option is not checked in the configuration of the WM-level movement type in the project practice. Even if it needs to be removed from the shelves, it is still set on the Storage Type.
Note: This article is based on the SAP S4/HANA 1909 system.
-over-
Written on 2022-4-4