Agenda

 AME Overview
– Business Processes for Transactions
and Approvals
– Approval Policies / AME Components
 AME components
 SSHR AME Integration
 Tool to view AME Rules
 How AME Can be used?
 Useful Links
 Q&A

1
 AME Overview
 AME is a powerful self-service Web application. It provides a great
deal of flexibility for creating the approval processes an organization
needs, usually without writing any custom code

 Advantages
– Minimal Coding required. One time setup
– No Customization in base application
– One time definition
– AME directly communicates with transactions from base
application
– Built in Testing features to test a new/existing rules

2
 Business Processes for
Transactions
and Approvals3
Manage
Approvals
Create 1 and
Transactio Notifications
n
• Approve
• Reject
2 Submit • Return
for
Approval
Update
4
when
approved

3
 AME Architecture & Components
 AME Architecture
– Pre Approval Groups
– Chain of Authority
– Post Approval Groups

 Components
– Attributes
– Conditions
– Actions (Approvals)
– Approval Groups
– Rules
 If <condition> = true
 Then <action>
– Test Workbench

4
 More on AME Components
 Rule = Condition + Action
 Action Types: Actions are of various types as mentioned below:
– post-chain-of-authority approvals
– pre-chain-of-authority approvals
– dual chains of authority
– absolute job level
– supervisory level
 Transaction Types: An application that uses AME to govern its approval process is
called ‘originating application’ . An originating application may divide its transactions into
several categories where each category requires a distinct set of rules. Each set of rules
is called ‘Transaction Type’.
– Transaction Types under ‘PER’ (HRMS) Application :
 Oracle Self Service Human Resources
 Oracle HRMS Self Service
 iRecruitment Offer Approval
 iRecruitment Vacancy Approval
 Approval Groups: Approval groups are generally defined to contain approvers who are
usually members of peer groups such as payroll or the HR department, I.e outside the
chains of authority. Approval parallelization can be obtained via Approval groups.

5
 Current Features in AME
– Rules based on evaluation of Conditions & Attributes
– Can define distinct rules for Pre-Approval, Approval and Post-
Approval
– Approval Types (seeded)
 Job Levels – (Absolute & Relative)
 Supervisor Hierarchy (Absolute)
 Manager & Final Approver, Final Approver Only
 Dual chain of authority, Approval Group Chain
– Static & Dynamic Approval Groups
– List Modification, Substitution Rules, & Ad-hoc
 Non-Final & Grant Final Authority
 If a specific condition exists then substitute approver
 Add/remove/replace a person/user

6
 SSHR AME Integration
 Oracle SSHR integrates directly with AME
using the standard AME supplied API’s
 The standard AME package in 11.5.10 is
‘ame_api2’

7
 How AME can be used?
 Responsibility “Approvals Management Business
Analyst” is defined , which gives the following utilities
to the business users:

– View all the existing AME rules and associated Objects for
a particular transaction type

– View the approval status of a current Transaction.

– View the applicable rules and approvals required for any

active transaction

8
AME Demo

9
Business Analyst Dashboard

10
AME Attributes

11
AME Attributes

12
AME Conditions

13
AME Conditions

14
AME Action Types

15
AME Rules

16
AME Rules

17
Test Workbench

18
AME Approval Groups

19
Test Workbench - Attributes

20
Test Workbench - Attributes

21
Test Workbench – Applicable
Rules

22
Test Workbench – Approval
List/Status

23