SBYN_OBJECT_NAME
|
Stores information for the parent objects associated with local
system records. This database table is named by the parent object
name. For example, a table storing company objects is named sbyn_company;
a table storing person objects is named sbyn_person. Only one table
stores parent object information for system records.
|
SBYN_OBJECT_NAMESBR
|
Stores information
for the parent objects associated with single best records. This database
table is named by the parent object name followed by “SBR”.
For example, a table storing company objects is named sbyn_companysbr;
a table storing person objects is named sbyn_personsbr. Only one table
stores parent object information for SBRs.
|
SBYN_CHILD_OBJECT
|
Stores information for child objects associated with local system
records. These database tables are named by their object name. For
example, a table storing address objects is named sbyn_address; a
table storing comment objects is named sbyn_comment. One database
table is created for each child object defined in the object structure.
|
SBYN_CHILD_OBJECTSBR
|
Stores
information for child objects associated with a single best record.
These database tables are named by their object name followed by “SBR”.
For example, a table storing address objects is named sbyn_addresssbr;
a table storing comment objects is named sbyn_commentsbr. One SBR
database table is created for each child object defined in the object
structure.
|
SBYN_APPL
|
Lists the applications with which each item in stc_common_header
is associated. Currently the only item in this table is eView.
|
SBYN_ASSUMEDMATCH
|
Stores information about records that were automatically matched
by the master index application.
|
SBYN_AUDIT
|
Stores audit information about each time object information
is accessed from the MIDM.
Note –
If audit logging is enabled, this table can grow very
large and might require periodic archiving.
|
SBYN_COMMON_DETAIL
|
Contains
all of the processing codes associated with the items listed in sbyn_common_header.
|
SBYN_COMMON_HEADER
|
Contains a list of the different types of processing codes used
by the master index application. These types are also associated with
the drop-down lists you can specify for the MIDM.
|
SBYN_ENTERPRISE
|
Stores the local ID and system pairs, along with their associated
EUID.
|
SBYN_MERGE
|
Stores information
about all merge and unmerge transactions processed from either external
systems or the MIDM.
|
SBYN_OVERWRITE
|
Stores information about fields that are locked for updates
in an SBR.
|
SBYN_POTENTIALDUPLICATES
|
Stores
a list of potential duplicate records and flags potential duplicate
pairs that have been resolved.
|
SBYN_SEQ_TABLE
|
Stores the sequential codes that are used in other tables in
the database, such as EUIDs, transaction numbers, and so on.
|
SBYN_SYSTEMOBJECT
|
Stores information about the system objects in the database,
including the local ID and system, create date and user, status, and
so on.
|
SBYN_SYSTEMS
|
Stores a list of systems in your organization, along with defining
information.
|
SBYN_SYSTEMSBR
|
Stores transaction information about an SBR, such as the create
or update date, status, and so on.
|
SBYN_TRANSACTION
|
Stores
a history of changes to each record stored in the database.
|
SBYN_USER_CODE
|
Like the sbyn_common_detail table, this table stores processing
codes and drop-down list values. This table contains additional validation
information that allows you to validate information in a dependent
field (for example, to validate cities against the entered postal
code).
|