These functions enable you to set up forecasting to account for different wishes regarding time periods. For example you can specify that all planning period have the same length or specify which calendar is to be used for demand planning. Planning calendars are valid for whole planning areas. You can specify the length of a planning period in the forecast period, so that this setting is valid just for a selection.
Demand Planning does not usually work with planning calendars. It could result in unexpected results when you release data to SNP using smaller periodicities such as days and weeks. However it is possible to specify that planning calendars are taken into account. You can thus use the same calendar in Demand Planning, SNP and PP/DS. This setting is valid for the whole planning area.
1. Create the time stream in Customizing under APO ® Master Data ® Calendar ® Maintain Planning Calendar (Time Stream). Refer to the implementation guide (IMG) before editing time streams.
2. Assign the time stream to a storage bucket profile (Demand Planning ® Environment ® Current Settings ® Periodicities for Planning Area).
3. Create the planning area with the above storage bucket profile.
Only those dates defined in the time stream are available in the planning book. It is not possible to plan demand for dates that lie outside the time stream. You can see this in interactive planning, if you are displaying sufficiently detailed periodicities. For instance, if in the time series you have defined a 5 day working week and taken public holidays into account, you will see only a difference in interactive planning if you are working in days, that is you are using a time buckets profile in the data view that contains days. If you are working in months, you see no difference due to the time series.
Note that you also define a periodicity in the forecast profile. This is the periodicity in which the forecast is executed. The quantities are then aggregated or disaggregated when you return to interactive planning. Time series are taken into account.
This function is another way of influencing time-based aggregation/disaggregation.
This function is for use in univariate forecasting with period other than days. In general Demand Planning uses the number of calendar days in a calendar month for planning purposes, that is for example 31 in January or 28 in February. However you may wish to stipulate that all months contain the same number of days, for instance 20.
You enter the number of days per period in the Days in period field on the Univariate prfl. tab page of the master forecast profile.
1. Corrects the historical values using this average number of workdays.
The new values are contained in the Corrected history row of the demand planning table.
2. Runs the forecast based on this average number of workdays in the forecast period.
3. Recalculates the figures to account for the actual number of workdays in the forecast period. The Corrected forecast row shows the results of this calculation.
For more details, refer to the F1 help for this field.
Using this function together with mixed periodicities, for example days and weeks, causes unexpected results. SAP recommends that you do not use the two functions together.