Lesson 3 of 5
Running plan-to-produce end to end with evidence
10 min
Listen to this lesson
End-to-end execution means one business flow runs through every step, with real roles, real authorizations and the same documents, from demand to settlement. The test proves the hand-offs: planner to supervisor, supervisor to warehouse, warehouse to quality, operations to finance.
Preconditions
- Master data in client 100 of CMQ: BOM, routing, work centers WIND-10, ASSY-10 and TEST-10, and a valid production version for CMC-ALT-100 in plant 1710. Production versions are mandatory in SAP S/4HANA for BOM and routing selection.
- Released standard cost estimates for CMC-ALT-100 and its components, so expected costs match the system.
- Stock set to the agreed starting values (300 alternators, 600 rotors) and the planning file current.
- Test users with production planner, supervisor, operator, warehouse, quality and cost accountant roles, not one super-user.
- Posting period open for the test month, and the period-end steps agreed with Dan.
- Day 1Demand and planningPlanned independent requirements entered; MRP Live run; results compared with the expected table
- Day 2Requisitions and conversionRotor requisitions released and ordered; planned orders converted to PP01 orders
- Day 3Release and stagingAvailability check; release; components staged and issued
- Days 4–5Confirmation and receiptOperations confirmed with yield and scrap; inspection lot; goods receipt
- Day 6ExceptionsMissing stator, rework order, Chicago variant
- Day 8Period-endWIP, variances, settlement; reconciliation with Dan
Capture the evidence chain
The test log for an end-to-end case is a chain of document numbers, each linked to the next, plus the values that prove the step. A reviewer must be able to follow the chain without the tester in the room.
| Step | Document (fictional) | Evidence to keep |
|---|---|---|
| Planning | Planned orders 0000412001–004 | Stock/requirements list export with quantities and dates |
| Rotor requisition | 10000871 | Release history (over $10,000), follow-on PO |
| Production order | 1000233 | Component list, planned costs, status history |
| Goods issue | 4900051201 | Material document; component stock before and after |
| Confirmations | 0000088410 ff. | Yield, scrap and activity quantities per operation |
| Inspection lot | 040000000315 | Results, usage decision, stock posting from quality stock |
| Goods receipt | 5000002210 | Material document, journal entry, finished stock value |
| Settlement | Settlement document for order 1000233 | Variance by category; G/L accounts posted |
Evidence chain for PTP-03, PTP-07 and PTP-09 on one order.
Quality and costing in the same run
If QM is active for goods receipts from production, the receipt lands in quality inspection stock with an inspection lot, and the alternators become available only after the usage decision. Test both outcomes: accept, so stock moves to unrestricted use, and reject a partial quantity, so it goes to blocked stock or scrap as Contoso's rules say. Check that MRP sees quality stock as Contoso expects, because planners are often surprised by it.
Costing runs on the same order. After goods receipt and the period-end steps, Dan compares the order's actual costs, the goods receipt credit and the variance with the expected table from lesson 2. A variance that "looks about right" is not a pass; the categories and the settlement accounts must match.
- Goods issueOrder debited with components at standard price
- ConfirmationOrder debited with activities at the cost rate
- OverheadApplied by costing sheet
- Goods receiptOrder credited at standard cost; stock valued at $150
- WIP or varianceOpen orders: WIP · Delivered orders: variance
- SettlementVariance posted to the price difference accounts
When a step fails
Stop the chain at the failed step, log the defect with the documents created so far and the expected versus actual values, and decide with the planner whether a workaround lets the chain continue. Do not let testers "fix" master data on the fly without recording it; an undocumented fix in the test client hides a cutover or data migration gap.
What would you do?
On Day 5 the goods receipt for order 1000233 posts, but the alternators sit in quality inspection stock and the next MRP run plans 500 extra pieces. The production planner wants to post the usage decision immediately so the test can continue. What is the best response?
- Run one flow from demand to settlement with real roles and authorizations.
- Keep a document chain with values that a reviewer can follow alone.
- Test quality outcomes and costing on the same orders as execution.
- Stop at a failed step, log expected versus actual, and never fix data silently.
Check your understanding · not graded
Lesson check
1. Which master data element must exist for MRP to select a BOM and routing in SAP S/4HANA?
2. Why should the test use separate role-based users instead of one super-user?
3. What should happen when a step in the end-to-end chain fails?
4. Goods receipt from production posts to quality inspection stock. What must the test cover next?
5. In the cost flow of a production order, what credits the order?