This action might not be possible to undo. Are you sure you want to continue?
NCOAUG Training Days March 8th 2004
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.
Overview of TCA Architecture
TCA Model Trading Community Architecture (TCA) is a structure designed to support complex trading relationships within an organization
Single Source of Information / Truth Party Concept Common Location / Address Entity Ability to Model Complex Trading Relationships Dun & Bradstreet Integration
Ensure Data Consistency Model Various Customer Bases Ease of Data Maintenance Respond to Changing Business Trends
© 2003 BearingPoint. All rights reserved.
TCA Model The TCA model revolves around the party concept and the relationships associated with it Location Contact Point Party site Party role Person Party Group Organization Relationship Party relationship Party account role Account Territory Organization Product Participation . 5 .Partner Participates how © 2003 BearingPoint. All rights reserved.Competitor .
hierarchy or matrix Indicates the direction of the relationship . member of.a contact becomes a party in itself © 2003 BearingPoint. married to) Indicates the nature of the relationship .Competitor . 6 .Partner Account Territory Participates how Organization Product Has a Role . All rights reserved.g.Specifies the nature of the relationship between parties (e. contact at.Relationship Detail Location Contact Point Party site Party role Person Party Group Organization Relationship Party relationship Relationship Associates two parties Party account role Participation .superior or subordinate Can become a party .
Customer Hub .
accurate. All rights reserved. single view of Customer across touchpoints and regions Lack of standard data management and governance policies Redundant customer records across different customer systems 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 © 2003 BearingPoint.Key Customer Data Challenges Issues No common definition & hierarchy for Customer information across applications No complete. 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 .
All rights reserved. 10 .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 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 Change Your Behavior Customer Master Viewer/Editor Customer Intelligence and Analytics © 2003 BearingPoint.
Tracking & Monitoring Duplicate Resolution Data Cleansing Audit Archival Data Validation Business Intelligence Customer Hub OLAP Data Mining DW DM List Pulls Campaign Tracking Customer House-Holding Translation Extract. Mktg Sales Service Mfg 11 . Extranets Internal Knowledge Systems Customer constituent example Rules Engine Workflow Queuing Publish/ Subscribe Prioritizing Connection Pooling Real-time Analytical Reports Segmentation Administration Data Mgmt. Transport & Load Synchronization Multilanguage support Publish/ Subscribe B2B Financial © 2003 BearingPoint.Customer Hub Enabled Enterprise Customer Hub provides for customer data integrity across enterprise applications and contact touchpoints Supplier Portals ERP Systems CRM Systems Partner Portals. All rights reserved.
All rights reserved. 12 . update. merges records. and prevents the creation of duplicates Restricts who can create.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. and delete TCA information Customer Intelligence Provides customer analytics D&B Integration Helps standardize current customer data and create relationships © 2003 BearingPoint.
Data Governance and Data Management .
process. ownership.Data Governance and Data Management Data Governance is a combination of people. All rights reserved. 14 . and technology required to support the ongoing management of the enterprise wide data that will be centralized a customer HUB (Oracle TCA). governance. and stewardship of Customer Data Defines priorities and precedence for creating and maintaining customer data Data Management Services Data Quality Tools © 2003 BearingPoint. Data Governance has three components supported by enabling data management services and data quality tools: Data Stewardship Data Ownership Data Quality Data Governance Data Stewardship Data Ownership Data Quality Data Management Processes Standardized policies and procedures for data acquisition.
Organization. legal policies and preferences Globalization & internationalization regulations and policies Delegated management of customer data distributed site administration © 2003 BearingPoint. Product. Service Identifying and managing company hierarchies Importance of privacy.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. Site.Customer Data Management Considerations Customer identification. matching. All rights reserved. external/partner company or 15 . Audits Validating and managing individual relationships with Company. de-duping across all touch points Common vocabulary to define customer and services Ownership of customer data .
Review of TCA API s .
relationships Share D&B information across modules (ERP) 17 . party records may appear as duplicate data. This issue has been reported to Oracle © 2003 BearingPoint. This is due to hierarchical relationships created from non-hierarchical relationships. All rights reserved.Dun & Bradstreet Integration to TCA Benefits Standardize customer master data Improve ability to manage duplicate records Ability to access corporate linkage data 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. parent and sub.
All rights reserved.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 FK1 FK2 FK3 C U S T _ A C C O U N T _ R O L E _ ID P A R T Y _ ID C U S T _ A C C O U N T _ ID C U S T _ A C C T _ S IT E _ ID PK FK2 FK1 C U S T _ A C C T _ S IT E _ ID C U S T _ A C C O U N T _ ID P A R T Y _ S IT E _ ID H Z _ C U S T _ S IT E _ U S E S _ A L L PK FK2 S IT E _ U S E _ ID C U S T _ A C C T _ S IT E _ ID H Z _ C U S T O M E R _ P R O F IL E S PK H Z _ P A R T Y _ S IT E S FK1 FK2 C U S T _ A C C O U N T _ P R O F IL E _ ID C U S T _ A C C O U N T _ ID S IT E _ U S E _ ID H Z _ C O N T A C T _ P O IN T S PK PK FK1 FK2 C O N T A C T _ P O IN T _ ID P A R T Y _ ID P A R T Y _ S IT E _ ID FK2 FK1 P A R T Y _ ID L O C A T IO N _ ID 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 H Z_O RG _CO NTACTS PK FK3 FK1 FK2 O R G _ C O N T A C T _ ID P A R T Y _ S IT E _ ID C O N T A C T _ P O IN T _ ID P A R T Y _ R E L A T IO N S H IP _ ID PK FK1 FK2 C U S T _ A C C O U N T _ ID P A R T Y _ ID S E L L IN G _ P A R T Y _ ID H Z _ L O C A T IO N S PK L O C A T IO N _ ID PK FK1 P A R T Y _ S IT E _ U S E _ ID P A R T Y _ S IT E _ ID H Z_O RG _CO NTACT_RO LES PK FK1 O R G _ C O N T A C T _ R O L E _ ID O R G _ C O N T A C T _ ID H Z _ P E R S O N _ P R O F IL E S PK H Z _ P A R T IE S PK P A R T Y _ ID FK1 P E R S O N _ P R O F IL E _ ID P A R T Y _ ID H Z _ R E L A T IO N S H IP S PK FK4 FK3 R E L A T IO N S H IP _ ID O B J E C T _ ID S U B J E C T _ ID H Z _ O R G A N IZ A T IO N _ P R O F IL E S PK FK1 O R G A N IZ A T IO N _ P R O F IL E _ ID P A R T Y _ ID © 2003 BearingPoint. 18 .
All rights reserved.Parties API Tables HZ_Parties HZ_Organization_Profiles HZ_Person_Profiles Record Structures: Party Organization Person Group Package HZ_Party_V2Pub © 2003 BearingPoint. 19 .
20 . All rights reserved.Party Contact API Tables HZ_Org_Contacts HZ_Org_Contact_Roles HZ_Parties HZ_Relationships Record Structures: Org Contact Org Contract Role Package HZ_Party_Contact_V2Pub © 2003 BearingPoint.
All rights reserved. 21 .Person Info API Tables HZ_Person_Language Record Structures: Person Language Package HZ_Person_Info_V2Pub © 2003 BearingPoint.
All rights reserved. 22 .Location Info API Tables HZ_Locations Record Structures: Location Package HZ_Location_V2Pub © 2003 BearingPoint.
23 . All rights reserved.Party Site API Tables HZ_Party_Sites HZ_Party_Site_Uses Record Structures: Party Site Party Site Use Package HZ_Party_Site_V2Pub © 2003 BearingPoint.
24 .Contact Point API Tables HZ_Contact_Point Package HZ_Contact_Point_V2Pub Record Structures: Contact Point EDI Email Phone Telex Web EFT © 2003 BearingPoint. All rights reserved.
Relationship Type API Tables HZ_Relationship_Types Record Structures: Relationship Type Package HZ_Relationship_Type_V2Pub © 2003 BearingPoint. All rights reserved. 25 .
All rights reserved. 26 .Relationship API Tables HZ_Relationship HZ_Hierarchy_Nodes Record Structures: Relationship Package HZ_Relationship_V2Pub © 2003 BearingPoint.
All rights reserved. 27 .Classification API Tables HZ_Class_Categories HZ_Class_Code_Relations HZ_Code_Assignments HZ_Class_Category_Uses Record Structures: Class Category Class Code Relation Code Assignment Class Category Use Package HZ_Classification_V2Pub © 2003 BearingPoint.
Contact Preference API Tables HZ_Contact_Preferences Record Structures: Contact Preference Package HZ_Contact_Preference_V2Pub © 2003 BearingPoint. 28 . All rights reserved.
29 .Customer Account API Tables HZ_Cust_Accounts HZ_Customer_Profiles HZ_Cust_Acct_Relate Record Structures: Customer Account Customer Account Relationship Package HZ_Cust_Account_V2Pub © 2003 BearingPoint. All rights reserved.
30 .Customer Account Site API Tables HZ_Cust_Acct_Sites HZ_Cust_Site_Uses Record Structures: Customer Account Site Customer Account Site Use Package HZ_Cust_Account_Site_V2Pub © 2003 BearingPoint. All rights reserved.
31 . All rights reserved.Customer Profile API Tables HZ_Customer_Profiles HZ_Cust_Profile_Amts Record Structures: Customer Profile Customer Profile Amount Package HZ_Customer_Profile_V2Pub © 2003 BearingPoint.
Customer Account Role API Tables HZ_Cust_Account_Roles HZ_Role_Responsibility Record Structures: Customer Account Role Role Responsibility Package HZ_Cust_Account_Role_V2Pub © 2003 BearingPoint. 32 . All rights reserved.
Integration Development Tips .
All rights reserved. Ultimately. interface table. 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. 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. and costs Integration spread across multiple initiatives / projects Integration architecture has different applications. 34 . file formats.Integration Development Tips Challenges Time. or target system? What exception and audit reports are required? Sarbanes Oxley considerations © 2003 BearingPoint. resources.
Integration Development Tips Technical Design Take into account processing rules. 35 . 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. 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. All rights reserved.
web services. 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. All rights reserved. custom or batch scripts Monitor changes in Oracle technology.it s a businessdriven technology solution. not vice-versa! Provide the ability for 2-way.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 can change © 2003 BearingPoint. 37 .
used. This document contains information that is proprietary and confidential to BearingPoint or its technical alliance partners. 39 . Higgins Road Chicago. © 2003 BearingPoint. Higgins Road Chicago.961. All rights reserved.net Sanjay Garg Manager Technology Integration BearingPoint 8725 W.773. © 2003 BearingPoint (Unpublished). All rights reserved.net This document is protected under the copyright laws of the United States and other countries as an unpublished work. IL 60631 Tel: +1.Contact Information George L. IL 60631 Tel +1. Any use or disclosure in whole or in part of this information without the express written permission of BearingPoint is prohibited. or disclosed in whole or in part for any purpose other than to evaluate BearingPoint.7196 E-mail: sgarg@bearingpoint. which shall not be disclosed outside or duplicated. Somogyi Senior Manager CIT Oracle Practice BearingPoint 8725 W.6743 E-mail:email@example.com.
daneprairie.com. The unregistered version of Win2PDF is for evaluation or non-commercial use only. .This document was created with Win2PDF available at http://www.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.