AME (Oracle Approval Management) Architecture

Today we will have a look at the flow of the AME. Following is the flowchart of the AME Process.

Overview about the architecture of AME

1.     Calling application send a request (to get list of approver) to the AME by means of sending Runtime data of transaction to AME API. e,g PO data to AME API

2.     AME execution Engine process the data.

3.     AME engine evaluate rules for that transaction types (rules are define in AME schema for  a transaction type).A transaction may have more than 1 rule associated with it.

4.     AME evaluate each rule depend on the conditions/attributes.

5.     Rules then execute action Type.

6.     AME then return calling application list of approvers(Sorted based on Setup in AME).

7.     (Please note when we call AME, it generate list of approvers, Identify next approver, check the status history to check if people has already approved or Not).

8.     Calling application receive response from AME and then send Notification to Approvers.

9.     PLUS calling application update the status of the Approver in AME by means of calling a AME API (Updatestatus API).

10.  AME is done when approves is complete

In general we will have a requirement to call the AME from workflow. This is a two steps process.

Process steps to link AME with workflow

1. Register your application in AME (in case it is not already registered). By registration, I mean, Create the Transaction type/Item Class/Mandatory attribute etc., for you Apllication (if it is not already defined) in the Approval Management Administrator Dashboard.

2. Once Step-1 is done, Call AME API to fetch the approver information from the Oracle workflow.