Purpose

Basic Maintenance Processing reduces complex plant maintenance processes to the necessary minimum and simplifies the overall process. This process uses a simplified Web user interface to map the basic plant maintenance processes. Since the process has been kept simple, the learning time is short.

An employee discovers damage to a device (for example, coffee machine, copier, or printer). The employee uses the process for Basic Maintenance Processing to report this damage. The notification of damage reaches the person responsible for the object, who ensures that an internal or external service provider deals with the damage and repairs it.

Integration in the standard transactions of the Plant Maintenance (PM) component is retained.

In Basic Maintenance Processing, both internal and external service providers can be used.

All notifications and pieces of equipment that are created within Basic Maintenance Processing can also be processed with the standard transactions of Plant Maintenance.

Prerequisites

You have implemented Business Add-In (BAdI) ILM_BE_ENHANCEMENTS and defined the necessary data.

You can check your Customizing settings using report RILMCUSTCHECK.

Process Flow

The creation of notifications in Basic Maintenance Processing comprises the following steps:

You create a notification.

Enter a description of the problem and the reporter.

You can also specify the affected piece of equipment with its location and room. You can also select the priority. You also have the option of creating a long text to describe the problem in detail. You can specify whether the malfunction is a breakdown.

The notification can be deleted as long as no service provider has been requested. The notification then has the status Flagged for Deletion (DLFL).

For more information about the special features of equipment processing in Basic Maintenance, for example, creating a new piece of equipment, see Equipment Processing .

To request a service provider, enter the equipment and a processor.

Internal service provider

Before you can request an internal service provider, a personnel number must be assigned to him or her in the system.

You can print the relevant shop papers.

External service provider

Before you can request an external service provider, a vendor master record must be recorded in the system. The vendor master record must be created for the purchasing organization entered in Customizing.

The system informs generated a purchase requisition, from which a purchase order can be created.

When you request a service provider, further notifications for the same equipment may already exist. If the existing notification concerns the same problem, you can assign your notification to the existing notification.

In case of any differences in the partner data, the system runs a synchronization with the existing notification.

If postprocessing is necessary, you can use the same service provider or a different one. This has the following effect on the purchase requisition:

Same service provider

No new purchase requisition is created, and no new shop papers can be printed. The processor in the order is deleted.

New service provider

A new purchase requisition is created, and new shop papers can be printed.

Once the service provider has been requested, you can replace the processor. The processor of all notifications concerning the same problem is changed accordingly.

The service provider performs the required work.

You complete the work.

Depending on the settings in Customizing, you see the Complete Work step. Depending on the Customizing settings, a goods receipt is executed for any existing purchase orders.

Since all operations for an order are confirmed, the order obtains the status Confirmed (CNF) . The processor used in the submitted notification is copied to the order.

After completion of the work, you assign one of the following evaluations:

Work OK:

If the work has been completed satisfactorily, the notification can also be completed.

Postprocessing required:

If the work requires postprocessing, request this. You can either request the same service provider again or request a different one (see point 2).

If you request the same service provider again for postprocessing, the status Confirmed (CNF) is revoked in the order.

You complete the notification.

At the same time, all the notifications belonging together are completed. The processor is replaced by the reporter of the notification. The reporter can now confirm the notification.

The individual notifications in the object list for the order are completed.

The reporter confirms the notification. The notification then has the status Flagged for Deletion (DLFL).