Forecast Comparison Use this function to compare and review planning versions, forecast versions, forecast parameters and forecast errors.
You have run at least one forecast.
Whenever you run a forecast, the last forecast is saved in an internal table as the active forecast version. Older forecast versions within this planning version are also stored in the table.
The standard APO system is configured to store up to 10 forecast versions. You can change this default. The maximum possible number of forecast versions is 999. However, SAP recommends that you keep the number of forecast versions to a minimum. Only in exceptional circumstances should you have more than 100 forecast versions.
The forecast comparison screen cosnsists of three tab pages:
Forecast Error
Here you can see the various error estimates that the system calculates during forecasting. You can sort the different versions according to any one of the measures of error.
When you have found forecast settings that produce the optimum results, you can generate a forecast profile from these settings (only available for univariate forecasting).
Parameters
Here you can see the parameters that each version uses for univariate forecasting (does not apply to MLR) and any lifecycle profiles used for the selection (does not apply if aggregated lifecycle planning was used).
Changes
Here you see more general information, such as the version (planning version or forecast version – see below), the planner who created the version, the date and time of the forecast, the profile used and its type (univariate, MLR, or composite)
You can specify (see below) whether you want to see the data for different planning versions and selections. In this case the system displays the data for the last forecast, the current forecast version. Alternatively you can display all (up to the maximum number of entries) forecast versions for one planning version and selection.
In interactive demand planning, choose
Note
In general the forecast comparison function is intended for use in interactive planning. However if you wish to store the error values from background planning, implement the Business Add-In (BadI) /SAPAPO/SDP_FCST4.
If you specify a planning area and key figure, the system shows you the following:
Planning versions
Univariate forecast errors of the different planning versions
Forecast parameters of the different planning versions
If relevant, which "like" profile, phase-in profile and/or phase-out profile were used to create the forecast
Information on who last saved each planning version, when, and which profile was used to create the forecast
If you specify a planning area, key figure and planning version, the system shows you the following:
All forecast versions that were created in this planning version
Univariate forecast errors of the different forecast versions
For example, you can run the forecast in interactive forecasting multiple times based on different univariate profiles. Then you can compare the forecast versions to see which version has the lowest errors.
Forecast parameters of the different forecast versions
If relevant, which "like" profile, phase-in profile and/or phase-out profile were used to create the forecast
Information on who last saved each forecast version, when, and which profile was used to create the forecast