Professional Documents
Culture Documents
Introduction ....................................................................................................... 4
Requisition Approval Process in AME.......................................................... 5
Approval Routing Chooser in Requisition Approval Workflow: ..... 6
AME Approval List Routing: ................................................................. 6
What AME Does and Does not do? .............................................................. 8
What AME Does?......................................................................................... 8
What AME Does Not Do? ......................................................................... 8
Setup in Core Purchasing:................................................................................ 9
AME-A Concepts............................................................................................ 10
AME- B Concepts........................................................................................... 10
OAF Approach: .......................................................................................... 10
Administrator Dashboard: .................................................................... 10
Business Analyst Dashboard: ............................................................... 11
Functional Components:................................................................................ 12
Transaction Type: ....................................................................................... 13
Attributes: .................................................................................................... 14
Conditions:................................................................................................... 15
Actions:......................................................................................................... 16
Pre-defined Action Types ..................................................................... 16
Approver Group: ........................................................................................ 17
Approver Lists:............................................................................................ 17
Rules: ............................................................................................................ 19
Item Class:.................................................................................................... 22
Configuration Variables: ............................................................................ 23
General Configuration Variables: ............................................................. 23
Parallelization Concepts: ................................................................................ 24
Voting Methods/Regimes: ........................................................................ 24
Serial ......................................................................................................... 24
Consensus................................................................................................ 24
First Responder Wins ............................................................................ 24
Order-Number ....................................................................................... 25
Diagnostics: ...................................................................................................... 25
AME in R12: .................................................................................................... 25
References : ...................................................................................................... 26
Test Case Scenario (Demo in Viewlets):...................................................... 26
Employee : ................................................................................................... 26
Attribute : ..................................................................................................... 26
Page 2
Condition : ................................................................................................... 27
Rule: .............................................................................................................. 27
Acknowledgement........................................................................................... 28
Page 3
INTRODUCTION
AME provides a central business rules repository and a common execution engine,
integrated with Oracle Workflow, to manage approvals for the business processes
delivered within the Oracle eBusiness Suite. Oracle Approvals Management (AME)
is available for Purchasing and iProcurement from Family Pack 'J' (11.5.10)
onwards. Current limitation in 11.5.10.2 is, AME is integrated only with Purchasing
Requisitions when using Employee/Supervisor relationships. AME does not
support Position Hierarchies nor Purchase Order Approvals workflow at this time.
However in R12 Position Hierarchy is supported.
FEATURES
Page 4
Page 5
This process in Requisition Approval Workflow is used to choose the route it has
to follow to get the approvers. There are two routes AME Approval list route or
normal Approval list route.
AME Approval List Routing:
Page 6
The calling application (Requisition Approval) calls AME from Workflow to get
next approver. Firstly the Requisition Approval workflow (REQAPPRV) validates
the setup for this document type / sub-type (AME_TRANSACTION_TYPE from
table PO_DOCUMENT_TYPES) and sets the workflow attribute
(IS_AME_APPROVAL) accordingly. To retrieve the next approver, the workflow
makes a call to procurement PL/SQL procedure, which in turn makes a call to
AME (using API getNextApprover) to find the right values. The results (or 'No
Approver Found' warning) are returned, and placed into the workflow attributes,
for onward processing. When workflow responses are processed, after validation
and initial processing, the PL/SQL calls again go to AME API's to update the
approver list and return the next approver.
AME evaluates applicable rules and generates an approver list. It then returns the
next approver. The calling application notifies next approver. The calling
application deals with approvers response Approve, Reject or Return and sends
response to AME.The calling application repeats these steps until no more
approvers are found. The function called here is Get Next Approver Using
AME.
Function: POR_AME_APPROVAL_LIST_WF1S.GET_NEXT_APPROVER
This function generates the list of approvers and from that it gets the next approver
to whom Notification is to be sent.
Most of the processing between iProcurement and AME is done in PL/SQL
package POR_AME_APPROVAL_LIST_WF1S (file: POXAME1B.pls).
Package POR_AME_APPROVAL_LIST_WF1S in file: POXAME1B.pls
Package POR_AME_APPROVAL_LIST in file: POXAPL2B.pls
Package REQAPPROVAL_INIT1 in file: POXWPA1B.pls
Package PO_APPROVALLIST_S1 in file: POXAPL1B.pls
Package PO_AME_SETUP_PVT in file: POXAMESB.pls (Release 12.x)
Package AME_API in file: ameeapin.pkb (and later ameeapi2.pkb)
Package AME_ENGINE in file: ameeengi.pkb
Workflow REQAPPRV in file: poxwfrqa.wft
Page 7
Page 8
If Approval transaction type is given a value, then Requisition will use AME for
approvals.
For Purchase Requisition, the value is PURCHASE_REQ
For Internal Requisition, the value is INTERNAL_REQ
These are seeded values defined in the table ame_calling_apps.
If Approval transaction type is Blank, AME will not be used for approvals.
Page 9
AME-A CONCEPTS
AME-A is the first version on AME. AME-A provides a single web page for
administration and setup. So, both the AME Business Analyst and Administrator
will have the rights to use the same responsibility. There are seven tabs in the
Approvals Management page. They are Attributes, Conditions, Actions, Groups,
Rules, Test and Admin.These will be covered later on in the whitepaper document.
Users have to select the transaction type and proceed with either setup or testing or
administration.
AME- B CONCEPTS
OAF Approach:
There are two entry points to AME. These are role based. One for Business
Analyst and another for Administrator.
Administrator Dashboard.
Administrator Dashboard:
Page 10
Page 11
Within setup the user / Oracle Dev teams, would define the objects that are
required before approval rules can be created.
FUNCTIONAL COMPONENTS:
Transaction Type
Attributes
Condition
Action
Approver Group
Rules
Page 12
Transaction Type:
Transaction Type is the root entity under which all the approval policies and related
setup for a particular transaction flow are grouped together.
Page 13
Attributes:
Requisition Total.
Item UOM.
Page 14
Conditions:
Conditions in AME are statements against which the business facts are evaluated
against for a transaction.
For example,
Page 15
Actions:
Supervisory Level
Position Based
HR Position Level
HR Position
Group Based
You can create your own Action Types, however you will need to write your own
PL/SQL handlers to tell AME how to handle this Action Type. This is not an easy
task. Anyhow, AME Development has seeded an extensive list of Action Types to
Page 16
be used, so there should no need to do this. If there were a Business Case for a new
Action Type, it would be best to contact the AME Development team.
Approver Group:
Page 17
This is the first page for Approver Group creation. An unique name for the
Approver Group is specified here along with Description Order Number in which
this Approver Group needs to be given preference, Voting method & Usage Type.
Usage type is of two types.
Static
Dynamic.
If Usage Type is given as dynamic, a query needs to be specified in Query field that
will be executed to generate approvers. If Usage type is Static, Approvers are
manually added which can be seen in the next picture.
Approver Type can be FND Users, Nested Group, HR People, HR Positions &
Position Control Roles. Order Number decides to which approver, Requisition
should be sent first.
Note: Upto 11.5.10.2, Voting method should be Serial for Requisition Transaction
types.
Page 18
Rules:
Approval Policies translates into a Rule in AME and are made up of the following
components
Rules can be dated (can specify the life span of it). This is called as Rule
Usage
Page 19
This is the first page for rule creation. An unique name for the rule is specified here
along with Rule type Item Class & Effective dates.
Step 2: (Add Conditions)
Conditions defined for the transaction type is linked to the rule here. On clicking
Add Condition, the following page is displayed.
Page 20
Actions defined are linked to the Rule in this page. Action type is selected from the
combo and appropriate Action is also selected.
Page 21
Step 4: (Review)
This is the Review page that shows that the Conditions and Action Type linked to
the Rule. On clicking Finish, the Rule will be created for the corresponding
transaction type specified.
Item Class:
Line
Page 22
Configuration Variables:
They work similar to FND Profiles in Applications (in the fact that they override
each other at different levels). They are delivered at the following levels:
4) Global (default)
5) Transaction Type
General Configuration Variables:
adminApprover
allowAllApproverTypes
allowAllItemClassRules
allowFyiNotifications
productionFunctionality
repeatedApprovers
Page 23
forwardingBehaviour
rulePriorityModes
purgeFrequency
currencyConversionWindow
distributedEnvironment
PARALLELIZATION CONCEPTS:
Voting method in AME determines in what order the notifications are to be sent to
approvers and how the approver responses should be tackled. AME provides the
voting methods for action-types and approver groups. The following 4 voting
methods
Serial
Consensus
Order-number
Serial
Page 24
Order-Number
You can manually set the Order in which approvers receive their
notifications.
A and B
2nd:
3rd:
D and E
DIAGNOSTICS:
AME IN R12:
Page 25
REFERENCES :
http://hcmwiki.uk.oracle.com/ame/index.php/Main_Page
Employee :
EMPLOYEE BYR
EMPLOYEE APR
EMPLOYEE MGR
Attribute :
DEMO_REQUISITION_TOTAL
Item Class
Header
Description
RequisitionTotal
Data Type
Currency
Approver Type
None
Usage Type
Dynamic
Value Set
Category
Others
Action Types
None
Value
Page 26
Condition :
Condition Type
Ordinary
Item Class
Header
Attribute Name
DEMO_REQUISITION_TOTAL
Data Type
Currency
Condition
DEMO_REQUISITION_TOTAL is greater than 10000 and less
than or equal to 50000,USD
All the rules will be tested based on the above attribute and condition.
Rule:
Name
Demo Rule
Rule Type
List Creation
Item Class
Header
Start Date
18-Oct-2007
End Date
31-Dec-4712
Priority
Condition
DEMO_REQUISITION_TOTAL is greater than 10000 and less
than or equal to 50000,USD
Action Type
Page 27
Action Type:
Supervisory Level
Action :
Action Type:
Supervisory Level
Action:
Action Type:
Action:
Action Type:
Action:
Action Type:
Action:
Action Type:
Approvers:
Action Type:
Approvers:
ACKNOWLEDGEMENT
Page 28
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com
Copyright 2007, Oracle. All rights reserved.
This document is provided for information purposes only and the
contents hereof are subject to change without notice.
This document is not warranted to be error-free, nor subject to any
other warranties or conditions, whether expressed orally or implied
in law, including implied warranties and conditions of merchantability
or fitness for a particular purpose. We specifically disclaim any
liability with respect to this document and no contractual obligations
are formed either directly or indirectly by this document. This document
may not be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without our prior written permission.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.