1.

Oracle AME (Approvals Management Engine) Training Dharma

lingam Kandampalayam Shanmugam, OCP, PMP
2. Agenda Introduction AME What and When Setup Details
Profles, Assign roles & grants Implementation Guidelines Limitations and
References Case study & Demo Q&A
3. AME What is it? AME is a simple to use Rules Engine for
Defning Approval Policy AME is generic engine can be used where no
integration currently exist, even with non EBS modules Standardizing on
one engine reduces costs for customer as well as consulting since only one
set of skills required None or only minimal coding required to setup rules
4. AME When can it be used? AME can be used to derive lists of
approvers based on user defned rules and maintain a history of approvers
statuses when: - Transferring employees from one division/cost centre to
another Authorizing expenses Paying invoices Approval of Purchase
Requisition Much more review EBS Module Integration List
5. AME Module Integration List 11i8/9 11i10 E-Records (ERES)
User Management iSupplier Quoting ODM BOM Sourcing Accounts
Payable ODM Engineering iProcurement Credit Management ODM
Inventory R12 iExpenses ODM Quality Mgt E-Tax Lease Management
ODM Receiving Grants iRecruitment ODM WIP Core Pay Training
Administration (SS) AR Credit Memo Public Sector Self Service HR (4.1)
Internal Controls Mgr Proposals OPM Inventory OTA Learner UI
Distribution OPM - New Product Dev OTA Manager UI GL-Journals OPM
Process Execution iAssets (Transfer) Account Planning OPM Quality
Mgt. Deal Registration Service Contracts Oracle Partners Mgt Referral
Management Collections AR Credit Mgt PO - Requisitions Incentive
Comp
6. Business Processes for Transactions and approvals Create
Transaction Manage Approvals and Notifcations Approve Reject Return
Submit for Approval Update when approved 1 3 2 4
7. Approval Policies AME Rules Approval Policies translate to
rules in AME and are made up of the following components: if and then
Transaction Category In {Salary} Salary Increase Pct > 15 require
approvals up to the frst two superiors Rule Conditions Action Types
Attributes require post approval from CIO
8. Setup Details Profle Options AME responsibilities can be
directly assigned in 11i.AME.A. But in 11i.AME.B & R12 & higher, the
responsibilities are assigned through roles. AME: Installed Set this profle
value to Yes at required application level. HR:Defer Update After Approval:
Set this profle value to No to avoid the status Pending Approval after
transactions approval. AME: Append to List option on Approvers region
To control the requesters/initiators to append approvers to the approval list.
If set to the value No would not allow the users to append the list.
9. AME How to assign the role? Login as System Administrator
(not a responsibility) & navigate to User Management > Users > Query the
user and click Update > Search & Add the AM Admin roles as shown below
10. AME How to grant transaction type access to users? AME
restricts access to transaction types using Data Security. Grant users
access to the transaction types using the Grants page. Login as Functional
Administrator responsibility & click on Create Grant
11. AME How to grant transaction type access to users?
12. AME How to grant transaction type access to users?
13. Setup Details Confguration Variables Important confguration
variables are shown below: Please note the values for these variables can
vary for each transaction type.
14. Setup Details New Transaction Type A new transaction type
can be created using Approvals Management Administrator responsibility
15. Setup Details New Transaction Type There are 4 steps in
creating a new transaction type The new transaction type can be created
with diferent item classes like Header, Line Item, Cost Center, Project, etc
depending on the requirement
16. Setup Details New Transaction Type There are 11 mandatory
attributes whose values can be derived using SQL queries
17. Setup Details Approval Process The approval process for the
newly created transaction type can be setup using Approvals Management
Business Analyst responsibility.
18. Setup Details Attribute Attributes are the base element for an
AME Rule. Attribute values are retrieved from the EBS Applications
database AME is seeded with attributes relevant to the transaction type
and the user can create new attributes in AME for use in AME rule
19. Setup Details Condition Conditions identify values and value
ranges for some or all of the attributes available AME rules refer to these
conditions to determine if a particular rule is applicable for the specifc
document (requisition) being approved There are 2 types of conditions
Regular & List Modifers
20. Setup Details Action Type An action type is a collection of
actions having similar functionality Every action belongs to an action type.
Action types are enabled or disabled for a particular transaction type Voting
method (or regime) decides how the responses to the action types are
treated
21. Setup Details Approver Group It is an optional setup.
Required only when additional approvers are required for particular
conditions The rules defned for the transaction can be based on Approver
Groups, Jobs defned in HR setup, or Positions defned in HR setup
Additional approvers are added here
22. Setup Details Rule Rules specify approvers to be included in
the approval list under specifc conditions Rule category can be either
approver or FYI
23. Setup Details Rule Actions are added from action type
associated with the transaction type
24. Setup Details Test Workbench This is used to determine
which AME rules apply to a specifc document (requisition) Test cases with
values for various attributes can be saved for repeated use
25. Setup Details Test Workbench For real transaction test,
requisitions header ID need to be entered as transaction ID. This would
pull values for all the attributes
26. Setup Details Test Workbench Final approver list is displayed
along with the applicable rules
27. Setup Report A setup report can be run from Business
Analysts dashboard which would show all the attributes, conditions, rules
used in the transaction type. A sample output of the report is attached
below
28. Implementation Guidelines Read the Implementation Guide
never go in blind, you will make mistakes Some SQL and EBS entities
knowledge required if additional Attributes or Dynamic Approval Groups
needed Design approval matrix / decision tree on paper and use that as
basis for your rules Dont create custom Action Types unless you really
have to If DFFs need to be used in AME, then custom attributes need to be
created using SQL query Purge transaction data using the concurrent
program Approvals Management Transaction Data Purge In 11.5.10 AME
supports only employee-supervisor hierarchy. But in R12, position
hierarchy & FYI notifcations are supported.
29. Implementation Guidelines Approval Decision Tree Model the
decision tree based on the approval rules. Path from the root node to a leaf
node represents a rule
30. Error Messages Approval List could not be generated. Please
contact your System Administrator to review AME rules setup. The
procedure getNextPosition could not fnd parent position for : HR Positions:
MM400.Materials Manager
31. Limitations Terminations (of the initiators) are not handled
efciently though AME would rebuild the chain of approval after each
approval Not possible to create custom AME responsibilities because of
RBAC limitations other than the 2 seeded responsibilities Approvals
Management Administrator', 'Approvals Management Business Analyst' It
is not possible to have Notifcation TimeOuts with Reminders within AME.
32. References How to Create the Approval Transaction Type for
AME.B or higher ( Metalink Note: 420387.1 ) How To Setup And Use AME
For Purchase Requisition Approvals ( Metalink Note: 434143.1 ) How To
Diagnose Issues in Building The Requisition Approval List ( Metalink Note:
412833.1 ) How to Create the Approval Transaction Type for AME.A
( Metalink Note: 420381.1 ) Frequently asked Questions on AME 11i
( Metalink Note: 431815.1 ) 11.5.10 FAQ for Approvals Management (AME)
Integration For iProcurement and Purchasing ( Metalink Note: 293315.1 )
33. Case Study Requirements / Approval Policies: If the total
requisition value is more than 25,000 USD, then it requires approval from 2
positions above the requestor. If it is less than 25,000 USD, then it can be
approved by the requestor himself if he has enough approval authority If
any of the requisition line has an item category COMPUTER.PC, then it
needs to be approved by a specifc user If any of the line item has an item
category COMPUTER.MISC, then IT Director position needs to be
notifed Let us now see in the application, how these policies are modeled -
Demo
34. Thank You A Q &