IW37N — Order and Operation List
IW37N is the Maintenance Order and Operation List. It selects order headers and operations in one worklist and supports authorized collective processing or mass changes. Use it for planner-level workload management, but review order and operation status carefully before mass actions because one selection can contain objects at very different execution stages.
Verified practitioner reference for IW37N — Order and Operation List. The page covers the operational purpose, correct usage sequence, key data to capture, evidence-based diagnosis, S/4HANA context, frequent mistakes, ownership and related SAP objects.
Published 20 Sept 2026· 557 words
Purpose
select maintenance orders and operations in one worklist and perform supported collective processing or mass changes. The transaction should be understood as one point in the full operational process. Master data, status, validity dates and preceding execution steps often determine what can happen here, so preserve that context before changing the symptom.
When it is used
IW37N is typically used when planners need to manage order headers and operations across a larger maintenance workload. It is also useful in project testing and support reproduction because it exposes a concrete process state. In production, keep the initial selection narrow and separate display/analysis from actions that mass-change, count, clear or post.
How to use it in practice
- Create a narrowly scoped order/operation selection.
- Review header and operation statuses before any collective action.
- Use mass change only for fields/processes approved across the selected set.
- Inspect the per-order result after collective processing.
- Re-run the list to confirm intended statuses and dates.
Key data objects
These are the fields and objects most useful for explaining a IW37N result. Record them in incident evidence and test scripts.
- maintenance order — verify the exact value, validity/status, and relationship to this transaction's business object.
- operation — verify the exact value, validity/status, and relationship to this transaction's business object.
- plant/work center — verify the exact value, validity/status, and relationship to this transaction's business object.
- system/user status — verify the exact value, validity/status, and relationship to this transaction's business object.
- dates and maintenance-plan call — verify the exact value, validity/status, and relationship to this transaction's business object.
How to prove it in the data
Prove an IW37N result by saving the exact selection and recording the affected order/operation statuses, dates, work centers, and processing log. Open representative orders in IW33 before and after a mass action. For partial failures, isolate the failed orders and compare their status or master-data prerequisites rather than rerunning the entire population blindly.
ECC vs S/4HANA
SAP Help documents IW37N as the Order and Operation List with mass-change and status-processing capabilities, including S/4HANA enhancements. Where a classic component is legacy, the page explicitly keeps that context so readers do not mistake technical availability for SAP's strategic architecture for new implementations.
Common pitfalls and how to diagnose them
- Selecting orders and operations with incompatible statuses for one mass action. Confirm the exact status and process ownership before applying a correction.
- Ignoring partial failures in the processing result. Confirm the exact status and process ownership before applying a correction.
- Mass-changing dates without checking maintenance-plan and capacity impact. Confirm the exact status and process ownership before applying a correction.
Whose problem this is
Primary ownership is the PM EAM team, with adjacent functional, technical, Security, or integration teams joining only where the evidence crosses component boundaries. Escalate with the exact object/document, organizational keys, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/iw37nERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.