Prepare the sales, material, and customer domains

Run three core pipelines to produce datasets that can be connected safely.

Question for this chapter

In what order should the source codes be prepared so the tables can be connected safely?

Why this matters now

Joining every raw table at once allows date formats, language-specific names, and customer-region values to contaminate the final result. Domain-level outputs reveal where a value changed.

Try it

Under Pipelines in the left sidebar, open these pipelines in order and select Run now:

Sales Data Join Pipeline
Material Join Pipeline
Customer Information Transformation Pipeline

Pipeline joining sales-document headers and lines and preparing order dates — Sales domain: join VBAK and VBAP into sales facts.

Pipeline preparing the material master and material descriptions — Material domain: connect MARA and MAKT to produce readable material data.

Pipeline transforming the customer master — Customer domain: prepare KNA1 as the customer master.

Success looks like this

Each pipeline shows a green Success state, and Sales Data, Material Data, and Customer Master have been created.

Interpret the result

Sales Data turns orders and lines into one sales fact per row.
Material Data selects a language description and attaches a material type.
Customer Master prepares the connection from customer to country and continent.

Next decision

The three domains are ready but still separate. Next, gather customer and material context around one order line.