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

Decrease Effective Period Example

Decrease Effective Period Example

Your organization has the CUSTOMER base object for which you track data change events. The CUSTOMER base object contains a record for John Smith who lives in New York effective 21 March 2014. You want to maintain contiguity of effective periods. You load a record version that is effective from 1 December 2014. Finally, you want to edit the record version that is effective from 1 December 2014 to be effective from 1 March 2015.
The cross-reference record for John Smith shows that he lives in New York from 21 March 2014.
Rowid XREF
Rowid Object
Customer ID
First Name
Last Name
City
Period Start date
Period End Date
1
2
25
John
Smith
New York
March 21, 2014
null
When you load the record version that is effective from 1 December 2014, the existing record version ends on 30 November 2014. The effective period of the existing record version decreases to avoid overlap and maintain contiguity.
After you load the record version that is effective from 1 December 2014, the cross-reference table shows that the existing record version for John Smith ends on 30 November 2014.
Rowid XREF
Rowid Object
Customer ID
First Name
Last Name
City
Period Start date
Period End Date
1
2
25
John
Smith
New York
March 21, 2014
November 30, 2014
2
2
25
John
Smith
Los Angeles
December 1, 2014
null
When you edit the record version that is effective from 1 December 2014 to be effective from 1 March 2015, the effective period decreases. Also, a gap is introduced between effective periods of the two record versions. The
MDM Hub
extends the end date of the record version that is adjacent to the version that you edit. The end date changes from 30 November 2014 to 28 February 2015 to fill the gap.
After you edit the effective date of the record version from 1 December 2014 to 1 March 2015.
Rowid XREF
Rowid Object
Customer ID
First Name
Last Name
City
Period Start date
Period End Date
1
2
25
John
Smith
New York
March 21, 2014
February 28, 2015
2
2
25
John
Smith
Los Angeles
March 1, 2015
null

0 COMMENTS

We’d like to hear from you!