You can use this component to perform a flexible time-based aggregation of planning data based on season years. You can divide the time frame of a season year into as many seasons as you wish, and model season years according to regions. Assume, for example, that you are planning the sales of products in Europe and Australia. You can plan both regions using the same season year, consisting of the four seasons. However, in the European season year, Spring begins in March and ends in May, whereas in the Australian season year, Spring lasts from September till November.
Seasonal Planning supports the following functions in Demand Planning (DP):
● Interactive Demand Planning including Macros
● Macro Execution with Mass Processing
For seasonal planning, the system aggregates the data of several periods of a specific periodicity (such as a month) to a season, and the data of several seasons to a season year. The system determines the valid season years based on the selected characteristic values combinations. For this you have assigned all the characteristic values combinations of the planning area to seasonal patterns, which are based on season years.
In interactive planning, you can switch between the following displays for seasonal planning:
● Display of seasons in a season year
To determine the season year, the system uses the seasonal pattern of the selected characteristic values combinations.
● Display of one or more season years, aggregated to season year level
The system determines the seasonal pattern(s) to which the selected characteristic values combinations are assigned. The system groups together the season years it determined to form aggregated season years per calendar year.
You can switch from a season year or an aggregated season year to another time buckets profile at any time. You select the display you want in interactive planning above the table area by choosing Period Structure.
To disaggregate the data from a season year to a periodicity of the planning buckets profile, the system uses the key figure-specific setting for time-based disaggregation in the planning area.
A season year begins in the calendar year in which the first season of that season year is. For example, if the start of planning is April 1, 2005 and the first season of the season year begins in December 2004, the season year is 2004. The current season year is always completely ready for input, regardless of the start of planning.
If you want to make sure that the system does not change the data of specific time series key figures in the time frame between the start of planning and the beginning of the season year, set the Cannot Change Pastindicator for these key figures. You can find this indicator in the planning area on the Key Figs tab page under Details.
Year-related entries, such as settings for the period structure in the data view, always refer to the beginning of the season year.
Note the following constraints:
● Seasonal planning is not available for planning areas of Supply Network Planning (SNP) or for DP planning areas with characteristics-based forecasting (CBF) or with a DP BOM.
● Macros containing date-relevant step definitions are not executed at seasonal level.
● If you select another period structure in interactive planning, those macros for which you have set the No Execution if Plan.Buck.Profile Changed indicator are not executed.