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

Global Identifier (GBID) Columns

Global Identifier (GBID) Columns

A Global Business Identifier (GBID) column contains common identifiers (key values) that allow you to uniquely and globally identify a record based on your business needs. Examples include:
  • Identifiers defined by applications external to the
    MDM Hub
    , such as ERP (SAP or Siebel customer numbers) or CRM systems.
  • Identifiers defined by external organizations, such as industry-specific codes (AMA numbers, DEA numbers. and so on), or government-issued identifiers (social security number, tax ID number, driver’s license number, and so on).
To be configured as a GBID column, the column must be an integer, CHAR, VARCHAR, NCHAR, or NVARCHAR column type. A non-integer column must be exactly 255 characters in length.
In the Schema Manager, you can define multiple GBID columns in a base object. For example, an employee table might have columns for social security number and driver’s license number, or a vendor table might have a tax ID number.
A Master Identifier (MID) is a common identifier that is generated by a system of reference or system of record that is used by others (for example, CIF, legacy hubs, the
, counterparty hub, and so on). In the
, the MID is the ROWID_OBJECT, which uniquely identifies individual records from various source systems.
GBIDs do not replace the ROWID_OBJECT. GBIDs provide additional ways to help you integrate your MDM Hub implementation with external systems, allowing you to query and access data through unique identifiers of your own choosing (using SIF requests, as described in the
Multidomain MDM Services Integration Framework Guide
). In addition, by configuring GBID columns using already-defined identifiers, you can avoid the need to custom-define identifiers.
GBIDs help with the
of your data. Traceability is keeping track of the data so that you can determine its
—which systems, and which records from those systems, contributed to consolidated records. When you define GBID columns in a base object, the Schema Manager creates two columns in the cross-reference table,
_GOV, to track the current and original GBID values.
For example, suppose two of your customers (both of which had different tax ID numbers) merged into a single company, and one tax ID number survived while the other one became obsolete. If you defined the taxID number column as a GBID, the
could help you track both the current and historical tax ID numbers so that you could access data (via SIF requests) using the historical value.
does not perform any data verification or error detection on GBID columns. If the source system has duplicate GBID values, then those duplicate values will be passed into the


We’d like to hear from you!