Professional Documents
Culture Documents
How To Setup and Use AME For Purchase Requisition Approvals
How To Setup and Use AME For Purchase Requisition Approvals
4. Search for the user to whom you wish to grant AME roles
7. Search for Approval% and Select roles from the resulting LOV. Choose the roles
that are applicable (proper authority) for the user, and click the Select button.
8. Specify justification and relevant dates for the newly assigned roles, and
click Apply to assign the roles to the user.
AME restricts access to transaction types using Data Security. Grant users access to the
transaction types using the Grants page. Set up user access as follows:
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 E-
Business 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. Attributes
3. Conditions
4. Approver Groups
5. Rules
6. Test Workbench
2. Adhoc test
1. Click the Setup Report link in the Quick Links section of the Dashboard
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.