Additive upload: non-forecasted, non-propagated driver type

Non-forecasted driver types support one data version for the same date period (forecast period): week, month, regardless of the date of the upload.
  • There is one data version for the month. For example, January, February, March 2018.
  • There is one data version for the week regardless of the upload. For example, W01-01/01/18, W02-01/08/18. The new upload overwrites the existing value.
  • The same principle is applied for the other supported planning frequencies. For example, actual production volume. There is only data version for the actual production volume for week W01-01/01/18.

Non-forecasted, non-propagated values are uploaded for the date periods (forecast periods) defined in the upload file and their corresponding periods [period]. For example, when the source file includes driver values for forecast periods 34, 35, 36, 37:

WDDPERIOD: period_034 - WDDFORECAST_PERIOD: forecast_period_034
WDDPERIOD: period_035 - WDDFORECAST_PERIOD: forecast_period_035
WDDPERIOD: period_036 - WDDFORECAST_PERIOD: forecast_period_036
WDDPERIOD: period_037 - WDDFORECAST_PERIOD: forecast_period_037

If new uploaded records are for different data area than the previous upload, the new records are added to existing data.

If new uploaded records are for the same data area, the existing records have their values overwritten.

If date information is missing in the source files, values are uploaded for the forecast period that corresponds with the current date.