Lesson 6 of 6
Testing corrective maintenance end to end
9 min
Listen to this lesson
The corrective flow is where maintenance, inventory, purchasing and controlling meet, so it deserves a true end-to-end test: one breakdown, followed from the operator's notification to settled costs on the receiver. Priya's rule for Contoso is simple: the test is not finished until the cost center report shows the cost.
The core test: breakdown to settlement
| Step | Action | Expected result and evidence |
|---|---|---|
| 1 | Create M2 notification on 10000451, priority 2, breakdown flag | Required start +1 day, end +3 days; status outstanding |
| 2 | Create PM01 order from it; two operations, bearing, belt, sensor | Header notification set; reservation and requisition created; planned costs shown |
| 3 | Purchase the sensor: requisition to PO, goods receipt | PO linked to the order; receipt posts $310 to the order |
| 4 | Release and issue parts | Status REL; material document for bearing and belt with the order as account assignment |
| 5 | Confirm 4.5 h and 2 h; record codes on the notification | PCNF then CNF; work center cost centers credited; codes saved |
| 6 | Set TECO and complete the notification | TECO and NOCO; no open reservations |
| 7 | Settle the order in the period-end run | Settlement document; $1,054.50 on cost center 17101107; order balance zero |
| 8 | Business complete | Status CLSD |
Contoso's end-to-end corrective maintenance test.
Variations and negative tests
- Emergency process in Report and Repair Malfunction, settled the same way.
- Order with an external service from Riverbend Facility Services, received through service entry.
- A requisition over $10,000 that must be released before purchasing can act.
- Release with a missing part, proving Contoso's availability rule.
- A wrong confirmation reversed and reposted.
- TECO reversed and redone, proving reservations are restored.
- Business completion attempted with a non-zero balance: must be refused.
- An order released in ECC before the conversion, confirmed, completed and settled in SAP S/4HANA.
What would you do?
The CMQ test of order 4001250 reaches step 6, but there is no time left in the cycle to run period-end settlement. A tester wants to mark the test passed because the order is TECO and costs look right. What should Priya decide?
- Day 1, 07:40NotificationOperator reports; required dates calculated
- Day 1, 09:00Order plannedReservation and requisition created
- Days 1 to 3Parts and releasePO, receipt, release, goods issue
- Days 2 to 3Work and confirmationHours, codes, TECO, NOCO
- Period endSettlementCosts to 17101107; balance zero; CLSD
Plan the test calendar backwards from settlement. If the cycle ends on the 20th and controlling only runs settlement in the first days of the next period, the end-to-end test cannot finish. Agree with Dan's team on a test settlement run in CMQ during the cycle and put it in the cycle plan. Record the order numbers created by each test so the settlement run can be limited to them and the results compared line by line.
Finally, keep the test as a reusable recipe: the object, the parts and their storage locations, the work centers and rates, the expected planned and actual costs and the receiver. After go-live, the same recipe becomes the corrective maintenance regression test for every SAP S/4HANA feature pack or upgrade.
| Defect found in Contoso's corrective tests | Root cause | Lesson for the test plan |
|---|---|---|
| Order settled to a closed cost center | Converted equipment kept an ECC cost center that was closed | Check receivers on in-scope technical objects before cycle 1 |
| Zero labor cost on confirmations in October | Activity prices planned only for the current fiscal year | Test confirmations in the fiscal year that go-live falls in |
| Technician could not post an unplanned issue | Role missing the goods movement authorization for order account assignment | Run the flow with production-like roles, not broad test users |
| Emergency notification without breakdown duration | Malfunction end not mandatory in the app | Check history fields in the emergency variant too |
Defects from Contoso's corrective maintenance test cycles and what they taught.
- Test corrective maintenance as one end-to-end flow, from notification to settled cost.
- Collect evidence at every layer: source documents, order costs, settlement document, cost center report.
- Add variations: emergency, external service, approvals, availability and reversals.
- Include in-flight ECC orders in a conversion.
Check your understanding · not graded
Lesson check
1. What is the final evidence for Contoso's corrective maintenance test?
2. Which negative test belongs in the corrective test set?
3. Why include an in-flight ECC order in the test?
4. Why should the corrective test run with production-like roles instead of broad test users?