UCM Merge Request: Survivor Child Pointing To Victim Parent Record Which Doesn't Exist
(Doc ID 2692332.1)
Last updated on JULY 21, 2020
Applies to:Siebel Universal Customer Master - Version 20.6 and later
Information in this document applies to any platform.
On : 20.6 version, Universal Customer Master
While merging two parent records with an identical child record, UCM is incorrectly updating the survivor child record with information from the victim's parent record. Not faced this issue for vanilla child entities and issue with custom child entities only.For example there is a parent Id field on the custom child entity(Example:ABC) and merge results in the survivor child pointing to a parent that does not exist.
The issue can be reproduced at will with the following steps:
1. From UI, try to merge 2 accounts with identical child record
In "UCMAccountMerge" IO, create custom child entity as Integration component
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