Explanation of Informatica MDM Data Loading Stages?

A batch process loads data from a source system to the Hub Store in a series of processes which is mentioned below.

Land: ETL (extract-transform-load) tools or other external processes copy data from source systems to Siperian Hub. This process is called Landing because this data is stored in a table called Landing Table within Siperian Hub. Note: This process is performed by another ETL tool of your choice. This ETL tool is not part of the Siperian Hub product suite.

Stage: The Siperian Hub Stage process reads data from the landing tables, performs the specified cleansing, and moves the cleansed data to appropriate tables called staging tables. With the delta detection feature enabled, Siperian Hub only processes new or changed records and ignores unchanged records.

Load: The Siperian Hub Load process loads data from staging tables into corresponding Hub Store tables, called base objects. When new data overlaps existing data in the Hub Store, Siperian Hub uses trust rules to determine which value is more trustworthy.

Match: Siperian Hub's matching process identifies data that conforms to the matching rules you define. These rules define duplicate data for integration by Siperian Hub.

Consolidate: The Siperian Hub Consolidate process consolidates data identified as duplicates by the matching process.

What do you mean by Global Identifier (GBID) Columns in Informatica MDM?

A GBID (Global Business Identifier) ​​column contains a common identifier (key value) that can be used to uniquely and globally identify a record based on your business needs. Examples include:

An identifier defined by an application external to the MDM Hub. B. ERP (SAP or Siebel customer number) or CRM system.

An identifier defined by an external organization. B. Industry-specific codes (AMA numbers, DEA numbers, etc.) or government-issued identifiers (social security numbers, tax numbers, driver's license numbers, etc.).

Schema Manager allows you to define multiple GBID columns for a base object. For example, an employee table might contain columns for social security numbers and driver's license numbers, and a vendor table might contain tax numbers. A Master Identifier (MID) is a universal identifier generated by a system of reference or record used by others (CIFs, legacy hubs, MDM hubs, counterparty hubs, etc.). In the MDM Hub, MIDs are ROWID_OBJECTs that uniquely identify individual records from various source systems. GBID does not replace ROWID_OBJECT. The GBID externalizes the MDM Hub implementation by allowing data to be queried and accessed through a unique identifier of your choice (using SIF requests, as described in the Multi-Domain MDM Service Integration Framework Guide). Provides additional features that help you integrate with your system. Additionally, configuring GBID columns with predefined identifiers eliminates the need to define custom identifiers. GBIDs are useful for data traceability. Traceability maintains an overview of the data so you can determine where the data came from: which systems and which records in those systems contributed to the consolidated record. When he defines a GBID column in the base object, the schema manager uses the locator to create two columns in his table called and _GOV to keep track of his current and original GBID values. Suppose two customers (both with different taxpayer ID numbers) merged into one company, leaving one taxpayer ID number, and discontinuing the other. If you define your TaxID number column as GBID, the MDM Hub will help you track both current and historical taxpayer ID numbers, allowing you to access the data using historical values ​​(via SIF requests)