An SAP PM maintenance order turns a need into planned, executed, costed, and traceable work. IW31 creates, IW32 changes, and IW33 displays the order, but the outcome depends on consistency across technical object, type, priority, operations, work center, duration, components, dates, status, and closure rules.
An order may be valid in the system and impossible to execute in the field. Generic text, missing duration, unavailable material, the wrong work center, and release without known constraints push decisions to technicians and destroy comparison between planned and actual work.
The order brings together the approved need, technical object, operations, resources, materials, dates, and acceptance criteria. Spreadsheets, queues, or integrations may support the flow when they preserve the relationship among decision, execution, exception, and SAP PM history.
The maintenance order as an executable contract
The design starts before field entry. The triggering need, preconditions, decision rights, official document, acceptance evidence, and routes for unavailable assets or changed scope must already be known.
The unit of work is each executable operation with defined scope, resource, duration, and outcome. Control follows the full order cycle through reconciliation of confirmations, materials, services, cost, and open work. Keeping those levels separate prevents a closed header from hiding unfinished execution or unlike records from being counted as productivity.
Header, operations, components, and relationships
| Object or resource | Role in the process |
|---|---|
| IW31 | Creates the order with type, object, and initial data consistent with the process. |
| IW32 | Changes and plans operations, components, dates, release, and follow-up. |
| IW33 | Displays the document for verification without changing it. |
| IW38 and IW39 | Collective lists for selection, follow-up, and backlog treatment according to authorization. |
| Operation | Executable unit with work, center, duration, text, control key, and relationships. |
| Confirmation and cost | Actual execution response and economic effect that close the cycle. |
Pump P-204 with an incomplete scope
In an instructional scenario, a food plant received a notification about recurring leakage on pump P-204. The planner created a corrective order in IW31 with the correct equipment but used one operation called repair pump, estimated two hours, and omitted gasket, alignment, and hygienic release. The order was released and scheduled.
In the field, the team dismantled the assembly, found misalignment, and waited four hours for a component. Two technicians worked six hours each, so actual effort was 2 technicians × 6 hours = 12 labor-hours. Confirmation recorded only two hours, material was issued later through an adjustment, and final text said work completed. SAP showed a closed order, but history did not explain recurrence or cost.
The revised process separated diagnosis, isolation, dismantling, replacement, alignment, test, and release. Every operation received duration, skill, and evidence. The kit was reserved before release. Completion required operation-level confirmation, consumed component, found condition, return test, and notification link. The next recurrence could be compared by scope, time, and cause.
From need to technical completion
The order advances through eight verifiable decisions. SAP's Maintenance Order documentation supports the object role; order type, status, fields, and authority still require confirmation for the customer's release.
- 1. Need and technical object. Link the notification, pump P-204, approved priority, order type, and requester. Passing requires a verified object and text that does not presume a diagnosis. An ambiguous need or mismatched object returns to planning.
- 2. Executable scope. Separate diagnosis, isolation, dismantling, alignment, assembly, testing, and hygienic release into operations with outcomes and exclusions. IW33 display provides the reviewed order evidence. A generic operation cannot enter scheduling.
- 3. Resources and effort. Define work center, skill, crew size, hours per person, tools, components, and external service. In the scenario, 2 technicians for 6 hours equal 12 labor-hours. The package fails when outage duration is mistaken for total crew effort.
- 4. Readiness and release. Confirm access, isolation, hygiene, safety, material, tools, and available capacity with source, owner, and validity. An open dependency keeps the order outside ready status and carries a specific reason.
- 5. Operation-level execution. Record actual work, waiting, found condition, consumed component, and test result against the relevant operation. Confirmation, material document, and technical text must describe one sequence. An undisposed deviation remains open.
- 6. Scope change. Retain released scope, new finding, consulted authority, and the decision to amend or create another order. Field narrative cannot authorize added consumption, risk, or work by itself. Reviewers must reconstruct who decided and from which evidence.
- 7. Order reconciliation. Inspect the order and its status in IW33 or use a controlled IW38 or IW39 list according to the process. IW31 is an entry for creation, not a reconciliation source. Compare confirmations, materials, services, notification, cost, and remaining work; every difference receives a cause, owner, and due time.
- 8. Technical completion. Accept only after functional testing, hygienic release, and disposition of every open item. Approved scope may end while effectiveness evaluation continues through another governed action. Closure retains result, authority, and history link.
Choices that reshape the order
| Path | When to use | When to reject | Minimum evidence |
|---|---|---|---|
| Create in IW31 | Known demand and planner with context | Minimal text without preparation | Reviewed object, scope, and operations |
| Convert notification | Recorded and triaged occurrence | Generic notification without cause or priority | Notification, order, and triage decision linked |
| Create from plan | Approved recurring work in strategy and task list | Copied plan without execution review | Call, package, list, and order aligned |
| Create through integration | Controlled source and approved object contract | Intermediate record without response or log | SAP key, messages, queue, and reconciliation |
Who may release, change, and close
Order governance starts with order type and accountability for every status. Planning controls preparation and scheduling; execution updates evidence and remaining work; engineering defines technical acceptance; materials and cost follow their authorities; SAP and IT control configuration and integration. Release or closure without that matrix transfers a business decision to the person updating a screen.
The trail left by scope, waiting, and execution
History becomes useful when another professional can reconstruct the event without relying on technician memory. This requires retaining technical object, order type, priority, operation, work center, dates, materials, status, confirmation, cost, cause, and closure evidence. An incomplete record may close the daily routine while weakening failure analysis, actual cost, compliance, MTTR, productivity, plan review, and audit defense.
History must reconstruct the difference between planned and actual work. Operations added after release, substituted material, waiting, found condition, test, and remaining work stay related to the order. Otherwise, IW38 shows a status while reliability cannot explain why the intervention took longer, cost more, or failed again.
Work-package review before release
Build a known set of six orders: two released, one still created, one technically completed, one missing a critical component, and one waiting for an external service. Create the controlled pump P-204 case in IW31, inspect it in IW33, then run IW38 and IW39 with the same planning plant, order type, date interval, and statuses used by the planner. Every variance must resolve to an order number because an aggregate count cannot prove that the package is executable.
- Verification 1: identity created through IW31. Capture order type, planning plant, equipment P-204, and the maintenance-request reference before saving. Evidence consists of the SAP order number paired with the approved input sheet. The case passes when IW33 shows the intended technical object and no second order exists for the same controlled request.
- Verification 2: status permitting execution. Keep one created order, one released order, and one technically completed order in the sample. Record their status sequence in IW33 before and after release. The list result is correct when the approved IW38 or IW39 variant presents only the intended executable population and does not make an unreleased order look ready for scheduling.
- Verification 3: operations and planned effort. For P-204, inspect operation number, description, work center, control key, duration, and crew size. In the instructional intervention, two technicians working six hours must equal 12 labor-hours, while calendar duration remains distinct from team effort. Acceptance requires the operation total in IW33 to reproduce that load against the correct capacity resource.
- Verification 4: dates and precedence. Model an isolation predecessor followed by the mechanical intervention inside the authorized outage window. Retain basic order dates, operation dates, and the relationship between both tasks. Reject the package if the successor can start before physical release or if rescheduling pushes either activity beyond the agreed window.
- Verification 5: material and service readiness. Include a reserved component, an unavailable critical item, and an external service that has not met mobilization conditions. Attach the disposition and owner of each constraint to the review. The order may proceed only when the unavailable item blocks release under the local rule or remains unmistakably identified as an open condition, never as false readiness.
- Verification 6: IW38 and IW39 population parity. Save the selection criteria, run both lists allowed by the process, and compare order numbers instead of row totals alone. The audit pack contains variant, user, cutoff time, and the expected six-order set. A list passes when every inclusion or exclusion follows a visible status or filter and no personal default silently removes an order.
- Verification 7: governed scope change. Add an alignment-inspection operation to P-204 through the authorized change procedure, then reopen the order in IW33. Change history should identify the editor, time, and reason while the planner's list reflects the additional work. Audit failure means duration changed without trace or an earlier export remained the release basis.
- Verification 8: operation-level execution. Post actuals only for the first test operation and leave the second open. Retrieve the confirmation through the document or list used in the system and compare actual work, operation, and status with IW33. The expected outcome preserves the unfinished activity and prevents a partial posting from completing the whole order.
- Verification 9: cost and remaining work. Reconcile estimate, commitments, material consumption, service value, and available actual cost for P-204. Each relevant variance must point to the component, operation, or document that produced it. Financial review succeeds when no amount lacks an explainable object and unperformed hours remain available for replanning.
- Verification 10: technical completion. Attempt completion once with an open operation and once after all scope has been accepted. Retain the previous status, material review, confirmations, service evidence, and the technical owner's disposition. The completed case must leave the open-work IW38 or IW39 variant, remain visible in IW33, and preserve the documents supporting closure.
Capacity and readiness over the SAP object
PM Run Mobility documents order creation with fields aligned with IW31 and operation-level execution. Planning works with scheduling, capacity, shifts, skills, and follow-up for orders integrated with SAP. This does not transfer order type, strategy, settlement rule, or technical closure decisions to the product.
Across the order cycle, PM Run is a planning, mobility, and execution layer on top of SAP PM without replacing the system of record. Planning and Mobility work with integrated orders and help schedule capacity and field operations. Order type, release, cost center, and closure remain customer-governed.
Continue the technical path: SAP PM execution gaps, maintenance backlog, late reporting and indicators, work order software integrated with SAP PM.
Inspect an order before the outage starts
Returning to the instructional P-204 case, the notification records recurring leakage without assigning a cause. Before scheduling, the planner checks the technical object, observed condition, approved priority, and event relationship. The description does not declare mechanical seal failure because alignment, sealing faces, and assembly condition still require inspection.
Operations separate isolation and hygienic release, equipment access, external cleaning, alignment verification, conditional disassembly, surface examination, assembly, and test. Each step identifies duration, skill, crew size, special tool, hold point, and acceptance rule. An uncertain diagnosis cannot become premature component replacement.
Components and materials are tied to work that may consume them. A seal kit may be available, but reservation does not prove consumption. Gaskets, fasteners, and cleaning material use quantities appropriate to scope. A shortage found before release keeps the package outside ready condition and preserves the window for executable work.
Readiness must be reproducible
The review covers operating access, safety, applicable instructions, material, tools, skill, capacity, and dependencies. Every item has a source, owner, and validity. An access statement obtained three weeks ago may not cover the current date. An instrument committed elsewhere also prevents readiness. The planner records the exact restriction so that reassessment can resume from evidence.
During scheduling, the order competes for finite capacity under known rules. Duration includes preparation, execution, testing, and return to operation as defined locally. Assigning wrench hours alone understates occupancy. A short window may take the initial inspection and leave correction as later conditional work instead of compressing the whole scope.
Material scope change after release requires authority. If inspection finds different damage, the supervisor preserves the finding, controls safety, and consults engineering. Field text alone cannot authorize expansion that changes resources, risk, or expected function. A separate order may be clearer when emerging work needs its own decision trail.
Technical completion and open commitments
On field return, planning reconciles performed operations, confirmations, actual material, documents, measurements, anomalies, and remaining work. Assembly earns acceptance through its defined result. Unused reservations receive local disposition. A future recommendation becomes a notification, task-list review, or another governed action instead of disappearing in narrative.
Technical completion records that approved scope ended and every open item received disposition. It does not promise that a cause was eliminated or that the asset will never fail again. Effectiveness may require operating hours, load, or later inspection. History distinguishes completion of approved scope, return to function, and future evaluation.
A sample that exposes weak order design
An audit selects an emergency order, a preventive order, an inspection, and a scope change. For each, it reconstructs need, decision, operations, resources, execution, and outcome. Generic operations, unexplained duration, unlinked material, or closure with a loose anomaly create a defined corrective action. Order quality is judged by its ability to guide field work and preserve decisions.
When this design works, the SAP object connects need, package, capacity, consumption, confirmation, and history. The relevant gain is coherence, without using closed-order volume as proof of reliability.
Technical sources
The technical references delimit the order role, its creation, change and display transactions, and related documents. Order types, status profiles, and list variants depend on the organization's active configuration and installed release.
Frequently asked questions
What is the difference between creating and releasing an order?
Creation establishes the control object. Release authorizes the next stage according to configuration and governance. An incomplete order may exist but should not enter the schedule as ready.
Is an IW38 list the maintenance backlog?
IW38 selects order lists. Backlog depends on scope, status, date, priority, and capacity rules. The variant must be explicit before the list represents the adopted concept.
When is an order technically ready to close?
When scope is performed or formally treated, confirmations and materials agree, tests are accepted, remaining work has a destination, and evidence reconstructs the service.
What should be reconciled after execution?
Operations, hours, materials, services, cost, measurement documents, notifications, permitted attachments, status, and remaining work.
Where does PM Run fit in the cycle?
In order and resource scheduling and integrated mobile execution. The order and its business rules remain in SAP PM under customer governance.
