My Oracle Support Banner

Blanket Purchase Agreement Releases Not Updating Via iSupplier Portal (Doc ID 2049518.1)

Last updated on JULY 14, 2020

Applies to:

Oracle iSupplier Portal - Version 12.1.3 to 12.2.4 [Release 12.1 to 12.2]
Information in this document applies to any platform.


Changes to Blanket Purchase Agreement Releases are not updating via iSupplier Portal.

The application appears to save the change and it looks like the changes are made but the original data remains; it doesn't actually change anything. If the user queries the PO release, no changes have been made and no update notifications are sent to the buyer.
Changes are working for standard POs. No errors are observed in the application.

Due to this issue, Suppliers think they are making a change because it looks as if it is saving but it really is not saving the changes. Also, no notifications are sent to buyers regarding the change(s).

The expected behavior is that when a supplier clicks the save button to save the form information it is saved to the database and the buyer is notified of the changes. 


The following error is observed n the FND_LOG_MESSAGES table: 

ORA-01416: two tables cannot be outer-joined to each other

- OR -

po.plsql.PO_CHG_REQUEST_PVT.process_supplier_request.others_exception 6 -1416

Steps To Reproduce
1. Log in as Supplier user in iSupplier portal.
2. Make a change to quantity, price or date on a blanket purchase agreement release.
3. Apply the changes.
4. It appears like application saves, but on re-query, observe that document does not have any of the changes.


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.