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: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Consensus Delete

Consensus Delete

The
MDM Hub
detects hard-deleted records based on the delete status of a record in all the contributing source systems. You use consensus delete in conjunction with direct delete.
The
MDM Hub
flags a base object record as inactive if the record is deleted from all the contributing source systems. All the cross-reference records that are associated with the base object record must be in the partially inactive state.
Perform a consensus delete when the source data comes from multiple source systems. The
MDM Hub
flags a record for delete, when there is a consensus among all the source systems to delete a record. The
MDM Hub
flags records from source systems as partially inactive. The
MDM Hub
then uses trust and validation rules to determine another source system record to overwrite the base object record. If delete dates are present, the
MDM Hub
uses delete dates to determine another source system record to overwrite the base object record.
When you need consensus on the delete state of records from all source systems, implement the Post Landing user exit to call direct delete. Also, the Post Staging user exit must call the consensus delete logic for a consensus delete of base object records.

0 COMMENTS

We’d like to hear from you!