Completion confirmations on SAP maintenance orders

A completion confirmation is how the work actually done on a maintenance order is reported back — the time spent, the progress made, and the technical findings. It is the step that turns a planned order into real actuals: actual cost, actual labour, capacity relief, and maintenance history. An order that is never confirmed stays open and never tells you what really happened.

What a confirmation captures

A confirmation is posted against an order operation and records:

• Actual work / time — how much labour was spent (and by which work center), feeding actual cost and capacity.
• Progress — partial vs final, and any remaining work still to do.
• Dates — actual start and finish.
• Variances — a reason when actual deviates from plan.
• Technical results — findings, measurement readings, and (optionally) the goods movements for materials consumed.

Partial vs final confirmation

• A partial confirmation reports progress but leaves the operation open — used when work spans several days or people.
• A final confirmation marks the operation as completed: it sets the confirmed status, clears the remaining open capacity, and signals that no more work is expected. Final-confirming the last operation is what moves the order toward technical completion.

Getting this discipline right matters: operations left without a final confirmation keep showing as open capacity and distort the backlog.

How it is done

Confirmations can be entered in several ways depending on the process:

• Individual confirmation for a single operation (transaction IW41).
• Collective / overall confirmation for several operations or a whole order at once (IW42 / overall confirmation).
• Confirmation with goods movement when material consumption is posted together with the time (IW48), and time-sheet entry (CATS) where labour is captured centrally.
• Fiori confirmation apps for technicians, often on mobile, in S/4HANA.

Why it matters

Confirmations are where the maintenance loop closes. They produce the actual cost on the order, relieve capacity so planning stays realistic, and build the history (with measurements and findings) that drives reliability analysis. In the readable phase model, confirmations are what carry an operation from Execution through Post-execution. Skip them and every downstream KPI — cost, backlog, MTTR — becomes unreliable.

Common questions

What is the difference between a partial and a final confirmation? A partial confirmation reports progress and keeps the operation open; a final confirmation completes it, clears remaining capacity, and signals the work is done.

Can material consumption be posted with the confirmation? Yes — confirmation with goods movement (IW48) records the time and the components used together.

What happens if operations are never confirmed? The order stays open, capacity is never relieved, and there are no actual costs or history — so reporting and planning are distorted.

---

Related: planned and preventive maintenance · the maintenance order phase model · maintenance notifications. Want reliable maintenance actuals in S/4HANA? Explore our SAP PM training.