MaterialsStory · Job Aid · Hands-on · Sim · sandbox
PrerequisiteSAP Fiori basics
Learning objectives
Create a standard sales order end-to-end — navigate → Sold-To → item → free goods → save → read the flow.
Handle the three decision points — availability, backorder, credit — and the real-world action for each (communicate the date, ask about the backorder, escalate the credit block).
Explain how the order connects to the rest of SAP — the master data it leans on and the downstream delivery → goods-issue → billing → FI chain.
Recognise the conjunction: SAP makes the check; the rep manages the customer.
Agenda
Time
Segment
Format
0:00–0:10
Why — an order is a promise
Story + discussion
0:10–0:25
The whole flow, then Sarah's steps
Course + Job Aid
0:25–0:45
When it bends — the 3 decisions
Discussion + Sim
0:45–1:10
You do it — the hands-on run
Hands-on (sandbox)
1:10–1:25
Connect — how it links to the rest of SAP
Connect view
1:25–1:35
Debrief, watch-fors, Q&A
Discussion
Facilitation notes
Open — why it matters
0:00–0:10 · set the stakes
Start with Sarah's Monday: a customer in Schöntal needs five units this week. Don't open with screens — open with the promise.
Ask the room: "When a sales order goes out wrong — wrong price, wrong ship-to — who feels it, and when?" Let it surface that the order is the start of a chain.
The happy path — Sarah's steps
order capture, the clean run
Walk navigate → order type/sales area → Sold-To → item → save. Land two points hard:
Ask: "When Sarah types the Sold-To and presses Enter, where do the Ship-To and the address come from?" (The customer master, via partner determination — one customer number pulls it all in. The number can be numeric or alphanumeric, per the customer's naming convention.)
Ask: "Where does the price come from?" (Determined automatically — not keyed; most users can't edit master data anyway. If it's wrong, flag it; the cause usually sits in the pricing procedure or the condition records. This one trips everyone.)
⚠ Free goods: SAP adds the free line automatically — but the rep still tells the customer and checks it matches the deal. SAP does the maths; the rep owns the conversation.
When it bends — the three decisions
where the job actually lives · the conjunction
Teach each as SAP-check + real-world action:
Availability (ATP): full / partial (later date) / zero. → if a later date, communicate it to the customer before committing.
Backorder: eligible → pop-up; not eligible → auto-reject. → ask the customer first; if rejected, offer an alternative.
Credit block: background check → blocked or clear. → don't override; inform the customer and escalate to Credit Control.
⚠ The whole point: SAP makes the check, but the decision and the customer conversation are the rep's. That's the difference between clicking the process and doing the job.
You do it — the hands-on run
0:45–1:10 · sandbox
Hand out the Hands-on Exercises and let them run the full order with Sarah's data (Sold-To 10100001, TG11 × 5, PO1111). Circulate; don't rescue too fast — let them hit the decisions, then debrief what tripped them.
As they finish: "Where did you hesitate?" — those are your real teaching points (and they feed the performance-support prompts).
Connect — the system view
1:10–1:25 · stage that makes it stick
Use the Connect view: the order leans on master data, runs cross-module checks, and fires a chain — delivery → goods issue → billing → FI.
Ask: "If the ship-to is wrong on the order, where does it surface?" (Downstream — the delivery, the invoice, the customer's door. A mistake here rides the whole chain.)
Questions you'll likely get
"Why are there two Create Sales Orders tiles?"
The modern Fiori app vs the classic VA01 transaction — same job, current interface. Use the modern one.
"My order won't confirm a quantity."
ATP couldn't confirm stock — it's the availability/backorder branch, not an error. Check the schedule line.
"The order is credit-blocked — what do I do?"
Don't release it yourself. Tell the customer it's on hold and contact Credit Control to run the analysis.
"Where do I change the price?"
You don't edit the material to fix a price — it's a pricing condition. Flag it to whoever owns pricing.
Close the loop with them
End where you started — Sarah's promise, now an order number, with the warehouse, the invoice and the customer all set to follow. Ask each person for the one watch-for they'll carry back to their desk. That recall is what makes it stick.
NeoKnova · Trainer Pack · Standard Sales Order · v2026-06-10