Nothing Special   »   [go: up one dir, main page]

Depot Repair Type

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 3

Repair Type Processing

Oracle Depot Repair provides Repair Types that enable service


providers to be more efficient in managing the repair through process
automation. Repair Types help to classify the Repair Order and
determine the repair management processes and logistics to fulfill the
repair process.

Oracle Depot Repair supports the following Repair Types:

 Repair and Return


 Loaner, Repair and Return
 Exchange
 Advance Exchange
 Loaner
 Replacement
 Standard
 Refurbishment

Repair and Return

Use this Repair Type when a customer returns the broken or damaged
item to the service depot for repair. After completion of the repair, you
return the repaired item to the customer. This Repair Type requires:

 A return materials authorization (RMA), or Return line, to receive


the customer's broken or damaged item.
 A Sales Order, or Ship line, to ship the repaired item and invoice
the customer.

Loaner, Repair and Return

This Repair Type combines two Repair Types, the Repair and Return,
with the Loaner. The loaner concept indicates that service depot sends
the customer the loaner before the receipt of the customer's broken or
damaged item. To track the shipping and return of both the loaner and
the broken or damaged item, the system creates four charge lines. This
Repair Type requires two RMA Orders and two Sales Orders. Use this
Repair Type when a customer uptime is critical.
Exchange

This Repair Type represents a scenario when the service depot sends
an exchange item to the customer after receiving the customer's broken
or damaged item. The Exchange Repair Type assumes that the repaired
item does not return to the customer. The system can generate an
internal Repair Order for the returned item, but there is not necessarily
an association between the repaired item and the original exchange
item.

Advance Exchange

This Repair Type is the same as the Exchange Repair Type except that
the service depot can send the item to the customer before the service
organization receives the customer's broken item.

Loaner

Use this Repair Type when the service depot sends an item to the
customer solely for the purpose of renting. This Repair Type requires a
Sales Order to ship the loaner item to the customer and to create an
invoice, and an RMA order to track the return of the loaner item. A
deposit and return due date may be a requirement. The customer has no
expectation of repairs.

Replacement

A Replacement Repair Type refers to a scenario when the service depot


sends an item to the customer without expecting a return. In this
scenario, the service provider sends the customer an item to replace the
customer's item. The service organization can:

 Link the replacement item to the original item in the Installed Base.
 Change the status of the replaced item to indicate that it is out of
service and that the new item has replaced it.

Standard

Use this Repair Type when the service agent is uncertain about the
customer's needs. This Repair Type is flexible however, and requires the
manual creation of RMAs and Sales Orders.

Refurbishment
A Repair Order and its associated Service Request can be created in the
Spares Management of Oracle Field Service as a result of a demand for
refurbishment or replenishment. The Repair Order has a Repair Type of
Refurbishment, and has two transaction lines, Move In and Move Out.

The Move In line tracks the shipment of the defective item from Spares
Management, and its reception into the depot. The Move Out line
processes the shipment of the repaired item back to Spares
Management.

The processing of Move In and Move Out lines leverages existing


Internal Order and Internal Requisition functionality. From the depot's
perspective, defective items are received via the Internal Requisition,
and usable/repaired items are shipped via the Internal Order.

Repair Job Management

Use either of the following repair modes to manage repair jobs:

 WIP (Work In Process): Recommended for use when the repair


jobs require a series of sequential steps and materials
management. The WIP mode leverages the costing of items
through Oracle Costing.
 Task: Recommended for use when the repairs require minimal
steps that do not necessarily require a series of sequential steps.
In contrast to WIP mode, Task mode does not integrate with
Oracle Costing.

You implement and manage either of these repair modes on separate


tabs in the Oracle Depot Repair area.

During implementation, you associate the WIP or Task mode with Repair
Types. Though a service organization can have different Repair Types
associated with different repair modes, it is recommended that a service
organization select only one repair mode for all Repair Types to enhance
usability.

You might also like