Professional Documents
Culture Documents
How To Setup and Use AME For Purchase Requisition Approvals
How To Setup and Use AME For Purchase Requisition Approvals
Purchase Requisitions can be routed for approval using the AME Approval Management
Engine. This whitepaper describes how to setup AME for use with requisition approvals,
and shows how a requisition approval list is built based on the AME setup. Approvers in
the AME based approver list are assigned to the requisition based on the AME rules setup
for the Purchase Requisition Approval transaction. Similar setup can be done for
Requester Change Order Approval and for Internal Requisition Approval, although those
are not specifically covered in this whitepaper. The screenshots provided are based on
11i.AME.B, and some of the navigation details are specific to 11i.AME.B. However,
most of the details provided are applicable to 11i.AME.A and higher including R12.
AME responsibilities in 11i.AME.A are assigned directly to the users. However, In R12
or 11i.AME.B and higher, AME responsibilities are assigned indirectly to users through
roles. The roles are assigned to the users by the SYSADMIN user using the User
Management responsibility. Once the roles are assigned, the AME responsibilities are
automatically available to the users without specifically assigning the
AME responsibilities to the users. Here are steps to assign the roles:
1. Login as System Administrator user
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.
Reference <<Note 413300.1>> Oracle Approvals Management Not Enabled? What Does
It Take To Enable It?
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.
AME is designed to provide approval logic for many transaction types. Transaction
types used for Purchase Requisitions include the following: Purchase Requisition
Approval, Internal Requisition Approval, and Requester Change Order Approval. This
whitepaper focuses on Purchase Requisition Approval, however, many of the concepts
are applicable to the other two requisition transaction types as well. Likewise, some
examples and comments in this paper are written in iProcurement context, but the same
AME concepts apply to core apps requisitions also.
2. Choose the Business Analyst Dashboard menu from the responsibility (see image
above)
3. Use the Transaction Type LOV to search and select the transaction type = Purchase
Requisition Approval
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.
3. The Action Types page shows the action types that are currently
enabled for the transaction type (Purchase Requisition Approval).
Use the Previous and Next links to scroll through the list of
enabled action types. Select the Use Existing Action Type button
to see other pre-defined action types available in AME. Some of
these may or may not be applicable to the currently select
transaction type; AME will give an error if the user tries to add a
non-relevant action type for the selected transaction type.
4. Navigate to HR responsibility -> Work Structures -> Job ->
Description - to assign a Level (Approval Authority) to a Job.
Query up the Job and enter the appropriate Job Level in the
Approval Authority field.
5. In AME, select any or all of the following Action Types for JOB
BASED approvals if applicable for your business requirements:
2. Attributes
1. Attributes are the base element for an AME Rule. Attribute values
are retrieved from the Oracle EBusiness Suite Applications
database or derived from values in the database. AME is seeded
with attributes relevant to the transaction type, and the user can
create new attributes in AME for use in AME rules.
2. Select the Attributes link to view or add attributes for the selected
transaction type
3. Use the Previous and Next links to scroll through the existing
attributes. Some of the attributes relevant to Purchase Requisition
Approval include ITEM_CATEGORY, ITEM_NUMBER, and
REQUISITION_TOTAL as well as other attributes. When AME
approvals is enabled for purchase requisitions, these values are
retrieved for the relevant requisition while navigating through
iProcurement checkout or core apps requisition create, and AME
uses this information to determine the appropriate AME rule(s) to
use.
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.
2. Select the Conditions link from the AME Business Analyst
Dashboard after specifying the Purchase Requisition Approval
transaction type.
4. Approver Groups
5. Rules
6. Test Workbench
2. Adhoc test
1. Create a requisition in Core Apps Purchasing or iProcurement and verify that the
Approval List is built per the AME rules based on the conditions present on the
requisition attributes.
1. Click the Setup Report link in the Quick Links section of the Dashboard
2. Select the appropriate transaction type (Example: Purchase Requisition
Approval) and click Go.
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.