|Bookshelf Home | Contents | Index | PDF|
The SDQ Universal Connector and the SDQ Matching Server support data matching on the Account, Contact, and List Mgmt Prospective Contact business components. For each type of record, data matching is performed for fields that are specified in user properties for the business component. These user properties specify the mapping between the Siebel field names and the vendor field names. For information about the preconfigured field mappings for SSA, see Preconfigured SSA Field Mappings, and for Firstlogic, see Preconfigured Field Mappings.
SDQ performs matching for some fields, for example, addresses, that have multi-value group (MVG) associations, however, SDQ does not match on MVGs. Therefore when performing matching for a contact, SDQ checks only the primary address for each contact record and does not consider other addresses.
In real-time data matching, whenever an account, contact, or prospect record is committed to the database, a request is automatically submitted to the Deduplication business service. The business service communicates with third-party data quality software, which checks for possible matches to the newly committed record and reports the results to the Siebel application.
In batch mode data matching, you first start a server task to generate or refresh the keys, and then start another server task to perform data matching. For information about performing batch mode data matching, see Matching Data Using Batch Jobs.
|Siebel Data Quality Administration Guide||Copyright © 2006, Oracle. All rights reserved.|