Professional Documents
Culture Documents
AME Introduction
AME is a self-service web application which lets users define business rules
governing who should approve transactions that originate in other Oracle
applications like in SSHR. It mainly provides the following services to the
calling application,
- A centralized rules repository for defining and sharing rules.
- Based on specific transaction date, it provides an execution engine to
evaluate the rules.
- It provides the List Management capabilities.
- It also provides the history of approval status.
Announcing Approvals Management Mini pack AME.B (4428060). This release
sees the adoption of OAF (Applications Framework) in place of the mod pl/sql
UI previously available within AME.
Announcing Approvals Management Mini pack AME.B rollup patch (4873179).
This fixes some issues with AME.B as well as introducing some functionality
for future uptake by integration teams. AME.B patch is the OAF version of
AME. Please note that the version of AME in R12 is equivalent to AME.B (up to
its rollup) and hence all the documents for AME.B are also applicable for R12
with some minor change.
Knowing AME.B
In AME B, the UI has moved to new OAF tech. With this, the old AME
Application administrator responsibility is end-dated and instead we have the
following two responsibilities;
- Approvals Management Business Analyst
- Approvals Management Administrator
Assigning these responsibilities directly to a user will NOT work. From AME.B
onwards RBAC (Role Based Access Control) is used. So, for the responsibilities
to work, AME roles should be assigned and data grand has to be provided to
the users. This is explained in detail in following sections.
For the Existing users, you can run the Approvals management Post Upgrade
Process concurrent process, which will attach the new responsibilities to the
existing AME Users. Using the System Administrator Responsibility, you can
attach the concurrent program to System Administrator Reports Request
Group.
The migration is implemented as a concurrent program with Switches. To
migrate users, pass 'MIGRATE_USERS' as parameter. To migrate item class
usages, pass 'MIGRATE_ITEM_CLASS_USAGES' as parameter. To migrate both
2.Attributes
3.Conditions
4.Actions
5.Approver Groups
6.Rules
1. Transaction Type:
Transaction Type is a distinct set of approval rules used by certain category of
transactions in an integrating Application
2. Attribute:
Attributes in AME are placeholders for transaction data elements. They are basic
elements of an AME rule.
Attributes can be static (fixed value) or dynamic (SQL Query based). AME comes
with several seeded attributes for each of the transaction types in the system. If
the seeded attributes cannot be used for approval rules, then organizations can
define their own attributes.
3. Condition:
The Condition component is used to tell AME engine to trigger an AME rule if the
result of the condition is TRUE.
One or more attributes are used to define a condition. In the condition setup, an
attribute is associated with a value or range of values. At runtime, the transaction
type value is evaluated against the attribute value. If the value transaction type
value qualifies with the attribute value, the outcome of the condition is TRUE and
the AME rule is eligible to trigger. Otherwise, the condition will yield FALSE and the
rule shall not apply.
Ex: This condition states if the payable Invoice Total is >= 100 and <= 500000
and the currency is USD, then tell AME to enable the rule associated with this
condition to fire.
4. Action Type:
An Action Type is a collection of one or more Actions having similar functionality. An
Action tells AME how to modify a transactions approval process in a certain
way.AME provides several seeded action types or one may define a custom action
type. The seeded Action Types available in AME can be used to ascend organization
hierarchies. Seeded Actions Types available in AME cannot be used with any
transaction type.
<![if !supportLists]>5.
<![endif]>Approver Group:
Static approver group, the approvers are constant, added at the time of Approver
Group setup and will be listed as Group Members.
Dynamic approver group, the approvers are generated at run time using an SQL
Query in the approver group setup and are later identified as Group Members at
run time.
Approver Group may have a voting method assigned such as Consensus, First
Responder Wins, Order Number and Serial. The voting method assigned to an
approver group determines the order in which the Group Members are notified and
also how the decision of the groups approval.
First-Responder-Wins
groups decision.
Order-Number Members notified according to order, ties notified in parallel. All
must respond.
6. Rule
A Rule (also called as Approval Rule) in AME is used to transform the business
rules into approval rules to specify approvers in the transactions approval list.
List-Creation
If invoice amount > $1000 INR (condition), THEN require approval one job levels
above requestor.
List-Creation Exception
If invoice amount > $500 INR and pay group = Employee, THEN require approval
two job levels above requestor.
List-Modification
If any approver = Sam Clark, THEN grant final authority.
Pre and Post
If expenditure category = Computers, THEN require approval from IS department.
Pre Requisites
Step1 : For invoice approval,
requester(Panchineni, Hanumanth).
Manger
should
be
assign
to
1. Login as SYSADMIN user (or a user that has full User Management functionality).
2. Switch the responsibility to User Management and Navigate to the Users function
button.
10. After selecting the Roles, provide the Justification for the role and the effective
date and click on Apply.
18. You have a default value of All Rows in the Data Context Type, leave it as it is,
and navigate further.
19. In the Object parameter and Select Set page, enter AME Calling Applications
as the value in the Set field.
20. Clicking Next will take you to the Review page.
22. Go to Payables Option select Approval (T), should be enable Use Invoice
Approval Workflow, Allow Force Approval and also enable Require
Validation Before Approval.
Nav : Payables Manager, Vision Operations (USA) Setup Options Payables
Option Approval(T)
Create Attribute
Click on the attribute link
Condition
Create a condition with above attribute
Select the above attribute and enter the amount value and click on apply
Action Types
Click on Finish
Create Rule:
Create Rules with the help of condition and action.
Click on create button
Enter the Name and remaining values are default and click on next
Click on Next
Click on Finish
Invoice is validated
Approver 1:
Login with OPERATIONS user and click on the notification link
Approver 2:
Login with CBROWN user and click on the notification link