Incorrect status for B2B Orders -- EXTERNAL_REQ_REQUESTED or External_requisition -- duplicate requisitions are created.
Last updated on JULY 12, 2017
Applies to:Oracle Order Management - Version 220.127.116.11 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 22-Jul-2013***
This is an intermittent issue where Sales Orders that go through the Back to Back order flow are not having the flow status set and they are left with a a status of EXTERNAL_REQ_REQUESTED or External_requisition. This is despite the fact that the stock has been received and the workflow progressed. This in turn causes duplicate requisitions to be created for the orders. The impact of this is that we are experiencing stocking issues and means that additional unwanted stock is being ordered.
Most orders do progress as expected, and if similar orders to the problematic orders are progressed again they will generally work without an issue.
There are three scenarios that have been observed when processing back-to-back orders :
1. The B2B Process is functioning as expected.
2. The B2B Process creates a requisition and Purchase Order, Stock is received. The Order is progressed to completion and the item is delivered and Invoiced.
HOWEVER the Status Code of the order line is ---
EXTERNAL_REQ_REQUESTED. The workflow for this order line shows that the order is closed and this is re-inforced by the open flag which is 'N'.
3. The Order gets neither delivered nor invoiced, and the added stock from the receipt is free for use. The flow status of the line is "External_requisition" and generates new requisitions.
Once the Purchase requisition has been created the flow status should be updated so that the next run of the AutoCreate Purchase Requisition process does not pick up the order for processing again.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms