BeyondERP.Newsletter
Menu

Setup page · Inventory management

Forecast models

A setup page where you create forecast models, each of which names and identifies a specific forecast.

Used by
Production manager, Production planner
Business process
Maintain inventory levels
Menu item
ForecastModel
Main table
ForecastModel
Data entity
ForecastModelEntity
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA setup page where you create forecast models, each of which names and identifies a specific forecast.
What you do hereUse this page to hold forecast lines and to combine forecasts by adding other forecast models as submodels.
ExampleFor example, you might set up a simulation that combines a regular forecast with the forecast for a spring promotion.
Forecast models page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

Business processMaintain inventory levels
Menu pathInventory management › Setup › Forecast › Forecast models
Related pagesItem allocation keys Microsoft Learn Period allocation categories Microsoft Learn
End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Step by step, with screenshots

Set up Forecast models1 screen

Use this page to hold forecast lines and to combine forecasts by adding other forecast models as submodels.

  1. Screen 1

    Create a forecast model

    Go to Inventory management > Setup > Forecast > Forecast models

    1. Select New
    2. Enter the model code and name
    3. Leave Stopped off so the model can be used
    4. Select Save
    5. Optionally add other models under Submodel to combine forecasts
    1ModelBEAT-FM
    2NameForecast model
    3StoppedNo
    Create a forecast model (zoomed on the outlined fields)
    Show the full screenCreate a forecast model
    page title tab to open what to set or check

Steps from Microsoft

  1. Go to Inventory management > Setup > Forecast > Forecast models.
  2. Select New.
  3. Enter a unique Model and a descriptive Name.
  4. Leave Stopped set to No unless the forecast lines should be locked.
  5. To add submodels, select the parent model and, on the Submodel FastTab, select Add.
  6. Select the Submodel and enter a Name for it.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExampleTable column
ModelA unique identifier for the forecast model.Microsoft Learn SALESModelId
NameA descriptive name for the forecast model.Microsoft Learn Forecast model
StoppedPrevents editing of all forecast lines assigned to the model.Microsoft Learn NoBlocked
SubmodelAnother forecast model whose forecasts are included in this model.Microsoft Learn SubModelId

Common errors and fixes

MessageWhat to do
Forecast model B is a submodel for model A.Don't add submodels to a model that is already a submodel; keep the structure one level deep and add all models directly under the parent. Microsoft Learn

Test checklist

  1. Create models A, B and C and add B and C as submodels of A.
  2. Enter demand forecast lines on the same day in A, B and C.
  3. Run master planning with a plan that uses model A and Include demand forecast = Yes.
  4. Check the forecast requirement is the sum of the three lines.
  5. Try to add a submodel to B and check the error appears.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Set up Forecast modelsStopped = No; one level of submodels at most, with each submodel created firstLearn says Stopped should usually be No (Yes prevents editing all its forecast lines), and submodels can be only one level deep.Adding a submodel to a model that is already a submodel, which raises an error; master planning also errors on a submodel that has its own submodels.
Solution architect

5Design impact

Shared or per companyPer company: each legal entity has its own records. Microsoft data model
Can it be undoneReversible: Models, submodels and the Stopped flag can be changed. Each submodel keeps its own parameters, and Stopped = Yes only locks editing of the model's forecast lines. Microsoft Learn
If you change it laterSubmodels can be only one level deep, so a model that is already a submodel can't have its own submodels. Microsoft Learn
Technical architect

6Technical

Menu itemForecastModel Checked in Dynamics 365
FormForecastModel Checked in Dynamics 365
TableForecastModelShown as “Forecast models” in Record infoKey field: Type, ModelId, SubModelIdChecked in Dynamics 365
Data entitiesForecastModelEntityForecast models Microsoft data model ForecastSubModelEntityForecast sub models Microsoft data model
Who can open itPrivilegesMaintain inventory forecast models ForecastModelMaintainView inventory forecast models ForecastModelViewDutiesEnable forecast process ForecastForecastProcessEnableReview forecast performance ForecastForecastProcessPerformanceRevieInquire into forecast reference data ForecastForecastReferenceDataInquireEnable the demand forecasting process ReqDemPlanProcessEnableMaintain the master for demand forecasting parameters ReqDemPlanSetupMaintain
2 security rolesProduction manager ProdProductionManagerProduction planner ReqProductionPlanner
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itProduction manager ProdProductionManagerProduction planner ReqProductionPlannerGive people one of these roles. On this system, 2 roles can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=ForecastModel
Integrate withForecastModelEntity data entity Microsoft data model
Data migrationForecastModelEntity (Forecast models): loaded for each company, in Microsoft's default template 430 - Master planning.ForecastSubModelEntity (Forecast sub models): loaded for each company, in Microsoft's default template 430 - Master planning.Load order: Microsoft's default template 430 - Master planning loads Forecast models at execution unit 1, level 30, sequence 10. Lower levels load first, and entities at the same level load in sequence order.Load first: the default templates at lower levels (System setup to General ledger)Microsoft Learn
Table definitionForecastModel columns and relations Microsoft data model
Everyone

8Sources