Ansicht
Dokumentation

RISTRA21 - Maintenance Plan Deadline Monitoring - Batch Input IP10 - Using MHIS

BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by SAP AG.

Description

The system converts all scheduling records on hold, whose call date lies within the selection, into maintenance orders.
The system also performs a complete rescheduling for the selected maintenance plans. When doing this, it always ensures that scheduling records are available for the next n-days (field Scheduling period on the screen Scheduling parameters).

Example

Scheduling period:,,,,30 days
Report run on:,,,,,,01.01.XX
Scheduled until:,,,,01.02.XX

Note

Even if you have not explicitly set a scheduling period, scheduling is always performed at least once. The maintenance plan is lengthened automatically, it is therefore no longer necessary to adjust it manually.

Note that only maintenance plans, which have on-hold calls within the specified call date, are scheduled. No other maintenance plans are scheduled.

Therefore, you should organize the following constellations:

1. The system reverts to the current call dates. If you are working with a positive shift, the call date can be changed during scheduling based on completion confirmations. It may be that the call date shifts so far into the future that no order is generated. On the other hand, a negative shift may result in the fact that an order should have already been called since the call date has moved into the past.
2. For performance-based maintenance, it is also possible during scheduling to adjust the call date through previously entered measurement documents. If you want all performance-based maintenance plans to be scheduled whilst the report is run, you can select Schedule all performance-based plans. However, note that this directly affects the runtime.

Procedure

Initially, you must distinguish between the Call transaction and Batch input modes, by selecting the appropriate field. On the initial screen, the call transaction mode is proposed automatically.

Requirements

No special prerequisites are required for the scheduling run. You should create report variants which are then started cyclically using system services. Deadline monitoring for a weekly strategy should ideally run every week.

Output

You can request a list of all maintenance plan calls which were generated during the deadline monitoring run.

To do this, choose Logistics -> Plant maintenance -> Maintenance processing -> Orders -> List editing -> Display.

Example

In the field Entered by, enter the group name which the system proposes on the initial screen for the deadline monitoring run.

IP1019950101,,--> All maintenance orders from 01.01.1995
IP10199501,,,,--> All maintenance orders in January 1995
IP101995*,,,,--> All maintenance orders in 1995

TXBHW - Original Tax Base Amount in Local Currency   General Material Data  
This documentation is copyright by SAP AG.

Length: 3645 Date: 20240531 Time: 173407     sap01-206 ( 65 ms )