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

Batch Unmerge

Batch Unmerge

You can unmerge records that were merged by a previous process. Use the ExecuteBatchUnmerge SIF API to batch unmerge records.
You can batch unmerge records that were consolidated by the following operations:
  • Automerge batch job.
  • Manual merge.
  • Manual record edit.
  • Load by ROWID_OBJECT.
  • Insert or update cross-reference records with the Put SIF API.
The ExecuteBatchUnmerge SIF API does not remove match records for the unmerged object that relate to parent records or related child tables. Use the list of unmerged records in table TEST_OUTPUT_TBL to remove these match records. The MDM Hub differentiates unmerged records from manually added records. By default, the MDM Hub assigns a value of 0 for manually added records. The MDM Hub assigns a value other than 0 for unmerged records in table TEST_OUTPUT_TBL in the EXPLODE_NODE_IND column.
You can also add the EXPLODE_NODE_IND column to the input table. If you set EXPLODE_NODE_IND to 1, the MDM Hub tries to unmerge the entire base object.
For more information about the ExecuteBatchUnmerge SIF API, see the
Multidomain MDM Services Integration Framework Guide
.

0 COMMENTS

We’d like to hear from you!