Pick Release Errors With Quantity Entered Does Not Meet Decimal Quantity Standard Causing All Lines In Batch To Fail And Not Eligible To Be Pick Released
(Doc ID 2406399.1)
Last updated on MARCH 30, 2022
Applies to:
Oracle Shipping Execution - Version 12.2.6 and laterOracle Warehouse Management - Version 12.2.6 and later
Information in this document applies to any platform.
Symptoms
ISSUE
In a WMS enabled Org, eligible lines are not getting pick released using either of the following:
- Standard Pick Release SRS program
- Concurrent request using the Release Orders form (without order number)
Pick Release SRS or the Concurrent request via form is scheduled to run every 20 minutes for a large number of orders.
For example, the daily order volume is around 3,500 orders, which adds up to 8,000 plus order lines daily.
Every time pick release request set is run, 24 child pick release processes are running.
Each pick release child process is typically less than 1000 lines.
The profile option WSH: Pick Release Batch Size = 1000.
Order with 4 lines where all 4 lines are eligible to pick release, meaning there are no credit check holds and there is sufficient quantity on hand:
> 1st batch will pick release 2 out of 4 lines even though all 4 lines are eligible to pick release.
> 2nd batch will pick release one more line from the same order.
> A few more batches later the 4th line gets pick released.
This is a problem as the order lines that get pick released in separate batches are assigned to different delivery id's created. However, when running the pick release concurrent request through the
Release Orders form for a specific sales order then it is pick releasing all eligible lines for that sales order. This is being used as a WORKAROUND. The expectation is that order lines that are eligible to pick release
having sufficient quantity, no credit check failure or holds will all be pick released at the same time when submitting the Pick Release SRS and NOT released across multiple separate batches.
In one batch, the following error was found and it caused all records in the batch to fail. Once the lines with the decimal quantity error were cancelled and pick release submitted. Eligible lines were pick released.
ERROR
STEPS
The issue can be reproduced at will with the following steps:
1. Order Management Super User Responsibility
2. Shipping
3. Interfaces
4. Pick Release SRS
Changes
Item attribute OM Indivisible is checked for the items.
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 |