Bug 2889192 7/6/18, 9)48 AM

Bug 2889192 : RELEASE SALES ORDER RESULTS IN ORDER GOING TO BACK ORDER STAGE

Bug Attributes

Fixed in Product
Type B - Defect 11.5.6
Version
2 - Severe
Severity Loss of Product Version 11.5.6
Service
90 - Closed, 319 - IBM AIX on
Status Verified by Platform POWER Systems
Filer (32-bit)
Created 04-Apr-2003 Platform Version
Updated 15-Apr-2003 Base Bug N/A

Database
9 Affects Platforms Generic
Version
Knowledge, Patches
Product
Oracle and Bugs related to
Source
this bug

Related Products

Oracle E-Business
Line Family Logistics
Suite
508 - Oracle Inventory
Area Logistics Product
Management

Hdr: 2889192 9 PICKRELEAS 11.5.6 PRODID-508 PORTID-319

Abstract: RELEASE SALES ORDER RESULTS IN ORDER GOING TO BACK ORDER STAGE

*** 04/04/03 10:49 am ***

=============================================================================
PROBLEM DESCRIPTION
=============================================================================
** DETAILED DESCRIPTION OF PROBLEM, INCLUDING ALL ERRORS:

Customer is trying to pick release their orders and they are going
automatically to backordered status. Customer has enough on hand qty. When
they try to re-release the orders, the process errors out

Client provided:
----------------------
We have moved over to Production and we are creating a Order in Prodn. The
Same Set up works fine in our Development Instance.
We have created and booked a Order - Order Num 26916.
After we carry out Release Sales Order we observe that the Order is going to
'BackOrder Stage'.
We are uploading :
1. omse11i.sql.
2. wshpickline115.sql script
3. Trace file when I carry out Launch Pick Realease from Shipping
Transactions
4. Set uP script.
Can u advise why this happens.

However when we carry out Pick Realease - again - thru Shipping Transactions
Pick Realease - The Request Pick Selection

https://support.oracle.com/epmos/faces/BugDisplay?_adf.ctrl-state=101n8on5vw_102&id=2889192 Page 1 of 4
Bug 2889192 7/6/18, 9)48 AM

List Generation gets completed as WARNING . The Order status is still at Back

Order. The Screenshots are uploaded.

This is the Message in the View Exceptions Window for this Order
Pick Release process could not allocate 1 of item PTM010402 for order 30970
as there was insufficient quantity available Or Inventory allocations have
failed,
and the line has been back ordered.

*** 04/04/03 10:50 am ***

*** 04/04/03 10:50 am ***
*** 04/04/03 10:53 am ***

and if it could be cleared ?

*** 04/04/03 10:57 am ***

*** 04/04/03 11:03 am ***
Files have been uploaded to ess30 -

>> Uploading local file: Prod1_ora_23119.trc.txt from client

>> Sending Prod1_ora_23119.trc.txt to ess30
>> Opening BINARY mode data connection for Prod1_ora_23119.trc.txt. Transfer
complete.

Listing of bug2889192:
Order_Header_of_30970.xls
Pick_Release_Log_fIle.txt
Pick_Release_log_l2321362_req.htm
SET_UP_OF_ORDER_MANAGEMENT.htm
WSHPickLine115_pick_release_diag.htm
error_in_pick_release.xls

*** 04/04/03 11:17 am ***

*** 04/04/03 11:17 am *** (CHG: Sta->30 Pri->2)

*** 04/04/03 11:29 am ***
Thanks for update -
submitted questiosn to client...
*** 04/04/03 11:58 am ***
Client has responded:
---------------------
1. Yes. The Instance is correct.
2. The On hand Quantity is sufficient. The screen prints show Qty on Hand of
625
3. We are making a sale only for this specific Item.
Regards
*** 04/04/03 11:58 am *** (CHG: Sta->11)
*** 04/04/03 12:08 pm ***
*** 04/04/03 12:08 pm ***
Client has added:
-----------------
New info : Query Output to check on Hand Qty [ Screen Print already sent ]
SELECT inventory_item_id , transaction_quantity , subinventory_code FROM
MTL_ONHAND_QUANTITIES where organization_id = 91 and inventory_item_id =
12802
INVENTORY_ITEM_ID+TRANSACTION_QUANTITY+SUBINVENTORY_CODE
12802 +625 +NEW

https://support.oracle.com/epmos/faces/BugDisplay?_adf.ctrl-state=101n8on5vw_102&id=2889192 Page 2 of 4
Bug 2889192 7/6/18, 9)48 AM

Regards
*** 04/04/03 12:09 pm ***
Repaging BDE for request for Sev 1, changed status to 16, sev 1...
*** 04/04/03 12:09 pm *** (CHG: Sta->16 Pri->1)
*** 04/04/03 12:10 pm ***
client added:
-------------
New info : Clarification :
We have not moved TEST to Production . We have set up Prodn afresh with the
same Set Up as that exists in TEST.
Regards
*** 04/04/03 12:46 pm ***
*** 04/04/03 12:52 pm *** (CHG: Sta->10)
*** 04/04/03 12:52 pm ***
*** 04/04/03 12:54 pm ***
Uploaded on hand qty screen shot - askign client for the remaining...
*** 04/04/03 01:26 pm *** (CHG: Sta->16)
*** 04/04/03 01:26 pm ***
Update from the customer:
New info : Hi Mark . Oracle ,
1) Are you using any item controls such as serial number, lot number, locator
?
No the Item is not Serial Num , Lot Num or Locator Controlled.
We have gone LIVE on PRODUCTION and have to catch up on a Backlog of over
1000 Orders.
2 Also, how can you live on a system where they have only tried one sales
order ?
Lets put it this way - Only after I catch up on my Back log of 1000 Orders
which I have to enter into the system ...would the System be thrown open to
the USERS.
3) If you are still loading orders, when are you planning to use this new
instance ? One order does not warrent a sev 1.
The system was supposed to be given to Users on 1st April [ That is the
Financial / Fiscal Year in India ]. I have logged a TAR with reference to 1
Order. However - I have 10 Orders stuck in the system.
As all my other Orders are similar to this Order - I am holding back entry of
the Balance 990 Orders.
More importantly I am holding back Current Order creation in the Apps System
Regards
*** 04/04/03 01:31 pm *** (CHG: Sta->10)
*** 04/04/03 01:31 pm ***
*** 04/04/03 01:42 pm *** (CHG: Sta->16)
*** 04/04/03 01:42 pm ***
The file On_Hand_Quantities_along_with_Locator_Break_Ups.doc is on ess30 under
the bug.
Thanks
*** 04/04/03 01:54 pm *** (CHG: Sta->10)
*** 04/04/03 01:54 pm ***
*** 04/04/03 02:51 pm ***
*** 04/05/03 07:03 am ***
Support is currently performing a ODC session with the customer.
*** 04/05/03 08:41 am ***
*** 04/05/03 08:41 am *** (CHG: Sta->16)
*** 04/05/03 09:12 am *** (CHG: Sta->30 Pri->2)
*** 04/05/03 09:12 am ***
*** 04/05/03 09:33 am *** (CHG: Sta->10)
*** 04/05/03 09:42 am ***
*** 04/05/03 09:42 am *** (CHG: Sta->16)
*** 04/05/03 09:52 am ***
*** 04/05/03 10:06 am *** (CHG: Sta->10)
*** 04/05/03 10:22 am ***
*** 04/05/03 10:22 am *** (CHG: Sta->16)
*** 04/05/03 10:31 am *** (CHG: Sta->10)
*** 04/05/03 10:31 am ***
*** 04/05/03 10:54 am ***

https://support.oracle.com/epmos/faces/BugDisplay?_adf.ctrl-state=101n8on5vw_102&id=2889192 Page 3 of 4
Bug 2889192 7/6/18, 9)48 AM

*** 04/05/03 10:54 am *** (CHG: Sta->16)

*** 04/05/03 10:57 am *** (CHG: Sta->30)
*** 04/06/03 11:02 pm ***
*** 04/15/03 03:29 am *** (CHG: Sta->90)
*** 04/15/03 03:29 am ***
*** 04/15/03 03:29 am ***
Hi

The assciated tar is closed and hence closing the bug also

Regards
Srinivas

https://support.oracle.com/epmos/faces/BugDisplay?_adf.ctrl-state=101n8on5vw_102&id=2889192 Page 4 of 4