IW41 — Enter Time Confirmation for Maintenance Order
IW41 records actual work, dates and personnel against a maintenance or service order without requiring the user to know the operation number in advance. It writes to the confirmation table AFRU, updates operation actual values, and can trigger order status changes if the final confirmation indicator is set. It does not replace technical completion, which happens separately in IW32 or via business completion.
This page covers the IW41 time confirmation transaction used in Plant Maintenance and Customer Service to record actual labour and time against an order operation. It focuses on the operation-selection ambiguity that causes most wrong confirmations, the final-confirmation flag that controls downstream status, and how to trace a confirmation back through AFRU and AFVC in the data.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,119 words
Purpose
IW41 posts an actual time confirmation against a maintenance or service order. Unlike operation-level confirmation transactions, IW41 is order-driven: the user enters the order number and the system either proposes the single open operation automatically or presents a list if the order has several. This is the structural fact behind most confusion with IW41 - technicians and clerks frequently confirm the wrong operation on multi-operation orders because the system's default proposal is accepted without checking. The confirmation records actual work, actual dates, personnel number, and optionally a final confirmation flag that tells the system no further work is expected on that operation. It is a posting transaction, not a planning one - it does not change planned values, only actuals.
When it is used
IW41 is used after physical work on an order has been completed or partially completed, and before the order is settled to a cost object. It sits between order release (via IW31/IW32) and settlement or technical completion. A consultant reaches for IW41 specifically when a single confirmation needs to be entered against an order without first opening the order itself - it is faster than navigating into IW32 and drilling into the operation overview. In S/4HANA landscapes, technicians increasingly use a Fiori time confirmation app or CATS-based time entry instead, with IW41 reserved for back-office correction, catch-up entries, or environments where the Fiori role has not been rolled out.
How to use it in practice
- Call IW41 and enter the order number in the initial screen
- If the order has one open operation the system proposes it automatically; if it has several, select the correct operation from the list rather than accepting the default
- Enter work center, personnel number, actual work (hours) and actual start/finish dates
- Set the final confirmation indicator only if no further work is expected against this operation
- Add a long text or reason if the site requires documentation of the work performed
- Save; the system generates a confirmation number and confirmation counter for the posting
Key data objects
- AFRU - the confirmation itself: order number, operation, confirmation counter, actual work, actual dates, personnel number, final confirmation flag, reversal indicator
- AFVC - the order operation record, whose status and actual quantities are updated when the confirmation is posted
- AFVV - operation values including cumulative actual work, used to compare planned versus actual
- COEP - CO actual cost line item generated when the confirmed work carries a cost rate through the activity type and work center
- JEST - object status records, updated if the final confirmation moves the operation or order toward a completed status
How to prove it in the data
Start in SE16 on AFRU filtered by AUFNR for the order in question. Check RUECK for the confirmation counter, ISTBER or ISM01/ISM02 style actual work fields for the hours posted, and STOKZ for a reversal flag - a reversed confirmation still shows in AFRU but is logically cancelled. Join AFRU to AFVC on AUFPL and APLZL to see which operation number and description the confirmation actually landed against; this join is the fastest way to prove a technician confirmed operation 0020 when they meant 0010.
ECC vs S/4HANA
IW41 is unchanged as a GUI transaction on S/4HANA and remains fully supported; the underlying data model for orders and confirmations has not been restructured in a way that affects this transaction's use. What has shifted is the front end - many sites push technicians toward a Fiori confirmation app or mobile app instead of GUI access, leaving IW41 mainly for planners, back-office corrections, and mass catch-up entry. No transaction replacement has occurred.
Common pitfalls and how to diagnose them
- Wrong operation confirmed: on multi-operation orders IW41 proposes an operation by default and users frequently accept it without checking the description. Diagnose by pulling AFRU joined to AFVC and comparing the operation text against what the work order actually describes.
- Order status stuck open: if the final confirmation indicator was never set, the order or operation never reaches a completed status even though all real work is done. Check AFRU for the flag before assuming a workflow or status profile problem.
- Attempted deletion instead of reversal: a posted confirmation cannot simply be deleted once cost or status effects have propagated. The correct fix is a reversal confirmation, which creates a second AFRU record with STOKZ set and nets the original. Deleting the underlying line directly in the table is never the answer.
- No cost posted despite hours confirmed: happens when the work center has no cost center or activity type assigned, or the controlling area rate is missing for the period. Confirmation succeeds in AFRU but COEP shows no corresponding line - check the work center cost center assignment first.
- Time overlap errors for a personnel number: the system can reject a confirmation if the person is already booked for overlapping hours on another order in the same period; this is a data integrity check, not a bug, and the fix is correcting the actual times entered.
- Order already technically complete or closed: IW41 blocks new confirmations against orders with a TECO or closed status. If a legitimate late entry is needed, the order status has to be reopened by the order owner first, which itself needs a decision on who approves that reopening.
Whose problem this is
This is functional territory, owned by the PM or CS consultant responsible for order execution and confirmation configuration, particularly the confirmation parameters and status profile. ABAP involvement is limited to custom validation or user-exit logic on confirmation posting. Basis is not involved unless authorization objects for confirmation transactions are misconfigured. A good handover includes the order number, operation number, confirmation counter, and whether the issue is a wrong posting, a missing cost, or a stuck status.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/iw41ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.