Siebel Data Quality Administration Guide > Configuring Siebel Data Quality > Mapping of Vendor Fields to Business Component Fields >

Adding a Field Mapping for Data Matching

In addition to the preconfigured fields that are used in data matching, you can configure your SDQ implementation to inspect certain additional fields during data matching, such as a date of birth field for Contacts, or a D-U-N-S number field for Accounts.

For the Universal Connector, if the key token expression changes, you must regenerate match keys. Therefore, if you are adding a new field and the new field is added to the token expression, you must generate the match keys.

The following procedure describes how to add a field mapping.

To add a field mapping for data matching

1. Navigate to the Administration - Data Quality screen, then the Third Party Administration view.
2. In the Vendor List, select the record for the required vendor.
3. Click the BC Vendor Field Mapping view tab.
4. In the BC Operation list, select the record for the required business component and operation
   • For example, to include a date of birth as a matching criterion, select the record for Contact and DeDuplication.
   • For example, to include a D-U-N-S number as a matching criterion, select the record for Account and DeDuplication.

     The field mappings are displayed in the Field Mapping list.

5. In the Field Mapping list, create a new record and complete the necessary fields as in the example shown in the following table.

   Business Component Field	Mapped Field
   Birth Date	Contact.Birth Date
   DUNS Number	Account.DUNS Number

6. If required, modify the corresponding real-time and batch mode data flows to incorporate the new field so that SDQ considers the new field during data matching comparisons.

   For example, for data matching that considers birth date, the correct data flows to modify are contact_match.xml and contact_incremental_match.xml.