In enterprise planning, high-level targets (such as revenue or budget) must be distributed across complex business structures—like regions, product lines, departments, and time periods. Multidimensional or cube forecasting automates this process by linking data across different levels of detail into a unified model. Learn more about creating forecasts.
Instead of manually maintaining separate planning sheets for each dimension, cube forecasting enables real-time distribution and aggregation across multiple dimensions simultaneously.
In this article, you learn to allocate a revenue target forecast defined at the region level to product and sales channel dimensions.
When you create a forecast, define one or more breakdown dimensions to convert it into a forecast cube. The cube can then store and allocate forecast values at multiple levels of dimensional granularity.
In this example,

Reference any measure in the semantic model as the weighting measure for allocation. The measure does not need to be included in the current planning sheet.
Ensure the reference measure contains values for the forecast period in the current planning sheet. Otherwise, cube creation fails during allocation.
In this example, Previous Year Units is used as the reference measure. Although it's not assigned to the current planning sheet, you can still use it to determine the allocation weights.

The top-level row dimension in the current planning sheet is required to create breakdowns for dimensions that are not included in the sheet. In this example, Region_name.
To allocate values across additional dimensions, select + Add to create a breakdown. Define breakdown dimensions.




In the following steps, you use bidirectional cube updates to modify the forecast in a different planning sheet at a different granularity. The cube automatically aggregates the updates and propagates them back to the Global Target Revenue planning sheet.

After configuring a cube measure, it can be used in other planning based on the configured breakdowns. For instance, a cube created in a region-level plan can be imported into a product-level plan.
When importing a forecast cube, the column dimensions in the second sheet must match those of the original sheet.
The row dimensions in the planning sheet must be a subset of the dimensions configured in the cube breakdowns. The dimensions can be in any order.
For example, if the cube breakdown is configured with the dimensions Region, City, Channel, Product Line, the planning sheet can include any subset of these dimensions, such as Channel > Product Line or Region > City > Product Line.
In this example, the original planning sheet uses Year > Quarter > Month as the column hierarchy, so the second planning sheet uses the same column dimensions.
One of the breakdowns is Region > Channel > Product Family > Product. The second planning sheet uses Channel, Product Family, Product as the row dimensions.




