Oracle Approvals Management (AME) Atlanta Oracle User Group January 18, 2008 Jon Moll.

Oracle Approvals Management(AME)

Atlanta Oracle User GroupJanuary 18, 2008

Oracle Approvals Management(AME)

Atlanta Oracle User GroupJanuary 18, 2008

Jon Moll

© 2008 O2Works, LLC. All Rights Reserved.2

IntroductionIntroduction

• 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

Jon Moll


AgendaAgenda

1. Overview of AME1. Overview of AME

2. AME Basics2. AME Basics

3. Workflow and AME3. Workflow and AME

4. Example4. Example


• Builds a list of approvers for a specific transaction using business rules.

• Mostly functional configuration in a self-service application.

• Common platform integrated with Oracle Applications.

1. Overview of AME1. Overview of AME


AME VersionsAME 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


Initial Setup StepsInitial Setup Steps• Login as Administrator (APPSADMIN or

SYSADMIN)• Create a new user with no responsibilities


Initial Setup StepsInitial Setup Steps• User Management responsibility• Users page• Find user and click Update


Initial Setup StepsInitial Setup Steps• Select Assign Roles and search for Role

starting with Approval

• Add all roles to the user


Initial Setup StepsInitial Setup Steps• Fill out Justification for each role and save.


Initial Setup StepsInitial Setup Steps• Verify roles are assigned to the user


Initial Setup StepsInitial Setup Steps• Switch to Functional Administrator

• Select Create Grant


Initial Setup StepsInitial Setup Steps


Initial Setup StepsInitial Setup Steps• AME Transaction Types – All Rows



• Application Set = AME Calling Applications

• Proceed to last page and select Finish



• If upgrading to AME.B, run Approvals Management Post Upgrade concurrent process under System Administrator responsibility.

• Migrates existing AME users.



• Set AME:Installed profile for calling applications



• Set application-specific setups


Approvals Management AdministratorApprovals Management AdministratorFull access to all AME functions


Approvals Management Business AnalystApprovals Management Business AnalystFunctional Access


• 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)

2. AME Basics2. AME Basics


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.

Approval RuleApproval Rule


If invoice amount > $1000 USD,

THEN use supervisor chain of requestor to go up two levels.

Approval RuleApproval Rule

condition

action


• Ordinary – Evaluates dates, numbers, currencies.

• List-Modifier – checks for a given approver.

Condition TypeCondition Type


• Chain of Authority – Uses HR supervisory or HR position hierarchies.

• List Modification• Substitution• Pre Approval Group• Post Approval Group

Action TypeAction Type


• 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

– Supervisory-Level – Climbs n levels, disregarding jobs.

Action Type – Chain of AuthorityAction 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.

Action Type – Chain of AuthorityAction Type – Chain of Authority


• Final Authority – Grants signing authority to an approver.

• Nonfinal Authority – Extends chain authority n levels past an approver (uses jobs).

Action Type – List ModificationAction Type – List Modification


• Substitution – Replaces the target approver with another.

Action Type – SubstitutionAction Type – Substitution


• Pre List – Inserts an approval group before the authority list.

• Post List – Inserts an approval group after the authority list.

Action Type – Pre and PostAction Type – Pre and Post


• 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.

Approver GroupApprover Group


• 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.

Approver Group – Membership ListApprover Group – Membership List


• 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.

Approver Group – Voting RegimesApprover Group – Voting Regimes


• 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.

Approval RulesApproval Rules


• 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.

Conflict ResolutionConflict Resolution


• Oracle Workflow calls AME to get approvers.

• Notifications are sent via Workflow engine.• Configure approvers using AME, messages

and behavior upon approve/reject using Workflow.

3. Workflow and AME3. Workflow and AME

© 2008 O2Works, LLC. All Rights Reserved.

Requisition ApprovalRequisition Approval

36


• If project type is Indirect, require requisition approval by Project Manager and then requester’s immediate supervisor.

1. Example1. Example


Example - AttributesExample - Attributes

38


Example - ConditionsExample - Conditions

39


Example – Approver GroupsExample – Approver Groups

40


Example - RulesExample - Rules

41


Example - TestingExample - Testing

42



43



44



45

Questions?Questions?

Jon [email protected]

O2Works LLCDallas – Chicago - Denver

Oracle Approvals Management (AME) Atlanta Oracle User Group January 18, 2008 Jon Moll.

Documents

initial setup stepsset

initial setup stepsswitch

initial setup stepslogin

initial setup stepsfill

initial setup stepsif

ame functions

ame versionsame

ame basics3