Address Cleansing Generates Error "Field "Cleanse Verification Code" is not activated in BusComp "CUT Address" for update" In The Log File (Doc ID 2303190.1)

Last updated on AUGUST 31, 2017

Applies to:

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

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: 15.8 [IP2015]
DATABASE VERSION: Microsoft Windows x64 (64-bit)


ISSUE STATEMENT:
----------------------------

When an existing address is cleansed by EDQ and the cleansed address field values are updated to the Siebel address record, the following occurs:

1. These errors show up in the log file:

ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Verification Code" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Verified Flag" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Verified Status" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Latitude" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Longitude" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Geo Accuracy Code" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Geo Accuracy Status" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Geo Accuracy Distance" is not activated in BusComp "CUT Address" for update.

2. The mentioned fields and their corresponding database columns are not populated with the cleansed value returned by EDQ.


ERROR MESSAGE:
--------------------------
The error message that occurs with this issue is:

ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Verification Code" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Verified Flag" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Verified Status" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Latitude" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Longitude" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Geo Accuracy Code" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Geo Accuracy Status" is not activated in BusComp "CUT Address" for update.
ObjMgrBusCompLog Error 1 000013f159a00bdc:0 2017-08-30 16:03:41 Field "Cleanse Geo Accuracy Distance" is not activated in BusComp "CUT Address" for update.


STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Set up Siebel application to use EDQ for address cleansing.

2. Use Siebel Client UI to update an existing address so that it triggers a cleansing request to EDQ.

3. The cleansed address values from EDQ is updated to the Siebel address record, but the log file shows the reported error in the fields and the database columns for those fields are not populated with the cleansed value returned by EDQ.


EXPECTED BEHAVIOR:
-------------------------------
The expected behaviour is that the values are update to the address record.


LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
Due to the missing data on the address, it did not capture the entire cleansed results from EDQ.

Changes

 

Cause

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