Configuration Guide

10.3 HotFix 1

Back Next

External Match Input (EMI) Table

Each base object has an External Match Input (EMI) table for External Match jobs. This table uses the following naming pattern:

C_BaseObject_EMI

where BaseObject is the name of the base object associated with this External Match job.

When you create a base object, the Schema Manager creates the associated EMI table, and adds the following system columns:

Column Name	Data Type	Size	Description
SOURCE_KEY	VARCHAR	50	Used as part of a three-column composite primary key to uniquely identify this record and to map to records in the C_`BaseObject`_EMO table.
SOURCE_NAME	VARCHAR	50	Used as part of a three-column composite primary key to uniquely identify this record and to map to records in the C_`BaseObject`_EMO table.
FILE_NAME	VARCHAR	50	Used as part of a three-column composite primary key to uniquely identify this record and to map to records in the C_`BaseObject`_EMO table.

When you populate the EMI table, at least one of the system columns must contain data. The column names are non-restrictive, which means that they can contain any identifying data if the composite three-column primary key is unique.

In addition, when you configure match rules for a particular column, such as Person_Name or Exact_Cust_ID, the Schema Manager adds that column to the C_BaseObject_EMI table.

To view the columns of an external match table in the Schema Manager, expand the External Match Table
node.

The records in the EMI table are analogous to the match batch used in Match jobs. The match batch contains the set of records that match with the rest of the base object records. The difference is that, for Match jobs, the match batch records reside in the base object, while for External Match, these records reside in a separate input table.

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

External Match Input (EMI) Table

External Match Input (EMI) Table