Handling Unit Check
Use
This logic is executed when a handling unit (HU) first passes the automatic conveyor technique. The system checks and evaluates the HU and its relationship to warehouse orders (WOs) and warehouse tasks (WTs).
Prerequisites
You have made the Customizing settings for the material flow system (MFS) as described in Setting Up MFS for Case Conveyor Systems. In particular, you have ensured that a HU check action (function module /SCWM/MFSACT_CASE_SP) is called at the correct point for your telegram type.
Features
The following features are available:
-
Old MFS errors of HUs are deleted if the Delete Error checkbox is selected in Customizing for the communication point.
-
Telegram errors mapped to the internal process code Move to Clarification Bin (CRCL) and HU Not Identifiable (HUNO) are processed, passed to the HU and the HU is directed to the error location according to the case conveyor routing definition.
-
A potentially open WT to the current communication point for the HU is confirmed.
-
HU attributes (such as weight) are filled based on telegram data.
-
A telegram with the next destination of the HU is sent to the programmable logic controller (PLC) based on the case conveyor routing definition.
You can use the following Business Add-Ins (BAdIs) to implement additional logic:
-
BAdI: Handling Unit Identification Check
You can use this BAdI to check the HU identification provided in telegrams. If the HU is not known in SAP Extended Warehouse Management (SAP EWM) or is a duplicate, you can use BAdI method HUID_CHECK to handle this. You can find this BAdI in Customizing for Extended Warehouse Management under .
-
BAdI: Warehouse Task Check
You can use this BAdI to check the WTs for the HU and decide whether they should be confirmed or canceled. You can use BAdI method WT_CHECK to create a follow-up WT for putaway of the HU. You can find this BAdI in Customizing for Extended Warehouse Management under .
-
BAdI: Handling Unit Check
You can use this BAdI and BAdI method HU_CHECK to check the HU regarding dimensions and decide whether the HU should be updated. You can find this BAdI in Customizing for Extended Warehouse Management under .
-
BAdI: Destination Determination
You can use this BAdI and BAdI method DST_BIN to determine the destination data if a WT should be created. You can find this BAdI in Customizing for Extended Warehouse Management under .
The function module can send telegrams to the following logical destinations for the PLC:
-
Logical destination with the category ERROR
-
Activity area set in the method WT_CHECK of the BAdI Warehouse Task Check
-
Logical destination set in the method HU_CHECK of the BAdI Handling Unit Check
-
Logical destination set in the method DST_BIN of the BAdI Destination Determination
-
Activity area based on the destination storage bin of the created HU-WT
-
Logical destination with the category DEFAULT

