Using SAP GUI-Based Functions for Single-Cycle Plans

To create a maintenance plan via SAP GUI, various transactions are available:

• IP41 – create a single-cycle plan
• IP42 – create a strategy plan
• IP43 – create a multiple-counter plan

Transaction IP30 (Deadline Monitoring) is the legacy transaction for scheduling maintenance plans. It allows scheduling of groups of maintenance plans, which you can define creating a selection variant. The transaction is usually not executed in dialog mode but rather by a system job that uses the ABAP program of the transaction (program RISTRA20). Mostly the system job will be scheduled to run on a daily basis.

IP30 offers the following functions:

• Rescheduling

• Immediate start for all

• Creating call objects

You can use the Interval for Call Objects to specify a period of time for which waiting planned dates will be converted to call objects at one time.

Transaction IP30H is the HANA-based equivalent of transaction IP30. Within IP30H, the system automatically performs a preselection of due maintenance plans, so there's no need for any parameter restrictions. This ensures the system only processes maintenance plans that are due and that no call objects are missed. The system schedules a much smaller number of maintenance plans, which results in a much faster response time and an easy-to-use transaction.

A scheduling log can be displayed via transaction SLG1, object IP30H.

Scheduling Overviews

You can call scheduling overviews as in a tabular display or a tabular display with navigation tree.

You can use the maintenance plan cost estimate to determine the costs of maintenance for a specific period.

Object-Related Cost Estimate

You can determine the maintenance costs for a technical object for a specific period of time.

General Costing

General costing allows you to calculate the maintenance costs for one or more maintenance plans.

In both cases, the active maintenance dates (waiting planned dates, calls-skipped dates aren't considered) during the period in question are used for the cost estimate. If the period specified extends past the last active date, the system simulates the relevant dates.

Values are assigned to work time and material using the rates and prices valid when the cost estimate is made. Different rates (for example, for internal service) for future posting periods aren't considered.

If the maintenance of a technical system, which consists of system parts with different maintenance cycles, is processed within an order, it can be performed using a work list of requests (notifications).

The individual maintenance plans generate maintenance requests for the respective parts of the system. At time X, all requests for the technical system are collected and converted into an order. The task lists from the relevant maintenance item are then copied to the order.

The object, for which the task should be performed, is clear for each operation in the order.

The reference object for the order is usually the superior technical system (for example, the functional location), to which the order costs are settled.