Using and Maintaining Oracle Approvals Management (AME) Student Guide (2) (1)
Short Description
Using_and_Maintaining_Oracle_Approvals_Management_(AME)...
Description
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 W orldwide 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 withTest Transactions....................................................................................................................5-4 Test Tab Rules Creating Transactions ........................... .............. .............. .............. ............... ........................5-5 Testing List Creation Rule Transaction.........................................................................................................5-6 Practice - Testing The List Creation Rule..................................................................................................5-7 Solution – Building List Creation Rules - 1...............................................................................................5-8 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 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 ......... .......... ........... ........... .......... .......... ........... .......... ........... ..........1 0-1 Effective Dates For Rules and Attributes .............. ............................ .............. ............... ........................... ....10-2 Objectives ........................... .............. .............. .............. .............. ........................... .......................... ..............1 0-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
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management (AME) Table of Contents ii
Line Level Attributes and String Attribute Types........................................................................................11-1 Line Level Attributes and String Attribute Types .............. .............. ........................... .............. .............. ......11-2 Objectives ........................... .............. .............. .............. .............. ........................... .......................... ..............1 1-3 Approval Policy – Rule Components ........................... .............. .............. .............. ............... ........................11-4 Steps For Defining Line Item Rules .......................... .............. .............. ........................... .............................11-5 Attribute Levels........................ ........................... ........................... ........................... .............. ......................11-6 String Attributes Types......... ........................... .............. ........................................ .............. ..........................1 1-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 ........................... .............. .............. .............. .............. ........................... .......................... ..............1 5-3 Topics Covered.................. .............. .............. ............... .............. ........................... ........................... .............1 5-4
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management (AME) Table of Contents iii
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management (AME) Table of Contents v
Using and Maintaining Oracle Approvals Management Chapter 1
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management Chapter 1 - Page 1
Using and Maintaining Oracle Approvals Management (AME)
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management Chapter 1 - Page 3
Topics Covered
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management Chapter 1 - Page 4
Topics Covered
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management Chapter 1 - Page 5
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management Chapter 1 - Page 6
Using and Maintaining Oracle Approvals Management Introduction Chapter 2
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction Chapter 2 - Page 1
Using and Maintaining Oracle Approvals Management (AME) Introduction
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction 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. Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction Chapter 2 - Page 6
When Can I Use AME?
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction Chapter 2 - Page 8
Overview of AME Components
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction Chapter 2 - Page 9
Copyright © Oracle Corporation, 2003. All rights reserved.
Using and Maintaining Oracle Approvals Management - Introduction Chapter 2 - Page 10
Mapping Business Requirements Chapter 3
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements Chapter 3 - Page 1
Mapping Business Requirements
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements Chapter 3 - Page 2
Approval Policies
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements Chapter 3 - Page 3
Approval Policies
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements 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
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements Chapter 3 - Page 5
Examples of Approval Policies
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements 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. Vision’s 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. Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements Chapter 3 - Page 7
The management has asked for these approvals to be defined and tested in AME.
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements 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 Newman’s manager is Lucy Lawson and Lucy reports to Vincent Price. • In the second chain, Fred Mason reports to B. Taylor and Taylor’s 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Mapping Business Requirements Chapter 3 - Page 10
Building List Creation Rules 1 Chapter 4
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 Chapter 4 - Page 1
Building List Creation Rules Part 1
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 Chapter 4 - Page 2
Objective
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 Chapter 4 - Page 4
Approval Policies – Rule Components
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 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)
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Building List Creation Rules - 1 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 (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 Peace’s record from HR. 32. Select approver type of person. 33. Select the search button.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining and Using Approval Groups Chapter 8 - Page 19
34. Select the continue button after AME finds Warren Peace’s 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 Warren’s 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. •
(N) Approvals > (T) Rules
39. Change the transaction type to VGB – Clothing Basket from the list of values and select the continue button. 40. 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. 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. 43. Accept the default system date as the start date. 44. Enter none in the end date. 45. Select the continue button. 46. Select the approval type of “group approvals before the chain of authority”. 47. Select the continue button. 48. In the approval field select “Require pre approvals from XX_VGB GIFT WRAPPING GROUP”. 49. Select the continue button. 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.) 51. Do not select anything in the Ordinary Conditions Line Item Attributes field. 52. Select the continue button to display “Add A Rule – Step 5 “ page.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining and Using Approval Groups 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. 54. Select the continue button. 55. AME will confirm the rule being successfully added. 56. Select the Quit button to return back to the approvals menu page.
Testing the Approval Group Rule 57. Navigate to the Test window. •
(N) Approvals > (T) Test
58. Select the test tab. 59. Change the transaction type to VGB – Clothing Basket from the list of values and select the continue button. 60. In the Choose Test Type page select “Create a test transaction”. 61. Select the continue button. 62. Choose a requestor type of person. 63. Enter morney 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, Mike Morney. 64. Select the continue button. 65. 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 − −
66. Scroll down the page to display the non-mandatory attributes available with the VGB – Clothing Basket transaction type. Note: AME will insert Sarah Bellem’s name as the “TRANSACTION_REQUESTOR_PERSON_ID”. 67. Enter “yes” against the following attributes: XX_VGB_IS_GIFT_WRAPPED XX_VGB_IS_NEW_BASKET − −
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining and Using Approval Groups 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. 69. Scroll to the end of the page and select the view approval list button. 70. Note: In the list of approvers you will see Mr. Warren Peace’s name first in the list followed by Sandy Beach’s name. 71. Select the Change Attribute Values button. 72. Change the value for the XX_VGB_IS_A_NEW_BASKET to “no”. 73. Select the View Approval Process button. 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. 74. Select the Quit button to return to the main menu page.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining and Using Approval Groups Chapter 8 - Page 22
Defining Exception Rules for List Creation Chapter 9
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 1
Defining Exception Rules for List Creation
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 3
Understanding Exception Conditions and Rules
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 5
Understanding Exception Conditions and Rules
Understanding Exception Conditions and Rules 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 6
Approval Policy – Rule Components
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 don’t 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation 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 willvalue define list creation rule, which will use ordinary header condition of the ofabasket as wellexception as the exception condition of the 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 8
Setup Required For Dealing With Exception Rules
Setup Required for Dealing With Exception Rules • 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 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”.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation 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 Geoff’s immediate supervisor.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation 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 •
•
•
•
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 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 11
Solution – Defining Exception Rules for List Creation Defining Conditions Responsibility = AME General Business User, Approvals 1.
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.
3.
Select an ordinary header condition type.
4.
Select the continue button.
5.
In the attribute field select XX_VGB_TOTAL_VALUE_OF_ITEMS_IN_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 200 in the lower limit field. (This is 200 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. 14. Scroll to the end of the conditions page and select Add a Condition button. 15. Select an exception condition type. 16. Select the continue button. 17. In the attribute field select XX_VGB_IS_GIFT_WRAPPED from the list of values. 18. Select the continue button. Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 12
19. Enter “false” as the value of this condition. 20. Select the Create Condition button. 21. AME will confirm the condition being added successfully.
Defining Rules Navigate to the Rules window. •
(N) Approvals > (T) Rules
22. Change the transaction type to VGB – Clothing Basket from the list of values and select the 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. 26. Accept the default system date as the start date. 27. Enter none in the end date. 28. Select the continue button. 29. Select the approval type of “chain of authority based on number of supervisory levels”. 30. Select the continue button. 31. In the approval field select “Require approvals up to the first superior, at most”. 32. Select the continue button. 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.) 34. Do not select anything in the Ordinary Conditions Line Item Attributes field. 35. Select the continue button to display “Add A Rule – Step 5 “ page. 36. Check the ordinary conditions “200 EUR (T) Test
42. Select the test tab. 43. Change the transaction type to VGB – Clothing Basket from the list of values and select the continue button. 44. In the Choose Test Type page select “Create a test transaction”. 45. Select the continue button. 46. Choose a requestor type of person. 47. Enter walker 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, Geoff Walker. 48. Select the continue button. 49. 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 50. Scroll down the page to display the non-mandatory attributes available with the VGB – Clothing Basket transaction type. Note: AME will insert Geoff Walker’s name as the “TRANSACTION_REQUESTOR_PERSON_ID”. 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
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation 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. 56. Scroll to the end of the page and select the view approval list button. Note: In the list of approvers you will see Susan Price’s name first as she is Geoff’s immediate supervisor. 57. Select the Quit button to return to the main menu page.
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 15
Copyright © Oracle Corporation, 2003. All rights reserved.
Defining Exception Rules for List Creation Chapter 9 - Page 16
Effective Dates for Rules and Attributes Chapter 10
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 1
Effective Dates For Rules and Attributes
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 2
Objectives
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 3
Approval Policy - Rule Components
Approval Policy - Rule Components • 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 1 st 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. Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 6
Transaction Date and AME
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes 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
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 9
Setup Required For Defining Rules With Future Effective Dates
Setup Required for Defining Rules With Future Effective Dates • 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 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. Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes 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, Vision’s 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 •
•
•
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 Approval Groups 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 11
Solution – Defining and Using Approval Groups Defining Attributes Responsibility = AME General Business User, Approvals
Defining Approval Groups 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 than “static” in the names Active via Lista field as we are going to define the names of the approvers rather selecting 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 Doe’s record from HR.
9.
Select approver type of person.
10. Select the search button. 11. Select the continue button after AME finds John Doe’s 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 John’s name in the members list.
Defining Rules 14. Navigate to the Rules window.
Copyright © Oracle Corporation, 2003. All rights reserved.
Effective Dates for Rules and Attributes Chapter 10 - Page 12
•
(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. 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) 20. Enter none in the end date. 21. Select the continue button. 22. Select the approval type of “chain of authority includes an approval group”. 23. Select the continue button. 24. In the approval field select “Require approval from XX_VGB_APPROVAL_GROUP_JOHN_DOE”. 25. Select the continue button. 26. Select XX_VGB_NO_OF_ITEMS_IN_BASKET. (XX is replaced with your initials or your terminal number.) 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 conditions “0 500 EUROS AME will check all 4 conditions listed above and if: • Item type - golfing items and • Item name = golf clubs and
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 11
• 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 12
Defining Line Items with Restrictive Evaluations
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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 13
Defining Line Items with Restrictive Evaluations
Defining Line Items with Restrictive Evaluations 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. Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 14
•
•
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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 15
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 performed by the instructor. • 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
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 16
selected using the edit line item button. The approver list generated should show Mike Money and Geoff Walker.
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 17
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 •
•
•
•
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 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 You will define 1 list creation rules, which will use the attributes, conditions and approval types defined above.
Testing You will test the rule created above by creating a test transaction. The requestor will be Sarah Bellem .
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 18
Solution – Line Level Attributes and String Attribute Types 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 line item attribute button.
5.
Select Create New Name button from the Create an Attribute – Step 1 page.
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. 11. Select the Create Attribute button. Note: AME will confirm the creation of the attribute for you. 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 typeblank. of string Leave an theattribute usage field
13. Select the Quit button to return back to the main menu page.
Defining Conditions 14. Navigate to the Conditions window. •
(N) Approvals > (T) Conditions Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 19
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 conditions page and select Add a Condition button. 17. Select an ordinary line item condition type. 18. Select the continue button. 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 25. Navigate to the Rules window. •
(N) Approvals > (T) Rules
26. Change the transaction type to VGB – Clothing Basket from the list of values and select the 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. 30. Accept the default system date as the start date. 31. Enter none in the end date. 32. Select the continue button. 33. Select the approval type of “one job level chain of authority per line item”. 34. Select the continue button. Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 20
35. In the approval field select “Require approvals up to at least level 2”. 36. Select the continue button. 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. 39. Select the continue button to display “Add A Rule – Step 5 “ page. 40. Select the conditions check boxes displayed for Golf Clubs and Golfing Items. 41. Select the continue button to save the rule. 42. AME will confirm the rule being successfully added. 43. Select the Quit button to return back to the approvals menu page.
Testing 44. Navigate to the Test window. •
(N) Approvals > (T) Test
45. Select the test tab. 46. Change the transaction type to VGB – Clothing Basket from the list of values and select the continue button. 47. In the Choose Test Type page select “Create a test transaction”. 48. Select the continue button. 49. Choose a requestor type of person. 50. 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. 51. Select the continue button. 52. 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 − −
53. Scroll down the page to display the non-mandatory attributes available with the VGB – Clothing Basket transaction type. Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 21
Note: AME will insert Sarah Bellem’s name as the “TRANSACTION_REQUESTOR_PERSON_ID”. 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. 63. Select the View Approval Process button. 64. AME displays the rule that it will execute. 65. Select the View Approver List button 66. AME displays the approvers for this rule. 67. Select the Quit button to return back to the Test Type page. 68. Select the Quit button to return to the main menu page.
Copyright © Oracle Corporation, 2003. All rights reserved.
Line Level Attributes and String Attribute Types Chapter 11 - Page 22
Dual Chains of Authority Chapter 12
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 1
Dual Chains Of Authority
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 2
Objective
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 3
Approval Policy – Rule Components
Approval Policy – Rule Components 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority 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 attributes item and item nametype; will be selected here. includes The secondand list the creation rule of will usetype the same approval “chain of authority 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:
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority 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
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 6
Dual Chains of Authority
Dual Chains of Authority
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 7
Dual Chains of Authority Attributes
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 8
Dual Chains Of Authority Rules
Copyright © Oracle Corporation, 2003. All rights reserved.
Dual Chains of Authority Chapter 12 - Page 9
Setup Required For Defining Dual Chain Of Authority Rules
Setup Required For Defining Dual Chain Of Authority Rules The notes following this slide will give 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 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_ (T) Rules
2.
Change the transaction type to VGB – Clothing Basket from the list of values and select the 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.
Select the continue button.
9.
Select the approval type of “chain of authority includes two sub chains, each based on job level”.
10. Select the continue button. 11. In the approval field select “Require approvals at least 1 level up in the first chain.” 12. Select the continue button. 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. . 15. Select the continue button to display “Add A Rule – Step 5 “ page. 16. Select the conditions check box displayed for “0 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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Rule Priorities Chapter 14 - Page 11
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.
Copyright © Oracle Corporation, 2003. All rights reserved.
Rule Priorities Chapter 14 - Page 12
Summary Chapter 15
Copyright © Oracle Corporation, 2003. All rights reserved.
Summary Chapter 15 - Page 1
Using and Maintaining Oracle Approvals Management (AME)
Copyright © Oracle Corporation, 2003. All rights reserved.
Summary Chapter 15 - Page 2
Objectives
Copyright © Oracle Corporation, 2003. All rights reserved.
Summary Chapter 15 - Page 3
Topics Covered
Copyright © Oracle Corporation, 2003. All rights reserved.
Summary Chapter 15 - Page 4
Topics Covered
Copyright © Oracle Corporation, 2003. All rights reserved.
Summary Chapter 15 - Page 5
Copyright © Oracle Corporation, 2003. All rights reserved.
Summary Chapter 15 - Page 6
View more...
Comments
