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
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
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.
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
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.
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.
• Business Analyst Dashboard.
Administrator Dashboard:
FUNCTIONAL COMPONENTS:
• Transaction Type
• Attributes
• Condition
• Action
• Approver Group
• Rules
Transaction Type is the root entity under which all the approval policies and related
setup for a particular transaction flow are grouped together.
Conditions in AME are statements against which the business facts are evaluated
against for a transaction.
For example,
• TOTAL_REQ_AMOUNT > 5,000
• COST_CENTER in {YAX1, YEC1}
Group Based
• Approval Group Chain of Authority
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
Approver Group:
An Approver Group is a ordered set of one or more approver; Usually contains
those approvers who do not fall under a certain hierarchy.
For example,
For certain in a company, for certain chemical items procurement, R&D
department manager needs to approve the Requisition. But there exists no
relationship between preparer and R&D Manager. This relationship can be defined
using Approver group.
Approver Lists:
A complete list of approvers generated by AME for a transaction is called as its
approver list. The initial approver list may not be same as the final approver list
when the approval process completes.An approver list can be divided into 3 sub
parts (or sub-lists) – they are ‘pre’, ‘chain-of-authority’ and ‘post’
A chain-of-authority (COA) is the sub list, which is generated using one of the
chain of authority/list creation based action type (like supervisory action type).
‘Pre’ and ‘Post’ sub lists are usually approvers generated by a group.
Step 1:
Create New Approver Group:
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.
Conditions defined for the transaction type is linked to the rule here. On clicking
“Add Condition”, the following page is displayed.
Actions defined are linked to the Rule in this page. Action type is selected from the
combo and appropriate Action is also selected.
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:
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
• adminApprover
• allowAllApproverTypes
• allowAllItemClassRules
• allowFyiNotifications
• productionFunctionality
• repeatedApprovers
PARALLELIZATION CONCEPTS:
Voting Methods/Regimes:
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
• First Responder Wins
• Order-number
Serial
Consensus
You can manually set the Order in which approvers receive their
notifications.
DIAGNOSTICS:
AME IN R12:
In R12, following are the main features implemented in Requisition Approval.
Position hierarchy support - Prior to R12, only employee - supervisor hierarchy was
used in AME. In R12, customers can configure position hierarchy approver group
for Requsition Approvals.
Customers who use position hierarchy for their regular approval process are greatly
benefitted by this.
Parallel approval support -Requisition approvals with AME integration supports
parallel approvals. This means send parallel notifications (notify all members of the
group at the same time).
Support for FYI Notifications - AME can now send FYI Notifications to required
persons.
• http://hcmwiki.uk.oracle.com/ame/index.php/Main_Page
• Note.428552.1 How To Diagnose Issues With Approvals Management
Engine (AME) In Procurement
Employee :
Created three employees.
• EMPLOYEE BYR
• EMPLOYEE APR
• EMPLOYEE MGR
EMPLOYEE BYR reports to EMPLOYEE APR.
EMPLOYEE APR reports to EMPLOYEE MGR.
Attribute :
Created one attribute. Demo_Requisition_total.
This will accommodate the Requisition’s total value.
Name 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 The following query is used :
Condition :
Created one condition.
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 1
Condition DEMO_REQUISITION_TOTAL is greater than 10000 and less
than or equal to 50000,USD
Action Type Action type will be changed for each scenario
Following action types are covered in the Viewlets:
ACKNOWLEDGEMENT
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