Format of user property on "UCM Data Quality Manager" business service (for Data Cleansing and Data Matching)

(Doc ID 732965.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Universal Customer Master - Version 8.0.0.4 [20417] and later
Information in this document applies to any platform.



Goal

The "UCM Data Quality Manager" Business Service (BS) has user properties what control the Data Cleansing and Data Matching operation on Contact (Person) and Account (Organization) updates, performed by the "UCM Transaction Manager" BS invoked from workflow process of the UCM Batch Manager or UCM Inbound Web Service.


In the standard configuration, the "UCM Transaction Manager" BS is provided with user properties: "DisableSessionRealtimeClns=true" and "DisableSessionRealtimeDeDup=true", which are disabling real-time data cleansing and data matching. Because of this the Data Cleansing and Data Macting can be selectively initiated by the "TurnOnCDMCleanse=true" and the  "TurnOnCDMExactMatch=true" input parameter of the "SOAPExecute" method. However in this (disabled real-time dq) case the decision to provide an object data (contact or account component and fields) to data cleansing and matching (invoke the DQ API of the DQ provider's shared library) is  controlled by user properties of the "UCM Data Quality Manager" BS.

 

The user properties names that controls, which integration and business components (on which former is based)  of integration object, based on the  Account or Contact business object should be a subject for data cleansing or data matching:

 

To register components as Integration Component Name: Business Component Name pairs:

Account Cleansing Component <1,...> = <Integration  Component Name 1>:<Business Component Name 1>;<Integration  Component Name 2>:<Business Component Name 2>;...

Contact Cleansing Component <1,..> = <Integration  Component Name 1>:<Business Component Name 1>;<Integration  Component Name 2>:<Business Component Name 2>;...

Account Matching Component <1,...> = <Integration  Component Name 1>:<Business Component Name 1>;<Integration  Component Name 2>:<Business Component Name 2>;...

Contact Matching Component <1,...> = <Integration  Component Name 1>:<Business Component Name 1>;<Integration  Component Name 2>:<Business Component Name 2>;...

 

To register components as Integration Component Field Name: Business Component Field Name pairs:

Contact <Integration Component Name <1,...>> Cleansing Field <1,...> = <Integration  Component Field Name 1>:<Business Component Field Name 1>;<Integration  Component Field Name 2>:<Business Component Field Name 2>;...

Account <Integration Component Name <1,...>> Cleansing Field <1,...> = <Integration  Component Field Name 1>:<Business Component Field Name 1>;<Integration  Component Field Name 2>:<Business Component Field Name 2>;...

Contact <Integration Component Name <1,...>> Matching Field <1,...> =  <Integration  Component Field Name 1>:<Business Component Field Name 1>;<Integration  Component Field Name 2>:<Business Component Field Name 2>;...

Account <Integration Component Name <1,...>> Matching Field <1,...> = <Integration  Component Field Name 1>:<Business Component Field Name 1>;<Integration  Component Field Name 2>:<Business Component Field Name 2>;...

Example:

A custom solution introduces the "CUT Address" Business Component as Address Component for "Contact" Business Object (by default the contact address is provided by the  "Personal Address" Business Component ). The Integration Component Name for the address data in the Integration Object, provided to the "UCM Transaction Manager" BS (e.g. the "SwiPersonIO" Integration Object) is the "CUT Address" (based on the "CUT Address" Business Component). The Data Cleansing on the "CUT Address"  should take place for the fBusiness Component fields (same name used for the Integration Component fields): "Street Address", "Postal Code", "City", "Country", "House Number" (custom field).

Then following user properties should be added/amended at the "UCM Data Quality Manager" BS to make the "SOAPExecute" method of the "UCM Transaction Mmanager" BS, invoked withthe "TurnOnCDMCleanse=true" input parameter and instance of the "SwiPersonIO" Integration Object to invoke the Data Cleansing for the Contact Address:

1) amend existing user property:  "Contact Cleansing Component 1"
from value:
  Contact:Contact;Contact_INS Personal Address:Personal Address;Contact_Account:Account;
 to value:
  Contact:Contact;Contact_INS Personal Address:Personal Address;CUT Address:CUT Address;Contact_Account:Account;

2) add new user property:  "Contact CUT Address Cleansing Field 1"
with value:
  Street Address:Street Address;City:City;Personal Postal Code:Postal Code;Country:Country;House Number:House Number

Solution

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