Northern California OAUG Oracle Trading Community Architecture June

Northern California OAUG Oracle Trading Community Architecture June, 2006

Trading Community Architecture WHY EVOLUTION WHAT’S IN R 12 SUMMARY

Trading Community Architecture WHY

To answer some questions Who are my Customers? Who are my Trading Partners? What have they purchased? What business have they done with us? What else can I sell to them? What more can we do with them? Who can I sell to next? How can we improve business with them?

Goals Ÿ For Customer information, bringing ERP and CRM to the same core architecture Ÿ Separating the entity that enters into a relationship from the business relationship itself Ÿ Allowing organizations and people to exist independently of their business relationship within a company Ÿ Sharing of party information across all of the ERP and CRM applications and reducing data redundancy Ÿ Providing complete view of a party and all of its relationships with you, and its relationships with other members of the trading community

Trading Community Architecture EVOLUTION

Evolution on a release scale 1 2 1 i. R 3 1 i. R 1 4 i. R 1 1 D&B Integration Classification Model Online Fuzzy Match TCA Data Model 6 1 i. R 1 Party Merge Public APIs 7 i. R 11 DQM BES Callouts Employee Integration OCO (CO) 10 9 1 1 i. R Web Services SSM ODL (CDL) Bulk Import CPUI Auto-Merge Address Validation CDH

Steps of Evolution Ÿ Started with building a best in class customer data model Ÿ Introduced inbound and outbound interfaces to the data model – Public APIs (Java and PL/SQL), Bulk Import, Event-Subscription Ÿ Focused heavily on building data quality – Fuzzy Match, DQM, Merge, Data Librarian Ÿ Introduced third party integration e. g. with content provider DNB, with address services providers Ÿ Built comprehensive UI to view and maintain customer information – Customers Online. Provided UI components to application products for consistent exposure of customer information – Common Party UI

Steps of Evolution Ÿ Introduced system cross-referencing mechanism – Source System Management Ÿ Provided unlimited extensibility to the model, to capture information specific to your company or your industry Ÿ Built 360 degree transaction viewer, graphical relationship viewer Ÿ Built integration with HRMS, Health. Care, Student System, User Management, B 2 B Gateways Ÿ Worked with product teams to streamline application flows having touch point with customer information

Evolution in 11 i EBS Ÿ Became central person and organization master for majority of applications in EBS Oracle E-Business Suite Application Families* CDM Areas of Responsibility CDM Sales Service Financials HR TCA Enabling Infrastructure Common Party UI, DQM, D&B Integration, APIs TCA Data Model HZ Schema * This diagram depicts only a small subset of the application families that utilize TCA

Campaign to Compensation Business Flows E-Business Suite Applications Ÿ Campaign to Lead Ÿ Marketing Online Ÿ Lead to Opportunity Ÿ Telesales Ÿ Sales Online Ÿ Opportunity to Quote Ÿ Territory Manager Ÿ Opportunity to Forecast Ÿ Quoting Ÿ Quote to Order Ÿ Pricing Ÿ Order to Invoice Ÿ i. Store Ÿ Order Management Ÿ Invoice to Cash Ÿ Accounts Receivable Ÿ Cash to Compensation Ÿ Credit Management Ÿ Incentive Compensation Ÿ Human Resources Ÿ Payroll Ÿ Marketing & Sales Intelligence

Service Request to Resolution Business Flows E-Business Suite Applications Ÿ Call to Resolution Ÿ Teleservice Ÿ Click to Resolution Ÿ Contact Center Ÿ Inbound Call to Depot Repair Ÿ Customer Care Ÿ Inbound Call to Dispatch Ÿ i. Support Ÿ Dispatch to Resolution Ÿ Field Service Ÿ Installed Base Ÿ Scheduling Ÿ Depot Repair

Contract to Renewal Business Flows E-Business Suite Applications Ÿ Contract Creation to Renewal Ÿ Ÿ Contract Usage to Cash Sales Contracts Ÿ Service Contracts Ÿ Accounts Receivable Ÿ Service Intelligence

Evolution in 11 i EBS Ÿ Became central person and organization master for majority of applications in EBS Oracle E-Business Suite Application Families* CDM Sales Service Financials HR TCA Enabling Infrastructure Common Party UI, DQM, D&B Integration, APIs TCA Data Model HZ Schema * This diagram depicts only a small subset of the application families that utilize TCA Others HR HR

Evolution in 11 i EBS …But what about organizations that are in a heterogeneous applications environment? Epiphany Navision Siebel Retek SAP People. Soft Lawson Oracle

Evolution of Customer Data Hub Extended the solution beyond Oracle e-Business Suite…Introduced Customer Data Hub Ÿ Central customer master data store Ÿ Data quality tools run in single instance for increased ROI Siebel Ÿ Platform for custom applications Ÿ Creates enterprise customer data ownership Retek Ÿ Improved customer visibility – Real-time access to all data – 360 degree view of all transactions Lawson Ÿ Lower total cost of ownership – Simplified integration – Reduced maintenance costs Epiphany Navision SAP People. Soft

Trading Community Architecture WHAT’S IN R 12 (This is not a product announcement)

R 12 – SOA Enabling TCA Save Update Create Get Servicebeans/SDOs/Generate Functions Integration Repository (Web Service Provider) Business Object Level APIs and Events Business Objects (DB Objects) V 2 API’s Entity Centric V 2 Business Events Entity Centric Business Object Layer Entity Centric V 2 API’s and Events

R 12 – Integration capabilities Release 11 i Release 12 Integration based on TCA Entities Business Objects based integration Low level entity access Business Object level access Extensive Custom Coding No coding required No middleware integration Out-of-the-box integration to Oracle SOA Suite Integration Components Complete Integration Solution Java & PL/SQL APIs Web Services

R 12 – Supplier Integration Ÿ Supplier organizations are in TCA Ÿ Terms of doing business with the supplier are in Purchasing / Payables Ÿ Supplier organization, address, contact, phone, email etc. are all in TCA Ÿ Employees are already in TCA, Payables using the same employee records in TCA Ÿ New supplier maintenance UI using TCA UI components

R 12 – Shared Services Architecture Ÿ Oracle E-Business Suite introduces new Shared Services Architecture in R 12 Ÿ TCA leverages the new architecture in providing easier maintenance of Account layer information that are operating unit sensitive Ÿ No more changing responsibility to access account information from different operating units

R 12 - What’s in TCA Legal Entity & Intercompany Supplier Customer Student, Faculty Partner & End Customer Patient & Doctor Bank & Branch Contact & User Employee

Trading Community Architecture SUMMARY

The Guy from Australia

What you get from TCA Ÿ Prevent situation like the one we just watched! Ÿ Tools that deploying companies can use to model their customers as they see best for their business Ÿ Architecture that will grow with deploying companies’ requirements Ÿ Features to maintain extremely reliable customer information Ÿ Glue that ties several E-Business Suite flows in a seamless way Ÿ Customer Data Integration solution even if deploying company is not running a single E-Business Suite module Ÿ Platform that can play a key role in your IT landscape for Master Data Management

What you have to do Ÿ Take a close look at how you do business and how your business processes are most efficiently performed Ÿ Ask questions about how you should model customer information e. g. which entities should be modeled as parties, when should you create an account, should you create multiple accounts for some parties, should you create multiple billing sites for an account, should you create account relationships Ÿ Even if you are implementing few modules of E-Business Suite to start with, keep in mind the bigger picture about customer information

Meta. Link Resource Ÿ Oracle Trading Community Architecture – Modeling Customer and Prospect Data : The document talks about answering a set of key questions about your prospect and customer data. This document offers guidance on the order in which these questions should be asked and on how to answer each question given your objectives and business processes. Ÿ Oracle Customer Data Hub Implementation Concepts and Strategies : The purpose of this document is to address the various considerations and decisions that come into play when implementing the Customer Data Hub, and to outline a concrete methodology for successfully implementing the CDH.