My Oracle Support Banner

Survivorship For The Custom Child Entity Not Working As Expected (Doc ID 1634813.1)

Last updated on FEBRUARY 04, 2019

Applies to:

Siebel Universal Customer Master - Version [23021] and later
Information in this document applies to any platform.
*** Checked for currency AUG-10-2016 ***
*** Checked for currency on MAR-01-2018 ***


Product Type: Siebel Universal Customer Master
Version: [23021]
OS platform: Microsoft Windows (32-bit)
Env type: Dev

Statement of Issue:
A custom child entity called MSCCR Contact Communication Profile has been created as a child of Contact by following the steps in Guidelines to configure additional UCM Source Data and history (SDH) Child objects (Doc ID 605661.1). Child instances are inserted and updated correctly.

Survivorship has been implemented for Contact and for the standard child entity Personal Address and this works as expected.

The next requirement is to implement survivorship for the custom child entity MSCCR Contact Communication Profile. A bus comp called MSCCRUCMCommunicationProfileAttributeData was created that maps onto the table CX_UCM_CXM_UPD and the following user properties were added to the UCM Survivorship Engine business service:

EntityInternalProcess_MSCCRContactCommunicationProfile = true
NULLValueOverride_MSCCRContactCommunicationProfile =true

When an incoming contact was processed, it appears that survivorship isn’t carried out for the custom child entity and CX_UCM_CXM_UPD isn’t populated.

Expected Behavior:
Survivorship is carried out for the custom child entity.

Actual Behavior:
Survivorship isn’t carried out for the custom child entity.


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.