Work/Service Order 

Definition

R/3 document containing processing data that can be transferred from the R/3 Maintenance and Service Management (MSM) system to Computer-aided Scheduling & Dispatch (CSD/MF) software.

Use

A work order may contain multiple operations, which in turn can contain multiple sub-operations. A work/service order can make reference to a business partner (customer), and one or more technical objects (for example, work locations, equipment). Work orders and work operations may have dependencies with one another, as well as external constraints such as permits. Tools, material and/or qualifications can be defined in the work/service order as requirements for the work.

Normally, work information provided by SAP is translated as 1 "job" per work order operation. However, for administrative expediency, the CSD system may dispatch a single "summary" of jobs instead of multiple operations in the work order. Under these circumstances, work completion transactions would normally only be generated for those work requests that were dispatched.

The CSD system may support functionality that permits feedback for jobs to be done to a "standing" work order that is not dispatched but used purely as a cost collector for a specific type of work.

Structure

The following types of work/service order data can be transferred from the R/3 System using the IORDER01 IDoc:

The IORD transaction performs the extraction of the work/service order data to build IDocs.

Integration

The selection criteria for the IDoc requires the entry of a user status code to be used to identify that the order has been transferred to and is now 'owned' by the CSD system. Data can only be extracted for the order if the user status code exists in the user status profile defined for the order.