UCM Execution Is Ignoring "Disable Cleansing Flag" = 'Y' On Incoming Addresses Message And Still Cleansing The Address Anyway

(Doc ID 2329269.1)

Last updated on NOVEMBER 16, 2017

Applies to:

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

Symptoms

PRODUCT VERSION

Siebel 15.18 [IP2015] version, Universal Customer Master


BEHAVIOR

A requirement was to disable address cleansing as there were some issues with the DQ Vendor software not returning properly cleansed addresses. Thus, the approach was to disable address cleansing to allow users to manually fix the address after it is inserted uncleansed into the Siebel application.

As part of this effort, the "Disable Cleansing Flag" field was exposed on the addresses (via the S_ADDR_PER.DISABLE_CLEANSE_FLG) on the Siebel Client UI Admin Data -> Addresses list view. When this field/flag is Y on the UI, the address is not getting sent from Siebel to EDQ for cleansing, this is the desired and working behaviour.

However, when this same field and value Y was passed in an inbound web service call to UCM, UCM ignores this "Disable Cleansing Flag" = "Y" and still sends the incoming address to EDQ for cleansing, DQ Vendor returns cleansed address to UCM, inserts the cleanse address into the record. This is not the desired result.


STEPS

The issue can be reproduced at will with the following steps:

1. Expose the "Disable Cleansing Flag" field was on the addresses (via the S_ADDR_PER.DISABLE_CLEANSE_FLG) on the Siebel Client UI Admin Data -> Addresses list view. Go to the Siebel Client UI > create a new address and check this flag to Y > save the address > the address is not getting sent from Siebel to EDQ for cleansing, this is the desired and working behaviour.

2. Add the same field to the UCM IO/Address IC > include the same IC field in the inbound message with the value of Y. UCM ignores this "Disable Cleansing Flag" = "Y" and still sends the incoming address to EDQ for cleansing, DQ Vendor returns cleansed address to UCM, inserts the cleanse address into the record. This is not the desired result.


BUSINESS IMPACT

The above causes inconsistency with how the address is processed and that the same "Disable Cleansing Flag" = Y is not handled by the Siebel Client and UCM consistently, ie. UCM processing is ignoring it and not honoring its value.

 

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