ReportingUnit.item_values_budget provides the budgeted order intake value at Reporting Unit (PRU) level, structured as an item-values dataset so it can be joined consistently with other CDM-style domains (actuals, forecasts, pipeline, etc.).
It is sourced from sales.order_intake_budget, which is derived from the Finance-controlled budget workbook in SharePoint, and then reshaped into the standard OBJECT + ITEM + ATTRIBUTE + VALUE pattern used across the Data Warehouse.
What this view is for
This view exists to make budget data behave like the rest of your “item values” model:
- Enable Budget vs Actual and Budget vs Forecast comparisons using a shared key pattern
- Provide budget values at a clean grain: PRU + Accounting Period + Budget Version
- Allow downstream solutions (Power BI, APIs, other marts) to consume budget values without having to interpret spreadsheet layouts
Grain and uniqueness
Each row represents a single budget value observation for:
- One Reporting Unit (PRU)
- One accounting period (derived from the source date)
- One budget version (type + budget + version)
- One attribute/value pair (currently:
ATTRIBUTE = 'VALUE')
Uniqueness is enforced via the checksum built from:OBJECT_SEQ + ITEM_KEY + ATTRIBUTE + CODE_VALUE