DQMgr Data Quality Setting = "Yes" And Having Object Where Clause With Only 1 Record Or Distinct Records Does Not Return Matches With EDQ (Doc ID 2052710.1)

Last updated on FEBRUARY 05, 2017

Applies to:

Siebel Data Quality - Version 8.1.1.11.12 [IP2013] and later
Siebel CRM - Version 8.1.1.11.12 [IP2013] and later
Information in this document applies to any platform.
*** Checked for currency FEB-05-2017 ***

Symptoms

SIEBEL VERSION:
---------------
Siebel 8.1.1.11 [23030] + EDQ 12.1.3

ISSUE STATEMENT:
----------------
Customer has Siebel application set up to use EDQ for Data Quality Matching. When using Siebel Data Quality Manager server task to perform batch matching on Contact object, customer observes that the request/data is sent to EDQ, but not matches are returned from EDQ to Siebel.

WHERE IT HAPPENED:
-------------------------------
The issue happens in customer's test environment.

STEPS TO REPRODUCE:
-------------------------------
The behaviour occurs as follows:

1. Install EDQ and Siebel application according to the respective product documentations.

2. Configure Siebel application to invoke EDQ for data matching, follow the respective documentations.

3. From Siebel application > Administration - Server Management screen > Server > Jobs view, create a new server job with the following parameters:

Component: Data Quality

Parameters:

Operation Type:          DeDuplication
Buscomp Name:          Contact
Data Quality Setting:    "'','Yes',''"
Object Where Clause:    [Id]='1-3K7SWM' or [Id]= '1-1288MQ'

4. The Siebel DQMgr request data goes to EDQ, but EDQ does not return any matching output.

BEHAVIOR PATTERN:
-------------------------------
The behavior is consistently occurring when performing the above task.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that since there are technically matching data in the Siebel application, matched data should be returned.

ERROR MESSAGE:
-------------------
There are no error messages that occurs with this issue, just the unexpected/undesired results being observed.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Since no matches are found/returned by EDQ, it results in similar data in Siebel that appears to be/are considered as duplicate/similar. Thus, this causes redundant data in the Siebel database.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms