My Oracle Support Banner

Error “'UCM Contact Privacy' is not a valid child type for component type 'Contact'” occurs when creating contact from incoming duplicate. (Doc ID 1265383.1)

Last updated on FEBRUARY 02, 2022

Applies to:

Siebel Universal Master - Version 8.0.0.6 SIA [20423] and later
Siebel Universal Customer Master - Version 15.18 [IP2015] to 15.18 [IP2015] [Release V15]
Information in this document applies to any platform.

Symptoms


Environment:
-------------------
Product type: Siebel Universal Master
Version: Siebel Universal Master
DB: Oracle Server - Enterprise Edition
OS platform: Microsoft Windows (32-bit)
Env type: dev


Statement of Issue:
-----------------------------
The UCM Batch Process Workflow was executed and an incoming contact was automatically identified as an incoming duplicate. When the contact is selected in the Incoming Duplicates view and the Create New button is clicked an error is displayed. The incoming contact is inserted into the base tables but the incoming duplicate is still displayed in Incoming Duplicates.


Error:
-------
ObjMgrLog Error 1 000010514cd01f50:0 2010-11-03 14:39:06 (eaiobjinst.cpp (2867)) SBL-EAI-04008: Integration component type 'UCM Contact Privacy' is not a valid child type for component type 'Contact'

ObjMgrBusServiceLog Error 1 000010514cd01f50:0 2010-11-03 14:39:06 (datasync.cpp (326)) SBL-EAI-04008: Integration component type '<?>' is not a valid child type for component type '<?>'

ObjMgrLog Error 1 000010514cd01f50:0 2010-11-03 14:39:06 (dataaccess.cpp (213)) SBL-EAI-04056: Cannot map input object ('') to internal integration object ('UCMContactSourceDataAndHistory').

Cause

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
Symptoms
Cause
Solution
References


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