This chapter describes implementation of specific features in Oracle Customer Data Librarian.
This chapter covers the following topics:
Oracle Customer Data Librarian provides many features for you to maintain quality customer data. To use these features, you can set up and administer:
De-Duplication: Set up for identifying and resolving duplicates. See: Setting Up De-Duplication.
Import: Set up for importing data from legacy, third party, and other external sources. See: Setting Up Import.
Party Maintenance: Set up for maintaining parties, including assigning certification levels and setting party status. See: Setting Up Party Maintenance.
Oracle Trading Community Architecture (TCA) features that are used or integrated into Oracle Customer Data Librarian, including:
Data Sharing and Security (DSS): Control the access privileges of users to create, update, or delete customer data.
Third Party Data Integration: Integrate Oracle Customer Data Librarian with D&B so that users can access D&B information to enrich customer information.
Source System Management: Set up for mappings between external source systems and customer data. You can control how source system and user-entered data are displayed, created, and overwritten.
See: Introduction, Oracle Trading Community Architecture Administration Guide.
Most of the TCA administration features are available from the Administration tab. You must have the Oracle Customer Data Librarian Superuser responsibility to access that tab.
Important: For features and functionality that are also in Oracle Customers Online, complete those setup steps as well. See: Feature-Specific Implementation Overview, Oracle Customers Online Implementation Guide.
Related Topics
Oracle Customer Data Librarian allows users to find and resolve duplicates. De-duplication uses Data Quality Management (DQM) for:
Identifying duplicates using Smart Search.
Identifying duplicates using System Duplicate Identification (SDI) batches.
Automatically merging parties identified as definite duplicates as part of creating SDI batches.
Identifying duplicates of organization or person using Integration Services in business object APIs and Create or a Save (create operation) Web services are used.
Searching for specific addresses or relationships, within a single party or a set of duplicate parties, for mapping purposes.
Generating suggested defaults for address mapping.
Generating suggested defaults for relationship mapping.
Much of de-duplication implementation involves setting up DQM for the above purposes.
See: Data Quality Management Overview, Oracle Trading Community Architecture Administration Guide.
To Set Up De-Duplication
Set up Data Quality Management. See: Administering Data Quality Management, Oracle Trading Community Architecture Administration Guide. Make sure to:
Run the DQM Staging program to create the staged schema.
Periodically run the DQM Synchronization program to update the staged schema.
Compile all match rules that you plan to use.
Optionally create match rules for any of the purposes mentioned above for using DQM. Seeded match rules, however, are available. See: Feature-Specific Match Rules, Oracle Trading Community Architecture Reference Guide.
To create match rules to be used for Automerge in System Duplicate Identification batch creation, you must define the match rules as allowed for Automerge.
If you create a new rule for identifying duplicates using Smart Search, the search criteria shown in the user interface will change based on your acquisition and scoring attributes. If you define a match rule set, the superset of all attributes in the set would be the search criteria.
Note: Status and Party Type are always displayed as search criteria for Smart Search, no matter the match rule.
For searching for addresses and relationships to map, the search criteria are always the same. The match rule affects only the scoring. Your custom match rules should have the same scoring attributes as the DL ADDRESS AND RELATIONSHIP SEARCH match rule, which is the seeded match rule for this purpose.
Optionally use the DUP_BATCH_RESTRICTION_LIST Receivables lookup to define the list of attributes that appear in the System Duplicate Identification Batches page. These attributes are used as restriction criteria for creating SDI batches. You can add any attribute from the HZ_PARTIES table to the list. See: Defining Receivables Lookups, Oracle Receivables Implementation Guide.
For address validation information to be displayed when users map duplicate addresses, set up and run address validation at a frequency that fits your needs. See: Setting Up Address Validation, Oracle Trading Community Architecture Administration Guide and Address Validation, Oracle Trading Community Architecture User Guide.
Important: Personalize the Merge Duplicate Addresses page to display the Validation Level column, which is hidden by default.
Define profile options:
Concurrent: Report Access Level
HZ: Create Suggested Merges from Party Merge
HZ: Data Sharing and Security Rules for Data Librarians
HZ: Default Profile Attributes for Merge Mapping
HZ: Default Secondary Profile Attributes for Merge Mapping
HZ: Match Rule for Address Mapping Suggestions
HZ: Match Rule for Address Search
HZ: Match Rule for Identifying Duplicates with Smart Search
HZ: Match Rule for Relationship Mapping Suggestions
HZ: Match Rule for Relationship Search
HZ: Merge Master Party Defaulting
HZ: Number of Workers for DQM Duplicate Identification Program
HZ: Protect Party Modeling Before Merge
HZ: Show Address Mapping Suggestions
HZ: Show Relationship Mapping Suggestions
HZ: Enable DQM for Integration Services
HZ: Match Rule for Organization Services
HZ: Match Rule for Person Services
IMC: Display Notes for Merge Request Mapping
See: Profile Options and Profile Option Categories Overview.
If you have source system data in the TCA Registry and are using Single Source of Truth rules, make sure that source system data can be overwritten in the de-duplication process. Users might not be able to complete certain merges if they do not have full overwrite privileges. See: Single Source of Truth Overview, Oracle Trading Community Architecture Administration Guide.
Create a user overwrite rule that allows update of all attributes. See: Setting Up User Overwrite Rules, Oracle Trading Community Architecture Administration Guide.
Set the HZ: User Overwrite Rule profile option at one or more levels using the rule that you created. If this profile option is set at the responsibility level, make sure that a conflicting or different rule is not set at the user level. See: Source System Management Setup, Oracle Trading Community Architecture Administration Guide.
Related Topics
Setting Up Duplicate Identification, Oracle Customers Online Implementation Guide
De-Duplication Overview, Oracle Customer Data Librarian User Guide
Feature-Specific Implementation Overview
In Oracle Customer Data Librarian, users can import data from external sources by:
Loading source files of data into the import interface tables.
Transferring batches of data from the interface tables into the TCA Registry.
You set up for users to manually perform both parts of the import process. You can also optionally set up the second part to automatically run after the user successfully completes the first part.
To Set Up Import
Set up as you would for TCA Bulk Import. See: Setting Up Bulk Import, Oracle Trading Community Architecture Administration Guide.
Set these profile options:
HZ: Import Batch De-Duplication Match Rule
HZ: Import Registry De-Duplication Match Rule
IMC: Import Preview Processing Results
IMC: Import Run Address Validation
IMC: Import Run Batch De-Duplication
IMC: Import Run Registry Match
See: Profile Options and Profile Option Categories Overview.
Tip: To optionally set up automatic import into the Registry after file load, you must set additional profile options. See: Setting Up Import, Oracle Customers Online Implementation Guide.
Related Topics
Import Overview, Oracle Customer Data Librarian User Guide
Oracle Customer Data Librarian allows users to maintain parties, including assigning certification levels and setting party status. You can:
Set up Data Quality Management for the search of organizations and person to maintain.
Manage the available certification levels and reasons.
To Set Up Party Maintenance
Set up Data Quality Management. See: Administering Data Quality Management, Oracle Trading Community Architecture Administration Guide. Make sure to:
Run the DQM Staging program to create the staged schema.
Periodically run the DQM Synchronization program to update the staged schema.
Compile all match rules that you plan to use.
Optionally create match rules with the Search purpose for the organization or person search. The search criteria shown in the user interface will change based on the acquisition and scoring attributes in the match rule. If you define a match rule set, the superset of all attributes in the set would be the search criteria.
Seeded match rules are also available. See: Seeded Match Rules, Oracle Trading Community Architecture Reference Guide.
Assign the match rule you want to use for search to the appropriate profile option:
Organizations: HZ: Match Rule for Organization Simple Search
Persons: HZ: Match Rule for Person Simple Search
See: Data Librarian Setup.
Optionally add or update certification levels or reasons, to be made available for certification assignment. See: Administering Certification, Oracle Trading Community Architecture Administration Guide.
Related Topics
Maintaining Parties, Oracle Customer Data Librarian User Guide