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.4 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Glossary

Configuration Guide

Configuration Guide

Back Next

Example of Hard Delete Detection for Direct Delete

Example of Hard Delete Detection for Direct Delete

Your organization has a single source system that supplies data to a base object record. You need to detect hard deletes in the source system to flag the base object record as deleted. The source system deletes a record, reactivates the record, and then deletes the reactivated record. The
MDM Hub
 accordingly flags the source record as deleted and end dated.

Records Before Hard Delete Detection

Before the
MDM Hub
 detects hard deletes in the source system, the delete flag for the base object record and the cross-reference record is active.
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
Robert
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 the Source

When there is a hard delete in a source system, the
MDM Hub
 performs the following tasks:
  1. Detects records that are deleted by comparing the landing table to the previous 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. Updates the cross-reference record as inactive 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 in the source.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Robert
James
Jones
I
04/05/13
The base object record when hard delete is detected in the source.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
James
Jones
I
04/05/13

Records After the Source Record Is Reactivated

If the record is reactivated in the 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 cross-reference record after the hard deleted record in the source system is reactivated.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Robert
James
Jones
A
null
The base object record after the hard deleted record in the source system is reactivated.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
James
Jones
A
null

Records When Hard Delete Is Detected Again In the Source

When there is a hard delete in a source system, the
MDM Hub
 performs the following tasks:
  1. Detects records that are deleted by comparing the landing table to the previous 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. Updates the cross-reference record as inactive 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 in the source.
Source
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
1
25
Robert
James
Jones
I
04/05/13
The base object record when hard delete is detected in the source.
Customer ID
First Name
Middle Name
Last Name
Del_Code
End Date
25
Robert
James
Jones
I
04/05/13
0 COMMENTS
We’d like to hear from you!