Siebel Data Quality Manager Incremental Matching Is Not Working When Contact BusComp Comment Field Is Used In The Object Where Clause Search Spec Expression (Doc ID 2220190.1)

Last updated on SEPTEMBER 09, 2021

Applies to:

Symptoms

PRODUCT VERSION : Siebel 8.1.1.14 [IP2014]

ACTUAL BEHAVIOR
---------------
During a Data Quality Manager batch job, a search spec expression is provided in the 'Object Where Clause' parameter to identify records to be processed.

When the RowId field is used in the search spec expression in the 'Object Where Clause' parameter, DQMgr job finds duplicates.

When the 'Comment' field is used in the search spec expression in the 'Object Where Clause' parameter, DQMgr job completes but no records are found.

EXPECTED BEHAVIOR
-----------------------
DQMgr job 'Object Where Clause' parameter should be able to use any field in the search spec expression from the Business Component being used in the job.

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

1. Create contact records with some data in the Comment field.

2. Create a DQMgr batch job based upon the search spec of the value in the 'Comment' field, example:

Object Where Clause: [Comment] = '2000 91712111-7772-4229-b086-1b4361448888 51'

3. Run the DQMgr job, it runs and completes but finds no duplicates.

BUSINESS IMPACT
-----------------------
Due to this issue, users cannot use a certain fields in the 'Object Where Clause' parameter for the search spec expression.

Cause

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