You are on page 1of 21

Approval

Management
Engine
When Can I Use AME?

You can use AME to derive lists of approvers based


on
user defined rules and maintain a history of
approvers
statuses when:
Authorizing expenses
Transferring employees from one division/cost
centre to another
Approving purchase orders with line or total order
values
Paying invoices
Business Processes or
Transactions
and Approvals
What is AME?

AME is a web application providing the following


services to calling applications:
A centralized rules repository for defining and
sharing rules
An execution engine to evaluate rules based on
transaction specific data
List management capabilities
History of approval statuses

AME does not manage the notification, routing or


responses from approvers
These remain the responsibility of the calling
application or the workflow process
AME Architecture
AME Architecture
Example of a Purchase
Order Approval List
How AME Works
Calling AME
A purchase order is submitted. This purchase order
is associated with:
A transaction type, which identifies the business
process provided by the eBusiness Suite
A unique transaction_id related to the specific PO

This information is passed to AME to start the


approval loop process.
There are also other common default attributes,
such as:
Set of books Id
Org Id
Requestor User Id etc
Approval Loop
How AME Works
Tracking Approvals
1. The calling application calls AME to get next
approver
2. AME returns the full ordered approval list
3. The calling application notifies next approver or
all approvers in the list
4. The calling application deals with approvers
response
Approve, Reject or Return
Sends response to AME
5. The calling application repeats these steps until
no more approvers are found
How AME Works
List of Approvers
AME generates the list of approvers
based on the rules configured for the
transaction type
AME evaluates the conditions associated
with the rules for the transaction
AME identifies the next approver from
the ordered list of approvers
An approver can be identified by:
Application username (user id)
Person name (person Id)
Approver Lists

AME executes the rules each time the application calls next approver
The list is always up to date with changes in hierarchy or personnel
How AME Works
Transaction
Completion
The approval process is complete when
there are no more approvers to be
notified
The calling application will execute the
next stage in the process.

For example, Oracle Purchasing, the


calling
application, will then create the
purchase order
Approvals

An Approval is an instruction to AME on how to execute


an Approval Type
For example, Require approvals up to at least level 7

Approval Types define the rules for generating a list of


approvers, based on:
1. HRMS supervisor hierarchy
Or
2. HRMS supervisor hierarchy and HRMS job level
Or
3. HRMS Position Level

Note: - Approvers are created in HRMS as employees


Approval Statuses
Approval Types and
Rule Types
Each approval type is associated with one or
more rule types:
List creation and exception
List modification
Pre and Post approval group
Substitution

Remember that an Approval Type identifies


the approvers that are to be added to an
approval list
For example, Absolute Job Level
List Creation and
Exception Rules
List creation rules generate a list of
approvers according to the chain of
authority defined
Exception rules allow you to exclude
approvers from the list generated
List creation and exception rules use
ordinary and exception conditions to
generate chains of authority based
on the approval type selected
Additional List Creation
and Exception
Rules
Rule Types
List Modification
List modification rules alter the default chain of
authority generated according to the approval
type selected.
Rule Types
Substitution
By using substitution, you can automatically
replace any identified approver with another
approver
Approval Groups
Static: Predefined, fixed, and ordered list of
approvers
Dynamic: List derived from a SQL statement

You might also like