Information on Address Validation and the Values of field "Cleanse Verified Flag" and "Validation_Status"
(Doc ID 1334771.1)
Last updated on MARCH 02, 2017
Applies to:Siebel CRM - Version 188.8.131.52  and later
Information in this document applies to any platform.
In UCM 8.2 (Siebel 184.108.40.206 and higher with ACR 437 and ACR 475 or Siebel 220.127.116.11 and higher when the Incremental Repository Merge has been applied) using Address Standardization Module (ASM) the Siebel Boolean field "Cleanse Verified Flag" on the CUT Address BC is set to "Y" when the "validation_status" returned to Siebel by ASM in the XML file is equal to a value of 2 or greater. When the validation_status = 0 or 1 then it is left at the default value of "N". This is the same behaviour for the ASM Third Party Address Doctor versions 4.x and 5.x. The field "Cleanse Verified Flag" is stored in the table S_ADDR_PER and column VERIFIED_FLG.
The Cleanse Verified Flag = Y indicates that the address needs to be checked and corrected manually by the Siebel user as ASM (Address Doctor) was not able to confirm that it is correct (validation status 0) and also not able to clean the address (validation status 1). The address records with the Cleanse Verified Flag = Y are visible in the view Administration - Data Quality > Incomplete Address, where it is used in the Search Specifcation for the applet "Incomplete Address Applet" in Tools.
In Siebel 18.104.22.168 and higher (UCM 8.2) there are new ASM vendor parameters "DQ Cleanse High Delivery Address" and "ASM High Deliverability Return Code". If the High Delivery Address is enabled and the Return Code is set to 0,1,2 then Bookshelf states that Siebel will now cleanse the entered address with the returned ASM address when the validation status is 2. However the Cleanse Verified Flag in Siebel is still set to "Y" although the address has been cleansed. This appears to be a conflict as the address is no longer incomplete and does not require manual correction.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|