Siebel Data Quality Administration Guide > Using the Value Match Method >

Scenario for Data Matching Using the Value Match Method

This topic gives one example of how you can invoke the Value Match business service method using Siebel Workflow. You may use the Value Match method differently, depending on your business model.

Your company needs to import a list of contacts into the Siebel application from other systems in your enterprise. To avoid introducing duplicate contacts in the Siebel application, you might consider invoking Siebel eScript through a workflow process to call the Value Match business service method. In this case, you invoke the Value Match method as a step in your contact import process. This step matches incoming contact information against the contacts within the Siebel business components. To prevent the introduction of duplicate information into the Siebel application, you add processing logic to your script based on the results returned from the value match parameter.

In this scenario, the business component name of the data entity that you want matched must be specified. For example, if you are using SSA to match contacts, then you set the business component name to Contact. Also, make sure the name/value pairs are Siebel field names that are configured for matching (the fields for contact matching appear as values for SSA Deduplication field 1, SSA Deduplication field 2, and so on, of the Contact business component user property). If the input contains fields that are not configured for matching, then those fields do not factor into the match. For example, if Personal Assistant is included in the list of values, but Personal Assistant is not a deduplication field of the matched business component, then this input is ignored.

For information about what the Value Match method does and how to use it, see Value Match Method.