SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP PM Transaction Codes List (IW21, IW31, IE01, IL01, IP10 and More)

Plant maintenance users and consultants repeat the same few dozen transactions every day. This list groups the SAP PM transaction codes by process step so you can find the create, change, display and list variant fast.

Download:

T-code	Description	Area	Action
IW21	Create PM notification	Notifications	Create
IW22	Change PM notification	Notifications	Change
IW23	Display PM notification	Notifications	Display
IW24	Create malfunction report	Notifications	Create
IW25	Create activity report	Notifications	Create
IW28	Change notifications list	Notifications	List
IW29	Display notifications list	Notifications	List
IW51	Create service notification	Notifications	Create
IW52	Change service notification	Notifications	Change
IW53	Display service notification	Notifications	Display
IW31	Create PM order	Orders	Create
IW32	Change PM order	Orders	Change
IW33	Display PM order	Orders	Display
IW37N	Change operations list (order operations)	Orders	List
IW38	Change PM orders list	Orders	List
IW39	Display PM orders list	Orders	List
IW41	Enter time confirmation for PM order	Confirmation	Create
IW44	Change PM order confirmation	Confirmation	Change
IW45	Cancel PM order confirmation	Confirmation	Cancel
IE01	Create equipment	Equipment	Create
IE02	Change equipment	Equipment	Change
IE03	Display equipment	Equipment	Display
IE05	Change equipment list	Equipment	List
IH08	Display equipment list	Equipment	List
IL01	Create functional location	Functional location	Create
IL02	Change functional location	Functional location	Change
IL03	Display functional location	Functional location	Display
IL05	Change functional location list	Functional location	List
IH06	Display functional location list	Functional location	List
IH01	Functional location structure list	Functional location	List
IQ01	Create material serial number	Equipment	Create
IA01	Create equipment or general task list	Task lists	Create
IA02	Change task list	Task lists	Change
IA03	Display task list	Task lists	Display
IP01	Create maintenance plan	Preventive maintenance	Create
IP02	Change maintenance plan	Preventive maintenance	Change
IP03	Display maintenance plan	Preventive maintenance	Display
IP10	Schedule maintenance plan	Preventive maintenance	Schedule
IP19	Maintenance scheduling overview	Preventive maintenance	Report
IP30	Deadline monitoring for maintenance plans	Preventive maintenance	Batch
IK01	Create measuring point	Condition monitoring	Create
IK02	Change measuring point	Condition monitoring	Change
IK03	Display measuring point	Condition monitoring	Display
IK11	Create measurement document	Condition monitoring	Create
IK12	Change measurement document	Condition monitoring	Change
IK13	Display measurement document	Condition monitoring	Display
IW13	Material where-used list (BOM)	Spare parts	Report
MB21	Create reservation	Spare parts	Create
MIGO	Goods movement (issue to order)	Spare parts	Post
KO88	Settle order (individual)	Settlement	Settle
KO8G	Settle orders (collective)	Settlement	Settle
KOB1	Orders: actual line items	Settlement	Report
CR01	Create work center	Master data	Create
CR02	Change work center	Master data	Change
CR03	Display work center	Master data	Display
CL02	Maintain class	Classification	Change
CT04	Maintain characteristics	Classification	Change
SE16N	General table display	Technical	Display
SM37	Job overview (background jobs)	Technical	Report

Codes are correct for the classic GUI transactions in ECC and S/4HANA on-premise. In S/4HANA many users work through Fiori apps instead. Authorizations (for example object I_AUART or I_IWERK) decide which codes a user may run.

PM role and access review

Optional: share your PM roles and we will point out transactions that look over-granted.

Optional. The tool and every export work without this. No spam.

How to use the list

Search by code, such as IW3, or by words such as measuring point or confirmation. The naming pattern helps: IW is work and notifications, IE is equipment, IL and IH are functional locations and lists, IA is task lists, IP is maintenance plans and IK is measuring points. The last digit is usually 1 create, 2 change, 3 display. List transactions like IW38 and IE05 let planners mass-change objects from one screen.

IW21 or IW24 to start a notification, IW31 to create an order
IW41 for time confirmation, KO88 to settle
IP10 to schedule a plan, IP30 as the batch call run

The preventive maintenance cycle in transaction order

A typical preventive loop runs in this order. Create the technical objects (IL01, IE01), build the task list (IA01), create the maintenance plan with strategy or single cycle (IP01), schedule it (IP10), and let the batch job for IP30 generate orders when the call horizon is reached. Planners then work orders in IW38, issue spares with MIGO, confirm with IW41, set TECO, and finance runs KO88 or KO8G to settle costs.

Common mistakes

Most issues come from mixing up list and single transactions, or from running a plan schedule without a valid start date. Another is giving users change access to technical objects when display is enough, which causes master data drift. Set up user roles by process step rather than by module, and keep IP30 as a scheduled job with a variant per plant so that the call horizon is honoured consistently.

Frequently Asked Questions

What is the difference between IW31 and IW38?

IW31 creates a single new maintenance order. IW38 is a list transaction: it selects many existing orders by criteria and lets you change them from the list. Planners use IW38 as their daily worklist and IW39 when they only need to display.

Which transaction schedules maintenance plans?

IP10 schedules a single maintenance plan manually. IP30 is the deadline monitoring run that checks all due plans and generates calls, orders or notifications. In production, IP30 is normally set up as a recurring background job.

How do I settle a maintenance order?

Use KO88 for an individual order or KO8G for many orders at once, after the settlement rule exists and the order is technically completed. Run a simulation first to check the receiver, such as a cost center, before the real settlement.

Are these codes different in S/4HANA?

The classic GUI transactions remain available in on-premise S/4HANA, but SAP promotes Fiori apps for many tasks such as work order lists. Menu paths and some screens change, so check your system and the roles assigned to your users.

If you want users to ask for open orders, overdue plans or notification counts in plain language instead of navigating these transactions, we can show you how that works on top of read-only SAP access.

Talk to an Expert Explore More Free Tools