Forecast engine warning codes
This table list the warning messages that can be returned when generating a forecast. These are
for informational purpose and for additional review. In spite of warning, the engine returns a
forecast, but the results can differ from the original forecast engine configuration.
Code | Warning message | Algorithm or Parameter (if applicable) | Description |
---|---|---|---|
1 | There is an event with no history. | Events only algorithm | The forecast engine is using Events Only algorithm. However, there is a historical period which contains an event value with no corresponding history value. A value of ‘0’ is assumed for this event for calculating of average event size. |
2 | There is history with no event. | Events Only algorithm | The forecast engine is using Events Only algorithm. However, there is a historical period which contains an event value with no corresponding history value. The history point value is not used for calculating the average event size. |
3 | Forecast combining has been selected and fails the forecast magnitude test. | Best algorithm with Forecast Combining. Forecast Test Magnitude |
The Best Fit selection returned a combined forecast for this item. However, the forecast magnitude test is failed. A Review Alerts (Forecast Magnitude Error) is returned for this item-location to review the Forecast Test Magnitude parameter. |
4 | A linear/seasonal Holt-Winters model could not be fitted using the AVERAGING initialisation as the history length after the initialisation period has been removed is 0 or 1. An alternative model has been used instead. | Best algorithm | The history length of item matches or is 1 period longer than the forecast engine Periodicity. There is not enough historical data available to perform a Holt-Winters linear or seasonal model using Averaging initialization, hence these model types are skipped during the Best Fit process. |
5 | There is at least one forecast event type that has no corresponding history event type. | Events Only algorithm or Perform Event Modeling | At least one event profile indicates a future event for which there is no corresponding historical event type is available. This means no average event size is calculated and hence the forecasts event value cannot be calculated. As a result of this, the baseline forecast value is applied to that forecast period. |
6 | There are not enough non-event periods to calculated average event size. All events have been removed and a model has been fit to the unaltered history. | Perform Event Modeling | The forecast engine is set to perform event modeling. However, the item does not have enough historical periods without a historical event to create a baseline forecast (without events). The item-location has been forecast as a normal, or non-event item. |
7 | The history replacement method has been changed to Naïve as there is not enough history for the given method. | History Replacement. Algorithm | The engine is set to perform history replacement, but the item-location combination does not have enough history data to process using the defined algorithm. Review the history data of the item-location or consider an alternative Algorithm. |