Planned and preventive maintenance in SAP S/4HANA

SAP S/4HANA separates the order that plans and pays for maintenance work from the maintenance plan that generates preventive work automatically on a schedule. Understanding both — the maintenance order and the maintenance plan engine — is what lets a team move from reacting to breakdowns toward planned, recurring, compliance-driven maintenance.

The maintenance order

A maintenance order enables the planning, execution, documentation, and cost allocation of a piece of work. It has two layers:

• Header data — valid for the whole order: order type, the technical object, the maintenance activity type, responsibilities (planner group, work center), scheduling dates, system condition, and the cost estimate.
• Operations — the individual steps of the work, each of which can carry internal labour, external services, and material/component requirements.

The order type (for example planned, preventive, or project work) and the maintenance activity type (a grouping such as repair, inspection, or preventive service) classify the order for reporting and control. As work proceeds, the order moves through system statuses (assigned automatically by the system, e.g. created → released → technically completed) and optional user statuses (set manually, often to drive an approval gate). For planned and preventive orders, SAP typically uses forward scheduling — start from the basic start date and calculate forward.

The maintenance plan: preventive work, automatically

Preventive maintenance is driven by a maintenance plan, which combines:

• a maintenance strategy (the rules — time-based cycles like every 3 months, or performance-based cycles like every 500 operating hours),
• a task list (the standard work to perform), and
• the scheduling that generates calls.

When the plan is scheduled, SAP looks ahead by the call horizon and automatically generates the due maintenance calls — which become maintenance orders (and/or notifications) ready for the planner. This is the engine that turns a maintenance policy into a steady stream of due work without anyone remembering to raise each order.

Planned vs preventive vs breakdown

• Breakdown / reactive — unplanned, triggered by a malfunction notification. Speed first.
• Planned — known work, planned ahead and scheduled, but not on a recurring cycle.
• Preventive — recurring work generated by a maintenance plan and strategy. Compliance first.

This split lines up with the standard EAM scope items (reactive 4HH, proactive 4HI) and runs through the readable phase model.

Why it matters

The maintenance order is where cost, materials, and labour come together, so its data quality drives every cost and reliability KPI. The maintenance plan is what makes prevention systematic — shifting effort from emergency repairs to scheduled work, which is cheaper and safer. Getting strategy, cycles, and call horizon right is the difference between a plan that pre-empts failures and one that floods planners with mistimed calls.

Common questions

What is the difference between a maintenance order and a maintenance plan? The order plans and executes one piece of work; the plan is the recurring engine that generates preventive orders on a schedule.

What does the call horizon do? It controls how far ahead the maintenance plan generates due calls — too short and work is generated late, too long and the order list fills with work that is not yet due.

Time-based or performance-based cycles? Time-based triggers on the calendar (e.g. quarterly); performance-based triggers on a counter (e.g. operating hours or output). A plan can combine them.

---

Related: the maintenance order phase model · planning buckets · Resource Scheduling (RSH) · maintenance notifications. Moving from reactive to preventive in S/4HANA? Explore our SAP PM training.