My Oracle Support Banner

Receiving Transaction Processor Incorrectly Processes LCM Records With "LC_PENDING" Status For ASN Mobile Receipts (WMS Enabled and LCM as Service Org) To "ERROR" Before LCM Programs Kick Off (Doc ID 3017719.1)

Last updated on JUNE 03, 2024

Applies to:

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


Landed Cost Management (LCM) PO Receipts seem to be getting stuck when receiving through mobile applications. This organization is WMS enabled and LCM as Service enabled. Receiving transaction processor request is scheduled every 3 minutes and LCM programs (Landed cost integration manager, Shipments Interface Import, Receiving transaction processor (spawned from the Shipments interface import request)  run every 5 minutes. Error is not consistently reproducible. This happens sometimes when the Receiving Transaction processor runs before the LCM programs request set kicks off. On a production instance, it is not possible to schedule these in perfectly sequential fashion.

The shipment_num specified is invalid. The value specified (XXXX) does not match the expected value ().

1. Purchasing Responsibility > Purchase Orders > Create and approve PO (LCM as service, WMS enabled org)
2. iSupplier > Advance Shipment notices > Create ASN from iSupplier portal for partial PO qty
3. Submit and Run Receiving transaction processor (no parameters provided)
4. ASN is created.
5. Whse Mgmt > Inbound > Receive > ASN > Receive partial quantity of ASN from mobile
6. Complete the receipt
7. Run LCM Programs - Landed cost integration manager and Shipments interface import
8. Quantity received successfully.
9. Create second receipt from Mobile for the same ASN
10. Data is loaded into RTI , RHI. (LC_PENDING)
11. Run Receiving transaction processor now, instead of LCM requests.
>> See RTP changes the RHI record to error. -- This is the first step leading into later errors, which are expected.
12. Then, LCM programs kick off.
13. See log for Shipments interface import > Record in RHI changes to ADD.
14. RTP runs now spawned from Shipments Interface import > RTP shows error -"Shipment_num is invalid" as this is ASN with record type 'ADD' which is not supported by design.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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