11Resolve Duplicates

This chapter contains the following:

You create a duplicate resolution request to resolve potential duplicates in the database.

Depending on your business scenarios, you may create duplicate resolution requests using one of the following options:

  • Create and Process Generic Resolution Requests.

  • Create Duplicate Resolution Requests Manually.

  • Create Duplicate Resolution Requests during the Duplicate Identification Flow.

Create and Process Generic Resolution Requests

You can choose to create a generic duplicate resolution request when not clear whether you want to merge or link the duplicate parties. Specifying a generic resolution request lets you make the merge or link decision later. You have the option of creating generic duplicate resolution requests while:

  • Creating duplicate identification batches by selecting the Create Duplicate Resolution Request as the Automatic Processing option on the Create Duplicate Identification Batch page.

  • Reviewing duplicate sets and creating single requests for each duplicate set on the Duplicate Identification Batch details page.

  • Creating a duplicate resolution request manually for confirmed duplicates on the Create Resolution Request UI page.

You can review these generic resolution requests on the Duplicate Resolution work area and complete processing them by creating duplicate resolution requests of the type merge or link. For more information, see the How You Process Duplicate Resolution Requests topic.

Create Duplicate Resolution Requests Manually

When you're sure that two or more records are confirmed duplicates, you can decide to create a duplicate resolution request manually using the following steps:

  1. Navigate to the Duplicate Resolution work area as follows: Navigator > Customer Date Management > Duplicate Resolution.

  2. Click Tasks and then click Create Resolution Request.

  3. Search for the records that you want to merge, link, or test merge. For example, select the Party Type as Person and enter the Name as John, and click Search.

  4. Select two or more duplicate records using the Shift or Control key.

  5. Click Actions > Create Request.

  6. Enter a name for the request in the Create Request: Select Type dialog.

  7. Select the request type as Generic, Merge, Link, or Test Merge. You can also select the Master Record if needed.

  8. Click OK.

Create Duplicate Resolution Requests during the Duplicate Identification Flow

You create a duplicate identification batch in the Duplicate Identification work area to identify potential duplicates in the database.

As part of the duplicate identification batch creation flow, you have the option of specifying a duplicate resolution request of an appropriate type, such as merge, link or generic, to resolve the identified duplicates. You can also create a duplicate resolution request of type Test Merge to test the merge request configuration without changing your application data. This test option helps you fine-tune your merge request configurations such as survivorship rules and agreement rules.

You can resolve duplicates by creating a duplicate resolution request to either merge or link the potential duplicate records. The type of request that you select determines how these duplicate records are handled after resolution. If not clear whether you want to merge or link the duplicate records, then you can select a Generic resolution request to make this decision later.

Test Merge

You can create a duplicate resolution request of type Test Merge to test your merge request configuration, such as survivorship rules and agreement rules, without:

  • Changing the application data

  • Depending upon Run Request Dispatcher Job task to review merge results

This helps you to get immediate feedback on the behavior of your merge configuration. After the test merge request is complete, you can drill down into the test resolution request to examine the results of the merge. You can also choose the override flow for the merge request to inspect the merge behavior in complete detail.

Merge Request

You create a merge duplicate resolution request to combine duplicate records into one new master record. The master record is also called survivor record. After the merge request is completed, all duplicate records are deleted from the data registry and you can update only the master record. The duplicate records that are deleted are also called victim records. Note that merge supports transfer of attachments from duplicate records to master record.

Link Request

You create a link request to associate the duplicate records. The linked records are treated as unique records in the data registry, and have their own unique identifiers.

While creating the request, you define one of the records as the master record. The resolution process marks and links the other records to the master record, and marks them as duplicates.

You can review and process generic duplicate resolution requests in new status in the Duplicate Resolution work area. As part of processing these requests, you can:

  • Choose to submit or reject them.

  • Decide the duplicate resolution request type, merge or link, based on whether you want to merge or link the duplicate records.

You can create generic duplicate resolution requests while:

  • Create duplicate identification batches by selecting the Create Duplicate Resolution Request as the Automatic Processing option on the Create Duplicate Identification Batch page. Review duplicate sets and creating single requests for each duplicate set on the Duplicate Identification Batch details page.

  • Create a duplicate resolution request manually for confirmed duplicates on the Create Resolution Request UI page.

Keep in mind that you can only process generic resolution requests with "New" status. The option to process resolution request is disabled when the resolution request status isn't new or the type is merge or link. A request dispatcher is run periodically for pending requests, and it sets the status of pending requests to New. You can also request your administrator to run the Run Request Dispatch Job from the Setup and Maintenance area to set the status of the pending requests to New.

Note: A setup user can access the Run Request Dispatch Job task in the Setup and Maintenance work area, using the following:
  • Offering: Customer Data Management

  • Functional Area: Customer Hub

  • Task: Run Request Dispatch Job

You can process a duplicate resolution request using these steps:

  • Select the duplicate resolution request to process.

  • Select the duplicate resolution request type.

  • Manage the duplicate set.

Note: Use the Purge Duplicate Resolution Data scheduled process to purge the duplicate resolution data such as resolution logs and to delete duplicate resolution batches and requests. You can schedule this process from the Scheduled Processes work area. You can access this work area as follows: Navigator > Tools > Scheduled Processes. Similarly, you can purge merged records using the Manage Party Purge Activities scheduled process. If you purge merged records, the victim records of the merge request are purged too.

Select Duplicate Resolution Request

  1. Navigate to the Duplicate Resolution work area.

  2. Select a new generic duplicate resolution request.

Select Duplicate Resolution Request Type

  1. Click the Process option on the Actions menu on the Duplicate Resolution work area.

  2. On the Select Type of Request page, select the duplicate resolution request type as:

    • Merge - to combine duplicate records

    • Link - to join duplicate records with the master record

    • Generic - to postpone your decision of merging or linking of records to a later stage

    • Test Merge - to test the merge request configuration without modifying your application data

Manage Duplicate Sets

  1. As appropriate, mark a record as nonduplicate, set as master a record other than the default master record, remove records that you don't want to include in the resolution request.

  2. Submit the duplicate set, as appropriate, as merge or link requests for resolution.

Duplicate Resolution Request Statuses

You can get detailed reasons for the rejection or failure of a duplicate resolution request from it's status.

You can use the status to correct data or system errors, and resubmit a resolution request with the updated data for processing. For more information, see Configuring the Diagnostic Testing Framework for Normal Operation, Oracle Fusion Applications Administrator's Guide 11g Release 1 (11.1.1.5).

The request status check uses the resolution request ID of the duplicated resolution request as an input parameter to check the request status. The duplicate resolution request status can be Rejected, Error, Completed, or Pending. The check result also includes the reasons for the status.

You can select one or more merge requests that are in new, error, or rejected statuses and change their status to pending by clicking Action > Reset on the Duplicate Resolution page. However, you can't change the status of a merge request that's in completed status.

Let's have a look at the process to merge records for resolving duplicates.

Suppose you have created a merge request. Your request may undergo some or all of the following processing stages before the merge is performed. In this process flow, we assume that notifications are turned on. For more information about turning on notifications for merge requests, see the Related Topics section.

  • First the survivorship rules are used to determine the master record for the merge.

  • After this, the agreement rule check is performed to verify if the merge request is violating any veto conditions. If the agreement rule check succeeds then a check is performed to determine if system mapping must be overridden or not. If the agreement rule check fails, then the merge request is rejected and a rejection notification is sent to the initiator.

  • However, a rejected merge request can also be restored in which case a new merge request is created.

  • If system mapping is overridden then the new mapping is stored before the merge request can be submitted. After the merge request is submitted, the actual merge is performed.

  • If the merge completes successfully then a completion notification is sent to the initiator and the submitter. If the merge fails then an error notification is sent to the initiator and the submitter.

Note: Use the Purge Duplicate Resolution Data scheduled process to purge the duplicate resolution data such as resolution logs and to delete duplicate resolution batches and requests. You can schedule this process from the Scheduled Processes work area. You can access this work area as follows: Navigator > Tools > Scheduled Processes.

Let's look at the following figure that illustrates the merge process flow.

Merge process flow chart

Merge Request Creation Options

A merge request is created as a result of one of the following:

  • The batch duplicate identification process creates a duplicate resolution request automatically for each identified duplicate set.

  • A data steward or another user creates a merge request and submits the request through the Create Resolution Request UI page or through the Accounts or Contact UI page.

  • A data steward or another user creates a merge request for processing a generic resolution request on the Duplicate Resolution work area.

  • You can create a test merge request, examine the results, modify the test merge configuration multiple times until you're satisfied with the merge results, and then create a merge request as per your requirements.

  • A bulk or file-based import process creates a merge request.

Note: You can also use the duplicate resolution request web service to create merge requests.

List of Merge Request Statuses

Your merge request may be in different statuses depending on its stage of processing.

This table lists the possible statuses of a merge request.

Status Description

Pending

All merge requests, and generic duplicate resolution requests, are created with the status as Pending. The requests with pending status require review by a data steward.

New

The request dispatcher is run periodically for pending requests, and sets status of pending requests to New. When the request dispatcher is run, the application selects the master record and attributes based on the survivorship rules, and runs the agreement rule check for the request.

Submitted

This status indicates that the merge request has been submitted for processing. You can also create merge requests with the status as Submitted to process the request without data steward intervention.

Rejected

This status indicates that the merge request is rejected by the data steward or by the process for agreement rule violations. You can restore a rejected merge request.

Error

This status indicates the request has failed because one or more records can't be processed.

Completed

This status indicates that the request has been processed successfully.

How You Select Master and Records to Merge

You can review new merge requests to:

  • Select the master record

  • Mark records as nonduplicates

  • Remove records from the duplicate set to avoid merging them

The merge process selects the master record based on set master rules, if survivorship rules are active. However, you can select to review and override system settings.

When to Override System Mapping

You can override system mappings, during the merge request review, if the system mapping of the request doesn't meet your requirements. You can select the accounts, account addresses, and the relationships that should be merged, transferred, or removed.

Merge Request Related Notifications

You can enable or disable notifications to notify the status of merge requests to interested parties. You can choose to enable notifications while you're creating a duplicate identification batch or while processing individual duplicate resolution requests. For more information about creating a duplicate identification batch, see Create Duplicate Identification Batches and Define Subset Rules Related Topics section. To receive notifications for individual duplicate resolution requests, select the request and click Actions > Notify in the Duplicate Resolution work area.

The merge process sends the following related notifications:

  • Rejection: This notification is sent to the merge request's initiator, such as a business user, salesperson, or administrator. You can restore and resubmit a rejected merge request, by selecting a different master record or by removing some records from the batch.

  • Error: This notification is sent to the merge request's initiator and submitter. The notification indicates that the merge request has errors and can't be processed.

  • Completion: This notification is sent to the initiator and the assignee of the merge process. The process merges duplicate records and updates the record hierarchies. The notifications include information such as the master and duplicate records.

After receiving the completion notification, the request initiator and assignee can:

  • Verify if the updated hierarchies are correct in the Manage Hierarchies work area.

  • Optionally, make the necessary edits to the updated hierarchies.

You can override system mapping for merge requests by manually modifying it. To manually modify system mapping, you must select the master record and its associated attributes, and then specify the resolution for the child entity conflicts and errors. You can resolve child entity conflicts and errors by merging, transferring, or removing the record attributes.

You can override system mapping using these steps:

  1. Navigate to the Duplicate Resolution work area as follows: Navigator > Customer Data Management > Duplicate Resolution.

  2. Select the duplicate resolution request for which you want to override system mappings and drill down through the request ID to the Review Merge Request page.

    Note: You can override system mappings only for those merge requests that are in New status, which indicates that the request is open for review and processing. The status depends on the following:
    • The merge request isn't an auto-merge request and the profile option ZCH_USER_MERGE_REQUESTS is set to Process Subject to Approval. For more information about this profile option, see Customer Hub Profile Options topic listed in the Related Links section.

    • Your administrator has run the Run Request Dispatch Job from the Setup and Maintenance area to change the merge request status from Pending to New. A request dispatcher is run periodically for pending merge requests, and sets the status of pending requests to New. You can also request your administrator to run the Run Request Dispatch Job from the Setup and Maintenance area to set the status of the pending requests to new. A setup user can access this task in the Setup and Maintenance work area, using the following:

      • Offering: Customer Data Management

      • Functional Area: Customer Hub

      • Task: Run Request Dispatch Job

  3. Click Override on the Review Merge Request page to view the Override System Mapping: Select Master Record page.

  4. In the duplicate set on the page, select the record that you want to make the master and click Set Master.

    Optionally, you can also remove records from the duplicate set to prevent them from being merged. You can also mark the removed record as a nonduplicate to exclude it from all the subsequent merge requests.

  5. Click Next to navigate to the Override System Mapping: Map Profile Attributes page.

  6. Select a value from any of the duplicate records for each profile attribute to be retained in the master record.

    If the number of duplicate records is five or less than five, you can select the value from the record columns. If the number of duplicate records is greater than five, you can select the value from the value choice list. In the profile attribute value choice list, you can hover over the value to see the attribute value's record. This helps you associate the correct value with the master record. You can also manually enter a new value in the Final Value column for an attribute.

  7. On the Override System Mapping: Map Entities page, you can merge two or more entities into a single entity. You can also remove merge entities, such as addresses, from the merge processes by clicking the Remove icon. If the Remove icon isn't available, you must enable the ORA_ZCH_ALLOW_REMOVE_FEATURE profile option. For more information about creating this profile option, see the Enable the Remove Option on the Override System Mapping UI topic in this chapter. Child entities associated with the entities that are removed using the Remove icon won't be transferred to the master record.

  8. Click Next to view the Override System Mapping: Review page. Now you can review the mapping settings and click Submit to override the default system mappings. In case there are edits, click Back to make updates to the mapping settings before submission.

Enable the Remove Option on the Override System Mapping UI

You can enable the Remove icon on the Override System Mapping UI by enabling the profile option ORA_ZCH_ALLOW_REMOVE_FEATURE by setting its value to Yes as follows:

  1. Sign in as a setup user such as, Sales Administrator, Master Data Management Application Administrator, or Application Implementation Consultant.

  2. Click Navigator > Setup and Maintenance work area.

  3. Click the Tasks menu and click Search. Search for Manage Administrator Profile Values task and open it.

  4. Search for the Profile Option ORA_ZCH_ALLOW_REMOVE_FEATURE.

  5. Click Actions, New in the ORA_ZCH_ALLOW_REMOVE_FEATURE: Profile Values area.

  6. Select Site as the profile level and Y as the profile value.

  7. Click Save and Close.

The automerge functionality merges duplicate records without any approval or intervention from the data steward. Automatic processing of merge requests is critical when processing large volumes of customer data as automerge can expedite the resolution of duplicate records without manual review. During automerge, the child entities of the duplicate records, such as contact points, relationships, classifications, and cross references, become the child entities of the master record. Note that groovy scripts on relationship objects don't run during merges. If they're critical, you can re-implement the scripts on the parent account or contact.

How Records are Selected for Automerge

Records are selected for automerge based on the following criteria:

  • Score threshold: The score threshold is defined in the Match Configuration and determines if a record is included in a duplicate set.

  • Automerge threshold: The automerge threshold is defined by the ZCH_AUTO_MERGE_THRESHOLD profile option and determines if the merge request for a duplicate set is processed automatically or if it must be reviewed manually.

Three possible outcomes for each record with regard to duplicate identification and merging are as follows:

  • Low score below score threshold: The record isn't included in duplicate set and in the merge request for that duplicate set.

  • Medium score above score threshold and below automerge threshold: The record is included in duplicate set but merge request for that duplicate set must be reviewed manually.

  • High score above score threshold and above automerge threshold: The record is included in duplicate set and merge request is processed automatically.

The score for all the records in a duplicate set must be above the automerge threshold for automated processing. If one record in the duplicate set is below automerge threshold, and the other records are above the automerge threshold, the merge request must be reviewed manually.

Note: When you merge two or more records with exactly same children information under phone, email, or address the children information is merged and rolled up to the survivor record.

How You Configure Automerge

Enabling Automerge involves several implementation steps that must be completed by an implementor using the following tasks from the Customer Data Management offering in the Setup and Maintenance work area:

  • Manage Customer Hub Profile Options: Use this task from the Customer Hub functional area to perform the following implementation steps:

    • Set Auto Merge Threshold profile option (ZCH_AUTO_MERGE_THRESHOLD) to the required value. This profile option specifies the threshold for auto merge. Merge requests with lower scores need data steward review. An exact match is 100.

    • Review the Record Size Limit of Duplicate Set (ZCH_DI_MERGEREQ_REC_SIZE). This profile option determines the maximum number of records in the duplicate set that can be merged automatically. By default, the maximum number is set to 10 records.

    • Set the Survivorship Enabled profile option (ZCH_ENABLE_SURVIVORSHIP) to Yes. This profile option enables the survivorship rules to select the master record and retain the attributes during a merge operation.

  • Manage Survivorship Rules: Use this task from the Customer Hub functional area to create Set Master survivorship rules to choose the master record for merge requests created from the duplicate identification batch and set the rule to active.

    If there are no active Set Master rules or if the Set Master rules didn't trigger, the merge request must be reviewed manually, even if the ZCH_AUTO_MERGE_THRESHOLD profile option is set, the score for all records is above the threshold value, and the number of records is below the record size limit.

    Note: You can use the Set Attribute rules with Set Master rules to determine the Golden Master record. For automerge, Set Master rule is mandatory.
  • Manage Enterprise Data Quality Matching Configurations: Use this task from the Data Quality Foundation functional area to perform the following implementation steps:

    • Create an active Match Configuration in Manage Enterprise Data Quality Matching Configurations task or use a predefined Match Configuration. Rebuild the keys if necessary.

    • Enable EDQ Real Time and Batch Basic Match Server in Manage Server Configurations task.

Run Automerge

This task involves the following two steps:

  1. Create a duplicate identification batch and select Create Merge Request as the Automatic Processing Option.

  2. Perform the task Run Request Dispatch Job to disposition the duplicate resolution sets.

The Dispatch Job processes any resolution request in Pending or Submitted status. You can run this job in two modes:

  • On demand: Run Request Dispatch Job > Submit

  • Per a specific schedule: Do the following steps to set up a recurring job:

    1. Click Advanced on the Run Request Dispatch Jobtask.

    2. Click Schedule tab and select the Using a Schedule radio button.

    3. Select the frequency you want and click Submit.

To see the list of dispatch jobs, and their statuses, navigate to Scheduled Processes under Tools.

Troubleshoot Automerge Issues

After you create your Duplicate Identification Batch, drill down into the completed batch to see the results. If duplicate sets have been found, and automerge is enabled, resolution requests are automatically submitted for merge.

If the resolution request wasn't submitted automatically, you can drill down to the duplicate set and compare the score for each record with the threshold in the ZCH_AUTO_MERGE_THRESHOLD profile option and the number of records with the limit in the ZCH_DI_MERGEREQ_REC_SIZE profile option. If all scores are above the threshold and the number of records is below the limit, verify that the following are true:

  • Set Master rules are active and triggered to choose a master for the records in the duplicate set.

  • ZCH_ENABLE_SURVIVORSHIP is set to yes.

Perform Automerge Using a SOAP Web Service

This topic describes how to automatically merge confirmed potential duplicates based on duplicate resolution requests using the DuplicateResolutionRequestService Web service.

Performing automerge involves the following tasks:

  • Enabling automerge.

  • Using the DuplicateResolutionRequestService Web Service to create an automatic merge request.

  • Running automerge.

  • Finding out the merge result.

Enable Automerge

  1. Set the User Merge Requests profile option to Allow Processing Without Approval. When the User Merge Requests profile option is set to this value, user merge requests are processed immediately without requiring any approval from Data Steward.

  2. Set the Merge Request Enabled (ZCA_MERGE_REQUEST) profile option to Yes.

  3. Enable the User Merge Requests (ZCH_USER_MERGE_REQUESTS) profile option. This profile option controls the behavior after the merge request is entered. See the section Customer Hub Profile Options.

Use the Web Service to Create an Automatic Merge Request

  1. To create an automatic merge request using the Web service, use the following URL:

    https://servername/crmService/DuplicateResolutionRequestService?WSDL

    For more information on DuplicateResolutionRequestService, see the Trading Community Real Time Data Quality section in the SOAP Web Services for CX Sales and B2B Service guide.

  2. You can use your proprietary, or a third party, SOAP Web services client to use the DuplicateResolutionRequestService Web service to create an automatic merge request. Enter the URL and run the createMergeRequest operation with the appropriate payload.

    For more information on Invoking SOAP Web Services, see the Invoking SOAP Web Services chapter in the SOAP Web Services for CX Sales and B2B Service guide.

Run Automerge

Request your administrator to perform the task Run Request Dispatch Job to disposition the duplicate resolution sets. The Dispatch Job processes any resolution request in Pending or Submitted status. You can run this job in two modes:

On demand:

  1. Navigate to the Run Request Dispatch Job task.

  2. Click Submit.

Per a specific schedule:

  1. Click Advanced on the Run Request Dispatch Job task.

  2. Click Schedule tab and select the Using a Schedule radio button.

  3. Select the frequency you want and click Submit.

Find Merge Result

  1. Use the getMergeResult operation of the DuplicateResolutionRequestService Web service to find the merge result.

  2. Use the operation with appropriate payload to view the result.

Merge requests are rejected either manually by a data steward or automatically by the application if the agreement rules are violated. You must login as a data steward to review or restore rejected merge requests in the Duplicate Resolution work area.

As a data steward, you can:

  • Review rejected requests: You review the rejected requests by drilling down through their request ID to the Review Merge Request page to find out the rejection reasons.

  • Refresh merge request details: You can refresh the merge request so that it has the latest details. For example, one of the records that must be merged could have been deleted after the merge request was created and before the data steward reviewed the merge request. Drill down the merge request, click Actions > Reprocess Merge on the Review Merge Request page to refresh the details of the merge request.

  • Restore rejected requests: After reviewing rejected requests, you can correct the rejection reason and then restore rejected requests by clicking Restore on the Review Merge Request page. You can either select a different master record or remove certain records from the merge request and submit the merge request for reprocessing.

If you know for sure that two or more records are confirmed duplicates, you can create a request to consolidate them from the Create Resolution Request UI page.

Consolidating confirmed duplicate records involves the following tasks:

  • Identify duplicate records

  • Select duplicate resolution request type such as merge or link

  • Create and submit the resolution request

Note: Groovy scripts on relationship objects don't run during merges. If they're critical, you can re-implement the scripts on the parent account or account.

Merge Confirmed Duplicate Records

You can merge confirmed duplicate records by creating and submitting a merge request from the Create Resolution Request UI page as follows.
Note: In this procedure you select the duplicates, which is quite unlike system merge in which the matching configuration selects duplicates.
  1. Navigate to the Duplicate Resolution work area as follows: Navigator > Customer Date Management > Duplicate Resolution.

  2. Click the Tasks menu and then click Create Resolution Request.

  3. Provide the search criteria to search for the records that you want to merge. For example, select the Party Type as Person and type the Name as John.

  4. Click Search.

  5. From the search results, using the Shift or Control keys, select the records that you want to merge.

  6. Click Actions > Create Request.

  7. Provide a name for the request in the Create Request: Select Type dialog box.

  8. Select the request type as Merge (Request to physically merge records into one record.).

    Note: You can select the request type as Generic if you want to defer the decision to select the resolution request type or Link if you want to link the records.

  9. Optionally, select a master record.

  10. Click OK.

    You can see a message that the duplicate resolution request was submitted. 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.

  11. Click Done.

You use linking to associate two or more duplicate records while resolving duplicate records. This association only creates a link between the records and doesn't affect the records. You use this association, which has a unique ID, to refer to the member records of a link.

You can also create links for normal records even if they aren't duplicate records. In a link, you designate one of the records as the master and the others as duplicates. This helps users identify the master records for use in transactions.

During merge, duplicate records are combined into a single master record. However, some parties can't be merged because of functional or legal reasons. For example, for certain bank operations, you can't merge duplicate records from different business units or geographical regions. In these scenarios, we create a link between duplicate records instead of merging them.

A link doesn't change the party and the associated child entities such as addresses, contact points, and relationships. A link doesn't affect the transactional processing of the record. The link is a separate record in the data model, and has its own registry ID.

You can manage links that are created either by duplicate resolution requests or by a data steward in the Manage Links page. Data stewards create links to resolve duplicate parties by manually linking them without a duplicate resolution request on the Create Link page.

You can access the managing links functionality by clicking on Manage Links on the Duplicate Resolution work area or by clicking Linked Parties on the Organization, Person, or Groups work area.

Create Links

To create links:

  1. Navigate to the Manage Links page as follows: Navigator > Customer Data Management > Duplicate Resolution > Tasks.

  2. Select Create from the Actions menu.

  3. In the Create Link page, enter the details about the link.

  4. In the Link Members area, select and add two or more parties that you want to link by selecting Add from the Actions menu. You must select one of the parties as the master.

  5. Click Save and Close.

Update Links

To update links:

  1. Navigate to the Manage Links page as follows: Navigator > Customer Data Management > Duplicate Resolution > Tasks

  2. Search for the link that you want to update. You can search by entering criteria such as link identification number, status, description, or the names of member record. You must select the Master Party Type to search for links.

  3. Select the link you want to update from the Search Results region and click Edit.

    Optionally, you can also delete a link by selecting the link and clicking Delete.

  4. In the Edit Link page, you can add link members, remove link members, and change the master record of the link.

    Note: If you remove the members of a link, you can't restore them. To restore a link member, you must add it again to the link.
  5. Click Save and Close.

How You Purge Duplicate Resolution Data

Legacy duplicate resolution data, such as resolution logs and legacy duplicate resolution batches and requests can clutter the duplicate resolution work area as well as affect the performance of the application. Use the Purge Duplicate Resolution Data scheduled process to purge the duplicate resolution data, such as resolution logs and to delete duplicate resolution batches and requests. You can schedule this process from the Scheduled Processes work area. You can navigate to this work area as follows: Navigator > Tools > Scheduled Processes.

This scheduled process lets you purge duplicate resolution data based on status and date range. You can specify the status of the duplicate resolution requests to be purged, such as duplicate resolution requests in Completed, Error, or Rejected status. You can also specify a date range by specifying the start and an end date to select duplicate resolution requests to be purged. For more information, see: Submitting Scheduled Processes and Process Sets: Procedure

FAQs for Duplicate Resolution

No. A member party can only participate in one link.

Records participating in a link remain intact. Only an association is created between members of a link.

Yes. Use the managing link functionality to create a link directly. You can access the managing links functionality by clicking on Manage Links on the Duplicate Resolution Work Area.

No. A link must contain members of the same party type.

No. You can override system mapping only for duplicate resolution request of the type merge.

Use the managing links functionality to access link information. You can access the managing links functionality by clicking on Manage Links on the Duplicate Resolution Work Area or by clicking Linked Parties in the Party Center.

How can I cancel a batch process?

You can cancel a batch process in the Scheduled Processes Overview page. You can navigate to this page as follows: . Navigator > Tools > Scheduled Processes. You must search for the batch process by its process ID, and then cancel the batch process request.

How can I make sure that a merge request contains the latest merge details?

Drill down the merge request, click Actions > Reprocess Merge on the Review Merge Request page to refresh the details of the merge request. You can refresh the details of a merge request only when the merge request is in error, rejected, or new statuses.

You must be logged in as a Data Steward Manager to assign duplicate resolutions requests. Data Steward Managers assign requests in the Duplicate Resolution work area.

You must be logged in as a Data Steward or a Data Steward Manager to reject a request. Data Steward Managers can reject any request. Data Stewards can reject only those requests that are assigned to them.

You can process duplicate resolution requests only if their status is New, and if the request type isn't link or merge. In short, you can only process generic duplicate resolution requests that are in New status.