Understanding Sun Master Index Processing (Repository)

SBYN_POTENTIALDUPLICATES

This table maintains a list of all records that are potential duplicates of one another. It also maintains a record of whether a potential duplicate pair has been resolved or permanently resolved. The differences in data types between Oracle and SQL Server are noted in Table 16. The Oracle type is on the first line, and the SQL Server type is on the second.

Table 16 SBYN_POTENTIALDUPLICATES Table Description

Column Name 

Data Type 

Description 

POTENTIALDUPLICATEID

VARCHAR2(20) 

Varchar(20) 

The unique identification number of the potential duplicate transaction. 

WEIGHT

VARCHAR2(20) 

Varchar(20) 

The matching weight of the potential duplicate pair. 

TYPE

VARCHAR2(15) 

Varchar(15) 

This column is reserved for future use. 

DESCRIPTION

VARCHAR2(120) 

Varchar(120) 

A description of what caused the potential duplicate flag. 

STATUS

VARCHAR2(15) 

Varchar(15) 

The status of the potential duplicate pair. The possible values are: 

  • U – Unresolved

  • R – Resolved

  • A – Resolved permanently

HIGHMATCHFLAG

VARCHAR2(15) 

Varchar(15) 

This column is reserved for future use. 

RESOLVEDUSER

VARCHAR2(30) 

Varchar(30) 

The user ID of the person who resolved the potential duplicate status. 

RESOLVEDDATE

DATE 

datetime 

The date the potential duplicate status was resolved. 

RESOLVEDCOMMENT

VARCHAR2(120) 

Varchar(120) 

Comments regarding the resolution of the duplicate status. This is not currently used. 

EUID2

VARCHAR2(20) 

Varchar(20) 

The EUID of the second record in the potential duplicate pair. 

TRANSACTIONNUMBER

VARCHAR2(20) 

Varchar(20) 

The transaction number associated with the transaction that produced the potential duplicate flag. 

EUID1

VARCHAR2(20) 

Varchar(20) 

The EUID of the first record in the potential duplicate pair.