Automatically links records that have qualified for autolinking during the match process and are flagged for autolinking (Automerge_ind=1).

Executes a continual cycle of a Match job, followed by an Automerge job, until there are no more records to match, or until the number of matches ready for manual consolidation exceeds the configured threshold. Used with merge-style base objects only.

Automatically merges records that have qualified for automerging during the match process and are flagged for automerging (Automerge_ind = 1). Used with merge-style base objects only.

Matches “externally managed/prepared” records with an existing base object, yielding the results based on the current match settings—all without actually modifying the data in the base object.

Prepares data for matching by generating match tokens according to the current match settings. Match tokens are strings that encode the columns used to identify candidates for matching.

Deletes data from the Hub based on base object / XREF level input.

Creates indexes for all the values of the searchable fields in a business entity type. Search uses the index to search for data within the searchable fields.

Matches records from two or more sources when these sources use the same primary key. Compares new records to each other and to existing records, and identifies potential matches based on the comparison of source record keys as defined by the match rules.

Copies records from a staging table to the corresponding target base object in the Hub Store. During the load process, applies the current trust and validation rules to the records.

Shows logs for records that have been manually merged in the Merge Manager tool. Used with merge-style base objects only.

Shows logs for records that have been manually unmerged in the Merge Manager tool.

Finds duplicate records in the base object, based on the current match rules.

Conducts a search to gather match statistics but does not actually perform the match process. If areas of data with the potential for huge match requirements are discovered,

Informatica MDM Hub

moves the records to a hold status, which allows a data steward to review the data manually before proceeding with the match process.

For data with a high percentage of duplicate records, compares new records to each other and to existing records, and identifies exact duplicates. The maximum number of exact duplicates is based on the Duplicate Match Threshold setting for this base object.

Allows the merge of multiple records in one job.

Reads the PROMOTE_IND column from an XREF table and changes to ACTIVE the state on all rows where the column’s value is 1.

Recalculates the BVT for the specified ROWID_OBJECT.

Shows logs of the operation where all matched records have been reset to be queued for match.

Executes the validation logic/rules for records that have been modified since the initial validation during the Load Process.

Copies records from a landing table into a staging table. During execution, cleanses the data according to the current cleanse settings.

Updates metadata for base objects. Used after a base object has been loaded but not yet merged, and subsequent trust configuration changes (such as enabling trust) have been made to columns in that base object. This job must be run before merging data for this base object.