In SAP Plant Maintenance, A Maintenance Order can be created by the following:


  • Scenario 1 : A maintenance order is automatically created in a maintenance item by the maintenance plan
  • Scenario2 :  The maintenance notification is entered at some remote location.  A maintenance order is created for the notification by the person responsible
  • Scenario 3 :  In the maintenance order, several notifications are combined into one or more objects
  • Scenario 4 :  The Maintenance order is created directly = Malfunction-based Maintenance/Emergencies
  • Scenario 5 :  An activity report for an existing maintenance order is entered subsequently as a technical confirmation.





ImageIn SAP Plant Maintenance, when a Maintenance Plan is created, the cycle is assigned and defines the interval for the call dates and thus for the creation of orders.

ImageIn addition, different scheduling parameters can be assigned in order to adapt the call dates to various requirements.

– The Cycle Start determines the date from which call dates are to be calculated.

– The Shift Factor enables you to react to early or late confirmation.  They are stated as a    percentage related to the cycle.

Call Dates are calculated on the basis of scheduling parameters.  For each call date, an order is created.

ImageThe changes in the schedules will vary depending on what you declare on the Early/Late Shift Factors and in the Tolerance Level of your Maintenance Plan.

For Example:

A Maintenance Plan shows the shift of a planned date triggered by a late confirmation.  The following parameters are taken as a basis:

Cycle start:  01/03/98                            – Cycle duration:  3 months

Planned dates:  01/06/98, 01/09/98    – Tolerance for late confirmation:  10%

Shift factor:  50%                                   – Confirmation:  15/06/98

ImageThe tolerance always refers to the shortest cycle, so that in this case the tolerance is 9 days (10% of 90 days).  The shift factor always refers to the total number of late days.  As the confirmation date is outside the tolerance of 9 days, the shift factor of 50% of 14 days = 7 days applies.  The newly derived planned date is therefore the 08/09/98 (instead of the 01/09/98).




ImageThe Maintenance Strategy consist of several maintenance packages. It is the scheduling rule for preventive maintenance.

ImageThe Scheduling Indicator determines the type of scheduling :


– time-based

  •     time-based with key date
  •     time-based as per factory calendar
  •     performance-based

A Maintenance Strategy can be assigned with Maintenance Packages.  The packages of a strategy can have different cycle units (for example month, year).  However, they must always have the same dimension (for example time).

ImageMaintenance Packages define how often certain operations are to be performed.As Part of the Maintenance Strategy,  Maintenance packages can be assigned to the operations of a task list.

The Parameters of a Maintenance Package are the following:

– Package number

   – Description

   – Cycle length

   – Unit of measurement

    – Hierarchy

When two packages fall due at the same time, the hierarchy determines which package    is carried out.

    – Offset

The offset determines the first due date of a package.

– Preliminary/follow-up buffer

The preliminary and/or follow-up buffer defines the tolerance of the envisaged start and end dates of a package.

Maintenance Task Lists can be created with preventive maintenance in mind.  The following steps are required to prepare tasks lists for use in Strategy Maintenance Plans. Where a Maintenance Strategy is defined in the Task List Header.

The different Operations of the task list are then assigned to Maintenance Packages to define the frequency at which the operations need to be carried out.