Capabilities Comparing measures

Two numbers for the same thing, side by side, with the difference explained.

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.

SAP revenue · Q3€4.82M · invoicesSalesforce bookings · Q3€5.40M · closed-wonDifference€0.58M · 3 orders awaiting invoiceboth measures resolve to golden C-00842 through the cross-reference, so the comparison is on the same customer, whichever spelling each system usescalculated measure: invoiced_share = sap_revenue / sf_bookings, saved once, reused by the pivot, the chart and the API
Two measures from two systems for one golden customer, and the calculated difference with its explanation.
2+
measures per cell, from any sources
product
1
definition per calculated measure, reused everywhere
product
unit-aware
formulas: currencies and units convert through the reference data
product
live
differences, with drill-down to the rows
product
Step by step

From two measures to an explained difference

Pick the measuressap_revenue from invoices and sf_bookings from closed-won opportunities, both for the customer hierarchy by quarter.
What you see

Revenue against bookings by key account, Q3

customer hierarchy · key accounts · Q3 2026measures: sap_revenue · sf_bookings · invoiced_sharethreshold: 0.85–1.05
customerSAP revenueSF bookingsinvoiced shareexplanation
Northbay Logistics€4.82M€5.40M0.893 orders invoiced in Oct
Helvetia Retail AG€2.10M€2.05M1.02—
Corvid Plastics€0.91M€1.40M0.652 orders on credit hold
Brightline Metals SA€1.62M€1.58M1.03—
Total€9.45M€10.43M0.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 measures

Formulas saved once, reused everywhere

Calculated measureFormulaNotes
varianceactual − planunit from the operands
variance_pct(actual − plan) / planguarded against zero
marginrevenue − costcurrency converted at the row's date or the budget rate, by choice
share_of_parentvalue / value at the parent nodefollows the pivot's hierarchy version
lead_time_gapplanned_lead_time − actual_lead_time_p50feeds the planning-parameter rule
invoiced_sharesap_revenue / sf_bookingsboth 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.

Terms on this page

Calculated measureA measure defined by a formula over other measures, saved once and reused everywhere.
VarianceThe difference between two measures, absolute or as a percentage.
Unit-awareA formula that converts currencies and units through the reference data before combining values.
Questions

Can a measure come from a source Lima reads in place?

Yes; a measure is a query over the bed, and the bed includes the sources read in place and the governed replicas.

Who can define calculated measures?

Analysts and stewards, with the definition versioned and approved before it appears in shared views.

Can a rule use a calculated measure?

Yes: the planning-parameter rule compares lead_time_gap with a tolerance and queues the outliers.

See your first domain built on your data

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.