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

Delete Flag Values of Base Objects

Delete Flag Values of Base Objects

When you define how to consolidate data in base objects, you need to identify the delete flag and determine the delete flag values.
The
MDM Hub
has default delete flag values. You can configure the
MDM Hub
to provide an end date value along with a delete flag for base object records.
Base objects have the following default delete flag values:
Active
Indicates that the record is active in all source systems. To change the value, set the value in the DELETE_FLAG_VAL_ACTIVE column to some other value. Default is A.
Inactive or fully deleted
Indicates that the record is hard-deleted in all source systems. To change the value, set the value in the DELETE_FLAG_VAL_INACTIVE column to some other value. Default is I.
Partially deleted
Indicates that the record is deleted in some source systems. To change the value, set the value in the DELETE_FLAG_VAL_PARTIAL column to some other value. Default is P.
Determine the base objects that need delete flags and possibly end dates. Ensure that you include the appropriate columns in the landing tables and staging tables associated with the base objects. Also, verify that you configured the hard delete detection table in the repository to detect hard deletes from the staging table.

0 COMMENTS

We’d like to hear from you!