Professional Documents
Culture Documents
AME For Requisition Approval PDF
AME For Requisition Approval PDF
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.
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 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.
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.
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:
1. absolute job level / chains of authority based on
absolute job level
2. final approver only / chains of authority containing
only the final job-level approver
3. manager then final approver / chain of authority
includes requestor's manager and then the final
approver
3. Use the Previous and Next links to scroll through the existing
attributes. Some of the attributes relevant to Purchase
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)
2. Select the Approver Groups link from the AME Business
Analyst Dashboard.
5. Rules
1. Define rules to specify approvers that should be included
in the approval list under specific conditions for the
requisition approval transaction.
2. Select the Rules link from the AME Dashboard after
selecting the transaction type Purchase Requisition
Approval
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
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.