Search from 700 + Posts

Jul 29, 2011

AME (Oracle Approval Management) Architecture


This is short post about  AME Architecture, for additional information feel free to leave comments and will more than happy to answer your question

AME Architecture –


 
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

3 comments:

  1. How do u link AME and Workflow ?

    ReplyDelete
  2. It's 2 Step Process

    1.Register your application in AME(in case it is not already register). By registration I mean Create the Transaction type/Item class/mandatory attribute etc for your Application ( if it is not already defined) in the Approval management administrator Dash board.


    2.Once step#1 is done, call the AME API to Fetch the approver information from the Oracle workflow.

    Hope that helps.

    ReplyDelete
  3. Hi, Is there a way to start the ame_engine from pl/sql code through ame apis? please help.

    ReplyDelete