Bookshelf Home | Contents | Index | PDF     

Siebel Data Quality Administration Guide > Siebel Data Quality Concepts >

Data Model for the SDQ Matching Server

This topic provides information about the database tables that the SDQ Matching Server interacts with. Table 4 lists the tables that are relevant to data matching. Table 5 lists the database operations that result from the various data matching functions.

Table 4. Tables Used by SDQ Matching Server
Siebel Table Name
Usage by SDQ Matching Server

S_CONTACT

Stores contact records.

S_DEDUP_RESULT

Stores the results of data matching. The following fields are of interest:

  • DUP_OBJ_ID field. Stores the row ID of a potential duplicate record.
  • OBJ_ID field. Stores the row ID of the master record (the record for which matching was performed).
  • OBJ_NAME field. Stores the name of the business component for which data matching was performed, for example, Account.
  • TOT_SCORE_VAL field. Stores the match score of the potential duplicate record.

S_ORG_DEDUP_KEY

Stores match keys for account records.

S_ORG_EXT

Stores account records.

S_PER_DEDUP_KEY

Stores match keys for contact records.

S_PRSP_CONTACT

Stores prospective contact records.

S_PRSP_DEDUPKEY

Stores match keys for prospective contact records.
Table 5. Database Operations Resulting from SDQ Matching Functions
Matching Function
Database Operation

Key Generation or Key Refresh
  • Data creation in one of the following tables:
    • S_ORG_DEDUP_KEY (Account records)
    • S_PER_DEDUP_KEY (Contact records)
    • S_PRSP_DEDUPKEY (List Mgmt Prospective Contact records)
  • Data update in one of the following tables:
    • S_CONTACT (Contact records)
    • S_ORG_EXT (Account records)
    • S_PRSP_CONTACT (List Mgmt Prospective Contact records)

      The DEDUP_KEY_UPD_DT column is updated.

Matching (DeDuplication)
  • Data lookup in one of the following tables:
    • S_ORG_DEDUP_KEY (Account records)
    • S_PER_DEDUP_KEY (Contact records)
    • S_PRSP_DEDUPKEY (List Mgmt Prospective Contact records)
  • Data creation in the S_DEDUP_RESULT table
  • Data update in one of the following tables:
    • S_CONTACT (Contact records)
    • S_ORG_EXT (Account records)
    • S_PRSP_CONTACT (List Mgmt Prospective Contact records)

      The DEDUP_LAST_MTCH_DT column is updated.

Merging
  • Data deletion in the S_DEDUP_RESULT table
  • Data update and deletion in one of the following tables:
    • S_CONTACT (Contact records)
    • S_ORG_EXT (Account records)
    • S_PRSP_CONTACT (List Mgmt Prospective Contact records)
    
Siebel Data Quality Administration Guide Copyright © 2006, Oracle. All rights reserved.