Service Order 

Definition

Short-term agreement between service provider and service recipient, in which one-time services are ordered by the service recipient and resource-related billing is performed upon completion.

A service order contains the following data:

●      Header data

●      Location and account assignment data

●      Object data

●      Settlement data

●      Operation data

●      Component data

Use

The service order is used to document service tasks and customer service tasks. In particular, you can use the service order to:

●      Plan services specifically with regard to usage of material, utilities and personnel

●      Monitor the execution of services

●      Enter and settle the costs which arise from the services

The data for the service order is transferred to the history and is important for evaluations and future planning.

You can also create a one-time customer in the order and transfer the data, for example, to the sales order. For more information, see Transfer of One-Time Customer Data and One-Time Customers and Vendors.

When displaying and editing service orders, you can use preconfigured side panels to display context-sensitive data and charts and call Web services.
For more information and prerequisites, see Working with Side Panels in Plant Maintenance.

 

Structure

A service order contains operations that describe the individual work steps. An operation can be divided into sub-operations for greater detail.

Spare parts and tools that are required for the service tasks can be planned in the operation.

Integration

Using the “worklist for notifications” for a maintenance or service order, you can group together similar notifications for processing. For more information, see Worklist for Notifications.

Services that are to be performed for several similar objects installed at a customer site can also be processed using a single service order.