Professional Documents
Culture Documents
AME For Requisition Approval
AME For Requisition Approval
4. Search for the user to whom you wish to grant AME roles
6. In the update user page, user details can be seen along with a list of roles available
to user
8. Specify justification and relevant dates for the newly assigned roles, and
click Apply to assign the roles to the user.
7. Click Next, review the setups and then Finish the process.
4. Use the links on the right in the Approval Process Setup region to
set the components (Attributes, Conditions, Action Types,
Approver Groups and rules) or to use the test workbench in AME.
1. Action Types
1. An action type is a collection of actions having
similar functionality. Every action belongs to an
action type. Action types are enabled or disabled for
a particular transaction type. AME may give an error
when attempting to enable an action type for a
transaction if the transaction is not designed to allow
that action type. Reference <<Note 293315.1>>
11.5.10 FAQ for Approvals Management (AME)
Integration For iProcurement and Purchasing - for a
list of action types allowed for requisition
transactions
in
AME.
In
addition,
<<Note
404152.1>> Release Content Documents for EBusiness Suite R12 - provides a link to the
Procurement Family RCD which clarifies (Section
3.4.2.14) that requisition approval with Oracle
Approvals Management (AME) in R12 allows use of
Position
Hierarchy
based
Approvals,
Parallel
Approvals, and Support for FYI Notifications.
2. To disable or enable action types for the transaction,
select the Action Types link
type.
3. Conditions
1. Conditions identify values and value ranges for some
or all of the attributes available. AME rules refer to
these conditions to determine if a particular rule is
applicable for the specific document (requisition)
being approved. For example, an AME rule can be
setup to require certain approvers if $0 USD <=
requisition total < $1000 USD. Since
REQUISITION_TOTAL is a seeded attribute, the user
can define a condition $0 USD <= requisition total <
$1000 USD, and then use this condition in a rule to
require certain approvers for the requisition. The
rule cannot refer to this condition until it is defined in
AME Conditions for the Purchase Requisition Approval
transaction type.
4. Approver Groups
1. Approver Groups are optional. Setup Approver Groups if
additional approvers are required for particular conditions,
or to specify a dynamic sql query for additional approvers.
The rules defined for the transaction can be based on
Approver Groups, Jobs defined in HR setup, or Positions
defined in HR setup (only in R12); the rules may also use
a combination of Job, Position, and Approver Group basis.
(See the Rules details later in this paper for more
information about the rules)
6. Test Workbench
1. Use the Test Workbench to determine which AME
Rule(s) apply to a specific requisition, or to determine
which AME Rule(s) apply for an adhoc combination of
values specified at the time of the test.
Select the Test Workbench link from the AME
Dashboard
2. Adhoc test
1. Click the Create button on the Test
Workbench page
3. Click the Printable Page button to view the complete setup for the selected
transaction type (Attributes, Conditions, Rules, Approval Groups, and etc.)
4. Compare the AME setup to the requisition attributes and approval list generated
for a specific requisition, or compare the AME setup to the business requirements.
NOTE: This document is not considered formal documentation of the product, but is a
useful tool for applying the functionality described.