Revenue from SAP against bookings from the CRM, lead time set in the ERP against lead time measured from receipts, stock in the warehouse system against stock in the ERP: the pivot puts two measures beside each other for the same golden record, computes a calculated measure from them, and lets you drill into the rows that make the difference.
| customer | SAP revenue | SF bookings | invoiced share | explanation |
|---|---|---|---|---|
| Northbay Logistics | €4.82M | €5.40M | 0.89 | 3 orders invoiced in Oct |
| Helvetia Retail AG | €2.10M | €2.05M | 1.02 | — |
| Corvid Plastics | €0.91M | €1.40M | 0.65 | 2 orders on credit hold |
| Brightline Metals SA | €1.62M | €1.58M | 1.03 | — |
| Total | €9.45M | €10.43M | 0.91 |
The explanation column is a calculated measure too: it counts the orders booked in the quarter with no invoice, and the ones on credit hold, and writes a sentence. A click on it opens those orders.
| Calculated measure | Formula | Notes |
|---|---|---|
| variance | actual − plan | unit from the operands |
| variance_pct | (actual − plan) / plan | guarded against zero |
| margin | revenue − cost | currency converted at the row's date or the budget rate, by choice |
| share_of_parent | value / value at the parent node | follows the pivot's hierarchy version |
| lead_time_gap | planned_lead_time − actual_lead_time_p50 | feeds the planning-parameter rule |
| invoiced_share | sap_revenue / sf_bookings | both resolved through the cross-reference |
Calculated measures are defined in the same language as rules, carry units and currencies, and appear in the pivot, the grid, the chart, the API and in rules that compare them with thresholds.
Yes; a measure is a query over the bed, and the bed includes the sources read in place and the governed replicas.
Analysts and stewards, with the definition versioned and approved before it appears in shared views.
Yes: the planning-parameter rule compares lead_time_gap with a tolerance and queues the outliers.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.