When the Detailed Financial Plan is configured to use 'calendar' date options instead of 'fiscal' date options, the end-user will have an issue with Time Scaled Value (TSV) scrolling or editing. This occurs when the plans have different types of fiscal periods or different fiscal period date ranges and are accessed in the same user session using the 'calendar' date options configuration. With this configuration, the application is not able to determine the correct TSV periods because fiscal periods may be defined differently than the ISO calendar periods.
This article describes two use-cases for some issues encountered when the configuration is not set up properly.
1. SCROLLING Use Case:
Scrolling on the time-varying grid stops before the start of the cost or benefit plan start period if the TSV configuration for start date is set to a non-fiscal, calendar date option such as 'Start of Current Year'.
The steps below describe the issues for scrolling
Steps to Reproduce:
Expected Result: TSV start period is January 2014
Actual Result: TSV start period is July 2014 and the TSV offset again set to -5, I am not able to edit the prior month where the TSV start period is configured (June 2014)
2. Editing Use Case:
Editing on the time-varying grid is not possible in cells before the start of the cost or benefit plan start period if the TSV configuration for start date is set to a non-fiscal, calendar date option such as 'Start of Current Year'.
This occurs when different plans have different types of fiscal periods or different fiscal period date ranges and are accessed in the same user session using the 'calendar' configuration.
Steps to Reproduce:
Expected Result: TSV cells for the newly added fiscal periods should be open for editing
Actual Result: The new periods are not open for editing. If the user logs out of the session and back in, they are able to edit the cells. If the configuration is changed to use the Fiscal Start Date, as described below, the application works as expected upon changes and does not require the user to log out of the session.
The use cases described above are just two specific examples of how the application misbehaves when using the 'calendar' date values instead of the 'fiscal' date values on a Fiscal Time-Varying attribute configuration. There may be other specific steps to reproduce issues with scrolling or editing when using the 'calendar' date values in the configuration.
When using a 'calendar' Time-varying attribute, the configuration should use 'calendar' date values.
When using a 'fiscal' Time-varying attribute, the configuration should use 'fiscal' date values.
Do not use the Rolling Date (calendar type of dates) with 'Start of Current Year' for the TSV start date, use "other date" with "Benefit Plan's Start Date" or "Cost Plan's Start Date" instead (fiscal type of dates).
With Fiscal TSV configurations, it is important to configure the views to use the dates that correspond to the plan period attributes.
To ensure proper functionality for scrolling across fiscal periods or for editing changed fiscal periods, use the following, recommended configuration, defined on the Benefit Plan Detail object for all users.
- Other Date: Benefit Plan's Start Date
- Other Time Scale: Period Type
Use the 'fiscal' date options to configure the TSV for the Cost Plan Detail Object as well. This configuration will automatically determine which type of fiscal period to display (monthly, annually, etc) based on the Fiscal Period Type and Fiscal Start Date attribute values selected on the Plan Properties page.
<Please see attached file for image>
Remember, in any list view, to always use 'Fiscal' date options for Fiscal TSV attributes and use 'Calendar' date options for regular, Calendar TSV attributes.