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

Support Tables Used in the Match Process

Support Tables Used in the Match Process

The match process uses the following support tables:
Table
Description
match key table
Contains the match keys that were generated for all base object records. A match key table uses the following naming convention:
C_
baseObjectName
_STRP
where
baseObjectName
is the root name of the base object.
Example: C_PARTY_STRP.
match table
Contains the pairs of matched records in the base object resulting from the execution of the match process on this base object.
Match tables use the following naming convention:
C_
baseObjectName
_MTCH
where
baseObjectName
is the root name of the base object.
Example: C_PARTY_MTCH.
match flag audit table
Contains the userID of the user who, in Merge Manager, queued a manual match record for automerging.
Match flag audit tables use the following naming convention:
C_
baseObjectName
_FHMA
where
baseObjectName
is the root name of the base object.
Used only if Match Flag Audit Table is enabled for this base object.

0 COMMENTS

We’d like to hear from you!