My Oracle Support Banner

Too Many Candidates Returned From Key Selection During Insert Of A New Contact Record Via Siebel UI Causing Duplicates To Be Created, Requires Changing EDQ Key Cluster Generation Logic (Doc ID 2124522.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Universal Customer Master - Version 8.1.1.11.11 [IP2013] and later
Siebel CRM - Version 8.1.1.11.11 [IP2013] and later
Information in this document applies to any platform.

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 8.1.1.11 (with no patchsets applied)

ISSUE STATEMENT:
----------------------------
Customer was trying to test matching for a contact record with these attributes:

First Name: Charlotte
Last Name: Poole
Email Address: charlottelaw0@gmail.com
Phone Number: 8889876543

Whenever this contact record/attribute are used in Siebel Client or UCM Inbound Web Service, it never produces a match and always results in a 2nd record created for the contact.

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

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

1. Set up Siebel application with data quality.

2. Insert a record for a contact through the Siebel Client with these attribute values:

First Name: Charlotte
Last Name: Poole
Email Address: charlottelaw0@gmail.com
Phone Number: 8889876543

3. No potential match applet is displayed, the contact is always inserted as a new record, thus resulting in it being a duplicate.

BEHAVIOR PATTERN:
-------------------------------
The behavior always occur for the above attribute values.

EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that there is indeed one matching record with same First Name, Last Name and email address and should be returned as a match.

WHAT IS NOT WORKING/ACTUAL RESULTS:
-------------------------------------
The actual result is that the matches are not found, the contact is created as another record, causing a duplicate.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Due to the record not being matched, records with same values are being created, which are considered as duplicates from a business perspective. it is impacting the Production Roll of Date.ODM Issue Clarification

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.