An Overview of Oracle

TCA Integration

NCOAUG Training Days

March 8th 2004
 Agenda

Overview of TCA Architecture

Customer Hub

Data Governance and Data Management

Review of TCA APIs

Integration Development Tips

Recommendations

Q&A

© 2003 BearingPoint. All rights reserved. 2

Overview of TCA
Architecture
 TCA Model
Trading Community Architecture (TCA) is a structure
designed to support complex trading relationships within
an organization
Features Benefits
Single Source of Information / Ensure Data Consistency
Truth Model Various Customer Bases
Party Concept Ease of Data Maintenance
Common Location / Address Respond to Changing Business
Entity Trends
Ability to Model Complex
Trading Relationships
Dun & Bradstreet Integration

© 2003 BearingPoint. All rights reserved. 4

 TCA Model
The TCA model revolves around the party concept and the
relationships associated with it
Location Party role
Contact
Point
Party site

Person Organization Party

Party relationship
Group Relationship

Participation
Party account role - Competitor
- Partner
Account
Territory
Participates
how
Organization Product

© 2003 BearingPoint. All rights reserved. 5

 Relationship Detail

Location
Party role
Contact
Point
Party site

Person
Party
Organization Party
relationship
Relationship -
Group Relationship
Associates two parties
Participation
Party account role
- Competitor
- Partner

Account
Territory
Participates
how
Organization Product

Has a Role - Specifies the nature of the relationship between parties (e.g. member of,
contact at, married to)

Indicates the nature of the relationship - hierarchy or matrix

Indicates the direction of the relationship - superior or subordinate

Can become a party - a contact becomes a party in itself

© 2003 BearingPoint. All rights reserved. 6

Customer Hub
 Key Customer Data Challenges
Issues
No common definition & hierarchy for
Customer information across
applications
No complete, accurate, single view of
Customer across touchpoints and
regions
Lack of standard data management
and governance policies
Redundant customer records across
different customer systems
© 2003 BearingPoint. All rights reserved.
Impact
Missed opportunities and insight for
effectively upselling/cross-selling
equipment and services to key
customers
Cannot efficiently address customer
service calls
Significant time spent on manual
processes to synchronize customer data
across applications
Cannot report on or analyze business
information by Customer as a
dimension
Cannot view global customer
information
8
 What is a Customer Hub?

An environment that provides for unique identification and consistent

treatment of Customer data across the enterprise

What it is not:

A data warehouse or datamart

A replacement for application databases

© 2003 BearingPoint. All rights reserved. 9

 Key Elements of a Customer Data Hub
Integrate Your Systems
Central Data Store
Integration Services
Packaged Business Processes
Hub to Spoke Mapping
High Volume Import
Change Your Behavior
Customer Master Viewer/Editor
Customer Intelligence and Analytics
© 2003 BearingPoint. All rights reserved.
Manage Your Data
Data Quality Tools
Data Librarian Function & Processes
Single Source Of Truth Record
Integrated Enrichment Capabilities
Security & Privacy Infrastructure
Extended Relationship Management
Custom Applications Platform
10
 Customer Hub Enabled Enterprise
Customer Hub provides for customer data integrity across enterprise applications and contact touchpoints

CRM Partner Portals,

Supplier Systems Extranets Customer
Portals Internal constituent
Knowledge
ERP Systems
Systems example
Rules Engine Workflow
Queuing Publish/ Subscribe
Prioritizing Connection Pooling
Real-time
Analytical
Reports

Administration Duplicate Resolution Business Segmentation

Data Cleansing Intelligence
Data Mgmt. Audit OLAP
Customer DW List Pulls
Archival
Data Validation Hub Data Mining
Tracking &
DM Campaign
Monitoring
Tracking
Translation
Extract, Transport & Load Customer
Synchronization House-Holding
Multilanguage support
Publish/ Subscribe

B2B Mktg
Sales
Financial
Service Mfg
© 2003 BearingPoint. All rights reserved. 11
 Oracle s Customer Hub Applications
Oracle Customer Hub Applications:
Trading Community Architecture (TCA) Oracle s Customer Model
Global repository for name and address information
Oracle Customers Online (OCO)
Web-based module that provides a centralized view of the customer and customer
transactions
Data Quality Management (DQM)/Data Librarian (DL)
Identifies duplicate customer records, merges records, and prevents the creation of
duplicates
Restricts who can create, update, and delete TCA information
Customer Intelligence
Provides customer analytics
D&B Integration
Helps standardize current customer data and create relationships

© 2003 BearingPoint. All rights reserved. 12

Data Governance and Data Management
 Data Governance and Data Management

Data Governance is a combination of people,

process, and technology required to support Data Governance
the ongoing management of the enterprise wide
data that will be centralized a customer HUB
(Oracle TCA). Data Governance has three

Data Stewardship
components supported by enabling data

Data Ownership

Data Quality
management services and data quality tools:
Data Stewardship
Data Ownership
Data Quality

Data Management Processes

Data Management Services
Standardized policies and procedures for
data acquisition, governance, ownership, and
stewardship of Customer Data
Data Quality Tools
Defines priorities and precedence for
creating and maintaining customer data

© 2003 BearingPoint. All rights reserved. 14

 Customer Data Management Considerations

Customer identification, matching, de-duping across all touch points

Common vocabulary to define customer and services
Ownership of customer data - funneled to single point
Stewardship of customer data
Precedence matrix and overwriting rules for data
Common data standards to manage Customer information
On going data quality management Pro-Active, Audits
Validating and managing individual relationships with Company, Site,
Organization, Product, Service
Identifying and managing company hierarchies
Importance of privacy, legal policies and preferences
Globalization & internationalization regulations and policies
Delegated management of customer data external/partner company or
distributed site administration
© 2003 BearingPoint. All rights reserved. 15
Review of TCA API s
 Dun & Bradstreet Integration to TCA
Benefits
Standardize customer master data
Improve ability to manage duplicate records
Ability to access corporate linkage data parent and sub. relationships
Share D&B information across modules (ERP)
Methods to Load Data
Conventional import process using HZ_Party_Interface
Estimated at 2K records per hour
Bulk Import
New with TCA HZ.L patch set
Uses 11 interface tables
Estimated at > 10K records per hour per worker
This method is Oracle s future direction
In either type of load, party records may appear as duplicate data. This is due to
hierarchical relationships created from non-hierarchical relationships. This issue
has been reported to Oracle
© 2003 BearingPoint. All rights reserved. 17
 TCA Data Model
H Z _ C U S T _ A C C T _ S IT E S _ A L L
H Z_C U ST _AC C O U N T _R O LES PK C U S T _ A C C T _ S IT E _ ID
PK C U S T _ A C C O U N T _ R O L E _ ID FK2 C U S T _ A C C O U N T _ ID
FK1 P A R T Y _ S IT E _ ID
FK1 P A R T Y _ ID
H Z _ C U S T _ S IT E _ U S E S _ A L L FK2 C U S T _ A C C O U N T _ ID
FK3 C U S T _ A C C T _ S IT E _ ID
PK S IT E _ U S E _ ID
H Z _ C U S T O M E R _ P R O F IL E S
FK2 C U S T _ A C C T _ S IT E _ ID PK C U S T _ A C C O U N T _ P R O F IL E _ ID

H Z _ P A R T Y _ S IT E S FK1 C U S T _ A C C O U N T _ ID
H Z _ C O N T A C T _ P O IN T S FK2 S IT E _ U S E _ ID
PK P A R T Y _ S IT E _ ID
PK C O N T A C T _ P O IN T _ ID
FK2 P A R T Y _ ID
FK1 P A R T Y _ ID FK1 L O C A T IO N _ ID
FK2 P A R T Y _ S IT E _ ID

H Z _ P A R T Y _ S IT E _ U S E S
HZ_C UST_ACCO U NTS PK P A R T Y _ S IT E _ U S E _ ID
H Z_O RG _CO NTACTS PK C U S T _ A C C O U N T _ ID
FK1 P A R T Y _ S IT E _ ID
PK O R G _ C O N T A C T _ ID FK1 P A R T Y _ ID
FK2 S E L L IN G _ P A R T Y _ ID
FK3 P A R T Y _ S IT E _ ID
FK1 C O N T A C T _ P O IN T _ ID H Z _ L O C A T IO N S
FK2 P A R T Y _ R E L A T IO N S H IP _ ID
PK L O C A T IO N _ ID

H Z_O RG _CO NTACT_RO LES

PK O R G _ C O N T A C T _ R O L E _ ID
H Z _ P E R S O N _ P R O F IL E S
FK1 O R G _ C O N T A C T _ ID PK P E R S O N _ P R O F IL E _ ID

FK1 P A R T Y _ ID
H Z _ P A R T IE S
H Z _ R E L A T IO N S H IP S
PK P A R T Y _ ID H Z _ O R G A N IZ A T IO N _ P R O F IL E S
PK R E L A T IO N S H IP _ ID
PK O R G A N IZ A T IO N _ P R O F IL E _ ID
FK4 O B J E C T _ ID
FK3 S U B J E C T _ ID FK1 P A R T Y _ ID

© 2003 BearingPoint. All rights reserved. 18

 Parties API

Tables Record Structures:

HZ_Parties Party
HZ_Organization_Profiles
Organization
Person
HZ_Person_Profiles
Group

Package
HZ_Party_V2Pub

© 2003 BearingPoint. All rights reserved. 19

 Party Contact API

Tables Record Structures:

HZ_Org_Contacts Org Contact
HZ_Org_Contact_Roles
Org Contract Role
HZ_Parties
HZ_Relationships

Package
HZ_Party_Contact_V2Pub

© 2003 BearingPoint. All rights reserved. 20

 Person Info API

Tables Record Structures:

HZ_Person_Language Person Language

Package
HZ_Person_Info_V2Pub

© 2003 BearingPoint. All rights reserved. 21

 Location Info API

Tables Record Structures:

HZ_Locations Location

Package
HZ_Location_V2Pub

© 2003 BearingPoint. All rights reserved. 22

 Party Site API

Tables Record Structures:

HZ_Party_Sites Party Site
HZ_Party_Site_Uses Party Site Use

Package
HZ_Party_Site_V2Pub

© 2003 BearingPoint. All rights reserved. 23

 Contact Point API

Tables Record Structures:

HZ_Contact_Point Contact Point
EDI
Email
Phone
Telex
Package Web
HZ_Contact_Point_V2Pub
EFT

© 2003 BearingPoint. All rights reserved. 24

 Relationship Type API

Tables Record Structures:

HZ_Relationship_Types Relationship Type

Package
HZ_Relationship_Type_V2Pub

© 2003 BearingPoint. All rights reserved. 25

 Relationship API

Tables Record Structures:

HZ_Relationship Relationship
HZ_Hierarchy_Nodes

Package
HZ_Relationship_V2Pub

© 2003 BearingPoint. All rights reserved. 26

 Classification API

Tables Record Structures:

HZ_Class_Categories Class Category
HZ_Class_Code_Relations Class Code Relation
HZ_Code_Assignments
Code Assignment
Class Category Use
HZ_Class_Category_Uses

Package
HZ_Classification_V2Pub

© 2003 BearingPoint. All rights reserved. 27

 Contact Preference API

Tables Record Structures:

HZ_Contact_Preferences Contact Preference

Package
HZ_Contact_Preference_V2Pub

© 2003 BearingPoint. All rights reserved. 28

 Customer Account API

Tables Record Structures:

HZ_Cust_Accounts Customer Account
HZ_Customer_Profiles Customer Account Relationship
HZ_Cust_Acct_Relate

Package
HZ_Cust_Account_V2Pub

© 2003 BearingPoint. All rights reserved. 29

 Customer Account Site API

Tables Record Structures:

HZ_Cust_Acct_Sites Customer Account Site
HZ_Cust_Site_Uses Customer Account Site Use

Package
HZ_Cust_Account_Site_V2Pub

© 2003 BearingPoint. All rights reserved. 30

 Customer Profile API

Tables Record Structures:

HZ_Customer_Profiles Customer Profile
HZ_Cust_Profile_Amts Customer Profile Amount

Package
HZ_Customer_Profile_V2Pub

© 2003 BearingPoint. All rights reserved. 31

 Customer Account Role API

Tables Record Structures:

HZ_Cust_Account_Roles Customer Account Role
HZ_Role_Responsibility Role Responsibility

Package
HZ_Cust_Account_Role_V2Pub

© 2003 BearingPoint. All rights reserved. 32

Integration Development Tips
 Integration Development Tips
Challenges
Time, resources, and costs
Integration spread across multiple initiatives / projects
Integration architecture has different applications, file formats, and platforms
Business Design
Each interface must have a user owner assigned with roles and responsibilities are clearly defined
Don t forget your business process. Ultimately, each interface is somehow related to a business process
Involve users / sponsors in design reviews
Make sure design is finalized
Always obtain sign-off on design
Processing Rules
Frequency of interface
Maintenance of data objects
What types of transactions will be interfaced
Determine exception handling
How will users be notified of errors?
How will errors be corrected: source system, interface table, or target system?
What exception and audit reports are required?
Sarbanes Oxley considerations

© 2003 BearingPoint. All rights reserved. 34

 Integration Development Tips
Technical Design
Take into account processing rules, especially exception handling
Use standard interface files / APIs
Understand file layouts and required fields
Determine which fields require actual data and which can be generic
Never hard-code values; use lookup tables for mappings
Understand the business transaction relationship between the source and target system

Testing
Plan ahead and make sure test environments with representative data are available
Test all possible conditions including exceptions and negative conditions
Perform thorough technical unit testing before releasing development object to user for review
On larger projects, conduct at least 2 full integration test cycles
Test every scenario you can think of. You ll miss some
Test! Test! and Test!

© 2003 BearingPoint. All rights reserved. 35

Recommendations
 Recommendations
Define clear objectives and metrics for data management

Data cleanliness is relative

Customer Data Management requires cross-functional and global guidance and

coordination

Business and data management rules are encapsulated in an integration and messaging
framework that allows for the uniform view of the customer record across the enterprise

Don t underestimate the business processes during the development -- it s a business-

driven technology solution, not vice-versa!

Provide the ability for 2-way, real-time information sharing between customer systems
without disrupting the format and/or processes of distinct customer functions and
applications

Technologies applied may include EAI tools, web services, custom or batch scripts

Monitor changes in Oracle technology; it can change

© 2003 BearingPoint. All rights reserved. 37

Q&A
 Contact Information

George L. Somogyi Sanjay Garg

Senior Manager Manager
CIT Oracle Practice Technology Integration
BearingPoint BearingPoint
8725 W. Higgins Road 8725 W. Higgins Road
Chicago, IL 60631 Chicago, IL 60631
Tel: +1.773.867.6743 Tel +1.312.961.7196
E-mail:gsomogyi@bearingpoint.net E-mail: sgarg@bearingpoint.net

This document is protected under the copyright laws of the United States and other countries as an unpublished
work. This document contains information that is proprietary and confidential to BearingPoint or its technical
alliance partners, which shall not be disclosed outside or duplicated, used, or disclosed in whole or in part for any
purpose other than to evaluate BearingPoint. Any use or disclosure in whole or in part of this information without
the express written permission of BearingPoint is prohibited. © 2003 BearingPoint (Unpublished). All rights
reserved.

© 2003 BearingPoint. All rights reserved. 39

This document was created with Win2PDF available at http://www.daneprairie.com.
The unregistered version of Win2PDF is for evaluation or non-commercial use only.