PeopleSoft CRM 9.1 Business Object Management PeopleBook

Setting Up CDH Integration

This chapter discusses how to

Set up Installation options.
Set up Smart Search and Duplicate Prevention options.

Setting Up Installation Options

Use the following pages to set up the required installation options.

Pages Used to Set Up CDH Installation Options

Page Name	Definition Name	Navigation	Usage
General Options	RB_INSTALLATION	Set Up CRM, Install, Installation Options, General Options	Activate CDH and Data Librarian options.
CDH Installation Options	RDH_INSTALLATION	Set Up CRM, Install, Oracle CDH Installation	Use this page to select installation options for your PeopleSoft CRM.

Enabling CDH Integration

Access the General Options page (Set Up CRM, Install, Installation Options, General Options).

Ensure that the Oracle Customer Data Hub and Oracle Data Librarian check boxes are selected.

Oracle Customer Data Hub

Select this check box to enable the Oracle Customer Data Hub (CDH) as a licensed product.

This will allow customer data to be synchronized between your PeopleSoft CRM applications and the Oracle Customer Data Hub.

Oracle Data Librarian

Select this check box to enable the Oracle Data Librarian as a licensed product.

This will allow PeopleSoft CRM users to initiate requests to merge duplicate customers: these requests will then be sent to the CDH Data Librarian’s queue for evaluation.

See PeopleSoft CRM 9.1 Application Fundamentals PeopleBook

Setting Up CDH Integration Options

Access the CDH Installation Options page (Set Up CRM, Install, Oracle CDH Installation).

Source System Code

This is the code used by CDH to identify PeopleSoft CRM as a spoke. The default value is set to ECRM.

Enable Smart Search

Select this check box to enable the CDH smart searching functionality as an option on all the advanced Business Object (BO) search screens in CRM. If this check box is not selected, smart searching functionality is not available on advanced BO search screens.

Enable Duplicate Prevention

Select this radio button to allow the duplicate checking functionality of CDH to be invoked from Quick Create pages and Customer Data Model component pages that deal with adding new Business Objects.

Note. When this option is selected, the option for HZ:Enable Duplicate Prevention at party Creation must also be selected within the CDH system.

No Duplicate Prevention

Select this radio button if you do not wish to invoke the duplicate checking functionality of CDH from Quick Create pages and Customer Data Model component pages that deal with adding new Business Objects.

Primary Merge Rule and Secondary Merge Rule

Select the merge rules that describe how to handle the merge of attributes from two Business Objects that are tagged to be merged. These rules will be used to determine how to merge any attributes of objects submitted for a merge request that are not set during the execution of the merge within the CDH system. The Primary Merge Rule is always set so that if an attribute exists on the surviving Business Object, that attribute value will remain after the merge operation.

If the surviving Business Object had no value for an attribute prior to the merge but there was a value for that attribute on the non-surviving Business Object, the post-merge value of the attribute on the surviving Business Object will be taken from the non-surviving Business Object.

The Secondary Merge Rule specifies what should happen if the surviving Business Object had no value for a particular attribute prior to the merge, and two or more Business Objects that will be merged into the first Business Object do have a value for that attribute.

Select the Use the Earliest Attribute Secondary Merge Rule to instruct the system to use the value from the attribute that was created earlier than the corresponding attribute of all other candidates.

Select the Use the Latest Attribute Secondary Merge Rule to instruct the system to use the value from the attribute that was created later than the corresponding attribute of all other candidates.

For example, assume Business Object One had no value for the Ownership attribute, and was about to have Business Object Two and Business Object Three merged into it. If the Ownership attribute from Business Object Two was created on 12/31/2004, and the same attribute from Business Object Three was created on 12/31/2006, after the merge the surviving Business Object One would have the Ownership attribute's value set from Business Object Two if the Use the Earliest Attribute rule was in effect. Similarly, the surviving Business Object One would have the Ownership attribute's value set from Business Object Three if the Use the Latest Attribute rule was in effect.

SCM Integrated Through CDH

If this check box is selected, the Customer Sync Enterprise Integration Points (EIPs) for the CRM-SCM integration are disabled and the Hub is used as the integration mechanism. Select this check box if PeopleSoft FSCM is also a spoke of the Customer Data Hub.

Setting Up Smart Search and Duplicate Prevention

This section provides an overview of match rules and discusses how to:

View CDH-imported match rules.
View match rule details.
View logs for imported match rules.
Establish CDH and CRM field mapping for match rules.
Specify match rule contexts.
Enable smart search on business object searches.
Set up merge processing rules.

Smart Searches and Duplicate Prevention utilize match rules to identify business objects that are similar to those being created or selected by the user.

Understanding Match Rules

Data Quality Match rules are used by the CDH to identify similar or potentially duplicate objects. A set of these rules is delivered as seeded data within the CDH system and as system data in the PeopleSoft CRM application. These system-delivered rules cannot be deleted or modified directly from within the PeopleSoft CRM system. However, if needed, additional rules can be defined in CDH and imported into the PeopleSoft CRM system. Match rules can be viewed on the Data Quality Match Rule – Summary page.

In order to utilize the Oracle Data Quality Match rules within PeopleSoft CRM, each rule is be mapped to one or more Match Rule field mappings. These mappings associate the Oracle application fields to their corresponding PeopleSoft fields. These mappings can be viewed on the Match Rule Mappings page.

Warning! Oracle delivers all necessary field mappings, and it is not necessary to change the mappings unless you have customized the underlying system. Use this component to review the delivered field mappings, but do not make changes to the delivered data without a thorough impact analysis.

Each Match Rule Mapping is associated with a context to specify the conditions under which that mapping is to be used. These rule contexts may be viewed in the Matching Context page.

How Match Rules are Used

Match Rules can be used to help prevent duplicate customer data entries and to help locate existing customer entries by using the following functionality:

Online Duplicate Prevention

When a user creates a new Business Object (BO) in the PeopleSoft CRM system, these match rules are invoked. Any resulting matches that exceed the match threshold are presented to the user as potential duplicates. The user can select one of the potential matches or proceed with the creation. If the override threshold is met or exceeded for a potential match, the user is required to use the matching BO and is prevented from creating a new BO. Online duplicate prevention is defined for Company, Partner, Site, and Person (Contact or Consumer) BOs.
Smart Search

Smart Search capability invokes the match rules to check for similar existing entries when a user searches for a Company, Partner, Site, Person or Customer. This provides two major benefits to the user. First, it allows the user to see entries that may not exactly match all the criteria typed by the user. For example, if the user searched for Thomas Madison but that person had been entered into the system as Tom Madison the CDH Smart Search logic will find the desired person as a possible match for the user to select. Secondly, when the search results are displayed, any results that exceed the match threshold are listed as potential duplicates, and the user can select two or more potential duplicates and submit them to the data librarian for merge evaluation.

Pages Used to Set Up Smart Search and Duplicate Prevention

Page Name	Definition Name	Navigation	Usage
Data Quality Match Rule – Summary	RDH_MATCH_SUM	Set Up CRM, Common Definitions, Customer, Matching, DQM Match Rules Summary, Match Rules Summary	View Match Rules imported from the CDH.
Match Rule Details	RDH_MATCH_RULE_DET	Set Up CRM, Common Definitions, Customer, Matching, DQM Match Rules Summary, Match Rules Summary. Select View Details icon for desired rule in row of Match Rules summary grid.	View details for a Match Rule imported from the CDH.
Data Quality Match Rule – Import Log Summary	RDH_MATCH_SUM	Set Up CRM, Common Definitions, Customer, Matching, DQM Match Rule Summary, Import Log	View the import log for the selected Match Rule.
Match Rule Mapping	RDH_MATCHRULE_MAP	Set Up CRM, Common Definitions, Customer, Matching, Match Rule Field Mapping	Establish the mapping between CRM and CDH fields on a Match Rule.
Matching Context	RDH_MATCH_CONTEXT	Set Up CRM, Common Definitions, Customer, Matching, Matching Context	Establish the context to in which Matching Rules are to be used.
Criteria	RBQ_CRITDFN	Set Up CRM, Common Definitions, Customer, BO Search, Criteria	Specify the advanced search criteria fields and advanced search definition.
Adapter	RBQ_ADPTR	Set Up CRM, Common Definitions, Customer, BO Search, Adapter	Specify the basic search criteria fields.
Data Hub Merge Registry	RDH_MERGE_REG	Set Up CRM, Common Definitions, Customer, Merge Registry, Data Hub Merge Registry	View the Merge Handlers used to process merge information from CDH.

Viewing CDH-Imported Match Rules

Access the Data Quality Match Rule - Summary page (Set Up CRM, Common Definitions, Customer, Matching, DQM Match Rules Summary, Match Rules Summary).

This page displays all the CDH Data Quality Match Rules that have been imported into the PeopleSoft CRM system.

Get All Match Rules	Select this button to import all Data Quality Match Rules from CDH into the PeopleSoft CRM application.
Get Match Rule (Rule ID)	Enter the ID of a CDH Data Quality Match Rule and click the adjacent Go button to import a specific rule from CDH into the PeopleSoft CRM application.

Viewing Match Rule Details

Access the Match Rule Details page (Set Up CRM, Common Definitions, Customer, Matching, DQM Match Rules Summary, Match Rules Summary).

Use this page to view details of the attributes that are associated with a CDH Match Rule.

Override Threshold

This displays the Override Threshold value defined for the rule within the CDH system. Override Thresholds can be defined in CDH for Match Rules used for searching. When a user in the PeopleSoft CRM system tries to create a business object using data that so closely matches an existing entry that the new object's match score would exceed the Override Threshold value, the system forces the user to select one of the existing close matches rather than allowing the new entry to be created.

Note. As delivered, the following four CDH Match Rules have Override Threshold values of 100%: ECRM_SITE_ADD, ECRM_PERSON_ADD, ECRM_COMPANY_ADD, and ECRM_PARTNER_ADD. These rules are used for creation of new business objects from the main CRM CDM components and from the BO Quick Create pages. These values may be adjusted when implementing the system based on business needs.

Update Match Rule

Click this button to update the Match Rule with data from the Oracle CDH system.

Viewing Logs for Imported Match Rules

Access the Data Quality Match Rule - Import Log Summary page (Set Up CRM, Common Definitions, Customer, Matching, DQM Match Rule Summary, Import Log).

Use this page to view details regarding the status of deleted or invalid Match Rules. If a Data Quality Match Rule that is already used in a Match Rule Mapping is changed in the CDH, the corresponding Match Rule Mappings in the PeopleSoft CRM system must be updated to be adjusted for the new changes. This page helps identifies when such changes may be required due to updated CDH Match Rule data.

Establishing CDH and CRM Field Mapping for Match Rules

Access the Match Rule Mapping page (Set Up CRM, Common Definitions, Customer, Matching, Match Rule Field Mapping).

Match Rule

Indicates the CDH Data Quality Match Rule to which the map applies.

Role Type

Indicates the BO Role Type for which the map applies. For example, if a Role Type of Company is used, the Match Rule Mapping will be used in situations in which the Business Object being evaluated also has a Role Type of Company.

See PeopleSoft CRM 9.1 Business Object Management PeopleBook.

Relationship Type

Indicates the BO Relationship Type for which the map applies.

Note. A mapping may only be created for a Role Type or a Relationship Type. You may not associate both a Role Type and a Relationship Type for a single mapping.

Mapping Type

Specifies the type of map that is being created. Valid values are BO Search, Rowset, and Object.

Match Rule Attribute

Lists each CDH Data Quality Match Rule attribute (table/field) used for the map. These are the attributes used to compare two or more entries for similarity and to evaluate whether a new entry might be a duplicate of an existing entry.

Record

Specify the CRM rowset record to be used in the mapping. This column only appears for mappings created with the Mapping Type of Rowset.

Field Name

Specify the CRM rowset field to be used in the mapping. This column only appears for mappings created with the Mapping Type of Rowset.

Property Name

Specify the CRM property to be used in the mapping. The available values will be derived from all the BO properties associated with the selected role type on the page. This column only appears for mappings created with the Mapping Type of Object.

BO Search Field

Indicates the PeopleSoft CRM BO Search field whose value will be compared to the equivalent CDH attribute when checking for duplicate or similar customer data entries. This column only appears for mappings created with the Mapping Type of BO Search.

Specifying Match Rule Contexts

Access the Matching Context page (Set Up CRM, Common Definitions, Customer, Matching, Matching Context).

Use this page to specify contexts in which match rules can be used.

Enabling Smart Search on Business Object Searches

The BO Search - Criteria page and BO Search - Adapter page both contain options that control the Smart Search functionality.

To enable smart search on BO search:

Access the BO Search - Criteria page (Set Up CRM, Common Definitions, Customer, BO Search, Criteria).

Select the Enable Smart Search check box to enable the Smart Search functionality for the associated BO search definition.

Note. The Enable Smart Search button on the BO Search - Criteria page applies only to the specific BO Search definition displayed on the page. The Enable Smart Search button on the CDH Installation Options page controls whether Smart Searching is available in general for the PeopleSoft CRM system.
Access the BO Search - Adapter page (Set Up CRM, Common Definitions, Customer, BO Search, Adapter).

Specify a role type in the Context Role Type field for which this adapter applies. This field will be visible if there is any data in the Matching Context page for the same component specified on the adapter definition. The available role types listed will be limited to those role types specified on the corresponding Matching Context page entry for that component.

Setting Up Merge Processing Rules

Access the Data Hub Merge Registry page (Set Up CRM, Common Definitions, Customer, Merge Registry, Data Hub Merge Registry).

The Data Hub Merge Registry page displays entries that control how PeopleSoft tables are updated upon notification of a duplicate object merge. Use this page to view the post merge processing that must occur to update PeopleSoft data tables in response to a CDH object merge.

Group and Sequence	Numeric values used to order the execution of the code specified in the row's corresponding Application Class Path. Code is executed in ascending Group order using ascending Sequence order within a Group.
Application Class Path	Specifies the Application Class Path where the PeopleCode resides to perform the merge processing updates. For example, if a company with a BO_ID value of 123 was inactivated during a merge because that company was merged into a company entry with a BO_ID value of 456, one type of update required for post-merge processing would be to update the BO_ID value on any transaction table entries that used to have a value of 123 to the new value of 456.
Owner ID	Specifies the owner ID associated with the product that must be selected on the system Installation page in order for the code defined on that row's Application Class Path entry to be invoked. For example, if the Sales check box is not selected on the Installation page, none of the code on the Data Hub Merge Registry page marked with the Owner ID of RSF will be executed. (Technical administrators may view the fields on the INSTALLATION record within the PeopleSoft CRM database to see how licensed products correspond to Owner ID values.)
Notify	Select this check box to send a notification whenever the code specified on that row is executed.
Role Name	When a row's Notify check box is selected, all users with the role specified in the Role Name field will receive the associated notification.

Warning! All required values for the proper execution of post-merge processing are delivered as system data, and should not require any changes. Exercise caution before adding or deleting any rows on this page, and do so only after a thorough analysis of how this will affect the way objects in your PeopleSoft system will be updated. Such changes would normally only be done in response to a code customization.

Source System Code	This is the code used by CDH to identify PeopleSoft CRM as a spoke. The default value is set to ECRM.
Enable Smart Search	Select this check box to enable the CDH smart searching functionality as an option on all the advanced Business Object (BO) search screens in CRM. If this check box is not selected, smart searching functionality is not available on advanced BO search screens.
Enable Duplicate Prevention	Select this radio button to allow the duplicate checking functionality of CDH to be invoked from Quick Create pages and Customer Data Model component pages that deal with adding new Business Objects. Note. When this option is selected, the option for HZ:Enable Duplicate Prevention at party Creation must also be selected within the CDH system.
No Duplicate Prevention	Select this radio button if you do not wish to invoke the duplicate checking functionality of CDH from Quick Create pages and Customer Data Model component pages that deal with adding new Business Objects.
Primary Merge Rule and Secondary Merge Rule	Select the merge rules that describe how to handle the merge of attributes from two Business Objects that are tagged to be merged. These rules will be used to determine how to merge any attributes of objects submitted for a merge request that are not set during the execution of the merge within the CDH system. The Primary Merge Rule is always set so that if an attribute exists on the surviving Business Object, that attribute value will remain after the merge operation. If the surviving Business Object had no value for an attribute prior to the merge but there was a value for that attribute on the non-surviving Business Object, the post-merge value of the attribute on the surviving Business Object will be taken from the non-surviving Business Object. The Secondary Merge Rule specifies what should happen if the surviving Business Object had no value for a particular attribute prior to the merge, and two or more Business Objects that will be merged into the first Business Object do have a value for that attribute. Select the Use the Earliest Attribute Secondary Merge Rule to instruct the system to use the value from the attribute that was created earlier than the corresponding attribute of all other candidates. Select the Use the Latest Attribute Secondary Merge Rule to instruct the system to use the value from the attribute that was created later than the corresponding attribute of all other candidates. For example, assume Business Object One had no value for the Ownership attribute, and was about to have Business Object Two and Business Object Three merged into it. If the Ownership attribute from Business Object Two was created on 12/31/2004, and the same attribute from Business Object Three was created on 12/31/2006, after the merge the surviving Business Object One would have the Ownership attribute's value set from Business Object Two if the Use the Earliest Attribute rule was in effect. Similarly, the surviving Business Object One would have the Ownership attribute's value set from Business Object Three if the Use the Latest Attribute rule was in effect.
SCM Integrated Through CDH	If this check box is selected, the Customer Sync Enterprise Integration Points (EIPs) for the CRM-SCM integration are disabled and the Hub is used as the integration mechanism. Select this check box if PeopleSoft FSCM is also a spoke of the Customer Data Hub.

Match Rule	Indicates the CDH Data Quality Match Rule to which the map applies.
Role Type	Indicates the BO Role Type for which the map applies. For example, if a Role Type of Company is used, the Match Rule Mapping will be used in situations in which the Business Object being evaluated also has a Role Type of Company. See PeopleSoft CRM 9.1 Business Object Management PeopleBook.
Relationship Type	Indicates the BO Relationship Type for which the map applies. Note. A mapping may only be created for a Role Type or a Relationship Type. You may not associate both a Role Type and a Relationship Type for a single mapping.
Mapping Type	Specifies the type of map that is being created. Valid values are BO Search, Rowset, and Object.
Match Rule Attribute	Lists each CDH Data Quality Match Rule attribute (table/field) used for the map. These are the attributes used to compare two or more entries for similarity and to evaluate whether a new entry might be a duplicate of an existing entry.
Record	Specify the CRM rowset record to be used in the mapping. This column only appears for mappings created with the Mapping Type of Rowset.
Field Name	Specify the CRM rowset field to be used in the mapping. This column only appears for mappings created with the Mapping Type of Rowset.
Property Name	Specify the CRM property to be used in the mapping. The available values will be derived from all the BO properties associated with the selected role type on the page. This column only appears for mappings created with the Mapping Type of Object.
BO Search Field	Indicates the PeopleSoft CRM BO Search field whose value will be compared to the equivalent CDH attribute when checking for duplicate or similar customer data entries. This column only appears for mappings created with the Mapping Type of BO Search.