Approval Management Engine in EBS

Approval Management Engine in EBS: Points to Ponder:

1.       About AME:

Oracle Approvals Management (AME) enables you to define business rules governing the process for approving transactions in Oracle applications that have integrated AME.

2.       Integration of AME with Oracle E-Business Suite Application

INTEGRATING FROM APPLICATION	INTEGRATING TO APPLICATION
Service Work in Process	Quoting Enterprise Asset Management
Service Contracts	Payables
Field Service	Inventory
Partner Management	Receivables
Purchase Requisition	Receivables
Payroll	Work In Process

3.       Business Flow

4.       Structure of AME

AME is a framework of well-defined approval rules constructed using the following 5 components for a given transaction-type:

1.       Transaction Type:

A transaction type describes the type of transaction for which business rules and approval routings will be based. Examples of transaction types are:

• Purchase Requisition Approval (Purchasing)

• Requester Change Order Approval (Purchasing)

• Service contract Approval (service contract)

• Work Order Approval (EAM)

A Transaction type is a combination of Rules, Attributes, Conditions and Approval Groups.

Please see the screenshot below:  

2.       Attributes

Attributes within AME are business variables that represent the value of a data element of a given transaction.

• Attributes in AME can be created as being static or they can be dynamic in nature

• Attributes can be defined at 3 different levels – Header, Line Item and Cost Center level.

• Examples of attributes are:

·         Contract_Amount(service contracts)

·         Request_Severity(service Request)

·         Item_Number(Purchasing)

3.       Conditions

Conditions are used to evaluate the value of attributes in a particular transaction

• The “Condition” component tells AME engine to trigger an AME rule if the result of the     Condition is TRUE

• One or more attributes are used to define a condition.

4.       Actions

·         Actions describe what should be done in AME if a particular condition is satisfied by the transaction

·         Action Type is a collection of actions having similar functionality. Every action belongs to an action type.

Action Types
Job Based	Absolute Job Level
	Final Approver Only
	Manager then Final Approver
	Relative Job Level
	Supervisory Level
HR Position Based	HR Position
	HR Position Level
Approver Group Based	Pre-Chain-of-authority approvals
	Post-chain-of-authority approvals
	Approval-group chain of authority

5.       Approver Groups

Approver Group is used to fetch approvers from Oracle Applications (HRMS).

• Static or Dynamic in nature

• The voting method determines the order in which the Group Members are notified and also how the decision of the group’s approval.

6. Rules

Transforms the business rules into approval rules to specify approvers in the transaction’s approval list

• Rules can also be categorized as “FYI” or “Approval”.

• A rule is constructed using the following components:

1. Rule Type

2. Item Class

3. Category

4. Conditions

5. Actions