Professional Documents
Culture Documents
Agenda
AME Basics
AME Implementation Examples
AP Setup
Requisition Setup
Advantages of AME
Approval Rules can be developed without
programming knowledge
Approver Lists leverage off existing Oracle
hierarchies (e.g. HR supervisor, HR position)
AME responds to changes such as organization
hierarchies or rule changes
Flexible combine hierarchy types
Alternative to AME is workflow customization
Minimize approval routing maintenance
Reduce approval cycle times
4
Limitations of AME
Timeout functionality is not supported in AME
Workflow can be customized, but timeout goes up
supervisor chain not back to AME
AME Components
Configuration Variables
Transaction Types
Attributes
Conditions
Actions / Action Types
Approver Groups
Rules
Configuration Variables
Default values apply to all transaction types
Allow FYI Notifications
Transaction Types
Describe the type of transaction on which approval
rules will be based (e.g. Invoice Approval)
178 Transaction Types in 11.5.10.2
251 Transaction Types in Release 12
Attributes
Variables that represents business data (e.g.
invoice amount, supplier, etc.)
Building blocks of rule development
Can be static (constant value) or dynamically
retrieved at runtime (SQL query)
Basic attributes seeded for transaction types
Create additional attributes for anything linked to
transaction id for header (invoice id, requisition id)
10
11
Use ame_util.booleanAttributeTrue or
ame_util.booleanAttributeFalse to ensure proper
format
12
Attributes - Types
Mandatory Attributes
13
Attributes - Types
Required Attributes
14
Attributes - Types
Optional Attributes Any other attributes defined
for a transaction type
This attribute calls a
function to
determine the
number of
supervisors to go
up to reach a
specified approval
amount based on a
custom table
15
Conditions
Used to evaluate the value of attributes at runtime
Condition result can either be True or False
Represent the IF part of an approval rule
Three types of conditions
Ordinary-Regular
Ordinary-Exception
List Modifier
16
Conditions - Types
Ordinary-Regular
Associates attribute with a defined value or range of
values (e.g. invoice amount > 10000)
17
Conditions - Types
Ordinary-Exception
Similar to Ordinary-Regular, but can only be used in
certain Rule Types (e.g. use regular rules except for
Utility suppliers)
18
Conditions - Types
List-Modification
Determines if specified approver appears in an approver
list (e.g. can be used for conflict of interest checking)
19
20
Action Types/Actions
Action Type
Description
Example
Absolute-job-level
~Ascends HR
supervisor hierarchy
~Based on specific
job level
Require approvals up
to at least job level six
Specific purchase
types
Relative-job-level
~Ascends HR
Require approvals at
supervisor hierarchy least four levels up
~Based on job level
Pay changes
relative to requesters
job level
22
Description
Example
Manager-then-FinalApprover
~Ascends HR
supervisor hierarchy
~Supervisor and final
approver are required
to approve
Require approval up
to first supervisor and
level six final
approver
Capital with CFO
approval
Final-Approver-Only
~Ascends HR
supervisor hierarchy
~Only final approver
needed for approval
Require approval
from level six final
approver
Reduce approval
cycle
23
Description
Example
Dual-Chains-of
Authority
~Ascends HR
supervisor hierarchy
~Builds two separate
approver lists
~Approval needed
from each list
Require approval
from previous and
current supervisor
(i.e. during employee
transfer)
Projects
Line-Item-Job-Level- ~Ascends HR
Approval Authority for supervisor hierarchy
Job
~Approver chain
based on line-level
attributes
Require approval
from manager of cost
center in account
code of distributions
Executive
24
Description
Example
Supervisory-Level
Ascends HR
supervisor hierarchy
a specified number of
levels
Require approvals up
to three supervisors
Expenses
HR-Position
Ascends HR position
hierarchy up to a
specified position
Require approvals up
to Accounting
Manager
HR approvals
25
Description
Example
Approver-Group
Chain-of-Authority
~Ascends custom
approver hierarchy
~Builds chain-ofauthority type
approver list
If transaction item
contains building
material
Approver groups
based on project
roles
Position-Level
Ascends HR position
hierarchy a specified
number of positions
Require approvals up
to position at level 4
HR Approvals
26
Description
Example
Final-Authority
If Approver is IT
Manager, allow final
approval
VP Approval
Non-Final-Authority
Revokes final
authority from an
approver by
extending approver
chain
If Approver is Harry,
require approval up to
one supervisor
Employee approval
for contractors
27
Description
Example
28
Description
Example
Substitution
Substitutes one
approver for another
use for vacation
rules
Substitute one
approver for another
Laterally or
delegate
29
Rules
The key component in AME application approval
setup
Represents the translation of an organization
business approval rule in AME
Associate one or more conditions to a rule
When the rule applies
30
31
32
33
34
Example:
35
APPROVALS UP TO 1 SUPERVISOR
Rule B: IF INVOICE_AMOUNT < 1000 AND (Exception)
COST_CENTER IS IN (0743) THEN REQUIRE APPROVALS UP
TO 2 SUPERVISORS
36
Examples:
38
39
Post-Chain of Authority
List-Modification
Substitution
Example:
41
AME
42
AME Setup
Install latest AME patchset
43
44
46
47
48
Select Document
Type: Purchase
Requisition
Set Approval
Transaction Type
=
PURCHASE_REQ
49
AME Dashboards
Current version 11i.AME.B delivers a dashboard
page to provide access to AME application
Dashboard page contents differ depending on
which AME role is assigned and accessed
AME Business Analyst dashboard provides birdseye view of AME setup components (e.g. attributes,
conditions, rules)
AME Administrator dashboard provides view to add
transaction types, item classes, approver types and
view the exception log
50
51
Administrator Dashboard
52
Business Case #1
Require Approvals up 1 level from invoice requester
for any invoice $100 or greater
The following AME components need to be defined
Attribute: Total Invoice Amount
Condition: Total Invoice Amount >= 100
Rule: If Total Invoice Amount >= 100, then
require approvals up to first supervisor
54
55
56
57
Business Case #2
Require pre-approval from the Tax Approver
group, for any invoices $100 or greater with Sales
Tax lines
The following New AME components need to be
defined
59
60
61
62
Business Case #3
Require pre-approval from key project members in
the following roles:
Project Manager
Technical Manager
Director
63
SB_PROJECT_MANAGER
SB_TECHNICAL_MANAGER
SB_DIRECTOR
New Rules
Pre-Approval Rule
Supervisor Rule
64
65
66
67
68
Business Case #3
Project
Invoice
69
Business Case #3
Require the following pre-approvals
Project Manager Pat
Technical Manager Lorraine
Director Susan
70
Business Case #3
Approval History from Invoice
Tools View Action History
71
72
73
74
75
76
Update
attributes
and save,
then run
test case
77
78
79
References
Oracle Approvals Management Implementation Guide Rel
11i Part No. B25324-01, MetaLink Note 336901.1
Oracle Approvals Management Developers Guide Release
AME.B, MetaLink Note 289927.1
How to Implement the Invoice Approval Workflow,
MetaLink Note 269057.1
Oracle Payables Users Guide 11i Part No. A81180-07
Oracle Approvals Management Not Enabled? What does it
take to Enabled It?, MetaLink Note 413300.1
About Oracle Approvals Management Minipack B,
MetaLink Note 336004.1
80
www.solutionbeacon.com
81
Got
Oracle?
Get the
Books!
The Release 12 Primer
Shining a Light on the
Release 12 World
Available
October 2007