Overview of MDM Site Hub Overview of Oracle Master Data Management 2 - 1

Overview of Oracle Master Data Management 2 - 2 Objectives After completing this lesson, you should be able to: Understand MDM Site Hub concepts Understand Trading Community Architecture components Overview of Oracle Master Data Management 2 - 2

Overview of Oracle Master Data Management 2 - 3 Agenda Overview of Master Data Management Site Hub Constructing a Data Model Consolidating Data Standardizing Data Synchronizing Updates Overview of Trading Community Architecture (TCA) Summary Overview of Oracle Master Data Management 2 - 3

Overview of Oracle Master Data Management 2 - 4 Overview of Site Hub Site Hub provides tools to: Construct a data model Consolidate data Standardize data Synchronize updates Overview of Master Data Management (MDM) As part of Oracle Master Data Management, Site Hub is a component of the multi-domain MDM footprint. MDM offers standards-based hub products for customer, product, and financial data. Oracle Master Data Management components include: Data Hub: Enables companies to create a single, centralized, enterprise view of their data. The data is continuously synchronized with all source systems, unifying all your operational and analytical systems. This enables capturing future transaction activity against the same record, improving reporting accuracy, productivity, and reliability of analytics. Source Applications: Enables companies to connect many heterogeneous systems to a single source using a middleware application. Trading Community Architecture (TCA) Data Model and Infrastructure: The TCA data model is constructed on the HZ schema, and lying above this schema is an Enabling Infrastructure layer consisting of tools used in cleansing and integrating entities. Overview of Oracle Master Data Management 2 - 4

Constructing a Data Model Site Hub can be used in constructing a data model to answer questions such as how to: Show relationships between data elements and structures Define and analyze the organization’s requirements Enable change according to business requirements Report completely on various criteria View information for targeting and marketing Overview of Oracle Master Data Management 2 - 5

Overview of Oracle Master Data Management 2 - 6 Consolidating Data SH enables you to import information from a variety of sources into a centralized hub including: Third party records Legacy records Consolidating Data Master Data Management enables you to gather data across disparate sources providing processes to aggregate information into a single enterprise source, a data hub.The data hub is a fully integrated data management solution that centralizes, scrubs, enriches, and continuously synchronizes data. There are two main parts to data consolidation capabilities: import utilities and source system management capabilities. You can use: File import utilities to bring in data from flat file sources such as Excel spreadsheets. APIs to perform row-by-row import of data. Extract-Transform-and-Load (ETL) tools for bulk import. Web services. The flexibility offered by MDM enables Site Hub to consolidate heterogeneous databases into a single data hub for business processes or applications to consume this data. All processes use the same data, eliminating any chances of inconsistent or wrong data usage. Overview of Oracle Master Data Management 2 - 6

Overview of Oracle Master Data Management 2 - 7 Standardizing Data After you gather information from sources into your data hub, SH Data Quality provides for: Validating third party information Preventing duplicate data Standardizing Data Information quality is the level of data integrity, that is, the accurateness and completeness of a given set of data. Because data can enter a system in many different ways, it can easily become fragmented, duplicated and inconsistent. Oracle's Data Quality Management engine is used in MDM to cleanse data management flows—preventing the creation of duplicate records and eliminating error corrections. This ensures that the data is consolidated, consistent, and complete. The Data Quality Management embedded engine has configurable rules for duplicate prevention, identification and resolution; data certification tools; address validation; and purge capabilities. Instructor Note Refer participants to the Oracle Trading Community Architecture Reference Guide for detailed information regarding Data Quality Management. Overview of Oracle Master Data Management 2 - 7

Synchronizing Updates MDM Site Hub enables you to: Capture all updates into a central master data hub Push updates into linked applications Synchronizing Updates With a hub managing the master identity, every departmental function can capture transaction activity against the same record. Overview of Oracle Master Data Management 2 - 8

Overview of Oracle Master Data Management 2 - 9 Agenda Overview of Master Data Management Constructing a Data Model Consolidating Data Standardizing Data Synchronizing Updates Overview of Trading Community Architecture (TCA) Summary Overview of Oracle Master Data Management 2 - 9

Overview of Oracle Trading Community Architecture (TCA) TCA is the underlying structure for entity data used by Oracle lines of business. It is an architecture and a model. TCA Data Model - HZ Schema TCA Enabling Infrastructure Common Party UI, DQM, APIs SCM Sales CRM FIN HR Overview of Trading Community Architecture (TCA) Oracle Trading Community Architecture (TCA) is a data model enabling you to manage complex information about the entities including organizations, locations, and the network of hierarchical relationships. TCA is Oracle’s central customer data repository underlying Oracle E-Business Suite applications. It is the master storing entities including sites, partners, prospects, contacts, and employees. The TCA data model is constructed on the HZ schema, and lying above this schema is a layer consisting of tools. TCA was created to facilitate a common view of data from all perspectives, and to separate characteristics in order to limit which users have access to certain types of information. You are able to model each entity within the Trading Community. Modeling is flexible. Information is maintained in the TCA Registry, which is the single source of trading community information for Oracle E-Business Suite applications. These applications and TCA provide user interfaces, batch data entry functionality, and other features for you to view, create, and update registry information. Site Purpose values specify the function used for the site and must have an active status in TCA. Instructor Note Refer participants to the Oracle Trading User’s Guide for detailed information regarding TCA components. Overview of Oracle Master Data Management 2 - 10

TCA Enabling Infrastructure TCA features include: Quality Tools Business Events Bulk Import Address Validation Data Hub Party Components TCA Infra TCA DM EBS TCA Enabling Infrastructure The TCA Enabling Infrastructure layer consists of the following functionality: Data Quality Management—embedded matching engine with rules for duplicate prevention, data certification tools, address validation, and purge capabilities. Business Event System—web services, APIs, open interfaces, and Business Event System callouts to receive updates to the hub. Bulk Import—enables large volumes of data to be imported into the TCA registry. Address Validation. Data Hub—fully integrated data management solution that centralizes, scrubs, and enriches your data. More importantly, data is continuously synchronized with all source systems, unifying all your operational and analytical systems Common Party User Interface Components—entity attributes designed to be reusable, configurable by other E-Business Suite Applications. Overview of Oracle Master Data Management 2 - 11

Overview of Oracle Master Data Management 2 - 12 TCA Party Components TCA provides entities for Site Hub to store and capture such as parties, party sites, party relationships, and contacts. Relationships Sites Parties Contacts TCA Party Components Entities in the TCA Registry consist of logical groups of descriptive, related attributes. For example, the Party entity contains attributes such as name and organization. An entity corresponds to one or more tables in TCA. Attribute values for a party record are stored in the HZ_PARTIES table. TCA party components include: Parties are any entities that can enter into a business relationship, such as people or organizations. Party Sites are the connection between a Party and a Location, that is, geospatial points usually defined by an address. Party Relationships are the connection between party components, such as a person as the contact for an organization, or a business as the division of another organization. Contacts are people who have a relationship with the party. This record consists of contact points such as phone number or email address. Overview of Oracle Master Data Management 2 - 12

Overview of Oracle Master Data Management 2 - 13 Agenda Overview of Master Data Management Constructing a Data Model Consolidating Data Standardizing Data Synchronizing Updates Overview of Trading Community Architecture (TCA) Summary Overview of Oracle Master Data Management 2 - 13

Overview of Oracle Master Data Management 2 - 14 Summary In this module, you should now: Understand Site MDM concepts including data models Understand Trading Community Architecture infrastructure and party components relevant for Site Hub Overview of Oracle Master Data Management 2 - 14