Resolution Request Was Created In "New" Status Instead Of "Submitted" Status Despite of ZCH_AUTO_MERGE_THRESHOLD Value (Doc ID 1632654.1)

Last updated on AUGUST 30, 2016

Applies to:

Oracle Fusion Customer Data Steward Cloud Service
Oracle Fusion Trading Community Data Quality - Version 11.1.7.0.0 and later
Oracle Customer Data Management Cloud Service
Information in this document applies to any platform.

Symptoms

On :  11.1.7.0.0 version, Manage Trading Community Data Quality

ACTUAL BEHAVIOR  
---------------
Resulting status if Resolution Request is inconsistent between the batches.
One resolution request was created in "New" status even though the match score (96) is above the auto merge threshold. from profile option :  ZCH_AUTO_MERGE_THRESHOLD

EXPECTED BEHAVIOR
-----------------------
Resolution request with match score (96) which is above the auto merge threshold. from profile option :  ZCH_AUTO_MERGE_THRESHOLD = 90
should be created with Submitted status  


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Manage Administrator Profile Values --> Profile Option Code = ZCH_AUTO_MERGE is set to 90
2. Match score threshold is set to 90.
3. So the expectation was that any matches above 90 from the duplicate identification will be automatically merged. The resolution request created for the duplicate identification batch will be in "Submitted" status.
But this is not happening consistently for all the records. Few records with the match above 90 have the duplicate resolution in submitted status , where as few records above 90 have duplicate resolution in "New' Status

4. Duplicate identification batch "300000009570044" with request id "300000009572308" was created. The match was 96.
On Sucessfull completion of the Duplicate Identification a resolution request was created in "Submitted" status and when the "Schedule Duplicate Resolution Requests" program was submitted , the resolution was "Completed"

5. Where as Duplicate Identification batch "300000009570041" with request id " 300000009572062" also have the match 96.
On Sucessfull completion of duplicate identification a resolution request was created. But the request was created in "new" status.

Why is the results inconsistent between the resolution. Please investigate why the resolution request " 300000009572062" was created in "New" status even though the match score (96) is above the auto merge threshold.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot manage Resolution request to be submitted in an automatic way even if their match score (96) is above the auto merge threshold.

Cause

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