Before starting the modernization process, ensure that you are familiar with some of the key concepts of the MDM Hub.
Lookup tables
Lookup tables manage reference data in the MDM Hub. For example, the Country lookup table contains information about different countries. The business entity fields are associated to the columns in lookup tables.
Base objects
A base object is a table that stores master data, consolidated from cross-reference tables. For example, the Party base object can contain information about a person or organization. The business entity fields are associated to the columns in base objects.
Business entities
Business entities define the data model and are associated with base objects. For example, the Person business entity stores personal information, such as name, address, phone number, and email address of customers. The fields within the Person business entity are associated with the columns in the Party base object.
Match rule sets
The match rule sets in the MDM Hub include multiple match rules that identify duplicate records.
Survivorship
Survivorship determines field values with high trust scores for master records when duplicate records merge.
In MDM SaaS, you can rank source systems as part of the survivorship configuration. A higher rank indicates a higher trust for that source system. In contrast, survivorship configurations in the MDM Hub don't include ranking source systems. After modernizing objects, MDM SaaS automatically assigns the highest rank, Rank 0, to the Informatica Customer 360 source system by default. You can manually adjust the source system rankings in Business 360 Console.
Note: The survivorship configuration, along with the trust scores configured for fields, is modernized to MDM SaaS. However, the validation rules aren’t modernized because they aren't part of the survivorship configuration in MDM SaaS. In MDM SaaS, validation rules belong to data quality rule associations. Therefore, you must manually review and modify the validation rules in MDM SaaS after modernization.
Users and user roles
A user role contains a collection of privileges, and users assigned to the user role get those privileges.
Hierarchies and relationships
Hierarchies and relationships relate records. For example, you can relate a company as a subsidiary to another company. A hierarchical relationship creates a parent-child relationship. A non-hierarchical relationship relates two records without any hierarchy in the relationship. For example, you can create a non-hierarchical relationship between the family members.