My Oracle Support Banner

Empty Flag Not Updated When Material Is Issued Out of Locator (Doc ID 2376289.1)

Last updated on MARCH 02, 2019

Applies to:

Oracle Warehouse Management - Version 12.2.4 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.4 version, Pick Drop

Actual Behavior
Empty Flag not updated for issue locator

On performing Pick Drop and Receiving Corrections, empty_flag on source/issue locator is not updated. Destination locator empty_flag is updated, while issue locator's is not.
1.> During Pick Drop, if there are more than 1 distinct items in the locator and all items are being picked to make the locator empty, the empty_flag does not revert to 'Y', thereby making the locator unusable for any putaway.
2.> Receiving Corrections does not update empty_flag at all, thereby making the locator unusable for any other putaway.

Subinventory Transfer works fine. Pick Drop and Receiving Corrections are the ones with this problem.


Expected Behavior
Expect the Source Locator's Empty flag to be updated once material is moved out

Steps
The issue can be reproduced at will with the following steps:
Pick Drop
Receive Corrections

Business Justification
The impact of empty flag being inaccurate is huge for our already running-out-of-space warehouse. Completely rely on locator empty flag to determine whether a locator is empty and strive to putaway in an empty locator before looking for a colocator, to ensure FIFO fashion of picking. Therefore, at any time, requirement is to empty locators in each zone to be suggested for putaway, but in reality, there is nota large number of extra locators which are empty to perform putaway.

Consider this, after performing putaway/picking for 6 hours, on an average, there could be as many as 00 locators which become unusable for putaway due to them having empty flag as 'N' despite being truly empty. Cannot run Update Locator Capacity program while the warehouse is in operation and that program is scheduled to run once every night.
There is no other way out but to wait for this nightly run of the empty_flag to be updated to fix the issue, but this is affecting warehouse performance and taking the users a much longer time to putaway each item.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.