UCM 'EnableExactMatch' Not Working With Null Or Empty 'ExactMatch' Field Values. (Doc ID 1954990.1)

Last updated on JULY 22, 2021

Applies to:

Symptoms

When processing UCM SDH records with 'ExactMatch' enabled, the UCM Batch Process Workflow should be using the value of the Exact Match field for each record in the job. However, if you have record(s) within the batch that have either an empty or null value in the Exact Match field, the value from the previous record is being used when searching. This leads to totally unrelated records going to Exact Match.

For example, 3 records,

1)
First Name: <FIRSTNAME1>
Last Name: <LASTNAME1>
Exact Match field : Support Engineer

2)
First Name: <FIRSTNAME2>
Last Name: <LASTNAME1>
Exact Match field : Support Engineer

3)
First Name: <FIRSTNAME3>
Last Name: <LASTNAME3>
Exact Match field :

If the records are processed in the order 1,2,3, the first goes to 'Source-Insert' (Correct), the second goes to 'Source-Upsert' (Correct), the third one either goes to 'Source-Upsert' due to 'Support Engineer' value incorrectly being used for the Exact Match query in the 'CDM Match' step, or the job fails with a 'SBL-SRB-00061' error and SDH record is not properly processed.

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.