OM Drop Ship ('External' Line Source Type) Uses Incorrect Issue Transaction Type For Internal Order
Last updated on DECEMBER 20, 2017
Applies to:Oracle Order Management - Version 188.8.131.52 to 184.108.40.206 [Release 11.5.10]
Information in this document applies to any platform.
Form:OEXOEORD.FMB - Sales Orders
On : 220.127.116.11 version, Transaction Fulfillment
The introduction of the ability to default the OM Order Line 'Source Type' from the Line Item's 'Default SO Source Type' attribute permits the following scenario to occur:
The Item in Organization X is Min-Max Planned, with its default Source being Organization A. Min-Max Planning therefore creates an Internal Req at Org X which becomes an Internal Order in Org A. In addition, the Item is defined in Org A as a Drop Ship Item ('Default SO Source Type' = 'External') so that any OM orders fulfilled from Org A will be Drop Shipped. The Internal Order Line's standard Defaulting Rule marks its Source Type as 'External' from the Item definition, and it then processes as a Drop Ship line through the workflow.
However, when the Drop Ship PO which results is Received in Org A, it creates a 'Sales Order Issue' transaction, instead of the required 'Int Order Intr Ship' or 'Int Order Direct Ship' transaction (as defined by the Inter-Org Shipping Network definition between Org A and Org X). This means the Internal Req at Org X cannot be received and can never be completed - essentially, standard functionality has created a data corruption.
It looks as though the Drop Ship receipt process is hard-coded to use the 'Sales Order Issue' transaction type, rather than recognizing from the Order's Source that it is an Internal Order, and from the Shipping Network which Issue Transaction Type to use.
Is this a known issue?
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