UiPath Documentation
industry-department-solutions
latest
false
Supply Chain & Retail Solutions user guide
Importante :
Este contenido no está disponible en el idioma seleccionado. Se muestra el contenido en inglés en su lugar

Forecast dataset

Forecast dataset containing demand forecast values per product and location, an optional forward-looking demand signal for Inventory Management.

The forecast dataset contains demand forecast values for each product at each location. It provides an optional forward-looking demand signal that customers can supply if they already produce their own forecasts.

Purpose​

The inventory management solution uses forecast data as an additional demand signal to complement historical demand analysis. When customers already generate their own forecasts, this dataset allows those forward-looking values to inform replenishment and stock optimization recommendations.

Required fields​

About the Constraint column: every field listed must be provided in your data. Non-null means its value cannot be null; Nullable means the value may be sent as null (or left blank in your source). Primary key, Unique, and Foreign key describe the field's role in the data model; a Primary key is always non-null.

FieldDescriptionTypeConstraint
product_idUnique identifier for the product.stringPrimary key
location_idUnique identifier for the store or distribution centre.stringPrimary key
cutoff_dateThe date on which the forecast was generated.datePrimary key
start_dateFirst date of the forecast period.datePrimary key
end_dateLast date of the forecast period.dateNon-null
horizonNumber of periods ahead of the cutoff date that the forecast covers.integerNon-null
yhatForecasted demand value for the period.floatNon-null
frequencyLength of the forecast period, in days.integerNon-null

Usage notes​

  • This dataset is optional and only required when customers already produce their own demand forecasts.
  • Product and location identifiers must align with the corresponding Products and Locations datasets.
  • Forecast periods should be consistent, with frequency defining the length of each period in days.
  • Forecast values should reflect expected demand, not historical actuals.
  • Purpose​
  • Required fields​
  • Usage notes​

¿Te ha resultado útil esta página?

Conectar

¿Necesita ayuda? Soporte

¿Quiere aprender? UiPath Academy

¿Tiene alguna pregunta? Foro de UiPath

Manténgase actualizado