Data Quality Matching with Realtime Deduplication using Universal Connector affected by Siebel visibility rules (Doc ID 1239903.1)

Last updated on AUGUST 17, 2022

Applies to:

Symptoms

When querying for possible duplicates to send to a 3rd party Data Quality solution for matching purposes, via the Universal Connector, Siebel is not taking into account records created by users who might hold a different position to that for whom the process is being run. That is, for example, if a Contact record is being created by a user within the 'My Contacts' view, when Realtime Deduplication is invoked it is done so with 'SalesRep' visibility applied, by the inclusion of a reference to the Position of the logged in user. This then means that similar/identical records created by another user holding a different Position, will not be taken into account, therefore affecting the effectiveness of the matching process.

This behaviour can be reproduced as such:

1) Enable Real Time deduplication for Universal Connector
2) Log in as any user who has access to 'My Contacts', go to this view and create a new unique Contact record.
3) Log in as another user who also has access to 'My Contacts', but has a different Position to the first user.
4) create the same contact in this view as when logged in as first user.

RESULT -> REAL TIME DEDUPLICATION DOES NOT PICK UP FIRST CONTACT AS BEING A CANDIDATE MATCH.

The reason for this is due to the reference to the 'POSTN_ID' in related queries, due to 'SalesRep' visibility being applied.

5) Still logged in as the second user, delete the Contact just created and go to 'All Contacts' view. You should then see the first contact created when logged in as first user.

6) Create the same contact again in the 'All Contacts' view.

RESULT -> REAL TIME DEDUPLICATION DOES NOT PICK UP FIRST CONTACT AS BEING A CANDIDATE MATCH.

Again, reason being that the first contact was created under SalesRep visibility.

7) Still logged in as second user, and in 'All Contacts' view, create a new, and unique, Contact record.

8) Log back in as first user and also go to 'All Contacts' view. You should then see the contact just created when logged in as second user.

9) Create an new contact record identical to this record.

RESULT -> REALTIME DUPLICATE POPUP DISPLAYS WITH FIRST CONTACT AS POSSIBLE MATCH.

The reason for this is because both records were created under the same visibility, that of 'Organization'.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.