Match Keys For Deduplication Getting Generated Even When Match Parameter Is False In Workflow
(Doc ID 2230968.1)
Last updated on FEBRUARY 05, 2019
Applies to:
Siebel Universal Customer Master - Version 8.1.1.10 [23021] and laterInformation in this document applies to any platform.
Symptoms
On : 8.1.1.10 [23021] version, Universal Customer Master
ACTUAL BEHAVIOR
---------------
In UCM Web services, match keys are getting generated all the time even though request is submitted to Transaction Manager with Match parameter as False("TurnOnCDMMatch" as 'False')
Even matching is disabled at the component level via "DeDuplication Enable Flag" = False, keys are still created/inserted.
WF:UCM Organization Customer Profile Integration SOAP Process
Step: Transaction Manager
Parameter: TurnOnCDMMatch
Scenario: 2 request are received by UCM Webservice
1. 1st request is submitted with parameter "TurnOnCDMMatch" as 'True'. In this case Match keys are generated, matching is triggered to OEDQ and match keys are generated.
2. 2nd request is submitted with parameter "TurnOnCDMMatch" as 'False'. In this case Match keys are generated though matching is not triggered to OEDQ.
Expectation is that in second request,match keys shouldn't get generated.
EXPECTED BEHAVIOR
-----------------------
While calling the web service,by disabling matching at workflow level and component level, Match keys should not get generated.
STEPS to Reproduce
-----------------------
The issue can be reproduced at will with the following steps:
1.Edit workflow "UCM Organization Customer Profile Integration SOAP Process",
set:Turn On CDM Match: false
2.Deploy/activate workflow.
3.DQ Setting View > Enable DeDuplication: Yes
4.EAI OM Parameter > DeDuplication Enable Flag: False
5.Restart Siebel server services.
6.Send inbound request to create a new account
Check that Match keys are getting generated.
Even though matching is disabled at the component level via "DeDuplication Enable Flag" = False, keys are still created/inserted.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Its a global application connected to multiple markets. This issue impacts performance of those markets where we don't need matching but still time is consumed in key generation.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |