My Oracle Support Banner

Ad-hoc Approvers Added During Purchase Approval (Using AME) Are Not Notified As Expected (Doc ID 1980941.1)

Last updated on JUNE 09, 2023

Applies to:

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


Using the Approval Management Engine (AME) with version 12.1.3, ad hoc approvers are not included in the approver list after Purchase Orders (PO)s are Rejected and then resubmitted.  There is no error, but the Ad-hoc approver is not included as part of the approval list

The issue can be replicated as follows:

Scenario 1
1) User creates PO in Buyer Work Center and there is one Default Approver (we call this approver Y)
2) User addes an Ad-Hoc approver Z so now approval sequence is :
    a. Approver Y
    b. Approver Z
3) PO is submitted for approval
4) Only Approver Y is notified (Approver Z is not notified)

Scenario 2
1) User creates PO in Buyer Work Center and there is one Default Approver (we call this approver A)
2) User adds an Ad-Hoc approver (Approver B) and submit
3) See that approval list is now
    a. Approver A
    b. Approver B

4) Approver A delegates to Approver X , so now approval history is :
    a. Approver A - Delegate
    b. Approver X - Rejects
    c. Approver B - pending

5) Submitter opens the PO and it is shown in Rejected status. The submitter clicks on Approval Options to resubmit and sees by default:
    Approver A - Rejected
    Approver B - null (no response)
    Then Submit

6) The approval list now shows the original Approver A in the approval list. Approver B is not included as an approver even though they were displayed as an approver in the Approver's screen


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.