Working with Effective Dates and Trees
This topic provides an overview of working with effective dates and trees.
User data are information collected from customers. When user data also has an effective date on key record, PeopleSoft Tree Manager checks that date to determine which dated record item belongs in the current dated tree. When only one dated item is in the user table, then the date determines whether that item is available for use in the tree at all.
Trees and user data differ in how effective dates are considered in respect to the current date and when the tree and the data come into scope. The rules are:
The tree’s effective date is the good through date for the tree’s representative organization.
The user data item’s effective date is the good from date for the user data.
Therefore, in a particular tree, the nodes and details valid for that tree must have an effective date on the user data record earlier or the same as the effective date on the tree.
The following table presents an example of an effective-dated tree with a user table that has three effective-dated records for the same item.
|
Tree Effective Date |
User Item Effective Date |
User Data Available to Tree? |
|---|---|---|
|
12-31-2005 |
12-01-2005 |
Yes |
|
12-31-2005 |
01-01-2006 |
No |
|
12-31-2005 |
01-31-2006 |
No |
|
12-31-2005 |
04-01-2006 |
No |
The following table shows the actions when the tree is copied to a new effective date, with the same user data records.
|
Tree Effective Date |
User Item Effective Date |
User Data Available to Tree? |
|---|---|---|
|
02-28-2006 |
12-01-2005 |
Yes |
|
02-28-2006 |
01-01-2006 |
Yes |
|
02-28-2006 |
01-31-2006 |
Yes |
|
02-28-2006 |
04-01-2006 |
No |
Image: Graphical representation of user data and tree effective dates
This diagram illustrates a graphical representation of user data and tree effective dates.
PeopleSoft trees are a hierarchical structure made up of the tree’s definition along with the nodes and details (leaves) that form the parent-child relationships in the tree. The nodes and details are tied in to a user record as defined in the tree structure.
When the user record has an effective date as a part of the record’s key, then that effective date determines the criteria used for details and nodes available for use in the tree.
Trees must have an effective date. Effective dates on trees show planned changes in the hierarchy the tree represents.
For example, in the HR Department tree, you want to add a new Hardware department effective 09/01/2001. You do this by copying the current HR Department tree to a new effective date of 09/01/2001, opening the new tree, and adding the Department node for Hardware.
When the current date reaches 09/01/2001, then the HR Department tree with the Hardware department will become effective for application and reporting purposes, and the previous effective date version of the HR Department tree will be a copy for historical purposes.