Warehouse Task Confirmation for MFS Resources
Use
You can confirm warehouse tasks that move handling units (HUs) from resource pick points into automated high bay storage or from automated high bay storage to resource drop-off points.
Prerequisites
-
You have made the Customizing settings for the material flow system (MFS) (see Setting Up MFS for Case Conveyor Systems).
In particular, you have ensured that a warehouse task confirmation for the MFS resource (action function module /SCWM/MFSACT_WT_CONFIRM_RSRC) is called at the correct point for your telegram type.
-
You have maintained layout-oriented storage control (see Layout-Oriented Storage Control).
Features
-
Telegram errors, such as the destination bin is occupied or the source bin is empty, are processed using function module /SCWM/MFS_REQ_EXCEPTION.
For more information about exceptions, see Exception Handling.
-
If the HU cannot be locked, the incoming telegram can be set to a retry state (see Reprocessing of Incoming Telegrams).
-
If there is no telegram error and no locking issue, the warehouse task is confirmed.
-
Optionally, a telegram can be sent to the next communication point about movements to resource drop-off points.
This is only done when an appropriate case conveyor routing entry is maintained (see Routing for Case Conveyor Systems).
You can use BAdI: Determination of Handling Units Used in Telegrams to inform standard coding about HUs and their destination location that should be processed based on the telegram. In the standard setup the default implementation for this BAdI is class /SCWM/CL_EI_MFS_HU_DET_TELE. The default implementation returns one HU and its destination location out of the standard telegram structure. For more information, see Customizing for Extended Warehouse Management under .

