Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

External Match Output Table

External Match Output Table

Each base object has an external match output table that contains the output data for external match batch jobs. The
MDM Hub
drops and recreates the external match output table before the external match batch job runs.
The
MDM Hub
names the external match output tables C_<
base_object_name
>_EMO, where
base_object_name
is the name of the base object associated with the external match batch job.
The external match batch job populates the external match output table with match pairs. The external match job does not populate the match table. Each row in the external match output table represents a pair of matched records. One record in the pair comes from the external match input table while the other record in the pair comes from the base object. The primary key, which is the SOURCE_KEY concatenated with the SOURCE_NAME and FILE_NAME, identifies the record from the external match input table. The ROWID_OBJECT_MATCHED value identifies the record from the base object.
An external match output table contains the following columns:
Column Name
MDM Hub Data Type (Size)
Can Be Null
Description
SOURCE_KEY
VARCHAR (50)
 Yes
Maps back to the source record in table C_<
base_object_name
>_EMI.
SOURCE_NAME
VARCHAR (50)
 Yes
Maps back to the source record in table C_<
base_object_name
>_EMI.
FILE_NAME
VARCHAR (50)
Yes
Maps back to the source record in table C_
base_object_name
_EMI.
ROWID_OBJECT_MATCHED
CHAR (14)
No
ROWID_OBJECT of the record in the base object that matches the record in the external match input table.
ROWID_MATCH_RULE
CHAR (14)
Yes 
Identifies the match rule that the external match batch job used to determine the match.
AUTOMERGE_IND
NUMBER (38)
No
Specifies whether a record qualifies for automatic consolidation during the match process. AUTOMERGE_IND is one of the following values:
  • 0: Record does not qualify for automatic consolidation.
  • 1: Record qualifies for automatic consolidation.
  • 2: Records qualify for automatic matching but one or more of the records are in a PENDING state. A value of 2 occurs if you enable state management and you enable "Enable Match on Pending Records." Do not build groups with PENDING records. Leave PENDING records as individual matches.
The Automerge batch job processes any records with an AUTOMERGE_IND value of 1.
CREATOR
VARCHAR2 (50)
Yes 
User or process responsible for creating the record.
CREATE_DATE
TIMESTAMP
Yes
Date on which the record was created.

0 COMMENTS

We’d like to hear from you!