My Oracle Support Banner

EMPLOYEE_ID Is Null In RCV_SHIPMENT_LINES And RCV_TRANSACTIONS Tables After ASN Import Process (Doc ID 2618872.1)

Last updated on DECEMBER 09, 2019

Applies to:

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


After upgrading to R12.2.8, it is noticed that Receiving Transaction Processor is not deriving employee_id as the buyer ID of the associated PO during Advance Shipment Notice (ASN) import process.
As a result, the ASN shipment is having null employee_id in rcv_shipment_lines table and also in rcv_transactions table (if ASN is also auto received during the import process).
It is also observed that it's not derived by both custom ASN import program and iSupplier Portal ASN import program.

Prior to the upgrade in R12.2.5, both the custom ASN import program and iSupplier Portal ASN import program were working fine by deriving the employee_id as buyer ID of the purchase order when the ASN was imported with no employee_id on it.
The behavior has changed after upgrading to R12.2.8 where the derivation is not happening anymore.
Due to null employee_id, the subsequent custom programs and other functions that depend on employee_id value for further processing are not working as expected.


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.