PO Does Not Go Into Requires Approval Status, When Using PO Update API For Quantity Changes at the Schedule Level (Doc ID 2964088.1)

Last updated on AUGUST 01, 2023

Applies to:

Symptoms

Purchase Orders do not go into Requires Approval status, when using PO Update API for Quantity changes at the Schedule Level.

DETAILS:
When using the PO update API "po_document_update_grp.update_document" for Quantity changes at the Schedule Level:

•  For the FIRST revision after the PO is Communicated, the PO is placed into Requires Reapproval status.  (Normal Approval can then occur)
•  For any consequent Quantity changes using the "po_document_update_grp.update_document" API, the PO remains in Approved status, rather than moving to Requires Reapproval status.
•  The Schedule Line Approved status is then put into R, while the document remains in Approved status
•  The difference in Approval status values, then causes issues in Receiving.

Changes

Upgrade from 12.2.9 to 12.2.11, which carried a change to PO_DOCUMENT_UPDATE_PVT. 

Cause

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