There are various places in Anaplan where you can select from a set of time periods. If time ranges are not used, the periods available are those periods and aggregation levels enabled for the model calendar. But when time ranges are in use, the set of periods offered depends on context. For example, when filtering module data, the set of periods offered is determined by the time range used for module dimensionality. But the set of periods offered for a time period-formatted cell is determined by the superset.
This page explains:
- the superset.
- how amendments to the Model Calendar could affect time ranges, see Changes to the Model Calendar.
- how you can define a different aggregation level in every time range, see Available Aggregations.
Anaplan generates a superset of all the periods (and their aggregation levels) across the Model Calendar and all time ranges. The superset also contains periods that are not contained in a time range. For example, if you create a series of time ranges between 2016 and 2018 and then add a time range, for 2020, the superset will contain values for 2019 even though there is no time range for that period. The superset will also contain the optional aggregation levels Quarter and Half year, if they are enabled for any time range.
Changes to time ranges can affect the superset. For example, if you:
- add a new time range, or edit an existing one, to include periods not present in any existing time range, the new periods are added to the superset.
- edit a time range to remove periods, providing those periods are not in any other time range, they are removed from the superset.
- edit a time range to add an aggregation level that isn’t already in the superset, it is included.
- edit a time range to remove an aggregation level, providing that aggregation level isn’t in any other time range, it is removed from the superset.
Model elements and associated time ranges
|Model Element||Time Range used|
|Line Item Time Scale||Line Item Time Range|
|Time Period format||Superset|
Import – Most aspects
|Module time range|
|Import – Selected Year||Superset|
|Current Period||Model Calendar|
Making amendments to the Model Calendar can affect some aspects of time ranges. Changing the:
- Current Fiscal Year has no effect on time ranges or on data.
- Number of past/future years has no effect on time ranges, but reducing this number can cause data loss for any line items that the model calendar applies to.
- Fiscal year start or end realigns all time ranges to the new fiscal year definition. This can cause data loss.
- Available Aggregations has no effect on time ranges but does affect the default settings for new time ranges. Removing aggregation levels can cause data loss in any line items the model calendar applies to, where granularity is set to the aggregation level being removed.
- Current Period has no effect on time ranges. They can, however, affect calculated data (YTD/YTG values, or other formula references such as SELECT:TIME.CURRENT PERIOD).
- Other settings for weeks calendar types. This includes labeling options such as Extra Week for 53-Week Year and Week Format; and the Week Grouping option for Weeks 4-4-5. These changes are inherited by time ranges but have no effect on data.
Note: You can update the Current Period via the Update Current Period action as well as the Model Calendar. This enables you to set the current period via a Time Period format line item and import the Current Period from a data hub.
Changes to Calendar Type
If you switch between Calendar Types, time ranges are preserved.
The ability to define a different aggregation level for every time range provides increased flexibility for the design of models and data analysis.
Available Aggregations, configured on the New Time Range or Edit Time Range dialog in the Time Ranges tab, can be selected for each time range or model calendar. The level of aggregation selected controls the:
- default module view;
- granularity for line item dimensionality;
- time period format;
- totals that can be referenced by calculations; and
- behavior of the PARENT function.