What is SAP PM_ORDER?

PM_ORDER is the SAP archiving object for plant maintenance and service orders.

PM_ORDER is the SAP archiving object for plant maintenance and service orders, archiving the order header, operations, components, costs and status history. Orders qualify only after technical completion, settlement, business completion and the residence times that follow the deletion flag and deletion indicator.

How PM_ORDER works

A maintenance order spreads across several tables: AUFK and AFIH for header data, AFKO and AFVC for operations, RESB for reservations, cost totals and status tables JEST and JCDS. PM_ORDER writes all of them to one archive file per order so the record stays complete.

Orders move through statuses. Technically complete (TECO) ends the work, settlement moves costs to their receiver, and business completion (CLSD) prevents further postings. Then a deletion flag is set, followed by a deletion indicator after the first residence time. Archiving happens after the second.

Notifications are archived separately with PM_QMEL, and equipment master records with their own object.

How to archive maintenance orders with PM_ORDER

  1. Set orders to TECO in IW32 or in bulk through the IW38 list.
  2. Settle costs (KO88 or collective settlement) so the balance is zero.
  3. Set business completion (CLSD).
  4. In IW38, select closed orders and set the deletion flag through the list edit.
  5. In SARA, enter PM_ORDER and maintain residence times under Customizing.
  6. Run preprocessing where available, then a write variant in test mode.
  7. Run production write and delete, and check the log for skipped orders.
  8. Archive related notifications with PM_QMEL in a coordinated run.

Users need S_ARCHIVE for PM_ORDER. Avoid running during settlement at period end.

Key parameters

Parameter or field What it controls Recommended setting or note
Order type Which orders are archived Archive one type at a time
Residence time 1 Deletion flag to deletion indicator Long enough to reverse errors
Residence time 2 Deletion indicator to archiving Align with audit and warranty needs
System status TECO, CLSD, DLFL, DLT Only closed and flagged orders progress
Planning plant Scope of the run Useful for staged rollout
Object Purpose When to use it Status
PM_ORDER Maintenance and service orders Closed orders Current
PM_QMEL Maintenance notifications Closed notifications Current
CO_ORDER Internal orders Controlling orders Current
PP_ORDER Production orders Manufacturing Current
JEST / JCDS Status and status history All orders Current

Common issues and troubleshooting

Why can PM_ORDER not archive my maintenance orders?

The order is not CLSD, still has a balance, has open purchase requisitions or commitments, or residence times are not met. The write log lists the reason.

Why can I not set the deletion flag in IW38?

Usually settlement is incomplete or there are open reservations or purchase orders. Close those first.

Why are notifications still visible after archiving orders?

Notifications have their own archiving object, PM_QMEL. Run it separately.

PM_ORDER in S/4HANA migration and decommissioning

Maintenance history shows that assets were inspected and repaired as required. Safety regulators, insurers and warranty claims rely on it, and for long-lived assets such as pressure vessels, pipelines or aircraft components, it may be needed for the asset’s whole life.

The risk is retiring the system while the assets are still running. Archived orders without equipment master data or notifications lose their meaning. Retain orders, notifications and equipment together, as covered in Archon’s application decommissioning approach.

  • List assets still in service and their maintenance history years.
  • Archive orders and notifications as one set.
  • Retain equipment and functional location master data.
  • Keep measurement documents linked to inspections.
  • Test retrieving an asset’s full history by equipment number.

Frequently asked questions

What is PM_ORDER in SAP?

PM_ORDER is the SAP archiving object for plant maintenance and service orders. It archives the order header, operations, components, costs and status history once orders are technically completed, settled, closed and past their residence times. Notifications are archived separately with PM_QMEL.

How do I archive plant maintenance orders in SAP?

Complete orders with TECO, settle costs, set business completion and then set the deletion flag, often in bulk through IW38. After residence times pass, run PM_ORDER in SARA with test mode, then write and delete. Archive notifications with PM_QMEL. Coordinate both runs.

What is the difference between PM_ORDER and PM_QMEL?

PM_ORDER archives maintenance and service orders, which hold planned work, costs and confirmations. PM_QMEL archives maintenance notifications, which record the reported problem or request. Both are usually needed to reconstruct an asset’s maintenance history. Archive them in coordinated runs so neither is orphaned.

Do maintenance orders need to be kept after decommissioning?

Often yes. Maintenance history supports safety compliance, insurance and warranty claims, sometimes for the full life of an asset. Retain orders with notifications and equipment master data so the history can still be retrieved by asset. Measurement documents from inspections belong in the same set.

Further reading

See Also

Ready to put this into practice?

See how Archon helps organizations with compliant archiving and legacy decommissioning.

Talk to us →

Archon © 2026, All rights reserved.