Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. 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!