Actual volume sold vs budgeted volume
Actual volume sold vs budgeted volume
it measures the outcome of commercial plans after the sales period has closed, confirming whether the budget was met or missed. The financial consequences are already locked in.
(Actual volume / Budget volume) x 100One row per SKU per location per forecast version per period
A preview of what's actually built for this KPI — extracted from the real Implementation Pack, not a mockup.
This is the primary ratio the pack's other measures build on — trend, rank, and period-comparison variants, all on Fact_Demand_Forecast.
Fact_Demand_Forecast — 9 mandatory columns — period key, product key, ...Dim_Customer — key + nameDim_Forecast_Version — key + nameDim_Material — material_key + material_descriptionDim_Period — key + nameDim_Plant — key + nameDim_Product — key + nameDim_Date — Auto-generated calendar table — no customer data requiredFull field-by-field data contract, in 4 SQL dialects (SQL Server, Snowflake, Databricks, BigQuery), ships in the pack.
| Target | 1 — reference value for this KPI |
| Warning | 0.92 — amber alert — triggers a review |
Both live in one Excel tab — change them, refresh the report, done. No DAX editing needed.
Everything you need to build Volume Forecast vs Budget in Power BI — dimensional model, DAX measures, SQL views, and a food-industry demo dataset.