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

Rule 15. Add an Effective Period

Rule 15. Add an Effective Period

You can add a record version with a new effective period.
If the following conditions exist, rule 15 applies:
  • A record version with a new effective period is added to the cross-reference table.
  • The specified effective period creates a gap between effective periods.
  • The base object property setting does not allow noncontiguous effective periods.
  • The timeline action is set to 4.
Rule 15 ensures the following
MDM Hub
behavior:
  • The cross-reference record with the new effective period is loaded.
  • If you want to fill gaps when contiguity is broken, the effective period of the existing record version is extended to fill the gap between record versions.
  • If you do not want to fill gaps when contiguity is broken, the new record version is not inserted and an error is generated. During a batch load, the record is moved to the reject table.
The following image shows the addition of a record to the cross-reference table when contiguity is enabled for the associated base object:
The addition of a record to the cross-reference table when contiguity is enabled for the associated base object.

0 COMMENTS

We’d like to hear from you!