Pick Slip Line Sequence Does Not Follow Release Sequence Rules
(Doc ID 429308.1)
Last updated on MARCH 31, 2019
Applies to:Oracle Shipping Execution - Version 18.104.22.168 to 22.214.171.124 [Release 11.5.10]
Information in this document applies to any platform.
Oracle Shipping Delivery Based - Version: 126.96.36.199 to 188.8.131.52
Executable:WSHREL - Pick Release
On 184.108.40.206 in Production:
The Pick Release process does not order or sequence the picked lines correctly according to the release sequence rules. It always uses the inventory_item_id as the first sort criteria, then follows the Release Sequence Rule order.
This can be demonstrated using the following steps.
A) Following lines are entered on the order:
Line 1.1 Item = <ItemA>, Item ID = <Item_ID1>, Schedule ship date = 24-APR-2007
Line 2.1 Item = <ItemB>, Item ID = <Item_ID2>, Schedule ship date = 25-APR-2007
Line 3.1 Item = <ItemC>, Item ID = <Item_ID3>, Schedule ship date = 26-APR-2007
Line 4.1 Item = <ItemD>, Item ID = <Item_ID4>, Schedule ship date = 27-APR-2007
B) Setup Release sequence rule 'ROD Schedule Date' which specifies Schedule Date having Priority 1 in Ascending order.
C) Run Pick Release using the above rule.
The expectation is the order lines should pick in the schedule date sequence, which is line 1.1 first, then 2.1, 3.1, and 4.1. Instead it is picking first by inventory_item_id, then schedule date which gives the sequence: 4.1, 3.1, 1.1, 2.1.
This is contrary to the business requirement and also to what the Oracle documentation says. In the OM Implementation Manual, under the section "Defining Release Sequence Rules" there is no mention of using the item id as a sort criteria.
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