|Bookshelf Home | Contents | Index | PDF|
The SDQ Universal Connector assigns a single key to each account, contact, or prospect record. The key is calculated by reading data from specific fields in the record. The fields used depend on the business component configuration, but they can include account name, postal code, street address, or last name fields.
Beginning with version 184.108.40.206, the value of the match key depends on a business component-specific Dedup Token Expression, as shown in Table 3.
You can customize the Dedup Token Expression but it must be consistent with the internal matching logic of the vendor, which is different for each vendor. For optimal results therefore, change the values only after consulting the relevant vendor.
In earlier versions of the SDQ product, keys for a Universal Connector implementation were stored outside of the Siebel application, in files on the file system. Beginning with version 220.127.116.11, keys are stored in the DEDUP_TOKEN fields of the following tables:
|Siebel Data Quality Administration Guide||Copyright © 2006, Oracle. All rights reserved.|