Siebel "DeDuplication Results (Contact)" BC "Sales Rep" ViewMode creates duplicate/multiple records in S_DEDUP_RESULT table with same Contact ROW_ID value during real time UI matching

(Doc ID 1935897.1)

Last updated on AUGUST 22, 2016

Applies to:

Siebel Data Quality Connector - Version [IP2013] and later
Information in this document applies to any platform.
*** Checked for currency AUG-22-2016 ***


Siebel SIA [23030]

Customer is using Siebel application with EDQ for data quality integration. During testing, customer observes that duplicate contact records are being created when a user logged into the application as one position creates a similar record to an existing contact which has a different position. Ie, if the login user's position is not the same as the existing matching record's team position, then the record created by the login user is created anew instead of being detected as a match.

Customer identified the source of the problem to the bus comp view mode on 'DeDuplication Results (Contact)'. There are two view modes defined. One for Organization and one for Position. The view mode for 'Position' is causing this issue. After inactivating the 'Position' bus comp view mode, no duplicate entries are created. Also the old entries for same contact id are getting deleted and new entries getting created when contact is updated with different position.

However, customer would like to understand if it is the correct solution to inactivate 'Position' bus comp view mode on DeDuplication Results (Contact)' Buscomp. Will there be any adverse impact on EDQ functionality?

The issue happens in customer's test environment.

The behaviour occurs as follows:

1. Log in with user 1 (position 1) and create a new contact. Now create another new contact in such a way that it is duplicate of first contact with few attributes change.

2. On save of second contact, a new entry is created in Data Quality->Duplicate Contacts view (S_DEDUP_RESULT table) for that second contact id.

3. Update contact which was create first. Another entry in Data Quality->Duplicate Contacts view for first contact id. So now, we have entires for both the contact id in Duplicate contacts view.

4. Log in with user 2 (position 2). Update any other attribute for first contact in such a way that EDQ is re triggered.

Earlier created entry in Data Quality->Duplicate Contacts view for first contact id remains intact.A new entry for same contact id is created.

Due to the duplicate records, there are now duplicates in the database, causing user confusion and overhead to manually review and merge potential duplicates.

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


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