depot repair-product specific

Upload: rama-kavirayani

Post on 07-Apr-2018

218 views

Category:

Documents


0 download

TRANSCRIPT

  • 8/6/2019 Depot Repair-Product Specific

    1/6

    Depot Repair

    Oracle Depot Repair is part of the Oracle E-Business Suite and offers an enterprise-widesolution for managing depot repair processing. It targets the repair business market from

    simple, quick repairs to routine maintenance. Oracle Depot Repair integrates with other OracleE-Business Suite modules to provide an integrated comprehensive solution for the repairbusiness sector.

    The depot repair process includes the return of broken and serviceable items, their diagnosesand repair job estimates, customer approvals and repairs management, and subsequent returnof items to customers. You use the collection of charges for materials, labor, and expenses forthe repairs to invoice the customer.

    The depot repair process also includes the processing of item refurbishments, where the itemseither belong to an internal party, or the items are received from a field service warehouse and

    then returned to the warehouse after repair.

    Customers expect quick and seamless repair processing. Oracle Depot Repair provides end-to-end repair management functionality for service organizations that are committed to deliveringa total service solution.

    Oracle Depot Repair enables service organizations to meet customer expectations, and drawmaximum benefit by improving service readiness.

  • 8/6/2019 Depot Repair-Product Specific

    2/6

    Overview of Depot Repair

    At the core of Oracle Depot Repair is the Depot Repair Workbench that provides service agentswith instant access to customer and Repair Order information. You can access a number of tabsfrom the Depot Repair Workbench. Some tabs show information about the customer, theService Request, and the service history of the item. Other tabs let you process transactions,such as: Receipt or shipment. Creation and processing of Repair Jobs and tasks.

    The Depot Repair Workbench also provides access to a knowledge base through OracleKnowledge Management.

    Navigation: Depot Repair > Repair Orders

    The title of the main window in Oracle Depot Repair is Repair Orders. As most of the OracleDepot Repair user operations start in this window, it is generally referred to as the DepotRepair Workbench.

    In the Depot Repair Workbench you can perform all service depot repair functions, includingRepair Order creation, status monitoring, receiving, and shipping. From the Depot Repair

  • 8/6/2019 Depot Repair-Product Specific

    3/6

    Workbench, you can create Repair Orders to track the activities on customer or vendor itemsreturned to service depot repair, for repair, upgrade, or overhaul.

    The Depot Repair Workbench provides integration with Oracle E-Business Application Suitemodules and components, such as Notes, Charges, Knowledge Management, Install Base, Workin Process (WIP), Bills of Material (BOM), General Ledger, Inventory, Shipping, and Receiving.

    Service organizations can start their service depot business process from the Depot RepairWorkbench. When a service agent enters the customer and item information, the Depot RepairWorkbench automatically validates the customer and item in the Install Base.

    Setup - Repair Type

    Oracle Depot Repair provides the similar functionalities as order type (line type) in ordermanagement or transaction type in account receivables. Repair Types help to classify the RepairOrder and determine the repair management processes and logistics to fulfill the repair process.These repair types enable service providers to be more efficient in managing the repair throughprocess automation.

  • 8/6/2019 Depot Repair-Product Specific

    4/6

    Oracle Depot Repair supports the following Repair Types:

    1. Loaner2. Repair and Return3. Loaner, Repair and Return4. Exchange5. Advance Exchange6. Replacement7. Standard8. Refurbishment

    LoanerUse this Repair Type when the service depot sends an item to the customer solely for thepurpose 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. Adeposit and return due date may be a requirement. The customer has no expectation of repairs.

    Repair and ReturnUse this Repair Type when a customer returns the broken or damaged item to the service depotfor repair. After completion of the repair, you return the repaired item to the customer. ThisRepair Type requires:

    A return materials authorization (RMA), or Return line, to receive the customer's broken ordamaged item. ASales Order, or Ship line, to ship the repaired item and invoice the customer.

    Loaner, Repair and ReturnThis Repair Type combines two Repair Types, the Repair and Return, with the Loaner. Theloaner 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 loanerand the broken or damaged item, the system creates four charge lines. This Repair Typerequires two RMAOrders and two Sales Orders. Use this Repair Type when a customer uptimeis critical.

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

    Advance ExchangeThis Repair Type is the same as the Exchange Repair Type except that the service depot cansend the item to the customer before the service organization receives the customer's brokenitem.

    Replacement Repair TypeAReplacement Repair Type refers to a scenario when the service depot sends an item to thecustomer without expecting a return. In this scenario, the service provider sends the customer

  • 8/6/2019 Depot Repair-Product Specific

    5/6

    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 itemhas replaced it.

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

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

    The Move In line tracks the shipment of the defective item from Spares Management, and itsreception 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 InternalRequisition functionality. From the depot's perspective, defective items are received via theInternal Requisition, and usable/repaired items are shipped via the Internal Order.

    User-to-resource link

  • 8/6/2019 Depot Repair-Product Specific

    6/6

    Select one of the users for which the issue happens and reset the link.

    1. Log on as Customer Support Responsibility

    2. Select Resources > Maintain Resources

    3. Open the Resource Form

    4. Find the Resource using the name and category

    5. Navigate to Resource Details

    6. Locate the field called User Name.If there are no values in that field click the LOV, select the user name and save the record.If there is a user name, clear the field and save the record.Then click the LOV again and select the correct user name.

    7. Log out of the application and log back in as the user that was just set up.

    8. Test again and replicate as necessary to other environments.