Explain a sales change from scattered SAP tables
Connect five SAP sources, explain a sales change by month, customer, region, and material, then choose the first order to review.
0/7 chapters complete
The month-end sales review room
The sales team wants to know why revenue changed, but order, line, material, material-name, and customer information live in separate SAP tables. A total from one table cannot distinguish one or two unusually large orders from broad growth in repeat orders.
How should the sales, material, and customer tables be connected to explain a revenue change?
Decision criteria for this mission
- Perspectives in play — Sales operations asks why revenue changed, data analysis verifies keys and duplicate-free joins across five sources, and commercial review separates source facts from training assumptions.
- Decision constraints — The source SAP tables do not contain discounts, costs, or currency, so those
values are marked
TRAINING_ASSUMPTION. All 3,413 business keys in the sales master must be unique before the aggregation is trusted. - Completion signals — Narrow January 2017 net revenue of about USD 9.11 million to order
18622, confirm its 93.21% share, and recommend reviewing contract, discount, actual cost, and currency before calling it broad growth.
Workshop goals
This Workshop focuses on selecting and interpreting the data needed for the question rather than running every imported asset. By the end, you will be able to explain this conclusion:
- January 2017 produced about USD 9.11 million in net revenue from 67 orders, but its training-assumption margin was only 11.35%.
- Order
18622generated 93.21% of that monthly revenue with an assumed discount of 18% and an assumed margin of 10%. - Review that order's contract, discount, actual cost, and currency terms before describing the month as broad growth.
Seven decisions
Loading the diagram. Mermaid source:
flowchart LR
accTitle: Seven stages that connect five SAP sources and explain a sales change
accDescr: Frame the month-end question, build a sales master, narrow the change to one transaction, trace its relationships, check evidence and assumptions in a quiz, and explain the conclusion.
q["1. Month-end question"] --> clean["2. Prepare three domains"]
clean --> master["3. Sales master"]
master --> narrow["4. Narrow the change"]
narrow --> trace["5. Trace relationships"]
trace --> check["6. Check the evidence"]
check --> explain["7. Explain the conclusion"]Every chapter follows the same question → reason → action → observation → interpretation → next decision sequence.
Prerequisites
- A D.Hub account that can open and run collections and pipelines
- An environment where you can download and upload the scenario ZIP
- 90 minutes of practice time
Learning journey
- Frame the month-end question and inspect five sources15 minImport the SAP scenario and distinguish the role of each of its five source tables.
- Prepare the sales, material, and customer domains15 minRun three core pipelines to produce datasets that can be connected safely.
- Build one-row sales facts15 minJoin the three domains and verify that all 3,413 order lines remain unique.
- Narrow the month to one priority-review order20 minCompare revenue with training profitability assumptions and choose the first order to inspect.
- Trace the customer through order, material, and date15 minMaterialize the ontology and verify the selected customer's sales context in the graph.
- Check the month-end reasoning5 minBefore the final explanation, review source joins, duplicate checks, order context, and the boundary of training assumptions in four questions.
- Explain what you solved and finish the Workshop5 minSummarize the cause of the sales change and the next verification step with evidence.