Presentation is loading. Please wait.

Presentation is loading. Please wait.

UC Best-in-Class Approval Rules 10s2 Configurable Approval Rules and Conversion Program © 2011 Ariba, Inc. All rights reserved. Leslie Martensen, Sr. Solutions.

Similar presentations


Presentation on theme: "UC Best-in-Class Approval Rules 10s2 Configurable Approval Rules and Conversion Program © 2011 Ariba, Inc. All rights reserved. Leslie Martensen, Sr. Solutions."— Presentation transcript:

1 UC Best-in-Class Approval Rules 10s2 Configurable Approval Rules and Conversion Program © 2011 Ariba, Inc. All rights reserved. Leslie Martensen, Sr. Solutions Manager, Ariba Dan Gercak, Sr. Manager, On-Demand Downstream Deployment, Ariba

2 Agenda Configurable Approval Rules  Overview  Concepts  Approval Process  Other Rules  Managing Approval Rules Approval Rule Conversion Process  Introductions  Roles and Responsibilities  Conversion Process  Assumptions  Timeline  Next Steps © 2011 Ariba, Inc. All rights reserved. 2

3 Configurable Approval Rules © 2011 Ariba, Inc. All rights reserved. Features  Browser-based configuration of approval rules  Robust management of approval processes  Support for simple and complex rules  Ability for customers to migrate to new rules on their own schedule Benefits  Additional self-service configuration capabilities for customers  Ability to change processes as organizations and policies evolve  Commodity-based requisition rules for P2P and P2O  Serial and parallel approvals in Contract Management  Commodity-based requisition rules for P2P and P2O  Serial and parallel approvals in Contract Management Examples Description Ability for customer administrators to configure approval rules in On Demand 3

4 Configurable Approval Rules © 2011 Ariba, Inc. All rights reserved. Browser-based configuration of approval rules  Customer and functional administrators can configure rules from the Manage drop-down menu  WYSIWYG graphical building of flows and rules  No coding required 4

5 Configurable Approval Rules © 2011 Ariba, Inc. All rights reserved. Robust management of approval processes  Centralized management of all approval processes  Create, edit, copy, activate and delete approval processes  Version control  Check-in/Check-out capabilities 5

6 Configurable Approval Rules Support for simple and complex rules  Serial and parallel flows  Robust set of fields available for rules  Out-of-the-box “system-defined” conditions for faster rule building  Look up approvers or groups based on the state of multiple fields (Approval Lookup Table Rules)  Ability to remove duplicate approvers or the requester based on conditions (Filter Rules)  Add management hierarchy as needed (Chain Rules)  Rules that dictate the ability or action based on the editing of an approvable (Edit Rules)  Support for collaborative requisition approval for P2P, P2O and Services Procurement  Support for adding groups, individual users or lists © 2011 Ariba, Inc. All rights reserved. 6

7 Configurable Approval Rules Technical - Agenda Concepts Approval Process Other Rules Managing Approval Rules © 2011 Ariba, Inc. All rights reserved. 7

8 Configurable Approval Rules Concepts Approvable  An object or document that can be approved  Examples: Requisitions, eForms, Invoice Exceptions Approver  The user that is given the right to approve or deny an approvable  Example: An executive is required to approve all requisitions that are over $5,000. Watcher  A user that is given visibility to the approvable during the approval process (“as an FYI”)  This user cannot approve or deny  Example: IT has requisitioned a new laptop for Sarah, who is watching the progress of approvals. © 2011 Ariba, Inc. All rights reserved. 8

9 Configurable Approval Rules Technical - Agenda Concepts Approval Process  Concepts  Conditions  Actions  Lookup Table Rules Other Rules Managing Approval Rules © 2011 Ariba, Inc. All rights reserved. 9

10 Configurable Approval Rules Approval Process What is an Approval Process?  The set of rules that govern the approval flow for each approvable  Each approvable can only have one active Approval Process © 2011 Ariba, Inc. All rights reserved. 10

11 Configurable Approval Rules Approval Process – Process Diagram © 2011 Ariba, Inc. All rights reserved. An Approval Process is set of one or more interconnected “nodes” Supports both serial and parallel nodes The approval rule(s) for each node are edited here…

12 Configurable Approval Rules Approval Process – Rule Editor © 2011 Ariba, Inc. All rights reserved. 12 Conditions determine if a rule for a node is active or “fired” If the conditions are met, these are the available Actions: Add Approvers, Groups or a Lookup Table Think of it as an IF-THEN statement: IF Condition, THEN Action

13 Configurable Approval Rules Approval Process – Conditions What is a condition?  A condition is an evaluation that determines if an Action needs to be taken for a node  Conditions can reference fields in the approvable or other system-defined conditions (see below)  Each evaluation/condition results in either True or False  Complex combination of conditions can be created Concepts  System-Defined Condition – out-of-the-box conditions that facilitate building rules (i.e. Requester Has a Manager, Any Line Item With Commodity Code)  Compound Condition – Modifies the condition(s) behind it – All of the following must be true (AND) – None of the following is true (NAND) – Any of the following are true (OR) © 2011 Ariba, Inc. All rights reserved. 13

14 Configurable Approval Rules Approval Process – Condition Example © 2011 Ariba, Inc. All rights reserved. Compound Condition – All of the following conditions must be true to be true overall Compound Condition – None of these two child conditions can be true for this compound condition to evaluate as true System-Defined Condition Conditions can compare fields Conditions can compare fields with values 14

15 Configurable Approval Rules Approval Process – Additional Notes on Conditions © 2011 Ariba, Inc. All rights reserved. Conceptually, conditions are evaluated from right-to-left The compound condition “All Are True” with no child conditions evaluates as True Fields available for conditions are limited to the header level. For more complex requirements (e.g., rules on requisition line level), we suggest using Approval Lookup Table Rules 15

16 Configurable Approval Rules Approval Process – Actions © 2011 Ariba, Inc. All rights reserved. What are Actions?  Actions add Approvers and Watchers to the Approval Process flow What Actions are available?  Adding individual approvers/watchers  Adding groups  Adding approvers and groups through the use of a lookup table 16

17 Configurable Approval Rules Approval Process – Actions (Approvers and Groups) © 2011 Ariba, Inc. All rights reserved. 17 Select what type of Approver or Group. These are system-defined. Selecting Add Group…. 17

18 Configurable Approval Rules Approval Process – Actions (Approvers and Groups) © 2011 Ariba, Inc. All rights reserved. Select which group to add to the Approval Process 18

19 Configurable Approval Rules Approval Process – Conditions and Actions © 2011 Ariba, Inc. All rights reserved. Demonstration 19

20 Configurable Approval Rules Approval Process – Lookup Table Rules © 2011 Ariba, Inc. All rights reserved. What are Lookup Table Rules?  Lookup Table rules provide a powerful approach to determine approvers based on a complex set of conditions 20

21 Configurable Approval Rules Approval Process – Lookup Table Rules © 2011 Ariba, Inc. All rights reserved. Select which fields to evaluate (can include line level fields) Multiple operation options available for each field First determine which fields to evaluate 21

22 Configurable Approval Rules Approval Process – Lookup Table Rules © 2011 Ariba, Inc. All rights reserved. 22 Automatically creates table headers Determine what approvers and/or groups to add Then determine what action(s) to take Export the column headers, fill out the values and then upload 22

23 Configurable Approval Rules Approval Process – Lookup Table Rules © 2011 Ariba, Inc. All rights reserved. CommodityCodeAmountIsNotCatalogGroupTooltipRequired 3010000TRUEIT ManagerTRUE 3020000TRUEIT ManagerTRUE 315000FALSEPurchasing Manager TRUE 3115000FALSEPurchasing Manager TRUE CSV File Format 23

24 Configurable Approval Rules Approval Process - Actions © 2011 Ariba, Inc. All rights reserved. Demonstration 24

25 Configurable Approval Rules Approval Process – Lookup Table Rules Line item amounts are aggregated for Lookup Table Rules (different from previous behavior)  Example – Approval rules state that office supplies > $50 requires approval by Purchasing Manager – Requisition with five lines of ink cartridges (different colors), each $29.99. – Old way: no lines are > $50, so the rule doesn’t trigger – New way: total for ink is $149.95, so Purchasing Manager must approve © 2011 Ariba, Inc. All rights reserved. 25

26 Configurable Approval Rules Technical - Agenda Concepts Approval Process Other Rules  Filter Rules  Edit Rules  Chain Rules Manage Approval Rules © 2011 Ariba, Inc. All rights reserved. 26

27 Configurable Approval Rules Filter Rules What are Filter Rules?  Remove approvers/watchers from the Approval Process  Facilitate auto-approvals © 2011 Ariba, Inc. All rights reserved. System-defined actions 27

28 Configurable Approval Rules Edit Rules What are Edit Rules?  Make the approval editable based on specified conditions © 2011 Ariba, Inc. All rights reserved. System-defined actions Condition Builder 28

29 Configurable Approval Rules Approval Process – Chain Rules What are Chain Rules?  Chain rules are secondary rules used to help generate additional approvers for each node  Used to add approvers up a management hierarchy © 2011 Ariba, Inc. All rights reserved. 29

30 Configurable Approval Rules Approval Process – Chain Rules © 2011 Ariba, Inc. All rights reserved. When chaining a rule, a secondary tab for a Chain Rule appears Note that you can only add Approvers and Groups. No Table Rules for Chain Rules Like the Base Rule, you can use the Condition Builder 30

31 Configurable Approval Rules Approval Process – Chain Rules Chain rule conditions should reference an object outside of the approvable (e.g., the requester) – otherwise the Chain Rule would continue to evaluate forever. © 2011 Ariba, Inc. All rights reserved. 31

32 Configurable Approval Rules Approval Process – Other Rules © 2011 Ariba, Inc. All rights reserved. Demonstration 32

33 Yes Configurable Approval Rules How do all these rules work together? © 2011 Ariba, Inc. All rights reserved. 33 Condition True? Step 1: For each node in the graph: Add Approvers/ Groups Is there a Chain Rule? Chain Condition True? Add Additional Approvers/Groups Node Finished No Step 2: Evaluate Filter Rules Edit Rules stand alone, as they determine the ability to edit post-submission (and the result of editing the approvable) rather than determining who can approve/watch

34 Configurable Approval Rules Technical - Agenda Concepts Approval Process Other Rules Manage Approval Rules  Version Control  Testing  Administrators © 2011 Ariba, Inc. All rights reserved. 34

35 Configurable Approval Rules Managing Approval Rules (Version Control) Approval processes can be in one of three states:  Active – In use  Checked In – Latest version of the approval rule, but not being used  Draft – Either being created or edited © 2011 Ariba, Inc. All rights reserved. 35

36 Configurable Approval Rules Managing Approval Rules (Version Control) © 2011 Ariba, Inc. All rights reserved. 36 Editing an Active or Checked-in Approval Process will create a new Draft Checking in a Draft will replace the previous version Note that any time you “edit,” you are creating a draft of the next version

37 Configurable Approval Rules Managing Approval Rules (Version Control) © 2011 Ariba, Inc. All rights reserved. 37 History Tab will give a full list of all rule changes History tab will allow you to revert to an old approval process

38 Configurable Approval Rules Impact on Customers Live customers will continue to use their current rules built by Ariba GSO  Customers can call GSO for help  Customers can migrate on their own  Legacy Rules will be End of Life 18 months after 10s2 GA New customers will only be able to use the new Configurable Approval Rules feature  The legacy best-practices Javascript-based rules will no longer be supported © 2011 Ariba, Inc. All rights reserved. 38

39 UC Approval Rule Conversion Process © 2011 Ariba, Inc. All rights reserved.

40 Agenda Introductions Roles and Responsibilities Conversion Process Assumptions Timeline Next Steps © 2011 Ariba, Inc. All rights reserved. 40

41 Introduction A new Approval Rule Engine was introduced in 10s2, and all rules need to be converted to this new format. This includes Out of the Box rules and custom rules. The document is a tool to help manage expectations, clarify responsibilities and provide an objective basis for assessing conversion service effectiveness. A Kick Off document has been created to support Ariba’s offering to manage and convert customers’ current production Approval Rules to the new configurable Approval Rule Engine. The intended audience for this service is customers who have deployed Ariba On-Demand P2P (single instance or FPC), Invoice Pro, Services Procurement, and/or Procurement Content. This offering is at no cost to the customer. The only anticipated costs during this effort is if the customer requests on-site support – in these situations, the customer will be required to pay for travel expenses. © 2011 Ariba, Inc. All rights reserved. 41

42 Ariba Roles and Responsibilities © 2011 Ariba, Inc. All rights reserved. 42 RoleResponsibilities Conversion Lead  Point of contact for conversion initiative  Provides recommendation to customer for conversion plan  Responsible for internal Ariba project tasks  Participates in the development of the Approval Rule Inventory  Facilitates testing sessions and verification sessions in Test and Production  Coordinates the wrap-up tasks  Provides periodic status updates to customer's leadership  Escalates issues to Customer and within Ariba Conversion Analyst  Participates in the development of the Approval Rule Inventory  Determines the compatibility of the Test environment  Assists in the synching of the Test environment to match Production  Converts the Approval Rules in the Test environment  Participates in the review and verification of the Test environment  Converts the Approval Rules in the Production environment  Participates in the review and verification of the Production environment  Assists in the wrap-up tasks Point of Contact  Manages conversion (issue tracking, status updates, project plan, etc.)  Manages Customer communication  Coordinates activities of Customer resources  Ensures participation of all required Customer resources  Provides timely resolution of any escalated issues  Reviews and verifies the conversion process stages Functional / Technical Participation  Participates in assessment of the current Approval Rules  Tests and verifies the revised new Approval Rules in the Test and the Production environments  Participate in issue resolution as required. As required, the Ariba team will engage with/request for additional Ariba resources as required during the project. This may include specific subject matter experts and technical support. Ariba estimates approximately eight hours per week of customer participation for the duration of the project. This will fluctuate between several personnel participation to part-time activity.

43 Conversion Project Phases and Tasks © 2011 Ariba, Inc. All rights reserved. 43 Project plan guiding Ariba and customer from beginning to end. Issue Resolution process defined and managed. Project Management Conversion/Verification Activities in Prod Conversion/Verification Activities in Test Review of Production Approval Rules Agreement on the Conversion Process Review the current Approval Rules in Production and develop an Inventory of these rules. Based on this review, adjust the Project Plan. Convert the current Approval Rules to the new structure. Customer verifies behavior and approves. Conduct Wrap-Up activities. Assess the Test environment and perform tasks to synch this environment with Production. Convert the current Approval Rules to the new structure. Customer verifies behavior and approves move to Production. Manage and resolve issues as they arise. Obtain Agreement to start this project. Review and establish Project Plan and assign resources from Ariba and customer Agreement on the Conversion Process Conversion / Verification Activities in Test Conversion / Verification Activities in Prod Review of Production Approval Rules Project Management

44 Assumptions © 2011 Ariba, Inc. All rights reserved. This process will not start until Ariba obtains agreement from the Customer on the project. At that point, an Ariba Conversion Lead and Conversion Analyst will be assigned. There will be several key drivers in this project  # of approval rules in place in Production. Since this is a conversion effort of rules, the number will drive effort.  Current status of the Customer Test environment. Unless there is a compelling reason, the Customer’s test environment will be utilized to convert the approval rules prior to Production. There will be an effort to synchronize this with Production. This does not mean all Production data needs to be ported to Test, but the data and structures used in the approval rules needs to be in place.  Customer understanding of the current approval rules. A solid understanding of the current rules will be attained during the Review of Production Approval Rules phase, but Customer knowledge of “end result” and any specific scenarios would be beneficial. 44

45 Assumptions © 2011 Ariba, Inc. All rights reserved. A review of the Test environment will occur before the sync process in the Conversion/Verification Activities in Test phase  Ariba will work with the customer to determine if there are any components (master data, approval rules, other configuration) in Test that are more up to date than in Production.  This could be based on efforts to test new items before moving to Production.  In these cases, Ariba and the customer will agree to what gets moved from Production to Test, as well as what will need to be moved to Production after this phase is completed. Proposed timeline for this effort is four to six weeks. Ariba has in place a focused team to support this initiative. 45

46 Documentation and Training © 2011 Ariba, Inc. All rights reserved. Documentation Ariba Contract Management Release Guide Ariba Procurement Release Guide Ariba Invoice Release Guide Training Configurable Approval Rules Pre-record Configurable Approval Rules https://knowledge.ariba.com/AC_web_page/1,5180,110809,00.html 46

47 Questions © 2011 Ariba, Inc. All rights reserved. 47

48 © 2011 Ariba, Inc. All rights reserved. 48 “Safe Harbor” and Confidential Information Statement This information reflects the status of Ariba solution planning as of January 2011. All such information is the Confidential Information of Ariba (per the contract between our companies), and must not be further disclosed, as stated in the confidentiality clause of that contract. This presentation contains only intended guidance and is not binding upon Ariba to any particular course of business, product strategy, and/or development. Its content is subject to change without notice. Ariba assumes no responsibility for errors or omissions in this document. Ariba shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.

49 UC Best-in-Class Approval Rules 10s2 Configurable Approval Rules and Conversion Program Leslie Martensen, Sr. Solutions Manager, Ariba Dan Gercak, Sr. Manager, On-Demand Downstream Deployment, Ariba © 2011 Ariba, Inc. All rights reserved.


Download ppt "UC Best-in-Class Approval Rules 10s2 Configurable Approval Rules and Conversion Program © 2011 Ariba, Inc. All rights reserved. Leslie Martensen, Sr. Solutions."

Similar presentations


Ads by Google