Lesson 5 of 5
Test scope: what the business must prove
8 min
Listen to this lesson
Asset Management touches many teams, so a maintenance test plan needs a clear scope. The aim is to prove that a plant can keep running on SAP S/4HANA from day one: problems can be reported, work can be planned and done, parts and services arrive, hours are recorded, and costs land where finance expects them. Contoso's conversion makes the scope a little narrower than a new implementation, because configuration and data come across from ECC, but every process still needs to be proven on the converted system.
The scenarios that matter
| Scenario | What it proves | Key evidence |
|---|---|---|
| Technical object maintenance | Functional locations and equipment can be created, changed, installed and dismantled | Usage list shows each installation with the right dates |
| Corrective maintenance | Notification to order to confirmation to completion works | Statuses in the right sequence; notification linked to the order |
| Spare parts and services | Stock parts are issued and non-stock parts and services are bought | Reservation and goods issue; requisition approved at the thresholds |
| Emergency maintenance | A breakdown can be reported and repaired fast | Malfunction report with codes and times, confirmed and completed |
| Preventive maintenance | Plans generate orders on the expected dates | Calls and orders with the expected operations and dates |
| Settlement | Costs reach the right receivers | Settlement document; order balance zero; cost center report |
Contoso's Asset Management test scope, from master data to settlement.
Conversion-specific checks
Because Contoso converts its ECC system, orders that are open at cutover come across as they are. A released order with parts already issued must continue in SAP S/4HANA: technicians must be able to confirm the remaining hours, the order must complete, and settlement must move both the ECC-era and the new costs. Maintenance plans also come across with their scheduling history, so the first scheduling run after go-live must not create a flood of duplicate calls. Both belong in the test plan, run on data from the mock conversions.
- sap-eam-201Technical objectsFunctional locations, equipment, BOMs, classification and their tests
- sap-eam-202Corrective maintenanceNotifications, orders, parts, confirmation, completion
- sap-eam-203Preventive maintenanceTask lists, plans, counters, scheduling and call testing
- sap-eam-301Costs and sign-offCosting, settlement, analytics, coverage and the sign-off pack
Who does what in testing
- Rosa (maintenance planner, key user): writes and runs the maintenance scenarios, owns technical object data checks.
- Detroit technicians: run confirmations and the emergency process on the shop-floor devices they will use.
- Storeroom and purchasing key users: post goods issues, approve requisitions and POs created from orders.
- Dan's controlling team: checks activity rates, settlement and the cost center reports.
- Priya (test lead): plans cycles, tracks defects and assembles the evidence for sign-off.
Run the scenarios on realistic data: a real Detroit machine from the converted data, a real spare part with stock in 171S, a work center with a valid activity rate for the current fiscal year. Tests that run on invented objects created just for the test tend to pass, then fail on day one when users work with the converted records.
| What goes wrong in a maintenance test cycle | Usual cause | Prevention |
|---|---|---|
| Tests pass on new test machines, fail on converted ones | Converted objects carry closed cost centers or missing catalog profiles | Run every scenario on converted Detroit objects |
| Confirmations post zero labor cost | Activity rates missing for the posting fiscal year | Check rates before the cycle with Dan's team |
| Corrective test "finishes" at TECO | Settlement not run in the cycle | Book a test settlement run in CMQ |
| Preventive calls appear twice after cutover | Deadline monitoring ran in ECC and again in S/4HANA | Stop ECC scheduling jobs in the cutover plan |
Four classic failures of maintenance testing in a conversion and how Contoso prevents them.
- Scope the test from master data through corrective, emergency and preventive maintenance to settlement.
- Every scenario needs named evidence: statuses, usage lists, material documents, requisitions, settlement documents.
- A conversion adds in-flight orders and converted maintenance plans to the scope.
- The process owner signs on evidence, not on a count of passed test cases.
Check your understanding · not graded
Lesson check
1. Which evidence best proves that maintenance costs reached the right place?
2. Why are in-flight orders part of a conversion test scope?
3. What should a preventive maintenance test prove?
4. Why should maintenance tests run on converted Detroit machines rather than new test objects?