Northern California OAUG

Oracle Trading Community Architecture

June, 2006

Trading Community Architecture

WHY EVOLUTION WHATS IN R12

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

D&B Integration Classification Model Online Fuzzy Match TCA Data Model

Party Merge Public APIs

Web Services ODL (CDL) DQM BES Callouts Employee Integration OCO (CO)

SSM CPUI

Bulk Import
Auto-Merge Address Validation CDH

OCO (CO)

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, HealthCare, Student System, User Management, B2B Gateways

Worked with product teams to streamline application flows having

touch point with customer information

Evolution in 11i EBS

Became central person and organization master for majority of applications in EBS
Oracle E-Business Suite Application Families*

CDM

Sales

Service

Financials

HR

CDM Areas of Responsibility

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
Campaign to Lead

E-Business Suite Applications

Marketing Online Telesales Sales Online Territory Manager Quoting Pricing iStore Order Management Accounts Receivable Credit Management Incentive Compensation Human Resources Payroll Marketing & Sales Intelligence

Lead to Opportunity
Opportunity to Quote Opportunity to Forecast Quote to Order Order to Invoice Invoice to Cash Cash to Compensation

Service Request to Resolution

Business Flows
Call to Resolution Click to Resolution

E-Business Suite Applications

Teleservice Contact Center Customer Care iSupport

Inbound Call to Depot Repair Inbound Call to Dispatch

Dispatch to Resolution

Field Service
Installed Base Scheduling Depot Repair

Contract to Renewal
Business Flows
Contract Usage to Cash

E-Business Suite Applications

Sales Contracts Service Contracts Accounts Receivable Service Intelligence

Contract Creation to Renewal

Evolution in 11i EBS

Became central person and organization master for majority of applications in EBS
Oracle E-Business Suite Application Families*

CDM

Sales

Service

Financials

HR

Others HR 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

Evolution in 11i EBS

But what about organizations that are in a heterogeneous applications environment?
Epiphany Siebel Navision

Retek

SAP PeopleSoft Oracle

Lawson

Evolution of Customer Data Hub

Extended the solution beyond Oracle e-Business SuiteIntroduced 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

PeopleSoft

Trading Community Architecture WHATS IN R12

(This is not a product announcement)

R12 SOA Enabling TCA

Servicebeans/SDOs/Generate Functions

Integration Repository (Web Service Provider) Business Object Level APIs and Events

Create

Update

Business Level APIs and Events

Business Objects (DB Objects)
Business Object Layer Entity Centric V2 APIs and Events

V2 APIs
Entity Centric

V2 Business Events
Entity Centric

Save

Get

R12 Integration capabilities

Release 11i
Integration based on TCA Entities

Release 12

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

R12 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

R12 Shared Services Architecture

Oracle E-Business Suite introduces new Shared Services
Architecture in R12 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

R12 - Whats in TCA

Supplier Legal Entity & Intercompany Student, Faculty Partner & End Customer Patient & Doctor Bank & Branch

Customer

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

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