Table of Contents


  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

Lookups for Foreign Key Columns

Lookups for Foreign Key Columns

You can use lookups to retrieve data from a parent table during load jobs. If a foreign key column in the staging table is related to the primary key in a parent table, configure a lookup to retrieve data from the parent table.
The target column in the lookup table must be a unique column such as the primary key.
After you define a lookup, if a load job is run on the base object, the MDM Hub looks up the Consumer code value of the source system in the primary key from the source system column of the Consumer code cross-reference table. After the lookup, the MDM Hub returns the customer type ROWID_OBJECT value that corresponds to the source consumer type.


The MDM Hub implementation in your organization has two base objects, a Consumer parent base object and an Address child base object. The base objects have the following relationships:
Consumer.Rowid_object = Address.Consumer_Fkey
In this case, the Consumer_Fkey is in the Address Staging table and it will look up data on some column.
The Address.Consumer_Fkey must be the same as Consumer.Rowid_object.
In this example, you can configure the following types of lookups:
  • Lookup to the ROWID_OBJECT, which is the primary key of the Consumer base object lookup table.
  • Lookup to the PKEY_SRC_OBJECT column, which is the primary key of the cross-reference table for the Consumer base object.
    In this case, you must also define the lookup system. If you configure a lookup to the PKEY_SRC_OBJECT column of a cross-reference table, point to parent tables associated with a source system that differ from the source system associated with this staging table.
  • Lookup to any other unique column, if available, in the base object or its cross-reference table.


We’d like to hear from you!