Aisle Decision Points
Use
You can use aisle decision points to determine rough destination bins for putaway tasks at a given communication point of the conveyor technique. The system creates a handling unit (HU) move entry containing the rough destination bin for the putaway task based on the following:
-
Current communication point
-
HU data
-
Stock data
-
Equipment status
For more information, see Putaway Strategy.
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 action function module /SCWM/MFSACT_CASE_AISLE_DET is called for an aisle decision point at the correct point for your telegram type.
-
You have maintained accessible aisles per communication point (see Aisles and Levels Accessible by Communication Point).
-
You have maintained accessible aisles per resource (see Aisles and Levels Accessible by Resource).
Features
-
The system processes telegram errors mapped to internal process codes Move to Clarification Bin (CRCL) and HU Not Identifiable (HUNO) and passes the telegram errors to the HU.
The system then directs the HU to the error location according to the case conveyor routing definition.
-
The system routes HUs according to the following scenarios:
-
If there is an open warehouse task for the HU, the routing decision action (see Routing Decision) is executed.
-
If the HU is empty and a logical destination for the category EMPTY has been maintained for the current communication point, the routing decision action (see Routing Decision) is executed.
-
If there is no open warehouse task for the HU or the HU is occupied, the system determines a rough destination bin. The HU is routed according to the activity area determined by the rough destination bin determination.
If the system cannot determine a rough destination bin due to a temporary issue (for example, equipment is blocked), the system can set the incoming telegram to a retry state (see Reprocessing of Incoming Telegrams). In this situation, the HU is posted to the current communication point. If the system cannot determine a destination bin at all, the system can send the HU to a logical destination with the category ERROR.
-
-
Function module /SCWM/MFSACT_CASE_AISLE_DET can send telegrams to the following logical destinations for the programmable logic controller (PLC):
-
Logical destination with the category ERROR
-
Activity area based on the destination storage bin of an existing HU-WT
-
Activity area determined based on rough destination bin determination
-
Logical destination with the category DEFAULT
-
You can use BAdI: Rough Destination Bin Determination to implement an alternative solution for determining a rough destination bin. In the standard setup there is a default implementation for this BAdI (class /SCWM/CL_EI_MFS_ACT_CASE_RBD). To implement your own logic you can use your own class that inherits from class /SCWM/CL_CORE_PUTSTRA. For your own logic you can redefine certain methods to follow your needs. For more information, see Customizing for Extended Warehouse Management under .

