Sunteți pe pagina 1din 22

Approvals Management

Emerson Business Services

Oracle Approvals Management (AME) Key Functionality

Oracle Approvals Management offers building blocks for flexible, custom approval rules to enhance the management approval workflow. The Rules can be based on
Supervisor Hierarchy based approvals Job level Hierarchy based approvals Position Hierarchy based approvals Group (Approving HR Position) Pre Approval Groups Post Approval Groups

Oracle Approvals Management


Approval Rule

Rule

if Process In {Change Pay}

Attributes

and Salary Increase Pct < 30 then require approvals up to the first two superiors require post approval from HR

Conditions

Approval Types

AME ATTRIBUTE
In AME an attribute is a variable that has exactly one value per item, for a given transaction.
Common attributes are WORKFLOW_PROCESS_NAME, HR_IS_SELECTED_PERSON_CONTACT_CHANGE_SS

Based on the requirements custom attributes can be created. e.g. EMR_IS_CHANGED_BY_SELF


EMR_SIT_STRUCTURE_NAME

AME ATTRIBUTE

AME ATTRIBUTE

AME ATTRIBUTE

AME CONDITIONS

A condition is a statement that is either true or false, for a given transaction. Condition is always associates with an attribute. The 'if' part of an approval rule consists of conditions. For the rule to apply to a transaction, all of its conditions must be satisfied for the transaction. We need to create conditions before we can define rules.

AME CONDITIONS

AME CONDITIONS

10

AME CONDITIONS

11

AME Action

An action is an instruction to AME to drive a transaction's approval process. An approval rule's 'then' part consists of one or more actions. Typically AME provides all of the action types and actions that are required for any implementation.

12

AME Action

13

AME APPROVAL GROUP

An approval group can either be an ordered set of one or more approvers (persons and/or user accounts) .

14

AME APPROVAL GROUP

15

AME APPROVAL GROUP

16

AME APPROVAL GROUP

17

AME RULES

In the AME implementation main step is rules and rule usages creation. Business rules needs to be translated into AME rules. Rule associate one or more conditions with an approval in an if-then statement. Before we can create rules, we must create conditions for the rules to use. Based on the requirements we may need to create some custom attributes and/or approval groups.

Creating rules is the last thing we do in AME setup.

18

AME RULES

19

AME RULES

20

AME RULES

21

AME RULES

22

S-ar putea să vă placă și