MDM Flashcards
Survivorship Techniques
Three types of survivorship techniques are available: most recent, most frequent, and most complete
Master data vs transactional data
This relationship between master data and transactional data may be fundamentally viewed as a noun/verb relationship. Transactional data captures the verbs, such as sale, delivery, purchase, email and revocation, while master data captures the nouns. This is the same relationship data warehouse facts and dimensions share.
IT Scenarios in MDM
Consolidation is use to identify duplicate records and merge them into one record.
Harmonization is the process of pushing the new cleansed data back out to your partner systems.
Central master data management means you create records within MDM and then you distribute (Syndicate) this centrally created data to your Remote Systems.
MDM Canonical Model
A canonical model may be used for communication between different formats used by enterprise systems.
A canonical model may be used for communication between the various enterprise systems. This design pattern is a form of enterprise application architecture that can be used for communication between different data formats.
It involves creating a data model which supersedes all the others and creating a ‘translator’ module or layer to/from which all existing systems exchange data with other systems.
System of Record (SOR)
The system of record (SOR) is the authoritative data source for a given piece of data. It is the primary repository of that data in the organization
The system of record is defined as the enterprise system that acts as the most authoritative source for a given piece of data.
It is the primary repository of correct, durable, restorable and disaster-ready data.
Golden/Single Source of Truth (SSOT)
The golden source of truth, also called the single source of truth (SSOT), is a trusted data source that provides a complete picture of a given piece of information.
It is typically the master hub that is used for data consolidation in a master data management system.
An SSOT system provides authentic and relevant data that other systems in an organization can refer to.
SSOT & SOR
The master data system can be established as the single source of truth (SSOT), while the system of record (SOR) can be defined based on specific data attributes.
Data Survivorship Rules
For merging duplicate records into a single golden record in the master hub, data survivorship rules can be utilized.
These rules can determine which data elements from the duplicate records should be considered to create the golden record.
Data elements that are more populated, more accurate (based on comparison with a third-party database) or were changed more recently can be picked during the merge process.
Empty, null, ambiguous and invalid field values can be ignored.
DATA MATCHING TECHNIQUES
Deterministic matching or probabilistic matching can be utilized to match records that exist in different systems for identifying duplicates.
Probabilistic matching should be preferred due to higher accuracy in matching records. The duplicate records can then be merged in the master hub.
DATA SURVIVORSHIP TECHNIQUES
Survivorship of data attributes can depend on several factors, including trust score, decay, validation, and precedence.
Survivorship criteria can be based on accuracy, recency, frequency, and completeness of records. LIATION AND CONSOLIDATION
DATA RECONCILIATION AND CONSOLIDATION
Data from multiple systems, such as contact records from Salesforce and the ERP system can be reconciled and consolidated in the master hub.
The information in the original record can be retained when the records are consolidated.
For example, the value of the ‘First Name’ field can be retained in both the systems.
Field History Tracking
Field History Tracking can be enabled for the Account object to track and display the new and old values of up to 20 fields in the History related list of the object.
Field history data can be accessed for up to 24 months or two years via the API.
Field Audit Trail
Field Audit Trail can be utilized to define a policy to retain archived field history data of up to 60 fields for up to 10 years.
Custom Metadata Types vs Custom Settings
Custom metdata types: It is possible to deploy custom metadata records using an unmanaged package. A developer can also use Apex to view, create, and update custom metadata records using SOQL. Can also be accessed using static methods like getAll(), which does NOT use SOQL and not count towards governor limits
Custom Settings: it is not possible to include custom settings data in a package. It would be necessary to populate the custom settings after installing the package.
Which MDM implementations style can be utilized to consolidate data from various source systems in a central hub and ensure that the data in the source systems are not modified?
Consolidation
