This table maintains a record of each assumed match transaction that occurs in the master index application, allowing you to review these transactions and, if necessary, reverse an assumed match. This table can grow quite large over time and might require periodic archiving. The differences in data types between Oracle and SQL Server are noted in Table 9. The Oracle type is on the first line, and the SQL Server type is on the second.
Table 9 SBYN_ASSUMEDMATCH Table Description
Column Name |
Data Type |
Description |
---|---|---|
VARCHAR2(20) Varchar(20) |
The unique ID for the assumed match transaction. |
|
VARCHAR2(20) Varchar(20) |
The EUID into which the incoming record was merged. |
|
VARCHAR2(20) Varchar(20) |
The system code for the source system (that is, the system from which the incoming record originated). |
|
VARCHAR2(25) Varchar(25) |
The local ID of the record in the source system. |
|
VARCHAR2(20) Varchar(20) |
The matching weight between the incoming record and the EUID record into which it was merged. |
|
VARCHAR2(20) Varchar(20) |
The transaction number associated with the assumed match. |