/SCWM/CL_EI_MFS_ACT_WT_CONF - Equal Distribution of Products in Aisles of High Rack

rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Functionality

This BAdI example implementation is called during confirmation of a WT connected to the material flowsystem (MFS). It tries to redetermine a valid destination storage bin from a MFS standpoint for theinactive WT for the HU that is currently being moved. For this decision, the BAdI example implementation takes the following into account:

• It is only executed if the current communication point has a certain communication point type. This communication point type has to be identical to the value of the constant GC_CP_TYPE_BADI.

• It determines the aisles with stock and the aisles without stock in the destination storage type.First, it attempts to put away the goods in an aisle without stock. Only if no accessible aisle withoutstock is found, does it take aisles with stock into consideration. By doing this, the BAdI example implementation tries to achieve a basic equal distribution of the product in the aisles.

• For each aisle, the status of the MFS resource and communication channel are checked. The aisle is only considered if there is no exception and the communication channel is synchronized.

Relationships

Example

Notes

Please note:

• The BAdI example implementation only considers the stock in the aisles if the WT is a homogenous HU-WT.

• As a prerequisite, all storage bins of the possible destination storage types must have an activity area, a storage bin sorting and an aisle assigned.

• We recommend that you use cross-line stock putaway for storage bin sorting of the destination storage type.

• To determine the aisles with and without stock, the BAdI example implementation performs extensivechecks. In a customer implementation, there may be less complex ways to determine the aisles for storagebins, which could lead to a better performance. For example, there may be a naming convention for storagebins to include the aisle in the storage bin name. The aisle could then simply be extracted from the storage bin name.

• During determination of the stock situation, you must check whether additional stock attributes (such as batches) are to be taken into account.

• The BAdI example implementation does not consider the amount of stock or HUs spread across the aisles.

• To determine the resource and communication channel responsible for an aisle, the BAdI example implementationtries to determine the correct queue. This queue determination may have to be adapted, depending on your configuration.

• During queue determination in the BAdI example implementation, the BAdI for queue determination is not executed.

• If the BAdI example implementation is not able to find a valid storage bin, the destination storage bin of the inactive WT is not changed at all.

Further information

ROGBILLS - Synchronize billing plans   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.


Length: 3117 Date: 20120526 Time: 073607     triton ( 147 ms )