SUSPECT
The SUSPECT table contains suspect duplicates (contacts that are possible duplicates of each other) that a particular contact has in the database.
This table is used by the following domain.
| Name | Comment | Datatype | Null Option | Is PK |
|---|---|---|---|---|
| SUSPECT_ID | A unique, system-generated key that identifies a suspect in the system. | BIGINT | Not Null | Yes |
| CONT_ID | A unique, system-generated key that identifies a party in the system. | BIGINT | Not Null | No |
| SUSPECT_CONT_ID | A unique, system-generated key that identifies a party in the system. | BIGINT | Not Null | No |
| SUSP_ST_TP_CD | Suspect Status Type code indicates the current situation for a particular suspect record. For example, suspect duplicate, not duplicate, under investigation, etc. | BIGINT | Not Null | No |
| SOURCE_TP_CD | The source of the Suspect Reason Code (system-marked or user-marked). | BIGINT | Not Null | No |
| SUSP_REASON_TP_CD | The field that caused the data match to occur. | BIGINT | Null | No |
| MATCH_RELEV_TP_CD | Identifies party match relevancies, providing a description of which elements were matched. | BIGINT | Null | No |
| ADJ_ACTION_CODE | When a PARTY is identified as a SUSPECT, the SUSPECT(party ID) can have relevancy scores dictating a 'B' action type. The client might take into account relationships or roles on a policy that can adjust the SUSPECT to an 'A' type action or alternatively a 'C' type SUSPECT. | CHAR(2) | Null | No |
| ADJ_ACTION_TP_CD | Identifies the business reasons for the action code on the suspect identification being modified. | BIGINT | Null | No |
| CREATED_BY | The ID of the user, system, or other entity that created the data. | VARCHAR(20) | Null | No |
| LAST_UPDATE_DT | When a record is added or updated, this field is updated with the date and time. On subsequent updates, the system uses this information to ensure that the update request includes a matching date and time on this field; if it does not, the update fails. | TIMESTAMP | Not Null | No |
| LAST_UPDATE_USER | The ID of the user who last updated the data. | VARCHAR(20) | Null | No |
| LAST_UPDATE_TX_ID | A unique, system-generated key that identifies the specific transaction within the log system that either created, updated, or deleted the data row. | BIGINT | Null | No |
| MATCH_ENG_TP_CD | Identifies the matching engine to use for matching parties. | BIGINT | Null | No |
| WEIGHT | The calculated weight used by the matching engine. | DECIMAL(17,3) | Null | No |
| CUR_SUSPECT_TP_CD | Identifies the current suspect type. | BIGINT | Null | No |
| CUR_MTCH_ENG_TP_CD | The current matching engine. | BIGINT | Null | No |
| PERSON_ORG_CODE | Indicates the Party type of the suspect duplicates. | CHAR(1) | Null | No |
| INACTIVATED_DT | Indicates the earliest inactivated date of the two suspect duplicate parties. | TIMESTAMP | Null | No |
| ACCESS_TOKEN_VALUE | An access token is a means to protect a resource from unauthorized user or group access. When an access token value is associated with a resource such as a database record, only users or groups that are assigned that token can have access to that resource. | VARCHAR(50) | Null | No |