UCM Matching With OEDQ Doesn't Use Address Information When Inserting a Record
Last updated on MARCH 02, 2017
Applies to:Siebel Financial Services CRM - Version 184.108.40.206.10 [IP2013] and later
Information in this document applies to any platform.
When using Siebel UCM version 220.127.116.11 with QF2190 or 18.104.22.168 with OEDQ 11 and try to insert a new record in Siebel the address information is not considered when it generates the matching keys.
This can cause existing records to not be found and also bad keys are getting generated at S_DQ_ORG_KEY where none of them contains address info.
Steps to reproduce this issue:
1 - Create a new account and a new address for the account using the Siebel UI > Accounts List View > new record: e.g.
Do not save or step off the the record yet, go to the bottom applet > open the address mvg > left side > New button > enter the new address information
2 - Then, step off the Account record to save it, it will get cleansed at this point.
3 - Check the keys at S_DQ_ORG_KEY and it will be observed about 4 records in this table (this may depend on the clusterlevel being used) but none of them contains address info.
If main0.log from OEDQ connector is analyzed it can be observed that during insert no address is considered and a line similar to this one can be noticed:
FINEST: 30-Oct-2014 13:52:46: get dedup keys in=<DriverRecord website= entityid=1-S79K languages=ENU subname=CA phone= name=SIEBEL taxnumber= vatnumber=>
If an update is issued for the same record the address information can be observed:
FINEST: 30-Oct-2014 16:30:49: dedup in=<DriverRecord website= entityid=3-CP1C3C languages=ENU subname=CA phone= name=Siebel taxnumber= vatnumber= <x <x city=London country=United Kingdom address1=80 Doverst Mayfair address2=80 Doverst Mayfair>>>
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms