Siebel Data Quality Administration Guide > Using Siebel Data Quality >

Real-Time Data Matching and Cleansing

In real-time mode, SDQ is called when you save a new or modified record. If both data cleansing and data matching are enabled for the same object manager, data cleansing runs first.

If data cleansing is enabled, a set of fields preconfigured to use data cleansing are standardized before the record is committed.

If data matching is enabled, and the new record is a potential duplicate, one of the following dialog boxes appears:

• Duplicate Accounts
• Duplicate Contacts
• Duplicate Prospects

You must then decide the fate of the new record, as follows:

• If you think the record is not a duplicate, close the dialog box or click Ignore All.

  This action commits the new record to the database.

• If you think the record is a duplicate, select the best-matching record from the dialog box using the Pick button.

  This action commits the new record to the database. The record that you choose becomes the surviving record, and is saved, but is then deleted by the merge process. Merging is performed as described in Sequenced Merges.

In real-time mode, if you enter two new records that have the same Name and Location, then an error message displays similar to the following: The same values for (Name, Location) already exist. To enter a new record, make sure that field values are unique. Real-time data matching prevents creation of a duplicate record in the following ways:

• If you are in the process of creating a new record, that record is not saved.
• If you are in the process of modifying a record, the change is not made to the record.

NOTE:  Only certain fields are configured to support data matching and data cleansing. If you do not enter values in these fields when you create a new record, or you do not modify the values in these fields when changing a record, data cleansing and data matching are not triggered. For more information about which fields are preconfigured for different business components, see Preconfigured Field Mappings for SSA.