How Does One Block Allocation From An Active Location Marked For Cycle Count After Short Picking?
(Doc ID 2581494.1)
Last updated on JANUARY 27, 2021
Applies to:Oracle Warehouse Management Enterprise Edition Cloud Service - Version 18 and later
Information in this document applies to any platform.
On : 18 version, Core Product Functionality
When a SHORT PICK is performed by a user for an ACTIVE LOCATION, the location is flagged for CYCLE COUNT. However, this location still allows allocations for orders, i.e. the Lock Code is not populated
3 units of item 123 were allocated from location AC11111 for the order Order1. A pick user arrives in the location to pick the goods, but the user performs a short pick. The order Order1 will have its status changed to Partially Allocated and the location AC11111 will be flagged to cycle count.
But another order can be created by the host system, ordering the same item code. When the wave runs, the item will be allocated from the location flagged for CC. This location is an ACTIVE location, and the system is not applying a lock code when short picking is performed
How does one prevent allocation from locations flagged for cycle count after a short pick?
Expect the location from which the pick was short picked to have a systematic lock code applied.
The issue can be reproduced at will with the following steps:
1. Short pick from an Active Location
2. Location is marked for CC
3. Run a wave for another order, the system allocates from the location that as short picked
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