In the preceding figure, a product pallet is to be moved from storage area A to storage bin Z. But in the layout-oriented storage control table for the movement from A to Z the intermediate point B is defined. That means that the WT from A to Z is created in an inactive state, and that an additional WT from A to B is created.
When the movement from A to B is confirmed, the system changes the source location for the inactive WT, which is changed to B. The system checks if this movement is possible and if the WT can be activated. But as the LOSC table defines that this movement requires the intermediate point C, the WT from B to Z continues to be inactive and a new, active WT is created for the movement from B to C.
This process continues until the system finds no intermediate point for the inactive warehouse task. Then the WT is activated, a warehouse order creation rule is determined, and it can be processed.
Note
"Intermediate points" in the text above can be separate storage types or just storage bins in the same storage type.
As LOSC requires the use of HUs, this can give a confusing picture in a picking process. When picking a full HU, LOSC is visible from the beginning. However, in case of a partial pick, the WT from the source bin has no HU and therefore LOSC is not triggered. There is no inactive WT and not WT to the intermediate storage type.
LOSC is then triggered when confirming the WT with a pick-HU. The destination bin for the pick WT is dynamically changed, and the next WT is created with the confirmation to the intermediate bin. This means that LOSC in such a scenario is only possible when working with mobile devices. A confirmation with the desktop app or in the Warehouse Management Monitor would not use LOSC.