A highly extensible approvals rules engine that enables organizations implementing Oracle Applications to simply and effectively define business rules that determine who must approve a transaction originating within an application. You can devise simple or complex rules, as your organization requires, which then form part of your overall business flow. A central repository holds all the rules to facilitate management and sharing between business processes.
Action
An Action is the Then part of an Approval Rule that specifies how the application must progress a transaction's approval process in a particular way depending on the conditions met.See: Approval Rule
Action Type
An Action Type is the generic type of specific actions. It enables you to specify the action to take if a transaction meets the condition of an approval rule. The action type, thus, generates the appropriate approvers for a transaction. As an AME administrator you can make particular action types available for specified transaction types. See: Transaction Types.
Approver Groups
An Approver Group is a collection of approvers you define, which you can include as part of actions when you set up your approval rules.
Approval Rule
A business rule that determines a transaction's approval process. You construct rules using conditions and actions. For example, you can write a business rule with the conditions that if the total cost of a transaction is less than 1000 USD, and the transaction is for travel expenses, then the action must be to obtain approval from the immediate supervisor of the person triggering the transaction.See also Conditions, Actions
Attribute
Attributes are the business facts of a transaction, such as the total amount of a transaction, percentage of a discount, an item's category, or a person's salary and so on. These business variables form part of the conditions of an approval rule, and determine how the transaction must progress for approvals.
Condition
A Condition is the If part of an Approval Rule that specifies the conditions a transaction must meet to trigger an approval action. A condition consists of an attribute, which is a business variable, and a set of attribute values that you can define. When a transaction meets the specified attribute values, then the application triggers the appropriate action.See: Approval Rule
Deviation
A change to the standard approver list is a deviation.
An integrating application that uses AME may divide its transactions into several categories, where each category requires a distinct set of approval rules. Each set of rules is a transaction type. Different transaction types can use the same attribute name to represent values that the application fetches from different places. This enables several transaction types to share approval rules, thus facilitating a uniform approval policy across multiple transaction types.