Configuration Guide

10.3 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

Increase Effective Period Example

Your organization has the CUSTOMER base object for which you track data change events. The cross-reference table associated with the CUSTOMER base object contains a record for John Smith who lives in New York effective 21 March 2014 to 30 November 2014. The cross-reference table also contains another version of the record that is effective from 1 December 2014. You want to edit the record version that is effective from 21 March 2014 to 30 November 2014 to be effective up to 28 February 2015.

Before you edit the first record version, the second record version for John Smith is effective from 1 December 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 effective period of the record version to end on 28 February 2015 instead of 30 November 2014, the effective period is extended. The start date of the adjacent record version changes from 1 December 2014 to 1 March 2015 to avoid overlapping of record versions.

After you extend the start date of the first record version, the

MDM Hub

updates the second record version to start after the first version ends.

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

Rename Saved Search

Table of Contents

Configuration Guide

Configuration Guide

Increase Effective Period Example

Increase Effective Period Example