Using and Maintaining Oracle Approvals Management (AME) Student Guide

Using and Maintaining Oracle
Approvals Management
(AME)
Student Guide
Internal Use Only
Copyright Oracle International Corporation, 2003. All rights reserved.

This documentation contains proprietary information of Oracle International Corporation. It is provided under a license agreement
containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is
prohibited. If this documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with
Restricted Rights and the following legend is applicable:
Restricted Rights Legend
Use, duplication or disclosure by the Government is subject to restrictions for commercial computer software and shall be deemed
to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in
Technical Data and Computer Software (October 1988).
This material or any portion of it may not be copied in any form or by any means without the express prior written permission of the
Education Products group of Oracle International Corporation. Any other copying is a violation of copyright law and may result in
civil and/or criminal penalties.
If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with
Restricted Rights, as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in the documentation, please report
them in writing to Worldwide Education Services, Oracle International Corporation, 500 Oracle Parkway, Box SB-6, Redwood
Shores, CA 94065. Oracle International Corporation does not warrant that this document is error-free.
Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle International Corporation.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Author
Ratna Kuplish
Technical Contributors and Reviewers
John Cafolla, Sarju Shah, Kev Koh, Bill Kerr
This book was published using:
oracletutor
Table of Contents
Using and Maintaining Oracle Approvals Management..............................................................................1-1
Using and Maintaining Oracle Approvals Management (AME) ...................................................................1-2
Objectives ......................................................................................................................................................1-3
Topics Covered..............................................................................................................................................1-4
Using and Maintaining Oracle Approvals Management - Introduction.....................................................2-1
Using and Maintaining Oracle Approvals Management (AME) Introduction ..............................................2-2
Objective........................................................................................................................................................2-3
Business Processes or Transactions and Approvals.......................................................................................2-4
What is AME? ...............................................................................................................................................2-6
When Can I Use AME? .................................................................................................................................2-7
Business Requirements..................................................................................................................................2-8
Overview of AME Components ....................................................................................................................2-9
Mapping Business Requirements ...................................................................................................................3-1
Mapping Business Requirements ..................................................................................................................3-2
Approval Policies ..........................................................................................................................................3-3
Approval Policies Attributes.......................................................................................................................3-5
Examples of Approval Policies .....................................................................................................................3-6
Vision Gift Basket Scenario ..........................................................................................................................3-7
Vision Gift International" Organisation Chart...............................................................................................3-9
Setup Required for Gift Basket Rules............................................................................................................3-10
Building List Creation Rules - 1 .....................................................................................................................4-1
Building List Creation Rules Part 1..............................................................................................................4-2
Objective........................................................................................................................................................4-3
Approval Policies ..........................................................................................................................................4-4
Approval Policies Rule Components..........................................................................................................4-5
Steps For Defining List Creation Rules.........................................................................................................4-6
List Creation Rule - Attributes .....................................................................................................................4-8
List Creation Rules - Conditions ...................................................................................................................4-10
Conditions Numbers and Ranges..................................................................................................................4-11
Approval Types and Rule Types ...................................................................................................................4-12
Approval Types for List Creation Rules........................................................................................................4-13
Supervisor Approval Type.............................................................................................................................4-15
Overview of Rules .........................................................................................................................................4-17
Setup Required for Defining List Creation Rules..........................................................................................4-18
Practice - Building List Creation Rules - 1................................................................................................4-20
Solution Building List Creation Rules - 1...............................................................................................4-22
Testing the List Creation Rule........................................................................................................................5-1
Testing The List Creation Rule......................................................................................................................5-2
Objective........................................................................................................................................................5-3
Testing Rules with Transactions....................................................................................................................5-4
Test Tab Creating Test Transactions ............................................................................................................5-5
Testing List Creation Rule Transaction .........................................................................................................5-6
Practice - Testing The List Creation Rule..................................................................................................5-7
Test Tab Viewing Approvals........................................................................................................................5-10
Building List Creation Rules - 2 .....................................................................................................................6-1
Building List Creation Rules Part 2..............................................................................................................6-2
Objective........................................................................................................................................................6-3
Approval Policy.............................................................................................................................................6-4
Steps For Defining List Creation Currency Rule...........................................................................................6-5
Copyright Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management (AME) Table of Contents

i
Using Currency Attributes.............................................................................................................................6-6

Using Currency Conditions ...........................................................................................................................6-8
Relative Job Level Approval Type ................................................................................................................6-9
Default and Non Default Starting Points .......................................................................................................6-10
Setup Required for Defining List Creation Rule with Currency....................................................................6-11
Practice - Building List Creation Rules - 2................................................................................................6-13
List Modification and Substitution Rules......................................................................................................7-1
List Modification and Substitution Rules ......................................................................................................7-2
Objective........................................................................................................................................................7-3
Approval Policy Rule Components ............................................................................................................7-4
Steps For Defining Substitution Rule ............................................................................................................7-5
List Modification Conditions.........................................................................................................................7-6
List Modification Approval Types ................................................................................................................7-7
Substitution Approval Type...........................................................................................................................7-8
Setup Required for Defining List Modification Rule ....................................................................................7-9
Practice - List Modifications and Substitution Rules.................................................................................7-11
Solution List Modifications and Substitution Rules ...............................................................................7-13
Defining and Using Approval Groups ...........................................................................................................8-1
Defining and Using Approval Groups ...........................................................................................................8-2
Objective........................................................................................................................................................8-3
Approval Policy - Rule Components ............................................................................................................8-4
Steps for Defining Pre Approval Group Rule................................................................................................8-5
Boolean Attributes and Conditions................................................................................................................8-6
Approval Groups ...........................................................................................................................................8-7
Using Dynamic Approval Groups .................................................................................................................8-9
How Nested Approval Groups Work.............................................................................................................8-11
Approval Types Approval Group Rules ........................................................................................................8-13
Setup Required for Defining and Using Approval Groups............................................................................8-14
Practice - Defining and Using Approval Groups .......................................................................................8-16
Solution Defining and Using Approval Groups......................................................................................8-18
Defining Exception Rules for List Creation ..................................................................................................9-1
Defining Exception Rules for List Creation ..................................................................................................9-2
Objectives ......................................................................................................................................................9-3
Understanding Exception Conditions and Rules ...........................................................................................9-4
Ordinary Conditions and Multiple Rules.......................................................................................................9-5
Understanding Exception Conditions and Rules ...........................................................................................9-6
Steps for Defining Exception Rules...............................................................................................................9-8
Setup Required For Dealing With Exception Rules ......................................................................................9-9
Practice - Defining Exception Rules for List Creation ..............................................................................9-11
Solution Defining Exception Rules for List Creation .............................................................................9-12
Effective Dates for Rules and Attributes .......................................................................................................10-1
Effective Dates For Rules and Attributes ......................................................................................................10-2
Objectives ......................................................................................................................................................10-3
Approval Policy - Rule Components .............................................................................................................10-4
Effective Dates and Rules..............................................................................................................................10-5
Mandatory Date Attributes ............................................................................................................................10-6
Transaction Date and AME ...........................................................................................................................10-7
Setting Conditions On Date Attributes ..........................................................................................................10-8
Steps For Defining Rule With Effective Date ...............................................................................................10-9
Setup Required For Defining Rules With Future Effective Dates.................................................................10-10
Practice - Effective Dates for Rules and Attributes ...................................................................................10-11
Solution Defining and Using Approval Groups......................................................................................10-12

ii
Line Level Attributes and String Attribute Types........................................................................................11-1

Line Level Attributes and String Attribute Types .........................................................................................11-2
Objectives ......................................................................................................................................................11-3
Steps For Defining Line Item Rules ..............................................................................................................11-5
Attribute Levels .............................................................................................................................................11-6
String Attributes Types..................................................................................................................................11-7
How AME uses Attributes.............................................................................................................................11-9
Understanding Multiple Conditions...............................................................................................................11-10
Defining Line Items with Restrictive Evaluations.........................................................................................11-13
Setup Required For Defining Line Item Rule................................................................................................11-16
Practice - Line Level Attributes and String Attribute Types .....................................................................11-18
Solution Line Level Attributes and String Attribute Types ....................................................................11-19
Dual Chains of Authority................................................................................................................................12-1
Dual Chains Of Authority..............................................................................................................................12-2
Objective........................................................................................................................................................12-3
Steps For Defining Dual Chain of Authority Rules.......................................................................................12-5
Dual Chains of Authority ..............................................................................................................................12-7
Dual Chains of Authority Attributes..............................................................................................................12-8
Dual Chains Of Authority Rules....................................................................................................................12-9
Setup Required For Defining Dual Chain Of Authority Rules ......................................................................12-10
Practice - Dual Chains Of Authority..........................................................................................................12-12
Solution Dual Chains Of Authority ........................................................................................................12-13
Handling Multiple Rules on Transactions.....................................................................................................13-1
Handling Multiple Rules On Transactions ....................................................................................................13-2
Objective........................................................................................................................................................13-3
How AME Sorts Rules At Run Time ............................................................................................................13-4
Rule Sharing In AME ....................................................................................................................................13-6
Setup Required For Rule Sharing ..................................................................................................................13-8
Practice - Handling Multiple Rules On Transactions ................................................................................13-9
Solution Handling Multiple Rules On Transactions ...............................................................................13-10
Rule Priorities ..................................................................................................................................................14-1
Rule Priorities................................................................................................................................................14-2
Objective........................................................................................................................................................14-3
Rule Priorities................................................................................................................................................14-4
Enabling Rule Priorities.................................................................................................................................14-5
Enabling Rule Priorities - Modes ..................................................................................................................14-6
Enabling Rule Priorities - Attributes .............................................................................................................14-8
Setup Required For Rule Priorities................................................................................................................14-9
Demo - Rule Priorities ...............................................................................................................................14-11
Summary ..........................................................................................................................................................15-1
Using and Maintaining Oracle Approvals Management (AME) ...................................................................15-2
Objectives ......................................................................................................................................................15-3
Topics Covered..............................................................................................................................................15-4

iii

v

Approvals Management
Chapter 1
Using and Maintaining Oracle Approvals Management

Chapter 1 - Page 1
Using and Maintaining Oracle Approvals Management (AME)

Chapter 1 - Page 2
Objectives
Objectives
Please note that this class is a follow up to the AME overview class, which is available from
OUOL. The overview class covers the basic concepts of rules, conditions, attributes and
groups.
The focus of this class on the practices that will follow each topic whereby the options of
defining different types of rules are demonstrated.

Chapter 1 - Page 3
Topics Covered

Chapter 1 - Page 4
Topics Covered

Chapter 1 - Page 5

Chapter 1 - Page 6

Approvals Management Introduction
Chapter 2
Using and Maintaining Oracle Approvals Management - Introduction

Chapter 2 - Page 1

Introduction

Chapter 2 - Page 2
Objective
Objective
Please access the Oracle Approvals Management Overview eclass for an overall understanding
of rules, attributes, conditions, groups and testing rules.

Chapter 2 - Page 3
Business Processes or Transactions and Approvals
Business Processes or Transactions and Approvals

Most business processes or transactions follow a common pattern:
1. Start the process by creating a document that includes the details for the transaction. The
document could be a paper document, a form or a webpage.
Consider, an expenses claim, a purchase order, the transfer of an employee, or any other
common process. All involve a request for some action, and the details are captured in
the document.
The details for many types of transaction are held until the transaction is finally approved
and the underlying records are only updated after final approval.
2. When the details are entered, the user submits the transaction for approval.
For a paper document you would typically mail this to your manager or professional
support person.
For business processes delivered with the Oracle eBusiness suite you can use Oracle
WorkFlow with Oracle Approvals Manager (AME) to automate the management of
approvals and notifications.
3. Approvals processing should follow your own business rules for each type of transaction.

Chapter 2 - Page 4
For example, you may have different routing rules for expenses and purchasing, or for
different departments; or you may require different levels of approval based on the total
value of an order, or based on specific details in the document.
Approvals usually involve a combination of notifications and standard responses to
notifications. For example, Oracle Applications use Approve, Reject and Return as
standard responses.
4. When finally approved the underlying records are updated.

Chapter 2 - Page 5
What is AME?
What Is AME?
Calling application refers to the application that is using AME components to define the
approval process. Calling applications can be Oracle applications or any application that is uses
PL/SQL code.

Chapter 2 - Page 6
When Can I Use AME?

Chapter 2 - Page 7
Business Requirements
Business Requirements: Example of approval loop using AME

The diagram above shows a basic business process using AME.
1. An employee creates their expense reports
2. An employee submits their expenses for approval.
3. These expenses go to the immediate manager (defined in the supervisor hierarchy) who
may have a sign off limit.
4. If the expenses cannot be approved by the immediate manager, they will then get passed to
the next manager in the chain.
5. The expenses get paid.
You can use AME, to define simple or complex rules which allow line level approval
based on the sign off authority. For example, you may want to set up approval rules,
which say that if an expense value is below $100, then manager 1 can approve the
expenses and if the value is more than $100, then manager 2 needs to approve the
transaction.

Chapter 2 - Page 8
Overview of AME Components

Chapter 2 - Page 9

Chapter 2 - Page 10
Mapping Business
Requirements
Chapter 3
Mapping Business Requirements

Chapter 3 - Page 1

Chapter 3 - Page 2
Approval Policies

Chapter 3 - Page 3
Approval Policies

Chapter 3 - Page 4
Approval Policies Attributes
Approval Policies Attributes

Note: Currency attributes have more than one value. When using currency attributes you use
the following values:
Amount
Denomination
Rate Type

Chapter 3 - Page 5
Examples of Approval Policies

Chapter 3 - Page 6
Vision Gift Basket Scenario
Vision Gift Basket Scenario

This class is going to demonstrate each of the above approval and discuss and demonstrate how
to define the specific attributes, conditions and rules. The test tab will be used to create test
transactions to test the rules and the list of approvers displayed.
The test tab will create test transactions, to test the rules and list the approvers.
Vision Gifts International, Inc. is an organisation selling company promotional goods (such as
baseball caps, key rings, tee-shirts, sweatshirts etc). These goods are sold via telephone orders,
which are entered by administrators who work for Vision Gifts International. Vision has a
number of product lines, and a large catalogue of products.
The company has recently installed software to assist the managers with approvals for various
types of transactions. This fictitious software called, Vision Gift Basket (VGB) is
integrated with Oracle Approvals Management (AME).
The Vision Gift Basket (VGB Clothing Basket) has been created in AME as a transaction type
and most of the demonstrations will be based on this transaction type.
Visions management is concerned about the lack of controls around the sales of the gift basket
configurations via the internet, and is implementing new approval rules to prevent incorrect
items and prices going out.

Chapter 3 - Page 7
The management has asked for these approvals to be defined and tested in AME.

Chapter 3 - Page 8
Vision Gift International Organisation Chart
Vision Gift International - Organisation Chart

The sample Organisation chart above shows relationships of individuals with their Job Levels
in Oracle HRMS.
In the organization chart above, Vincent Price is the last person in the approval chain and
is therefore at job level 6.
Pauline Newmans manager is Lucy Lawson and Lucy reports to Vincent Price.
In the second chain, Fred Mason reports to B. Taylor and Taylors manager is C. Jones.
Mr Jones also reports to Vincent Price.
During this eclass we will be referring to all three chains for the various examples of
approvals rules.

Chapter 3 - Page 9
Setup Required for Gift Basket Rules
Setup Required for Gift Basket Rules

Note the demonstrations and practices in this module will take you through the decisions
and discuss the setup of each type of approval rule showing how different attributes,
conditions, approvals and rules can be defined to achieve a particular type of approval.

Chapter 3 - Page 10
Building List Creation Rules 1

Chapter 4
Building List Creation Rules - 1

Chapter 4 - Page 1
Building List Creation Rules Part 1

Chapter 4 - Page 2
Objective

Chapter 4 - Page 3
Approval Policies
Approval Policies
At the end of this topic the demonstration will show you how to define the 3 rules mentioned
above.
The rules are all list creation rules which use an approval type of chains of authority based
supervisory levels. The number of items in the basket determine how high up the chain the
approval needs to ascend.
The above rule requires you to define a number of items attribute.
There will be 3 different conditions created as the approval levels vary according to the number
of items in the basket.
Finally you will need to define 3 different rules each using one of the conditions defined.

Chapter 4 - Page 4
Approval Policies Rule Components

Chapter 4 - Page 5
Steps For Defining List Creation Rules
Steps For Defining List Creation Rules

1. Defining Attributes - In the example being discussed the attribute is the Number of items
in the basket. When you define attributes they are saved as non-mandatory attributes, which
can be deleted or modified. AME will check when you delete attributes to ensure that they
are not already being used with any rules. Although attributes are specific to transactions
types they can be shared across transaction types by sharing the name of the attribute and
defining specific usages for the attribute.
2. Conditions In our example we would like to perform 3 different types of actions
depending on the number of items in the basket, therefore we must define 3 conditions with
varying numeric ranges. Condition are specific to transaction types. AME will let you
modify conditions. You can delete conditions, provided they are not used within a rule.
3. Rules this step combines the attribute and condition that you defined, and associates
these to a list creation rule which you will test at run time by creating test transactions.
Rules are unique to each transaction type. AME does allow rules to be shared across
different transaction types. You can also modify the behaviour of conditions when defining
rules, thus reducing maintenance.

Chapter 4 - Page 6
4. Testing this is a very useful step as it allows you to create test transactions by entering the
values to test, rather than having to fetch values from actual SQL tables only to find that a
rule is missing a particular test criteria.

Chapter 4 - Page 7
List Creation Rule - Attributes
List Creation Rules Attributes

For the List Creation rule example we are defining a numeric attribute because the approval
policy is checking the number of items in the basket to determine the approval required.
Attributes names can be shared across transaction type, however by defining unique usages
you can determine various ways of using the attribute.
Attribute usages can be dynamic or static. For the purposes of this demonstration we are going
to use static usages as we are using a fictitious application for testing the rules. This means
that when we create test transactions in the test tab values representing the number of items in
the basket will be entered and the rule evaluated.
You define attribute usages and the Usages function gives you flexibility.
For example:
select
fnd_number.number_to_canonical(ai.PO_TRANSACTION_AMOUNT),
nvl(ai.Transaction_Currency_Code,asp.Transaction_Currency_Code)
,
nvl(ai.Exchange_Rate_Type,asp.Default_Exchange_Rate_Type)

Chapter 4 - Page 8
from
po_transaction_all ai, po_system_parameters_all asp
where
ai.purchase_order_id = :transactionId
and
ai.org_id = asp.org_id
You define dynamic usages of an attribute and in the usage field by entering SQL statements
which will retrieve the data from tables and columns specified.
User defined attributes are listed as non-mandatory attributes since these are defined according
to the requirements of the transaction.
Note that AME also has:
Mandatory attributes are system level attributes and cannot be deleted. These attributes
are delivered with AME to meet most business requirements.
Required attributes are required for certain approval types.

Chapter 4 - Page 9
List Creation Rules - Conditions
List Creation Rules - Conditions

Conditions can be defined at header or line level. Header conditions apply to transaction
headers for example in the list creation rule scenario we will define a header condition
which will apply to all lines in the transaction.
You can use ordinary and exception condition types with attributes that have a list or a
range of possible values such as number of items in the basket from 0 - 5 etc . At run
time, if the attribute has this value, then the condition is true, otherwise the condition is
false.
Ordinary conditions can occur in all rule types
For this list creation rule we are going to use an ordinary header condition in the
following format:
- Number
Lower limit <{=} attribute name <{=} upper limit

Chapter 4 - Page 10
Conditions Numbers and Ranges
Conditions Numbers and Ranges

Note that when you define numerical conditions AME inserts the < or <= symbols in the
completed condition according to the answers in the following prompts:
Upper Limit use this to assign the highest numerical value required to evaluate.
Lower Limit use this to assign the lowest numerical value to evaluate.
Include Upper Limit a yes prompt here will insert a <= symbol with the upper limit.
A no prompt will end the range below this value. So for example if the Upper Limit is 5 and
you enter a no in the use upper limit field the range will end at a value <5.
Include Lower Limit - a yes prompt here will insert a <= symbol with the lower limit.
A no prompt will start the range one number after this value. So for example if the lower
Limit is 0 and you enter a no in the use upper limit field the range will start at 1. Therefore if
you have a range of numbers to be used in the approval it is better to enter a yes in the include
upper and lower limit fields to ensure that the range values and inclusive.
Note that AME does not use the > symbol.

Chapter 4 - Page 11
Approval Types and Rule Types
Approval Types and Rule Types

For our list creation rule example we are going use the supervisory level approval type as we
want to ascent the supervisor chain of authority and list the managers who can approve
transactions depending on the number of items in the basket.

Chapter 4 - Page 12
Approval Types for List Creation Rules
Approval Types - List Creation and Exception Rules

Supervisor Level: You may have to specify the starting point of the chain by selecting the
supervisor level in the hierarchy.
Relative Job Level: You may have to specify the starting point of the chain by selecting
the job level in the hierarchy.
Absolute Job Level uses the supervisor hierarchy to generate the default chain of
approvers, but it also uses the job hierarchy to determine the start and end points of the
chain. You, therefore, must ensure that the approvers, defined as employees, have both
the supervisor as well as job level hierarchies defined in order for this rule to work.
- If you are using a chain-of-authority approval type, then you must consider the
starting point of the chain, that is, which approver.
- For single chains of authority, AME defaults to the transaction requestor, that is the
person initiating the transaction, but you can override this if you wish.
Manager then Final will include the first and last approvers in any chain of authority. For
example, in our purchase order chain of authority, this will include Mike Morney and
Vincent Price.

Chapter 4 - Page 13
For dual chains of authority (useful, for example, when a person is being transferred from
one manager to another), you must define usages for first and second starting point
attributes.
When you transfer a person from one manager to another, dual chains of authority can be
used with the selected persons current manager as the first starting point in the chain and
the proposed manager as the second starting point.

Chapter 4 - Page 14
Supervisor Approval Type
Supervisor Approval Type

When using the supervisor hierarchy with a job level, you must define jobs and levels before
assigning these to the employees.
The number of supervisors that are selected in the approval list, depends on where the chain
starts and ends.
The start point of the chain depends of the value of the required attribute and how high in
hierarchy the ascent goes depends on the particular approval and the required attribute of this
approval.
By default the starting point of this chain would be the supervisor of the person who initiates
the transaction. This person is identified by the mandatory attribute
TRANSACTION_REQUESTOR_PERSON_ID
However if a value is specified for the
SUPERVISORY_NON_DEFAULT_STARTING_POINT_PERSON_ID then AME will
bypass the transaction requestors supervisor and go to the person specified in this chain and
then ascend up this chain of authority instead selecting all supervisors as approvers.

Chapter 4 - Page 15
If the value for the SUPERVISORY_NON_DEFAULT_STARTING_POINT_PERSON_ID is

null for a given transaction, the transaction's chain of authority will start with the supervisor of
the person identified by TRANSACTION_REQUESTOR_PERSON_ID.
The end point of the ascent is reached when the TOP_SUPERVISOR_PERSON_ID value is
reached. If this is a null value, AME will raise an exception because it cannot find a supervisor
while ascending the supervisory hierarchy.

Chapter 4 - Page 16
Overview of Rules
Rules
By combining rule types with conditions and approval types, you produce different effects on a
transactions approver list.
You must define your approval groups before using the pre or post list approval types.
List-creation rules will generate a chain of authority for your transaction.
List-creation exception is used with the list creation rule, but it creates an exception to the
list generated.
List-modification rules modify the default chain of authority that is generated by the list
creation and exception rules.
You can use substitution rules to replace an approver with another specified approver in
the chain of authority.
You can use the pre and post approval groups rules to insert a group of approvers either
before or after in the chain of authority.

Chapter 4 - Page 17
Setup Required for Defining List Creation Rules
Setup Required for Defining List Creation Rule

The notes following this slide give you details, step by step for the demonstration being
performed by the instructor.
When analysing the approval required for the above example you need to think about the
rule types you may want to use. For example think about which rule type will generate a
chain of authority using the supervisor hierarchy and how you may want modify the
default supervisors that would be selected according to the number of items in the
shopping basket.
Next consider the conditions you would need to create and then determine the attribute
that will be most suitable to use.
To set up the example of value and job approval for the purchase order you will need to follow
the steps below:
1. Create an attribute for this transaction type called for example
NUMBER_OF_ITEMS_IN_BASKET.
2. Create multiple ordinary header conditions by using the attribute defined in step 1. Enter
the value ranges for approval amounts, that is, from 0 5, 6- 10 and 11 onwards.

Chapter 4 - Page 18
Note that you will need to create multiple conditions for each of the ranges
required.
3. Create multiple list creation rules to match the conditions defined earlier. Each rule,
which will have an approval type of chains of authority based on number of supervisory
levels. and the approval will determine how high to go in the approval list. Finally you
select the condition with the value range when defining rules.
4. Test the rule by selecting the create a test transaction option. This is because we are
using a fictitious application called Vision Gift Basket and the attribute usage was
defined as static. Testing is covered in more detail in the next topic.

Chapter 4 - Page 19
Practice - Building List Creation Rules - 1

Overview
In this practice you will add the following rules to the clothing basket transaction type:
Rule A If the basket contains 0 5 items then approval has to be done by the immediate
supervisor of the person submitting the transaction
Rule B If the basket contains 6 10 items then approval has to be done by the second
immediate supervisor in the chain of authority as well as the immediate supervisor of the
person submitting the transaction.
Rule C if the basket contains 11 or more items then approval has to be done by the third
immediate supervisor in the chain of authority as well as the second immediate supervisor of
the person submitting the transaction.
Assumptions
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
The names used throughout this practice are for the purpose of the practice and bear no
resemblance to any particular organization or individuals
Prefix all names of rules, attributes and conditions with your assigned unique group
number or your initials.
Use the General Business User responsibility for all practices unless stated otherwise
Tasks
Defining Attributes
You will need to define one non-mandatory header number attribute for the 2 rules mentioned
above. This attribute will then be associated with the condition and rule that will be defined later.
Note: this rule is going to use the supervisory approval type, which has 2 required attributes.
When you are defining attributes check that the following required attributes do appear on
the attributes page:
SUPERVISORY_NON_DEFAULT_STARTING_POINT_PERSON_ID
TOP_SUPERVISOR_PERSON_ID

Chapter 4 - Page 20
Defining Conditions
You will need to define three ordinary header conditions for the ranges of items in the basket
specified. These ranges will be from 0 5, 6- 10 and 11 upwards.
Defining Rules
You will define three list creation rules, which will use the attributes, conditions and approval
types defined. The ranges of the 3 rules will be as follows:
0 5 items
6- 10 items
11 or more items

Chapter 4 - Page 21
Solution Building List Creation Rules - 1

Defining Attributes
Responsibility = AME General Business User, Approvals
1.
Navigate to the Attribute window.
(N) Approvals > (T) Attributes
2.
Change the transaction type to VGB Clothing Basket from the list of values available and
select the continue button.
3.
Scroll to the end of the page and select the Add Attribute button
4.
Select the header attribute button.
5.
Select Create New Name button from the Create an Attribute Step 1 page.
6.
Enter XX_VGB_NO_OF_ITEMS_IN_BASKET in the name field and select the continue

button. (Replace XX with your initials or your terminal number.)
7.
Select an Attribute type of number.
8.
Enter XXs number of items in basket in the description field. (Replace XX with your name
or terminal number.)
9.
Select static yes.
10. Leave the Usage area blank.

11. Select the Create Attribute button.
Note: AME will confirm the creation of the attribute for you.
12. Select the Quit button to return back to the main menu page.
Defining Conditions
Navigate to the Conditions window.
(N) Approvals > (T) Conditions
1.
Change the transaction type to VGB Clothing Basket from the list of values and select the
continue button.
2.
Scroll to the end of the conditions page and select Add a Condition button.

Chapter 4 - Page 22
3.
Select an ordinary header condition type.
4.
Select the continue button.
5.
In the attribute field select XX_VGB_NO_OF_ITEMS_IN_BASKET from the list of

values.
6.
Select the continue button to enter the first range of items( from 0 5).
7.
Enter 0 in the lower limit field.
8.
Enter 5 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.
13. Repeat steps 2 to 11 for the second range (from 6 to 10) with the following values:
Enter 10 in the upper limit field.
Select yes for include upper limit
14. Repeat steps 2 to 11 for the third range (from 11 onwards) with the following values:
Leave the upper limit field blank.
Select yes for include upper limit
Defining Rules
Navigate to the Rules window.
(N) Approvals > (T) Rules
15. Change the transaction type to VGB Clothing Basket from the list of values and select the
continue button.
16. Scroll to the end of the attributes page and select the Add A Rule button to define the first
rule for a range of items within 0 5.

Chapter 4 - Page 23
17. Enter XX VGB_0_TO_5_ITEMS IN BASKET in the description field.

18. Select list-creation rule in the rule type field.
19. Accept the default system date as the start date.
20. Enter none in the end date.
21. Select the continue button.
22. Select the approval type of chains of authority based on number of supervisory levels.
24. In the approval field select Require approvals up to the first superior at most.
26. Select XX_VGB_NO_OF_ITEMS_IN_BASKET in the Ordinary Conditions Header
Attributes field.
27. Do not select anything in the Ordinary Conditions Line Item Attributes field.
28. Select the continue button to display Add A Rule Step 5 page.
29. Check the ordinary condition 0 <= VGB_NO_OF_ITEMS_IN_BASKET <= 5 from the
list available.
31. AME will confirm the rule being successfully added.
32. Scroll to the end of the attributes page and select the Add A Rule button to define the second
33. Enter XX VGB_6_TO_10_ITEMS IN BASKET in the description field.
40. In the approval field select Require approvals up to the first two superior at most.

Chapter 4 - Page 24

Attributes field.
45. Check the ordinary condition 6 <= VGB_NO_OF_ITEMS_IN_BASKET <= 10 from the
list available.
48. Scroll to the end of the attributes page and select the Add A Rule button to define the third
rule for a range of items from 11 upwards.
49. Enter XX VGB_MORE_THAN_11_ITEMS IN BASKET in the description field.
56. In the approval field select Require approvals up to the first three superiors at most.
Attributes field.
61. Check the ordinary condition 11 <= VGB_NO_OF_ITEMS_IN_BASKET from the list
available.

Chapter 4 - Page 25
64. Select the Quit button to return back to the approvals menu page.

Chapter 4 - Page 26
Testing the List Creation Rule

Chapter 5

Chapter 5 - Page 1
Testing The List Creation Rule

Chapter 5 - Page 2
Objective

Chapter 5 - Page 3
Testing Rules with Transactions
Testing Rules With Transactions

The 2 features of the test tab allow you to create a fictitious transaction or view how
AME will process a real transaction fetched by the transaction id entered. In both cases
no information is passed back to the calling application and no notifications are produced.
These features allow you to check the rules defined in AME before starting to update any
information back to the calling application.
For the purpose of our demonstrations we are going to create test transactions for all
testing of the rules as we are using a fictitious application Vision Clothing Basket and
therefore do not have any SQL tables that we would normally use when addressing
dynamic usages for example.

Chapter 5 - Page 4
Test Tab Creating Test Transactions
Test Tab Creating Test Transactions

Using this feature you create a fictitious transaction and select the attribute values for the
transaction. You can change the attributes values as often as you like to see how each change
effects which rules apply and the resulting approvers list. You can use this feature to test the
boundary conditions of the rules you may have defined.
Note that when you create a transaction using this feature AME will prefix the transaction
number with a minus sign to distinguish this from a real transaction id number.
Transactions created using this feature are stored within AMEs transactions tables.

Chapter 5 - Page 5
Testing List Creation Rule Transaction
Testing List Creation Rule Transaction

The rules defined in the previous topic will be used when creating test transactions with
various values being entered to see how AME will choose the appropriate approver, based
on the value of the transaction. Please see the demonstration at the end of this topic which
will display the results of these test transactions.
The tests will be done in three stages using Sarah Bellem as the person submitting the
transaction:
Stage 1 we will enter a value between 0 - 5 and see the approvers. The test should show
Mike Morneys name as he is Sarahs immediate supervisor.
Stage 2 we will enter a value between 6 - 10 and see the approvers. The test should show
Mike Morney and Geoff Walker as the approvers as the second condition asked for 2
approvers ascending up the chain of authority.
Stage 3 we will enter a value more than 10 and the approvers should be Mike Morney,
Geoff Walker and Susan Price because the condition is asking for 3 approvers to be
selected.

Chapter 5 - Page 6
Practice - Testing The List Creation Rule

Overview
In this practice students will test the rules created earlier using the create a test transaction option
as we are testing with a fictitious application The 3 rules to be tested are:
Rule A If the basket contains 0 5 items then approval has to be done by the immediate
supervisor of the person submitting the transaction.
Rule B If the basket contains 6 10 items then approval has to be done by the second
immediate supervisor in the chain of authority as well as the immediate supervisor of the
person submitting the transaction.
Rule C if the basket contains 11 or more items then approval has to be done by the third
immediate supervisor in the chain of authority as well as the second immediate supervisor of
the person submitting the transaction.
Assumptions
Use Sarah Bellem for this test.
Tasks
Testing Rules
You will test three list creation rules, using the test tab. The ranges of the 3 rules are as follows:
0 5 items
6- 10 items
11 or more items

Chapter 5 - Page 7

Testing Rules
1.
Navigate to the Test window.
(N) Approvals > (T) Test
1.
Select the test tab.
2.
continue button.
3.
In the Choose Test Type page select Create a test transaction.
4.
5.
Choose a requestor type of person.
6.
Enter Bellem in the Last Name field and select the search button.
Note: AME will retrieve all records that match the search criteria. In this case there is only
one employee record with this name, Sarah Bellem.
7.
8.
In the Mandatory Attributes section turn off the following attributes by changing the value
to no:
EVALUATE_PRIORITIES_PER_LINE_ITEM
USE_RESTRICTIVE_LINE_ITEM_EVALUATION
9.
Scroll down the page to display the non-mandatory attributes available with the VGB
Clothing Basket transaction type.
Note: AME will insert Sarah Bellems name as the
TRANSACTION_REQUESTOR_PERSON_ID.
10. Enter no against any attributes that you do not want to be checked with this rule for
example:
VGB_IS_GIFT_WRAPPED
VGB_IS_NEW_BASKET

Chapter 5 - Page 8
11. Enter a value less than 6 (for example 5) in the attribute called
XX_VGB_NO_OF_ITEMS_IN_BASKET
Note: The only rule being applied for this test transaction is a list creation rule called
VGB_NO_OF_ITEMS_IN_BASKET, which we had defined earlier.
12. Select the note pad icon to display full details about this rule.
13. Scroll to the end of the page and select the view approval list button.
Note: In the list of approvers you will see Mike Morneys name.
14. Select the Change Attribute Values button.
15. Change the value for the XX_VGB_NO_OF_ITEMS_IN_BASKET attribute to 7.
Note: There is a different rule being applied to this transaction as the value of the number of
items in the basket has changed from 5 to 7.
16. Select the View Approval Process button.
You will see Mike Morney and Geoff Walkers names as the approvers
18. Change the value for the XX_VGB_NO_OF_ITEMS_IN_BASKET attribute to 17.
Note: There is a different rule being applied to this transaction as the value of the number of
items in the basket has changed to 17.
You will see Mike Morney, Geoff Walker and Susan Price as the approvers
20. Select the Quit button to return back to the Test Type page.
21. Select the Quit button to return to the main menu page.

Chapter 5 - Page 9
Test Tab Viewing Approvals
Test Tab View Transactions

You can create a transaction within you calling application and query on the transaction
id number. You can then enter this transaction id number in the test tab in AME which
will automatically load in all the attributes details for the transaction. AME will then
apply the rules for the transaction and generate the list of approvers.
Note that this feature would normally be used by the system administrator who may want
to query specific transaction ids with the rules. The general day to day user would use
the create a test transaction feature to test the rules defined.
An example of this could be as follows:
1. A job change has been submitted in SSHR which is linked to approvals for authorising this
in the chain of authority.
2. This record change will enter a transaction id in the HR_API_TRANSACTIONS table.
3. Use PL/SQL and write a select statement to query this table and find out the item key and
then the transaction id of this record. The record will also store the following information
which will be loaded into AME:
TRANSACTION_REQUESTOR_PERSON_ID

Chapter 5 - Page 10
4.
5.
6.
7.
8.
WORKFLOW_ITEM_KEY
WORKFLOW_ITEM_TYPE
CURRENT_ASSIGNMENT_ID
CURRENT_EFFECTIVE_DATE
TOP_SUPERVISOR_PERSON_ID
WORKFLOW_PROCESS_NAME
In AME go to the test tab and select the view a real transactions approval process feature.
AME will prompt you to enter the transaction id
All the transactions details will now be loaded and displayed in AME.
Note that you cannot change any of these details and they have been fetched directly from
the calling applications API Transaction tables.
AME will then display the order in which the rules are going to apply to the transaction.
AME generates the list of approvers for that transaction.
SQL for extracting the Transaction i.d.

By Notification i.d.:select context from wf_notifications
where notification_id=&notificationId
By Item Key:Query 1 - To find 'item key' for tranasction requestor
Enter in your user_name for the owner role and run the below query:
select * from wf_items
where item_type='HRSSA'
and owner_role= 'put user name here'
order by begin_date desc
Query 2 - To find transaction id
Take the item key for the transaction you just ran and insert it into query 2 below:
select transaction_id from hr_api_transaction_steps
where item_type='HRSSA'
and item_key=put item_key here
By 'Transaction requestor' last_ name:
select hat.transaction_id,
hats.processing_order,
hats.transaction_step_id,
hats.api_name
from hr_api_transactions hat,
hr_api_transaction_steps hats
where hats.transaction_id = hat.transaction_id
and hat.selected_person_id = (select person_id

Chapter 5 - Page 11
from per_people_x
where last_name = 'PJS US New Employee 2')
/*and hat.transaction_id in (
select transaction_id
from hr_api_transaction_steps
where api_name = 'HR_PAY_RATE_SS.PROCESS_API'
)*/
and hat.creation_date between sysdate-1 and sysdate+1
order by hat.transaction_id desc

Chapter 5 - Page 12
Building List Creation Rules 2

Chapter 6

Chapter 6 - Page 1
Building List Creation Rules Part 2

Chapter 6 - Page 2
Objective

Chapter 6 - Page 3
Approval Policy
Approval Policy
At the end of this topic the demonstration will show you how to define the list creation rule
mentioned above which is similar to the previous rule however it has the following
difference:
The number of items attribute is now a currency value attribute
The approval type is a relative job level rather than supervisory level as we want the
chain to start relative to the transaction requestor.
- For example is Sarah is the transaction requestor and she submits a transaction for
300 EUROS the approvers should be Geoff Walker and Susan Price. Mike Morney
is not selected as he is Sarahs immediate supervisor.
The rule is still a list creation rule, which is going to use an approval type of chains of authority
which are based on relative job levels. The Euro value of the basket will determine if the
approval is going to be done by Geoff and Susan.

Chapter 6 - Page 4
Steps For Defining List Creation Currency Rule
Steps For Defining List Creation Currency Rule

1. Attributes - In the above example being discussed the attribute is the currency value of
the basket..
2. Conditions In the above example there is going to be one condition for the EURO value.
The values that you enter in the upper and lower limits will be Euros.
3. Rules this step really combines the attribute and condition that you define and associates
these to a list creation rule which is tested at run time by creating test transactions. Rules
are unique to each transaction type, however AME does allow rules to be shared across
different transaction types. You can also modify the behaviour of conditions when defining
rules, thus reducing maintenance.
4. Testing this is a very useful step as it allows you to create test transactions by entering the
values to test, rather than having to fetch values from actual SQL tables only to find that a
rule is missing a particular test criteria.

Chapter 6 - Page 5
Using Currency Attributes
Using Currency Attributes

AME has a defined attribute type called currency which is used with transactions where you
want to convert the entered currency amount into the currency amount specified in the attribute
type. For example if the TRANSACTION_AMOUNT is US dollars (USD) and when AME is
run the value it fetches is Euros (EUR) then AME will convert the Euros to the equalivant US
dollar value by applying the conversion from Euros to USD according to the date specified in
the Effective Rule Date attribute. This conversion rate is held in the GL Daily Rates table.
Note : To use this functionality it is assumed that you have setup Currencies, Rate Types and
have valid exchange rates.
If you decide to use static usage with the currency type attribute the format for setting up the
usage is amount,code,type where :
Amount this is the currency amount you want to set when using this attribute in a rule.
Note that the amount should use a period to denote a decimal point. So for example
99.99.
Code is the currency code defined in the GL Define Currency table. Usually these are
ISO codes for currencies.

Chapter 6 - Page 6
Type relates to the Rate Type field on the GL Daily Rates table. This type field is the
currency conversion type and can have values such as Corporate, User or Spot which
denote where the currency exchange rate information has come from.
If you decide to use dynamic usage then queries for the currency data type must select three
columns; amount, code and type. The amount selected must be converted to a varchar2 by:
fnd_number.number_to_canonical (amount)

Chapter 6 - Page 7
Using Currency Conditions

Chapter 6 - Page 8
Relative Job Level Approval Type
Relative Job Level Approval Type

This job level works similar to the absolute job level however the difference is that the ascent
up the chain of authority is relative to the start point.
For example if a hierarchy consists of 4 job levels (J1, J2, J3 and J4 ) and the approval says
require approvals at most 2 levels up and the start point is at level J1. The approval will select
the approver at J4.
The required attribute INCLUDE_ALL_JOB_LEVEL_APPROVERS, if set to yes will include
all approvers with the same job level if the level is included in the list. Otherwise only the first
approver within the job level will be included.
The JOB_LEVEL_NON_DEFAULT_STARTING_POINT_PERSON_ID attribute determines
an alternative requestor for the approval. This requestor is a different person to the one who
submits the transaction initially.

Chapter 6 - Page 9
Default and Non Default Starting Points

Chapter 6 - Page 10
Setup Required for Defining List Creation Rule with Currency
Setup Required for Defining List Creation Rule with currency

rule types you may want to use. For example think about which rule type will generate a
chain of authority using the relative job level as you want the chain to start relative to the
transaction requestor.
Next consider the currency condition you would need to create and then determine the
attribute that will be most suitable to use.
To set up the example of currency value and relative job level approval for the basket you will
need to follow the steps below:
1. Create an attribute for this transaction type called for example
TOTAL_VALUE_OF_BASKET. Ensure that you set up the usage with the 3
components of the currency attribute: value, code and rate type.
2. Create conditions by using the attribute defined in step 1. Enter the currency code
specified in the attribute as code and use the value ranges for approval amounts.

Chapter 6 - Page 11
3. Create your rule selecting the attribute and condition defined earlier. The rule will have
an approval type of chains of authority based on relative job levels. and the approval
will determine how high to go in the approval list. Finally you select the condition with
the value range when defining rules.
3. Test the rule by creating a test transaction and viewing the list of approvers generated by
AME.

Chapter 6 - Page 12
Practice - Building List Creation Rules - 2

Overview
In this practice you will learn how to define rules based on currency and understand the use of
the relative job level approval type.
You need to define a rule, which says that any clothing basket with a value over EUR 100
requires approval from the next 2 supervisors relative to the person submitting the transaction.
So for example if Sarah Bellem submits this Euro transaction then Mike Morney and Geoff
Walker should be the approvers and if Mike Morney submits the transaction then the approvers
should be Geoff Walker and Sarah Price.
Assumptions
Tasks
Defining Attributes
You will need to define one non-mandatory header currency attribute for the rule mentioned
above. This attribute will then be associated with the condition and rule that will be defined later.
Note: this rule is going to use the relative job level approval type, which has 2 required
attributes. When you are defining attributes check that the following required attributes do
appear on the attributes page:
INCLUDE_ALL_JOB_LEVEL_APPROVERS
JOB_LEVEL_NON_DEFAULT_STARTING_POINT_PERSON_ID
Defining Conditions
You will need to define 1 ordinary header conditions for the EURO value of the basket to say
that the condition applies for all transactions over EUR 100.

Chapter 6 - Page 13
Defining Rules
You will define 1 list creation rules, which will use the attributes, conditions and approval types
defined.
Testing
You will test the rule created above by creating a test transaction. The first test will be to use
Sarah Bellem as the person submitting the transaction for 300 Euros. Then change the value to
30 Euros and still have Sarah Bellem as the transaction requestor. Finally enter Mike Morneys
name as the person submitting the transaction for 300 Euros.

Chapter 6 - Page 14

Defining Attributes
1.
2.
3.
4.
5.
6.
Enter XX_VGB_TOTAL_VALUE_OF_BASKET in the name field and select the continue

button. (Replace XX with your initials or your terminal number.)
7.
Select an Attribute type of currency.
8.
Enter XX total value of items in basket in the description field. (Replace XX with your name
9.
Select static yes.
10. Enter 9999,EUR, Corporate in the Usage area.

Defining Conditions
1.
continue button.
2.

Chapter 6 - Page 15
3.
4.
5.
In the attribute field select XX_VGB_TOTAL_VALUE_OF_BASKET from the list of

values.
6.
Select the continue button

Note that the page displayed is asking for currency information.
7.
Select EUR (Euro) from the list of values
8.
Enter 100 in the lower limit field. (This is 100 Euros)
9.
Leave upper limit field blank.
10. Select yes for include lower limit.

Defining Rules
continue button.
16. Enter XX_VGB_TOTAL_OVER_EUR100 in the description field.
21. Select the approval type of chains of authority based on relative job level.

Chapter 6 - Page 16
23. In the approval field select Require approvals at most 2 levels up.
25. Select XX_VGB_TOTAL_VALUE_OF_BASKET in the Ordinary Conditions Header
Attributes field.
28. Check the ordinary condition 100 EUR <= XX_VGB_TOTAL_VALUE_OF_BASKET
from the list available.
Testing
32. Select the test tab.

continue button.
34. In the Choose Test Type page select Create a test transaction.
36. Choose a requestor type of person.
37. Enter Bellem in the Last Name field and select the search button.
39. In the Mandatory Attributes section turn off the following attributes by changing the value
to no. For example:

Chapter 6 - Page 17
40. Scroll down the page to display the non-mandatory attributes available with the VGB
41. Enter no against any non-mandatory attributes that you do not want to be checked with this
rule for example:
VGB_IS_GIFT_WRAPPED
VGB_IS_NEW_BASKET
48. Enter a value of 300 in the attribute field called
XX_VGB_TOTAL_VALUE_OF_BASKET Amount:
49. Select EUR from the list of values available in the
XX_VGB_TOTAL_VALUE_OF_BASKET Currency field
50. Select Corporate from the list of values available in the
RK_VGB_TOTAL_VALUE_OF_BASKET Conversion Type field
51. Select the View Approval Process button to see the rule(s) AME will execute for this test
transaction.
Note: The only rule being applied for this test transaction is a list creation rule called
XX_VGB_TOTAL_VALUE_OVER_EUR100, which we had defined earlier.
Note: In the list of approvers you will see Mike Morney and Geoff Walkers name.
54. Change the value for the XX_VGB_TOTAL_VALUE_OF_BASKET attribute to 30.
Note: AME displays that there are no rules that apply to this Euro value. .
55. Scroll down the page and select the Change an ID Attribute Value button.
56. Select TRANSACTION_REQUESTOR_PERSON_ID.
57. Select Query for TRANSACTION_REQUESTOR_PERSON_ID.
58. Enter morney in the last name field
59. Select continue. AME will replace Sarahs name with Mikes name as the transaction
requestor person ID
60. Enter a value of 300 in the XX_VGB_TOTAL_VALUE_OF_BASKET amount attribute.

Chapter 6 - Page 18
Note AME will retain the other attribute values selected previously such as the currency
code and the conversion type.
61. Select the View Approval Process button
Note: In the list of approvers you will now see Geoff Walker and Sarah Prices name.

Chapter 6 - Page 19

Chapter 6 - Page 20
List Modification and

Substitution Rules
Chapter 7
List Modification and Substitution Rules

Chapter 7 - Page 1

Chapter 7 - Page 2
Objective

Chapter 7 - Page 3
Approval Policy Rule Components
Approval Policy
At the end of this topic the demonstration will show you how to define the substitution rule
mentioned above.
The rule will substitute Fred Masons name with John Doe. When defining the condition you
enter the name of the person you want to substitute; in our example this is going to be Fred
Mason. In this planning department Guy Wire reports to Fred Mason and Fred reports to Bob
Taylor and Bob reports to Mr. C. Jones. Thus if the transaction is submitted by Guy Wire it
would normally go to Fred for approval, however since we are going to substitute Fred with
John Doe it will go to John Doe an then onto Bob and C. Jones.
Note that we do not need to define any new attributes as we can use the number of items in
basket attribute defined earlier.

Chapter 7 - Page 4
Steps For Defining Substitution Rule
Steps For Defining Substitution Rule

1. Conditions In the above example there are is going to be one list modification condition
to be defined. The condition will simply nominate the name of the person who is going to
be the substitute. In our example this is John Doe
2. Define Approval in this step you will define the person that is going to substitute Fred
Mason. For our example this is John Doe.
3. Rules when defining the substitution rule you select the substitution condition defined in
the previous step.
4. Testing the test transaction will be created with Guy Wire as the person submitting the
transaction and the approvers should be John Doe, Bob Taylor and C.Jones.
Note that in the demonstration for this practice we will view person details record to
verify that Guy Wires supervisor is Fred Mason according to the HR record.

Chapter 7 - Page 5
List Modification Conditions
List Modification Conditions

When using List Modification conditions approvers can be selected by person or user details.
User detail is the application sign on name and the person is the employee name.
For example you could identify John Doe as the approver of any transaction over a certain
value by selecting Johns name when defining the condition. When this condition is selected in
a rule any transaction over the specified value will automatically default to John for approval
regardless of who has submitted the transaction.
You select the approver type when defining list modification conditions.
Select any approver if you want the condition to be true regardless of where the approver you
selected appears in the chain of authority.
Select final approver if you want the condition to be true only when the approver is last in the
chain of authority.

Chapter 7 - Page 6
List Modification Approval Types
List Modification Approval Types

Substitution approval type substitutes one approver for another. Note that this approval
type has no required attributes.
- For example substitute Fred Mason for John Doe in the chain of authority.
Non Final approval type extends the chain of authority beyond the approver listed in
the chain to a specified persons ID further up the job level chain.
- For example: Person A has a specified person_id of 123 and the non-finalauthority states that approval is required at job level 2. In this case, AME will
extend the chain past person A until it reaches another approver (person) with a job
level 2 in the chain
Final Authority approval type only has one approver regardless of the position in the
chain of authority.

Chapter 7 - Page 7
Substitution Approval Type
Substitution Approval Type

This approval type does not have any required attributes and when defining the approval it will
allow you to define one person for another when a rule when this approval is used.
For example if Sarah Bellem is on holiday we can set a rule, which substitutes Betty Price for
approvals which normally would have gone to Sarah Bellem.
This type of substitution is defined when setting up the approval and used when creating the
substitution rule.
Note: Substitution rules do not have any setup at the attribute stage or use any attribute types.

Chapter 7 - Page 8
Setup Required for Defining List Modification Rule
Setup Required for Defining List Modification Rule

approval type and condition you may want to use. For example think about the final
authority approver and any approver distinction when defining conditions.
Note that for this example we do not need to define attributes as we can use the attribute
defined for an earlier topic (NUMBER_OF_ITEMS_IN_BASKET)
To set up the example of list modification rule for the basket you will need to follow the steps
below:
1. Condition - Define a list modification condition selecting the name of the approver you
want to substitute, Fred Mason in this case and select the approver type of any approver
because you want the condition to be true regardless of where Fred Mason appears in the
chain of authority.
Check the header condition defined earlier for the number of items rule to be greater
than or equal to 11.

Chapter 7 - Page 9
2. Approval - Create the name of the person you want to substitute Fred Mason with, in this
case John Doe by using the pre-defined substitution approval and adding the approval
name.
3. Rule - Create your substitution rule and select substitute John Doe as the approver.
4. Test - Create your test transaction with Guy Wire as the transaction requestor.
Note that this demonstration will execute 2 rules the number of items in the basket and then
the substation rule.
Note : Prior to running through the above creation steps it is worth view Guy Wires HR
record to verify that he does report to Fred Mason so that when John Doe appears in the
approval list we know that this is because of the rule being actioned.

Chapter 7 - Page 10
Practice - List Modifications and Substitution Rules

Overview
In this practice you will learn how to define a substitution rule where by one approver will be
substituted for another approver.
You need to define a rule, which says that Fred Mason, a planning manager at VGB has been
assigned a new project therefore he will not have time to approve any transactions submitted by
Guy Wire who reports to him. If Guy Wire submits a transaction with 11 or more items in the
basket the approval should go to John Doe first rather than Fred Mason
Assumptions
Use the List creation rule defined earlier for the number of items in the basket with the
list modification condition that you will define in this practice.
Tasks
Viewing Person Details
View Guy Wires person details to ensure that Fred Mason is his supervisor.
Defining Conditions
You will need to define 1 list modification conditions selecting John Doe as the approver. This
condition is going to be used with the number of items in the basket condition defined in an
earlier practice.
Defining Approvals
You will need to select the approvals tab and select the substitution approval type and add the
name of the person you are going to substitute Fred Mason with. In this case John Doe.

Chapter 7 - Page 11
Defining Rules
You will define 1 substitution rules, which will use the list modification conditions defined in the
task above.
Testing
You will test the rule created above by creating a test transaction, which is going to be submitted
by Guy Wire.
The test will select two rules:
The list creation rule based on the number of items in the basket
Substitution rule which should select John Doe as the approver rather than Fred
Mason even though Guy Wires supervisor in Fred Mason.

Chapter 7 - Page 12
Solution List Modifications and Substitution Rules

Viewing Person Details
Responsibility = HR Manager
Navigate to the List People By Assignment window.
(N) View > Lists > People by Assignments
1. In the Job field select the list of values.

2. Enter VGB% in the Find field. This will retrieve all jobs, which start with VGB.
3. Select VGB.LEVEL_1 because this is Guy Wires job level.
4. Check the Employees box in the Person Type.
5. Select the find button. This will retrieve 2 employees records: - Ms. Sarah Bellem and Mr.
Guy Wire.
6. Select Guy Wires record and scroll to the right to see the additional fields.
Note that Guys supervisor is Fred Mason.
7. Close the window and exit the PUI Application.
Defining Conditions
Responsibility = AME General Business User
1.
continue button.
2.
3.
Select a list modification condition type.
4.
5.
In the Search for an Approver page enter mason in the last name field.
6.
Select an approver type of person.

Chapter 7 - Page 13
7.
Select the search button.

AME will display Fred Masons employee record in the Matching Approvers page..
8.
9.
In the Choose Approver Type page select an approver type of any approver.
10. Select the create Condition button to save the list modification condition.
Defining Approval
Navigate to the Approvals window.
(N) Approvals > (T) Approval
Note that you do not need to select the transaction type, as approvals are common to all
transaction types.
11. Select the substitution approval type from the list displayed.
12. Select the Add Approval button.
13. Enter doe in the last name field to search for John Does record.
14. Select the continue button and AME will add the name as the substitute.
Defining Rules
continue button.
16. Scroll to the end of the attributes page and select the Add A Rule button to define a
substitution rule.
17. Enter XX VGB_SUBSTITUTION_RULE in the description field.
18. Select substitution in the rule type field.
22. Select the approval type of substitute one approver for another.

Chapter 7 - Page 14

24. In the approval field select Substitute John Doe for the approver.
26. Do not select anything in the Ordinary Conditions Header Attributes field.
28. Select the continue button to display Add A Rule Step 5 page..
30. In the next step of defining the rule select the substitution condition Any approver is Fred
Mason from the list available.
Testing

continue button.
38. Enter wire in the Last Name field and select the search button.
one employee record with this name, Guy Wire.
40. In the Mandatory Attributes section turn off the following attributes by changing the value to
no:

Chapter 7 - Page 15
Note: AME will insert Guy Wires name as the
42. Enter no against any attributes that you do not want to be checked with this rule for example:
VGB_IS_GIFT_WRAPPED
VGB_IS_NEW_BASKET
48. Enter a value of 45 in the attribute called
VGB_TOTAL_NUMBER_OF_ITEMS_IN_BASKET
Note: AME will apply 2 rules to this transaction:
RK_VGB_HAS_MORE_THAN_11_ITEMS
And
RK_VGB_SUBSTITUTE_JOHN_DOE_FOR_FRED_MASON
Note: In the list of approvers you will see John Doe, Bob Taylor and C. Jones.

Chapter 7 - Page 16
Defining and Using Approval

Groups
Chapter 8
Defining and Using Approval Groups

Chapter 8 - Page 1

Chapter 8 - Page 2
Objective

Chapter 8 - Page 3
Approval Policy - Rule Components
Approval Policy
At the end of this topic the demonstration will show you how to define a pre - list approval
group rule mentioned above.
The rule will check to see if the transaction is a new basket and if gift wrapping is required. If
both of these conditions are true then AME will generate the names of the people who work in
the gift wrapping department as approvers before the remaining approvers in the chain.
Note that we do need to define two new boolean attributes for the rule above.

Chapter 8 - Page 4
Steps for Defining Pre Approval Group Rule
Steps for Defining Pre Approval Group Rule

1. Attributes The 2 new attributes for this example, will be true / false attributes. One for the
New Basket and the other for Gift Wrapping Required.
Note while creating attributes you can also verify that the required attributes of:
ALLOW_EMPTY_APPROVAL_GROUPS for the pre-chain-of-authority approval has
been defined for the clothing basket transaction type.
2. Conditions There will be 2 new conditions defined using the attributes created. These
conditions will be ordinary header conditions with the value set to true so that the rule
will be executed if both conditions are met i.e. the basket is a new transaction and gift
wrapping is required.
3. Groups Since both members working in the gift wrapping department need to approve
this transaction we will define an approval group with the names of Warren Peace and
Sandy Beach.
4. Rules We will define a pre approval group rule as we want both Warren and Sandy to
approve the transaction before the remaining approvers in the chain.
5. Testing the test transaction will be created with Mike Morney as the person submitting
the transaction and the approvers should be Warren Peace and Sandy Beach.

Chapter 8 - Page 5
Boolean Attributes and Conditions

Chapter 8 - Page 6
Approval Groups
Approval Groups
By using approval groups, you can combine a list of names of approvers who have no
reporting relationships.
These lists can be:
- Static, that is, you select the names of the approvers (employees) or the usernames
and enter these into the group
or
- Dynamic, where a PL/SQL statement can be entered to select all employees in a
particular department, such as HR or a group of employees from the employee table
based on a particular column id.
For example, in the select statement below, the group will consist of all
employees whose payroll number begins with 10:
select 'person_id:'||person_id
from per_people_x
where employee_number like '10%

Chapter 8 - Page 7
You can also nest approval groups within existing groups. For example in the diagram
above, static list 2 could nest within static list 1 and therefore you would only have one
approval group but with two lists of employee names.

Chapter 8 - Page 8
Using Dynamic Approval Groups
Using Dynamic Approval Groups

There are two new fields on the create-approval-group and edit-approval-group page on the
groups tab. One is a radio button labelled Active List; the other is a text area labelled Query.
The active-list radio button has two possible values: static and dynamic. When the radio button
is set to static, AME uses the member list at the bottom of the (create or edit) page to determine
the approval group's membership. When the radio button is set to dynamic, AME executes the
query and uses the rows returned by the query to determine the approval group's membership.
- For example in the above SQL statement AME will retrieve all employee names
whose employee number begins with 10.
If the query is null, the group has no members when the radio button selects the value dynamic.
(This lets you "switch off" a group without deleting its static members.) Otherwise, the query
must select rows from approver_type:id, where approver_type is one of the strings 'person_id'
and 'user_id', and id is a valid ID of the type specified by approver_type. For example,
person_id:502 and user_id:205 are syntactically correct values.
The query should select approvers in the order that you want them to appear in a transaction's
approver list.

Chapter 8 - Page 9
You can toggle the Active List button's values without deleting either the static list or the query
string.
ALLOW_EMPTY_APPROVAL_GROUPS allows you to define an approval group with no
members. This will use AME to generate a list of approvers but no approval action will be
required by the approvers.

Chapter 8 - Page 10
How Nested Approval Groups Work
How Nested Approval Groups Work

AME now lets you make one approval group a member of another approval group. For
example, a purchasing department might define groups to handle post-approvals of computerhardware purchases
Use the Add Nested Group button on the groups tab to nest approval groups.
It is possible to nest a dynamic group in a static group, but it is not possible to nest either a
dynamic or static group in a dynamic group.
Dynamic groups can only include persons and users.
Nested approval groups let you build an approvals matrix using AME approval groups. For
example, the purchasing department defining the computer-hardware approval groups above
might define three corresponding post-approval rules:
Rule 1
If
ITEM_CATEGORY in {COMPUTER_HARDWARE}
and

Chapter 8 - Page 11
ITEM_AMOUNT <= 1,000 USD

then
require post-approval from the COMPUTER_HARDWARE_POST_APPROVERS_1 group.
Rule 2
If
and
1,000 USD < ITEM_AMOUNT <= 10,000 USD
then
Rule 3
If
and
10,000 USD < ITEM_AMOUNT
then
These rules effectively define a hierarchy of per-item dollar-amount signing authorities for
three subject-matter approvers. You can seed a hierarchy of nested approval groups containing
no members other than nested groups, along with a set of approval rules like those above and
you can easily populate the groups with person or user approvers upon installation.

Chapter 8 - Page 12
Approval Types Approval Group Rules
Approval Types: Approval Group Rules

Pre Approvers
This adds an approval group to a transactions approval list before all approvers in the
transaction chains of authority. The members will appear in the order they are defined in
the approval group.
Post Approvers
This adds an approval group to a transactions approval list after all approvers in the
transaction chains of authority. As with the pre approvers, the members appear in the
order sequence determined in the approval group.
Dynamic Approver
- With this approval type, you can insert a single or a list of pre approver(s), who are
not already in an approval group, anywhere in the list of approvers.
- Approvers of this type can be pre or post approvers and the insertion of the
approver is done at run time.

Chapter 8 - Page 13
Setup Required for Defining and Using Approval Groups
Setup Required for Defining and Using Approval Groups

rule types you may want to use. For example think about which rule type will generate
per approvals with approval groups and post approvals.
Next consider the conditions you would need to create and then determine the attribute
that will be most suitable to use.
To set up the example of pre approval for the basket you will need to follow the steps below:
1. Create two boolean attributes for this policy called for example BASKET IS NEW and
BASKET_IS_GIFT_WRAPPED. Ensure that you set up the usage with the true / false
usage.
2. Create two ordinary header conditions, which will be actioned when the condition is met.
For example if the basket is a new transaction and gift-wrapping is required then the rule
will be executed.
3. Define the approval group to specify the approvers required when this condition is true.

Chapter 8 - Page 14
4. Create your rule and choose per list approval group. Next decide if this group is going to
be checked before the chain of authority or when the pre - approver is selected at runtime.
Select the approval and choose the header and or line attributes this applies to and test the
rule.
5. Test the rule with Mike Morney as the person submitting the transaction and test the rule
when both conditions and met and also see what happens when one of the conditions is
not met.

Chapter 8 - Page 15
Practice - Defining and Using Approval Groups

Overview
In this practice you will add a rule to the clothing basket transaction type, which says that any
new clothing basket transaction, requiring to be gift wrapped will have to be approved by the
gift Wrapping service department. This department consists of Mr. Warren Peace and Ms.
Sandy Beach. Warren must do the Approval first followed by Sandy.
Assumptions
resemblance to any particular organization or individuals.
Use the General Business User responsibility for all practices unless stated otherwise.
Tasks
Defining Attributes
You will need to define two Boolean non-mandatory header attributes. One for the New Basket
attribute and the other for the gift-wrapping service attribute. These attributes will be associated
with the 2 conditions defined in the next task.
Note: this rule is going to use the group approvals before chain of authority approval type,
which has 1 required attribute. When you are defining attributes check that the following
required attributes does appear on the attributes page for the transaction type of VGB
Clothing Basket:
ALLOW_EMPTY_APPROVAL_GROUPS
Defining Conditions
You will need to define 2 ordinary header conditions for the Boolean attributes defined earlier
using the true false values as appropriate.
Defining Approval Groups
You will need to define an approval group for the gift-wrapping department. This group will
consist of 2 people: - Mr. Warren Peace and Ms. Sandy Beach.

Chapter 8 - Page 16
Defining Rules
You will define a pre-list group approval rule, which will use the attributes, conditions and
approval group defined in the previous tasks.
Testing Rule
You will test the rule by creating a test transaction. The requestor is Mike Morney and when
submitting the rule the attributes not required will be turned off. The gift-wrapping and new
basket attributes will be set to yes.

Chapter 8 - Page 17
Solution Defining and Using Approval Groups

Defining Attributes
1.
2.
3.
4.
5.
6.
Enter XX_VGB_IS_GIFT_WRAPPED in the name field and select the continue button.
(Replace XX with your initials or your terminal number.)
7.
Select an Attribute type of boolean.
8.
Enter XX is gift wrapping required in the description field. (Replace XX with your name
9.
Select static yes.
10. Enter false in the Usage area.

12. Repeat steps 3 11 above to create the second attribute.
For the second boolean attribute enter XX_VGB_IS_A_NEW_BASKET as the attribute
name and enter a description of XX is a new basket with true in the usage field.
Defining Conditions
14. Navigate to the Conditions window.

Chapter 8 - Page 18
continue button.
16. Scroll to the end of the conditions page and select Add a Condition button.
17. Select an ordinary header condition type.
19. In the attribute field select XX_VGB_IS_GIFT_WRAPPED from the list of values.
20. Select the continue button to select the value true.
23. Repeat steps 2 to 8 for the second condition XX_VGB_IS_A_NEW_BASKET with a
usage of true.

24. Navigate to the Groups window.
(N) Approvals > (T) Groups
Note that Approval groups are common to all transaction types therefore you will not be
asked to select a transaction type.
25. Scroll to the end of the page and select the Add Group button.
26. Enter XX_VGB_GIFT_WRAPPING_GROUP as the name of your approval group.
27. Enter VGB group for gift wrapping service in the description field.
28. Select static in the Active List field as we are going to define the names of the approvers
rather than selecting names via a query.
29. Select the Create Group button. AME will confirm the group being successfully added,
however you have to now define the members of this group.
30. Select the Add Approver button found at the bottom of the page.
31. Enter peace in the last name field to search for Mr. Warren Peaces record from HR.
32. Select approver type of person.
33. Select the search button.

Chapter 8 - Page 19
34. Select the continue button after AME finds Warren Peaces record and displays the full
name and employee number.
35. Select the Order number of 1 for this record i.e. Warren is the first person in this
approval group.
36. AME will add Warrens name in the members list.
37. Repeat steps 21- 27 to add Ms Sandy Beach into this approval group.
Defining Rules
38. Navigate to the Rules window.
continue button.
41. Enter XX_VGB_GIFT_WRAPPING_SERVICE in the description field. (Replace XX with
your initials or your terminal number.)
42. Select pre-list approval-group rule in the rule type field.
46. Select the approval type of group approvals before the chain of authority.
48. In the approval field select Require pre approvals from XX_VGB GIFT WRAPPING
GROUP.
50. Select XX_VGB_IS_A_NEW_BASKET and XX_VGB_IS_GIFT_WRAPPED in the
Ordinary Conditions Header Attributes field. (XX is replaced with your initials or your
terminal number.)

Chapter 8 - Page 20
53. Check the ordinary conditions XX_VGB_IS_A_NEW_BASKET is true and

XX_VGB_IS_GIFT_WRAPPED is true from the list available.
Testing the Approval Group Rule

57. Navigate to the Test window.

continue button.
63. Enter morney in the Last Name field and select the search button.
one employee record with this name, Mike Morney.
to no:
67. Enter yes against the following attributes:
XX_VGB_IS_GIFT_WRAPPED
XX_VGB_IS_NEW_BASKET

Chapter 8 - Page 21
Note: The only rule being applied for this test transaction is the pre approval rule called
XX_VGB_GIFT_WRAPPING_SERVICE, which we had defined earlier.
68. Select the note pad icon to display full details about this rule.
70. Note: In the list of approvers you will see Mr. Warren Peaces name first in the list followed
by Sandy Beachs name.
72. Change the value for the XX_VGB_IS_A_NEW_BASKET to no.
Note AME comes back with an error message saying that at least one rule must apply to
the transaction. The Gift Wrapping rule could not apply in this instance because the basket
was not new.

Chapter 8 - Page 22
Defining Exception Rules for

List Creation
Chapter 9
Defining Exception Rules for List Creation

Chapter 9 - Page 1

Chapter 9 - Page 2
Objectives
Objectives
In this topic we look at ordinary and exception rule combinations as an introduction to
handling multiple rules.
In a later topic within this eclass we will look at combinations of multiple types and multiple
rules with rule priorities.

Chapter 9 - Page 3
Understanding Exception Conditions and Rules

Chapter 9 - Page 4
Ordinary Conditions and Multiple Rules
Ordinary Conditions and Multiple Rules

The above example shows 2 rules defined with ordinary conditions. AME will execute both
rules to determine the list of approvers.

Chapter 9 - Page 5

The ordinary and exception rule above are both defined using the same attribute, AMOUNT
however in the exception rule the first condition is the ordinary condition and the exception is
the gift-wrapping.
The exception of Gift Wrapping will narrow the scope, if the transaction amount is above
EUR 200.
At runtime AME will execute the action for the exception rule to determine the list of
approvers.

Chapter 9 - Page 6
Approval Policy
At the end of this topic the demonstration will show you how to define an exception rule
mentioned above.
The rule will check to see if the value of the basket is more than 200 Euros and if gift-wrapping
is not required. If both of these conditions are met then AME will generate the name of the
immediate supervisor of the person submitting the transaction.
Note that we dont need to define attributes for the rule mentioned above as we can use the
attributes of Value Of Basket and Gift Wrapping which we defined for earlier.
Note:in this topic we are not considering the impact of rule priorities at this point. Rule
priorities will be discussed in a later topic.

Chapter 9 - Page 7
Steps for Defining Exception Rules
Steps for this rule are:

Attributes Generally you would need to define the value of basket and gift wrapping
attributes, however since these have already been defined for pervious demonstrations we will
not be defining these during the demonstration.
Conditions There will be 2 new conditions defined using the attributes created earlier. These
conditions will be an ordinary header conditions for the value of the basket which will be set to
>= 200 Euros and the second condition will be an exception condition on the Gift wrapping
attribute with the usage set to false.
Rules You will define a list creation exception rule, which will use the ordinary header
condition of the value of basket as well as the exception condition of no gift-wrapping service.
Testing the test transaction will be created with Geoff Walker as the person submitting the
transaction and the approver should be Susan Price.

Chapter 9 - Page 8
Setup Required For Dealing With Exception Rules
Setup Required for Dealing With Exception Rules

exception conditions you may want to use. For example think about which list creation
and list creation exception rule type will generate the approval of supervisor and the next
level up to the person submitting the transaction.
Next the attribute that will be most suitable to use.
To set up the exception rule approval for the basket you will need to follow the steps below:
Note: You do not need to define new attributes as we can use
XX_VGB_TOTAL_VALUE_OF_ITEMS_IN_BASKET attribute defined earlier.
1. Condition - Create 2 conditions: an ordinary header condition with the
XX_VGB_TOTAL_VALUE_OF_ITEMS_IN_BASKET and an exception header
condition by selecting the XX_VGB_IS_GIFT_WRAPPED attribute, however you will
set the value to false.

Chapter 9 - Page 9
2. Rule - Create your list creation exception rule with an approval type of chain of authority
based on number of supervisory levels and an approval of Require approvals up to the
first superior, at most.
3. Test - Test the rule using the test tab and create a test transaction with Geoff Walker as
the transaction requestor. The approval list should show Susan Price as the approver as
she is Geoffs immediate supervisor.

Chapter 9 - Page 10
Practice - Defining Exception Rules for List Creation

Overview
In this practice you will define a rule, which says that any clothing basket, which is over EUR
200 and is not gift-wrapped should be approved by the immediate supervisor of the person
submitting the transaction.
Assumptions
Tasks
Defining Conditions
You will need to define 2 conditions using the attributes we have defined already. The ordinary
condition for number of items in basket will be defined for the EUR value of 200 or over, while
the Boolean condition VGB is gift wrapped will be defined as an exception condition with the
value set to false.
Defining Rules
You will define an exception rule, which will use the conditions defined in the previous tasks.
Testing
You will test the rule by creating a test transaction. The requestor is Geoff Walker.

Chapter 9 - Page 11
Solution Defining Exception Rules for List Creation

Defining Conditions
1.
1.
continue button.
2.
3.
4.
5.
In the attribute field select XX_VGB_TOTAL_VALUE_OF_ITEMS_IN_BASKET from

the list of values.
6.

Note that the page displayed is asking for currency information.
7.
Select EUR (Euro) from the list of values
8.
Enter 200 in the lower limit field. (This is 200 Euros)
9.
Leave upper limit field blank.
10. Select yes for include lower limit.

15. Select an exception condition type.
17. In the attribute field select XX_VGB_IS_GIFT_WRAPPED from the list of values.

Chapter 9 - Page 12
19. Enter false as the value of this condition.

Defining Rules
continue button.
23. Scroll to the end of the attributes page and select the Add A Rule and Usage button..
24. Select RK_VGB_>=EUR200_NO_GIFT_WRAP in the description field. (Note the XX
will be replaced with your initials or your terminal number.)
25. Select list-creation exception in the rule type field.
29. Select the approval type of chain of authority based on number of supervisory levels.
31. In the approval field select Require approvals up to the first superior, at most.
33. Select XX_TOTAL_VALUE_OF_ITEMS_IN_BASKET in the Ordinary Conditions Header
Attributes field. (XX is replaced with your initials or your terminal number.)
36. Check the ordinary conditions 200 EUR <=
RK_TOTAL_VALUE_OF_ITEMS_IN_BASKET box.
38. In step 6 of defining a rule select the XX_VGB_IS_GIFT_WRAPPED as the exception
condition header attribute.

Chapter 9 - Page 13
39. In step 7 of defining the rule check the exception condition

XX_VGB_IS_GIFT_WRAPPED id false box.
40. Select the continue button and AME will save the rule.
Testing the Exception Rule


continue button.
47. Enter walker in the Last Name field and select the search button.
one employee record with this name, Geoff Walker.
to no:
Note: AME will insert Geoff Walkers name as the
51. Enter a value of 250 in the attribute called XX_VGB_TOTAL_VALUE_OF_BASKET
Amount:
52. Select a currency code of EUR (Euro) in the attribute called
XX_VGB_TOTAL_VALUE_OF_BASKET Currency

Chapter 9 - Page 14
53. Select a conversion type of corporate in the RK_VGB_TOTAL_VALUE_OF_BASKET

Conversion Type attribute.
54. Turn off the XX_VGB_IS_GIFT_WRAPPED and the XX_VGB_IS_A_NEW_BASKET
attributes by selecting a no value.
55. Select the View Approval Process button to see the rule that AME will execute.
Note: The only rule being applied for this test transaction is the exception rule called
RK_VGB_>=EUR200_NO_GIFT_WRAP, which we had defined earlier.
Note: In the list of approvers you will see Susan Prices name first as she is Geoffs
immediate supervisor.

Chapter 9 - Page 15

Chapter 9 - Page 16
Effective Dates for Rules and

Attributes
Chapter 10
Effective Dates for Rules and Attributes

Chapter 10 - Page 1
Effective Dates For Rules and Attributes

Chapter 10 - Page 2
Objectives

Chapter 10 - Page 3

The demonstration at the end of this topic, will show you how to define a condition to
check for transaction date. The rule is a post list approval group rule with John Doe as the
only member of the approval group.
The rule will check to see if the number of items in the basket is less than 5 and if the
transaction date is on or after 1st April 2004. If both of these conditions are met then
AME will display the name of the immediate supervisor of the person submitting the
transaction as John Doe.
- Note : You can prevent a rule from being applied by entering a future effective date.
Transaction date is always the system date.
Note that for the rule mentioned above we can reuse the attribute Number Of Items in
Basket Basket, and the condition number of items in basket which were defined
earlier.
In this example you are adding a named approver to the list. To do this, you need to
define an approval group with the named approver, John Doe, as the only member of the
group. When defining the rule you will select the approval type of chain of authority
includes an approval group and this approval group will be used as a post approval group.

Chapter 10 - Page 4
Effective Dates and Rules
Effective Dates And Rules

There are various places where dates are used / stored. For example :
Database this stores the system date (sysdate)
Transactions such as Purchase Orders have the transaction date and the delivery date
AME uses dates on rules (effective date) and conditions.
The demonstration in this topic shows how to define a rule with an effective rule date which is
in the future.

Chapter 10 - Page 5
Mandatory Date Attributes
Mandatory Date Attributes

For most transaction types sysdate is the appropriate EFFECTIVE_RULE_DATE value. To
use this value give EFFECTIVE_RULE_DATE a static null (empty) usage. This will be more
efficient at run time than giving it a dynamic usage that selects sysdate from dual.

Chapter 10 - Page 6
Transaction Date and AME

Chapter 10 - Page 7
Setting Conditions On Date Attributes
Setting Conditions On Date Attributes

Technical Information on Date Formats
The date format in AME is YYYY:MON:DD:HH24:MI:SS however if you enter a date as
2003:JAN:13:1400:00:00 AME will convert the JAN to 01 and store the date in canonical
format. AME does not currently support multiple user date formats as in NLS.
Queries for date attributes convert a date value into a varchar2 using the
ame_util.versionDateToString function. This function guarantees that the date will be stored in
the ame model as a varchar2.
AME can only correctly evaluate conditions defined on a date attribute when the attributes
dynamic usage converts the date using this format. AME will then convert the date back using
the same model.
An example of an SQL syntax for a date attribute would be:
Select ame_util.versionDateToString (sysdate)
from dual

Chapter 10 - Page 8
Steps For Defining Rule With Effective Date
Steps For Defining Rule With Effective Date

1. Groups: Define a new approval group with John Doe as the only member.
2. Rules: We will define a list creation rule with a start date (in the future). This rule will use
a post approval group with an approval type of chain of authority includes an approval
group and an ordinary header condition of the number of items in basket.
3. Testing: the test transaction will be created with Sarah Bellem as the person submitting the
transaction and we will change the transaction date to be after 1st April 2004 and enter a
value less than 5 in the number of items in basket attribute. The approvers should be Mike
Morney and John Doe.

Chapter 10 - Page 9
Setup Required For Defining Rules With Future Effective Dates
Setup Required for Defining Rules With Future Effective Dates

transaction dates and dates as to when the rule will be effective.
Next review existing rules to see how adding dates changes the rule.
To set up the future dated list creation rule for the basket you will need to follow the steps
below:
1. Group - Define an approval group called
XX_VGB_FUTURE_DATED_RULE_JOHN_DOE with John Doe as the only
member.
2. Rule - Create your future dated list creation rule specifying the conditions and selecting
the approval group defined in the first step.
3. Test - Test the rule using the test tab. Create a test transaction with Sarah Bellem as the
person submitting the transaction and change the transaction date to be after 1st April
2004. Enter a value less than 5 in the number of items in basket attribute.
The approvers should be Mike Morney and John Doe.

Chapter 10 - Page 10
Practice - Effective Dates for Rules and Attributes

Overview
In this practice you will add a rule which says that that from 1st April 2004, Visions fiscal start
of year, the organsation will require all baskets with 5 or less items to be approved by the
immediate supervisor as well as John Doe.
For this rule you will be using an approval group which will consist of John Doe only and an
approval type of chain of authority, which includes an approval group. You do not need to define
any new conditions or attributes, as you will be using the attributes and condition defined in
topic 2.
Assumptions
Tasks
You will need to define an approval group with John Doe as the only member.
Defining Rules
You will define a list creation rule, which will use the attributes and condition defined for topic 2
(number of items in basket less than 5).
Testing
You will test the rule by creating a test transaction. The requestor is Sarah Bellem and when
submitting the rule the attributes not required will be turned off.

Solution Defining and Using Approval Groups

Defining Attributes

1.
Navigate to the Groups window.
(N) Approvals > (T) Groups
Note that Approval groups are common to all transaction types therefore you will not be
asked to select a transaction type.
2.
Scroll to the end of the page and select the Add Group button.
3.
Enter XX_VGB_APPROVAL_GROUP_JOHN_DOE as the name of you r approval

group. (Replace XX with your initials or your terminal number).
4.
Enter VGB Approval Group for Future Date Rule in the description field.
5.
Select static in the Active List field as we are going to define the names of the approvers
rather than selecting names via a query.
6.
Select the Create Group button. AME will confirm the group being successfully added,
however you have to now define the members of this group.
7.
Select the Add Approver button found at the bottom of the page.
8.
Enter doe in the last name field to search for Mr. John Does record from HR.
9.
Select approver type of person.
10. Select the search button.

11. Select the continue button after AME finds John Does record and displays the full name
and employee number.
12. Select the Order number of 1 for this record i.e. John is the only person in this approval
group.
13. AME will add Johns name in the members list.
Defining Rules

continue button.
17. Enter XX_VGB_FUTURE_DATED_RULE_JOHN_DOE in the description field. (Replace
XX with your initials or your terminal number.)
18. Select list creation rule in the rule type field.
19. Enter 04-01-2004 as the start date. (This will be 1st April 2004)
22. Select the approval type of chain of authority includes an approval group.
24. In the approval field select Require approval from
XX_VGB_APPROVAL_GROUP_JOHN_DOE.
26. Select XX_VGB_NO_OF_ITEMS_IN_BASKET. (XX is replaced with your initials or your
terminal number.)
29. Check the ordinary conditions 0 <= XX_VGB_NO_OF_ITEMS_IN_BASKET <= 5 from
the list available.
31. AME will confirm the rule being added successfully.
Testing



continue button.
39. Enter bellem in the Last Name field and select the search button.
41. Enter selected date in the effective rule date and transaction date and select a date of 1st
April 2004 (since we want to test a future dated rule.)
to no:
44. Enter 3 as the value in the attribute XX_VGB_NO_OF_ITEMS_IN_BASKET.
45. Enter no against the following non-mandatory attributes:
XX_VGB_IS_GIFT_WRAPPED
XX_VGB_IS_NEW_BASKET
Note: There are two rules being applied for this transaction:
RK_VGB_0_TO_5_ITEMS_IN_BASKET
RK_VGB_FUTURE_DATED_RULE_JOHN_DOE
Note: In the list of approvers you will see Mr. Mike Morneys name first in the list followed
by John Does name.

48. Change the effective and selected dates to none.

Note this time AME will only apply one rule XX_VGB_0_TO_5_ITEMS_IN_BASKET.
50. Select the view approval list button.
Note: In the list of approvers you will see Mr. Mike Morneys name only as he is Sarahs
immediate supervisor.


Line Level Attributes and

String Attribute Types
Chapter 11
Line Level Attributes and String Attribute Types

Chapter 11 - Page 1

Chapter 11 - Page 2
Objectives

Chapter 11 - Page 3
Approval Policy
At the end of this topic the demonstration will show you how to define the list creation rule
mentioned above. This rule will be using line item attributes which are string attributes.
2 new attributes will need to be defined
2 ordinary line level conditions for the Item Type of Golfing Items and Item Name of
Golf Clubs will need to be defined
When creating the rule the approval type of one job level chain of authority per line item
will be selected.

Chapter 11 - Page 4
Steps For Defining Line Item Rules
Steps For Defining Line Item Rules

1. Attributes define 2 new string attributes for Item Type and Item Name.
2. Conditions define 2 new ordinary line item conditions using the attribute defined in the
previous step.
3. Rules define a list creation rule, which will use an approval type of one job level chain
of authority per line item and an approval of Require approvals up to at least level 2.
The rule will use ordinary line item conditions and the attributes of item type and item
name will be selected here.
4. Testing The test transaction will be created with Sarah Bellem as the transaction
requestor and in the item type and item name will be added using the edit line items button
and a line item created with Golfing Items and Golf Clubs. Since we are going to use a job
level chain the starting point person in this chain will have to be selected too. This is going
to be Sarah Bellem. The approval list should show Mike Morney and Geoff Walker.

Chapter 11 - Page 5
Attribute Levels

Chapter 11 - Page 6
String Attributes Types
String Attributes Types

Header Level attribute queries usually contain the transaction ID placeholder.
Queries for line item attribute contain the line item ID placeholder which is used by AME to
determine the sequence in which AME will read the lines within a transaction.
The where and the order by clauses order the attribute values in ascending order of the
associated line-item IDs.
The example query below shows a header and line item currency attribute:
select
fnd_number.number_to_canonical (amount),
currency_code,
currency_conversion_type
from
some_app_line_items
where
header_id = :transactionID

Chapter 11 - Page 7
and
line_item_id =:lineItemIdList
order by
line_item_id

Chapter 11 - Page 8
How AME uses Attributes

Chapter 11 - Page 9
Understanding Multiple Conditions

AME allows you to attach any number of conditions to a rule with various attribute types such
as string, boolean, number etc.
AME will check all conditions at run time and if all conditional criteria are met AME will
execute the rule.
Note: Exception conditions also contain multiple conditions. An exception contains at
least one ordinary condition and at least one exception condition. An exception can use
any available approval types for list creation rules.
For more details on exception conditions please refer to topic 8 covered earlier.


The above example illustrates a situation where you may have several conditions that could
apply to a transaction.
For example you define a list creation rule, which has the following:
Rule Type: list-creation rule
Conditions:
1. ITEM_TYPE allowed values: Golfing Items
2. ITEM_NAME allowed values: Golf Clubs
3. VGB_NO_OF_ITEMS_IN_BASKET < 20
4. TOTAL_VALUE_OF_BASKET > 500 EUROS
AME will check all 4 conditions listed above and if:
Item type - golfing items
and
Item name = golf clubs
and

There are less than 20 items in the basket

and
Value of the basket is > 500 EUROS
the list creation rule will be evaluated and the approvers listed.

Defining Line Items with Restrictive Evaluations

USE_RESTRICTIVE_LINE_ITEM_EVALUATION is a mandatory attribute. This attribute is
visible if the transaction type has been defined with a select statement in the Line-Item Id
Query field.
When you enter a query in this field it selects in ascending order the IDs of the line items
belonging to a transaction of this transaction type.
A typical type of query in this field would be:
select line_item_id
from app_line_items
where transaction_id = :transactionId
order by line_item_id
If you leave this area blank AME will not select any line item for this particular transaction
type and hence you will not see the attribute allowing you to place restrictions on line items.


In the above example we want to ensure that all line items in the PO must be > $100 before the
rule can be executed.
To do this follow these steps:
1. Ensure that the transaction type has been created with a select statement in the Line-Item Id
Query field.
2. Modify the usage value for the USE_RESTRICTIVE_LINE_ITEM_EVALUATION
attribute according to how you want to set the restriction i.e. for all line items or a single
line item.
3. Define a non-mandatory line item attribute for your item.
4. Define your line item condition using the attribute defined in the previous step with the
value required.
5. Define your rule using the attribute and condition setup in step 3 & 4
6. When you test the rule using the create test transaction option, change the Yes / No
mandatory attribute USE_RESTRICTIVE_LINE_ITEM_EVALUATION option as
required and execute the rule to see the list of approvers.

For example if you set the attribute option to Yes when testing the rule and the attribute
usage is set to true then AME will apply the restriction to all line items in the PO to
execute the rule.
If you set the attribute option to Yes when testing the rule and the attribute usage is set
to false, when testing only 1 line item in the PO will need to meet the rule criteria to be
executed.

Setup Required For Defining Line Item Rule
Setup Required for Defining Line Item Rule

The notes following this slide will give details, step by step for the demonstration being
When analysing the approval required for the above example you need to think about
header and line level attributes.
To set up the line item rule approval for the basket you will need to follow the steps below:
1. Attributes - Define 2 non-mandatory line item string attributes for example
VGB_ITEM_NAME and VGB_ITEM_TYPE with static usage.
2. Conditions - Create an 2 ordinary line item conditions on the string attribute with
VGB_ITEM_NAME of golf clubs and VGB_ITEM_TYPE of golfing items for true
values of the condition.
3. Rule - define a list creation rule, which will use an approval type of one job level chain
of authority per line item and an approval of Require approvals up to at least level 2.
4. Test - Test the rule using the test tab. The test transaction will be created with Sarah
Bellem as the transaction requestor and she will also be the starting point person in the
job level chain. When creating the test transaction the item type and item name will be

selected using the edit line item button. The approver list generated should show Mike
Money and Geoff Walker.

Practice - Line Level Attributes and String Attribute Types

Overview
In this practice you will learn how to define rules on line items and item types.
You need to define a rule, which says that any clothing basket transaction which contains any
items type of golfing items and contains any items such golf clubs then approval must be
done by the requestors manager and a final approver who must be at job level 5 (Director Level).
Assumptions
Tasks
Defining Attributes
You will need to define two line level string attributes for the Item Type and Item Name. These
attributes will then be associated with the condition and rule that will be defined later.
Defining Conditions
You will need to define 2 ordinary line level conditions for the Item Type of Golfing Items and
Item Name of Golf Clubs.
Defining Rules
defined above.
Testing
You will test the rule created above by creating a test transaction. The requestor will be Sarah
Bellem .

Solution Line Level Attributes and String Attribute Types

Defining Attributes
1.
2.
3.
4.
Select the line item attribute button.
5.
6.
Enter XX_VGB_ITEM_NAME in the name field and select the continue button. (Replace
XX with your initials or your terminal number.)
7.
Select an Attribute type of string.
8.
Enter XX VGB name of item in the description field. (Replace XX with your name or
terminal number.)
9.
Select static yes.
10. Leave the usage field blank.

12. Repeat steps 3- 11 for the item type attribute.
Enter XX_VGB_ITEM_TYPE as the attribute name
Enter XX VGB type of item as the attribute description
Select an attribute type of string
Leave the usage field blank.
Defining Conditions
14. Navigate to the Conditions window.


continue button.
17. Select an ordinary line item condition type.
19. In the attribute field select XX_VGB_ITEM_NAME from the list of values.
20. Select the continue button
Note that the page displayed is asking for Attribute Value information.
21. Enter Golf Clubs in this field.
22. Select the Continue button to see the text value of the condition.
23. Select Quit to save the condition.
24. Repeat step 2 9 above to add the second condition of Item Type with the following values:
Select XX_VGB_ITEM_TYPE from the list of values
Enter Golfing Items as the attribute value.
Defining Rules
continue button.
27. Scroll to the end of the attributes page and select the Add A Rule button to define a
substitution rule.
28. Enter XX VGB_LINE_ITEM_RULE in the description field.
29. Select list creation in the rule type field.
33. Select the approval type of one job level chain of authority per line item.

35. In the approval field select Require approvals up to at least level 2.

37. Do not select anything in the Ordinary Conditions Header Attributes field.
38. In the Ordinary Conditions Line Item Attributes field select XX_VGB_ITEM_TYPE and
XX_VGB_ITEM_NAME.
40. Select the conditions check boxes displayed for Golf Clubs and Golfing Items.
41. Select the continue button to save the rule.
Testing

continue button.
50. Enter Bellem in the Last Name field and select the search button.
52. In the Mandatory Attributes section turn off the following attributes by changing the value to
no:


54. Enter no against any attributes that you do not want to be checked with this rule for example:
VGB_IS_GIFT_WRAPPED
VGB_IS_NEW_BASKET
55. Scroll to the end of the page and select the Edit Line Items button.
56. Select Add a Line Item button.
57. Enter Golf Clubs as the value to test in the XX_VGB_ITEM_NAME attribute
58. Enter Golfing Items as the value to test in the XX_VGB_ITEM_TYPE attribute
59. Select the Change an ID Attribute Value button so that you can enter the name of the person
as the starting point person id for the line item. In our example we are going to enter the same
name Sara Bellem.
60. Select the Query for LINE_ITEM_STARTING_POINT_PERSON_ID button.
61. Enter bellem in the last name field.
62. Select the continue button when the matching approver is found.
64. AME displays the rule that it will execute.
65. Select the View Approver List button
66. AME displays the approvers for this rule.

Dual Chains of Authority

Chapter 12

Chapter 12 - Page 1
Dual Chains Of Authority

Chapter 12 - Page 2
Objective

Chapter 12 - Page 3

At the end of this topic the demonstration will show you how to define a dual chain of
authority rule mentioned above.
The rule states that any basket with 5 or less items must be approved by the purchasing
department (chain 1) as well as the planning department (chain2).
This time the approvers in the purchasing department have changed to Mike and Geoff , while
the approvers in the planning department remain the same - Bob Taylor and C. Jones.
Note that we do not need to define any new attributes as we can use the number of items in
basket attribute defined earlier.

Chapter 12 - Page 4
Steps For Defining Dual Chain of Authority Rules
Steps For Defining Dual Chain of Authority Rules

1. Attributes We can use the Number of Items in Basket attribute defined for earlier
practices.
2. Conditions We can use the number of items in basket < 5 condition defined for earlier
practices.
3. Rules define the first list creation rule, which will use an approval type of chain of
authority includes two sub chains, each based on job level and an approval of Require
approvals at least 1 level up in the first chain. The rule will use ordinary line item
conditions and the attributes of item type and item name will be selected here.
The second list creation rule will use the same approval type; chain of authority includes
two sub chains, each based on job level however the approval will be Require approvals
at least 1 level up in the second chain.
4. Testing The test transaction will be created with Sarah Bellem as the transaction
requestor as well as being the starting point person in the first chain (the purchasing
department). In the second chain the starting point person is Bob Taylor, in the Planning
department. The result of the test transaction should display the following:

Chapter 12 - Page 5
1. Sarah Bellem
2. Mike Morney
3. Bob Taylor
4. C. Jones
The test transaction will then be modified to change the starting point person in the first
chain, from Sarah Bellem to Mike Morney and the result will be as follows:
1. Mike Morney
2. Geoff Walker
3. Bob Taylor
4. C. Jones

Chapter 12 - Page 6

Chapter 12 - Page 7
Dual Chains of Authority Attributes

Chapter 12 - Page 8
Dual Chains Of Authority Rules

Chapter 12 - Page 9
Setup Required For Defining Dual Chain Of Authority Rules
Setup Required For Defining Dual Chain Of Authority Rules

When analysing the approval required for the above example you need to think about
dual chain of authority attributes and approvals.
Use the existing number of items in basket attribute and number of items in basket <
5 condition.
To set up the dual chain of authority you will need to follow the steps below:
1. Use the VGB_NUMBER_OF_ITEMS_IN_BASKET attributes defined earlier.
2. Use the VGB_NUMBER_OF_ITEMS_IN_BASKET_<5 condition defined earlier.
3. Define 2 rules one for the first chain and the second for the second chain of authority.
The rules will use an approval type of chain of authority includes two sub chains, each
based on job level and an approval of Require approvals at least 1 level up in the first
chain and for the second rule Require approvals at least 1 level up in the second
chain.

4. Test the rule using the test tab. The testing will be done with Sarah Bellem as the starting
point person for the first chain and Bob Taylor as the starting point person for the second
chain. The test transaction will then be modified to change the attribute ID value so that
the starting point person for the first chain is Mike Morney instead of Sarah Bellem to see
how the list of approvers will change.

Practice - Dual Chains Of Authority

Overview
In this practice you will learn how to define rules using a dual (two) chains of authority.
You need to define a rule, which says that any clothing basket transaction, which contains 5 or
less items in the basket must be approved by managers in two different departments - the
planning department and the purchasing department.
The transaction is going to be submitted by Sarah Bellem in the purchasing department and when
Sarahs manager Mike Morney completes the approval the transaction will then go to the
planning department starting with B.Taylor and then approved by his manager Mr. C. Jones.
Since we have already created a rule with number of items in the baskets you will not need to
define any attributes or conditions. Define a new rule with these attributes and conditions.
Assumptions
Tasks
Defining Rules
defined above. The list creation rules will have an approval type of chain of authority, which will
include two sub chains based on job level. Both rules will have the same condition.
Testing
You will test the rule created above by creating a test transaction. The requestor will be Sarah
Bellem. When testing the rule you will determine the starting point person ids of both chains.

Solution Dual Chains Of Authority

Defining Rules
1.
2.
continue button.
3.
Scroll to the end of the attributes page and select the Add A Rule button to define a list
creation rule for the first chain of authority.
4.
Enter XX VGB_CHAIN_1 in the description field.
5.
Select list creation in the rule type field.
6.
Accept the default system date as the start date.
7.
Enter none in the end date.
8.
9.
Select the approval type of chain of authority includes two sub chains, each based on job
level.

11. In the approval field select Require approvals at least 1 level up in the first chain.
13. In the Ordinary Conditions Header Attributes field select
XX_VGB_NUMBER_OF_ITEMS_IN_BASKET.
14. Do not select anything in the Ordinary Conditions Line Item Attributes field. .
16. Select the conditions check box displayed for
0<=XX_VGB_NO_OF_ITEMS_IN_BASKET <= 5.

19. Scroll to the end of the attributes page and select the Add A Rule button to define the second
list creation rule for the second chain of authority.
20. Enter XX VGB_CHAIN_2 in the description field.
21. Select list creation in the rule type field.
25. Select the approval type of chain of authority includes two sub chains, each based on job
level.
27. In the approval field select Require approvals at least 1 level up in the second chain.
29. In the Ordinary Conditions Header Attributes field select
XX_VGB_NUMBER_OF_ITEMS_IN_BASKET.
30. Do not select anything in the Ordinary Conditions Line Item Attributes field. .
32. Select the conditions check box displayed for
0<=XX_VGB_NO_OF_ITEMS_IN_BASKET <= 5.
Testing

continue button.


to no, for example :
VGB_IS_GIFT_WRAPPED
VGB_IS_NEW_BASKET
46. Enter a value of 4 in the attribute called XX_VGB_NO_OF_ITEMS_IN_BASKET.
47. Scroll to the end of the page and select the Change An Attribute ID Value button.
48. Select the First Starting Point Person ID.
49. Select Query for FIRST_STARTING_POINT_PERSON_ID button.
50. Select Continue button to search for the name of the requestor in the first chain.
51. Enter bellem as the last name and select the search button.
Note that AME will retrieve Sarah Bellems record.
52. Select continue to return back to the Test Transaction Attributes Values page.
54. Select the Second Starting Point Person ID .
55. Select Query for SECOND_STARTING_POINT_PERSON_ID button.
57. Enter taylor as the last name and select the search button.

Note that AME will retrieve Mr. B. Taylors record

60. AME displays the list creation rules that it will execute.
62. AME displays the approvers for this rule. The list consists of Sarah Bellem, Mike Morney,
Mr. B. Taylor and Mr. C. Jones
63. Select the Change An Attribute ID Value button.
67. Enter morney as the last name and select the search button.
Note that AME will retrieve Mike Morneys record.
72. AME displays the approvers for this rule. The list consists of Mike Morney, Geoff Walker,

Handling Multiple Rules on

Transactions
Chapter 13
Handling Multiple Rules on Transactions

Chapter 13 - Page 1
Handling Multiple Rules On Transactions

Chapter 13 - Page 2
Objective

Chapter 13 - Page 3
How AME Sorts Rules At Run Time
How AME Sorts Rules at Run Time

At run time AME decides the order in which rules should be applied to a particular
transaction according to the following algorithm:
1. Exception rules first thus suppressing any appropriate list-creation rules
2. Remaining list creation and exception rules.
3. List modification rules
4. Substitution Rules
5. Pre-Approval Rules
6. Post-Approval Rules
Within each step of the algorithm AME groups the rules by approval type (such as absolute
job level, dual chains of authority, etc ) and processes all rules of one type before
processing rules of the next type.
Step 1 above contains another algorithm used by AME to order the rules. AME first sorts
the list creation and exception rules by their approval types. Secondly AME will do the
following for each approval type:

Chapter 13 - Page 4
a) If the value of the mandatory boolean attribute (ALLOW_REQUESTOR_APPROVAL)

is true AME will check to see if the requestor has signing authority for this transaction. If
this is the case AME will continue to the next approver
b) AME will fetch the identity of the next approver and add that approver to the end of the
approval list.
c) If the latest approver responds to the request by forwarding the request to another
approver AME will add the forwarder to the end of the approver list.
d) AME will check if the latest approver has the required signing authority for the
transaction. If this is the case AME will continue to the next approval type. If this is not the
case AME will go back to step (b) above.
AME processes list-modification, substitution, pre and post approval rules in the same way
as it processes list-creation rules i.e. it sorts the rules by approval type and processes all
rules for a particular approval type together.

Chapter 13 - Page 5
Rule Sharing In AME
Rule Sharing In AME

The above diagram illustrates the relationship of the components in AME with Transaction
Types.
Transaction Types: are the highest defining level in AME and these are usually defined
by the administrator using the administration tab. Transaction types share approval
groups defined by users and the pre-delivered approvals.
Rules: are specific to a transaction type; however, they can share user defined conditions
and attribute names.
Conditions :when adding new conditions AME will display the attributes defined for the
transaction type thus allowing you to select the only those attributes. If you shared the
attribute name when defining attributes AME will automatically display the conditions
associated with that attribute allowing you to modify these as required for the particular
rule and thus the transactions type.
Attributes: when defining new attributes AME will allow you the option to share an
existing attributes name. However you can define the attribute usage differently (i.e. use a
different SQL table for dynamic usage or use a different value for static usage.

Chapter 13 - Page 6
You can therefore reduce maintenance in AME by defining generic rules which can be
selected across multiple transaction types and customise the behaviour of these rules by
modifying the conditions and attribute usages.

Chapter 13 - Page 7
Setup Required For Rule Sharing
Setup Required For Rule Sharing

To demonstrate rule sharing you will need to follow the steps below:
1. Define a new transaction type called for example, VGB Golfing Basket, using the Admin
tab
2. Define an new attribute but share the existing name of ITEM TYPE and ITEM NAME
3. Define a new condition with new upper and lower limits.
4. Verify the approvals used for the approval types.
5. Define a rule to test an approval when the number of items in the basket has increased
and the value of the basket has therefore altered.
6. Test the rule using the test tab.

Chapter 13 - Page 8
Practice - Handling Multiple Rules On Transactions

Overview
In this practice you will learn how to share rules defined for the VGB Clothing Basket with a
new basket configuration called VGB Accessories basket.
You do nor need to define any new attributes or conditions, however you do need to define the
rule usage with the new basket configuration and test the rules by creating test transactions using
the test tab.
Assumptions
Instructor needs to define a new basket configuration called VGB Accessories Basket
using the admin tab.
Tasks
Defining Rules
You will define rule usages (share these rules) with the accessories basket. These rules currently
being used by the VGB Clothing Basket configuration:
XX_VGB_SUBS_RULE_JOHN_DOE_FOR_FRED_MASON
XX_VGB_GIFT_WRAPPING_SERVICE
XX_VGB_0_5_ITEMS_IN_BASKET
XX_VGB_TOTAL_VALUE_OVER_EUR100
Testing
You will test the rule created above by creating a test transaction. The requestor will be Guy
Wire (in the planning department). When testing the rule you will determine the number of items
in the basket and the value in Euros.

Chapter 13 - Page 9
Solution Handling Multiple Rules On Transactions

Defining Rules
1.
2.
Change the transaction type to VGB Accessories Basket from the list of values and select
the continue button.
3.
Scroll to the end of the attributes page and select the Add Usage button to select the rules
you want to share with the Accessories basket.
4.
Select the transaction type of add usage for rule used by another transaction type in step 1
of adding a rule usage.
5.
Select the continue button to define the dates from when you want to start to share these
rules.
6.
Select the Transaction type, which has the rules currently, defined. So this example you will
select VGB Clothing Basket from the list of transactions types.
7.
Select the List of Values in the Rules field and this will display all rules, which are currently
available with the VGB Clothing basket.
8.
Select XX_VGB_SUBS_RULE_JOHN_DOE_FOR_FRED_MASON from the list of values

displayed
9.
Select continue to enter a start date for this rule to be active.
10. Accept the default start and end which should be the system date.
11. Accept the default value of none in the end date and the rule will be active until you enter an
end date.
12. Select the create Usage button and AME will confirm this rule to be added to the VGB
Accessories transaction type.
13. Repeat steps 2-11 above for the remaining rules that you want to share with the Accessories
basket transaction type.
Testing


continue button.
to no, for example:
VGB_IS_GIFT_WRAPPED
VGB_IS_NEW_BASKET
25. Enter a value of 4 in the attribute called XX_VGB_NO_OF_ITEMS_IN_BASKET.
27. Select the First Starting Point Person ID .
30. Enter bellem as the last name and select the search button.
Note that AME will retrieve Sarah Bellems record.

33. Select the Second Starting Point Person ID .
34. Select Query for SECOND_STARTING_POINT_PERSON_ID button.
36. Enter taylor as the last name and select the search button.
Note that AME will retrieve Mr. B.Taylors record
41. AME displays the approvers for this rule. The list consists of Sarah Bellem, Mike Morney,
42. Select the Change An Attribute ID Value button.
46. Enter morney as the last name and select the search button.
Note that AME will retrieve Mike Morneys record.
52. AME displays the approvers for this rule. The list consists of Mike Morney, Geoff Walker,

Rule Priorities
Chapter 14
Rule Priorities
Chapter 14 - Page 1
Rule Priorities
Rule Priorities
Chapter 14 - Page 2
Objective
Rule Priorities
Chapter 14 - Page 3
Rule Priorities
Rule Priorities
Chapter 14 - Page 4
Enabling Rule Priorities
Rule Priorities
Chapter 14 - Page 5
Enabling Rule Priorities - Modes
Enabling Rule Priorities Modes

Absolute this will check the threshold value against the value inserted for the rule itself and if
the values match or the rule priority is higher then AME will apply the rule priority.
For example consider the following list creation rules
Rule A :
if CATEGORY in {Computer Hardware}
then
require approvals up to at least level 2 (Priority = 3)
Rule B:
if CATEGORY in {Computer Hardware}
and
10,000 USD <= TRANSACTION_AMOUNT
then
require approvals up to al least level 4 (Priority = 2)
If rule priority is not being used both rules would apply to the transaction.
Rule Priorities
Chapter 14 - Page 6
If rule priority is being used and the threshold is set to 2 then AME will remove Rule A and
execute Rule B to determine the list of approvers.
Relative process rules according to their ranking order.
For example using the 2 rules mentioned above, if the threshold value is 2 and mode is
relative both rules would qualify because we have allowed 2 highest stringent qualifying
rules to be accepted.
Disabled simply turns off any rule priorities in AME and does not display the ranking option
when defining rules.
Rule Priorities
Chapter 14 - Page 7
Enabling Rule Priorities - Attributes
Enabling Rule Priorities Attributes

Use the EVALUATE_PRIORITIES_PER_LINE_ITEM attribute if you want to evaluate rule
priorities per line item. If you decide to use this attribute you must also use the
USE_RESTRICTIVE_LINE_ITEM_EVALUATION which determines if the specified line
item satisfies all line-item conditions in a the rule.
Both attributes are boolean attributes and the usage can be static or dynamic.
Rule Priorities
Chapter 14 - Page 8
Setup Required For Rule Priorities
Setup Required For Rule Priorities

The notes following this slide give details, step by step for the demonstration being performed
by the instructor.
To demonstrate rule priority you will need to access the admin tab (usually done by the
system administrators) to set rule priority thresholds up and then modify existing rules
before creating test transactions.
1. Create a test transaction using the accessories basket with no rule priorities switched on.
The test results will select 4 rules in total to apply. Two of these rules are list creation rules:
1. XX_VGB_MORE_THAN_11_ITEMS_IN_BASKET
2. XX_VGB_TOTAL_VALUE_OVER_EUR100
2. Select the Admin tab and change the set the rulePrioritesModes configuration value by
using a default value of yes. For list creation priorities select the absolute option and enter a
threshold value of 1.
3. Submit your changes.
Rule Priorities
Chapter 14 - Page 9
4. Select the Rules tab and modify all list creation rules to have a priority value of 1, 2 etc.
For the 2 rules mentioned above enter a value of 1 on the first rule and 2 for the second
rule.
5. Create a test transaction with the same values and using the same attributes as before to see
the effect of setting absolute rule priority has with a threshold value of 1.
6. Change the threshold value to 2 and test the rule again.
Rule Priorities
Demo - Rule Priorities

Responsibility: General Business User
N > Approvals > Test (to create test transactions)
Note that the names used in this demonstration are for the purpose of the demonstration and bear
no resemblance to any particular organization or individuals.
This demonstration is going to be done in two stages. In the first stage a test transaction is going
to be created without using any rule priorities. This will show the rules that AME will action
with the particular attributes selected.
In the second part the rule priorities option will be activated using the admin tab on list
creation rules. The priority value will be set on all list creation rules and then the test transaction
will be created again using the same options as before to see how switching on rule priorities has
made changes to the rules actioned by AME.
1.
Select the test tab and create a test transaction for the accessories basket
2.
Select Sarah Bellem as the transaction requestor.
3.
Select the following Test Transaction Attribute Values:

XX_VGB_NO_OF_ITEMS_IN_BASKET
XX_VGB_TOTAL_VALUE_OF_BASKET_Amount
XX_VGB_TOTAL_VALUE_OF_BASKET_Currency
4.
Enter 45 as the number of items in the basket
5.
Enter 550 as the value of the basket (amount)
6.
Select EUR (Euros) as the value (currency) from the list of values available
7.
Select Corporate as the conversion type
8.
Select the view approval process button

AME displays all the possible rules that will be actioned with the attributes selected. Note
the 2 list creations rules.
N > Approvals > Admin

Note this tab is usually used by system administrators and therefore may not be available
under the General User Responsibility.
Rule Priorities
1.
Select the Admin tab
2.
Select Maintain Transaction Types option and then select the continue button.
3.
Select VGB Accessories Basket from the transaction types displayed.
4.
Select Update Configuration Variables button
5.
Select the rulePriorityModes configuration variable.
6.
Change the Use Default Value field to Yes so that AME will now start to use rule
priorities.
7.
Select the absolute button for the list creation priorities. This will set the rule priorities at
absolute for all list creation rules for the Accessories Basket transaction type.
8.
Enter a 1 in the threshold value.

Note that by selecting absolute, for our example, and entering a value of 1 in the threshold
AME will look at the rule priority of all list creation rules for the accessories basket and at
runtime it will only apply those rules who have a priority number of 1 and ignore all other
list creation rules.
9.
Select the submit changes button.
10. Select the Rules tab and select the transaction type of Accessories Basket.
Ame will display all rules that are currently defined for the accessories transaction type.
Since the rule priorities are being used after the rule has been defined, you will need to
define the rule priority number for each list creation rule.
11. Select the priority field and enter the value required. Ensure that you enter the following for
the 2 rules that are being actioned when creating test transactions:
XX_VGB_MORE_THAN_11_ITEMS_IN_BASKET
PRIORITY = 1
XX_VGB_TOTAL_VALUE_OVER_EUR100
PRIORITY = 2
12. Select the test tab and repeat steps 1- 8 above.
Note: AME will display the rules that will be actioned with the attribute values entered.
There should be 4 rules, which include the 2 list creation rules mentioned above.
13. Select the View Rules After Priority Processing button. Ame will now only select one list
creation rule to action and this should be the one which had the priority number set to 1.
14. Select the View Approval List button. AME will display the list of approvers starting with
Mike Morney, Geoff Walker and Susan Price.
Rule Priorities
Summary
Chapter 15
Summary
Chapter 15 - Page 1
Summary
Chapter 15 - Page 2
Objectives
Summary
Chapter 15 - Page 3
Topics Covered
Summary
Chapter 15 - Page 4
Topics Covered
Summary
Chapter 15 - Page 5
Summary
Chapter 15 - Page 6

Using and Maintaining Oracle Approvals Management (AME) Student Guide

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Using and Maintaining Oracle Approvals Management (AME) Student Guide

Transféré par

Droits d'auteur :

Formats disponibles

Using and Maintaining Oracle

Copyright Oracle International Corporation, 2003. All rights reserved.

Using and Maintaining Oracle Approvals Management (AME) Table of Contents

Using Currency Attributes.............................................................................................................................6-6

Copyright Oracle Corporation, 2003. All rights reserved.

Using and Maintaining Oracle Approvals Management (AME) Table of Contents

Line Level Attributes and String Attribute Types........................................................................................11-1

Copyright Oracle Corporation, 2003. All rights reserved.

Using and Maintaining Oracle Approvals Management (AME) Table of Contents

Copyright Oracle Corporation, 2003. All rights reserved.

Using and Maintaining Oracle Approvals Management (AME) Table of Contents