Oracle Approvals Management

AME RULE
An approval rule is a
business rule that helps
determine a
transactions approval
process.

Rules are constructed
from conditions and
actions. For example an
approval rule.
Example:

WHAT CAN BE DONE BY AME:
Require subject-matter-expert approval.
Require managerial approval.
Create exceptions for rules requiring managerial
approval.
Substitute one approver for another in special cases.

AME IMPLEMENTATION PROCESS
Planning the Organizations Approval
Processes
A set of business cases
Transactions having similarly structured approval
processes.
Transactions whose default approver lists include
repeated approvers.
Transactions whose approvers forward approval
requests in unusual ways.
Transactions whose approval processes should
have similar parallelization.
STEPS FOR BASIC AME
IMPLEMENTATION
Set up the Attributes
Set up the required Conditions
The required Action Types
Approval Groups
Building up Approval Rules
Testing of the set Approval Rule.


CASE STUDY - EXIT PROCESS:

The Termination of the employee is to be raised by the employee.
The Function in the Self Service is TERMINATION.

REQUIREMENT:
The Manager raises the termination of the employee. The approval has to
go to the 1. Reporting Manager (Supervisor)
2. HR Coordinator.

1. The Work Flow name is given as: HR_TERMINATION_JSP_PRC

2. ADD the responsibility of Approvals Management Administrator
Approvals Management Business Analyst






1. Attributes
Attributes are business variables with a single value for a
particular transaction.

E.g. If the transactions total cost is less than 1,000 USD,
and the transaction is for travel expenses.
TRANSACTION_AMOUNT is the attribute.

Attribute use can be of two MAJOR types:
Static: A static use specifies a fixed value for the
attribute, for all items and transactions
Dynamic: A dynamic use specifies an SQL query that
AME executes at run time to fetch the attributes value
ATTRIBUTE TYPES
Boolean: AME defines constants for them: ame_util.booleanAttributeTrue
and ame_util.booleanAttributeFalse
Number: Static use for number attributes should either be integers or
decimal numbers using the decimal-point character required by the users
character set. For example, 1 , -2 and -3.1415 is an acceptable decimal
value.
Dynamic use for number attributes should convert a number column to
canonical form using the function fnd_number.number_to_canonical.
String: String attributes can have any text value up to 100 bytes long (100
characters).
Date: Date-attribute values must conform to the format model
ame_util.versionDateFormatModel , which currently has the
value YYYY:MON:DD:HH24:MI:SS . For example, 2001:JAN:01:06:00:00 is
an acceptable date value
Currency: Currency-attribute values must have the form:
amount,code,type 5000.00,USD,Corporate might be a valid static currency
value.
Functions on Attribute
Creating
Editing
Copying: Click Use Existing Attribute on the
Attributes page to open the Use Existing
Attribute page.
Deleting: If enabled
2. Conditions
The if part of an approval rule consists of
zero or more conditions.
A condition is a statement that is either true
or false, for a given transaction.
For the rule to apply to a transaction, all of
its conditions must be true for the
transaction.
Condition Types
There are two types of conditions:
1.Regular, which has Ordinary and Exception
conditions
2.List-modifiers
Ordinary: An ordinary condition associates an
attribute with a set of allowed values or range . Can
have one of the following three forms.
Conditions on Date, Number, and Currency
Attributes
Exception: Exception condition can only appear in
exception rules.

FUNCTIONS ON CONDITIONS
Creating
Editing
Attribute page.
Deleting
3. Actions
An action is an instruction to AME to modify a
transactions approval process in the manner you
specify.
An approval rules then part (its consequent) consists of
one or more actions.
Pre de ned Action Types
The action types are sorted by allowed rule type and
are broadly categorized as:
Chain of authority action types
List Modification action types
Substitution action types
Production action types

Choosing an Action

1. Choose a rule type:
Use list-creation rules to generate chains of authority.
Use pre- and post-chain of authority rules to let groups of subject-matter
experts
approve a transaction before or after management.
Use list-modification rules to grant unusual signing authority, or to revoke usual
signing authority, in special cases.
Use substitution rules to replace one approver with another in special cases, or
for short periods of time (such as vacations or leaves of absence).
Use combination rules when several of your business rules apply to exactly the
same cases.
Use production rules when an integrating application uses AME
productions.

Choosing an Action
..
2. Choose an approver type
AME current supports three approver types: HR
employees (sometimes called persons/HR people in
the AME UI), HR positions, and FND (Oracle
Applications) users.
3. Choose an action type:
That generates a chain of authority containing that
approver type, and having the structure you want.


4. Approver Groups
An approver group can either be an ordered set of
one or more approvers or it can be a list, which is
dynamically generated at rule evaluation time.

AME creates corresponding actions of the pre- and
post-approval action types automatically.

ORDER NUMBER: Approver-group order numbers
determine how the approver groups in the same sub-
list are ordered
WHEN TO USE APPROVAL GROUPS
Using Approver groups for Pre- and Post-
Approvals - represent functional or subject-
matter-expert approvers.
Using Approver groups for Chain of Authority
Approvals.
Containing an approver type that lacks a
hierarchical structure.
5. Rules

Rule associate one or more conditions with
an approval in an if-then statement
Thus, while creating rules is your ultimate
goal, it is also the last thing you do when you
set up AME.
Rule Types


LIST CREATION and LIST EXCEPTION
RULE: If TRANSACTION_AMOUNT < 500 USD
and Exception: COST_CENTER is in
{0743}, then require approvals up to at least
supervisory level 1 .
SUBSTITUTION
RULE: If TRANSACTION_AMOUNT < 500 USD
and CATEGORY in {MISCELLANEOUS OFFICE
EXENSES} and any approver is: John Doe, then
substitute Jane Smith for the approver.
Rule Types
Pre- and Post-List Approval-Group Rules
If TRANSACTION_AMOUNT < 1000 USD
and CATEGORY_NAME in {Marketing
Event}, then require pre-approval from
Marketing Approvals Group.

Combination Rules

TESTING
Raising a transaction.
Testing the AME setup.