My Oracle Support Banner

Merge Functionality Is Not Transferring Custom Child Objects to Surviving Object (Doc ID 2800128.1)

Last updated on MAY 13, 2022

Applies to:

Siebel CRM - Version 21.6 and later
Information in this document applies to any platform.


Siebel Merge functionality for custom child objects is not working, i.e. objects are not transferred to surviving records during the merge operation.
All Child objects should be transferred to the surviving record.

The issue can be reproduced at will with the following steps:
1. Create a new Extension Table "CX_NOTE_OPTY_X" for "S_NOTE_OPTY". The BC in this context is "Opportunity Note", which is pointed to the new "CX_NOTE_OPTY_X" table created.
2. Open the Application > navigate to Opportunities > add 2 new Opportunities, and make sure each has at least one Note added in the Child Applet "Public Notes".
3. From the corresponding Opportunity List Applet select the 2 rows.
4. Merge the records: custom child objects are not transferred to the surviving record during the merge operation.

When using "S_NOTE_OPTY" which is a Standalone Table, the issue is not replicated. The records are correctly merged.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.