Worked Walkthrough: Model Order Lines as a Transaction Fact

The source system stores order headers, order lines, shipping fees, and refunds in related tables. Leaders want product and customer sales analytics without double counting. For a sales star, use one row per submitted order line and keep only measures that belong to that event grain. The common trap is pulling header-level totals such as shipping fees or order tax onto every order line because they are “part of the order.” That multiplies totals when analysts aggregate across lines. Choose the business process Model submitted sales, not payments, invoices, or refunds. This narrows the warehouse question to one event family:…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in