using and maintaining oracle approvals management (ame) student guide (2) (1)

8/10/2019 Using and Maintaining Oracle Approvals Management (AME) Student Guide (2) (1)

1/229

Using and Maintaining OracleApprovals Management(AME)Student Guide

Internal Use Only


2/229

Copyright Oracle International Corporation, 2003. All rights reserved.

This documentation contains proprietary information of Oracle International Corporation. It is provided under a license agreementcontaining restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software isprohibited. If this documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered withRestricted 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 deemedto be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights inTechnical 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 theEducation Products group of Oracle International Corporation. Any other copying is a violation of copyright law and may result incivil 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 withRestricted 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 reportthem 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: oracle tutor


3/229


4/229

Copyright Oracle Corporation, 2003. All rights reserved.

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

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 Solution Building List Creation Rules - 2...............................................................................................6-15

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 Approval Policy Rule Components ............................................................................................................9-7 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


5/229


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

Line Level Attributes and String Attribute Types........................................................................................11-1 Line Level Attributes and String Attribute Types .........................................................................................11-2 Objectives ......................................................................................................................................................11-3 Approval Policy Rule Components ............................................................................................................11-4 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 Approval Policy Rule Components ............................................................................................................12-4

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


6/229


7/229


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


8/229


Using and Maintaining Oracle Approvals ManagementChapter 1 - Page 1

Using and Maintaining OracleApprovals ManagementChapter 1


9/229



Using and Maintaining Oracle Approvals Management (AME)


10/229



Objectives

ObjectivesPlease note that this class is a follow up to the AME overview class, which is available fromOUOL. The overview class covers the basic concepts of rules, conditions, attributes andgroups.The focus of this class on the practices that will follow each topic whereby the options ofdefining different types of rules are demonstrated.


11/229



Topics Covered


12/229



Topics Covered


13/229




14/229


Using and Maintaining Oracle Approvals Management - IntroductionChapter 2 - Page 1

Using and Maintaining OracleApprovals Management -IntroductionChapter 2


15/229



Using and Maintaining Oracle Approvals Management (AME)Introduction


16/229



Objective

ObjectivePlease access the Oracle Approvals Management Overview eclass for an overall understandingof rules, attributes, conditions, groups and testing rules.


17/229



Business Processes or Transactions and Approvals

Business Processes or Transactions and ApprovalsMost 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 inthe document.

The details for many types of transaction are held until the transaction is finally approvedand 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 ofapprovals and notifications.

3. Approvals processing should follow your own business rules for each type of transaction.


18/229



For example, you may have different routing rules for expenses and purchasing, or fordifferent departments; or you may require different levels of approval based on the totalvalue of an order, or based on specific details in the document.

Approvals usually involve a combination of notifications and standard responses tonotifications. For example, Oracle Applications use Approve, Reject and Return asstandard responses.

4. When finally approved the underlying records are updated.


19/229



What is AME?

What Is AME?Calling application refers to the application that is using AME components to define theapproval process. Calling applications can be Oracle applications or any application that is usesPL/SQL code.


20/229



When Can I Use AME?


21/229



Business Requirements

Business Requirements: Example of approval loop using AMEThe diagram above shows a basic business process using AME.1. An employee creates their expense reports2. 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 theexpenses and if the value is more than $100, then manager 2 needs to approve thetransaction.


22/229



Overview of AME Components


23/229




24/229


Mapping Business RequirementsChapter 3 - Page 1

Mapping BusinessRequirementsChapter 3


25/229



Mapping Business Requirements


26/229



Approval Policies


27/229



Approval Policies


28/229



Approval Policies Attributes

Approval Policies Attributes Note: Currency attributes have more than one value. When using currency attributes you usethe following values:AmountDenominationRate Type


29/229



Examples of Approval Policies


30/229



Vision Gift Basket Scenario

Vision Gift Basket ScenarioThis class is going to demonstrate each of the above approval and discuss and demonstrate howto define the specific attributes, conditions and rules. The test tab will be used to create testtransactions 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 anumber of product lines, and a large catalogue of products.The company has recently installed software to assist the managers with approvals for varioustypes of transactions. This fictitious software called, Vision Gift Basket (VGB) isintegrated with Oracle Approvals Management (AME).The Vision Gift Basket (VGB Clothing Basket) has been created in AME as a transaction typeand 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 basketconfigurations via the internet, and is implementing new approval rules to prevent incorrectitems and prices going out.


31/229



The management has asked for these approvals to be defined and tested in AME.


32/229



Vision Gift International Organisation Chart

Vision Gift International - Organisation ChartThe sample Organisation chart above shows relationships of individuals with their Job Levelsin Oracle HRMS.

In the organization chart above, Vincent Price is the last person in the approval chain andis 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 ofapprovals rules.


33/229



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.


34/229


Building List Creation Rules - 1Chapter 4 - Page 1

Building List Creation Rules -1Chapter 4


35/229



Building List Creation Rules Part 1


36/229



Objective


37/229



Approval Policies

Approval PoliciesAt the end of this topic the demonstration will show you how to define the 3 rules mentionedabove.The rules are all list creation rules which use an approval type of chains of authority basedsupervisory levels. The number of items in the basket determine how high up the chain theapproval 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 numberof items in the basket.Finally you will need to define 3 different rules each using one of the conditions defined.


38/229



Approval Policies Rule Components


39/229



Steps For Defining List Creation Rules

Steps For Defining List Creation Rules1. 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, whichcan be deleted or modified. AME will check when you delete attributes to ensure that theyare not already being used with any rules. Although attributes are specific to transactionstypes they can be shared across transaction types by sharing the name of the attribute anddefining specific usages for the attribute.

2. Conditions In our example we would like to perform 3 different types of actionsdepending on the number of items in the basket, therefore we must define 3 conditions withvarying numeric ranges. Condition are specific to transaction types. AME will let youmodify 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 associatesthese 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 acrossdifferent transaction types. You can also modify the behaviour of conditions when definingrules, thus reducing maintenance.


40/229



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


41/229



List Creation Rule - Attributes

List Creation Rules AttributesFor 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 usagesyou can determine various ways of using the attribute.Attribute usages can be dynamic or static. For the purposes of this demonstration we are goingto 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 inthe 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)


42/229



from

po_transaction_all ai, po_system_parameters_all asp

where

ai.purchase_order_id = :transactionIdand

ai.org_id = asp.org_id You define dynamic usages of an attribute and in the usage field by entering SQL statementswhich will retrieve the data from tables and columns specified.User defined attributes are listed as non-mandatory attributes since these are defined accordingto 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.


43/229



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 conditionwhich will apply to all lines in the transaction.

You can use ordinary and exception condition types with attributes that have a list or arange of possible values such as number of items in the basket from 0 - 5 etc . At runtime, if the attribute has this value, then the condition is true, otherwise the condition isfalse.

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


44/229



Conditions Numbers and Ranges

Conditions Numbers and Ranges Note that when you define numerical conditions AME inserts the < or


45/229



Approval Types and Rule Types

Approval Types and Rule TypesFor our list creation rule example we are going use the supervisory level approval type as wewant to ascent the supervisor chain of authority and list the managers who can approvetransactions depending on the number of items in the basket.


46/229



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 boththe 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 andVincent Price.


47/229



For dual chains of authority (useful, for example, when a person is being transferred fromone manager to another), you must define usages for first and second starting pointattributes.

When you transfer a person from one manager to another, dual chains of authority can beused with the selected persons current manager as the first starting point in the chain andthe proposed manager as the second starting point.


48/229



Supervisor Approval Type

Supervisor Approval TypeWhen using the supervisor hierarchy with a job level, you must define jobs and levels beforeassigning these to the employees.The number of supervisors that are selected in the approval list, depends on where the chainstarts and ends.The start point of the chain depends of the value of the required attribute and how high inhierarchy 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 initiatesthe transaction. This person is identified by the mandatory attributeTRANSACTION_REQUESTOR_PERSON_IDHowever if a value is specified for theSUPERVISORY_NON_DEFAULT_STARTING_POINT_PERSON_ID then AME will

bypass the transaction requestors supervisor and go to the person specified in this chain andthen ascend up this chain of authority instead selecting all supervisors as approvers.


49/229



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


50/229



Overview of Rules

RulesBy combining rule types with conditions and approval types, you produce different effects on atransactions 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 listcreation and exception rules.

You can use substitution rules to replace an approver with another specified approver inthe 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.


51/229



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 achain of authority using the supervisor hierarchy and how you may want modify thedefault supervisors that would be selected according to the number of items in theshopping basket.

Next consider the conditions you would need to create and then determine the attributethat will be most suitable to use.

To set up the example of value and job approval for the purchase order you will need to followthe steps below:

1. Create an attribute for this transaction type called for exampleNUMBER_OF_ITEMS_IN_BASKET.

2. Create multiple ordinary header conditions by using the attribute defined in step 1. Enterthe value ranges for approval amounts, that is, from 0 5, 6- 10 and 11 onwards.


52/229



- Note that you will need to create multiple conditions for each of the rangesrequired.

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 supervisorylevels. and the approval will determine how high to go in the approval list. Finally youselect 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 areusing a fictitious application called Vision Gift Basket and the attribute usage wasdefined as static. Testing is covered in more detail in the next topic.


53/229



Practice - Building List Creation Rules - 1

OverviewIn 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 immediatesupervisor of the person submitting the transaction

Rule B If the basket contains 6 10 items then approval has to be done by the secondimmediate 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 thirdimmediate supervisor in the chain of authority as well as the second immediate supervisor ofthe person submitting the transaction.

Assumptions

You must have access to an Oracle Application Vision database or comparable trainingor 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 noresemblance to any particular organization or individuals

Prefix all names of rules, attributes and conditions with your assigned unique groupnumber 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 mentionedabove. 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 onthe attributes page:

SUPERVISORY_NON_DEFAULT_STARTING_POINT_PERSON_ID

TOP_SUPERVISOR_PERSON_ID


54/229



Defining Conditions

You will need to define three ordinary header conditions for the ranges of items in the basketspecified. 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 approvaltypes defined. The ranges of the 3 rules will be as follows:

0 5 items 6- 10 items 11 or more items


55/229



Solution Building List Creation Rules - 1

Defining AttributesResponsibility = 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 andselect 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 nameor 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 thecontinue button.

2. Scroll to the end of the conditions page and select Add a Condition button.


56/229



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 ofvalues.

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 6 in the lower limit field.

Enter 10 in the upper limit field.

Select yes for include lower limit.

Select yes for include upper limit

14. Repeat steps 2 to 11 for the third range (from 11 onwards) with the following values: Enter 11 in the lower limit field. Leave the upper limit field blank. Select yes for include lower limit. Select yes for include upper limit

Defining Rules

Navigate to the Rules window.

(N) Approvals > (T) Rules


16. Scroll to the end of the attributes page and select the Add A Rule button to define the firstrule for a range of items within 0 5.


57/229



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.


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 HeaderAttributes 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


58/229




42. Select XX_VGB_NO_OF_ITEMS_IN_BASKET in the Ordinary Conditions HeaderAttributes field.



45. Check the ordinary condition 6


59/229



64. Select the Quit button to return back to the approvals menu page.


60/229


Testing the List Creation RuleChapter 5 - Page 1

Testing the List Creation RuleChapter 5


61/229



Testing The List Creation Rule


62/229



Objective


63/229



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 casesno 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 anyinformation 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 andtherefore do not have any SQL tables that we would normally use when addressingdynamic usages for example.


64/229



Test Tab Creating Test Transactions

Test Tab Creating Test TransactionsUsing this feature you create a fictitious transaction and select the attribute values for thetransaction. You can change the attributes values as often as you like to see how each changeeffects 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 transactionnumber with a minus sign to distinguish this from a real transaction id number.

Transactions created using this feature are stored within AMEs transactions tables.


65/229



Testing List Creation Rule Transaction

Testing List Creation Rule TransactionThe 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, basedon the value of the transaction. Please see the demonstration at the end of this topic whichwill display the results of these test transactions.

The tests will be done in three stages using Sarah Bellem as the person submitting thetransaction:

Stage 1 we will enter a value between 0 - 5 and see the approvers. The test should showMike 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 2approvers 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 beselected.


66/229



Practice - Testing The List Creation Rule

OverviewIn this practice students will test the rules created earlier using the create a test transaction optionas 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 immediatesupervisor of the person submitting the transaction.

Rule B If the basket contains 6 10 items then approval has to be done by the secondimmediate 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 thirdimmediate supervisor in the chain of authority as well as the second immediate supervisor ofthe 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


67/229




Testing RulesResponsibility = AME General Business User, Approvals

1. Navigate to the Test window.

(N) Approvals > (T) Test

1. Select the test tab.


3. In the Choose Test Type page select Create a test transaction.


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 onlyone employee record with this name, Sarah Bellem.


8. In the Mandatory Attributes section turn off the following attributes by changing the valueto 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 theTRANSACTION_REQUESTOR_PERSON_ID.

10. Enter no against any attributes that you do not want to be checked with this rule forexample:

VGB_IS_GIFT_WRAPPED

VGB_IS_NEW_BASKET


68/229



11. Enter a value less than 6 (for example 5) in the attribute calledXX_VGB_NO_OF_ITEMS_IN_BASKET

Note: The only rule being applied for this test transaction is a list creation rule calledVGB_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 ofitems 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 ofitems in the basket has changed to 17.

19. Select the View Approval Process button.

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.


69/229



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 whichwill automatically load in all the attributes details for the transaction. AME will thenapply 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 wantto query specific transaction ids with the rules. The general day to day user would usethe 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 informationwhich will be loaded into AME:

TRANSACTION_REQUESTOR_PERSON_ID


70/229



WORKFLOW_ITEM_KEY WORKFLOW_ITEM_TYPE CURRENT_ASSIGNMENT_ID

CURRENT_EFFECTIVE_DATE TOP_SUPERVISOR_PERSON_ID WORKFLOW_PROCESS_NAME

4. In AME go to the test tab and select the view a real transactions approval process feature.5. AME will prompt you to enter the transaction id6. 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.7. AME will then display the order in which the rules are going to apply to the transaction.

8. AME generates the list of approvers for that transaction.

SQL for extracting the Transaction i.d. By Notification i.d.:-

select context from wf_notificationswhere 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_itemswhere item_type='HRSSA'and owner_role= 'put user name here'order by begin_date desc

Query 2 - To find transaction idTake the item key for the transaction you just ran and insert it into query 2 below:

select transaction_id from hr_api_transaction_stepswhere 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_idand hat.selected_person_id = (select person_id


71/229



from per_people_xwhere last_name = 'PJS US New Employee 2')

/*and hat.transaction_id in (

select transaction_idfrom hr_api_transaction_stepswhere api_name = 'HR_PAY_RATE_SS.PROCESS_API')*/

and hat.creation_date between sysdate-1 and sysdate+1order by hat.transaction_id desc


72/229



Building List Creation Rules -2Chapter 6


73/229



Building List Creation Rules Part 2


74/229



Objective


75/229



Approval Policy

Approval PolicyAt 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 followingdifference:

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 for300 EUROS the approvers should be Geoff Walker and Susan Price. Mike Morneyis 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 authoritywhich are based on relative job levels. The Euro value of the basket will determine if theapproval is going to be done by Geoff and Susan.


76/229



Steps For Defining List Creation Currency Rule

Steps For Defining List Creation Currency Rule1. 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 acrossdifferent transaction types. You can also modify the behaviour of conditions when definingrules, thus reducing maintenance.

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


77/229



Using Currency Attributes

Using Currency AttributesAME has a defined attribute type called currency which is used with transactions where youwant to convert the entered currency amount into the currency amount specified in the attributetype. For example if the TRANSACTION_AMOUNT is US dollars (USD) and when AME isrun the value it fetches is Euros (EUR) then AME will convert the Euros to the equalivant USdollar value by applying the conversion from Euros to USD according to the date specified inthe 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 andhave valid exchange rates.If you decide to use static usage with the currency type attribute the format for setting up theusage 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 example99.99.

Code is the currency code defined in the GL Define Currency table. Usually these areISO codes for currencies.


78/229



Type relates to the Rate Type field on the GL Daily Rates table. This type field is thecurrency conversion type and can have values such as Corporate, User or Spot whichdenote 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 threecolumns; amount, code and type. The amount selected must be converted to a varchar2 by:

fnd_number.number_to_canonical (amount)


79/229



Using Currency Conditions


80/229



Relative Job Level Approval Type

Relative Job Level Approval TypeThis job level works similar to the absolute job level however the difference is that the ascentup 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 selectthe 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 firstapprover within the job level will be included.The JOB_LEVEL_NON_DEFAULT_STARTING_POINT_PERSON_ID attribute determinesan alternative requestor for the approval. This requestor is a different person to the one whosubmits the transaction initially.


81/229



Default and Non Default Starting Points


82/229



Setup Required for Defining List Creation Rule with Currency

Setup Required for Defining List Creation Rule with currency 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 achain of authority using the relative job level as you want the chain to start relative to thetransaction requestor.

Next consider the currency condition you would need to create and then determine theattribute 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 3components of the currency attribute: value, code and rate type.

2. Create conditions by using the attribute defined in step 1. Enter the currency codespecified in the attribute as code and use the value ranges for approval amounts.


83/229



3. Create your rule selecting the attribute and condition defined earlier. The rule will havean approval type of chains of authority based on relative job levels. and the approvalwill determine how high to go in the approval list. Finally you select the condition withthe value range when defining rules.

3. Test the rule by creating a test transaction and viewing the list of approvers generated byAME.


84/229



Practice - Building List Creation Rules - 2

OverviewIn this practice you will learn how to define rules based on currency and understand the use ofthe relative job level approval type.

You need to define a rule, which says that any clothing basket with a value over EUR 100requires 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 GeoffWalker should be the approvers and if Mike Morney submits the transaction then the approversshould be Geoff Walker and Sarah Price.

Assumptions



Prefix all names of rules, attributes and conditions with your assigned unique groupnumber or your initials.


Tasks

Defining Attributes

You will need to define one non-mandatory header currency attribute for the rule mentionedabove. 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 requiredattributes. When you are defining attributes check that the following required attributes doappear 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 saythat the condition applies for all transactions over EUR 100.


85/229



Defining Rules

You will define 1 list creation rules, which will use the attributes, conditions and approval typesdefined.

Testing

You will test the rule created above by creating a test transaction. The first test will be to useSarah Bellem as the person submitting the transaction for 300 Euros. Then change the value to30 Euros and still have Sarah Bellem as the transaction requestor. Finally enter Mike Morneysname as the person submitting the transaction for 300 Euros.


86/229




Defining AttributesResponsibility = 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 andselect 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_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 nameor terminal number.)

9. Select static yes.

10. Enter 9999,EUR, Corporate in the Usage area.

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


2. Scroll to the end of the conditions page and select Add a Condition button.


87/229



3. Select an ordinary header condition type.


5. In the attribute field select XX_VGB_TOTAL_VALUE_OF_BASKET from the list ofvalues.

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.

11. Select yes for include upper limit

12. Select the Create Condition button.

13. AME will confirm the condition being added successfully.

Defining Rules

Navigate to the Rules window. (N) Approvals > (T) Rules


15. Scroll to the end of the attributes page and select the Add A Rule button to define the firstrule for a range of items within 0 5.

16. Enter XX_VGB_TOTAL_OVER_EUR100 in the description field.

17. Select list-creation rule in the rule type field.

18. Accept the default system date as the start date.

19. Enter none in the end date.


21. Select the approval type of chains of authority based on relative job level.



88/229



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 HeaderAttributes field.



28. Check the ordinary condition 100 EUR (T) Test

32. Select the test tab.


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.

Note: AME will retrieve all records that match the search criteria. In this case there is onlyone employee record with this name, Sarah Bellem.


39. In the Mandatory Attributes section turn off the following attributes by changing the valueto no. For example:

EVALUATE_PRIORITIES_PER_LINE_ITEM

USE_RESTRICTIVE_LINE_ITEM_EVALUATION


89/229



40. 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 theTRANSACTION_REQUESTOR_PERSON_ID.

41. Enter no against any non-mandatory attributes that you do not want to be checked with thisrule 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 theXX_VGB_TOTAL_VALUE_OF_BASKET Currency field

50. Select Corporate from the list of values available in theRK_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 testtransaction.

Note: The only rule being applied for this test transaction is a list creation rule calledXX_VGB_TOTAL_VALUE_OVER_EUR100, which we had defined earlier.

52. Scroll to the end of the page and select the view approval list button.

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 transactionrequestor person ID

60. Enter a value of 300 in the XX_VGB_TOTAL_VALUE_OF_BASKET amount attribute.


90/229



Note AME will retain the other attribute values selected previously such as the currencycode 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.

62. Select the Quit button to return back to the Test Type page.

63. Select the Quit button to return to the main menu page.


91/229




92/229


List Modification and Substitution RulesChapter 7 - Page 1

List Modification andSubstitution RulesChapter 7


93/229



List Modification and Substitution Rules


94/229



Objective


95/229



Approval Policy Rule Components

Approval PolicyAt the end of this topic the demonstration will show you how to define the substitution rulementioned above.The rule will substitute Fred Masons name with John Doe. When defining the condition youenter the name of the person you want to substitute; in our example this is going to be FredMason. In this planning department Guy Wire reports to Fred Mason and Fred reports to BobTaylor and Bob reports to Mr. C. Jones. Thus if the transaction is submitted by Guy Wire itwould normally go to Fred for approval, however since we are going to substitute Fred withJohn 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.


96/229



Steps For Defining Substitution Rule

Steps For

using and maintaining oracle approvals management (ame) student guide (2) (1)

Documents