1. Approvals Management with TCA Hierarchy Ajoy A. Devadawson Oracle Corporation - Consulting

2. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract INTRODUCTION About Oracle Consulting Profile of Project Organization Purpose of CRM - Service 1

3. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Enterprise Architecture Consolidate Supply Chain applications Capacity Planning of organization, people and materials for deployment Customer Units to generate Demand, going away from supply chain functions which reduce effectiveness Focused on Field Service and Mobile Field Service Requests for Supply, Maintenance and Service routed to back end modules Service Request Charges functionality used to route to Order Management module Tracking Customer Items through Install Base 2

4. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Trading Community Architecture (TCA) Data Structure for Customers, Partners, Vendors and their Employees Customer Data Management(CDM) with Customers Online, Customer Data Librarian and Customer Data Hub Organizations, People and Groups as Parties Party Relationships (hierarchical & lateral) for Organizations and People Relationships for Customer Items in Install Base Third party integration with D&B eLocations Spatial Data Integration ( in R12) 3

5. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Integrated View of Customer Model through TCA Customer Customer Accounts Customer Profiles Demographic Data Customer Financial Information Party Relationships Trading Partners Marketing Prospect Leads Target Offers and Promotions Customer Preferences & Behavior Customer Profitability Customer Survey Detail Sales Opportunities Prospect Profiles Quotes Proposals Interaction History Collateral History Account Contacts Service Customer Products Service Requests Service Contracts Warranties Entitlements Interaction History Fulfillment History Order Management Pricing Orders Returns (RMA) Accounts Receivable Invoices Payments Credits Configure/BOM Products Product Configuration Estimates Customization (ECO) 4

6. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract ORGANIZATION Relationships (Hierarchical and Lateral) 5

7. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract PERSON Relationship to Organization 6

8. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract User Management (UMX) Roles 7

9. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Service Request – Field Service 8

10. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Overview of AME Highly extensible approval rules engine Design approval rules without/minimal code Integrated into eBusiness Suite Dynamically regenerate approval list Maintains history of approval status 9

11. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract How does AME work? Notify Next Approver Get Next ApproverEnd (Approved) End (Rejected) Start Approve? Final Approver? - AME - Workflow Yes No Yes 10

12. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Architecture with TCA / ROLES 11

13. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Administrator Dashboard 12

14. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Components of AME Attributes (e.g., UMX_ROLE) Conditions (e.g., UMX_ROLE in (‘XXMC SR Approver A’) Action Types (e.g., ‘Approval-group chain of Authority’, ‘HR Position’) Action Handler ( program to build Approver Group based on Action Type) Approver Groups ( list of approvers who have to approve notifications) Rules ( link Conditions to Approver Groups) 13

15. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Attribute 14

16. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Condition 15

17. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Action Type 16

18. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Approver Group 17

19. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Custom Action Handler The Custom Handler has the following features: Builds Approver Groups of People attached to organizations in TCA Recognizes Roles assigned to People Callable from within AME module, thereby integrating TCA and UMX modules Can climb TCA hierarchy to find next approver who could be in requestor’s org or in a higher level org Can find another approver who is in another org attached to requestor’s org through a relationship 18

20. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract AME Rule 19

21. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Useful References Approvals Management Responsibilities and Setup in AME.B – Metalink Note # 434567.1 FAQ on AME – Note # 431815.1 AME Developer’s / Implementation Guide – Note # 289927.1 TCA Documentation Resources, R12 – Note # 396778.1 Oracle TCA Best Practices – Note # 269124.1 Oracle Customer Data Hub Implementation Concepts and Strategies – Note # 312811.1 Email: ajoy.devadawson@oracle.com 20

22. CONFIDENTIAL: All capabilities are for planning purposes only and may not be used in any contract Q & A 21