Example: Optional HU Check When Creating a WT 

The system can only find the appropriate storage bins for a handling unit type when creating warehouse tasks (WT) if you have activated the HU type check.

You can enter *** as an allowed HU type in this table. This entry means that all the HU types in this storage type are allowed. The system then searches for a suitable storage bin for the HU type on the basis of the allowed storage bin types per HU type.

Before you activate the optional HU type check, you should check the table parameters carefully. If the configuration settings are not optimal, you may encounter performance problems.

The following example outlines the performance problems associated with the optional HU type check and their solutions:

§         Storage bin types P1, P2, P3, P4, and P5 are allowed for HU type E1. The system is to put away HU type E1 in storage type 0001. However, only storage bins of the type P0 are available in this storage type.

§         The system is not allowed to put away HU type E1 in storage type 0001. A system that has been configured optimally recognizes this (since access to a completely buffered table is possible) and searches for a suitable storage bin in the next storage type.

§         In the optional HU type check, the system tries to access the database five times without success. If you work with different storage sections, this number increases accordingly.

You can easily check the Customizing settings by viewing the log for the storage bin search. The greater the number of unsuccessful attempts that the system has made, the more ineffective the process for storage bin determination becomes. You should reduce the number of attempts by optimizing the storage type search.