This is what happens in the video
If you use demand forecasting in Microsoft Dynamics 365 Business Central and work with forecasts per dimension, you need to understand how dimension values are assigned to forecast entries. When you enter a quantity in a view filtered on a specific dimension, the entry gets that dimension value automatically. But if you enter a quantity in a view without a dimension filter, the entry gets a blank dimension value, which can place it outside your intended forecast.
The risk is that you accidentally create forecast entries with the wrong dimension value, or with a blank dimension value, depending on which view you are working in. To avoid this, always check which view you are in and how it is filtered before you enter or update forecast quantities.
How forecast per dimension updates entries automatically
When you work with forecast per dimension, the forecast updates automatically in the forecast per dimension window with the correct dimension value.
For example, if you have dimension code 13 on a line with a quantity of four and you update it to a quantity of seven, you can drill down on the entry. The forecast entry will automatically carry the project code and the dimension code you were working on. The dimension value follows the view you are in.
Blank dimension values in the forecast per period view
The behaviour changes when you switch to the forecast per period view for a single item. Here you see all the quantities, but when you enter a new line, it gets a blank dimension code.
So if you are working with dimensions, a quantity of 95 in this view might actually consist of several dimension codes. If you then add to a blank line, for instance adding six, that entry will have a blank dimension value. This is something you need to be aware of when you work with dimensions, because the blank value is easy to overlook.
Filtering on dimensions and the risk of wrong dimension values
The same issue appears when you filter on dimensions. Say you filter on two dimensions and you see the forecast for those two dimension values. If you then add another quantity in the same period, that entry can end up with the wrong dimension value.
Because the new entry did not pick up the filtered dimension value, it falls outside the filter. When you remove the dimension filter again and update the forecast, you can see that you have created a forecast entry with a dimension value that does not match the filter you intended.
What to check before entering forecast quantities
The core point is to stay aware of how dimension codes behave across the different views. Before you enter or update quantities, check three things:
- How you work with dimension codes on each line
- Which view you are using, since forecast per dimension and forecast per period behave differently
- How you have filtered the view, so new entries pick up the dimension value you expect
Keeping these in mind prevents forecast entries with blank or incorrect dimension values that end up outside your forecast.
Q&A
Why does my forecast entry get a blank dimension value?
If you enter a quantity in the forecast per period view, or on a line without a dimension filter, the entry gets a blank dimension code. The dimension value follows the view you are working in, so a view without a dimension filter produces a blank value.
How does the forecast per dimension view assign dimension values?
When you enter or update a quantity in the forecast per dimension window, the forecast entry automatically gets the dimension code and project code of the line you were working on. The dimension value is taken from the view.
Why does my forecast entry fall outside my dimension filter?
If you filter on specific dimensions and then add a quantity, the new entry can pick up a different dimension value than the filtered one. That entry then falls outside the filter. When you remove the filter and update, you can see the entry was created with a dimension value that does not match what you intended.
What should I check before entering forecast quantities with dimensions?
Check how you work with dimension codes on each line, which view you are using, and how the view is filtered. The forecast per dimension and forecast per period views behave differently, so confirming the filter ensures new entries get the dimension value you expect.