Oracle® Fusion Applications Customer Data Management Implementation Guide 11g Release 1 (11.1.1.5.0) Part Number E20433-01

Contents

Previous

Next

26 Define Customer Hub Configuration

This chapter contains the following:

Manage Customer Hub Profile Options

Manage Agreement Rules

Enter Merge Request

Manage Customer Hub Profile Options

Customer Hub Profile Options: Explained

The Customer Hub profile options provide data access and processing options related to data governance, duplicate identification processes, data cleansing processes, and duplicate resolution requests.

Navigate to Manage Customer Hub Profile Options page using the Setup and Maintenance option on the Tools menu to configure the following profile options:

• Address Cleansing Configuration

• Data Cleansing Process Batch Size

• Resolution Request Type Default

• Duplicate Identification Organization Configuration

• Duplicate Identification Person Configuration

• Duplicate Identification Process Batch Size

• User Merge Requests

Address Cleansing Configuration

Specify the data quality address cleansing configuration used by the data cleansing process.

Default value: BT_LOC_CLEANSE

Data Cleansing Process Batch Size

Control the transaction batch size for the data cleansing process. Set this value based on available system resources. Set this value based on available system resources.

Default value: 100

Resolution Request Type Default

Specify the default request type value for duplicate resolution requests.

Default value: Merge

Duplicate Identification Organization Configuration

Specify the data quality organization match configuration used by the duplicate identification process.

Default value: BT_ORG_DUP_BASIC

Duplicate Identification Person Configuration

Specify the data quality person match configuration used by the duplicate identification process.

Default value: BT_PERSON_DUP_BASIC

Duplicate Identification Process Batch Size

Control the transaction batch size for the duplicate identification process. The value is used to chunk records in the batch and process each chunk in a loop as a separate transaction.

Default value: 100

User Merge Requests

Specify the processing of merge requests, such as, process without approval and approval needed. The different values of this profile option are explained below.

• Allow Processing Without Approval: If the User Merge Requests profile option is set to this value, user merge requests are processed immediately without approval by Data Steward.

• Process Subject to Approval: If the User Merge Requests profile option is set to this value, user merge requests are entered for review by Data Steward, who can decide to process them or not.

• Unspecified (NULL): This default values of the User Merge Requests profile option indicates that the Customer Hub is not configured and that user merge requests can be processed immediately without the need for Data Steward approval.

Manage Agreement Rules

Agreement Rules: Explained

An agreement rule is a collection of patterns and conditions that are defined to determine whether a merge request should be vetoed by the application or not. Merge requests that violate these rules are either rejected or end in error.

Agreement rules let you check a merge request for any veto conditions that can prevent a merge from occurring. These rules save resources and time by obviating the need to review merge request to prevent undesired merge from being processed. Besides, agreement rules prompt you to consider alternative duplicate resolution mechanism such as linking.

Agreement rule can be of the following two types:

• Predefined

• User-defined

Predefined Agreement Rules

These are agreement rules that are predefined in the application. You can only view the predefined agreement rules.

The following table describes the predefined agreement rules for the Oracle Fusion Trading Community Hub. Merge requests that violate these rules are automatically rejected.

User-defined Agreement Rules

These are additional agreement rules that you can define to determine whether a merge request should be vetoed by the application. You can create, view, update, and delete user-defined agreement rules.

Defining Agreement Rules: Worked Example

This example demonstrates how to create user-defined agreement rules that you can use to prevent a merge request from being processed.

Agreement rules are collections of patterns and conditions that are defined to determine whether a merge request should be vetoed by the application or not. Perform the following tasks to define agreement rules:

• Select the relevant agreement rules dictionary

• Add a new agreement rule

For more information on agreement rules, see Oracle Fusion Middleware User's Guide for Oracle Business Rules on Oracle Technology Network at http://www.oracle.com/technetwork.

Select Agreement Rules Dictionary

An agreement rules dictionary is a collection of predefined terms and attributes for which agreement rules can be defined. Use the following steps to select the relevant agreement rules dictionary:

1. Navigate to Manage Agreement Rules: Define Dictionary page as follows: Set Up Tasks - Manage Agreement Rules - Define Dictionary
2. Select the relevant agreement rules dictionary from the Select Dictionary drop down list and click Load to load its predefined terms.
3. Select Visible for the terms and term attributes that you want to be available when defining rules later on in the flow.
4. Click Save or Save and Close.

Add a New Agreement Rule

1. Navigate to Manage Agreement Rules: Define Rules page.
2. Add a new rule and provide a rule name.
3. Click on Define Pattern.
4. In the Justification Reason, enter the reason for creating the agreement rule.
5. In the Justification Area enter the scope of the agreement rule.
6. Add a new pattern and complete the fields, using the sample information provided in this table. Use the default values except where indicated. Note that the relation is always AND between patterns and cannot be edited.

   Pattern	Dictionary Term	Term Alias	Relation
   for each case where	PersonPartyVO	Person	AND
   for each case where	OrganizationPartyVO	NonmasterParty	AND
   there is a case where	PartyUsageAssignmentVO	PartyUsageAssignment	AND

   
   
7. To define term conditions for each pattern defined, select the pattern in the Patterns table and navigate to the Conditions table underneath.
8. Add a new condition and complete the fields using the sample information provided in this table. Use the default values except where indicated.

   Term Attribute	Operator	Value	Relation
   Person.PartyNumber - missing PartyNumber	is not	1234	AND
   NonmasterParty.MergeType	=	Nonmaster	AND
   UsageAssignment.PartyUsageCode	=	HR_APPLICANT	AND

   
   
9. Click Save or Save and Close.
10. Click Submit.

Enter Merge Request

Manual Merge: Explained

Manual merge involves selection of duplicate records directly by the user of a merge functionality consuming application. Examples of such applications include Oracle Fusion Sales and Receivables.

Manual merge is unlike the system merge in which duplicates are selected automatically using a matching configuration. Another difference is that while only two records can be merged as part of manual merge multiple records can be merged as part of system merge.

Manually merge the two records that you think are duplicates as in one of the following two ways:

• Immediate manual merge

• Deferred manual merge

Immediate Manual Merge

Involves specification of one of the two duplicate records as the master record for an immediate merge. In an immediate merge, while you can specify some of the attributes from individual records to be mapped to the master record, other attributes are automatically transferred.

Deferred Manual Merge

Involves submission of merge request to be reviewed and processed later by a data steward.

Merging Records Manually: Worked Example

This example demonstrates how the business user of a merge functionality consuming application, such as Oracle Fusion Sales or Receivables, can merge manually two duplicate records. This example illustrates only the generic process for merging records manually from the Enter Merge Request task in the Define Customer Hub Configuration central setup task list. Alternatively, as the business user of a merge functionality consuming application, you can merge two records that you think are duplicate from your own application UI pages that you use to manage customer information.

Merging records manually involves the following tasks:

• Identifying duplicate records

• Selecting the master and duplicate records

• Submitting the merge

Identifying Duplicate Records

1. Navigate to the Search and Select: Record to Merge page as follows: Set Up Tasks Enter Merge Request Search and Select: Record to Merge.
2. To search and select the record to be merged, complete the search criteria using the sample information provided in the given table. Use the default values except where indicated.

   Name	Registry ID (Optional)
   John	15918

   
   
3. Click Search.
4. From the search results, select the first record to be merged.
5. Select Merge Record from the Actions menu

Selecting the Master and Duplicate Records

1. In the Merge secondary window, specify the selected record either as master or duplicate.
2. To select the second (master or duplicate) record to be merged, in the Party Picker enter the sample information provided in the given table. Use the default values except where indicated.

   Name	Registry ID (Optional)
   John	10854

   
   
3. Click Search.

Submitting the Merge

1. On the Map Profile Attributes page, specify the attributes from each of the two records, such as name and gender, that should be mapped to the master record. Any child entities, such as addresses, accounts, account addresses, relationships, and contact points, are transferred to the master record.
2. Click Submit. The merge happens immediately if the data governance profile: User merge requests is set to Allow Processing Without Approval. If the profile is set to Process Subject to Approval, the merge is reviewed and processed later by a data steward.

Previous Next

Copyright ©  2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

Contents Contact Us