Survivorship rules are not applied as expected with ExactMatch set to true.
Last updated on AUGUST 16, 2016
Applies to:Siebel Universal Customer Master - Version 8.0 SIA  and later
Information in this document applies to any platform.
***Checked for relevance on 24-Dec-2012***
The same account (Account1) is being sent to the UCM application from 2 external applications (SystemA and SystemB). The customer created survivorship rules with comparison rule set to Source to control which application could update which fields.
The workflow Customer Profile Integration Process was executed for Account1, which was sent from SystemA and Account1 was inserted into the Siebel base table.
Account1 was then sent from SystemB. This was matched against the Account1 in the base table and that record was updated using all of the field settings from SystemB, even though the confidence level of SystemA is higher than that of SystemB for some of the fields e.g. Home Page.
The functionality is being tested by executing the workflow UCM Customer Profile Integration Process (File Transport Test Workflow) using the server component Workflow Process Manager.
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