Informatica MDM SaaS Foundation key terms

A modeled object in MDM SaaS that represents a real-world thing such as a customer, product, or supplier, and holds the master records, its fields, relationships, and validation rules.

The metadata definition of a business entity: its fields, field groups, data types, mandatory rules, lookups, and relationships. Deployed into the MDM SaaS tenant to create the entity structure.

A logical grouping of fields inside a business entity model, used to organize related attributes and to control layout and access at a granular level.

The single trusted, consolidated version of a business entity instance produced by matching and merging source records, used as the authoritative value across downstream systems.

A record loaded into MDM SaaS from a source system before consolidation. It retains its source lineage and participates in match and merge but is not itself the trusted master record.

A configurable set of criteria that compares field values between records to decide whether they refer to the same real-world entity, using exact, fuzzy, or phonetic comparison logic.

A derived, normalized value computed from one or more source fields (for example a cleaned name or address key) that matching compares instead of raw input, improving accuracy and performance.

The score boundary that determines whether a candidate pair is treated as a match, a possible match for review, or a non-match, tuned to balance false positives and false negatives.

A workflow task where a data steward examines candidate record pairs that fall in an uncertain score range and decides whether they should be linked or kept separate.

Configuration that determines, field by field, which surviving value is chosen when records are consolidated, for example most recent, most frequent, longest, or source-priority based.

A per-source or per-field confidence setting used in merge decisions so that values from more reliable systems or stewards outrank values from less trusted origins.

The stored link between a master record and the individual source records (and their source keys) that contributed to it, enabling lineage, unmerge, and downstream key resolution.

The operation of separating records that were previously consolidated into one master record, restoring them as distinct entities when matching or stewardship decisions were wrong.

The step that standardizes, corrects, and enriches incoming values before matching and storage, such as normalizing addresses, parsing names, and applying validation or reference data.

A configurable validation or transformation check applied to entity fields to detect missing, invalid, or non-conforming values and drive remediation or scorecards.

The business role responsible for reviewing match candidates, resolving data quality exceptions, approving changes, and maintaining the accuracy of master data in MDM SaaS.

A defined parent-child relationship structure among entity records, such as an organizational rollup or product classification, used for reporting and relationship navigation.

A modeled association between two business entities or records, with its own cardinality and attributes, such as a customer linked to its accounts or contacts.

Controlled code lists and lookup values (for example country codes or industry classifications) that standardize entity field values and are managed centrally in MDM SaaS.

A configured field that restricts input to values from a reference data set, enforcing consistent coded values and enabling display of the code's description.

An application or dataset that supplies records to MDM SaaS, identified by a source identifier used for lineage, trust scoring, and cross-reference tracking.

The process of loading source data into MDM SaaS, typically through batch file loads or API-based near-real-time feeds, followed by validation and staging before consolidation.

A scheduled or on-demand run that processes data in bulk, such as loading a source file, executing match and merge, or exporting master records to a target.

A programmatic interface exposed by MDM SaaS for creating, reading, updating, and searching records and for triggering processes, used for real-time integration with other systems.

A prebuilt or configured MDM SaaS application that presents a consolidated, multi-domain view of an entity such as a customer, with related records, hierarchies, and insights in one interface.

The MDM SaaS application view that unifies customer records from multiple sources into a single profile showing identifiers, addresses, relationships, and related interactions for business users.

The overall structure of entities, fields, relationships, and reference data configured for a tenant, which defines what master data MDM SaaS stores and how it is linked.

The isolated MDM SaaS environment instance provisioned for an organization, containing its own configuration, data model, users, and master data separate from other customers.

A distinct deployment stage such as development, test, or production, each with its own tenant configuration, used to promote and validate changes before they reach production.

The act of publishing configuration changes, such as a modified business entity model or match rule, from a design state into a running environment where they take effect.

A named set of permissions assigned to users that controls which entities, records, fields, and actions they can view or change within MDM SaaS.

A work item assigned to a user or role in MDM SaaS, such as a match review, data quality exception, or approval request, tracked through a workflow inbox.

A configured sequence of steps, approvals, and assignments that governs how records or changes move through review and approval before becoming trusted master data.

The recorded history of changes to a record or configuration, capturing who changed what and when, used for compliance, troubleshooting, and stewardship accountability.

The capability to find records by identifiers or attribute values, including exact, partial, and fuzzy lookup, which business users rely on to locate and inspect master records.

The process of publishing master records or their changes out of MDM SaaS to downstream systems, either in bulk or as incremental updates via files or APIs.

The overall logic that decides which values survive into the master record when sources disagree, combining merge rules, trust scores, and recency or frequency preferences.

A category of master data managed in MDM SaaS, such as customer, product, supplier, or reference data, each typically modeled with its own entities and rules.