Professional Documents
Culture Documents
AME OIE Whitepaper
AME OIE Whitepaper
May 2006
2. REFERENCE
This paper is intended to supplement the following reference materials, which should also
be studied for a full understanding of the topic.
Implementing Oracle Approvals Management
Oracle Internet Expenses Implementation and Administration Guide
3. SCOPE
The scope of this document is to define List creation rule of type chain of authority based
on number of supervisory levels. We would also cover the basic setup involved to
accomplish the same.
4. SETUP
a) HRMS
The Test case explained here uses the following supervisory hierarchy with each
Employee reporting to the top level:
Russ Mitchell
Stock Patt
Rob Alan
Below is the screenshot of Mr. Russ Mitchell Employee Setup showing the
supervisor assigned.
Similar setup is done for the remaining Employees. .Please note that no
Supervisor is selected for Mike Edwards who is the CEO of the Virtual
Organization.
b) SYSADMIN
We need to create users in sysadmin and attached these Employees. We also need
to attach some responsibilities required for the testing:
a) Internet Expense Responsibility
b) Workflow User Web Applications
1. Attribute
An attribute is a variable that has exactly one value per item, for a given
transaction. Common attributes are things like a transaction’s total amount, a
percent discount, an item’s category, a person’s salary, and so on. In AME,
attribute names always appear uppercased, for example
EXPENSE_REPORT_TOTAL.
An attribute item class determines what class of items has a value for the attribute.
For a given transaction, each of the items in an attribute's item class has its own
value for the attribute. An attribute always has the same item class, regardless of
the transaction type. Attributes belonging to the header item class are sometimes
termed header-level attributes. Attributes belonging to subordinate item classes
are sometimes termed line-item-level attributes, cost-center-level attributes, etc.
EXPENSE_REPORT_TOTAL is a Header level attribute and
EXPENSE_LINE_AMOUNT is a line level attribute.
Attribute Usages:
select fnd_number.number_to_canonical(erh.total),
nvl(erh.default_currency_code,asp.invoice_currency_code),
nvl(erh.default_exchange_rate_type,asp.default_exchange_rate_type)
from ap_expense_report_headers_all erh, ap_system_parameters_all asp
where erh.report_header_id = :transactionId
and erh.org_id = asp.org_id
Please review the syntax rules for Dynamic usage queries in the AME
implementation guide. This is very important while you design your query.
Further the execution of dynamic attribute usages’ queries represents the majority
of AME’s runtime overhead. Therefore, optimizing your dynamic–usage queries
can have a big impact on AME’s performance. Make sure you optimize these
queries thoroughly, especially if the transaction type that owns them processes a
high volume of transactions.
2. Condition
An approval rule’s “if” part consists of one or more conditions, each of which is
either true or false. For the rule to apply to a transaction, all of its conditions must
be true for the transaction.
The “if” part of an approval rule is the condition. It may consist of one or more
conditions each of which is either true or false. For a rule to apply to a transaction,
all the condition must be true for the transaction. We can create conditions based
on the attributes.
Ordinary header conditions are based on columns of the Expense report Header
i.e, AP_EXPENSE_REPORT_HEADERS_ALL table.
An example is if the EXPENSE_REPORT_TOTAL <= 5000 US Dollars
3. Actions
4. Rules
Creating rules and rule usages is the main step in the AME implementation
process. Rarely will an organization’s business rules match any rules that are
seeded with a transaction type. Instead, you must translate the business rules you
documented into AME rules yourself. Rule associate one or more conditions with
an approval in an “if-then” statement. Before you can create rules, you must
create conditions for the rules to use. You may need to create (or have a system
administrator create) some custom attributes and/or approvals. Thus, while
creating rules is your ultimate goal, it is also the last thing you do when you set up
AME.
Please note that AME Patchset used for this setup is AME.A (Patch #3962268). If you
are using higher version of AME Patchset level, the User Interface may change slightly.
a) Create Attributes
Using Responsibility: AME Application Administrator N >Approvals >
Attributes
In our case, it is a dynamic usage and the following SQL query is used
select fnd_number.number_to_canonical(erh.total),
nvl(erh.default_currency_code,asp.invoice_currency_code),
nvl(erh.default_exchange_rate_type,asp.default_exchange_rate_type)
from ap_expense_report_headers_all erh, ap_system_parameters_all asp
where erh.report_header_id = :transactionId
and erh.org_id = asp.org_id
9. Select the Continue button. Note: AME will confirm the creation of the
attribute for you.
10. Select the Quit button to return back to the main menu page.
b) Create Conditions
1. Check if required conditions exist. If not add one by scrolling to the end of
the conditions page and select Add a Condition button.
2. Select an ordinary header/line condition type (in our case header).
3. Select the continue button.
4. In the attribute field select EXPENSE_REPORT_TOTAL from the list of
values.
5. Select the continue button.
6. Select the Currency code say USD
7. Enter 0 in the lower limit field.
8. Enter 5000 in the upper limit field.
9. Select “yes” for include lower limit.
10. Select “yes” for include upper limit
11. Select the Create Condition button.
12. AME will confirm the condition being added successfully.
Similar condition created for condition EXPENSE REPORT TOTAL >= 5001
USD
Below is the screenshot of the condition EXPENSE REPORT TOTAL >= 5001
USD
c) Create Actions
In the actions types page view scroll down to view the supervisory level chain of
authority.
Verify that these attributes have been defined for OIE Expense Report transaction
type. N > Approvals > Attributes
1. Select the OIE Expense Report transaction type from the list of values.
2. Select the continue button.
3. Scroll down and check the non-mandatory attributes list to see if the
following attributes appear and proper usage is setup
• SUPERVISORY_NON_DEFAULT_STARTING_POINT_PERS
ON_ID
• TOP_SUPERVISOR_PERSON_ID
• TRANSACTION_REQUESTOR_PERSON_ID
4. Add these attributes if they are missing.
Our objective in the test case is to setup simple rules such as:
Below is the Rule defined where by all expense reports submitted in set of books
1 having an expense total of less than 5000 USD would require approval of at
least 2 supervisors
Below is the Rule defined where by all expense reports submitted in set of books
1 having an expense total of less than 5000 USD would require approval of at
least 2 supervisors
With these two list creation rule of type chain of authority based on number of
supervisory levels in place all Expense reports submitted in set of books ID 1
would be subject to approval through AME. The approver list would contain 2
supervisors if the expense report amount is <=5000 USD and 3 supervisors if the
expense report amount is >=5000 USD
Test case 1:
Rob Alan will submit expense report of 1000 USD from set of books ID 1. This
should be routed for approval to 2 supervisors up the chain i.e. Stock Patt and
Russ Mitchell
Test case 2:
Rob Alan will submit expense report of 6000 USD from set of books ID 1. This
should be routed for approval to 3 supervisors up the chain i.e. Stock Patt, Russ
Mitchell and Mike Edwards.
Click on View Transaction Productions > Continue > View Final Approver List
f) Simulation
Enter Expense report for 100 USD and find that the report goes for approval to 2
supervisors up the chain. Once approved by the supervisors, you find the details
in Approval Note section as under in the expense report history
In our test case, Mike Edwards is the Top supervisor and so his person_id is given as
a static usage. Supervisory level chain of authority action will consider
TOP_SUPERVISOR_PERSON_ID only when the action is of type ‘ATMOST’
With the above setup, when CEO creates Expense reports, the report is AUTO
APPROVED.
Oracle Corporation
Author and Date
Sriram Ramanujam, Nivas Ramanathan May 2006
Copyright Information
Copyright © 2006 All rights reserved.
Disclaimer
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Trademark Information
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation
and/or its affiliates. Other names may be trademarks of their respective owners.