Diagnosis
During the replenishment run, the system attempted to read the forecastdata in aggregated form. When doing this, the forecast results can beread in varying degrees. The system reads the forecast data from thedatabase within the time interval given by replenishment, which iscalculated from the replenishment lead time and replenishment horizon,subsequently known as a time interval. The forecast data is thentransferred to replenishment in aggregated form as forecastrequirements. Aggregation can take place in varying degrees of detail:

• Aggregation of the whole period: the system aggregates and reads all
forecast values for a forecast period that fall within the timeinterval. The forecast values for a forecast period that are cut off bythe beginning or the end of the time interval are included entirely inthe forecast requirements.

• Proportional aggregation of the outlying forecast periods and complete
aggregation of the whole periods within the time interval: all forecastrequirements belonging to forecast periods that lie entirely within thetime interval are added completely to the forecast requirements. Thefirst and last forecast periods that do not necessarily lie completelywithin the time interval are added proportionately.
Example of proportional forecast requirements:
The time interval for replenishment covers five forecast periods thatare a week long. The beginning of the time interval falls on theThursday of the first forecast period and the end of the time intervalfalls on a Wednesday. The system adds the entire forecast values forthe three middle periods to the forecast requirements. Four sevenths ofthe forecast value for the first period and three sevenths for the lastperiod are added to the forecast requirements.

System Response
The system is unable to calculate a forecast requirement for thereplenishment.