ORG_ID In RTI Table Not Populated When ASBN Data Uploaded Via file In iSupplier (Doc ID 1944692.1)

Last updated on OCTOBER 29, 2015

Applies to:

Oracle iSupplier Portal - Version 12.1.3 and later
Information in this document applies to any platform.


ASBN data uploaded via file in iSupplier Portal doesn't create receiving transactions.
The uploaded file status shows up as PENDING, however notification gets sent to the buyer that an ASBN details.
Pending status is caused because Receiving Transaction Processor is not picking up the transaction due to ORG_ID is NULL in RCV_TRANSACTIONS_INTERFACE.
There are no error in po_interface_errors.


Create a manual ASBN.
If the ASBN is created manually (not by file) in iSupplier, the RTP picks the transaction and then processed without any issue because the ORG_ID is populated in RCV_TRANSACTIONS_INTERFACE table.

Expect the ASBN transactions uploaded to iSupplier via file, being picked up by the RTP.

The issue can be reproduced at will with the following steps:
1. Go to iSupplier
2. Create ASBN
3. Download the template
4. Upload the template
5. See uploaded file with status PENDING


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