Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.3 HotFix 3
  • All Products

Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Configuration Guide

Configuration Guide

Back Next

Example of Hard Delete Detection for Consensus Delete

Example of Hard Delete Detection for Consensus Delete

Your organization has multiple source systems that provide data to a base object record. The records in each source system are deleted one after the other, and then the record from source system 1 is reactivated and is hard deleted again. The
MDM Hub
 needs to detect hard deletes in the source systems. If records are hard-deleted in all the source systems, the base object record is flagged as deleted.
The
MDM Hub
 will update the column values of the base object record based on the trust downgrades for the deleted source records. The records in all the source systems must be hard-deleted and the
MDM Hub
 must flag all the associated cross-reference records as partially inactive or inactive.

Records Before Hard Delete Detection

Before detecting hard deletes in the source systems, the delete flag for the base object record and the cross-reference records is active. The
MDM Hub
 merges 3 source records into one base object record. The first name comes from source system 2, the middle name comes from source system 3, and the last name from source system 1.
The cross-reference record before hard delete is detected in the source.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Bob
J
Jones
A
null
2
163
Robert
J
Jones
A
null
3
163
Bob
James
Jones
A
null
The base object record before hard delete is detected in the source.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
James
Jones
A
null

Records When Hard Delete Is Detected In Source 3

When there is a hard delete in a source system 3, the
MDM Hub
 performs the following tasks:
  1. Detects deleted source records from the landing table.
  2. Reinserts the column values for the deleted records into the landing table along with an inactive delete flag and the end date.
  3. Verifies if all the cross-reference records are inactive or partially inactive and updates the associated cross-reference records as partially inactive.
  4. Retains the middle name provided by the record from source system 3 in the base object until a source record with a higher trust score provides an update for that column.
The cross-reference records when hard delete is detected in the source system 3.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Bob
J
Jones
A
null
2
163
Robert
J
Jones
A
null
3
163
Bob
James
Jones
P
null
The base object record when hard delete is detected in source system 3.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
James
Jones
A
null

Records When Hard Delete Is Detected In Source 1

When there is a hard delete in a source system 1, the
MDM Hub
 performs the following tasks:
  1. Detects deleted source records from the landing table.
  2. Reinserts the column values for the deleted records into the landing table along with a delete flag and the end date.
  3. Verifies if all the cross-reference records are inactive or partially inactive and updates the associated cross-reference records as partially inactive.
  4. BVT is calculated and the base object reflects the value from source 1 for the middle name, which is John, as it has a higher trust score even though the record is partially deleted.
The cross-reference records when hard delete is detected in the source system 1.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Bob
John
Jones
P
null
2
163
Robert
J
Jones
A
null
3
163
Bob
James
Jones
P
null
The base object record when hard delete is detected in source system 1.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
John
Jones
A
null

Records When Hard Delete Is Detected In Source 2

When there is a hard delete in a source system 2, the
MDM Hub
 performs the following tasks:
  1. Detects deleted source records from the landing table.
  2. Reinserts the deleted records into the landing table along with a delete flag and the end date.
  3. Verifies if all the cross-reference records are inactive or partially inactive and updates the associated cross-reference records as inactive.
    At this point, no other source systems can provide an active status.
  4. If no other source systems can provide an active record, the base object record reflects an inactive state with an end date.
The end date contains the system date or the date that you provide when you determine the end date value.
The cross-reference records when hard delete is detected in the source system 2.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Bob
John
Jones
P
null
2
163
Robert
J
Jones
I
04/05/13
3
163
Bob
James
Jones
P
null
The base object record when hard delete is detected in source system 2.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
John
Jones
I
04/05/13

Records After the Source 1 Record Is Reactivated

If a record is reactivated in a source system, the
MDM Hub
 flags the base object record and the cross-reference record as active. The end date is null when the source record is active.
The source record in source system 1 is reactivated, and the
MDM Hub
 flags the associated cross-reference record as active. The end date is null when the record is active.
The cross-reference record after the hard deleted record in the source system 1 is reactivated.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Bob
John
Jones
A
null
2
163
Robert
J
Jones
I
04/05/13
3
163
Bob
James
Jones
P
null
The base object record after the hard deleted record in the source system 1 is reactivated.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
John
Jones
A
null

Records When Hard Delete Is Detected Again In Source 1

When there is a hard delete in a source system 1, the
MDM Hub
 performs the following tasks:
  1. Detects deleted source records from the landing table.
  2. Reinserts the column values for the deleted records into the landing table along with a delete flag and the end date.
  3. Verifies if all the cross-reference records are inactive or partially inactive and updates the associated cross-reference records as inactive.
    At this point, no other source systems can provide an active status.
  4. The base object record reflects an inactive state with an end date.
The end date contains the system date or the date that you provide when you determine the end date value.
The cross-reference record when hard delete is detected again in source system 1.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Bob
John
Jones
I
04/05/13
2
163
Robert
J
Jones
I
04/05/13
3
163
Bob
James
Jones
P
null
The base object record when hard delete is detected again in source system 1.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
John
Jones
I
04/05/13
0 COMMENTS
We’d like to hear from you!