Measures and dimensions reference
One row per measure: group, grain, unit, whether it adds up across slices, the currency conversion rule, the source and the owner. Needed so that the buying plan is fed with agreed facts.
What the template is for
Describing the data for buying planning and checking that the numerator and the denominator of a metric share one grain and one currency rule.
- What one row is
- one row = a measure
Columns
| Column | Code | Type | Required | Validation rule |
|---|---|---|---|---|
| Measure name | measure | Text | yes | unique in the file |
| Measure group | group | List value | yes | budget, order, receipt, sales, discount, stock, area or markup |
| Grain | grain | Text | yes | what one fact row means, not empty |
| Unit | unit | List value | yes | pcs, rub, pct, days, m² or k |
| Adds up across slices | additive | List value | yes | yes or no; shares and averages do not add up |
| Currency rule | fxrule | List value | yes | none, original, transaction_date or period_end |
| Source | source | Text | yes | a system or a document |
| Owner | owner | Text | yes | a role, not a surname |
Example rows
| Measure name | Measure group | Grain | Unit | Adds up across slices | Currency rule | Source | Owner |
|---|---|---|---|---|---|---|---|
| order_qty | order | order line | pcs | yes | none | ordering system | buyer |
| delivered_cost | receipt | delivery × product × date | rub | yes | transaction_date | receiving | buyer |
| sales_cost | sales | receipt line × product × date | rub | yes | transaction_date | cash and accounting | finance |
| stock_end_qty | stock | product × place × day | pcs | no | none | warehouse | logistics |
| markup_coef | markup | product × price list | k | no | none | price list | category |
The example data is illustrative: an exercise, replace it with your own.
Note
The currency rule transaction_date means the rate at the date of receipt or sale. Do not filter the sell-through denominator by the season calendar. The examples are illustrative.
How to open the file
The file is UTF-8 with a BOM, comma separated, with a decimal point. Set the text format for code columns (SKU, article, GTIN) so that long numbers and leading zeros are not distorted. The validation rules are suggested defaults, not norms: your systems and contracts may require something else.
Calculations that use these fields
- Buying plan from revenue backwards: revenue → cost → order
- Open-to-buy (OTB) for the season
- Order path: confirmation, fill rate and lost sales
- New and carryover: share, return per SKU, sell-through and margin
- Sales forecast: method, horizon, error
- Buying budget by category and weeks of supply
- Buying plan adherence: receipts, sales and stock
- Season sell-through pace and leftover risk