LCM Shipment Number Does Not Appear In Receipt RCVRCERC Ship Txn Stuck RTI RCV_ASN_EXPECTED_RECEIPT_DATE

LCM Shipment Number Does Not Appear In Receipt RCVRCERC Ship Txn Stuck RTI RCV_ASN_EXPECTED_RECEIPT_DATE


In this Document
Symptoms
Changes
Cause
Solution
References

APPLIES TO:

Oracle Inventory Management - Version 12.1.1 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.
SYMPTOMS

In Pre-receiving LCM as a Service organization.

When creating a shipment in Landed Cost Management and the status completed then the shipment is stuck and does not appear in the Receipt form.

When checking Transaction Status Summary, it shows that the LCM Shipment is stuck

Transaction Type = Ship
Processing Mode = Batch
Transaction Status = Pending

Steps
The issue can be reproduced at will with the following steps:
1. Create and Approve PO : Purchasing Super User > Purchase Order > Purchase Order

2. Create LC Shipment : Landed Cost Management > Workbench > Shipments > Create > Source Type (Purchase Order) > Group Reference(on header) > Line > Purchase Order
Create Shipment

3. Generate LCM Charges
Validate Shipment
Calculate Shipment
Verify the Calculated Estimated Landed Cost
Submit to Receiving

4. Oracle Landed Cost Management
Run: Matches Interface Import
Run: Submit Pending Shipments
Shipment Interface Import

5. Oracle Inventory > Receiving > Receipt  RCVRCERC form
With Source Type (LCM) > The Shipment is not in List of Value LOV, so not allowing to receive the PO
On Find Expected Receipts  form
Search for
Source Type = LCM
Shipment = Shipment Number
get

FRM-40212: Invalid value for filed SHIPMENT_NUM.

6. Oracle Inventory > Receiving > Transaction Status Summary RCVTXVTX form
See stuck SHIP transactions in RCV_TRANSACTIONS_INTERFACE table.

CHANGES

RCVNRMDB.pls version is 120.15.12010000.12

CAUSE

The issue is caused by a coding error in RCV_INSERT_FROM_INL package, RCVINSTB.pls as described in Bug 16274612 LCM SHIPMENTS NOT VISIBLE IN PO RECEIPTS FORMS FOR RECEIVING.

In package RCV_INSERT_FROM_INL, the org_id is not populated before submitting RTP, which results in the RHI/RTI not being processed,
so the expected_receipt_date column is not populated in RCV_HEADERS_INTERFACE table and records will fail with error ' Expected receipt date is missing '.

The issue is resolved by upgrading to file RCVINSTB.pls version 120.0.12010000.11 or higher.

Examination of the Receiving Data Collection Script (Note 402245.1) shows the following:

RCV_HEADERS_INTERFACE

Header_Interface_Id 3471
Group_Id 5908
Processing_Status_Code ERROR
Receipt_Source_Code VENDOR
Asn_Type LCM
Transaction_Type NEW
Shipment_Num 403.1
Ship_To_Organization_Id 265
Shipped_Date 05-26-2013 00:00
Expected_Receipt_Date            <---- null="" p="">Validation_Flag Y
Org_Id                           <---- null="" p="">
RCV_TRANSACTIONS_INTERFACE

Interface_Transaction_Id 20334
Group_Id 5908
Transaction_Type SHIP
Transaction_Date 05-26-2013 15:20
Processing_Status_Code ERROR
Processing_Mode_Code BATCH
Transaction_Status_Code PENDING
Quantity 2
Interface_Source_Code LCM
Interface_Source_Line_Id 11841
Auto_Transact_Code SHIP
Receipt_Source_Code VENDOR
To_Organization_Id 265
Source_Document_Code PO
Po_Header_Id 12327
Shipment_Num 403.1
Expected_Receipt_Date            <---- null="" p="">Header_Interface_Id 3471
Validation_Flag Y
Org_Id 141
Lcm_Shipment_Line_Id 11841

PO_INTERFACE_ERRORS

Column_Name EXPECTED_RECEIPT_DATE
Error_Message Error: Expected receipt date is missing
Error_Message_Name RCV_ASN_EXPECTED_RECEIPT_DATE
Table_Name RCV_HEADERS_INTERFACE
Batch_Id 5908
Interface_Header_Id 3471
Interface_Line_Id 20334
MTL_PARAMETERS

Organization_Id    265
Organization_Code  RMW
Lcm_Enabled_Flag    Y

RCV_PARAMETERS

Organization_Id    265
Pre_Receive        Y
SOLUTION

To implement the solution, please execute the following steps:

1. Download and review the readme and pre-requisites for Patch 16511283:R12.PO.B that includes the fixed file version.

2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Confirm the following file versions: RCVINSTB.pls 120.0.12010000.11

select DO.STATUS,DO.OBJECT_TYPE,DS.NAME,DS.TEXT
from dba_source ds,DBA_OBJECTS DO
where DS.name = UPPER(RTRIM(LTRIM('RCV_INSERT_FROM_INL')))
and ds.line=2
and DS.name = DO.OBJECT_NAME
and DS.type = DO.OBJECT_TYPE
order by  DO.OBJECT_TYPE, ds.text;
Or run Diagnostics Apps Check Report for Purchasing application

5. Retest the issue.

6. Migrate the solution as appropriate to other environments.