AME

Approvals Management Engine

What is AME
Not a Module.
Self service web application.
Based on business rules AME statically / dynamically
generates Approvers List at Run Time based on SQL
queries.
Dynamic approvers list may base on
Its a part of Oracle Applications and used across Oracle
Apps.
AME can be Extended.

Advantages of AME
No / Little coding.
Business logic can be implemented globally from a single
window.
It can make use of Employee-Supervisor / Position Hierarchies.
It can also use any custom hierarchies that you may have
developed.
No need of other workflow customizations. Hence, reduced
cost.
Has inbuilt TEST workbench for testing different scenarios.
Automatically responds to changes in the hierarchies.
Works with Custom Applications also.

Parallel Approval Process Advantage

Approver List
Approver list has six subordinate levels.
Item class
Item Sub-list
Action type
Group or chain
Group or chain member

Parallelization Process
AME constructs Approver Tree

 Parallel approval has a tree structure & enables each part of

the tree to progress thru its approval cycle independently.
This enables the approval process of each item in the txn to
continue irrespective of the progress of approval of the other
items.
This greatly reduces approval process time.

About AME
It has various Transaction Types already defined in AME.
Ex: PR, PO, Inv, Holds, Quotations
Custom Transaction Types also can be defined.
Maintains Approvals History.
It has administrative dashboard for maintenance.
Integrating Application <-> AME

AME Components
1. Transaction Types: (Seeded, Custom)

Ex:

Documents like PR, PO, Invoice, JE.. or

Custom Transaction Types can also be used.

2. Attributes:
Variables that represent a value of a data element
Ex:

Price, Item type, Discount

Attributes can be defined at 3 different levels Header, Line

Item and Cost Center level.
3. Conditions: IF
This evaluates the value of attributes.
Ex:

if Price<$100,000 | if Discount > 20% | if item type =

Condition = TRUE AME is fired

if Price<$100,000
if Discount > 20%
if item type = goods
if Price<$100,000 & if Discount > 20% & if item type = goods TRUE
AME is fired

Transaction Type + Attribute value TRUE AME is fired

4. Actions: THEN
What to do if a condition is satisfied.
5. Approval Groups:
Has a list of Approvers derived from HRMS
Can be static / Dynamic - based on SQL codes.
6. Rules:
Contains Attributes, Conditions, Actions.

SETUP

 AME is Role Based Access Model (RBAC)

Approvals Matrix

Not an exhaustive list because it doesnt address what

happens to amounts over %5,000.

Best Practices - AME

Capture every business case that requires an approval.
Rules should not have conflicting outcomes.
Minimize the rules on any transaction.
Minimize the total number of rules in a Transaction Type.