Attribute value effective date template
Additionally, you can define and maintain an attribute value effective date template to attach an effective date to an attribute value. These date values are available to build a list of activities, activity groups, or account categories for an attribute value in a specified range.
Without defining the Attribute Value Effective Date Template (MX06.1), the system will treat each attribute value as though it was in existence from the initial setup of the activity, activity group, or account category. You will not have the ability to retrieve data for specific attribute values that existed in the past for the activities, activity groups, or account categories.
You must run Attribute Effective Date Update (AC135) before attribute values that are based on an effective date will show up on reports and in attribute lists.
Example
Moose Wood Outfitters wants to track activities for the different phases of store openings over a period of time. They created store attributes, phases attribute values, and assigned effective dates.
Attributes | Values | Effective dates |
---|---|---|
A | New | 01/01/2000 - 03/31/2000 |
A | Post-opening | 04/01/2000 - 12/31/2000 |
A | Established | 01/01/2001 - 12/31/2002 |
A | Remodeled | 01/01/2003 - 06/30/2003 |
B | New | 01/01/2000 - 07/31/2000 |
B | Post-opening | 08/01/2000 - 12/31/2000 |
B | Established | 01/01/2001 - 12/31/2002 |
B | Remodeled | 01/01/2003 - 06/30/2003 |
C | New | 01/01/2000 - 05/31/2000 |
C | Post-opening | 06/01/2000 - 12/31/2000 |
C | Established | 01/01/2001 - 12/31/2002 |
C | Remodeled | 01/01/2003 - 06/30/2003 |
Next, they ran Activity Attribute Effect Date Update (AC135) to build a list of activities and the phase they were in as of 6/30/2000. The list is:
Attributes | Values | Effective dates |
---|---|---|
A | Post-opening | 04/01/2000 - 12/31/2000 |
B | New | 01/01/2000 - 07/31/2000 |
C | Post-opening | 06/01/2000 - 12/31/2000 |