Table of Contents

Search

  1. Preface
  2. Using the Designer
  3. Working with Sources
  4. Working with Flat Files
  5. Working with Targets
  6. Mappings
  7. Mapplets
  8. Mapping Parameters and Variables
  9. Working with User-Defined Functions
  10. Using the Debugger
  11. Viewing Data Lineage
  12. Comparing Objects
  13. Managing Business Components
  14. Creating Cubes and Dimensions
  15. Using the Mapping Wizards
  16. POWERCENTERHELP
  17. Datatype Reference
  18. Configure the Web Browser

Maintaining the Effective Date Range

Maintaining the Effective Date Range

The Integration Service generates a begin date for each new and changed dimension it inserts into the target, using the current system date. The end date for these dimensions is NULL.
Each time the Integration Service inserts a changed dimension, it updates the previous version of the dimension in the target, using the current system date to fill the previously null end date column.
As a result, all current dimension data in the Type 2 Dimension/Effective Date Range target have null values in the PM_END_DATE column. All previous versions of dimension data have a system date in PM_END_DATE to indicate the end of the effective date range for each version.
For example, the following dimensions are current dimension data since their end date columns are null:
PM_PRIMARYKEY
ITEM
STYLES
PM_BEGIN_DATE
PM_END_DATE
4325
Sock
13
9/1/98
-
5401
Boot
20
10/1/98
-
When the Integration Service finds updated versions of these dimensions in the source, it inserts them into the target, using the system date to indicate the beginning of their effective date ranges and leaving the end dates null.
The Integration Service also updates the existing versions in the target, entering the system date to end the effective date range:
PM_PRIMARYKEY
ITEM
STYLES
PM_BEGIN_DATE
PM_END_DATE
4325
Sock
13
9/1/98
6/1/99
5401
Boot
20
10/1/98
6/1/99
6345
Sock
18
6/1/99
-
6346
Boot
25
6/1/99
-


Updated June 25, 2018