1. Getting Started with Your Customer Data Management (CDM) Implementation
  2. Implement Automerge

Implement Automerge

Automatic processing of merge requests is critical when processing large volumes of customer data.

Automerge can expedite the resolution of duplicate records without any manual review or approval from the data steward.

How You Enable Automerge

You can enable Automerge by completing the following implementation tasks in the Setup and Maintenance work area:

  • Manage Customer Hub Profile Options: Navigate to this task either from the implementation project or through the Setup and Maintenance work area as follows: Offering: Customer Data Management > Functional Area: Customer Hub > Task: Manage Customer Hub Profile Options. 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's 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 value 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 or update operation.

  • Manage Survivorship Rules: Navigate to this task either from the implementation project or through the Setup and Maintenance work area as follows: Offering: Customer Data Management> Functional Area: Customer Hub > Task: Manage Survivorship Rules. Create Set Master survivorship rules or activate the predefined survivorship rules, base on your business requirements. Set Master survivorship rules are used to choose the master record for merge requests created from the duplicate identification batch.

    If there are no active Set Master rules or if the Set Master rules did not trigger, then 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 you must activate Set Master rules to complete the automerge without manual review.

    Note:

    You can use the Set Attribute rules with Set Master rules to determine the Golden Master record. For automerge, Set Master rule is required.

  • Define Data Quality: Perform the following implementation steps:

    • Enable EDQ Real Time and Batch Basic Match Server in Manage Server Configurations task. Navigate to this task either from the implementation project or through the Setup and Maintenance work area as follows: Offering: Customer Data Management > Functional Area: Data Quality Foundation > Task: Manage Server Configurations.

    • Create an active Match Configuration in Manage Enterprise Data Quality Matching Configurations task or use a predefined Match Configuration. Rebuild the keys if necessary. Navigate to this task either from the implementation project or through the Setup and Maintenance work area as follows: Offering: Customer Data Management > Functional Area: Data Quality Foundation > Task: Manage Enterprise Data Quality Matching Configurations.

Run Automerge

Running automerge involves the following two tasks:

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

  2. Run the task Run Request Dispatch Job from the Setup and Maintenance work area as follows to disposition the duplicate resolution sets.

The Run Request Dispatch Job processes all resolution requests in Pending or Submitted status. You can run this job in two modes:

  • On demand. Complete the following steps to run the job on an ad-hoc basis:

    1. Open the Run Request Dispatch Job task from the implementation project. Alternatively, in the Setup and Maintenance work area, go to the following:

      • Offering: Customer Data Management

      • Functional Area: Customer Hub

      • Task: Run Request Dispatch Job

    2. Click Submit and make a note of the Process ID.

  • Per a specific schedule: You can set up a recurring job when you:

    1. Open the Run Request Dispatch Job task from the implementation project. Alternatively, in the Setup and Maintenance work area, go to the following:

      • Offering: Customer Data Management

      • Functional Area: Customer Hub

      • Task: Run Request Dispatch Job

    2. Click Advanced.

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

    4. Select the required frequency and start date and click Submit and make a note of the Process ID.

To see the list of dispatch jobs, and their statuses:

  1. Go to the Tools section on the Navigator

  2. Click the Scheduled Processes link under Tools.

  3. Use the Process ID that you noted earlier to search and view the status of the Schedule Duplicate Resolution Requests process.

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 merging.

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 Set Master rules are active. These rules trigger you to choose a master for the records in the duplicate set. One last thing that you would have to check is that the ZCH_ENABLE_SURVIVORSHIP is set to yes.