Addresses entered through Siebel Client UI are not being matched, cleansed and corrected as expected with EDQ Address Verification (Doc ID 1932956.1)

Last updated on OCTOBER 03, 2016

Applies to:

Siebel Universal Customer Master - Version 8.1.1.11 [IP2013] and later
Siebel Data Quality - Version 8.1.1.11 [IP2013] and later
Information in this document applies to any platform.
*** Checked for currency on OCT-03-2016 ***

Symptoms

PRODUCT VERSIONS:
---------------
Siebel 8.1.1.11 [23030]
EDQ 11.1.1.7.4
AV 14.2.0.0.0

ISSUE STATEMENT:
----------------
Customer uses Oracle EDQ Address Verification for address matching and cleansing. Siebel application has been set up to use EDQ Address Verification. When using Siebel client UI application to enter an address, customer observes that EDQ address verification triggers off when Street address or Zip Code field values are changed in the address pick applet. The verification isn't working/triggered off if the City or State fields in the address are being modified.

WHERE IT HAPPENED:
-------------------------------
The issue happens in customer's test environment.

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

1. Set up and configure Siebel application to use Oracle EDQ Address Verification for address cleansing/matching.

2. Launch Siebel client and create an address via the Sitemap > Administration - Data screen > Addresses View:

a. Create a new address: 161 Delaware Ave, Delmar NY

Save the record => address is cleansed into: 161 Delaware Ave, Delmar, NY, 12251, USA

b. Update the same address changing the City as: 161 Delaware Avenue, Rochester, NY, 12251, USA (keep the zip code as-is)

Save the record => address is cleansed into: 161 Delaware Ave, Rochester, NY, 12251, USA

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
------------------------------
Since the address verification isn't triggered off on every address field change, the address is not being cleansed and corrected as expected, leading to data inconsistency.

ERROR MESSAGE:
-------------------
There are no error messages that occurs with this issue, just the unexpected/undesired results being observed.

 

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