Dynamics 365 Supply Chain: Warehouse Demand Forecast Dimension Removal - Explained

Table of Contents

KB number: 4614408

Symptoms¶

Users of Dynamics 365 Supply Chain Management may observe an unexpected behavior related to the Warehouse dimension within the demand forecasting process. This specific issue arises even when the Warehouse dimension is not explicitly enabled or assigned on the Forecast dimensions tab, which is located on the Demand forecasting parameter page. Despite this configuration, the Warehouse column is still prominently displayed on the Demand forecast page. This page is accessed through the navigation path: Master planning > Forecasting > Manual forecast entity > Demand forecast lines. The discrepancy between the parameter settings for forecast dimensions and the visible columns on the manual demand forecast entry page can lead to confusion regarding which dimensions are active and influencing the forecast process.

The appearance of the Warehouse column suggests that the system might be expecting or allowing forecast data entry at the warehouse level, even though the global forecasting parameters seem to indicate that warehouse-level forecasting is not configured. This inconsistency can cause operational issues, potentially leading users to believe they should enter warehouse-specific forecast data when the underlying system configuration, controlled by the forecast dimension parameters, might not be set up to process or utilize this detailed information in the subsequent baseline forecast generation. Understanding the intended function of each page and parameter is crucial to navigating this apparent conflict and ensuring accurate forecasting practices within the system.

Resolution¶

The observed behavior, where the Warehouse column appears on the Demand forecast page despite not being selected as a forecast dimension on the Demand forecasting parameter page, is by design. This design reflects a distinction in Dynamics 365 Supply Chain Management between the dimensions used for generating the baseline forecast and the dimensions available for manual forecast entry and management. The settings configured on the Forecast dimensions tab of the Demand forecasting parameter page specifically govern which product dimensions (such as Color, Size, Style) and storage dimensions (like Site and Warehouse) are considered when the system automatically generates the baseline forecast. This baseline forecast is derived from historical data and is the initial prediction produced by the forecasting engine.

Therefore, the parameters on the Demand forecasting parameter page are primarily focused on the input requirements and aggregation levels for the automated forecasting algorithms that create the baseline. They dictate how historical transactions are grouped and analyzed, and at what level the statistical forecast is generated. The results of this process are typically viewed and managed on the Adjusted demand forecast page. This distinction is key: the parameters control the automated creation of the forecast baseline, but they do not directly control the data entry interface for manual forecasts or the final “real” forecast entries used in master planning. The presence of the Warehouse dimension on the Demand forecast page is intended to provide flexibility for manual data entry at various levels, irrespective of the automated baseline generation settings.

Understanding the Different Forecast Pages¶

Dynamics 365 Supply Chain Management utilizes several pages to manage the demand forecasting process, each serving a distinct purpose:

1. Demand forecasting parameter page: This page is the central hub for configuring the overall demand forecasting process. The Forecast dimensions tab here determines which dimensions (Product, Storage, Tracking) are included when the baseline forecast is generated statistically from historical data. For example, if only Site is selected here but not Warehouse, the baseline forecast will be aggregated and generated at the Site level, even if historical data exists at the Warehouse level. Other settings on this page include forecast methods, time periods, historical data parameters, and integration settings. The configurations here significantly influence the output generated by the forecasting engine.
2. Demand forecast page: This page serves as a data entry point for managing forecast lines. It is often used for manual forecast creation or adjustments. The columns displayed on this page, including Product dimensions (like Size, Color, Style) and Storage dimensions (like Site, Warehouse), represent the level of detail at which forecast data can be entered or viewed. The presence of the Warehouse column here allows users to manually specify forecast quantities for a particular item at a specific warehouse, even if the system’s baseline forecast generation is configured to operate at a higher level (e.g., Site only). This provides flexibility for incorporating specific market intelligence or planned promotions that are warehouse-specific and may not be captured by the statistical baseline.
3. Adjusted demand forecast page: This page is where the output of the baseline forecast generation process is presented. It shows the statistically calculated forecast lines, aggregated or disaggregated according to the dimensions selected on the Demand forecasting parameter page. Users typically review the baseline forecast on this page and make manual adjustments based on their expertise, market knowledge, or planned events. This adjusted forecast represents the refined prediction before it is finalized for master planning. The dimensions visible on this page reflect the level at which the baseline was generated and subsequently adjusted.

The Role of Baseline vs. Real Forecasts¶

The concept of a “baseline forecast” versus a “real forecast” is fundamental to understanding the resolution. The baseline forecast, generated automatically based on historical data and the dimensions defined in the parameters, is an initial, often statistical, prediction. It’s a starting point. This baseline is then presented on the Adjusted demand forecast page for review and modification.

The “real” demand forecast entries are those that are ultimately used by Master Planning to calculate material and capacity requirements. These “real” entries are created by authorizing the lines from the Adjusted demand forecast page. When you authorize the adjusted forecast, the system essentially converts these planned forecast lines into concrete demand forecast entries that are linked to a specific forecast model. Master Planning runs calculations against data within a designated forecast model.

This authorization process bridges the gap between the statistically generated/adjusted baseline and the operational forecast used for planning. The dimensions available for authorization and subsequent use in the forecast model depend on how the forecast model is configured and, implicitly, the dimensions carried through from the adjusted forecast, which in turn depends on the baseline generation dimensions.

Why the Warehouse Column Appears on the Demand Forecast Page¶

The presence of the Warehouse column on the Demand forecast page, even when Warehouse is not selected in the forecast parameters, serves the purpose of enabling manual forecast entry or management at a granular level. Users can manually create forecast lines directly on this page, specifying quantities for particular items at specific sites and warehouses, regardless of how the automated baseline forecast is configured. This allows for flexibility in forecasting processes where some inputs might come from a statistical model (via the Adjusted demand forecast page) and others might be entered manually with specific location details.

The key takeaway from the resolution is that the Forecast dimensions tab on the Demand forecasting parameter page only dictates the dimensions used for the baseline forecast generation. It does not control the dimensions available for manual entry on the Demand forecast page or the dimensions ultimately stored with the “real” forecast entries after authorization. The Demand forecast page is a flexible interface for managing forecast lines, potentially at a finer level of detail than the automated baseline forecast might provide.

Consider the following conceptual diagram illustrating the flow:

```mermaid
graph LR
A[Historical Data] → B(Forecast Engine);
B → C{Demand Forecasting
Parameters};
C → B;
B → D[Baseline Forecast
(Adjusted Demand Forecast Page)];
E[Manual Entry
(Demand Forecast Page)] → D;
D → F{Authorization};
F → G[Real Demand Forecast
(Linked to Forecast Model)];
G → H(Master Planning);

%% Styling for emphasis
C -.-> |Controls baseline dimensions| B;
E -.-> |Direct Entry/Adjustments| D;
F -.-> |Converts to Real Forecast| G;

```

This diagram illustrates that historical data and parameters feed the forecast engine to generate the baseline. Manual entry on the “Demand forecast” page can supplement or modify this. The “Adjusted demand forecast” page shows the result, which is then authorized to become the “Real Demand Forecast” used by Master Planning. The parameters control the baseline generation dimensions, not the manual entry dimensions.

Let’s delve a bit deeper into the implications. If your company’s business process requires Master Planning to consider forecast demand at the warehouse level (e.g., to drive warehouse-specific transfers or purchasing), then the “real” forecast entries used by Master Planning must include the Warehouse dimension. How do you achieve this if the baseline forecast is generated only at the Site level?

You have a few options, given the system’s design:

1. Manual Entry at Warehouse Level: Use the Demand forecast page to manually create forecast lines, explicitly including the Site and Warehouse for each line item. These manually entered lines can then be reviewed and potentially authorized directly or consolidated with baseline data if needed (though consolidating site-level baseline with warehouse-level manual entries requires careful process design).
2. Disaggregate Baseline: Generate the baseline forecast at the Site level (as per parameters), view it on the Adjusted demand forecast page, and then use system functionalities to disaggregate this site-level forecast down to the warehouse level before authorization. This disaggregation might be based on historical sales distribution by warehouse, allocation rules, or manual input. This requires specific processes or potential customizations.
3. Adjust Baseline Parameters: If feasible for the business process, configure the Demand forecasting parameter page to include the Warehouse dimension for baseline generation. This means the statistical forecast will attempt to predict demand at the Site and Warehouse level directly from historical data. This requires sufficient historical data granularity at the warehouse level and impacts processing time and complexity. However, if this parameter is not set, the issue described (column visible but not used in baseline) is what occurs.

The resolution highlights that the settings on the Forecast dimensions tab primarily affect option 3 (how the baseline is generated). The fact that the Warehouse column is visible on the Demand forecast page is an enabler for option 1 (manual entry) and a facilitator for processes related to option 2 (managing lines potentially used for disaggregation) before authorization.

In summary, the visibility of the Warehouse column on the Demand forecast page is not a bug related to the Demand forecasting parameter settings. It is a feature designed to provide flexibility for manual data entry and management of forecast lines at a detailed level, independent of the dimensions configured for the automated baseline forecast generation. The parameters control the engine, while the forecast pages offer interfaces for reviewing, adjusting, and entering data at various granularities. The “real” forecast, used by Master Planning, is derived from the authorized lines, typically originating from the Adjusted demand forecast page, which may include baseline data, manual adjustments, and potentially disaggregated data, ensuring it has the necessary dimensions for subsequent planning processes.

Understanding this distinction is crucial for correctly configuring demand forecasting parameters and effectively using the different forecast management pages within Dynamics 365 Supply Chain Management. It ensures that users do not mistakenly assume the presence of a column on the manual entry page implies it is actively being used by the baseline generation process if not configured as a forecast dimension in the parameters.

Navigating the complexities of demand forecasting within an ERP system like Dynamics 365 involves understanding the interplay between configuration settings, automated processes, and manual data management interfaces. This specific scenario serves as a reminder that different parts of the system are responsible for different aspects of the forecasting workflow – from baseline generation parameters to manual adjustment interfaces and the final output used for planning.

Do you have experience with configuring forecast dimensions in Dynamics 365 Supply Chain Management? How have you managed the need for warehouse-specific forecasts? Share your thoughts and experiences in the comments below!