/SCWM/CL_EI_CORE_RMS_DETERMINE - MFS EI to Consider Equipment State during Stock Removal

CPI1466 during Backup   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Functionality

This BAdI example implementation is called during stock removal WT creation. As input, it receives aset of possible source stock that has been determined by the stock removal strategies in advance. Ittries to determine valid source storage bins from a material flow system (MFS) standpoint. For this decision, the BAdI example implementation takes the following into account:

• It is only executed if the source storage type has the storage type role AutomaticWarehouse (Controlled by MFS), the caller of the BAdI is internal WT processing, and the original WT is processed (not routing relevant).

• It determines the aisles for the possible source stock.

• 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:

• 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.

• To determine the aisles for the source 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.

• 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.

• To be able to determine the queue, the BAdI example implementation tries to determine the firststep based on the layout-oriented storage control. This determination must also be verified in a customerscenario. If the destination of the WT is not fixed at the execution of the BAdI, the HU type or homogeneous HU movements must be taken into account, the determination has to be adapted.

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

• The stock removal strategy may determine that one of the storage bins returned by this BAdI example implementation is not valid.

• The BAdI example implementation may be called multiple times for a position based on the available stock situation for the product and quantity required.

Further information

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.


Length: 3066 Date: 20120526 Time: 073515     triton ( 150 ms )