18Duplicate Identification Setup

This chapter contains the following:

Matching is a process that identifies the potential duplicates for account, contact, and address. You can identify the potential duplicate records in real-time when you create a customer record, and in batch mode for existing records.

Oracle provides the data matching solution for Oracle Cloud applications through integration of Oracle Enterprise Data Quality (EDQ). EDQ is a complete data quality product with capabilities such as profiling, standardization, matching and merging, which is also available as a standalone product.

Defining data matching involves setting up two components, matching and address cleansing. As part of implementing these components, you must perform the following related setup tasks in the Setup and Maintenance work area from the Data Quality Foundation functional area of the Customer Data Management offering:

  • Manage Server Configurations

  • Manage Enterprise Data Quality Matching Configurations

Note: You must set up the server configurations prior to implementing EDQ matching.

Enterprise Data Quality (EDQ) server configurations are predefined configurations for EDQ integration. You can enable and disable a data quality management operation by selecting or deselecting the related EDQ server configuration.

EDQ Real-Time and Batch Basic Match Server is the predefined server configuration available for EDQ.

EDQ Real-Time and Batch Basic Match Server

Enable this configuration if you want to use the matching capabilities. Enabling this configuration lets you benefit from both real-time and batch matching features. Real-time matching is used to prevent entry of duplicate records. Batch data matching is used for identifying duplicates of existing records.

Enterprise Data Quality (EDQ) matching configurations comprise attributes and parameters for real-time and batch matching of entities to prevent duplicate entries and identify existing duplicates. EDQ real-time and batch matching are available for account and contact entities. You have the option of using either the predefined ready-to-use configuration or copying and adapting it to your address matching requirements.

The predefined EDQ matching configurations applicable for both real-time and batch matching are:

  • Account Duplicate Identification

  • Contact Duplicate Identification

These configurations are used to identify the duplicate account and contact entries. You can review and edit these predefined matching configurations to optimize the matching functionality to meet your needs.

EDQ Matching Process

In EDQ matching process, the record added or updated to the application for comparison is called a driver record. And, the records that are compared with the driver record are called the candidate records. Driver records are compared with each other, but candidate records are never compared with other candidates. The EDQ real-time matching process compares a single driver record against many candidates and returns possible duplicate records based on matching attributes and threshold. The batch matching process compares all driver records of the same type, such as account and contact, and identifies all possible matches within these sets of records.

The batch matching process runs in two modes, full batch and incremental batch. While the full batch mode matches all records against each other, the incremental mode matches a subset of records against all of their selected candidates. In batch matching, separate matching templates are provided that lets you specify different match rules. For example, you may want to minimize user intervention of adding customers in front end applications, and perform an exhaustive match on a regular basis.

The EDQ matching process for real-time and batch matching runs the EDQ Cluster Key Generation service and EDQ matching service for duplicate identification. The EDQ Cluster Key Generation service is called whenever a record is added or updated in an application. This service generates keys for records added as well as for the records that are updated in the application. These generated keys are stored in the application, which are then used to select the candidate records that may match to the data in the application.

The selected candidate records along with the driver record are returned to the EDQ matching service. Then, this service examines the records and decides which of the candidate records are a good match with the driving record. Once EDQ matching service arrives at the best match, it assigns a score to every duplicate record identified based on the strength of the match.

For more information about the EDQ matching process, see the Oracle Enterprise Data Quality Customer Data Services Pack Matching Guide at

http://docs.oracle.com/cd/E48549_01/doc.11117/e40737/toc.htm

Match Attributes

Match attributes define the attributes that are used for real-time and batch matching of the account and contact entities to identify duplicate entries. You use two types of attributes for matching:

  • Match Identifier: Specifies the EDQ attribute that you want to use for matching

  • Application Attributes: Specifies the application attribute that you want to use for matching

You can map the attributes in application with the corresponding EDQ attributes to create an attribute mapping. For example, for the Name EDQ attribute, you can select the Org.OrganizationName as the corresponding Organization attribute to create a mapping. You can define such attribute mappings for real-time matching, batch-data matching, or both.

When you map the attributes in the application with the corresponding EDQ attributes, you create a matching configuration setting for identifying duplicate entries. These settings are stored as matching keys in the application. Whenever you change the attribute mappings, you must regenerate matching key values for the new or updated accounts and contacts. You can regenerate matching key values using the Rebuild Keys option in the Edit Matching Configuration page.

Match Configuration Parameters

Matching configuration parameters are system-level parameters that control aspects of the data quality matching services.

The following parameters control matching operations for identification of duplicate entries such as account and contact in the database, between database and sets of data, such as import batches, or within sets of data to resolve them from merging or linking.

Score Threshold

  • Parameter Value: Between 0 and 100. Default Value: 90

  • Parameter Description: Specifies the score above which the matched records are returned by the matching service. Records equal to or greater than the score are considered as matches and the records with scores less than the threshold are rejected.

Match Results Display Threshold

Note: This match configuration parameter is enabled only for real-time matching.
  • Parameter Value: Between 0 and 100. Default Value: 10

  • Parameter Description: Controls the number of matched records that are returned by the real-time matching.

Preview Configuration

The Preview Configuration option lets you enter the following parameters to identify and view the duplicate matching records in real-time without rebuilding the keys.

  • Cluster Key Level: Returns records based on the cluster key level.

  • Score Threshold: Returns records based on score threshold.

  • Maximum Candidates: Returns records based on maximum candidates.

  • Match Results Display Threshold: Returns records based on the match results display threshold value.

Review Configuration Results

The Review Configuration Results option lets you check if the input account or contact entered for matching in the Edit Matching Configuration page returns the expected matched account or contact after the rebuilding of keys. Alternatively, in the Review Configuration Results page, you can enter the attribute information for one or more of the following matching configuration parameters that you want to match:

  • Cluster Key Level: Returns records based on the cluster key level.

  • Score Threshold: Returns records based on score threshold.

  • Maximum Candidates: Returns records based on maximum candidates.

  • Match Results Display Threshold: Returns records based on the match results display threshold value.

How You Manage Level of Indirection

You can control the level and number of indirect duplicates for a driver record using a user defined profile option ORA_ZCQ_LEVEL_OF_INDIRECTION. This profile option lets you include indirect duplicates. For example, look at a duplicate set having possible drivers A, C and candidates B, D as follows:

A - B

A - C

C - D

Here, we delete duplicate pair C-D because its winner C is a matched record of A-C. Hence, we lose D as a potential duplicate. This would possibly be identified as a duplicate only in the next batch run. However, we know that D is an indirect duplicate of A. If we set up the value of the profile option ORA_ZCQ_LEVEL_OF_INDIRECTION as 1, you can consider D as a matched record in the first batch run itself. Therefore, the duplicate sets would be as follows:

A - B

A - C

A - D (because D is now an indirect duplicate of A).

Let's understand how the profile option ORA_ZCQ_LEVEL_OF_INDIRECTION controls the level of indirect duplicates with another example where we have the duplicate pairs as A-B, A-C, C-D, D-E, and E-F. In this case, setting the profile option value as 1 would mean that only the first level of indirect duplicates which is C-D is considered as part of A's duplicate set, causing the A-D pair to be formed. However, if we set the profile option value as 2, it would also extend to second level of indirection. Therefore, A-D and also A-E would be the duplicate pairs identified because of the A-C, C-D, and D-E indirection sequence.

To control the level and thereby number of indirect duplicates for a driver record using the profile option ORA_ZCQ_LEVEL_OF_INDIRECTION , perform the following steps:

  1. In the Setup and Maintenance work area, go to the Manage Administrator Profile Values task.

  2. On the Manage Administrator Profile Values page, search for and select the profile option.

  3. In the Profile Values section, click Add. A new row is added for you to specify the following conditions:

    • Profile Level: Specify the level at which the profile value is to be set. Select Site.

    • Profile Value: Select or enter the value, such as 1 or 2, depending on the required level of indirection.

  4. Click Save and Close.

    Note: Changes in the profile values take effect for a user on the next sign in.

You can perform the following tasks as part of managing Enterprise Data Quality (EDQ) matching configurations.

  • Copying a predefined Enterprise Data Quality matching configuration

  • Editing a copy of the predefined Enterprise Data Quality matching configuration

Copy a Predefined Enterprise Data Quality Matching Configuration

To copy or make a duplicate of a predefined Enterprise Data Quality matching configuration, complete these steps:

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Customer Data Management

    • Functional Area: Data Quality Foundation

    • Task: Manage Enterprise Data Quality Matching Configurations

  2. On the Manage Enterprise Data Quality Matching Configurations page, select the Account Duplicate Identification match configuration, and click Duplicate.

  3. Click Yes in the Warning dialog box.

  4. Click Save to save the copy of the predefined configuration.

    Note: You must save the copy of the predefined configuration, if you want to edit it.
  5. Repeat Steps 2 to 4 to create copies of the predefined configuration for the Contact Duplicate Identification match configurations.

Edit a Copy of the Predefined Enterprise Data Quality Matching Configuration

To edit a copy of the predefined Enterprise Data Quality matching configuration, complete these steps:

Note: You can't edit the predefined Enterprise Data Quality configuration. You can only make a copy of it and edit it by following this procedure.
  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Customer Data Management

    • Functional Area: Data Quality Foundation

    • Task: Manage Enterprise Data Quality Matching Configurations

  2. On the Manage Enterprise Data Quality Matching Configurations page, select the copy of Account Duplicate Identification match configuration that you created in Copying a Predefined Enterprise Data Quality Matching Configuration section, and click Edit.

  3. Select the Active check box to set the Account Duplicate Identification match configuration as the active configuration.

    Note: By default, the predefined configurations are always set to active. If there are one or more copies of the predefined configurations, then you can set any of them to active by selecting the Active check box. At any given point in time, only one configuration can be active.
    Note: Also, note that the Usage option is set to Both, which indicates that the configuration is for both real-time and batch matching.
    Note: You must rebuild keys before activating a new or copied configuration. For more information about Rebuilding Keys, see the Managing Key Generation section in this chapter.
  4. Click Yes in the Warning dialog box to set this configuration as active.

  5. In the Match Attributes section, perform the following steps:

    1. Select a row to edit the mapping, and click the drop-down button for the selected row.

    2. Select the relevant attribute from the list.

    3. If the list doesn't display the attribute that you want for the mapping, then click Search to search for the attribute.

    4. Select the relevant option and click OK.

  6. Select a Cluster Key Level option. For example, select Typical.

  7. In the Score Threshold field, enter a value between 0 and 100, such as 85. In the Match Results Display Limit field, enter a value between 0 and 100, such as 20.

    Note: The Match Results Display Limit option isn't available for Batch.
  8. Click Save.

    Note: You can see the Automerge Threshold and Autolink Threshold values in the Batch tab. You can change these values in the Manage Customer Hub Profile Options page or override these values while creating the duplicate identification batch criteria rules.

Unique Identifiers and Elimination Identifiers

The duplicate identification setup process lets you configure up to three unique identifiers and three elimination identifiers as part of your matching configuration. Unique identifiers and elimination identifiers are special match tokens that you can use for cases where the value of a single attribute conclusively determines whether a set of records are duplicates, without needing to consider any other attribute values. The meanings of these Unique identifiers and elimination identifiers fields are as follows:

  • Unique Identifiers - any records that have the same non-null value for an attribute that has been defined as a unique identifiers are automatically identified as duplicates, regardless of any other attribute values

  • Elimination Identifiers - any records that have different non-null values for an attribute that has been defined as an elimination identifiers are never identified as duplicates, regardless of any other attribute values

Both unique identifiers and elimination identifiers only evaluate non-null values, and matching is still possible between records that have a mixture of populated and null elimination identifier or unique identifier values. For example, two records may be identified as duplicates when one record has a value in an elimination identifier field, the other record has no value (null) for the elimination identifier field, and the records also match on other attributes such as name and address.

To better understand the difference between unique identifiers and elimination identifiers, consider the following requirements:

  • We will always consider contacts that have the same email address to be duplicates. (This requirement could be handled with a unique identifier field)

  • We will never consider contacts that have different email addresses to be duplicates. (This requirement could be handled with an elimination identifier field)

If you choose to use Custom Scoring as part of your duplicate identification configuration, keep the following in mind:

  • Records with different non-null elimination identifier values are never identified as duplicates, regardless of any scoring rules. Elimination identifier fields should not be included in custom scoring rules, and adding elimination identifier fields to your custom scoring rules may lead to unpredictable or inconsistent matching results.

  • The custom scoring rules for unique identifier fields must always be defined as a single-value exact match rule with a score of 100. The standard matching configuration comes seeded with default custom scoring rules for the three available unique identifier fields, and these default custom scoring rules should not be modified. Unique identifier fields are specifically designed for their function and adding unique identifier fields to any other custom scoring rules may lead to unpredictable or inconsistent matching results.

This topic describes how to enable the custom match rules and scoring functionality.

Use the following procedure to enable custom match rules for account and contact. Note that custom match rules are available only for account and contact.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Customer Data Management

    • Functional Area: Data Quality Foundation

    • Task: Manage Enterprise Data Quality Matching Configurations

  2. On the Manage Enterprise Data Quality Matching Configurations page, drill down on the predefined or the user-defined matching configuration, for which you want to enable or disable custom match rules and scoring.

  3. Scroll down to the Scoring Type drop-down list and select Custom from the Real-Time or Batch tabs on the Edit Match Configuration page.

  4. Click Save or Save and Close

You can use the custom match rule and scoring functionality to create your own match rules and scores based on your business requirements.

Use the following procedure to create custom match rules.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Customer Data Management

    • Functional Area: Data Quality Foundation

    • Task: Manage Enterprise Data Quality Matching Configurations

  2. On the Manage Enterprise Data Quality Matching Configurations page, drill down on the predefined or the user-defined matching configuration for which you want to create or update predefined rules.

  3. Click Manage Match Rules on the Edit Match configuration page.

  4. On the Manage Match Rules page click New. Alternatively, you can click Duplicate to create a new rule based on an existing predefined or user-defined match rule.

  5. Enter the following values for the newly created or copied match rule:

    • Rule Name: The name of the new rule.

    • Match Rule Score: The score that you assign to the rule. The value must be between 1 and 100.

    • Rule Attribute: The standard or predefined attributes that must be used in the custom match rules. Ensure that the syntax and spelling are exact.

  6. Click Save or Save and Close.

The Customer Data Quality application comes with two options for match rules and scoring, predefined match rules (EDQ match rules) and custom match rules (Customer Data Management match rules). You can use a drop-down button on the Enterprise Data Quality Matching Configuration page to select the match rules and scoring option best suited for your business requirements.

The predefined EDQ match rules include a single, view-only matching rule for each object such as account and contact. These match rules can't be edited, scores can't be changed, and no new rules can be added.

In case the predefined match rules aren't suitable for your business requirements, you should enable custom match rules and scoring. You should be able to turn on custom scoring by selecting Custom from the Scoring Type drop-down list on the Manage Enterprise Data Quality Matching Configurations UI page. You can use this functionality to create your own match rules and scores.

How You Configure Synonyms and Skip-words Dictionary

You can use synonyms and skip-words to improve the quality of match results. Synonyms help you to map words that are used interchangeably in your industry. For example, Tech maybe mapped to Technology. Skip-words help reduce noise words such as titles like Mr or Ms in names. These synonyms and skip-words dictionaries are pre-defined as lookup types. You can configure these dictionaries by modifying the lookup types. These lookup types let you tailor the match results by word replacement patterns that may be unique to your application.

Note: Synonyms are supported only for Person names, Organization Names, and Address lines 1 to 4.

You can add, edit, or remove words or patterns in the following out of the box lookup types:

  • ORA_ZCQ_CS_ACC_MAPPING_DATA: Modify this lookup type to update the mapping of account data. For example, Tech indicates Technology.

  • ORA_ZCQ_CS_CON_MAPPING_DATA: Modify this lookup type to update the mapping of contact data. For example, Abbi indicates Abigail.

  • ORA_ZCQ_CS_ADD_MAPPING_DATA: Modify this lookup type to update the mapping of address data. For example, Rd indicates Road.

  • ORA_ZCQ_CS_ACC_STRIP_DATA: Modify this lookup type to update the list of strip words for account data. For example, add Org to the list to remove it during data matches.

  • ORA_ZCQ_CS_ADD_STRIP_DATA: Modify this lookup type to update the list of strip words for address data.

  • ORA_ZCQ_CS_CON_STRIP_DATA: Modify this lookup type to update the list of strip words for contact data. For example, add Mr. or Ms. to the list to remove them during data matches.

Note: These lookups don't support these special characters ! " # $ % ' * - : ; @

You can access the lookup types by following these steps:

  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 Standard Lookups task and open it.

  4. Type ORA_ZCQ_CS% in the Lookup Type field and click Search.

    A list of lookup types is displayed.

  5. Click to select a lookup type.

    The details of the lookup are displayed. You can add, delete, or modify the lookup values as per your requirement.

The EDQ matching process for real-time and batch matching makes use of the EDQ Cluster Key Generation service and the EDQ matching service for duplicate identification. Successful key generation is critical to duplicate identification. Key generation identifies similar parties and assigns a key to each. When a matching configuration is made active, the application passes a set of keys (subset of parties) to the EDQ matching service to process for duplicate identification.

The EDQ Cluster Key Generation service must be run whenever a record is added or updated in the application. This service generates keys for records added as well as for the records that are updated in the application. If keys aren't generated, duplicate identification fails.

How You Configure Key Generation

The duplicate identification process uses matching keys, which must be maintained through a key generation process. You need to set up a recurring, incremental key generation job for each active data quality matching configuration for batch duplicate identification. You also may want to configure real-time key generation for immediate matching of new data as soon as new data is entered.

How You Setup Recurring Incremental Key Generation (Required)

You can schedule incremental key generation for an active matching configuration using the schedule key generation option on the Edit Matching Configuration page. This generates keys for records that don't have a key or if the key time stamp is older than that of the records. You must incrementally generate matching key values for the new or updated accounts and contacts.

To assure your duplicate identification processes use up-to-date matching keys, check if the following setup tasks have been completed.

  1. In the Setup and Maintenance work area, go to the following:

    • Offering: Customer Data Management

    • Functional Area: Data Quality Foundation

    • Task: Enterprise Data Quality Matching Configuration

  2. Click the name of the required active match configuration.

  3. Click Scheduled Key Generation.

  4. Click Advanced.

  5. Select Using a schedule option in the Advanced Options section.

  6. Specify the frequency, the start date, and end date to run the scheduled process.

    You may want to select a distant end-date to reduce how often you must run this task and to help assure that the recurring schedule doesn't lapse.

  7. Click Submit.

    The recurring incremental key generation scheduled process is submitted.

How You Specify Real-time Key Generation (Optional)

You may want to configure keys to be generated for immediate matching of new data as soon as new data is entered. For example, different users may be entering duplicate records at nearly the same time and you may want the keys to be generated immediately. Real-Time key generation process is available to handle such scenarios.

Follow these steps to enable real-time key generation:

  1. Search and navigate to the Manage Administrator Profile Values task.

  2. Search for the ORA_ZCQ_ENABLE_REALTIME_KEYGEN profile option.

  3. Set the Site level profile option value to Yes.

  4. Click Save and Close.

Best Practices for Real-Time Key generation

Here are guidelines to help you decide if real-time key generation is right for your business needs:

  • Use Real-Time key generation only if an appropriately scheduled incremental key generation process doesn't support your business process needs.

  • Certain processes, such as batch address cleansing, don't trigger real-time key generation events. Real-time key generation isn't sufficient to replace recurring incremental key generation, but it may be used as a complement for certain business scenarios.

  • If possible, disable update events for higher-volume data creation and update processes, such as web service-based data integration flows.

To disable high-volume user accounts from generating update events:

  1. Search and navigate to the Manage Administrator Profile Values task.

  2. Search for the ZCA_PUBLIC_BUSINESS_EVENTS profile option.

  3. Click Actions > New in the Profile Values section.

  4. Specify the following values:

    • Set the Profile Level to User.

    • Select the User Name for which you want to suppress business events.

    • Set the Profile Value to No.

  5. Click Save and Close.

How You Rebuild Keys

You must rebuild keys before activating a new configuration. You must rebuild keys if you change match configuration mappings or if you think that the keys are no longer valid because of updates to the records. You can regenerate matching key values using the Rebuild Keys option in the Edit Matching Configuration page.

How You Specify Real-time and Batch Key Generation Options

You can specify different key generation options for batch matching and real-time matching. Take for example the cluster key level parameter that has the values, limited, typical, or exhaustive. It's possible to select one value of this parameter, say limited, for batch matching and another, say exhaustive, for real-time matching, depending on how tightly you want the data quality engine to match records.

How You Review Key Generations Status

You can search for key generation jobs and review the status of each key generation job on the Manage Key Generation page. The following table describes the various possible key generation statuses for a matching configuration.

Key Generation Status Description

Pending

Key generation for the configuration is required.

Processing

Key generation for the configuration is in progress.

Review Required

Key generation for this configuration needs review.

Ready

Key generation for this configuration is complete.

Select Customer Identifying URLs During Duplicate Identification

The Duplicate Identification process evaluates the domain name portion of URLs to help determine whether a set of customer records are likely to be duplicates of each other. You can ensure that distinct customer records aren't incorrectly classified as duplicates because a common domain name is present in the web contact points collection when that domain name doesn't actually identify the organization. For example, customer records can be given web contact points based on social websites, analyst websites, or other types of web resources that use a common domain name when referencing the customer in a query string or page-level locator. By registering those common domain names, the duplicate identification process doesn't consider those web contact points.

You can use the Manage Standard Lookups setup task and create new entries under the ORA_ZCQ_FILTER_DOMAINS lookup type for the required URLS.

You can add the URL details 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 Standard Lookups task and open it.

  4. Type ORA_ZCQ_FILTER_DOMAINS in the Lookup Type field and click Search.

    The details of the lookup are displayed.

  5. In the Lookup Codes section, click Action > New and specify the URL details.

    Specify the domain name in the Lookup Code field for the lookup. For example, type DATAFOX or TWITTER in the Lookup Code field. Also type the Meaning and Description for the lookup code.

  6. Click Save and Close.

Identify Duplicates in Real-Time Using REST APIs and SOAP Web Services

This topic describes how to identify duplicates using REST APIs and SOAP Web services leveraging the Enterprise Data Quality (EDQ) engine.

Before you begin, perform these steps:
  1. Enable EDQ Real time and Batch Basic Match Server in the Manage Data Quality Server Configurations page.

  2. Identify the configuration code for the EDQ match configuration that you want to perform from the Setup and Maintenance work area by going to the following:

    • Offering: Customer Data Management

    • Functional Area: Data Quality Foundation

    • Task: Enterprise Data Quality Matching Configuration

    How You Identify Duplicates Using REST APIs

    To identify duplicates for accounts (organizations) in real-time using REST API, use the following URL:

    crmRestAPI/resouces/latest/accounts/action/findDuplicates

    To identify duplicates for contacts (persons) in real-time using REST API, use the following URL:

    crmRestAPI/resouces/latest/contacts/action/findDuplicates

    You must use the POST method of these APIs. For more information on findDuplicates, see the Identify Duplicate Accounts and Contacts section in the REST API for CX Sales and B2B Service guide. You can use your proprietary, or a third party, REST API client to use the findDuplicates custom action to identify duplicates.

    For more information on working with REST API client, see the Work with your REST Client topic in the REST API for CX Sales and B2B Service guide.

    How You Identify Duplicates Using SOAP Web Services (Deprecated)

    To identify duplicates in real-time using SOAP Web services (deprecated), use the following URL:

    https://servername/crmService/DQRealTimeService?WSDL

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

    You can use your proprietary, or a third party, SOAP Web services client to use the DQRealTimeService to identify duplicates. Enter the URL and run the relevant operations listed here with appropriate payloads:

    • matchPerson: Use this operation to identify duplicate persons.

    • matchLocation: Use this operation to identify duplicate locations.

    • matchOrganization: Use this operation to identify duplicate organizations.

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

FAQs for Duplicate Identification

Matching configurations include parameters that can be set at the matching configuration level and modified depending on cleansing strategy, data, and result requirements. You can use these configurations during real-time matching to prevent duplicate entries and during batch matching to identify existing duplicates.

Matching server configurations provide the address and port of the data quality server used to process match requests. These configurations show both matching configuration and server configuration level parameters along with their type and cardinality. The parameters set at the server level are applicable to all the matching configurations.

Real-time duplicate prevention identifies all possible duplicate records that may exist in the database for an entered record. This prevents entering of duplicate entities, such as organization, person, or location, into the database.

Duplicate identification identifies potential duplicate entities already existing in the database using batch matching, and resolves the actual duplicates by merging or linking.