Top 25 SAP PM Transaction Codes Every Maintenance Planner Should Know
SAP PM has more than 200 transaction codes, but maintenance planners actually use a few dozen day-to-day. The trick is knowing which ones matter, what each does, and how they string together into the real workflows your team runs every shift. This guide covers the 25 essential transaction codes every SAP PM planner should have at their fingertips, organized by functional module—notifications, work orders, equipment master, functional locations, maintenance plans, measurements, and reporting. Each entry explains what the code does, when to use it, and where it fits in the daily planner routine that keeps your maintenance organization running.
REFERENCE GUIDE
25 SAP PM Transaction Codes Every Planner Should Know
Bookmarkable reference covering the t-codes maintenance planners actually run daily—organized by module, mapped to real workflows, ready to use.
25Essential codes
7PM modules
90%Daily coverage
Why SAP PM Transaction Codes Matter for Maintenance Planners
Transaction codes are the keyboard shortcuts that separate fluent SAP PM users from people who still hunt through menus. A planner who knows IW31 and IW28 by reflex moves through a dozen work orders in the time it takes someone else to navigate to the same screen once. More important, t-codes are the building blocks of every documented SAP PM workflow—every step in a maintenance procedure ultimately traces back to a specific transaction. Mastery of the right 25 codes covers the overwhelming majority of what planners do day-to-day across notifications, orders, master data, scheduling, and reporting.
The Seven Functional Modules at a Glance
SAP PM organizes maintenance functionality into seven core modules, each with its own family of transaction codes. Knowing which module a t-code belongs to is half the battle of remembering what it does—the prefix usually tells you (IW = Work, IE = Equipment, IL = Location, IP = Plan, IA = Task List, IK = Measurement, MCI = Maintenance Cost Information).
IW2x
Notifications
4 codes
IW3x
Work Orders
5 codes
IExx
Equipment
4 codes
ILxx
Locations
3 codes
IPxx
Maint. Plans
4 codes
IKxx
Measurement
2 codes
MCIx
Reporting
3 codes
Together these seven modules cover roughly 90% of what a maintenance planner does inside SAP every day. Teams looking to map their actual planner workflows against these modules can sign up free to audit their daily t-code usage and identify which transactions consume the most planner time.
The 25 Essential SAP PM Transaction Codes
Below are the 25 codes organized by module. Each card shows the t-code itself, the official function name, what it actually does, and the moment in the planner workflow when you reach for it. Read this section in order the first time; bookmark the page for quick reference after.
IW2x
Notifications
4 codes
IW21
Create Notification
Creates a maintenance notification reporting an issue, defect, or maintenance request against a piece of equipment or location.
Use when: a failure, defect, or maintenance need is identified
IW22
Change Notification
Edits an existing notification to update description, priority, classification, or assign to a planner group.
Use when: triaging incoming notifications
IW23
Display Notification
Read-only view of a notification including history, related orders, and assignments.
Use when: reviewing or referencing a notification
IW28
Notification List (Change)
Mass list view of notifications with selection criteria—filter by status, priority, work center, or date range.
Use when: daily notification triage
IW3x
Work Orders
5 codes
IW31
Create Maintenance Order
Creates a new maintenance order with operations, materials, costs, and scheduling. The workhorse t-code for planners.
Use when: planning any work that requires execution
IW32
Change Maintenance Order
Edits an existing order—update operations, add materials, change dates, release for execution, or close.
Use when: order needs scope, schedule, or status change
IW33
Display Maintenance Order
Read-only view of an order with full history, settlements, confirmations, and document attachments.
Use when: reviewing or troubleshooting an order
IW39
Display Order List
Mass list view of orders with extensive filter and selection options. The reporting backbone for order-level analysis.
Use when: weekly planning, backlog review, or reporting
IW41
Time Confirmation
Records actual hours worked on a maintenance order operation, including labor type and confirmation details.
Use when: closing out completed work
IExx
Equipment Master
4 codes
IE01
Create Equipment
Creates an equipment master record with technical attributes, serial number, location, and classification data.
Use when: onboarding new equipment
IE02
Change Equipment
Edits an existing equipment master—update status, technical fields, location assignment, or partner data.
Use when: equipment relocates or attributes change
IE03
Display Equipment
Read-only view of an equipment record including measurement points, BOMs, and maintenance history.
Use when: reviewing equipment configuration
IH08
Equipment List
Mass selection list for equipment master records with extensive filter capabilities by class, location, or status.
Use when: equipment audits or fleet reporting
ILxx
Functional Locations
3 codes
IL01
Create Functional Location
Creates a new functional location representing a physical or logical place where maintenance is performed.
Use when: building plant structure
IL03
Display Functional Location
Read-only view of a functional location including its hierarchy, assigned equipment, and historical work.
Use when: reviewing location structure
IH01
Functional Location Structure
Tree view of the complete functional location hierarchy with drill-down into child locations and equipment.
Use when: navigating plant layout visually
IPxx
Maintenance Plans
4 codes
IP01
Create Maintenance Plan
Creates a preventive maintenance plan defining strategy, cycle, task list, and target object for recurring work.
Use when: setting up PM cycles for new assets
IP10
Schedule Maintenance Plan
Generates the maintenance call objects—usually orders or notifications—for upcoming scheduled PM activities.
Use when: rolling out the next planning horizon
IP30
Deadline Monitoring
Mass scheduling of maintenance plans with date selection—the backbone of automated PM call generation.
Use when: monthly or quarterly PM batch runs
IA01
Create Task List
Creates a standardized task list with operations, durations, materials, and resources reusable across maintenance plans.
Use when: standardizing repeated PM procedures
IKxx
Measurement & Counters
2 codes
IK11
Create Measurement Document
Records a measurement reading or counter value against a measuring point on equipment—operating hours, temperature, runtime cycles.
Use when: capturing meter readings for time-based PMs
IK17
Measurement Documents List
List display of measurement documents with filters by measuring point, period, or characteristic value.
Use when: trending counter values over time
MCIx
Reporting & Analytics
3 codes
MCI3
Breakdown Analysis
Statistical analysis of equipment breakdowns including frequency, MTBF, and MTTR by object class or location.
Use when: reliability reviews and root-cause analysis
MCI8
Cost Analysis
Cost analytics across maintenance orders by cost center, equipment class, or order type for budget review and variance.
Use when: monthly maintenance cost reporting
IW8W
Goods Movement for Order
Posts material withdrawal or return movements against a maintenance order—links MM to PM execution.
Use when: parts are issued from inventory to a work order
Each code above ties to a specific moment in the planner workflow. The real value emerges when you start stringing them together into the multi-step procedures that make up a planner's daily routine. Teams looking to streamline these workflows can book a free demo of the integrated planner workspace to see how the t-codes map to mobile-friendly workflows.
Power Workflows: Stringing T-Codes Into Real Tasks
Individual t-codes are building blocks. The real planner skill is knowing which codes string together to complete a complete task—from incoming notification to closed order, or from new equipment install to first scheduled PM. The four workflows below cover the highest-frequency multi-step procedures that planners run repeatedly.
01
Daily Notification Triage
IW28
List queue
IW22
Triage & assign
IW31
Escalate to order
Pull the morning notification queue, edit each one to set priority and planner-group assignment, then convert the ones requiring execution into maintenance orders. This is the first thing most planners do every shift.
02
New Equipment Onboarding
IL01
Create location
IE01
Create equipment
IA01
Build task list
IP01
Set PM plan
When a new asset is installed, build out the functional location first, then create the equipment master tied to that location, define the standard task list for recurring work, and finally configure the maintenance plan that will trigger PMs on schedule.
03
Monthly Cost Review
MCI8
Pull cost report
IW39
Drill into orders
IW33
Investigate outliers
Start with cost analytics to identify variance against budget, drill into the underlying order list to see which work drove the spend, then open individual high-cost orders to understand what happened. The standard monthly variance hunt.
04
PM Schedule Rollout
IP30
Run deadline monitor
IW39
Review generated orders
IW32
Release for execution
Mass-schedule the maintenance plans for the upcoming horizon, review the orders that get generated against capacity, then release the validated ones for execution. The backbone of the PM cycle running every month or quarter.
These four workflows cover roughly 80% of recurring planner activity. The pattern is the same in each: list view to find the relevant items, edit view to make decisions, then display view to verify or escalate. Teams that want to compress these multi-step workflows into mobile-friendly single-screen flows can sign up free to test the integrated planner workspace against their own SAP environment.
Skip the T-Code Maze for Daily Work
A 30-minute working session shows how Oxmaint's planner workspace consolidates the four power workflows into mobile-first interfaces while keeping SAP PM as the system of record—giving planners the depth without the screen-hopping.
Mastery of these 25 codes is non-negotiable for any maintenance planner, but the reality of modern operations is that most field execution—and a fair amount of planner work—now happens outside the SAP GUI. A mobile CMMS integrated with SAP PM means technicians close work orders from their phone without ever opening IW32. Planners triage notifications from a dashboard that replaces IW28's list view. The t-codes still exist in the background, but they're no longer the only path to the work.
T-Codes Versus Integrated CMMS Workflows
IW31
Create Order
One-tap order creation from notification with template defaults
IW28
Notification List
Live notification dashboard with priority sorting and visual urgency indicators
IW41
Time Confirmation
Mobile time capture at the asset with auto-pre-fill from technician sign-in
IK11
Measurement Entry
Automatic capture from IoT sensors or QR-scan measurement workflow on mobile
MCI8
Cost Analysis
Live cost dashboard with variance alerts and drill-down by category
SAP PM remains the system of record. The CMMS layer just removes the friction.
The point is not to abandon SAP PM—the system of record matters, the t-codes still execute under the hood, and planners still benefit from knowing them. The point is that maintenance teams should not have to navigate seven screens to complete a single action when one screen would do. Operations leaders can sign up free to test the planner workspace against their own SAP environment, or book a free demo to see how SAP t-codes map to the unified workspace against representative planner scenarios.
The Planner Workspace SAP Never Built
Oxmaint maps the 25 essential t-codes into mobile-first workflows that planners and technicians actually want to use—while every transaction still flows back to SAP PM as the system of record. Keep the depth, lose the friction.
Are these transaction codes the same in SAP S/4HANA as in classic SAP ECC?
For the most part, yes. The core PM transaction codes (IW21, IW31, IE01, IL01, IP01, and so on) work identically in S/4HANA on-premise. The difference shows up in the user interface: S/4HANA emphasizes Fiori apps that wrap many of the classic transactions in modernized UIs, and S/4HANA Cloud may restrict access to certain GUI transactions in favor of Fiori-only flows. The underlying business logic and data structures remain consistent, so planner skills transfer cleanly.
What's the difference between IW31 (Create Order) and IW21 (Create Notification)?
Notifications report the existence of a maintenance need—a defect, a request, a problem to investigate. They don't necessarily require execution. Orders represent the actual planned work to address something, with operations, materials, costs, and assigned resources. The standard flow is notification first, then order if execution is needed. Some notifications close without ever becoming orders if they're informational or get triaged out. Knowing when to use each is fundamental planner discipline.
Do I need to use all 25 codes every day, or is the list more aspirational?
No planner uses all 25 daily. A typical planner touches 8–12 codes on any given shift, with the specific mix depending on role. Order planners live in IW31, IW32, IW33, IW39, and IW28. Reliability planners spend time in MCI3, MCI8, IK17, and IH08. Master data specialists work in IE01, IE02, IL01, and IA01. The full 25 represents the working vocabulary a maintenance planner should have available—not what they exercise every shift.
How do these transaction codes change when SAP PM is integrated with a modern CMMS?
The codes don't change—they still execute the same business logic in SAP. What changes is who runs them and how. With CMMS integration, technicians close work orders from mobile devices that call IW32 behind the scenes without exposing the screen. Planners triage notifications from dashboards that consolidate IW28's list view with priority sorting and visual cues. The transactions still happen; the workflow just moves out of the SAP GUI for the parts of the job where the GUI added friction without adding value.
Are there mobile-friendly versions of these classic transaction codes?
SAP offers Fiori apps that mobile-enable many of the classic transactions—Create Work Order, My Work Orders, Manage Maintenance Notifications, and others. They work, but they're tied to the SAP environment and licensing model, and the depth varies by app. Third-party CMMS platforms typically offer richer mobile workflows by integrating with SAP via OData APIs and presenting the same underlying transactions through purpose-built mobile interfaces optimized for technician and planner workflows.
