External Key Generation Function

This function allows you to enable third party vendors to generate deduplication keys in Siebel CRM. This topic describes the functions that set parameters for external deduplication key.

To facilitate the matching process, Siebel CRM generates a match key for each record (Account, Contact, and Prospect) using the token expression defined in the Vendor Parameter. This approach has some limitations, foremost is each record can only have one match key; also, the keys have a simple general format that do not take advantage of each vendor’s specific matching process. The match keys are stored in Siebel CRM key tables for use in the matching candidate selection step, where Siebel queries the key table for potential matching candidates that have similar key value as the driver record.

Furthermore, Oracle Enterprise Data Quality (OEDQ) generates its own match keys; it can generate multiple match keys per driver record, and each key has an associated key priority number to indicate how significant the key is in the matching process. For this reason, a new optional function is added to the Universal Connector API to allow Siebel CRM to call third party software vendor to get the set of match keys generated by the vendor. Any vendor who can generate the match keys itself, can implement this function to take advantage of this new feature.

The OEDQ connector is further enhanced to improve matching effectiveness, bringing stronger candidates to the top of the list by sorting on the Key Priority Number field. Not only does this improve matching accuracy but it also provides better performance.

OEDQ provides richer information about the match result such as the matching rule used by the engine, and the list of attributes that contributed to the match.