PO_CHANGE_API1_S.UPDATE_PO Does Not Trigger Change Request Flow and Supplier Notification (Doc ID 1946341.1)

Last updated on FEBRUARY 01, 2023

Applies to:

Symptoms

The API po_change_api1_s.update_po is called directly to update Purchase Order (PO) tables with a change which in turn updates the PO and increments the revision number. However; it is also expected that a notification would then be generated for the Supplier and that in iSupplier the status would change to SUPPLIER CHANGE PENDING.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. As part of inbound EDI855 program used for acknowledgements, the Supplier informs the customer of a change, e.g. promised date.
2. The API po_change_api1_s.update_po is called to update directly the PO tables with this change.
3. The PO is properly updated and the revision is incremented.
4. It is expected to see also the change as part of the change history from iSupplier. However, this does not happen.  Also a notification is not generated for the iSupplier.

Changes

Cause

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