Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

External Match Input (EMI) Table

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
Not Null
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.

0 COMMENTS

We’d like to hear from you!