Siebel OEDQ Match Not returning Candidates (Doc ID 2092852.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM - Version 8.1.1.11.16 [IP2013] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.11.16 [IP2013] version, Client Functionality

ACTUAL BEHAVIOR
---------------
Siebel OEDQ Match not returning any candidates when trying to create a Contact using Person Match Webservice.

EXPECTED BEHAVIOR
-----------------------
It is expected that OEDQ is called and return duplicate matches when using Person WS.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

FROM Siebel UI:
1.Create NEW Contact record
2.Call is made to OEDQ to generate Cluster
3.Cluster KEY is sent back and stored in Siebel(S_DQ_CON_KEY) table
4.Driver and Candidate records are identified based on Cluster KEY
5.Individual Clean(De-Duplication) call is made to OEDQ
6.OEDQ returns the Match Record and Match Score,if applicable
7.Potential Matches are presented to the user in Siebel UI

FROM SOAP UI calling the Person Service:
1.Create NEW Contact record via Webservice Call
2.Call is made to OEDQ to generate Cluster
3.Cluster KEY is sent back and stored in Siebel(S_DQ_CON_KEY) table
4.Driver and Candidate records are identified based on Cluster KEY
5.Individual Clean(De-Duplication) call is made to OEDQ
6.OEDQ DOESN'T RETURN any MATCH SCORE;a blank XML is returned

Here, the following was seen in the EDQ log:

FINEST: 10-Dec-2015 14:40:20: dedup in[1]=<DriverRecord firstname=TestA0001_Wave87 jobtitle=Banner lastname=TestA0001_LN87 krcard=Card1234587>
FINEST: 10-Dec-2015 14:40:20: dedup in[2]=<CandidateRecord firstname=TestA0001_Wave87 individualid=1-DTLFH jobtitle=Banner lastname=TestA0001_LN87 krcard=Card1234587>
FINEST: 10-Dec-2015 14:40:20: POSTing <soap:Envelope xmlns:soap='http://schemas.xmlsoap.org/soap/envelope/'>
<soap:Body>
<dn:request xmlns:dn="http://www.datanomic.com/ws"><dn:record><dn:firstname>TestA0001_Wave87</dn:firstname><dn:jobtitle>Banner</dn:jobtitle><dn:lastname>TestA0001_LN87</dn:lastname><dn:krcard>Card1234587</dn:krcard><dn:candidate>0</dn:candidate><dn:matchthreshold>70</dn:matchthreshold></dn:record><dn:record><dn:firstname>TestA0001_Wave87</dn:firstname><dn:individualid>1-DTLFH</dn:individualid><dn:jobtitle>Banner</dn:jobtitle><dn:lastname>TestA0001_LN87</dn:lastname><dn:krcard>Card1234587</dn:krcard><dn:candidate>1</dn:candidate><dn:matchthreshold>70</dn:matchthreshold></dn:record></dn:request>
</soap:Body>
</soap:Envelope>
to server
FINEST: 10-Dec-2015 14:40:20: response is <?xml version="1.0" ?><env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"><env:Body><dn:response xmlns:dn="http://www.datanomic.com/ws" id=""></dn:response></env:Body></env:Envelope>
FINEST: 10-Dec-2015 14:40:20: dedup xml response=<Data></Data>

 

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot deduplicate using Person Webservice.

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