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 14. Update Effective Period

Rule 14. Update Effective Period

You can update the effective period of a record version.
If the following conditions exist, rule 14 applies:
  • The effective period of the existing cross-reference record is updated to either increase or decrease the effective period.
  • The data in the existing cross-reference record is unchanged.
  • The timeline action is set to 2.
Rule 14 ensures the following
MDM Hub
behavior:
  • The existing version of the cross-reference record is updated.
  • The existing version of the cross-reference record has the effective period that you specify with no change to data.
  • If the base object can have noncontiguous effective periods and you increase the effective period of a record version, the effective period of the prior adjacent and the later adjacent record versions decrease. To avoid overlapping of record versions, the MDM Hub decreases the effective period of the adjacent record version.
  • If the base object can have noncontiguous effective periods and you decrease the effective period of a record version, the
    MDM Hub
    introduces a gap between record versions.
  • If the base object must have contiguous effective periods, the
    MDM Hub
    extends or decreases the effective period of the adjacent record to maintain contiguity.
The following image shows an update to the effective period when contiguity is enabled for the base object:
An update to the effective period when contiguity is enabled for the base object.

0 COMMENTS

We’d like to hear from you!