Incorrect Handling Of Child Entities In Merge Override
(Doc ID 2668290.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Fusion B2B Service Cloud Service - Version 11.13.20.01.0 and later
Information in this document applies to any platform.
Incorrect Handling of child entities in Merge Override
When running the merge process, all child entities are transferred from victim record to the survivor record. The primary record, the child entity of the master, should be set as the primary record of the child entity of the survivor.
This is the default behavior of the process when the merge override is not used.
We've noticed that if the data steward click on the override button and after selects the child entities records to be transferred to the master record, not always the primary record is set to be the same as the master record primary.
Eg : When merging two contact with emails, the survivor Contact should have a primary email that is equal to the primary email from Master Contact.
The issue that we noticed is that in this applet the Master Record column is not automatically set to the proper record. We would expect that the primary email of the master record to have the Master Record Flag set to true. This is the default behavior when using the merge process without using the override button. However we've notice that this not always the case.
The issue can be reproduced at will with the following steps:
1) Click on Navigator -> Duplicate Resolution
2) Select a Merge Request in New State
3) Drill down on the Merge Request Id
4) Click on the Override Button
5) Click on the Next button to start
6) Click on the Next to accept the proposed values for Contact
7) you should be now be on the Override System Mapping: Map Entities.
Assuming you are merging two records with emails associated, you should select all the data to be transferred.
Select all records to be needs to be transferred and click on the merge button.
8) In button applet you should be able to see all the record that should be transferred to the survivor record.
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