Oracle Approvals Management (AME) used to explain approval policy that chooses the approval method for the Oracle applications. This approval policy is a business rule that assists to decide a transaction’s endorsement method. Rules are constructed from the conditions and actions. For example, an approval rule can be as follows. AME provides an extensive Test Workbench allows you to maintain this important task. The Administrator Dashboard delivers a number of functions to the sure smooth running of Oracle Approvals Management. Log files are easily viewed in order to determine the errors in the endorsement process. The approval rule’s if the element contains zero or additional conditions, and its then part contains one or more actions. This term contains a business variable (in AME, an attribute) and a group of attribute values, any one of which makes the condition true.
The action says AME to alter a transaction’s approval method in some fashion. The circumstances in the example rule in the graphic prefer to two attributes: the transactions is total value and the transaction’s purpose. The sample policy action says AME to include the requestor’s supervisor to the transaction’s approver list. We can record this transaction deviation by surroundings the Record Approval Deviations configuration variable to Yes at transaction type level, and running the Approvals Deviations it Report after the approval of a transaction.
This report shows the transaction deviations to generate the approver list. It permits multiple transaction types of the share approval rules (thereby executing a uniform approval policy across the multiple transaction types). A rule use occurs when a transaction type uses a particular rule for a given time period, optionally at a given main object of the level. We can catch deviation make to the standard approver list by running the Approvals Deviations report.