Creating Follow-On Orders

You can create maintenance orders as follow-on orders for an order or order operation. When you create a follow-on order, you create a relationship to the reference order or operation. You can display this relationship in the document flow of the corresponding SAP GUI transactions. You can create follow-on orders either directly from the work overview (Create Order) or whilst you are displaying, changing, or confirming an order. You can display the relationship between the preceding order and the follow-on order in a list in the document flow of the corresponding GUI transactions.

When you create a new order as a follow-on order for an existing order, the system copies the header data of the existing order to the new order. You can use checkboxes to specify whether the system should also copy operation data, components, relationships, document links, settlement rules, and order descriptions to the follow-on order.

When you change or display an order, there are new symbols that show you whether a follow-on order or a preceding order exists for the corresponding order.

For more information, see Creating an Order with Reference and Creating a Follow-On Order.

Improved UI for User Status on Header Level

An enhanced user interface (UI) is available for setting the user status on header level in maintenance orders, maintenance notifications, and technical objects. All the user statuses that have been entered in the corresponding status profile are listed in the drop-down list for the new Set User Status pushbutton. In this list you can set a user status and even reset it, if allowed.

For more information, see Maintenance Order, Maintenance Notification and Technical Objects on the Web User Interface (PM-EQM).

Changing the Notification Type

You can use this function to allow changes to be made to the notification type when maintenance notifications are created or changed on the SAP Web UI. In Customizing you can specify which target notification types are allowed for which original notification types, so that when users change maintenance notifications, they can only change the notification type entered to one you have allowed. The original notification type and the target notification type must have the same notification category. In addition, you can only change the notification type of maintenance notifications if the notification has not yet been completed.

When the notification type is changed, the system does not assign a new notification number and all data of the original notification type is retained (such as reference objects). This also applies even if specific data is irrelevant for the target notification type. To override this behavior, implement the Business Add-In (BAdI) Checks for Extended Change of Notification Type (BADI_IQS0_NOTIF_TYPE_CHANGE).

For more information, see Changing the Notification Type.

Documents and Long Texts of Notification Codes

Codes ensure that issues can be entered in a standardized way and therefore be evaluated automatically. In Plant Maintenance, codes describe damage and malfunctions, the causes of the damage as well as its maintenance and repair, all of which is entered as technical findings in the plant maintenance history.

You can use this function to copy long texts and documents attached to codes, which you assign during notification processing, to the corresponding maintenance notifications. If the damage codes, cause codes, activity codes, and task codes you selected have long texts or documents stored in Customizing, you can copy them to the notification. The system copies the long text of the code to the Long Text column and stores any documents assigned to the code on the Documents tab page.

For more information, see Working with Notification Codes.