SAP System

______________________________________________________________

RE RISTRA20
____________________________________________________
Short Text
Deadline Monitoring for Maintenance Plans (Batch Input IP10)

Description
For scheduling, the system converts all the on-hold maintenance calls, with a date that
satisfies the call horizon, into a maintenance call object (for example, maintenance order)
The system also performs a complete rescheduling of the maintenance plan, and ensures that
maintenance calls exist for the next n days (field Scheduling period in the Scheduling
parameters screen). The system always generates at least one on-hold maintenance call.
Start deadline monitoring regularly (for example, using report variants). Deadline monitoring for
a weekly strategy should ideally run every week.

Example
Scheduling period: 30 days
Report run on: January 1, 19XX
Scheduling performed up to: February 1, 19XX

Note
Even if you have not set a scheduling period in the maintenance plan, scheduling will always
be performed once. You no longer need to schedule the maintenance plan manually.

Procedure
In the initial screen, choose between the modes Call transaction and Batch input by selecting
the appropriate field. The call transaction mode is proposed automatically in the initial screen.

Output
You can display a list of all the maintenance call objects that the system generated during
deadline monitoring.
You can display the list of maintenance orders generated using Logistics -> Plant
maintenance -> Maintenance processing -> Orders -> Display list editing.
In the field Entered by, enter the group name that the system proposes on the initial screen of
the date monitoring session.
IP1019950101 --> All maintenance orders from January 1, 1995
IP10199501 --> All maintenance orders in January 1995
IP101995* --> All maintenance orders in 1995

______________________________________________________________
SAP AG 1