Below is a list of tips and tricks for the Executing Component Repair Order course. Click one of the items below to see information that may be helpful to you as you take the course.
The course should begin with a demonstration of an entire flow of both an in-house service and a customer-requested service. This makes it much easier to understand how the component repair order functionality works. It also helps to explain why and how component repair order basics are set up. The natural place to start with is the component repair order. From there, you can create a component repair order header for either in-house service or customer-requested service, create component repair order lines, reserve or receive material, define work scope, and select repair order type for performing the service.
Before you start with setting up your component repair order parts and entering your component repair order, it is important to determine in which type of environment the service is to be executed, i.e., Manufacturing or Maintenance. Depending on environment, different types of setup are required in order to receive a predefined work scope for a service type when releasing the selected repair order type.
You can facilitate and speed up the service process for small and easy services by setting up a predefine work scope for the repair order types Work Order and Repair Shop Order. You can list a number of service types for a part and connect one or several repair codes to the service types. The repair codes is a way of grouping; standard jobs for the repair order type Work Order and/or Material and operations for the repair order type Repair Shop Order. When including a service type with connected repair codes in a part’s work scope then is either a set of standard jobs or material and/or operations predefined, assuming that Work Order or Repair Shop Order is selected as repair order type for the component repair order line.
The connection between the repair codes and the service type can only be used if Repair Shop Order or Work Order is selected as supply for a component repair order line, hence not if a disposition shop order or external service order is created.
For each service type a non-inventory sales part must be connected. The sales part is then used as the invoicing object when transferring the sales lines (for the corresponding service type) to a customer order for invoicing. If the same tax code is applicable for many service types, and if the demand on statistics of the sales is low, then a recommendation is to use the same sales part for more than one service type in order to reduce the data to be maintained.
If there is a service contract defined for; the customer, the part and the service type, then the price is automatically fetched from the service contract. If no service contract exists, the price is fetched from the Part Service Definition and Pricing window. The invoice type is then always set to service price. The service contract is always the primary choice for fetching the price and the Part Service Definition and Pricing window is always the secondary choice.
The service contract offers four possibilities to differentiate the invoicing of a service type depending on the outcome from negotiations with the customer, internal decisions and the complexity of the work scope related to the service type. A part service contract line can be defined with any of the following four invoice types; Free of Charge, Invoice Plan, Fixed Price and Resources Used.
A recommendation is to create a service contract for customers with high demands on differentiated prices for different services. Without a service contract the application support of differentiated prices handling is limited to just fixed price.