Master the Approval Management Engine: Attributes, Conditions, Groups, and Rules.
Oracle Approval Management Engine (AME) is a centralized, rules-based engine used to define approval routing rules for various transactions (like Purchase Requisitions, AP Invoices, or HR absences). Instead of hardcoding logic, AME allows you to configure complex "If-This-Then-That" approval hierarchies without writing code.
You must have the "Approvals Management Administrator" and "Approvals Management Business Analyst" responsibilities.
The calling application (e.g., Purchasing) must be configured to use AME instead of its standard hierarchy.
You must grant transaction type access to the specific AME user via the Functional Administrator responsibility.
AME Business Analyst
AME Business Analyst
AME Business Analyst
AME Business Analyst
Actor: AME Business Analyst | Module: Approval Management Engine (AME)
A Transaction Type represents the business process you want to approve (e.g., "Purchase Requisition Approval"). Every AME setup starts by selecting or creating a Transaction Type.
Example: Select the "Purchase Requisition Approval" transaction type from the AME dashboard.
Navigation Path:
BPM Worklist > Administration > Task Configuration
Key Actions:
In Fusion, AME is replaced by Business Process Management (BPM). You search for the specific Task (e.g., ReqApproval).
Actor: AME Business Analyst | Module: Approval Management Engine (AME)
Attributes are the variables AME uses to evaluate rules. They are essentially SQL queries that fetch data from the transaction (e.g., "Requisition Total Amount", "Cost Center").
Example: Create a custom Attribute called "REQ_AMOUNT" using a SQL query: `SELECT total_amount FROM po_requisition_headers WHERE requisition_header_id = :transactionId`.
Navigation Path:
BPM Worklist > Task Configuration > Data Objects
Key Actions:
BPM uses predefined payload attributes (XML data) passed by the Fusion application.
Actor: AME Business Analyst | Module: Approval Management Engine (AME)
Conditions are the "If" part of your "If-Then" rule. They evaluate an Attribute against a specific value or range.
Example: Create a Condition: "If REQ_AMOUNT is greater than or equal to 10,000 and less than 50,000".
Navigation Path:
BPM Worklist > Task Configuration > Rules (IF section)
Key Actions:
Use the graphical rule builder in BPM to define the IF conditions based on the payload data.
Actor: AME Business Analyst | Module: Approval Management Engine (AME)
An Approval Group is a list of approvers (users or roles). This is the "Then" part of your rule. If the condition is met, route it to this group.
Example: Create an Approval Group named "IT_DIRECTORS_GROUP" and add "John Doe" and "Jane Smith" as approvers.
Navigation Path:
BPM Worklist > Task Configuration > Approval Groups
Key Actions:
Similar concept in BPM; you can define static groups or use dynamic hierarchy routing.
Actor: AME Business Analyst | Module: Approval Management Engine (AME)
Rules bring it all together. A Rule connects your Conditions to your Actions (like routing to an Approval Group or requiring a Supervisory hierarchy).
Example: Create Rule: "High Value IT Reqs". Attach Condition: "Amount > 10K AND Cost Center = IT". Attach Action: "Require approval from IT_DIRECTORS_GROUP".
Navigation Path:
BPM Worklist > Task Configuration > Rules
Key Actions:
Use the IF/THEN graphical interface. IF conditions are met, THEN assign to Approval Group.
Understand where AME fits into the Requisition and PO approval process.
Read Guide