OPM Pick Release Shipset Backorders All Lines Even Though SO Lines are Reserved.

(Doc ID 559699.1)

Last updated on AUGUST 01, 2016

Applies to:

Oracle Process Manufacturing Logistics - Version 11.5.10 to 11.5.10 [Release 11.5]
Information in this document applies to any platform.
*** Checked for relevance on 23-Dec-2011 ***


Symptoms


In Release 11.5.10.2 in a Process Manufacturing (OPM) environment, Pick Release puts all Lines of a Sales Order on Backorder even though each Line has a reservation of available stock.

All of the Lines are in a Ship Set.

When you remove the ship set check at pick release and re-run, all lines are successfully released.


The following error is seen in the Pick Release concurrent logfile.


PROCESS ORG 115
Calling program unit GMI_RESERVATION_UTIL.GET_OPM_ITEM_FROM_APPS
(opm_dbg) in Util q: item_no=564.
Calling program unit GMI_RESERVATION_UTIL.PRINTLN
Item is opm invnetory
Calling program unit GMI_RESERVATION_PVT.CALCULATE_RESERVATION
value of is p_organization_id115
value of p_demand_source_line_id is 25057
Value of item_id is 2924
value of p_requested_quantity is 8
value of p_requested_quantity2 is
Value of Whse Code is HFG
check profile GML_CHK_INV_PICK_REL is Y
Line has Shipset 165272
Enforce shipset in Shipping parameters for the warehouse is set as Y
Line Has Shipset and shipset is enforced for the warehouse
Calling Calc_Reservation_For_shipset
IN Calc_Reservation_For_shipset id 165272
Shipset Found in global table - NOT RESERVED - Exiting from calc_reservation_for_shipset
Entering WSH_UTIL_CORE.GET_ITEM_NAME (WSHUTCOB.pls 115.120.11510.6) (12/06/2007
09:38:37 AM)
P_ITEM_ID ==> 2923
P_ORGANIZATION_ID ==> 115
P_FLEX_CODE ==> MSTK
P_STRUCT_NUM ==> 101
Exiting WSH_UTIL_CORE.GET_ITEM_NAME (12/06/2007 09:38:37 AM, .01 seconds)
PRIOR RESERVATIONS IS SPECIFIED AND RESERVED QUANTITY IS 0
SET LINE TO BE BACKORDER FOR OPM
Entering WSH_XC_UTIL.LOG_EXCEPTION (WSHXCUTB.pls 115.90.11510.3) (12/06/2007
09:38:37 AM)
P_API_VERSION ==> 1
P_INIT_MSG_LIST ==> F
P_COMMIT ==> F
P_VALIDATION_LEVEL ==> 100
X_EXCEPTION_ID ==> is NULL
P_EXCEPTION_LOCATION_ID ==> 142
P_LOGGED_AT_LOCATION_ID ==> 142
P_LOGGING_ENTITY ==> SHIPPER
P_LOGGING_ENTITY_ID ==> 1124
P_EXCEPTION_NAME ==> WSH_PICK_BACKORDER
P_MESSAGE ==> Pick Release process could not allocate 8 of item 564 for order
2000551 as there was insufficient quantity available Or Inventory allocations have failed, and the
line has been back ordered.
P_MANUALLY_LOGGED ==> >



The issue can be reproduced at will with the following steps:

1. create and book the order.
2. Create OPM batches and allocate the batches to the order lines through the scheduling >
reservation details option.
3. Complete batch output and verify lots now reserved.
4. Run pick release - fails.
5. Uncheck 'enforce ship sets at pick release' checkbox. We leave the ship set number on the order lines.
6. Run pick release - succeeds.


Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms