Pick Release Is Picking Order Lines From Wrong Subinventories Versus Subinventory Value Populated On Order Line
(Doc ID 1505046.1)
Last updated on SEPTEMBER 27, 2021
Applies to:
Oracle Shipping Execution - Version 11.5.10.2 to 12.2 [Release 11.5.10 to 12.2]Information in this document applies to any platform.
Goal
Business has a few orders where there is a subinventory specified on the order line. Majority of the orders do not have a subinventory specified on the order line. Orders that contain
a subinventory on the order line are released manually while orders without are released using Pick Release - SRS with a pick release rule which does NOT specify a subinventory in
the 'release critieria'.
When pick release is run (in batch or SRS mode) for orders without a subinventory using a pick release rule which does not specify subinventory as release-criteria, orders which do contain
a subinventory on the order line are also pick released. Since the release rule has a 'pick from' subinventory' specified, these orders are picked from the 'pick from' subinventory rather
than the subinventory on the order line.
The expectation is that if there is a NULL value for the release criteria subinventory, and a NON-NULL subinventory value on the order line then these orders would NOT be eligible for pick release.
Why is pick release releasing orders having lines with a subinventory value populated when it conflicts with the picking rule that does NOT have a subinventory selected as release criteria?
Solution
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
Goal |
Solution |
References |