AME Setup - AP Invoice Approval (Gates India)

Oracle Approvals Management (AME)
Introduction:
The purpose of Oracle Approvals Management (AME) is to define approval rules

that determine the approval processes for Oracle applications. Oracle Approvals
Management (AME) is a self-service Web application that enables you to define
business rules governing the process for approving transactions in Oracle
applications that have integrated AME.
Advantage of AME:
Oracle Approvals Management enables you as a business user to specify the

approval rules for an application without having to write code or customize the
application. Once you define the rules for an application, that application
communicates directly with AME to manage the approvals for the application's
transactions.
Approval Hierarchies:
We can define approvals by job, supervisor hierarchy, positions, or by lists of

individuals created either at the time you set up the approval rule or generated
dynamically when the rule is invoked. You can link different approval methods
together, resulting in an extremely flexible approval process.
Setups:
Setting up Responsibilities:
This section gives a step-by-step illustration of adding the two AME

responsibilities to the user.
1. Login as SYSADMIN user

2. Create a New user account and give an appropriate effective date. Do NOT add
any Approval responsibility.
Prepared By A.GOWTHAMAN
3. Save the record
4. Switch the responsibility to User Management and Navigate to the Users

function.
5. Query for the newly created user.

6. Click on the update action from the result table.
7. In the Update User page, click on the Assign Roles button
8. Change the “Search By” field from “Roles and Responsibilities” to “Roles”
9. In the search window, query for Approval%
10. Following five roles will be displayed.
11. Select only the “Approvals Management Administrator” and “Approvals

Management Business Analyst” roles
12. After selecting the Roles, provide the Justification for the role and the effective
date.
13. After completing the action, you can query back the same user and can verify
the list of roles being attached to the user.
14. Now switch the responsibility to Functional Administrator.

15. Click on create grants under the grants sub-tab
16. Enter a Grant Name and provide an effective date.

17. Navigate to the security Context region and select the Grantee Type as
‘Specific User’
18. In the Grantee field select the newly created User
19. In the Data Security region select ‘AME Transaction Types’ as the Object
20. Clicking Next will take you to the ‘Select Object Data Context’ page’.
21. You have a default value of ‘All Rows’ in the Data Context Type, leave it as it
is, and navigate further.
22. In the ‘Object parameter and Select Set’ page, enter ‘AME calling applications’
as the value in the Set field.
23. Clicking Next will take you to the Review page.

24. Verify the information and submit the transaction.
25. Now Switch the responsibility to System Administrator and Navigate to

System Profiles.
26. Query for the profile ‘AME:Installed’ at the required level and set the value to
‘Yes’.
27. Save the data
28. Now switch the responsibility to Payables.

29.Go to Payable Option
30.Click Approval (Tab) Enable Use Invoice Approval workflow and Require
Validation Before Approval
31.Now you can login as the newly created user.

32.You should be able to see the following responsibilities:
a. Approvals Management Administrator
b. Approvals Management Business Analyst
Approvals Management Administrator Dashboard:
Approvals Management Administrator responsibility has full access to AME’s user

interface. To perform any technical tasks such as setting AME’s configuration
variables, at least one user administrative privilege in AME should be granted.
Transaction Types
A transaction type describes the type of transaction for which business rules and
approval routings will be based. This can include Oracle Application transactions
such as purchase requisitions, sales orders or accounting journals. Oracle provides
many seeded transaction types to satisfy many of the common transactions that
occur within a particular application. The creation of a new transaction type in
AME is available for those business users that want to integrate custom
applications with AME. However, Oracle typically does not encourage the
development of new transaction types because of the significant programming
effort involved to integrate with the AME application.
The administrator dashboard mainly consists of three regions,

- The transaction Type
- Unused Approver Groups
- Quick Links
Approvals Management Business Analyst Dashboard:
Approvals Management Business Analyst responsibility enables you to access

areas of the user interface that do not require expertise in SQL or PL/SQL
programming, or technical knowledge of Oracle Applications.
The Business Analyst dashboard mainly consist of the following regions,

- Transaction Types
- Recently Updated Rules
- Future Active Rules
- Future Inactive Rules
- Approval Process Setup
- Quick Links
Attribute:
Attributes within AME are business variables that represent the value of a data
element of a given Transaction. Attributes can be thought of the as the ‘building
blocks’ of business case development. The reason being is that the value of an
attribute(s) for a transaction can ultimately determine whether a business case
(approval rule) has been met because approval rules use conditions which in turn
use attributes. Most of the attributes you will need to create business rules are
seeded with the transaction type. Additional attributes can be created as needed as
long as they can be linked to the source transaction. Attributes in AME can be
created as being static or they can be dynamic in nature.
Static attributes have a constant value that remains the same for each and every
transaction associated with the attribute’s transaction type.
Dynamic attributes use a SQL query to retrieve the value of an attribute at runtime
whenever a transaction is created. Most attributes in a transaction type are dynamic.
Example:
AP invoice Type Attribute
Condition:
The next major component of AME setup is conditions. Conditions are used to
evaluate the value of attributes in a particular transaction. The result of a condition
can either be true or false. Conditions are precursors to AME business rules. The
result of a condition helps to determine whether a business case (rule) has been
satisfied.
Approver Group Action Types:

Approver group action types allow an approver list to be built based on a
predefined list of members that are part of the approval group. This list can be
static, containing the specific names of individuals responsible for approvals of a
given transaction. The list can also be dynamically built based on a SQL statement.
Action Types and Actions

Actions within the AME application describe the nature of what should be done in
AME if a particular condition and rule is satisfied by a transaction. It is the actions
that dictate the approver list that is generated by AME for the given transaction.
Actions not only provide instruction as to who the approvers are, but how many
approvers are required for a given transaction and in what order should they be
notified. Action types are groupings of actions that have a similar functionality
such as the approval hierarchy that should be traversed when building an approver
list.
Rule:
Rules could arguably be considered the essential component when defining

business cases for an organization. Whenever a transaction is initiated, the rules are
evaluated to determine what approval path the transaction will follow when
submitted for approval. Rules are defined by associating the conditions that
ultimately determine whether a particular business case has been satisfied.
Additionally, rules are associated with action types to determine the approval
action and thus the approver list that should be generated for the transaction.
Similar to action types, rules use rule types to determine the type list to build if the
results of the rule are true.
Case 1:
If AP invoice Type Prepayment, Debit Memo, Credit Memo, Standard Invoice

Approval go to ACCTHO User.
AP Invoice:
Once ACCTHO Approver approve the Invoice , Invoice Status “Workflow

Approved”.
Case 2:
If PO_Match Invoice Created by APCLERK1,Then Invoice will Approve By

APCLERK2. IF PO_match invoice prepared By APCLERK2, Then Invoice will
Approve by APCLERK1.
Attribute 1 :
These two Attributes for Fetches the User.( APCLERK1 & APCLERK2 )
Attribute creation:
SQL Query :
Attribute 2 :
This Attribute for Check the PO_MATCH_TYPE = “ ITEM_TO_PO ”
Condition 1:
Condition 2:
Action Type and Approval Group setup Referred: Invoice Type case.
Rule for this case:
we have to create two rules
1. One for APCLERK1
2. Another for APCLERK 2
In this Rule we have to add two conditions.
FND_USER_AP_INVOICE Check in (YES)

AP_INV_PO_MATCH Check in (YES)
AP Invoice With PO match:
Approve the Invoice :
Log In APCLERK2 we can see the invoices in worklist.
--------------******---------------------******--------------------******----------------
For More Details about AME Refereed:
1. AME Implementation Guide

2. AME White Paper

AME Setup - AP Invoice Approval (Gates India)

Uploaded by

Copyright:

Available Formats

AME Setup - AP Invoice Approval (Gates India)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AME Setup - AP Invoice Approval (Gates India)

Uploaded by

Copyright:

Available Formats

Oracle Approvals Management (AME)

The purpose of Oracle Approvals Management (AME) is to define approval rules

Oracle Approvals Management enables you as a business user to specify the

We can define approvals by job, supervisor hierarchy, positions, or by lists of

This section gives a step-by-step illustration of adding the two AME

1. Login as SYSADMIN user

3. Save the record

4. Switch the responsibility to User Management and Navigate to the Users

5. Query for the newly created user.

7. In the Update User page, click on the Assign Roles button

11. Select only the “Approvals Management Administrator” and “Approvals

14. Now switch the responsibility to Functional Administrator.

16. Enter a Grant Name and provide an effective date.

18. In the Grantee field select the newly created User

23. Clicking Next will take you to the Review page.

25. Now Switch the responsibility to System Administrator and Navigate to

28. Now switch the responsibility to Payables.

31.Now you can login as the newly created user.

Approvals Management Administrator Dashboard:

Approvals Management Administrator responsibility has full access to AME’s user

The administrator dashboard mainly consists of three regions,

Approvals Management Business Analyst Dashboard:

Approvals Management Business Analyst responsibility enables you to access

The Business Analyst dashboard mainly consist of the following regions,

AP invoice Type Attribute

Approver Group Action Types:

Action Types and Actions

Rules could arguably be considered the essential component when defining

If AP invoice Type Prepayment, Debit Memo, Credit Memo, Standard Invoice

Once ACCTHO Approver approve the Invoice , Invoice Status “Workflow

If PO_Match Invoice Created by APCLERK1,Then Invoice will Approve By

This Attribute for Check the PO_MATCH_TYPE = “ ITEM_TO_PO ”

In this Rule we have to add two conditions.

FND_USER_AP_INVOICE Check in (YES)

AP Invoice With PO match:

Approve the Invoice :

Log In APCLERK2 we can see the invoices in worklist.

For More Details about AME Refereed:

1. AME Implementation Guide

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.