22Define Data Quality

This chapter contains the following:

Setting Up Data Quality Using Enterprise Data Quality: Explained

Oracle provides a robust data quality solution for all Oracle Sales Cloud applications through a ready-to-use integration with a product called Oracle Enterprise Data Quality (EDQ). EDQ is a complete data quality product with capabilities such as profiling, standardization, matching and merging, and address verification, which is also available as a standalone product.

Setting up data quality using EDQ involves two operations, matching and address cleansing.

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.

Address cleansing is a process that corrects and validates address data, based on postal requirements. For example, if you enter valid values for postal code, city, and country, the data quality functionality may return a value for state. Likewise, if you enter valid values for city, state, and country, the data quality functionality automatically supplies a postal code value.

The data quality services receive matching or cleansing requests, such as duplicate prevention or address validation, from a variety of consuming applications. The data quality service then calls the EDQ service based on the configuration for further processing. The primary components of the Oracle Sales Cloud data quality architecture are as follows:

  • OSC-EDQ Connector in the Oracle Sales Cloud CRM Server - Receives requests from Oracle Sales Cloud applications for address validation, matching, and so on

  • Oracle Address Validation Service - Performs address validations

  • Shared Sharing Database - Handles batch jobs

  • EDQ Matching Server - Performs address matching

The following figure illustrates the various architecture components of the Oracle Sales Cloud data quality solution and how Oracle Sales Cloud applications interface with the EDQ engine.

Enterprise data quality management architecture

Defining data quality involves setting up two components, matching and address cleansing. As part of implementing these components, you must perform the related regular setup tasks in the Setup and Maintenance work area:

  • Manage Server Configurations

  • Manage Enterprise Data Quality Matching and Cleansing Configurations

Note: You must set up the server configurations prior to implementing EDQ matching or cleansing, depending on the data quality requirements.

Manage Server Configurations

You have the option of enabling or disabling the predefined server configurations for EDQ integration by selecting or deselecting the related server configuration. Enabling a predefined matching or cleansing server configuration allows you to benefit from both the real-time and batch matching or cleansing capabilities.

  • For more information on managing EDQ server configurations, see Enterprise Data Quality Server Configurations: Explained.

Manage Enterprise Data Quality Matching Configurations

You have the option of using either the predefined matching configurations shipped ready-to-use or copying and adapting it to your address matching requirements. Real-time matching identifies duplicate account, contact, and address entries in Oracle Sales Cloud. Batch matching identifies duplicate entries within a set of records or a batch of the same type in the database. For more information, see Managing Enterprise Data Quality Matching Configurations: Procedures.

Manage Enterprise Data Quality Cleansing Configurations

You have the option of using either the predefined cleansing configuration shipped ready-to-use or copying and adapting it to your address cleansing requirements. Real-time address cleansing performs cleansing, standardization, and validation of addresses during the data entry process. Batch address cleansing performs cleansing operations on a set of address records in the database. For more information, see Managing Enterprise Data Quality Cleansing Configurations: Procedures.

Server Configurations

Enterprise Data Quality Server Configurations: Explained

Enterprise Data Quality (EDQ) server configurations are predefined configurations for EDQ integration. Each EDQ server configuration is associated with a data quality management operation such as matching or cleansing. You can enable and disable a data quality management operation by selecting or deselecting the related EDQ server configuration.

Two predefined server configurations are available for EDQ:

  • EDQ Real-Time and Batch Basic Match Server

  • EDQ Real-Time and Batch Basic Cleanse Server

EDQ Real-Time and Batch Basic Match Server

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

EDQ Real-Time and Batch Basic Cleanse Server

Enable this configuration if you want to use the cleansing capabilities. Enabling this configuration allows you to benefit from both real-time and batch cleansing features in Oracle Sales Cloud. Real-time address cleansing service allows the sales representative to verify the addresses while creating a contact or an account. Batch address cleansing allows the sales administrator or data steward to cleanse a set of addresses that already exist in Oracle Sales Cloud in bulk and during import process.

Matching Configurations

Enterprise Data Quality Matching Configurations: Explained

Enterprise Data Quality (EDQ) matching configurations comprise attributes and parameters for real-time and batch matching of Oracle Sales Cloud entities to prevent duplicate entries and identify existing duplicates. EDQ real-time and batch matching are available for account, contact, and address 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

  • Address Duplicate Identification

These configurations are used to identify the duplicate account, contact, and address entries in Oracle Sales Cloud. 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, contact, and address, 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 Oracle Sales Cloud. These generated keys are stored in Oracle Sales Cloud, 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, contact, and address entities to identify duplicate entries. You use two types of attributes for matching:

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

  • Oracle Sales Cloud Attributes: Specifies the Oracle Sales Cloud attribute that you want to use for matching

You can map the attributes in Oracle Sales Cloud 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 Oracle Sales Cloud with the corresponding EDQ attributes, you create a matching configuration setting for identifying duplicate entries. These settings are stored as matching keys in Oracle Sales Cloud. Whenever you change the attribute mappings, you must regenerate matching key values for the new or updated accounts, contacts, and addresses. 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, contact, and address 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 allows you to 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 allows you to check if the input address entered for matching in the Edit Matching Configuration page returns the expected matched address 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.

Managing Enterprise Data Quality Matching Configurations: Procedures

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

Copying 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. From the Setup and Maintenance work area, search for Manage Enterprise Data Quality Matching Configurations and click Go to Task.

  2. 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 or Address Duplicate Identification match configurations.

Editing 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 configurations. You can only make a copy of it and edit it by following this procedure.
  1. From the Setup and Maintenance work area, search for Manage Enterprise Data Quality Matching Configurations and click Go to Task.

  2. 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.
  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. In the Cluster Key Level drop-down list, select Typical.

  7. In the Score Threshold field, enter 85. In the Match Results Display Threshold field, enter 20.

    Note: The Match Results Display Threshold option isn't available for Batch.
  8. Click Save to save your changes.

Managing Custom Match Rules and Scoring: Explained

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. Navigate to: Setup and Maintenance > Customer Data Management offering > Setup >Data Quality functional area > Define Data Quality > Manage Enterprise Data Quality Matching Configuration.

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

  3. Select Custom from the Scoring Type drop-down list on the Edit Match Configuration page.

  4. Click Save or Save and Close

Creating Custom Match Rules: Procedure

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. Navigate to: Setup and Maintenance > Customer Data Management offering > Setup > Data Quality functional area > Define Data Quality> Manage Enterprise Data Quality Matching Configurations.

  2. Drill down on the predefined or the user-defined matching configuration, on the Manage Enterprise Data Quality Matching Configurations UI page, for which you want to create or update custom 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 custom match rule.

  5. Enter the following valued for the 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 custom 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.

Selecting Sources of Match Rules and Scoring:Points to Consider

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, contact, and address. These match rules cannot be edited, scores cannot be changed, and no new rules can be added.

In case the predefined match rules are not 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.

Managing Key Generation: Explained

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 are not generated, duplicate identification fails.

Scheduling Key Generation

You can schedule key generation for a matching configuration using the schedule key generation option on the Edit Matching Configuration page.

Rebuilding Keys

You must regenerate matching key values for the new or updated accounts, contacts, and addresses. You can regenerate matching key values using the Rebuild Keys option in the Edit Matching Configuration page.

Specifying 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 is 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.

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

Identifying Duplicates Using Web Services: Worked Example

This example describes how to identify duplicates using Web services leveraging the Enterprise Data Quality (EDQ) engine.

The following table summarizes key decisions for this scenario.

Decisions to Consider In This Example

What type of service is set up in Oracle Enterprise Manager Fusion Applications Control?

DQRealTimeService

Which duplicate entries do I want to identify using Web Services?

Contact

What is the associated configuration code for Contact?

DQ_SEED_CONTACT_DUP_IDENTIFICATION

What record type is associated with the data quality engine?

Driver

To identify duplicates using Web services, complete the following tasks:

  • Extract the web services URL

  • Derive the request payload

  • Test the web service

  • Test the match results

Prerequisites

  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, Enterprise Data Quality Matching Configuration task. The configuration code is displayed in the Manage Enterprise Data Quality Matching Configurations page.

Extracting the Web Services URL

  1. Sign in to the Oracle Enterprise Manager Fusion Applications Control using the Web Logic Server credentials.

  2. Select Oracle Fusion Customer Relationship Management from the navigation tree, and then select Oracle Fusion Applications.

  3. From the tree, select CrmCommonApp, and then select CrmCommonApp (CRMCommonServer_1).

  4. In the Web Services pane on the page, click Test for the DQRealTimeServiceSoapHttpPort port.

  5. In the Test Web Service pane, copy the URL of a WSDL that appears in the WSDL field until "?wsdl", and then paste to a notepad.

Deriving the Request Payload

  1. Launch the WSDL URL in a Web browser to open the DQRealTimeService endpoint page.

  2. In the DQRealTimeServiceSoapHttpPort pane, select matchPerson from the Operation list.

  3. In the Request Payload pane, complete the fields, as shown in the following table.

    Field Value

    DataQualityRequestId

    1

    ConfigCode

    DQ_SEED_CONTACT_DUP_IDENTIFICATION

  4. In the DataQualityParam section, complete the fields, as shown in the following table.

    Field Value

    ParamName

    ScoreThreshold

    ParamValue

    10

  5. In the DataQualityPerson section, enter the minimum details of the person such as the first name, last name, and address that you want to match. The following table contains sample details of a person that you want to match.

    Field Value

    DataQualityRequestId

    1

    DataQualityRecordType

    Driver

    PersonFirstName

    Smith

    PersonLastName

    Wilson

    AddressLine1

    401 Island Parkway

    City

    Redwood

    Country

    US

  6. Click the XML Source option.

    Note: This option appears next to the Operation list.

  7. Copy the XML source and paste to a notepad.

  8. Select matchLocation and repeat steps 1 to 7 to identify duplicates for address or select matchOrganization and repeat steps 1 to 7 to identify duplicates for account.

Testing the Web Service

  1. Open the Oracle Fusion Service Tester page.

  2. In the WebService URL field, paste the WSDL URL that you derived from Step 5 of the "Extracting the Web Services URL" section.

  3. Enter the user name and password credentials.

  4. In the Input Argument pane, paste the XML source that you derived from Step 7 of the "Deriving the Request Payload" section.

  5. Click Test Web Service. The Output Payload pane displays the output payload.

Testing the Match Results

  1. Copy and paste the output payload to a notepad.

  2. Verify if the COMPLETED and SUCCESS messages are displayed in the ErrorCode and Message tags, respectively.

  3. Search by the person first name to identify the number of duplicates displayed.

  4. Verify the match results.

Cleansing Configurations

Enterprise Data Quality Cleansing Configurations: Explained

Enterprise Data Quality (EDQ) cleansing configurations comprise attributes and parameters for real-time and batch cleansing of addresses. You have the option of using either the predefined configuration shipped out-of-the-box or copying and adapting it to your address cleansing requirements. The predefined EDQ address cleansing configuration is named as Real-Time and Batch Address Cleansing. As part of defining and managing EDQ cleansing configurations, you can review and edit the predefined cleansing configuration.

EDQ real-time address cleansing includes an online, interactive service to cleanse and validate addresses during the data entry process either through a UI or any other service creating address data into the registry. The real-time address cleansing service parses the input address and validates it against the country-specific postal address reference databases, such as United States Postal Service (USPS), Canada Post. The real-time address cleansing service runs in two modes:

  • Verify: The verify mode allows you to parse, verify, cleanse, transliterate, and format the input address data. This mode checks the reference data and returns the best match (1 to 1).

  • Search: The search mode allows you to search all installed data and return multiple results (1 to Many).

EDQ batch address cleansing performs address cleansing, verification, standardization, and validation for a subset or entirety of the address records in the registry, or as part of a data import process. Batch address cleansing service can only be run in the Verify mode that parses and cleanses the input address data and enables output to be displayed in either native or Roman characters.

Note: For more information on address verification, see the "Manage Sales Cloud and Data Cloud Integration: Explained" topic in the Related Topics section.

Cleansing Attributes Mapping

The mapping of the EDQ cleansing attributes with the corresponding Oracle Sales Cloud attributes to create cleansing configurations is called cleansing attributes mapping. Oracle Sales Cloud provides the following attributes for address cleansing:

  • Input Address Attribute: The attribute used to describe the input Oracle Sales Cloud address for address cleansing is called the input address attribute.

  • Output Address Attribute: The attribute used to describe the output Oracle Sales Cloud address after the address cleansing process is called the output address attribute.

  • EDQ Attribute: The Oracle Sales Cloud attribute that is used for cleansing.

You can determine what input address attribute you want to map to the Oracle Sales Cloud EDQ attribute for address cleansing. An EDQ attribute is used to describe a distinct item of information that relates to a record. For example a City attribute might describe the city details of a Customer record. Once the mapping is established, the input address is verified, cleansed, and validated in Oracle Sales Cloud. You can map the cleansed address described in the Oracle Sales Cloud EDQ attribute to the corresponding output address attribute.

In this example, the sample input data contains a part of the postal address and lacks the complete street address and state information as shown in the following table.

Input Address Attribute Value

Address1

8500 Normandale Lake Suite 710

City

Bloomington

Postal Code

55437

After the mapping, the input address is verified, validated, and corrected. The cleansed output address data is shown in the following table.

Output Address Attribute Value

Address1

8500 NORMANDALE LAKE BLVD

Address2

STE 710

City

BLOOMINGTON

State

MN

Postal Code

55437-3813

Cleansing Configuration Parameters

Cleansing configuration parameters are system-level parameters that control aspects of the data quality cleansing services. The EDQ cleansing configuration includes real-time and batch cleansing configuration parameters.

The following parameters control real-time and batch address cleansing, standardization, and validation operations for a subset or entirety of the address records in the database, or as part of a data import process.

Default Country

  • Parameter Description: Used to specify the country to cleanse the address, if no identifiable country can be found in an input address.

Output Casing

  • Parameter Value: Upper case, Lower case, Mixed case. Default Value: Mixed

  • Parameter Description: Used to specify the letter case for an output address.

Minimum Verification Level

  • Parameter Value: Between 1 and 5. Default Value: 3

  • Parameter Description: Used to specify the level of verification to which the input data matches the available reference data during the verification process.

Minimum Verification Score

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

  • Parameter Description: Used to specify the similarity between the address entry and closest reference data match as a percentage between 0 (no match) and 100 (perfect match).

Correct Partially Verified Addresses: Determines if you want to correct the addresses entry that are partially verified.

Correct Ambiguous Addresses: Determines if you want to correct the unclear addresses entry and resolve it to the correct address.

Review Configuration Results

The Review Configuration Results option allows you to check if the input address entered for cleansing in the Edit Cleansing Configuration page returns the expected cleansed address. Alternatively, in the Review Configuration Results page, you can enter the attribute information for one or more of the following cleansing configuration parameters that you want to cleanse:

  • Minimum Verification Level: Returns records based on the minimum verification level.

  • Minimum Verification Score: Returns records based on the minimum verification score.

  • Processing Mode: Returns records based on the processing mode.

Then, verify if the records returned for the cleansed address meets your expectations.

Managing Enterprise Data Quality Cleansing Configurations: Procedures

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

  • Copying a predefined Enterprise Data Quality cleansing configuration

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

Copying a Predefined Enterprise Data Quality Cleansing Configuration

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

  1. From the Setup and Maintenance work area, search for Manage Enterprise Data Quality Cleansing Configurations and click Go to Task.

  2. Select the Address Cleansing configuration, and click Duplicate.

  3. Enter a name in the Name field and click Save to save your changes.

Editing a Copy of the Predefined Enterprise Data Quality Cleansing Configuration

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

Note: You can't edit the predefined Enterprise Data Quality configurations. You can only make a copy of it and edit it by following this procedure.
  1. From the Setup and Maintenance work area, search for Manage Enterprise Data Quality Cleansing Configurations and click Go to Task.

  2. Select the Address Cleansing configuration and click Edit.

  3. Select the Active check box to set the address cleansing 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.
  4. Click Yes in the Warning dialog box to set this configuration as active.

  5. In the Cleansing Attributes Mapping section, select an attribute in the Address column, enter a corresponding attribute in the Attributes column, and then map it with the corresponding attributes in the Attributes column to create an attribute mapping.

  6. In the Cleansing Configuration Parameters section, perform the following tasks:

    1. In the Default Country drop-down list, select the relevant country name.

    2. In the Output Casing drop-down list, select Upper Case to print the address in upper case.

    3. In the Minimum Verification Level drop-down list, select 3-Verified to Thoroughfare Level.

    4. In the Minimum Verification Score drop-down list, select 80.

    5. Select the Correct Partially Verified Addresses check box.

    6. Select the Correct Ambiguous Addresses check box.

  7. Click Save to save your changes.

Cleansing Addresses Using Web Services: Worked Example

This example describes how to cleanse addresses using Web services leveraging the Enterprise Data Quality (EDQ) engine.

The following table summarizes key decisions for this scenario.

Decisions to Consider In This Example

What type of service is set up in Oracle Enterprise Manager Fusion Applications Control?

DQRealTimeService

Which processing mode do I want to use for address cleansing?

Search: This mode lets you search all installed data and return multiple results.

What is the associated configuration code for address cleansing?

DQ_SEED_LOC_CLEANSE

What record type is associated with the data quality engine?

Driver

To cleanse addresses using Web services, complete the following tasks:

  • Extract the web services URL

  • Derive the request payload

  • Test the web service

  • Test the cleanse results

Prerequisites

  1. Enable EDQ Real time and Batch Basic Cleanse Server in the Manage Data Quality Server Configurations page.

  2. Identify the configuration code for the EDQ cleansing configuration that you want to perform from the Setup and Maintenance, Enterprise Data Quality Cleansing Configuration task. The configuration code is displayed in the Manage Enterprise Data Quality Cleansing Configurations page.

Extracting the Web Services URL

  1. Sign in to the Oracle Enterprise Manager Fusion Applications Control using the WebLogic Server credentials.

  2. Select Oracle Fusion Customer Relationship Management from the navigation tree, and then select Oracle Fusion Applications.

  3. From the tree, select CrmCommonApp, and then select CrmCommonApp (CRMCommonServer_1).

  4. In the Web Services pane on the page, click Test for the DQRealTimeServiceSoapHttpPort port.

  5. In the Test Web Service pane, copy the URL of a WSDL that appears in the WSDL field until "?wsdl", and then paste to a notepad.

Deriving the Request Payload

  1. Launch the WSDL URL in a Web browser to open the DQRealTimeService endpoint page.

  2. In the DQRealTimeServiceSoapHttpPort pane, select cleanseAddress from the Operation list.

  3. In the Request Payload pane, complete the fields, as shown in the following table.

    Field Value

    DataQualityRequestId

    1

    ConfigCode

    DQ_SEED_LOC_CLEANSE

  4. In the DataQualityParam section, complete the fields, as shown in the following table.

    Field Value

    ParamName

    ProcessingMode

    ParamValue

    Search

    Note: In the ParamValue field, if you enter Verify, it checks the input address data and returns the best match.

  5. In the DataQualityPerson section, enter the address that you want to cleanse. For example, complete the fields, as shown in the following table.

    Field Value

    DataQualityRequestId

    1

    DataQualityRecordType

    Driver

    AddressLine1

    401 Island Parkway

    Country

    US

  6. Click the XML Source option.

    Note: This option appears next to the Operation list.

  7. Copy the XML source and paste to a notepad.

Calling the Web Service

  1. Open the Oracle Fusion Service Tester page.

  2. In the WebService URL field, paste the WSDL URL that you derived from Step 5 of the "Extracting the Web Services URL" section.

  3. Enter the user name and password credentials.

  4. In the Input Argument pane, paste the XML source that you derived from Step 7 of the "Deriving the Request Payload" section.

  5. Click Test Web Service. The Output Payload pane displays the output payload.

Testing the Cleanse Results

  1. Copy and paste the output payload to a notepad.

  2. Verify if the COMPLETED and SUCCESS messages are displayed in the ErrorCode and Message tags, respectively.

  3. Verify the cleansed address.

Enabling Search Mode for Address Verification Cloud Service

The Address Verification Cloud Service comes with two processing modes, Verify and Search. You can use this functionality to verify an address in real-time while entering information on the Create Accounts or the Create Contacts page.

Out of the box, only the Verify mode is available to customers. When the Verify mode is enabled and you do real-time address verification on the Create or Edit Accounts or Contacts page, the service returns a single verified address that matches the address information you entered on the page.

The search mode is available only to the Oracle Data Cloud Address Verification Unlimited License customers from Release 11 Patch Bundle 15. When the Search mode is enabled and you do real-time address verification on the Create or Edit Accounts or Contacts page, the service returns a list of the suggested verified addresses that match the address information you entered. You can then select the appropriate address from the list. You must create a new profile option and configure the address verification process mode to enable search mode. This topic describes how Oracle Data Cloud Address Verification Unlimited License customers can enable the DaaS Address Verification Search Mode.

Create New Profile Option for Enabling Search Mode

Perform the following steps to create a new profile option that you require to enable search mode.

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

  2. Navigate to Setup and Maintenance > Manage Applications Core Profile Options task.

  3. Click New from Actions. The Create Profile Option page appears.

  4. Enter the following information in the Create Profile Option page:

    • Profile Option code: ORA_ZCQ_AV_UNLIMITED_LIC

    • Profile Display Name: ORA_ZCQ_AV_UNLIMITED_LIC

    • Application: Trading Community Data Quality

    • Module: Application Common

    • Provide appropriate Description

    • Provide appropriate Start Date and End Date.

  5. Click Save and Close.

    Now you can see the new profile option in the Manage Applications Core Profile Options page.

  6. Select the SiteEnabled and Updatable check boxes in the Profile Options Levels section.

  7. Click Save and Close.

  8. Navigate to the Manage Applications Core Administrator Profile Values task.

  9. Search for the Profile Option Code ORA_ZCQ_AV_UNLIMITED_LIC.

  10. Click New under the ORA_ZCQ_AV_UNLIMITED_LIC: Profile Values section.

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

  12. Click Save and Close.

Configure Address Verification Processing Mode

You can configure the address verification process mode by performing the following tasks:

  1. Navigate to the Setup and Maintenance work area > > Manage Enterprise Data Quality Cleansing Configurations task.

  2. Click Address Cleansing.

    The Edit EDQ Cleansing Configuration: Address Cleansing page appears.

  3. Select Search from the Processing Mode drop down list in the Cleansing Configuration Parameters section.

    Note: You can select either Verify or Search mode form the Processing Mode drop down list according to your requirements. Select Verify mode if you want only one verified address to be returned while verifying an address on the Create Accounts or Create Contacts page. Select Search mode to get a list of the suggested verified addresses that match the address you entered so that you can select the appropriate address from the list.
  4. Click Save and Close.

Verify Search Mode on Account or Contact Creation Page

You can verify the functionality of the Search mode while creating a new account or contact. Perform the following steps to verify an address in the search mode while creating a new account:

  1. Navigate to Accounts work area.

  2. Click Create Account.

  3. Enter Address Line 1, City, and State of the account that you want to create on the Create Accounts page.

  4. Click Verify Address.

    Note: If you click Verify Address after populating all the fields in the Address section of the Create Address page, you will get only one verified address with the complete match.
  5. Select the correct address by clicking Select for the appropriate address from the list of suggested verified addresses.

  6. Click OK.

    When you click OK the selected address gets populated in the Address section of the Create Account page.

  7. Enter account details on the Create Account page.

  8. Click Save and Close.

FAQs for Integrating with Oracle Enterprise Data Quality Engine

What's the difference between matching configurations and matching server configurations?

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.

What's the difference between cleansing configurations and cleansing server configurations?

Cleansing configurations include parameters that can be set at the cleansing configuration level and modified depending on cleansing strategy, data, and result requirements. You can use these configurations to cleanse address during data entry, and to cleanse and validate existing addresses to ensure data accuracy.

Cleansing server configurations provide the address and port of the data quality server used to process cleanse requests. There are no server configuration parameters for cleansing.

What's the difference between real-time duplicate prevention and duplicate identification?

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.

What's the difference between real-time address cleansing and batch address cleansing?

Real-time address cleansing is an online, interactive service to cleanse and validate addresses during the data entry process.

Batch address cleansing cleanses and validates addresses that already exist in the database or are imported into it.