fulfillment Order Webservice is Returning Status X and Leaves the Customer Order No and Fulfillment Order No Details (Doc ID 2986019.1)

Last updated on NOVEMBER 08, 2023

Applies to:

Symptoms

 Fulfillment Orders Retry on Status X

Customer reports scenario where the fulfillment order webservice is returning Status X and leaves the Customer Order No and Fulfillment Order No details on RMS tables.

1 - When the item_loc_soh record is locked by another user:
"This record on table ITEM_LOC_SOH with key values tsf_no: -----------, item: -------- was locked by another user. Unable to update record at this time"

Once the original issue is resolved (the record is no longer locked or stock issue is corrected) if the same call is done the webservice is refusing to use the same Customer Order No and Fulfillment Order No:
"The customer order number/fulfill order number/source loc ID/fulfill loc ID combination already exists in ordcust. Customer order no -------------, Fulfill order no ----------------.."

Cancelling the Customer Order did not resolve the issue as the data remained in RMS tables.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Scenario 1:
1 - loc the record item_loc_soh record
2 - publish the webservice message
3 - confirm return is Status X with the locking error: "This record on table ITEM_LOC_SOH with key values tsf_no: XXXXXXXXX, item: XXXXXXXXX was locked by another user. Unable to update record at this time"
4 - confirm data exists in ORDCUST_% tables
5 - retry the same message to get the error "The customer order number/fulfill order number/source loc ID/fulfill loc ID combination already exists in ordcust. Customer order no XXXXXXXXX, Fulfill order no XXXXXXXXX.."

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.