Show TOC

Perform Setup - Plant Maintenance

In this step you can initialize the information structures of the Plant Maintenance Information System.

The following reports are available for this purpose:

This report is designed for the statistical setup of file PMCO (order costs).
This report is designed for the statistical setup of the information structures in Plant Maintenance.
The following events are taken into account:

The statistical setup of information structures is necessary in the following situtaions:

If you have already created maintenance orders in the 2.2 system, you must set up the PMCO file (cost view for maintenance orders). Use the report RIPMCO00 for this purpose. You need to start this report after you upgrade from a 2.2 System to a 3.0 System. This report must be carried out successfully before the information structures of the Plant Maintenance Information System can be set up via the report RIPMS001.

The statistical setup of the PMIS can take a great deal of time if the data volume is large.

For this reason, you find selection parameters in the report that limit the data volume of documents to be considered.

If you can restrict your selection period, then the run-time can be reduced considerably.

If you started with Release 3.0, you always need to start the report RIPMCO00 if you have changed the value categories in Customizing. You then have to carry out the statistical setup of the information structures.

Caution

The file PMCO is the basis file for the information structures of Plant Maintenance, therefore you absolutely must perform the statistical setup of this file before you set up the information structures.

Standard settings

If you started with Release 3.0, the information structures will be automatically and correctly set up by the update programs.

The system will then fill in the field Name of run with the first two letters of the user name and the current date.

Additional functions

In the Plant Maintenance Information System, the system automatically makes a log after every completed Online run.

This log can be printed, but not saved.