Build one-row sales facts

Join the three domains and verify that all 3,413 order lines remain unique.

Question for this chapter

Will the original order-line count survive after customer and material context is attached?

Why this matters now

A duplicate join copies one sale into several rows and inflates revenue. Check both the row count and the uniqueness of the business key before analyzing the result.

Try it

Open the Full Data Integration Pipeline, inspect its inputs and output, then select Run now.

Full data-integration pipeline joining sales data, material data, and the customer master — Connect sales, material, and customer context into one sales-master row.

When the run completes, open Sales Master → Data in the collection.

Sales Master dataset showing 3413 rows — The sales master contains 3,413 order-line rows.

Success looks like this

Sales Master has 3,413 rows, and the business key made from order number and line number also has 3,413 unique values. The duplicate count is zero.

Interpret the result

Each row represents one material line in one customer's order. You can now group the same sales facts by month, customer, country, or material type without changing the underlying transaction set.

Next decision

The trusted row is ready. Instead of running all 14 pipelines, select only the summaries needed to explain the monthly change.