Approval Management EngineOverview
The purpose of Oracle Approvals Management (AME) is to define approval rules that determine the approval processes for Oracle applications.
Purpose is to find approvers based on business rules
– AME generates approver list
– Request for next approver re-generates approver list to return
next approver to calling application
Business Learning Center
AME is a web application that provides the following services:
A centralized rules repository for defining and sharing rules
An executive engine to define rules based on transaction data
List management capabilities
AME does not manage notification, routing or responses from approvers
Business Learning Center
Business Learning Center
Advantages
AME helps you maintain your business logic associated with approval transactions globally from single window
Lets you cut down approval related workflow customizations, hence reducing the cost of ownership
Helps you leverage common expenditure policies across modules, thus consolidating your approval policy requirements
Any transaction is assured to be approved under the latest conditions, regardless of organizational changes, currency fluctuations or transaction data
Built-in testing utility to check the correctness of setup performed for both real-time and test transactions, hence reduces the need for elaborate testing cycles
Business Learning Center
Parallel Approvals
Position Hierarchy
FYI Notifications
R11i – 178 transaction types
Approval Handler
A pre defined PL/SQL package procedure to execute the logic for an approval type
Approvals
Business Learning Center
Calling AME
When a request is submitted, it is associated with a Transaction type, associated with the business process
A Transaction ID is generated
The information is passed to AME to start the approval process
Business Learning Center
The application calls for the approver
AME returns the full approver list
It notifies the next approver or all the approvers in the list
Deals with approvers response
Business Learning Center
How AME Works???
List of approvers
AME evaluates the conditions associated with the rules of the transaction
Generates a list of approvers
Identifies the approver
Approval process is complete when there are no more approvers
It proceeds to the next step in the business process
Business Learning Center
AME Access
AME uses Oracle Role Based Access Model (RBAC) to access AME components
Oracle Approvals Management uses roles and responsibilities to define access levels. It provides security at two levels:
Data security, which enables you to define access to transaction types for a limited user role.
Function security, which enables you to define access to AME functions (modules) for a business analyst and administrator.
Business Learning Center
Grant access to roles
Approvals Management Business Analyst –
Transaction Type
In AME, a transaction type represents a set of transactions generated by a given application, for which AME maintains a single set of approval rules
A single application can have several transaction types
What will be approved – Invoice, requisition, salary change, Leave…
Custom transaction types can be created
Business Learning Center
Attribute
Attributes are business variables with a single value for a particular transaction
Examples of attributes are:
Business Learning Center
Condition
The if part of an approval rule consists of zero or more conditions.
A condition is a statement that is either true or false, for a given transaction. For the rule to apply to a transaction, all of its conditions must be true for the transaction
Types of conditions:
Action and Action Types
An approval rule's then part (its consequent) consists of one or more actions
Every action belongs to an action type. An action type is a collection of actions having similar functionality
AME provides all the action types and actions your implementation will require
Business Learning Center
Pre- and Post-Chain of Authority Action Types
Business Learning Center
Rules
Creating rules and rule use are the main steps in the AME implementation process
Rule associate one or more conditions with an approval in an if-then statement
You may need to create (or have a system administrator create) some custom attributes and/or approvals
You may also need to create some approver groups. Thus, while creating rules is your ultimate goal, it is also the last thing you do when you set up AME
Business Learning Center
List-creation rules
List-creation exceptions
List-modification rules
Test workbench
AME provides a testing workbench to allow defined business rules to be evaluated and tested against transactions
Testing workbench allows user to verify various aspects of setups
– Are attribute values, particularly custom attributes, retrieving values correctly?
– Does the invoice satisfy the appropriate rule?
– Is the proper approver chain being generated for the
transaction based on the rule chosen?
Business Learning Center
The Administrator Dashboard
The Administrator Dashboard is available only to users with the Application Administrator responsibility. The administrator can perform the following:
Set the configuration variables' default
Set the transaction type's configuration variables' values
Create a transaction type
Update a transaction type
Delete a transaction type
View the exception log
Clear the exception log
Run the Setup report
Organization: Business Learning Centre.
All the requests for leave go for a 2 level approval
We require to design an approval where all the vacation leaves applied for more than 6 days go for a one level approval and then further to the Head of the Department(Mr. Mehul Shah)
Business Learning Center
Venkataramana_Kolla
Srikant_Ganesan