How To Fix PR021 - Not sufficient historical values available for initialization

PR021 - Overview

• Message type: E = Error

• Message class: PR - Forecast: Help messages

• Message number: 021

• Message text: Not sufficient historical values available for initialization

What causes this issue?

The minimum number of historical values necessary for model
initialization is greater than the number that has been given. The
number required depends on the individual forecast model:
<ZH>Model,, ,,Number of past time values</>

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Constant model,, ,, ,,1
Trend model,, ,, ,,3
Seasonal model,, ,, ,,1 season
Seasonal trend model,, ,, ,,1 season + 3
2nd order exp. smoothing,, ,, ,,3
Moving average,, ,, ,,1
Weighted moving average,, ,, ,,1

System Response

How to fix this error?

Manually fill in the historical values.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PR021 - Not sufficient historical values available for initialization ?

  The SAP error message PR021, which states "Not sufficient historical values available for initialization," typically occurs in the context of SAP's Production Planning (PP) or other modules that rely on historical data for forecasting or planning purposes. This error indicates that the system does not have enough historical data to perform the required calculations or initializations for a particular process, such as demand planning or material requirements planning.
  Causes:
  
  
  Insufficient Historical Data: The most common cause is that there is not enough historical data available for the specific material or planning object. This can happen if:
  
  The material has just been created and has no historical sales or consumption data.
  Historical data has been archived or deleted.
  The data is not available for the required time frame.
  
  
  
  
  Configuration Issues: Incorrect configuration in the planning settings or master data can lead to this error. For example, if the planning parameters are set to require a certain number