Enabling Data Cleansing For Custom Child Entity Underneath Account

(Doc ID 2359149.1)

Last updated on FEBRUARY 09, 2018

Applies to:

Siebel Call Center - Version 16.18 [IP2016] and later
Information in this document applies to any platform.


SIEBEL VERSION: Siebel 16.18 [IP2016]
SIEBEL APP O/S: Microsoft Windows x64 (64-bit)


A custom business component has been create as a child entity to Account object. End to End setup was done from siebel side aswellas from OEDQ side to invoke data cleansing but this is not working.

The behaviour occurs as follows:

1. Create a custom business component 'New Communication Address' as a child entity to Account object.

2. Add the following user properties to the 'New Communication Address' BC:

DQ Business Object/DQ Vendor
DQ Field Mapping Info/DQ Field Mapping Info
DQ Mapping Config BC/DQ Mapping Config
DQ Vendor Info BC/DQ Vendor Info

3. In DQ Administration > Third Party Administration > EDQ > BC Field Mappings > add this BC for Data Cleansing and map the fields from Siebel application to the EDQ application.

4. Use Siebel Client UI to create an Account a child record for 'New Communication Address' BC. After the data is created, the record for the 'New Communication Address' is not cleansed.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms