Professional Documents
Culture Documents
(AME)
North
North Central
Central OAUG
OAUG
February
February 22,
22, 2008
2008
Jon Moll
Introduction
Jon Moll
• Senior Principal Consultant, O2Works LLC
• Ten years of Oracle applications experience
• Specializing in Financials and Projects
• Approved Oracle Instructor
• Frequent presenter at regional and national
conferences
2
© 2008 O2Works, LLC. All Rights Reserved.
Agenda
Agenda
1.
1.Overview
Overviewof
ofAME
AME
2.
2.AME
AMEBasics
Basics
3.
3.Workflow
Workflowand
andAME
AME
4.
4.Example
Example
3
© 2008 O2Works, LLC. All Rights Reserved.
1.
1. Overview
Overview of
of AME
AME
4
© 2008 O2Works, LLC. All Rights Reserved.
AME Versions
• AME.A (11.5.X) – FYI notifications, parallel approvals.
• AME.B (11.5.X, 12-delivered) 4428060 – Forwarding,
Role Based Access Control (security), use of OA
Framework , new user dashboards.
• AME.B RUP 1 (11.5.X, 12) 4873179 – Bug fixes, future
functionality.
• What version am I on? See Metalink note 368280.1
5
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Login as Administrator (APPSADMIN or
SYSADMIN)
• Create a new user with no responsibilities
6
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• User Management responsibility
• Users page
• Find user and click Update
7
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Select Assign Roles and search for Role
starting with Approval
9
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Verify roles are assigned to the user
10
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Switch to Functional Administrator
12
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• AME Transaction Types – All Rows
13
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Application Set = AME Calling Applications
14
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• If upgrading to AME.B, run Approvals
Management Post Upgrade concurrent
process under System Administrator
responsibility.
• Migrates existing AME users.
15
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Set AME:Installed profile for calling
applications
16
© 2008 O2Works, LLC. All Rights Reserved.
Initial Setup Steps
• Set application-specific setups
17
© 2008 O2Works, LLC. All Rights Reserved.
Approvals Management Administrator
Full access to all AME functions
18
© 2008 O2Works, LLC. All Rights Reserved.
Approvals
Approvals Management
Management Business
Business Analyst
Analyst
Functional Access
19
© 2008 O2Works, LLC. All Rights Reserved.
2.
2. AME
AME Basics
Basics
• Transaction Type – A distinct set of approval rules
applied by the integrating application.
– Payables Invoice Approval
– Oracle Self-Service Human Resources
• Attribute – Variable with a single value for a
transaction. Mandatory, required or other
(optional). Boolean, Number, String, Date, Currency.
– Static (set for all transactions)
– Dynamic (set by a SQL statement at runtime)
20
© 2008 O2Works, LLC. All Rights Reserved.
Approval
Approval Rule
Rule
Business rule that determines the approval
process used by a transaction. Constructed
with conditions and actions.
– If invoice amount > $1000 USD (condition), THEN
use supervisor chain of requestor (action) to go up
two levels.
21
© 2008 O2Works, LLC. All Rights Reserved.
Approval
Approval Rule
Rule
If
invoice amount > $1000 USD,
condition
THEN
use supervisor chain of requestor to go up two levels.
action
22
© 2008 O2Works, LLC. All Rights Reserved.
Condition
Condition Type
Type
• Ordinary – Evaluates dates, numbers,
currencies.
• List-Modifier – checks for a given approver.
23
© 2008 O2Works, LLC. All Rights Reserved.
Action Type
• Chain of Authority – Uses HR supervisory or
HR position hierarchies.
• List Modification
• Substitution
• Pre Approval Group
• Post Approval Group
24
© 2008 O2Works, LLC. All Rights Reserved.
Action Type – Chain of Authority
• HR Supervisory – Requires population of attribute
TOP_SUPERVISORY_PERSON_ID.
– Absolute-Job-Level - Starts with
TRANSACTION_REQUESTOR_PERSON_ID and climbs to the nth level.
– Relative-Job-Level – Considers the difference between
requestor and approver’s job level. Climbs n levels.
– Dual-Chains-of-Authority – requires FIRST_STARTING_POINT
PERSON_ID , SECOND_STARTING_POINT_PERSON_ID
25
© 2008 O2Works, LLC. All Rights Reserved.
Action Type – Chain of Authority
• HR Position – Uses primary position structure
of the BG, or NON_DEFAULT_POSITION_STRUCTURE_ID.
– HR Position – Ends with specified position.
– HR Position Level – Climbs n positions.
26
© 2008 O2Works, LLC. All Rights Reserved.
Action Type – List Modification
• Final Authority – Grants signing authority to
an approver.
• Nonfinal Authority – Extends chain authority
n levels past an approver (uses jobs).
27
© 2008 O2Works, LLC. All Rights Reserved.
Action Type – Substitution
• Substitution – Replaces the target approver
with another.
28
© 2008 O2Works, LLC. All Rights Reserved.
Action Type – Pre and Post
• Pre List – Inserts an approval group before the
authority list.
• Post List – Inserts an approval group after the
authority list.
29
© 2008 O2Works, LLC. All Rights Reserved.
Approver
Approver Group
Group
• Set of one or more approvers typically used
outside the normal transaction chain of
authority.
• Members and groups have order numbers.
• Groups can be nested.
• ALLOW_EMPTY_APPROVAL_GROUPS
attribute.
• Voting Regime is assigned to the group.
30
© 2008 O2Works, LLC. All Rights Reserved.
Approver
Approver Group – Membership List
• Static – Chosen while creating or editing the
group.
• Dynamic – Chosen by SQL query entered
during creation of group. Query results
either:
– person_id:<person_id> or user_id:<user_id>
– wf_roles
– Can return multiple values.
31
© 2008 O2Works, LLC. All Rights Reserved.
Approver Group – Voting Regimes
• Serial – Members are notified one after the other
according to their member order (ties broken
arbitrarily). All members must approve.
• Consensus – Members notified in parallel. All
must approve.
• First-Responder-Wins - Members notified in
parallel. First responder = group’s decision.
• Order-Number – Members notified according to
order, ties notified in parallel. All must respond.
32
© 2008 O2Works, LLC. All Rights Reserved.
Approval Rules
• List-Creation
• If invoice amount > $1000 USD (condition), THEN require
approval one job levels above requestor.
• List-Creation Exception
– If invoice amount > $500 USD and pay group = Employee,
THEN require approval two job levels above requestor.
• List-Modification
– If any approver = Sam Clark, THEN grant final authority.
• Pre and Post
– If expenditure category = Computers, THEN require approval
from IS department.
33
© 2008 O2Works, LLC. All Rights Reserved.
Conflict Resolution
Resolution
• A person should only approve once.
• If chain-of-authority and pre or post approval
rule include the same person, chain-of-
authority wins.
• If pre and post rules include the same person,
pre wins.
34
© 2008 O2Works, LLC. All Rights Reserved.
3.
3.Workflow
Workflow and
andAME
AME
35
© 2008 O2Works, LLC. All Rights Reserved.
Requisition Approval
36
© 2008 O2Works, LLC. All Rights Reserved.
1.
1. Example
Example
37
© 2008 O2Works, LLC. All Rights Reserved.
Example - Attributes
38
© 2008 O2Works, LLC. All Rights Reserved.
Example - Conditions
39
© 2008 O2Works, LLC. All Rights Reserved.
Example – Approver Groups
40
© 2008 O2Works, LLC. All Rights Reserved.
Example - Rules
41
© 2008 O2Works, LLC. All Rights Reserved.
Example - Testing
42
© 2008 O2Works, LLC. All Rights Reserved.
Example - Testing
43
© 2008 O2Works, LLC. All Rights Reserved.
Example - Testing
44
© 2008 O2Works, LLC. All Rights Reserved.
Example - Testing
45
© 2008 O2Works, LLC. All Rights Reserved.
Questions?
Jon Moll
jon@o2works.com
O2Works LLC
Dallas – Chicago - Denver