REQ Supply Remains After Successful Ship Confirm Of Internal Sales Order

(Doc ID 1605613.1)

Last updated on APRIL 24, 2015

Applies to:

Oracle Inventory Management - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

Internal Orders are Ship Confirmed then Shipment Lines are available to Receive.

As expected, the following records exist:
rcv_shipment_headers
rcv_shipment_lines
mtl_supply (supply_type_code=SHIPMENT)

There is no problem completing the Receiving activities

In addition to SHIPMENT supply, REQ supply also exists.
This REQ supply record should have been deleted when the SHIPMENT supply was created.

This issue was noted after patches for Signal 11 were applied per <Note 1323573.1> (Receiving Transaction Processor Fails Intermittently With Signal 11 And Leaves rcv_transactions_interface Records in RUNNING Status) were applied

Workaround:
Use datafix to delete the extraneous REQ supply records (new backup table name must be used each time).

Other issues that also began to occur after Signal 11 patches were applied:

a. Intransit Shipment completes successfully, but has REQ supply instead of SHIPMENT supply (so cannot be Received)
- datafix bug 17368987 was logged for this issue

b. RUNNING/ONLINE/SHIP
-  records are reset to PENDING/BATCH

c. duplicate Shipment lines are created
- Dev approved datafix is run to delete the extraneous records


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