Depot Workbench

This chapter describes task-based procedures for different processes that a user can perform to fulfill responsibilities.

This chapter covers the following topics:

Overview of Managing Business Processes

Oracle Depot Repair improves the efficiency of the service depot repair process.

Many different users can be involved in the overall service depot process. These users and roles include the call center agent, service technician, shop floor technician, shop floor accountant, shop floor production manager, warehouse administrator, shipping administrator, receiving administrator, service administrator, accounts receivable manager, purchasing manager, HR manager, and depot manager.

For example, the call center agent logs the Service Request, the service technician diagnoses the broken part, the shop floor technician fixes the item, the shop floor accountant keeps track of the repair costs, the shop floor production manager schedules the repair jobs, and the depot manager has the overall repair process responsibility. Depending on the service organization, a user can have multiple roles. For example, the service technician can log the Service Request, and diagnose the broken part.

For key concepts and features of Oracle Depot Repair, see the Introduction to Depot Repair.

To explore the Oracle Depot Repair user interface, see Overview of Using Oracle Depot Repair.

For an overview of the processes behind different depot repair business scenarios, see Oracle Depot Repair Business Scenarios.

Note: To discover how to easily receive many items as they arrive in the depot without an RMA, see Performing Bulk Receiving.

To use an enhanced set of operations to process your repairs, see Performing High Volume Repair.

View Customer Profile

The customer profile summarizes customer information. A system administrator usually sets up the profile entries that appear in the customer profile, which contain a set of previously defined verifications. You can configure these verifications, as well as the actual range values and value definitions. The verification results appear by using the Customer Profile Engine, which is a concurrent program.

The customer profile information appears in the Profile window when you select Profile from the Tools menu in the Depot Repair Workbench. Click Refresh in the Profile region to view the latest profile information for the customer. This Oracle Depot Repair functionality lets service agents verify a customer's profile information, including Open Orders, Booked Orders, Cancelled Orders, Open Service Requests, Escalated Service Requests, Active Contracts, Expired Contracts, Cancelled Contracts, Open Repair Orders.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

Repair Order records associated with the customer must exist in the database.

Navigation

Depot Repair > Repair Orders > (Find Repair Orders window) New

Steps:

  1. In the Depot Repair Workbench, select the customer whose profile you want to view.

  2. Select Profile from the Tools menu.

    The Profile window opens.

  3. Double-click a key indicator in the profile window.

    Oracle Depot Repair shows a summary list of that profile verification. For example, double-clicking Open Service Request (a key indicator) displays the list showing all open Service Requests for the selected customer type.

    This list displays information such as the Service Request Number, incident date, problem code and resolution code.

    the picture is described in the document text

  4. Double-click any line in the summary list.

    Oracle Depot Repair displays the appropriate window containing details of the selected line.

View Coverage Information

Items that a warranty or service contract covers and that link to Oracle Installed Base, populate the coverage fields with a list of all entitlements or all active entitlements (based on option selection) that apply to the selected Repair Order.

Oracle Depot Repair permits the service agent to select a contract coverage that can be applied to the Sales Order charge lines that Charges created. The selected Contract Number automatically defaults on each charge line that is generated from the WIP Summary Report only. This option excludes those charge lines that relate to any new item upgrades and enhancements. The agent can verify active warranties existing for the item. Also, the contract selected as default in the Coverage window cannot be applied to charge lines in the Debrief Report. Instead, the contract selected at the Service Request level applies by default to the Debrief charge lines.

Oracle Depot Repair also permits the agent to find all contracts including those that have already expired. This is a handy tool for service agents to advise customers on contract coverage expiry, and service contract renewal offers to reinstate their coverage.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You can view coverage information only for an Installed Base item referenced on a Repair Order.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order referencing the item for which you want to view coverage information.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. From the top menu, select Tools > Coverage.

    the picture is described in the document text

    The Coverage window displays the configuration and entitlements for the Installed Base item referenced on the Repair Order.

    Based on option selection, you can automatically query all contracts or all active contracts applicable to the Repair Order. By selecting the Default check box beside a contract, you apply this as the default contract to the Repair Order. For detailed field descriptions, see Coverage Window.

    If you select a contract that does not specify a Price List, the application defaults the Price List that is set for the default Price List profile option. This happens if the Price List currency is the same as the Repair Order currency. If the Price List currency is not the same as that of the Repair Order, or if the profile option is not set, you can select any Price List from the list.

View Service History

Service agents can view all the Service Requests and Repair Orders that were logged against a service item. The item must be serialized and linked to an Installed Base Instance value in order for this functionality to work. This valuable functionality permits the service provider to review the service history and repair records that were recorded over the lifetime of the Installed Base item, and is especially useful when attempting to troubleshoot and diagnose repair patterns and service trends that affect the item.

The following procedures describe how to view an item's service history.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You can view the service history of only an Installed Base item. Repair Order records must exist for the item.

Navigation

Depot Repair > Repair Orders

Steps:

  1. Retrieve the Repair Order corresponding to the item, the service history of which you want to view.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. From the top menu, select Data > Service History.

    The Service History window lists all the Service Requests and Repair Orders previously opened against the Installed Base item on a Repair Order.

    For detailed field descriptions, see Service History Tab.

    the picture is described in the document text

Determine Contract and Price List Defaults at Repair Order Creation

A service contract has entitlements, for example, discounts, and response time. Entitlements are specified for each business process setup for the contract. There are cases where a contract can have entitlements that are specified for the Business Process of the Service Request, but not for the Depot Repair Business Process. If that is the case, Oracle Depot Repair cannot use that contract.

The rest of this section describes how the default contract and Price List are evaluated when you create a new Repair Order.

Default Contract

Default Price List

1. With Contract

2. Without Contract

Create a Customer Contact

You can create a new contact for a customer in the Depot Repair Workbench, and use this contact while creating your new Service Request.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

The customer whose new contact is being created must have an existing record in the database.

Navigation

Depot Repair > Repair Orders

Steps:

  1. In the Find Repair Orders window, click New to display the Repair Orders window.

    The Repair Orders window serves as the Depot Repair Workbench. From the Depot Repair Workbench, you can perform all depot processes, end-to-end.

  2. In the Depot Repair Workbench, in the Service Request Information area, click New Contact.

    The New Customer window opens.

    the picture is described in the document text

  3. In the New Customer window, select the Customer Type: Person or Organization.

    Customer Type refers to the type of the contact, and indicates whether or not the contact is a person or an organization.

    When you select the Person Customer Type, the following fields appear:

    • Title: Indicates the contact's title, such as Miss, Mr., Mrs., and Dr.

    • First, Last, Middle, Suffix: Indicate the First, Last and Middle names of the contact, and Suffixes in the name.

    • Phone: Indicates the contact's phone number. You can look up area codes in the list of values.

    • Type: Refers to the phone type, such as Work, Home, Cell, or General. Select from the list of values.

    • Relation: Specifies the contact's relationship with the customer, such as Associate of, Child of, and Benefactor of. Select from the list of values.

    • Party: Refers to the name of the customer. Select from the list of values.

    • Email: Enter the contact's e-mail address.

    • Create Account: Check box, when selected, creates an account for the new contact in your database.

    • Bill-to: Refers to the address to which you should send the contact's bill.

      When you have entered the Country in the Address field, the Address window appears where you can select the Context Value to choose the contact's Address style, such as North European, Japanese, or South American. After you select the Context Value, the Address window provides you with fields appropriate to the address style you have chosen. Enter the address, and click OK.

    • Ship-to: Refers to the address to which you should ship an item for the contact.

    • Primary: Check boxes that indicate whether the Bill-to and Ship-to addresses are the contact's primary addresses.

      If you select the Customer Type Organization, the Title, First, Last, Middle, and Suffix fields are replaced with the Organization name field. All the other fields remain the same with the exception of an additional field for the organization's URL or Web address.

  4. In the New Customer window, click OK.

    A note appears informing you that a Party Number and an Account Number (if you selected the Create Account check box) have been created and saved for the new contact.

  5. In the note, click OK.

    The application returns you to the Depot Repair Workbench.

Create a Service Request

Service Requests initiate the actions required to solve a customer problem. A Service Request is mandatory for any repair process, and needs to be created before any Repair Order can be created in the Oracle Depot Repair module.

Note: You do not have to create the Service Request explicitly before creating the Repair Order. You can enter details for both the Service Request and the Repair Order, and create both at the same time.

On the Depot Repair Workbench, you can log a customer request for assistance. The application lets you create Service Requests without having to leave the Depot Repair Workbench.

Generally, as you create a Service Request, you know which customer to associate with the Service Request. There may be situations where you are only provided with identifiers for Installed Base items, and the customer information is not provided. In this case, you can use an Oracle Depot Repair feature to find and select the customer associated with the item.

Note: You cannot create a Service Request without a value in the Item field if the profile CSD: Require Item For Service Request has been set to Yes during implementation. Setting this profile option to No lets you create a Service Request without entering a value in the Item field. Also, when the profile option is set to No, you can specify an Installed Base item without specifying an Instance value in the Service Request.

You can search for existing Service Requests and Repair Orders from the Find Repair Orders window.

For more information, see Find Service Requests and Repair Orders.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

The customer and contact records must exist in the database.Service Requests can be logged only for items recorded in inventory.

Navigation

Depot Repair > Repair Orders

Steps:

  1. In the Find Repair Orders window, click New.

    The Depot Repair Workbench opens.

    In the Service Request Information area in the Depot Repair Workbench, the Contact Type, Customer Type, and Opened Date fields default to Relation, Organization, and the Current Date respectively.

    The Severity and Status fields default to the value of the profile options Service: Default Service Request Severity and Service: Default Service Request Status respectively.

    If you need to discover the customer for the Installed Base item that will be the subject of the Service Request, perform the operations in Find a Customer for an Installed Base Item.

  2. If you select a customer using these operations, the customer-related and the item-related fields in the Service Request Information area are automatically filled in. The fields can be changed before you save the Service Request.

  3. Choose the Contact Type and Customer Type from the lists of values, and use lists of values to select the Contact, Customer, Request Type (such as Customer Call, Depot Repair, Field Service), Severity, and Status fields.

    You can also enter the date and time in the Opened field.

    Note: Contact information is not mandatory for creating a Service Request. Selecting a blank contact type in the Contact Type field disables all Contact information fields.

    The Bill-To and Ship-To address fields are populated automatically when the Customer and Contact Names are entered. The addresses always default to the primary Bill-To and Ship-To addresses of the customer. Even if you select a primary address for the Installed Base instance, the Bill-To and Ship-To address fields default only to the primary address of the customer party. Also, the list of values for both fields contains addresses for related parties, which can be for either persons or for organizations.

    For more information, see The Service Request Information Area.

  4. To validate the item against the Installed Base, select the Installed Items Only check box.

  5. Select the Item that the customer is reporting as defective from the Item list of values.

    If the item is serialized, the Serial Number appears. After validation, the Instance field is automatically populated. For a given customer, the call center agent can view all the items in the customer Installed Base.

    For more information about entering the Item, Instance and Serial Number fields, see Item Information Fields.

  6. Select the name of the person responsible for overseeing the Service Request in the Owner field from the list of values.

  7. Enter a brief summary of the repair issue in the Summary text field.

    the picture is described in the document text

  8. Click the Save icon on the toolbar to create the Service Request record.

    The application populates the Request field in the Service Request Information area with the Service Request Number. When you click any of the fields in the Repair Order Information area, the application populates the Item, Item Description, UOM, and Quantity fields from the Service Request Information area.

  9. Authorized users can launch the Service Request HTML page by clicking the hyperlinked Request Number from both the Depot Workbench and the Repair Technician Portal. This renders the Service Request HTML page in editable mode where you can update and save data. This enables you to update service request values such as Customer Bill-to and Ship-to addresses, SR Status and SR Resolution Type.

    You can enable the hyperlink through profile option, CSD: Enable Service Request Drill-down (Yes/No).

Find a Customer for an Installed Base Item

Sometimes, when you are creating a Service Request, you may know the Item Name, or its Serial Number, or its Installed Base Instance Number, but the customer name is unknown or simply not provided.

In these circumstances, you can provide the item information, and search for the customers that have the item in their Installed Base.

After you select one of the customers for the item, all the customer-related and item-related fields appear in the Service Request Information area of the Depot Repair Workbench.

This procedure is only available when you are creating a new Service Request in the Depot Repair Workbench.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must be in the process of creating a Service Request.

The items provided as search parameters must be Installed Base trackable or serialized items.

Navigation

Depot Repair > Repair Orders > New

Steps:

  1. In the Depot Repair Workbench, from the top menu, select Tools > Find Customer.

    The Find Customer window opens.

  2. Select one or more of the following fields as search parameters:

    • Item

    • Instance

    • Serial Num

    • Revision

  3. Click Find.

    The Results area shows the customers that have the item in their Installed Base.

  4. Highlight the customer whose data you want to have on the Service Request, and click OK.

  5. The Find Customer window closes, and the fields related to the customer and the item appear in the Service Request Information area of the Depot Repair Workbench.

Create a Repair Order in the Depot Repair Workbench

The depot business process starts with a Repair Order. Creation of Repair Orders occurs only against Service Requests for serviceable items.

You can create a Repair Order and its associated Service Request directly in the Depot Repair Workbench, which automates part of the process. Alternatively, you can start the process of creating a Repair Order in another Oracle application. For more information, see Alternative Ways of Creating Repair Orders.

For repair items that are under revision control, a correct Revision Number is mandatory. If your Repair Order Item is serialized, and the quantity to repair is greater than 1, you will have specify each of the Serial Numbers of the item to be repaired, for Installed Base trackable items.

Oracle Depot Repair also lets you add items to a customer's Installed Base from the Depot Repair Workbench. This enables the depot to process (Installed Base trackable) repair items that the customer purchased from outside the service organization. If you try to create a Repair Order line without specifying an Instance value for an Installed Base trackable item, the application will prompt you to add a new item instance to the Installed Base. This lets you process the repair.

Each Repair Order must have a Repair Type. When you create a Repair Order in Oracle Depot Repair, then, depending on the Repair Type, the application automatically creates one or more RMA and Sales Order lines. The RMA and Sales Order lines appear in the Logistics tab, with action types of Repair and Ship respectively. If you choose the Standard Repair Type, no charge lines are created automatically; you must create them manually.

You can also choose to create RMA charge lines manually. If you want to create the RMA charge line manually, first you must clear the check box Automatically Enter and Book RMA, during the creation of the Repair Order. Afterwards, you can create the RMA charge line, as described in Create an RMA Manually.

The following procedures describe how to create a Repair Order in the Depot Repair Workbench.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

A Service Request record must exist for the broken item in order to create a Repair Order for its repair.

Navigation

Depot Repair > Repair Orders

Note: You can also proceed to creating a Repair Order immediately after creating a Service Request record, without having to navigate to the Find Repair Orders window. In this case, start at step 3.

Steps:

  1. From the Find Repair Orders window, retrieve the pertinent Service Request.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant Service Request, and click OK.

    The Depot Repair Workbench shows the Service Request information.

  3. In the Repair Order Information area in the Depot Repair Workbench, confirm the information appearing in the table, or enter the appropriate information for the defective item.

  4. Select the Repair Type from the list of values.

    For more information on Repair Types, see Repair Type Processing. For field descriptions, see Details Tab.

    Note: A Repair Order supports a single currency. Different currencies are supported for different Repair Orders within a Service Request. The default currency is based on the default contract. If no default contract is selected, the default Price List determines the currency. If neither defaults are set, the currency selection is based on the manually selected Price List in the Details tab.

    After a charge line is created, you cannot change the currency of the Repair Order in the Details tab or select another default contract that has a Price List with a different currency. To change the currency of a Repair Order, all the charge lines have to be deleted.

  5. Optionally, enter the quantity of items to be repaired in the Qty field.

    The default quantity is 1. If you specify a Qty that is greater than 1 for a serialized item, then you will need to capture the Serial Numbers separately, after the Repair Order is created. For details, see step 13.

  6. In the Details tab, optionally enter the Promise Date (date and time) for repair completion after negotiation with the customer.

  7. Optionally, select the name of the person responsible for overseeing the repair in the Repair Owner field from the list of values.

  8. If you require estimates to be approved before you can proceed with the repair of an item, then select the check box Estimate Approval Required, else uncheck this check box.

  9. If you want the RMA line to be automatically entered and booked when you create the Repair Order, then select the check box Automatically Enter and Book RMA, else uncheck this check box.

  10. Click Save to create the Repair Order.

  11. If you have tried to create a Repair Order line without specifying an Instance value for an Installed Base trackable item, or without specifying a Serial Number for a serialized item with a Qty of 1, a message window appears.

    In the message window, you can either click Add to IB to add an item instance to the Installed Base, or you can click Save As Is to create the Repair Order without adding to the Installed Base. You can only Add to IB if the User Function Name Repair Orders: Add to IB is associated with your responsibility

    Note: If you select Save As Is, the Repair Order is created, but no charge lines are created automatically. You will have to create all the required charge lines for your Repair Type manually in the Logistics tab.

    After the Repair Order is created, the application populates the Repair Number fields both in the Details tab, and in the Repair Order Information area, with the Repair Order Number.

    the picture is described in the document text

  12. For the case where the Repair Order Item is serialized, and the quantity of the item Repair Order Item is greater than 1, continue at step 13.

    For all other cases, continue at step 18.

    Capture Serial Numbers

  13. If your Repair Order contains a serialized item, and the quantity is greater than 1, when you click Save, a message window appears, which instructs you as follows:

    • The Repair Order created will be a draft Repair Order, that is, its Repair Status will be Draft.

    • You must enter the Serial Numbers using the Capture Serial Numbers option from the Tools Menu.

  14. To complete the processing for repairing many individual serialized items, click OK in the message window, then, from the top menu, select the options Tools > Capture Serial Numbers.

    In the Serial Numbers window that appears, your main functions are to select a Serial Number for each individual item instance, and to process the Serial Numbers. Processing the Serial Numbers creates a separate Repair Order for each item instance.

  15. Select a Serial Number from the Serial Number list of values for the customer account.

    You can specify a Serial Number that does not exist yet. In this case, a message appears asking if you wish to create the new Serial Number.

  16. You can optionally select the check box Add to Order within Service Request.

    If you select this option, then, when the Serial Numbers are processed, each RMA line will be added to the same Order Number.

  17. After you have specified the Serial Numbers, click one of the following buttons:

    • Save: This saves the Serial Numbers, but does not process the values into separate Repair Orders for each Serial Number.

    • Process: This creates a separate Repair Order for each Serial Number, each with a status of Open.

    • Close: This closes the window without saving or processing the Serial Numbers.

      Note: For serialized, non-Installed Base trackable items, if you enter fewer Serial Numbers than the Qty on the Repair Order, Oracle Depot Repair creates as many Repair Orders as the Qty number of units. For example, if Qty is 10, and you enter 8 Serial Numbers, you get 8 Repair Orders with Serial Numbers provided, and 2 without Serial Numbers. You will need to provide the 2 missing Serial Numbers at time of receipt.

      Note: For serialized, Installed Base trackable items, if you enter fewer Serial Numbers than the Qty on the Repair Order, Oracle Depot Repair creates only as many Repair Orders as the number of Serial Numbers you entered. For example, if Qty is 10, and you enter 8 Serial Numbers, you get 8 Repair Orders with Serial Numbers provided.

    Checking the Logistics Tab

  18. Click the Logistics tab.

    While not technically part of the creation process, after you have created the Repair Order, you should check the Logistics tab to determine the next process to perform.

    Depending on your choice of Repair Type and whether you set the check box Automatically Enter and Book RMA, the Logistics tab generally contains one or more Return and Ship lines, each of which has a Status.

  19. In certain cases, there are no charge lines in the Logistics tab, such as when one of the following has occurred:

    • The Repair Type is Standard.

    • For a serialized repair item, you selected Save As Is in the Create IB Instance window (see step 11).

    You must create and book the required charge lines manually.

    See Create and Book a Return Line Manually and Create a Ship Line Manually.

  20. If your Repair Type involves the return of a defective item, then, in order to receive the defective item into inventory, the following conditions must apply:

    • There must be a Return line in the Logistics tab.

    • The Status of the Return line must be Booked.

    To fulfill these conditions, except for the special case where you created the Repair Order after creating an order in Oracle Order Management, proceed to create and book the Return line, as required.

    See Create and Book a Return Line Manually.

Comments:

  1. If you are creating more than one repair order line, and the value of the profile option CSD: Default Repair Order is set to Yes, then, as you arrow down from the last repair order line, the values are defaulted from the last repair order line into the new line.

  2. After creating the Repair Order record, you can attach additional information to the Service Request or Repair Order by clicking the Notes button in the Details tab

    For more information, see Create and Maintain Notes.

    After creating the Repair Order record, you can attach additional information to the Service Request or Repair Order by clicking the Notes button in the Details tab.

  3. After creating the Repair Order record, you can also search from the Diagnostics tab for possible solutions to the problem affecting the repair item.

    In the Diagnostics tab, by selecting Service Codes, either manually or as a result of a search performed in Oracle Knowledge Management, you can get the information ready to automatically create estimate lines and default Bills and Routings for WIP Repair Jobs.

    For more information, see Use the Diagnostics Tab and Oracle Knowledge Management.

Alternative Ways of Creating Repair Orders

In addition to the method of creating a Repair Order and its associated Service Request in the Depot Repair Workbench, which enables you to automatically create charge lines associated with the Repair Type, there are two other ways by which you can create a Repair Order, as follows:

Create a Repair Order Starting From Oracle TeleService

The depot agent can view activities performed against a Service Request that was initiated in the call center and transferred to the depot for resolution. You can link RMAs and Sales Orders generated through the call center to Repair Orders created within the Depot Repair Workbench.

This procedure shows an example of creating a Repair Order, where an existing Service Request already has RMA and Sales Order lines.

  1. Create a Service Request in Oracle TeleService, with a Service Request Type of Depot Repair.

  2. In the Charges tab of the Service Request, create one or more charge lines with typical Depot Repair activities for the items that require repair processing.

    A RMA charge line, for example, could include the following values:

    • Charge Line Type = Actual

    • Business Process = Depot Repair

    • Service Activity = Return for Repair

    A Sales order line, for example, could include the following values:

    • Charge Line Type = Actual

    • Business Process = Depot Repair

    • Service Activity = Ship Returned Item

  3. Submit the lines for processing.

  4. In the Navigator, using the Depot Repair Super User responsibility, navigate the path Depot Repair > Repair Orders.

  5. In the Find Repair Orders window, enter the Service Request Number you created in step 1, and click Find.

  6. When the record appears in the Results area, click OK.

    A message window informs you that RMA/Sales Order lines not linked to a Repair Order were found, and asks if you want to create a Repair Order or associate the RMA/sales lines.

  7. When you click OK, the Create Repair Order window appears, containing the not-yet-linked RMA lines.

  8. Select the lines that you want to become Return (RMA) lines in the Repair Order, and click OK.

    If there are submitted Sales Order lines in the Service Request, the Link Sales Order window appears, containing the not-yet-linked Sales Order lines.

  9. Select the lines that you want to become Ship lines in the Repair Order, and click OK.

    The Repair Order appears in the Depot Repair Workbench, with a Standard Repair Type. The Return and Ship lines appear in the Logistics tab, each with the Status of Submitted.

Create a Repair Order Starting From Oracle Order Management

This procedure shows an example of creating a Repair Order, which starts with the creation of an order in Oracle Order Management, and includes the operation of receiving the repair item into inventory.

  1. In Oracle Order Management (if you use the Depot Repair Super User responsibility, navigate the path: Order Management > Orders, Returns > Sales Orders), create a Sales Order, with the following values:

    Order Information tab:

    • Set Order Type = Mixed

    Line Items tab, Main sub-tab:

    • Specify the item to be repaired in Ordered Item, and set Qty = -1

    Line Items tab, Returns sub-tab:

    • Specify the Return Reason

    Line Items tab, Shipping sub-tab:

    • Specify the Warehouse

  2. When the order status is Booked, note the Order Number.

  3. In Oracle Purchasing (if you use the Depot Repair Super User responsibility, navigate the path: Purchasing > Receiving > Receipts), in the Find Expected Receipts window, click the Customer tab, and search for the receipt whose RMA Number you noted in step 2.

  4. In the Receipts window, select Inventory for the Destination Type, select the Subinventory.

  5. If required, specify the Serial Number or Serial Number range of the item to be received.

  6. Submit a request to run the program Create SR/RO from OM RMA Lines; specify the Organization and Subinventory parameters.

  7. When this program finishes, the Repair Order has been created, with a Standard Repair Type.

    Because the item to be repaired has already been received, the Logistics tab contains neither Return nor Ship lines.

  8. From the top menu, select Data > Activity, to find summary information in the Activity window about the receiving of the item.

Update the Repair Order Status

You can update the Status of a Repair Order either by selecting a Repair Order and then clicking the Update RO Status button from the Depot Repair Workbench or by clicking the Update Status button from the Repair Order page.

When you update the Status of a Repair Order, you can only change to a Status defined as acceptable for the current Repair Type in your setup of Repair Order Status Transitions. The list of values for New Status shows only the allowable statuses from which you can select.

For more details, see Repair Order Status Transitions in the Oracle Depot Repair Implementation Guide.

If the transition has been set up to require you to enter a reason at the time of status change, enter the Reason, else it is optional for you to do this. You may also add or edit Comments.

the picture is described in the document text

Update the Repair Type of a Repair Order

Start the process of updating the Repair Type of a Repair Order by selecting Tools > Update Repair Type from the main menu.

You can update the Repair Type of a Repair Order only if the Status of the Repair Order has previously been defined as a Status of both the current Repair Type and your intended target Repair Type.

For more details, see Repair Type Transitions in the Oracle Depot Repair Implementation Guide.

Enter the New Repair Type. The Description associated with the repair type transition appears.

If the transition has been set up to require you to enter a reason at the time of repair type change, enter the Reason, else it is optional for you to do this.

Important: Repair type transitions do not add, delete, nor default any logistic lines. After a repair type transition is performed on a repair order, you must perform manual adjustments to your logistic lines, if your organization processes require this.

Create and Book a Return Line Manually

Important: In this section, the terms RMA, RMA line, and Return line are used interchangeably.

When creating a Repair Order, then, for Repair Types that require RMA creation, the application automatically generates the Return line based on Repair Type setup. If you choose or have to create an RMA manually, then, in the Details tab, clear the Automatically Enter and Book RMA check box, before saving the Repair Order.

The main objective of creating and booking an RMA is to create an order in Oracle Order Management. When the RMA is fully interfaced with Oracle Order Management, an Order Number is associated with the RMA, and appears in the Return line.

The following procedures explain how you can create and book an RMA manually, after you have created the Repair Order. If the RMA has already been created, you can just book the RMA.

For background information about RMA creation, see Create a Repair Order in the Depot Repair Workbench.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must have created a Repair Order.

Navigation

Depot Repair > Repair Orders

Steps:

  1. Retrieve the Repair Order for which you want to create or book the RMA.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Select the Logistics tab in the Depot Repair Workbench.

    If a Return line already exists for the defective item to be returned, but the Status is not Booked, then continue at step 10.

    Creating a Return Line

  4. If you need to create a Return line, click the Action Type field in the next blank line, and select Return.

  5. Select the fields for the Return line.

    The main fields that you must select are Action Code, Service Activity, Price List, and Return Reason. For serialized items, you must select the Source Serial Number.

    Item-related fields default to the Repair Order Item. You may edit these as required.

    Note also the Add to Order field. Oracle Depot Repair lets you place all Return (RMA) and Ship lines on the same order.

    By default, all Return (RMA) and Ship lines appear on the next-highest Order Number created when the lines are transferred to Order Management.

    You can also select the specific order for the Return (RMA) or Ship line by selecting the Order Number in the Add to Order field before interfacing the specified line to Oracle Order Management.

    For field descriptions, see Logistics Tab.

    If you want to process the Return line directly to the Booked stage, continue at step 10.

  6. Select the Process Trans check box for the Return line.

  7. Select the Automate order processing steps through check box.

  8. Select the Enter Order button option.

  9. Click Process.

    Acknowledge the message in any message window that appears.

    The Status of the Return line changes to Entered or Submitted.

    Booking a Return Line

  10. Select the Process Trans check box for the Return line.

  11. Select the Automate order processing steps through check box.

  12. Select Book Order radio button option.

  13. Click Process.

    Acknowledge the message in any message window that appears.

    The Status of the Return line changes to Booked.

The Sales Order Number can optionally be hyperlinked to allow you to click on it to launch the Sales Order window in editable mode and in context of the clicked Order Number. You can enter information such as credit card number, ship method and payment details, save the order, close the Sales Order screen and return to the Depot Workbench without ever leaving.

Comments:

  1. During the processing of the Return line, when the Return line is fully interfaced with Oracle Order Management, the Order Num field is populated with the system-generated RMA Order Number.

    If you have not selected the No Charge check box, the application returns the item price to the Price field based on Price List selected.

  2. To delete a Return or Ship line, select the Return or Ship line on the Logistics tab, and click the Delete icon on the toolbar.

    Note: The Delete icon on the toolbar remains enabled as long as the Return or Ship line has not been fully interfaced with Order Management. After the order is fully interfaced to Order Management, the application disables the Delete icon, and you cannot delete the order line.

Move Items Internally

The Internal Move capability allows you to move items or parts from one location to another from a single window. The Internal Move window wraps the capabilities provided by the Internal Requisition and Internal Sales Order modules provided by Purchasing and Order Management. This new capability enables a single repair order to track both internal and external logistical operations. You can perform logistical transactions without leaving the Depot Repair interface.

Additionally, it provides the ability to create Internal Requisitions and Internal Sales Orders in one step, ship and receive Internal Sales Orders and link Internal Moves to a repair order along with RMAs and Sales Orders. The business value of this functionality is that it prevents losing track of items as they move from one location to another, enables ad-hoc routing of material to the best processing location and reduces click count to create Internal Requisitions and Sales Orders.

To move items internally:

  1. Navigate to the Find Service Requests window and select a Repair Order to open the Repair Orders window.

  2. Select the Logistics tab.

  3. Choose the Internal Move Orders option from the Actions drop down list and click Go.

    the picture is described in the document text

    The Move Items Internally page appears. The page displays the existing internal move orders linked to this repair order. The Move Details region provides the ability to enter one or more serial numbers or a serial number range.

    the picture is described in the document text

  4. To create a new internal move order, click the New Internal Move button. The Create Move Orders page appears.

  5. Enter the fields in the Internal Order Attributes region:

    • Item

    • Description

    • Quantity

    • Unit of Measure

    • Need By

  6. Enter the Operating Unit and Inventory Organization in the Ship From region.

  7. Enter the Operating Unit, Inventory Organization, and Location in the Receive Into region.

    the picture is described in the document text

  8. Click Apply to create a new internal move order. A confirmation page appears. You cannot edit any fields once an Internal Sales order is created.

    The header of the Create Move Orders page populates with the following:

    • Order Number

    • Order Status

    • Requisition Number

    • Requisition Status

    • Quantity Shipped

    • Quantity Received

  9. To Pick Release the internal sales order line, select the move order on the Move Items Internally page and click the Pick Release button. A confirmation message appears validating the pick release.

    the picture is described in the document text

  10. To Ship Confirm the internal sales order line, select the relevant move order and click the Ship Confirm button. A confirmation message appears validating the ship confirm.

    the picture is described in the document text

  11. You can receive the internal requisition associated with Internal sales order in the destination organization. If the shipping network between source and destination organization are set up as direct then the receipt automatically happens as part of ship confirm action in the source organization. Though the internal requisition is automatically received as part of ship confirm action, you must click the Receive button to refresh the receipt information in the depot schema. A confirmation message appears validating the receipt.

    the picture is described in the document text

Additionally, you can perform partial shipments and partial receipts. For example, for an Internal Order with quantity of 5, the shipping clerk ships out only 3. In this case the destination organization receives these 3 into their inventory. Later when the remaining quantity of 2 is shipped out, the destination organization receives the remaining quantity.

Find Service Requests and Repair Orders

On the Find Repair Orders window, you can retrieve Service Requests or Repair Orders from the database.

A search in Oracle Depot Repair enables you to retrieve Service Requests and Repair Orders based on parameters related to a Service Request or Repair Order (Number, Customer, Item, or Date Opened). You can use a combination of these parameters to restrict your search so as to retrieve only the Service Requests or Repair Orders that you want.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

The Service Request or Repair Order record that you want to retrieve must exist in the database.

Navigation

Depot Repair > Repair Orders

Steps:

  1. In the Find Repair Orders window, specify the parameters based on whether you want to search for the Service Request or Repair Order.

  2. The search parameters in the Service Request area include:

    • Request Number

    • Status

    • Customer Name

    • Customer Account

    • Date Opened

    • Item

    • Serial Number

    • Owner

    The search parameters in the Repair Order area include:

    • Repair Number

    • RMA / Sales Order Number

    • Internal Order Number

    • Internal Requisition Number

    • PO Num

    • Project

    • Date Opened

    • Item

    • Serial Number

    • Status

    • Job Name

    • Project Task

    Note: Performing a search based on these values searches for Project or Task values saved on the Repair Order Details tab, and not the values stored on linked Sales Orders or WIP jobs.

  3. Click Find to find matching Service Requests or Repair Orders based on the parameters you have specified.

  4. The Results region in the Find Repair Orders window displays the search results.

    You can select any of the retrieved Service Requests or Repair Orders, and click OK to view its details in the Repair Orders window, generally known as the Depot Repair Workbench.

    the picture is described in the document text

Transfer Install Base Ownership

Transfer Install Base Ownership function is performed in two ways:

Changing ownership based on the service request

You can change the ownership based on the service request.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must set up Transfer Ownership from System Administrator Responsibility.

Navigation

Depot Repair > Repair Orders

Steps

  1. Navigate to the Service Request region.

  2. Enter an SR with Install Base item instance owned by a party other than the SR party.

  3. Save the SR.

  4. Click OK when the system prompts you to change the ownership of instance.

  5. Select Change Ownership option from the Tools menu.

  6. Click Yes to commit the change in the decision window.

  7. Save the SR.

From Install Base query the instance number; you will find item's owner name is changed to new one.

Changing ownership on a repair order

You can change the ownership based on a repair order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must set up Transfer Ownership from System Administrator Responsibility.

Navigation

Depot Repair > Repair Orders

Steps

  1. Navigate to the Service Request region.

  2. Enter an SR without item details.

  3. Enter RO details with item instance belonging to another customer other than the SR Party.

  4. Save the RO.

  5. Click OK when the system prompts you to change the ownership of instance.

  6. Select Change Ownership option from the Tools menu.

  7. Click Yes to commit the change in the decision window.

  8. Save the RO.

From Install Base query the instance number; you will find item's owner name is changed to new one.

Create and Maintain Notes

Notes are used to record and manage the comments that the depot agents and technicians generated against various services. Notes in a Service Request help in recording the descriptive information about customer repair issues, any progress that the agent had done in resolving this issue, and so on. You can enter either Service Request or Repair Order notes from the Details tab in the Depot Repair Workbench.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

A Repair Order record must exist for an item before you can attach notes to the relevant Service Request or Repair Order.

Navigation

Depot Repair > Repair Orders

Steps:

  1. Retrieve the Service Request or Repair Order to which you want to attach a note.

    For more information, see Find Service Requests and Repair Orders.

  2. In the Results area of the Find Repair Orders window, select the relevant result, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. On the Details tab of the Repair Order window, select Service Request or Depot Repair in the Notes area.

  4. To open the Notes window, click Notes.

  5. In the Type field, select a note type.

  6. In the Status field, select a note status.

    The choices are: Personal, Internal, and Publish. If you use the Personal status, this note would not be viewable to any customer in a customer facing application. Employees at the depot can view Internal notes. All employees and customers can view Publish notes. You can create additional Status codes. For more information, see the Oracle Common Application Components Implementation Guide.

  7. In the Note field, enter a brief description of the note.

  8. To enter more notes, click the More button.

    The Detailed Note window opens and holds textual notes up to 32K characters.

  9. After entering notes, click OK.

  10. In the main Notes window, to specify more details for the note, specify the Related To and Value fields.

  11. Save the note.

    The note appears in the table under the Notes tab on the left. The Summary tab displays the notes as text in a chronological or reverse chronological manner. You can change the chronological view by clicking the Latest First check box.

  12. To search for existing notes, use the Find Notes functionality.

    1. Open the Notes main window.

    2. Click the flashlight icon on the toolbar to open the Find Notes window.

    3. Enter the fields such as Source, Entered By, and so on.

    4. Click Search to display the results.

Use the Diagnostics Tab and Oracle Knowledge Management

The main purpose of the Diagnostics tab is to enable you to make use of solutions to previous problems stored in Oracle Knowledge Management. Oracle Knowledge Management is a repository of solution sets that have already been contributed. Solutions to previous incidents can guide users to resolve current problems at hand.

However, even if you have not installed Oracle Knowledge Management, you can still use the Diagnostics tab to select Service Codes, which enable you to automatically create estimate lines and default Bills and Routings for WIP Repair Jobs.

This section consists of the following topics:

Diagnostic Codes and Service Codes

Depot repairs are generally repetitive in nature and the number of problems and resolutions is finite. As such, Oracle Depot Repair provides the ability to associate the potential problems with a Diagnostic Code, and to associate the potential resolutions with a Service Code. By utilizing Diagnostic Codes and Service Codes, users can quickly document repair efforts for customer charges and depot service history.

An example Diagnostic Code is DC100, whose descriptive Name is Engine Oil Light On, and a corresponding example Service Code is SC100, with descriptive Name Engine Oil Change.

For details of setting up Diagnostic Codes and Service Codes, see the Oracle Depot Repair Implementation Guide.

Using Diagnostic Codes and Service Codes with Oracle Knowledge Management

The association of Diagnostic Codes to Service Codes is done in Oracle Knowledge Management via Solutions. First, during implementation, Service Codes are linked to Oracle Knowledge Management Solutions as external objects. Then, during the authoring of Solutions in Oracle Knowledge Management, Diagnostic Codes (for example, DC100) are included in the title or body of the Solution.

Once a Diagnostic Code is associated to a Service Code and that Service Code is linked to an Oracle Knowledge Management Solution, then the repair work to be performed has been defined.

For details of associating Diagnostic Codes and Service Codes with Oracle Knowledge Management, see the Oracle Depot Repair Implementation Guide.

Using Service Codes in the Repair Order

Oracle Depot Repair enables you to automate Repair Order processing as follows:

For details of how Service Codes are used in the Repair Order, see the following:

Diagnostics Tab Usage Overview

The interface from Oracle Depot Repair to Oracle Knowledge Management is the Diagnostics tab, which is divided into three areas:

The following figure shows an overview of the standard use of the different areas of the Diagnostics tab.

Overview of Standard Diagnostics Tab Usage

the picture is described in the document text

See Also

Manage Diagnostic Codes in the Diagnostics Tab

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must have set up Diagnostic codes and Service Codes in Oracle Depot Repair.

You must have associated the Diagnostic Codes and Service Codes to Solutions in Oracle Knowledge Management.

For details of setting up and associating Diagnostic Codes and Service Codes, see the Oracle Depot Repair Implementation Guide.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order that you want to process.

    For more information, see Find Service Requests and Repair Orders.

  2. If you are not already in the Diagnostics tab, click the Diagnostics tab.

  3. If you do not want to provide any Diagnostic Codes as parameters to the search in Oracle Knowledge Management, continue at step 7.

  4. Enter a Diagnostic Code manually or select a Diagnostic Code from the list of values.

    The list shows all Diagnostic Codes that have been associated with either the Item or the Item Category of the Repair Order Item.

    For more information on setting up Diagnostic Codes, see the Oracle Depot Repair Implementation Guide.

    Note: If you enter an invalid Diagnostic Code, the list of values appears, which contains all the valid Diagnostic Codes for your Repair Order.

  5. Click the Select check box.

  6. Repeat steps 4 to 5 for as many Diagnostic Codes as you want to display.

    Note: You may click the Select All or Deselect All as appropriate any time before you click Search Solutions.

    Note: Only the Diagnostic Codes that are explicitly selected are forwarded as search parameters to the Oracle Knowledge Management search.

  7. Click Search Solutions.

    This launches two windows:

    • A Refresh linked Solutions box, with the message: Please press OK after searching for Solutions.

    • An Oracle Knowledge Management window.

      The window that is launched in Oracle Knowledge Management depends on the value of the profile option Knowledge: Search to display for integrating applications.

      If the value of this profile option is Unified Search, then the window that is launched is a Simple Search window; if the value of the profile option is Advanced Search, then the window that is launched is the Advanced Solution Search Results window.

      Continue the search process at the section Search Oracle Knowledge Management.

Search Oracle Knowledge Management

The search in Oracle Knowledge Management is the second stage of the completely integrated process which starts in the Diagnostics tab. This section concentrates on the Oracle Knowledge Management search itself, and how it provides feedback back into the Diagnostics tab.

This procedure follows immediately after you have clicked the Search Solutions button in the Diagnostics tab.

Use of the Search Parameters in Oracle Knowledge Management

The parameters passed to Oracle Knowledge Management to search for solutions are the following:

The search for solutions is performed as follows:

By utilizing the profile option Knowledge: Search results include weighting from Product, Platform and Category filters, you can narrow or widen your search results.

When the profile option is set to No, the search results contain only Solutions matching the specified Product/Platform/Category.

When the profile option is set to Yes, the results can also contain Solutions that do not match the Product/Platform/Category specified -- the Solutions that do match the Product/Platform/Category are given a boost in the scoring algorithm.

Note: Oracle Depot Repair does not make use of platform and category filters in Oracle Knowledge Management.

For additional information on how to use Oracle Knowledge Management, please refer to the Oracle Knowledge Management User Guide.

Search Result Examples

Consider the following search parameters:

With the profile option Knowledge: Search results include weighting from Product, Platform and category filters set to No, you get the following results:

With the profile option Knowledge: Search results include weighting from Product, Platform and category filters set to Yes, you get both of the following sets of results, with the first set having a higher score:

Prerequisites

You must have started the search process by clicking the Search Solutions button in the Diagnostics tab.

For details, see Manage Diagnostic Codes in the Diagnostics Tab.

Overview of Main Oracle Knowledge Management Search Procedure

the picture is described in the document text

Steps

  1. You can optionally add and edit search parameters in the Oracle Knowledge Management search window, and then perform an explicit search.

    The net objective of the Oracle Knowledge Management search is to specify whether a solution is useful or potentially useful for the current repair problem. To do this, you must first select a solution in a "search results" window, then access the solution details for that solution.

  2. If you are in the Simple Search window, click the Title hyperlink of the potentially useful solution in the Simple Search Result area. If you are in the Solution Advanced Search Results window, click the radio button beside the potentially useful solution, and click Full Solution.

    In the Solution Details window, there is a section available for you to decide the usefulness of the solution. This section is the Feedback section, whose main constituent is the question "Is the solution useful in resolving your question or problem?"

    Note: The Feedback section only appears if the solution has not already been linked to the current Repair Order. However, after a user explicitly selects an answer to the usefulness question, then the next time the Solution Details window appears for that solution, the Feedback section does not appear.

  3. In the Solution details window, scroll down to, and just beyond, the External Objects area.

  4. If the Feedback section appears, then, you can optionally respond to the question "Is the solution useful in resolving your question or problem?", by clicking Yes, Maybe, or No.

    If you choose one of these options, a confirmation message appears, indicating that your feedback was recorded.

  5. You may optionally continue in Oracle Knowledge Management, and select more Solutions for feedback to Oracle Depot Repair.

  6. When you have finished in Oracle Knowledge Management, close the Oracle Knowledge Management window.

  7. Click OK in the Refresh linked Solutions box.

    If you have linked any Solutions from Oracle Knowledge Management to a Repair Order, they appear in the Solutions area of the Diagnostics tab. Additionally, Service Codes appear in the Service Codes area of the Diagnostics tab (if any exist).

Providing Feedback into the Solutions Area of the Diagnostics Tab

In step 4, your response to the question "Is the solution useful in resolving your question or problem?" causes the following to occur in the Solutions area of the Diagnostics tab:

Providing Feedback into the Service Codes Area of the Diagnostics Tab

If the Useful Solutions returned to the Solutions area have any Service Codes associated with them, then those Service Codes will appear in the Service Codes area, together with their associated Solution Number and with their Applicable check box set.

the picture is described in the document text

Manage Solutions in the Diagnostics Tab

The main use of the Solutions area is to change the status of Solutions returned from Oracle Knowledge Management searches, in order to influence the Service Code information in the Service Codes area.

When you change the Status of a Solution in the Solutions area to Useful, any Service Codes associated with that Solution in Oracle Knowledge Management appear in the Service Codes area, and are initially marked as Applicable.

Under the following conditions:

you can retrieve the associated Task Template charge lines into the Repair Estimate tab by clicking Add Lines from Diagnostics.

For more details, see Create a Repair Estimate.

Note: From the Solutions area, you may also return to Oracle Knowledge Management to view the solution details, by clicking the Details button.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must have previously performed an Oracle Knowledge Management search for the Repair Order, and returned one or more Solutions into the Solutions area (see Search Oracle Knowledge Management)

Navigation

Depot Repair > Repair Orders

Steps

  1. If you have not already accessed the Repair Order, retrieve the Repair Order that you want to process.

    For more information, see Find Service Requests and Repair Orders.

  2. If you are not already in the Diagnostics tab, click the Diagnostics tab.

  3. Click the right-hand side of the Status field of a solution whose status you want to change.

  4. Select a different status from the list of values.

    This enables the Update Status button.

  5. Click Update Status.

    If, in steps 3 and 4, you changed the Status to Useful, existing Service Codes associated with the solution will appear in the Service Code area with the Applicable check box set on.

    Continue at step 6.

  6. If, in steps 3 and 4, you "downgraded" the Status from Useful to Possibly useful or Not useful, then an Update Solution Status message box appears, presenting the following information:

    • Service Codes associated with the solution in the Service Codes area will be marked as not applicable.

    • You may delete the Service Code in the Service Codes area manually.

    Click OK in the Update Solution Status message box.

    This unsets the Applicable check box for the associated Service Code in the Service Codes area.

    For details of deleting Service Codes in the Service Codes area, see Delete Service Codes Manually in the Service Codes Area.

  7. Optionally, repeat steps 3 through 6 for each solution whose status you want to change.

    Note: You cannot delete any Solutions from the Solutions area, you can only change the status values of the Solutions.

Manage Service Codes in the Diagnostics Tab

The topics in this section include the following:

Select Service Codes Manually in the Service Codes Area

As part of Oracle Depot Repair implementation, when Service Codes are set up, they are associated with Items, Categories, a combination of Bills and Routings, and Task Template Groups.

The main usage of the Service Codes area in the Diagnostics tab is to enable the associated elements of the Service Codes to be added to the estimate lines and WIP Repair Jobs of the current Repair Order.

The Service Codes area is populated with Service Codes in one or more of the following ways:

This section deals with the manual selection of Service Codes in the Service Codes area.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must have set up Service Codes in Oracle Depot Repair.

To make use of prior repair knowledge, you must have associated Service Codes to Solutions in Oracle Knowledge Management.

For details of setting up and associating Diagnostic Codes and Service Codes, see the Oracle Depot Repair Implementation Guide.

Navigation

Depot Repair > Repair Orders

Steps

  1. If you have not already accessed the Repair Order, retrieve the Repair Order that you want to process.

    For more information, see Find Service Requests and Repair Orders.

  2. If you are not already in the Diagnostics tab, click the Diagnostics tab.

  3. Select a Service Code from the Service Code list of values in the Service Codes area.

    This list of values that appears shows all the Service Codes that have been associated with either the repair Item or the Inventory Category of the repair item.

    For more information on setting up Service Codes, see the Oracle Depot Repair Implementation Guide.

  4. In the Code field, either enter a Service Code, or select a Service Code from the list of values.

    Note: If you enter an invalid Service Code, the list of values appears, which contains all the valid Service Codes for your Repair Order.

    By default, as each valid Service Code is entered or selected, its Applicable check box is set.

    Manually entered Service Codes do not have a Solution Number.

  5. Repeat steps 3 to 4 for as many Service Codes as you want to display.

  6. Save your changes.

Activate and Deactivate Service Codes in the Service Codes Area

You activate Service Codes in the Service Codes area by marking them as applicable.

Activating Service Codes in the Service Codes area enables the following subsequent processing options:

For more information on setting up Service Codes, see the Oracle Depot Repair Implementation Guide.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must have previously performed one or more of the following operations for the Repair Order:

Navigation

Depot Repair > Repair Orders

Steps

  1. If you have not already accessed the Repair Order, retrieve the Repair Order that you want to process.

    For more information, see Find Service Requests and Repair Orders.

  2. If you are not already in the Diagnostics tab, click the Diagnostics tab.

  3. In the Service Codes area, check the Applicable check box for each Service Code that you want to activate.

  4. In the Service Codes area, uncheck the Applicable check box for each Service Code that you want to deactivate.

  5. Save your changes.

Delete Service Codes in the Service Codes Area

You may delete Service Codes from the Service Codes area, whether they are marked as applicable or not.

Note: After the first time that you use Service Codes in a Repair Order in either the creation of a repair estimate or the creation of a WIP Repair Job, then the selected Service Codes are protected against deletion in that Repair Order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must have previously performed one or more of the following operations for the Repair Order:

Navigation

Depot Repair > Repair Orders

Steps

  1. If you have not already accessed the Repair Order, retrieve the Repair Order that you want to process.

    For more information, see Find Service Requests and Repair Orders.

  2. If you are not already in the Diagnostics tab, click the Diagnostics tab.

  3. In the Service Codes area, click the marker field to the left of the Service Code that you want to delete.

  4. From the top menu, select Edit > Delete.

  5. Optionally, repeat steps 2 through 3 for each Service Code that you want to delete.

  6. Save your changes.

Comments

If you wish to reinstate Service Codes that you have deleted, then perform one of the following operations:

Estimate Repair Charges

Depots can require a repair diagnosis of the customer's returned item in order to accurately determine the cost involved in the actual repair, upgrade, or overhaul. The depot technician typically performs this by inspecting or performing a teardown of the item to determine the required parts and labor for the repair. After completing this process, the depot provides a formal quotation to the customer for approval before any work is scheduled. During the teardown, the technician can identify individual parts, and diagnose for further service requirements using typical repair manuals and technical notes for aid.

Note: If you have set up the application to not use the Estimate functionality, by setting the profile option CSD: Enable Estimates to No, the Repair Estimate tab in the Depot Repair Workbench is not available and you cannot create a repair estimate. For more information, see the note in the topic Repair Estimate Tab.

Items for Estimates

Items for estimates must be defined in the organization specified by the profile option Service: Inventory Validation Organization.

Pricing and Currency

To charge for repair services, a service provider can use standard pricing method using Price Lists to determine the fixed repair price. Variable pricing method can also be used, which permits the depot to charge the customer for the actual material, labor, and other expenses incurred during the repair. When exchanging or replacing items, a service provider typically calculates the price of the exchange as 60% of the new item price, and possession of the customer's broken item.

In Oracle Depot Repair, a Repair Order supports a single currency. The default currency is based on the default contract. If no default contract is selected, the default Price List determines the currency. If neither defaults are set, the currency selection is based on the Price List manually selected in the Details tab. After a charge line is created, you cannot change the currency of the Repair Order in the Details tab, or select another default contract that has a Price List of a different currency. To change the currency of a Repair Order, all the charge lines, including the Logistics lines, have to be deleted.

The Repair Order currency drives the list of Price Lists that you can use for estimate charge lines. You cannot select a Price List with a currency that is different from the Repair Order currency.

Estimate Lines from Diagnostics

If you have Service Codes marked as applicable in the Diagnostics tab, and these Service Codes are associated with Bills, Routings, and Task Template Groups, then you can copy the following into the Repair Estimate tab:

When you add in lines for WIP mode repairs through Service Codes, then, typically:

When you add in lines for Task mode repairs through Service Codes, then, typically:

Estimate Cost Analysis

While preparing an estimate, you can also perform estimate cost analysis. Estimate cost analysis lets you compare your estimated margins and profitability based on estimated costs and estimated charges. The only supported costing method is standard costing. The estimate cost analysis is always an aggregate of all estimated costs and charges for the Repair Order.

Materials, labor, and expenses comprise the totals for charges or costs. Taxes and other fees are not included in cost analysis.

Costing of items differs in WIP and Task mode.

To enable estimate cost analysis, the following conditions must apply:

Estimate Approval

On the Details tab for a Repair Order, you can check or uncheck the Estimate Approval Required field. If the check box is set, you must get customer approval for the estimate, and record this as a status change in the repair estimate.

The topics in this section include the following:

Create a Repair Estimate

The following procedures describe how to prepare a repair charges estimate for the customer.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating the estimate. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to estimate charges.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Select the Repair Estimate tab in the Depot Repair Workbench.

  4. Optionally enter the Status, Date, Lead Time, and UOM field values.

    For field descriptions, see the topic Repair Estimate Tab.

  5. Click Save Estimate to save the estimate header record.

  6. You can enter estimate details in one or more of the following ways:

    • Manually, by entering individual charge line details in the multi-record table area.

      For field descriptions, see the topic Repair Estimate Tab.

    • If you have previously selected and activated Service Codes in the Diagnostics tab, then you can click Add Lines from Diagnostics.

      This adds the charge lines associated with the active Service Codes in the Diagnostics tab, that is, the Service Codes marked as applicable.

      You can also add Task Template charge lines associated with Solutions if the following conditions are true:

      1. The profile option CSD: Use Tasks from Knowledge Base Solutions is set to Yes.

      2. At least one Solution in the Solutions area of the Diagnostics tab is marked as Useful, and the corresponding Solution in Oracle Knowledge Management has one or more Task Templates among its Related Objects.

      When these conditions are true and you click Add Lines from Diagnostics, you retrieve the associated Task Template charge lines into the Repair Estimate tab.

      After you have clicked Add Lines from Diagnostics, the added lines appear in the Repair Estimate tab, and an information window appears which records any errors and information about the lines added.

      If the lines that you expect to be added do not appear, you should check a variety of factors associated with your Repair Order and the data that you are trying to add in. See Checks for Adding Estimate Lines from Diagnostics.

      For more information, see the topic Activate and Deactivate Service Codes in the Service Codes Area.

      Note: After you have added the lines associated with the active Service Codes, the Service Code rows from which you derived the estimate lines are disabled in the Service Codes area of the Diagnostics tab.

  7. After entering a charge line, click Save Estimate to record the charge line.

    The application populates the Unit Price and Est Charge fields in the table. The Summary of Estimated Charges region is also populated. This region is updated as you add (or delete) charge lines.

  8. Optionally, click Costs to see an estimate cost analysis.

    the picture is described in the document text

  9. The Estimated Costs versus Estimated Charges window opens and shows the estimated Cost, the estimated Charge, the estimated Profit (Charge less Cost), and the estimated Profit Margin% by separate Material, Labor, Expense, and Total lines.

    Click Close to exit the Estimated Costs versus Estimated Charges window.

  10. Click Line Details to display the Estimate Charge Details window.

    Enter the detailed charge line values in the table fields.

    For field descriptions, see the topic About Estimate Charge Line Details Window.

  11. To allow provisioning for overriding the entered charges later, select the Override Charges check box.

    This is enabled if the profile option CSD: Allow Charge Override for Estimates is set to Yes.

    The Override Charges check box lets you override repair charges, in the Estimated Charge field, after you have saved it. Discounts associated with the contract are not applied if you manually change the Estimated Charge.

    the picture is described in the document text

  12. Click Save to record the changes.

  13. Click Close to close the Estimate Charge Details window, and return to the Repair Estimate tab.

    The Totals fields in the lower part of the Repair Estimate tab show charge line totals.

  14. To delete a charge line, select the relevant charge line on the Repair Estimate tab, and click the Delete icon on the toolbar.

Comments

  1. You cannot add or delete charge lines in the Estimate Charge Details worksheet. You can add or delete charge lines only in the Repair Estimate tab.

  2. If you have added estimate lines derived from a Service Code, using Add Lines from Diagnostics, then you cannot add the lines again from the same Service Code.

Checks for Adding Estimate Lines from Diagnostics

You should ensure that the following conditions are true before you add lines from the Diagnostics tab. Failure to satisfy all the conditions results in rows not being imported as estimate lines.

(A) General Checks

The following checks apply to all lines:

(B) WIP-Specific Checks

The following checks apply to WIP lines:

(C) Task-Specific Checks

The following checks apply to task lines derived through Service Codes and, under profile control, directly from Task Templates related to Oracle Knowledge Management Solutions.

(D) Tasks-from-Solutions Checks

In addition to the Task-Specific checks, the following additional checks apply to task lines derived directly from Oracle Knowledge Management Solutions:

Revise a Repair Estimate

Certain repairs can require service providers to revise repair estimates many times. The service agent should verify existing warranties or contracts while quoting and revising estimates.

Note: If you manually override the Estimated Charge, which you are allowed to do if the profile option CSD: Allow Charge Override for Estimates is set to Yes, then discounts associated with the contract are not applied.

Note: Net Discount will always be the Extended Price minus the Estimated Charge, not the contract discount.

The following procedures describe how to revise the estimated charges for an item under repair.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

A repair charges estimate must exist for the broken item.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to revise the estimate.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Select the Repair Estimate tab in the Depot Repair Workbench.

    The existing charge lines appear in the multi-record area.

  4. Click Line Details.

    The Estimate Charge Line Details window opens.

  5. Make the necessary changes to the charge line field values.

    For more information, see Estimate Repair Charges.

  6. Click Save to record the revised charges.

  7. Click Close to close the Estimate Charge Line Details window and return to the Repair Estimate tab.

    The charge lines and totals on the Repair Estimate tab reflect the revision made to the estimate.

  8. To change the repair estimate status, choose an appropriate value from the list of values in the Status field.

  9. Click Save Estimate to record the changes.

Obtain Customer Approval for a Repair Estimate

If estimate approval is required for a repair estimate, then, after creating the repair charges estimate, the service agent seeks the customer's approval of the estimate.

Upon customer's approval, the depot receives the defective parts in repair subinventory. If the customer rejects the estimate, the Repair Order can be closed, or put on hold as appropriate.

Repair Order estimates can be New, Drafted, Bid, Accepted, Rejected, or Cancelled. These statuses indicate whether to start a repair process. Typically, a repair estimate must be approved prior to the start of the WIP Repair Job.

The following procedures describe how to record customer approval for a repair estimate.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

A Repair Order record with an approved estimate must exist. Also, you must have revised the original estimate as appropriate.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order that you want to revise.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

    The Details tab of the Depot Repair Workbench displays the total charges for the repair in the Charges area.

  3. Make changes to the original estimate charge lines as required.

    For detailed instructions, see Revise a Repair Estimate.

  4. Discuss the revised charges with the customer.

  5. In the Repair Estimate tab, update the estimate Status to Estimate Accepted or Estimate Rejected.

  6. Click the Save icon on the toolbar to save the updated status.

    The Repair Order is revised with the new charges and customer approval information.

  7. On the Details tab, create or consult notes as required.

    For detailed instructions, see Create and Maintain Notes.

  8. Click Update RO Status.

    In the Update Repair Order Status window, you can update the Repair Order status.

    For details, see Update the Repair Order Status.

  9. Optionally, from the top menu, click Tools > Freeze Estimate to freeze the estimate.

    After the estimate is frozen, you cannot change the estimate.

Receive a General Item

The term "general item" indicates an item that is not being refurbished.

Depot technicians can receive hand carried (walk-in) items for repair, or receive serviceable items against RMAs. Oracle Depot Repair provides flexible options when receiving and shipping items from and to customers and vendors.

Before receiving an item the system allows you to receive a serial number different from the one originally entered in the repair order. In case of a mismatch or discrepancy the system allows the receipt of the discrepant serial number and logs an activity to track the discrepancy.

Inspection

You can also inspect items during the receiving process, which allows for more accurate repair estimates as a result of inspection. Inspection of items is possible only if the routing on the RMA order is either Standard Receipt or Inspection Required.

The procedure for receiving an item with inspection is more extensive than the procedure for receiving an item without inspection

The following is an overview of the procedure for receiving an item without inspection:

The following is an overview of the procedure for receiving an item with inspection:

The following procedures describe how to receive a general item (except for internal order refurbishment items - for details of those procedures, see Receive an Item for Refurbishment).

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to receiving the general item. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to receive the general item.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Select the Logistics tab in the Depot Repair Workbench.

    If the RMA (Return) line was not created and booked automatically for the Repair Order, then create an RMA order manually.

    For detailed instructions, see Create and Book a Return Line Manually.

  4. Click Receive to open the Find Expected Receipts window.

  5. In the Customer tab in the Find Expected Receipts window, enter the RMA Number, and click Find.

    If the RMA is found, the application displays the Receipt Header and Receipts windows.

  6. Confirm the Received By field of the Receipt Header window, that is, the person receiving the RMA.

  7. Confirm the Receipt Date, and click the Save icon on the toolbar to obtain the system-generated Receipt Number.

  8. Close the Receipt Header window.

    If you want to receive an item without inspection, continue at step 9.

    If you want to receive an item with inspection, continue at step 16.

    Receiving an Item Without Inspection

    Note: For Direct Delivery Routings, you must receive an item without inspection. Inspection is optional if your routing is Standard Delivery or Inspection Required.

    However, for Inspection Required Routings, Oracle recommends that you perform the steps starting at step 16.

  9. In the Receipts window, in the Lines tab, select the check box located beside the Qty field to confirm quantity.

  10. For the Destination Type, select Inventory.

  11. Scroll the horizontal bar to reveal the Subinventory field, and select a Subinventory location in this field from the list of values.

    If the general item is a serialized item, the Lot-Serial button on the Receipts window is enabled.

    1. Click Lot-Serial to display the Serial Number window.

    2. Enter the received Serial Number, and click OK.

      You can manually enter a Serial Number even if the number does not appear in the list of values

  12. Click the Save icon on the toolbar.

  13. Close the Receipts window to return to the Depot Repair Workbench.

  14. In the Logistics tab, click Refresh Logistics.

    The status of the RMA (Return) line changes to Received.

  15. Optionally, you can see item reception details in the Activity window. From the top menu, select Data > Activity to open up the Activity window.

    This completes the procedures for receiving an item without inspection.

    Receiving an Item With Inspection

    Note: Note: For Inspection Required Routings, Oracle recommends that you perform the inspection steps that follow.

  16. In the Receipts window, in the Lines tab, select the check box located beside the Qty field to confirm quantity.

  17. For the Destination Type, select Receiving.

  18. Select a Location.

  19. Click the Save icon on the toolbar.

  20. Close the Receipts window.

  21. Back in the Logistics tab of the Depot Repair Workbench, click Inspect/Move.

  22. In the Customer tab in the Find Receiving Transactions window, enter the RMA Number, and click Find.

    The Receiving Transactions window appears.

  23. If there is more than one line, select the lien you want to inspect.

  24. Click Inspect.

  25. In the Inspection Details window, select the Status (values are either Accept or Reject).

  26. Click OK.

    This closes the Inspection Details window.

    The Destination Type of the item shows as Inspect.

  27. Click the Save icon on the toolbar.

  28. Close the Receipt Transactions window.

  29. Back in the Logistics tab of the Depot Repair Workbench, click Inspect/Move.

  30. In the Customer tab in the Find Receiving Transactions window, enter the RMA Number, and click Find.

    The Receiving Transactions window appears, with the Destination Type of the item showing as Inventory.

  31. Scroll the horizontal bar to reveal the Subinventory field, and select a Subinventory location in this field from the list of values.

  32. If the general item is a serialized item, the Lot-Serial button on the Receiving Transactions window is enabled.

    1. Click Lot-Serial to display the Serial Number window.

    2. Enter the received Serial Number, and click OK.

      You can manually enter a Serial Number even if the number does not appear in the list of values.

  33. Click the Save icon on the toolbar.

  34. Close the Receiving Transactions window to return to the Depot Repair Workbench.

  35. In the Logistics tab, click Refresh Logistics.

    The status of the RMA (Return) line changes to Received.

  36. Optionally, you can see item reception details in the Activity window. From the top menu, select Data > Activity to open up the Activity window.

    This completes the procedures for receiving an item with inspection.

    Note: You can enable the functionality of updating the Repair Status automatically once an item is received successfully. This is done by setting the profile option, CSD: Enable Auto Update of Repair Order Status upon Receiving, to Yes, and the profile option, CSD: Default Repair Order Status After Receiving, will hold the value for the new status.

    Use caution in setting the profile option, CSD: Default Repair Order Status After Receiving, to Yes as only one status can be chosen irrespective of the item or repair type used.

Ship Additional Items

On the Logistics tab, Oracle Depot Repair verifies that the item quantity on the Repair Order matches the RMA quantity on Logistics tab. This implies that it is not possible to ship additional items or quantities of items against the same Repair Order. To ship additional items or quantities of items, you must create a new Repair Order with the additional item or quantity.

Auto-Receive an Item

When you receive an item into a subinventory, you generally have to perform a number of operations in several different windows (for example, find a receipt, edit one or more receipt fields).

Under certain conditions, you can receive an item directly from the Logistics tab, without having to navigate through extra windows. The operation of receiving an item directly from the Logistics tab is called auto-receive.

The conditions under which you can auto-receive an item are as follows:

When all these conditions apply, and you click the Receive button on the Logistics tab, an alert message appears that informs you that the item is eligible for auto-receive.

If you accept the option to auto-receive the item, the auto-receive operation is performed.

Note: After the successful completion of the auto-receive operation, the Status of the RMA (Return) line is Booked. After you click Refresh Logistics, the Status changes to Received.

Receive an Item for an Internal Order Refurbishment

When a Repair Order has been created in the Planner's Desktop of Spares Management, or an equivalent external agency, and the item or items are to be sent to an Oracle Depot Repair depot for processing, this type of repair is called an internal order refurbishment.

Note: This is not the same as an internal party refurbishment, where the items to be refurbished belong to an internal party. For more information, see Create and Process an Internal Party Refurbishment.

If you do not select a subinventory for the item, the subinventory is derived from the picking rule defined in the profile option CSD: Default Pick Release Rule for Sales Orders.

In Oracle Depot Repair, the Repair Order for each item or item instance to be refurbished contains two transactions, with action types Move In and Move Out. This section describes the Move In transaction.

The Move In transaction has two components:

  1. First, the shipment stage, where the item is shipped from a source organization, such as Spares Management.

  2. Then, the receiving stage, where the item is received into a depot subinventory.

In the shipment stage, if you do not select a subinventory for the item, the subinventory is derived from the picking rule defined in the profile option CSD: Default Pick Release Rule for Sales Orders.

The shipment stage includes a Pick Release process, and then either a manual Ship process or an automatic Ship Confirm process. When both Pick Release and Ship Confirm processes can be performed automatically, that is, without any manual Serial Number entry required, you can select whether to perform both processes separately one after the other, or in sequence automatically.

Inspection

During the receiving stage, you can also inspect the items to be refurbished, which allows for more accurate repair estimates as a result of inspection. Inspection of items is possible only if the routing on the requisition order is either Standard Receipt or Inspection Required.

The procedure for receiving an item with inspection is more extensive than the procedure for receiving an item without inspection.

The following is an overview of the procedure for receiving an item without inspection:

The following is an overview of the procedure for receiving an item with inspection:

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

The Service Request and the associated refurbishment Repair Order or orders must have been created in the Planner's Desktop of the Spares Management module of Oracle Field Service.

Note: It is possible to create demand for refurbishment using a module other than Oracle Field Service and to pass this demand to Oracle Depot Repair.

Note: The module must be able to create Internal Requisitions and associate them to Internal Sales Orders. However, Oracle recommends using the out-of-the-box integration to Oracle Field Service.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to receive the item for refurbishment.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

  3. Click the Logistics tab.

  4. Click any field of the Move In line to make that line current.

    The Status of the Move In line should be Booked.

    Shipping the Item to be Refurbished from Spares Management

    Note: The following description assumes that you select the automatic Pick Release option when processing the Move In line.

    Note: Even if you select Ship Confirm as your first choice for processing the Move In line, the application automatically processes the Pick Release stage first, then the Ship Confirm stage.

    Pick Release

  5. Click the Process Trans check box for the Move In line.

  6. Click the Automate order processing steps through check box.

  7. Select the Pick Release radio button.

  8. Click Process.

    The Status of the Move In line generally changes to Released.

    However, for a serialized item that has Serial Control which is either Predefined or At Receipt, the resulting Status depends on whether you are performing the Pick Release processing for the first time or the second time.

    1. The first time, you must enter a Serial Number, navigating through the Find Move Order Lines window that appears automatically, to the Transact Move Orders window.

      For details of the Find Move Order Lines window and the Transact Move Orders window, see the Oracle Inventory User's Guide.

      When you return from the Transact Move Orders window, the Status of the Move In line remains as Booked.

    2. The second time you perform the Pick Release process (steps 5 through 8), you do not have to enter any further data, and the Status changes to Released.

      To see the Serial Number that you entered during the first-time Pick Release processing in the (Source) Serial Num field on the Logistics tab, click Refresh Logistics, after you complete the second-time Pick Release processing.

  9. Optionally, from the top menu, select Data > Activity to see the details of the item shipment in the Activity window.

    If there has been a mismatch between the Serial Number in the Move In line and the Serial Number you entered in the Transact Move Orders window, an alert message line appears in the Activity window, recording the two Serial Numbers. You must explicitly select Data > Activity to display the alert message.

    This completes the Pick Release processing.

    Manual Ship or Ship Confirm

  10. For the case of a serialized refurbished item, whose Serial Control is At Sales Order Issue, the Ship Confirm button is disabled. In this situation, click Ship and enter the item's Serial Number in Oracle Shipping Execution windows. For details of these windows, see the Oracle Shipping Execution User's Guide.

    When you return to the Logistics tab, click Refresh Logistics. The Status changes to Shipped.

    This completes the manual ship processing for these special Move In lines.

    Continue at step 16.

  11. For all other cases, click the Process Trans check box for the Move In line.

  12. Click the Automate order processing steps through check box.

  13. Select the Ship Confirm radio button.

  14. Click Process.

    When processing the Ship Confirm stage, you should wait until the concurrent program Interface Trip Stop has completed successfully before you click Refresh Logistics, to see the changed value of the Status.

    You can monitor the progress of the program by selecting Requests from the View menu on the toolbar, and selecting appropriate search criteria.

  15. Click Refresh Logistics.

    The purpose of this is to update the Status on the Move In line, so that it reflects in Oracle Depot Repair the results of the procedures executed in other Oracle applications when you clicked Process.

    After the background concurrent process Interface Trip Stop has completed successfully, the Status changes to Shipped.

    Starting the Process of Receiving the Item to be Refurbished

  16. Click any field of the Move In line to make that line current.

  17. Click Receive to open the Find Expected Receipts window.

  18. In the Supplier and Internal tab in the Find Expected Receipts window, enter the Requisition from the Requisition Num of the Move In line, and click Find.

    If the requisition is found, the application displays the Receipt Header and Receipts windows.

  19. Confirm the Received By field of the Receipt Header window, that is, the person receiving the requisition.

  20. Confirm the Receipt Date, and click the Save icon on the toolbar to obtain the system-generated Receipt Number.

  21. Close the Receipt Header window.

    If you want to receive an item without inspection, continue at step 22.

    If you want to receive an item with inspection, continue at step 29.

    Receiving the Item to be Refurbished Without Inspection

  22. In the Receipts window, in the Lines tab, select the check box located beside the Qty field to confirm quantity.

  23. In the Destination Type field, select Inventory.

  24. Scroll the horizontal bar to reveal the Subinventory field, and select a Subinventory location in this field from the list of values.

    If the item is a serialized item, the Lot-Serial button on the Receipts window is enabled.

    1. Click Lot-Serial to display the Serial Number window.

    2. Enter the received Serial Number, and click OK.

      You can manually enter a serial number even if the number does not appear in the list of values.

  25. Click the Save icon on the toolbar to save the receipt record.

  26. Close the Receipts window to return to the Depot Repair Workbench.

  27. Click Refresh Logistics.

    The Status of the Move In line changes to Received.

  28. Optionally, from the top menu, select Data > Activity to see the details of the reception of the item in the Activity window.

    This completes the process of receiving an item without inspection.

    Receiving the Item to be Refurbished With Inspection

  29. In the Receipts window, in the Lines tab, select the check box located beside the Qty field to confirm quantity.

  30. For the Destination Type, select Receiving.

  31. Select a Location.

  32. Click the Save icon on the toolbar.

  33. Close the Receipts window.

  34. Back in the Logistics tab of the Depot Repair Workbench, click Inspect/Move.

  35. In the Supplier and Internal tab in the Find Expected Receipts window, enter the Requisition from the Requisition Num of the Move In line, and click Find.

    The Receiving Transactions window appears.

  36. Click Inspect.

  37. In the Inspection Details window, select the Status (values are either Accept or Reject).

  38. Click OK.

    This closes the Inspection Details window.

    The Destination Type of the item shows as Inspect.

  39. Click the Save icon on the toolbar.

  40. Close the Receipt Transactions window.

  41. Back in the Logistics tab of the Depot Repair Workbench, click Inspect/Move.

  42. In the Supplier and Internal tab in the Find Expected Receipts window, enter the Requisition from the Requisition Num of the Move In line, and click Find.

    The Receiving Transactions window appears, with the Destination Type of the item showing as Inventory.

  43. Scroll the horizontal bar to reveal the Subinventory field, and select a Subinventory location in this field from the list of values.

  44. If the item is a serialized item, the Lot-Serial button on the Receiving Transactions window is enabled.

    1. Click Lot-Serial to display the Serial Number window.

    2. Enter the received Serial Number, and click OK.

      You can manually enter a Serial Number even if the number does not appear in the list of values.

  45. Click the Save icon on the toolbar.

  46. Close the Receiving Transactions window to return to the Depot Repair Workbench.

  47. In the Logistics tab, click Refresh Logistics.

    The status of the Move In line changes to Received.

  48. Optionally, from the top menu, select Data > Activity to see the details of the reception of the item in the Activity window.

    This completes the procedures for receiving an item with inspection.

Split a Repair Order

Often as a result of an inspection carried out during the receiving of an item, you may decide to repair some but not all of the defective units.

Under certain conditions (see the Prerequisites that follow in this section), Oracle Depot Repair allows you to split a Repair Order, but not necessarily just because of an inspection.

Repair Type Change Options

One of the prerequisite conditions is that the original Repair Type must have a Repair Type Ref value of either Standard or Repair and Return. You can change the Repair Type on the new Repair Order, so long as the final Repair Type also has a Repair Type Ref value of either Standard or Repair and Return.

Note: The explicit condition specifies the Repair Type Ref attribute of the allowable Repair Types. The seeded Repair Types Standard and Return and Repair have the same Repair Type Ref values as their Repair Type names.

For details of setting up Repair Types, see the Oracle Depot Repair Implementation Guide.

Splitting Options

When you choose to split a Repair Order, you have the following options:

When you choose to split the Repair Order into two separate Repair Orders, you can also decide whether to copy attachments from the original Repair Order to the new Repair Order.

When you split into multiple lines, each with a quantity of 1, all attachments on the original Repair Order, if any exist, are automatically copied to each new Repair Order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

The Repair Order Item must be serialized.

The item must not be Installed Base trackable.

All quantities must be received.

For WIP mode, all jobs must be completed, that is, no partial completions are allowed.

The Repair Order status must be Open.

The Repair Type Ref of the Repair Type must be Standard or Repair and Return.

No Ship lines have been interfaced to Oracle Order Management.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order that you want to split.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

  3. From the top menu, select Tools > Split Repair Order.

    The Split Repair Order window appears.

    Your splitting options are indicated by the two radio buttons:

    • Split into 2 lines

    • Split into lines with quantity of 1

    Split into 2 Lines

    Under the Split into 2 lines option, there is a table showing the following fields:

    • Original Repair Order Quantity (enabled)

    • Original Repair Order Repair Type

    • New Repair Order Quantity

    • New Repair Order Repair Type (enabled)

    There is also a check box under the Split into 2 lines option, enabling you to copy attachments from the original Repair Order to the new Repair Order.

    If there are no attachments to the original Repair Order, the check box is disabled.

    Split into Lines with a Quantity of 1

    Under the Split into lines with a quantity of 1 option, a message indicates that any attachments to the original order will be automatically copied to the new order.

  4. Select one of the radio buttons.

  5. If you selected Split into lines with a quantity of 1, you have no further choices. Continue at step 7.

  6. If you selected Split into 2 lines:

    1. Enter the Original Repair Order Quantity, that is, the new quantity that you wish to have on the original Repair Order after splitting.

      The New Repair Order Quantity is automatically calculated after you enter the Original Repair Order Quantity.

    2. Select the New Repair Order Repair Type.

      You can only select a Repair Type whose Repair Type Ref was set up as Standard or Repair and Return.

    3. Optionally, select the check box Copy attachments from original Repair Order to new Repair Order.

  7. Click OK.

Manage the Repair Process

Oracle Depot Repair lets service organizations manage repair by using either Oracle WIP or Task Manager, a module in Oracle Common Application Components.

WIP mode is recommended for use when the repair jobs require series of sequential steps, and materials management. Task mode is recommended for use when the repairs require minimal steps that are not necessarily completed in sequence.

The WIP or Task modes are associated to the Repair Types during implementation. 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.

The topics in this section include the following:

Create and Process WIP Repair Jobs

Note: Oracle Depot Repair provides E-records and E-signature (ERES) functionality in WIP mode via Oracle WIP.

The topics in this section include the following:

Create a WIP Repair Job for a Single Repair Order

The Shop Floor Technician can create a non-standard WIP Repair Job from the Depot Repair Workbench. You select the organization for the WIP Repair Job, and the items for the WIP Repair Job must be defined in that organization.

Multiple jobs can be created for each Repair Order. You can release WIP Repair Jobs on to the shop floor. You must provide the WIP Accounting Class through which costs are posted to Oracle General Ledger.

Depot agents can view WIP Discrete Jobs window in a read-only mode to verify the status and additional details of the WIP Repair Job.

The following procedures describe how to create a WIP Repair Job for a single Repair Order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating the WIP Repair Job for the Repair Orders. For more information, see Oracle Depot Repair Business Scenarios.

Note: You may need to create a Repair Job without an RMA in case of remanufacture or refurbishment on items that your organization already owns, or if your organization took ownership or possession of an item through a field service agent rather than against an RMA.

Note: Oracle Depot Repair provides you with a profile option, CSD: Allow Creating WIP Job Without RMA, which enables you to create a WIP Repair Job without an RMA. Refer to Oracle Depot Repair Implementation Guide for details.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to create a WIP Repair Job.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. In the Depot Repair Workbench, select the Repair Jobs tab, and click Create Job.

    The Submit Repair Jobs window opens. The job you create will be in the organization set up when you perform the Change Organization operation. If you have not performed the Change Organization operation, the organization is taken from the profile option CSD: Default Repair Inventory Org.

    the picture is described in the document text

  4. If the WIP Repair Job item is different from the Repair Order Item, select the relevant WIP item from the list of values in the Item field.

  5. Select the Released Job Status from the list of values.

    Note: The default value for this field is taken from the profile option CSD: Default Repair Job Status.

    Note: You may submit a WIP Repair Job with a Job Status of Unreleased. You will be able to change the status later using Oracle Work In Process transactions.

  6. Select an Accounting Class from the list of values, for example, Rework.

  7. Enter the number of items that you want to submit in the (Quantity) Submit field.

  8. The system date defaults as Start Date. Select the Complete Date for the WIP Repair Job.

  9. In the Service Codes, Bills and Routings area, select one of the three radio buttons:

    • Use Service Codes

    • Select Bills and Routings

    • Do not Specify Bills and Routings

    If you select Use Service Codes, the following occurs:

    • Bills and Routings associated with the active Service Codes, that is, the Service Codes marked as applicable, in the Diagnostics tab are attached to the WIP Repair Job.

    • Read-only summary information about the Service Codes, Bills, and Routings is displayed in the Service Codes, Bills and Routings area.

    • After you have added the Bills and Routings associated with the active Service Codes, the Service Code rows from which you derived the Bills and Routings are disabled in the Service Codes area of the Diagnostics tab.

      Note: After you have added the Bills and Routings associated with the active Service Codes, the Service Code rows from which you derived the Bills and Routings are disabled in the Service Codes area of the Diagnostics tab.

    If you select Select Bills and Routings, enter appropriate Bill and Routing data in the Bill and Routing sections.

    If you select Do not Specify Bills and Routings, you are choosing not to provide any Bill and Routing information for the WIP Repair Job.

  10. Click Submit Job to submit the job in a released status to WIP.

  11. To make sure that the program completes successfully, monitor the requests by choosing View > Requests.

  12. Close Repair Jobs window to return to the Depot Repair Workbench.

  13. Click Refresh Job.

    The new job appears on the Repair Jobs tab.

  14. To view the job, select the job record on the Repair Jobs tab, and click View Job.

    To process the WIP Repair Job, see Process a WIP Repair Job for a Single Repair Order.

See Also

Create a WIP Repair Job Across Multiple Repair Orders.

Multiple WIP Repair Jobs and Partial Quantities for a Single Repair Order

Oracle Depot Repair lets you create multiple WIP Repair Jobs for a single Repair Order and supports the creation of multiple WIP Repair Jobs with partial quantities per RMA.

WIP Repair Job Item Same As Repair Order Item

If the item selected for the WIP Repair Job is the same as the one in the Repair Order, then for each WIP Repair Job submission, the submit quantity cannot be greater than the quantity received. A submit quantity less than the quantity received implies that you can create multiple WIP Repair Jobs against a single Repair Order, with each WIP Repair Job handling part of the RMA quantity.

For example, consider that the item on the Repair Order is A, and the quantity of item A is 5. When you submit WIP Repair Jobs for item A, the maximum number of units of A that can be submitted in a WIP Repair Job is 5, and the minimum is 1.

WIP Repair Job Item Different From Repair Order Item

If the item selected for a WIP Repair Job is different from the one on the Repair Order, the submit quantity restriction does not apply, and you can submit the WIP Repair Job for any quantity. The application validates this quantity with the quantity received in the Repair Order line. In this case, the quantity to be submitted to WIP must be at least 1.

Process a WIP Repair Job for a Single Repair Order

The following procedures describe how to process a repair WIP Repair Job that contains a single Repair Order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to processing the WIP Repair Job for the Repair Order. For more information, see Oracle Depot Repair Business Scenarios.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to process the WIP Repair Job.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. In the Depot Repair Workbench, select the Repair Jobs tab.

  4. Click Material Txn to display the Material Transaction window.

  5. Issue the item and the material required to process the WIP Repair Job.

    For details, see Issuing and Returning Specific Components in the Oracle Work In Process User's Guide.

  6. Complete the item repair using a recommended repair procedure.

  7. When the repair is complete, click Complete Job in the Repair Jobs tab.

    The Completion Transaction Find window opens.

    Enter the completion details, such as quantity completed and completion subinventory, for the WIP Repair Job.

    For details, see Completing and Returning Assemblies in the Oracle Work In Process User's Guide.

  8. In the Repair Jobs tab of the Depot Repair Workbench, click Refresh Job to update the Repair Order activity information.

Post-Processing

  1. To see information about the WIP Repair Job activity, from the top menu, select Data > Activity.

    For more information, see View Activities Related to a Repair Order.

  2. After you have processed a WIP Repair Job, if invoicing is required, you must move the data to Repair Actuals.

    For more information, see Record Billing Data in Repair Actuals.

Create a WIP Repair Job Across Multiple Repair Orders

Oracle Depot Repair lets service organizations automatically create a single WIP Repair Job against multiple Repair Orders for identical items.

You search for WIP Repair Jobs issued for items that have already been received into the repair organization. You can perform the search against the Item Code, or attributes that pertain to the linked Service Request.

You perform this operation in two stages:

  1. First, you search for the Repair Orders, in the Find Repair Orders for Job Submission window.

  2. Then, you determine how many units to submit for repair for each Repair Order, and submit the WIP Repair Job, in the Submit Repair Jobs for Repair Orders window.

The Find Repair Orders for Job Submission window incorporates a multi-select feature to let you select any or all Repair Order lines that appear in the search results.

In the Submit Repair Jobs for Repair Orders window, you can specify the quantity of the item to submit for each Repair Order, and optionally, select Bills and Routings.

The following procedures describe how to create a WIP Repair Job for multiple Repair Orders relating to the same item.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating the WIP Repair Job for the Repair Orders. For more information, see Oracle Depot Repair Business Scenarios.

Navigation

Depot Repair > Submit Repair Jobs...Organizations window

Steps

  1. Select the relevant Repair Organization from the list of values.

    Find Repair Orders for Job Submission Window

    The Find Repair Orders for Job Submission window opens.

    For field descriptions, see Find Repair Orders for Job Submission Window.

  2. Enter one or more search criteria by using one or more of the following fields:

    • (Service Request) Request Num

    • (Service Request) Customer

    • (Service Request) Account

    • (Service Request) Severity or Urgency

    • (Repair Order) Item

    • (Repair Order) Promise Date or Date Range

    • (Repair Order) Create Date or Date Range

      This is a sample list of the search parameters.

      For descriptions of all the fields, see Find Repair Orders for Job Submission Window.

  3. Click Find to start the query.

    The search results appear in the Results area of the Find Repair Orders for Job Submission window.

  4. Select the relevant Repair Order or combination of Repair Orders.

    • To select all the rows, click Select All.

    • To select multiple, non-contiguous rows from among the search results, press and hold the Control key, and click each row.

    • To select a complete range of rows from among the search results, click the first row of the range, then press and hold the Shift key, and click the final row of the range.

    • To deselect all rows, click Deselect All.

  5. After you select the relevant rows, click OK.

    Submit Repair Jobs for Repair Orders Window

    The Submit Repair Jobs for Repair Orders window opens.

    The selected rows populate the Repair Order Information area in the window, and the Total Quantity Submitted for repair automatically appears.

    For field descriptions, see Submit Repair Jobs Window.

  6. In the Job Status field, select Released from the list of values.

    You may submit a WIP Repair Job with a Job Status of Unreleased. You will be able to change the status later using Oracle Work In Process transactions.

  7. Select an Accounting Class from the list of values, for example, Rework.

    Your organization determined these values during implementation of Oracle Depot Repair.

  8. The system date defaults as Start Date. Select the WIP Complete Date.

  9. In any line of the Repair Order Details tab, you can optionally change the number of units to submit in the (Quantity) Submit field.

  10. You can optionally click the Bills and Routings tab, and select one of the radio buttons:

    • Select Bills and Routings

    • Do not Specify Bills and Routings

    If you choose Select Bills and Routings, then you must select at least one Bill or Routing.

  11. Click Submit Jobs to submit the job in a released status to WIP.

  12. To verify that the program completes successfully, monitor the requests by choosing View > Requests from the toolbar.

  13. Close the Submit Repair Jobs for Repair Orders window and return to the Navigator.

    Refresh Job for Each Repair Order

  14. Retrieve these Repair Orders by using the Find Repair Orders window.

  15. In the Depot Repair Workbench, select each Repair Order, and click Refresh Job. The new job appears on the Repair Jobs tab.

    For more information, see Update Repair Orders Concurrently.

Comments

After you have created and submitted a WIP Repair Job for identical items across multiple Repair Orders, you can process the WIP Repair Job.

For more information, see Process a WIP Repair Job Across Multiple Repair Orders.

See Also

Create a WIP Repair Job for a Single Repair Order

Process a WIP Repair Job Across Multiple Repair Orders

The following procedures describe how to process a WIP Repair Job containing multiple Repair Orders. Processing a WIP Repair Job across multiple Repair Orders involves the following areas:

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to processing the WIP Repair Job for the Repair Orders. For more information, see Oracle Depot Repair Business Scenarios.

Navigation

WIP > Discrete > Discrete Jobs...Find Discrete Jobs window

Steps

Find Discrete Jobs Window

  1. Enter the WIP Repair Job Number, and click the Find button.

    The Discrete Jobs window opens.

  2. Confirm that the Repair Job is in Released status.

  3. Click the Routing Tab and select the Completion Subinventory from the list of values.

  4. If the item is under Locator control, enter the Locator value.

  5. Save your work.

  6. Close the Discrete Jobs window to return to the navigator.

Material Transactions Window

  1. Navigate to WIP > Material Transactions > WIP Material Transactions.

    The Material Transactions window opens.

  2. Select the Specific Component option if the material to be issued is not defined as a material requirement for the job.

  3. Enter the WIP Job Number, and click the Continue button.

    The WIP Component Issue window opens.

  4. In the Components Issue window, enter the Items to be repaired.

    If you did not select the Specific Component option, and the material you want to issue is not defined as a material requirement for the job, you might not be able to issue the item.

  5. Select the present Subinventory location of the items.

  6. If the items are Locator controlled, enter Locator information.

  7. Enter the Quantity to be repaired.

  8. If the items are under Serial or Lot control, enter Serial or Lot information.

  9. Enter the material needed to assist the repair.

  10. Click Done.

    This issues the material and closes the window.

  11. Close the Material Transactions window to return to the Navigator.

Completion Transactions Window

  1. After completing the repair, navigate to WIP > Material Transactions > Completion Transactions.

    The Completion Transactions window opens.

  2. Enter the WIP Repair Job Number, and click the Continue button.

  3. Enter the completed quantity and the completion subinventory if you did not enter this information previously.

  4. If the items are Locator, Serial, or Lot controlled, and you entered such information previously, enter these values.

  5. Click Done to perform the completion transaction and return to the Depot Repair Navigator window.

WIP Jobs and Schedules Window

  1. Navigate to WIP > Discrete > WIP Value Summary.

    The WIP Jobs and Schedules window opens.

  2. Enter the WIP Repair Job Number, and click Find.

    The WIP Jobs and Schedules window opens.

  3. Enter the From Period and To Period information.

  4. Click Value Summary.

    The WIP Value Summary window opens.

Create and Process Repair Tasks

Note: In Task mode, Oracle Depot Repair provides E-records and E-signature (ERES) functionality via the Debrief screen for each Task.

Tasks consist of work assignments that detail the actions required of company personnel.

The Repair Tasks tab in the Depot Repair Workbench provides a solution for repair establishments that use simple, standard business processes without requirements for WIP-based processes. The Tasks module is accessed (Repair Tasks tab is enabled or disabled) depending on the Repair Type selected in the Depot Repair Workbench Details tab.

In the Repair Tasks tab, you can create, update, assign, and view previous tasks assigned to a Repair Order. Tasks assigned previously appear in the table in the upper part of the tab, while details of the selected task appear in the fields below it. You can create a task directly from the Repair Tasks tab by entering all the relevant information, or by using a template.

Using Quality Collection Plans with Tasks

You can assign Oracle Quality collection plans to tasks, through setups to be performed in Oracle Quality.

For general information about collection plans, see the Oracle Quality User's Guide.

Tip: When creating the collection plan, copy the elements from the Template Depot Repair Task Plan as a starting point.

To link a collection plan with a task, you must select Depot Repair Task Transaction as a Quality Collection Transaction. You may choose to make this transaction mandatory: this will require Oracle Depot Repair users to enter quality results before they close the task.

You can also set up one or more collection triggers to specify conditions under which the collection plan is to be assigned to tasks.

In Oracle Depot Repair, you must enter the quality results for mandatory plans. For details, see Enter and Update Task Details.

Repair Task Debrief

On the Repair Tasks tab, you can click the Debrief button to display Material, Labor, and Expense forms. You can debrief a job with actual Material, Labor, and Expense repair charges.

For repair jobs that you have managed using Tasks, the Debrief provides the actual charges incurred during the repair that would be invoiced to a customer. If both estimate and debrief exists for a repair that you have managed using Tasks, the customer is invoiced based on charges that appear in the debrief.

The topics in this section include the following:

Create a Repair Task Manually

The following procedures describe how to create a repair task manually.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating the repair tasks for the Repair Order. For more information, see Oracle Depot Repair Business Scenarios.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to create repair tasks.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. In the Depot Repair Workbench, click the Repair Tasks tab.

    If tasks have already been defined for the Repair Order, the table lists the tasks. If more than one task appears, selecting a different task displays the corresponding detail in the lower fields on the tab.

    the picture is described in the document text

  4. Enter the task information in the required fields by selecting from the list of values.

    For field descriptions, see The Repair Tasks Tab.

  5. Enter the values in the Assignee and Owner fields (or change them) by selecting from the list of values.

    You can also change the Assignee field values from the Assignment Manager. To access the Assignment Manager, click the Assignment Manager button next to the fields. For additional information about the Assignment Manager, see Oracle Common Application Components User's Guide.

  6. Choose the Planned Start and End Dates.

  7. Click the Save icon to save the task record.

    A system-generated Task Number populates the Num field.

  8. Optionally, you can click Add Tasks from Diagnostics. This adds tasks from task template groups associated with the service codes marked as applicable in the Diagnostics tab.

  9. To manually launch workflow, select the task from the table, and click Launch Workflow.

    Based on the task, the workflow runs. The designated resources are reserved, and the workflow notifies the task owner of task creation through email.

    Note: The Launch Workflow button is available only if resources have been assigned to the selected task.

  10. To add or update task details, click More.

    The Task Details window opens.

    For more information, see Enter and Update Task Details.

Create a Repair Task Using a Task Template

The following procedures describe how to create a repair task using a Task Template.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating the repair tasks for the Repair Order. For more information, see Oracle Depot Repair Business Scenarios..

Before you create a task from a Task Template, a template design must exist.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to create repair tasks.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. In the Depot Repair Workbench, select the Repair Tasks tab.

    If tasks have already been defined for the Repair Order, the table lists the tasks. If more than one task appears, selecting a different task displays the corresponding detail in the lower fields on the tab.

  4. On the Repair Tasks tab, click Use Template.

    The Create Tasks from Template Group window opens.

  5. In the Template Group field, select the Template Group based on the task which is to be created.

    Values in the Source Document, Source Name, Owner Type and Owner fields are default values. You can change these values.

    the picture is described in the document text

  6. Click Create Tasks.

    The Repair Tasks tab opens and displays a new task line that shows a system-generated Task Number in the Num field.

  7. To manually launch workflow, click Launch Workflow.

    Based on the task, the workflow runs. The designated resources are reserved, and the workflow notifies the task owner of task creation through email.

    Note: The Launch Workflow button is available only if a resource has been assigned to a selected task.

  8. Click More to open the Task Details window to enter details such as resource assignments, dependencies, references, and contacts.

    For more information, see Enter and Update Task Details.

Enter and Update Task Details

After a task record is created, you can update task information and task details. The following procedures describe how to update task information and to add task details.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

Task records that you want to update or add details to must exist in the database.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to update task details.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

  3. The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  4. In the Depot Repair Workbench, select the Repair Tasks tab.

    If tasks have already been defined for the Repair Order, the table lists the tasks. If more than one task appears, selecting a different task displays the corresponding detail in the lower section of the window.

  5. To update task information, make the necessary changes to the field values, and click the Save icon.

    For field descriptions, see the Repair Tasks Tab topic.

    Entering Quality Results

  6. If your task has any mandatory collection plans associated with it, you will not be able to set the task Status to Closed unless you first enter quality results for the task. To do this, either click the Enter Quality Results icon in the toolbar, or select Tools > Enter Quality Results; then enter the information required.

    Specifying Task Details

  7. To specify task details, select the task for which you want to update details, and click More.

    The Task Details window opens. The Task Details window comprises the following tabs:

    • Resources: Assign personnel information to a task. This tab defines resource requirements, assignments, and scheduling information.

    • Dependencies: Determine the order of tasks. Oracle Depot Repair, however, does not enforce task dependencies.

    • References: Link the task to different documents or tasks with pertinent background information.

    • Dates: Identify more dates in addition to the planned dates, the scheduled dates, and the actual dates. You can track task progress by entering dates after task milestones such as task creation, resource reservation, or task completion.

    • Contacts: Create and manage multiple contacts assigned to a task. Contact information is obtained from customer information. To enter this information, you must identify a customer in the main task window.

    • Recurrences: Schedule tasks so as to occur automatically. Examples of intervals include daily, weekly, monthly, or yearly occurrences. To schedule recurring tasks, you must either specify a start date and the number of tasks to create, or the end date. The task dates are populated as the planned start and end dates.

    • Others: Identify additional information about the task, and select different configurations for each task. Setting flags customizes each task according to business needs.

    • Audit: Track each update to a task. The tab documents and dates the history of task change, and provides a trail from the original task through to the current task status.

      the picture is described in the document text

  8. Enter the field values on the different tabs as required.

    For detailed instructions, refer to the Task Manager topic in Oracle Common Application Components User's Guide.

  9. Click OK to save your work and return to the Repair Tasks tab in the Depot Repair Workbench.

Prepare the Repair Tasks Debrief

On the Repair Tasks tab, you can click the Debrief button to display the Debrief Report, with Material, Labor, and Expense tabs. You can debrief a job with actual Material, Labor, and Expense repair charges.

For repair jobs that you have managed using Tasks, the Debrief provides the actual charges incurred during the repair that would be invoiced to a customer. If both estimate and debrief exists for a repair that you have managed using Tasks, the customer is invoiced based on charges that appear in the debrief.

Note: The Debrief Report form does not let you apply contracts per charge line. If you are using the Debrief Report form to generate charges, the system automatically applies the contract at the Service Request level to the charge line.

The following procedures describe how to create the Debrief. This procedure is applicable only to repair processes that you have managed by using Tasks.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating the repair tasks for the Repair Order. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to update task details.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant record from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. In the Depot Repair Workbench, select the Repair Tasks tab.

    If tasks have already been defined for the Repair Order, the table lists the tasks. If more than one task appears, selecting a different task displays the corresponding detail in the lower section of the window.

  4. Select the task for which you want to create the report, and click Debrief.

    The Debrief Report window shows the selected task details populated in the fields at the upper part of the window. The lower half of the window comprises the Material, Expense, and Labor tabs.

    the picture is described in the document text

  5. Select the Material tab to enter required details of material transactions of the repair task.

  6. Select the Expense tab to enter required details of other expenses of the repair task.

  7. Select the Labor tab to enter required labor transaction details of the repair task.

  8. Click Update to save the details.

    For detailed instructions and discussion on buttons and check boxes accessible from the Debrief Report window, refer to Oracle Field Service User Guide.

View Activities Related to a Repair Order

The Activity window displays a real-time view of events and activities that surround a Repair Order. This permits the depot agents and planners to know the exact status of each Repair Order line.

The following procedures describe how to view the activities that have elapsed at the depot in association with a Repair Order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

None

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to view the elapsed depot activities.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. From the top menu, select Data > Activity.

    The Activity window displays the quantity received, quantity submitted to WIP, quantity completed in WIP, and quantity shipped. It also displays individual events, event dates, quantity, and other details. For detailed field descriptions, see Activity Tab.

    Note: The fields, Quantity Submitted to WIP and Quantity Completed in WIP, appear only for repairs processed in WIP mode. However, when quantities are submitted in WIP mode across Repair Orders, these Quantity fields do not contain valid values.

    the picture is described in the document text

  4. If the Activity window does not display the updated information that you expect, you may need to run the appropriate information update program:

    • Click the Logistics tab, then click Refresh Logistics.

    • Click the Repair Jobs tab, then click Refresh Job.

    Note: The programs triggered by the Refresh Logistics and Refresh Job buttons update the activity information only for the Repair Order currently selected in the Depot Repair Workbench.

    For more information, see Update Repair Orders Concurrently.

Update Repair Orders Concurrently

The following concurrent programs update all the open Repair Orders at the same time:

To access these programs, from the Depot Repair Navigator, navigate to:

Depot Repair > Other > Run Requests.

The Submit a New Request window opens. In the Submit a New Request window, you can choose to submit a single request. When you submit a single request, the Submit Request window opens. In the Name field, select the program that you want to run. Choices include Depot Repair Receipt Update, Depot Repair Job (WIP) Update, or Depot Repair Shipment Update. You also specify to update quantity received, quantity submitted to or completed in WIP, and quantity shipped respectively, for all open Repair Orders.

In the remaining fields, you can schedule the program to run at times or intervals of your choice, choose whom to notify on completion, and choose whether to print or save the reports. For more information, refer to the online help available from these windows.

The Depot Repair Receipt Update concurrent program picks only the receiving lines that are delivered to a subinventory. This is to support business scenarios that involve quantity correction of goods received at the dock.

For example, during the inspection of goods received at a dock, you can correct or return some quantity of the goods delivered. This could be because not as many items were sent as the customer said they would, or the customer returned more than expected, such as, goods that were too damaged to qualify for a refund, or goods that your organization did not sell. Items are not considered as received until they pass the inspection, and are delivered to a subinventory. Only at this point does the Depot Repair Receipt Update concurrent program stamp the received quantity and show the change in the received quantity.

Send and View Workflow-Based Messages

At a high level, the Workflow-based Messaging functionality provides the ability to send a workflow notification message, and have that message link to the Repair Order selected in the Depot Repair Workbench at the time the message was sent. Messages can be of various types, from information-only to those that request actions or approvals from others. When the message recipient responds to the message linked to the specified Repair Order, that response is captured in the Repair Order's message history. A message can be sent to one or many recipients, and can be sent to group lists. Messages sent to multiple recipients can only be informational messages.

In Oracle Depot Repair, messages are tied to a Repair Order, and are sent from the Repair Orders form.

the picture is described in the document text

For more information on message types, sending, receiving, and viewing messages, and user procedures, see the Oracle TeleService User Guide and Oracle TeleService Implementation Guide.

Create a Ship Line Manually

The following procedures describe how to create a Ship line manually.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to creating a ship line manually. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to create the Ship line manually.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Select the Logistics tab in the Depot Repair Workbench.

  4. In the Action Type field, select Ship.

  5. Select the fields for the Ship line.

    The main fields that you must select are Action Code, Service Activity, and Price List.

    Note also the Add to Order field. Oracle Depot Repair lets you place all Return (RMA) and Ship lines on the same order.

    By default, all Return (RMA) and Ship lines appear on the next-highest Order Number created when the lines are transferred to Order Management.

    You can also select the specific order for the Return (RMA) or Ship line by selecting the Order Number in the Add to Order field before interfacing the specified line to Order Management.

    For field descriptions, see Logistics Tab.

  6. Click the Save icon on the toolbar to save the record.

    The Ship line is created with the Status of Entered.

Ship a General Item

The term "general item" indicates an item that is not being refurbished.

Depending on the business scenario, an item being shipped might be repaired. Shipments can include repaired, replacement, loaner, or exchange items.

If you do not select a subinventory for the item, the subinventory is derived from the picking rule defined in the profile option CSD: Default Pick Release Rule for Sales Orders.

The Ship line that corresponds to the shipment goes through several stages of processing, and at each stage the Status is updated. The Status values that it passes through are Entered, Submitted, Booked, Released, and Shipped.

You may go through each processing stage one stage at a time, or process several stages in sequence automatically.

Enter Order (Submit to Oracle Order Management)

After a Ship line is created, its first Status is Entered.

When you submit the line to Oracle Order Management, and it is successfully interfaced, it gets an Order Number returned from Oracle Order Management, and its Status changes to Submitted.

After the Ship line has been interfaced with Oracle Order Management, it cannot be deleted.

Book Order

In this stage, the line must be booked in Oracle Order Management. The main effect of this in Oracle Depot Repair is that the Status of the line changes to Booked.

Pick Release

During the Pick Release processing, the application reserves the exact items to ship.

The Status of the Ship line at the end of the Pick Release stage changes to Released.

[For serialized items whose Serial Control is either Predefined or At Receipt, you are required to perform the Pick Release processing twice:

Ship Confirm

At the end of the Ship Confirm stage, the item has been shipped and the Status of the line changes to Shipped.

Automatic Processing of a Ship Line

The standard way to process a Ship line for a general item is as follows:

  1. Decide the stage you want to reach.

  2. Click the Automate Order Processing steps through check box.

  3. Select the radio button which corresponds to the stage you want to reach:

    • Enter Order

    • Book Order

    • Pick Release

    • Ship Confirm

  4. Click Process.

    Note: You can optionally process the last stage, that is, with the Ship line in the Released status, by clicking the Ship button, and then entering data in Oracle Shipping Execution windows. For details of these windows, see the Oracle Shipping Execution User's Guide.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to shipping the general item. For more information, see Oracle Depot Repair Business Scenarios.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for the item that you want to ship.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant order from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Select the Logistics tab of the Depot Repair Workbench.

  4. Click any field of the Ship line to make that line current.

  5. Click the Process Trans check box.

  6. Select the Automate Order Processing Steps Through check box.

  7. Select one of the following radio buttons:

    • Enter Order

    • Book Order

    • Pick Release

    • Ship Confirm

  8. For the special case where you have chosen Ship Confirm, for a serialized item whose Serial Control is At Sales Order Issue, enter the Source Serial Number.

  9. Click Process.

    Depending on how many stages you have chosen to perform, a variety of procedures are performed.

    In all cases, acknowledge the message in any message window that appears.

    Enter Order

    If, at step 7, you chose Enter Order, the Status changes to Submitted.

    Book Order

    If, at step 7, you chose Book Order, the Status changes to Booked.

    Pick Release

    If, at step 7, you chose Pick Release, the Status generally changes to Released.

    Pick Release for Items with Serial Control Predefined or At Receipt

    For a serialized item that has Serial Control which is either Predefined or At Receipt, the resulting Status depends on whether you are performing the Pick Release processing for the first time or the second time.

    1. The first time, you must enter a Serial Number, navigating through the Find Move Order Lines window that appears automatically, to the Transact Move Orders window.

      For details of the Find Move Order Lines window and the Transact Move Orders window, see the Oracle Inventory User's Guide.

      When you return from the Transact Move Orders window, the Status of the Ship line remains as Booked.

      Repeat the Pick Release processing (steps 5 through 9).

    2. The second time you perform the Pick Release process, you do not have to enter any further data, and the Status changes to Released.

  10. To see the Serial Number that you entered during the first-time Pick Release processing in the (Source) Serial Num field on the Logistics tab, click Refresh Logistics, after you complete the second-time Pick Release process.

  11. To check if there has been a mismatch between the Serial Number in the Ship line and the Serial Number you entered in the Transact Move Orders window, select Data > Activity to display the Activity window. If a mismatch occurred, an alert message in the Activity window records the two Serial Numbers.

    When the Status of the Ship line is Released, the Pick Release stage is complete.

    Ship Confirm

    When processing the Ship Confirm stage, you should wait until the concurrent program Interface Trip Stop has completed successfully before you click Refresh Logistics, to see the changed value of the Status.

  12. You can monitor the progress of the program by selecting Requests from the View menu on the toolbar, and selecting appropriate search criteria.

  13. Click Refresh Logistics.

    The purpose of this is to update the Status on the Ship line, so that it reflects in Oracle Depot Repair the results of the procedures executed in other Oracle applications when you clicked Process.

    If, at step 7, you chose Ship Confirm, and the background concurrent process Interface Trip Stop completes successfully, the Status changes to Shipped.

  14. When the transaction is completed, you can optionally view the shipping information in the Activity window, by selecting Data > Activity from the top menu.

Ship a Refurbished Item

In Oracle Depot Repair, after a refurbished item has been received from the Spares Management warehouse and repaired, it is ready to be shipped back to Spares Management.

Note: Spares Management is a module of Oracle Field Service.

If you do not select a subinventory for the item, the subinventory is derived from the picking rule defined in the profile option CSD: Default Pick Release Rule for Sales Orders.

You must process the item through the Pick Release and a Ship stages. These stages are similar to the Pick Release and Ship Confirm stages for shipping a general item.

Where both options are allowed (that is, where the equivalent radio buttons are both enabled), you can either perform the two stages one at a time, or process both stages in sequence automatically.

For serialized items whose Serial Control is either Predefined or At Receipt, you are required to perform the Pick Release processing twice, as for general items. For more information, see Ship a General Item.

Manual Ship Processing for Items with Serial Control At Sales Order Issue

The only difference in the processing of a refurbishment item and a general item occurs in the final, Ship stage, and then only for the case of a serialized refurbished item, whose Serial Control is At Sales Order Issue.

To ship this type of item, you must use the manual method of clicking Ship and entering the Serial Number using Oracle Shipping Execution windows; you cannot use the automatic method of choosing Ship Confirm and clicking Process.

Note: You must also use the manual method for partial shipments.

The following procedures describe the Move Out transaction, that processes the shipment of the refurbished item back to Spares Management.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

The Service Request and the associated refurbishment Repair Order or orders must have been created in the Spares Management module of Oracle Field Service.

The item must have been received and repaired.

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for which you want to ship the refurbished item.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

  3. Click the Logistics tab.

  4. Click any field of the Move Out line to make that line current.

    The Status of the Move Out line should be Booked.

    Note: The following description assumes that you select the automatic Pick Release option when processing the Move Out line.

    Even if you select Ship Confirm as your first choice for processing the Move Out line, the application automatically processes the Pick Release stage first, then the Ship Confirm stage.

    Pick Release

  5. Click the Process Trans check box for the Move Out line.

  6. Click the Automate order processing steps through check box.

  7. Select the Pick Release radio button.

  8. Click Process.

    The Status of the Move Out line generally changes to Released.

    Pick Release for Items with Serial Control Predefined or At Receipt

    For a serialized item that has Serial Control which is either Predefined or At Receipt, the resulting Status depends on whether you are performing the Pick Release processing for the first time or the second time.

    1. The first time, you must enter a Serial Number, navigating through the Find Move Order Lines window that appears automatically, to the Transact Move Orders window.

      For details of the Find Move Order Lines window and the Transact Move Orders window, see the Oracle Inventory User's Guide.

      When you return from the Transact Move Orders window, the Status of the Move Out line remains as Booked.

    2. The second time you perform the Pick Release process (steps 5 through 8), you do not have to enter any further data, and the Status changes to Released.

  9. To see the Serial Number that you entered during the first-time Pick Release processing in the (Source) Serial Num field on the Logistics tab, click Refresh Logistics, after you complete the second-time Pick Release process.

  10. To check if there has been a mismatch between the Serial Number in the Move Out line and the Serial Number you entered in the Transact Move Orders window, select Data > Activity to display the Activity window. If a mismatch occurred, an alert message in the Activity window records the two Serial Numbers.

    When the Status of the Move Out line is Released, the Pick Release stage is complete.

    Manual Ship or Ship Confirm

  11. For the case of a serialized refurbished item, whose Serial Control is At Sales Order Issue, or for partial shipments, the Ship Confirm button is disabled. In these situations, click Ship and enter the item's Serial Number in Oracle Shipping Execution windows. For details of these windows, see the Oracle Shipping Execution User's Guide.

    When you return to the Logistics tab, click Refresh Logistics. The Status changes to Shipped.

    This completes the manual ship processing for these special Move Out lines.

  12. For all other cases, click the Process Trans check box for the Move Out line.

  13. Click the Automate order processing steps through check box.

  14. Select the Ship Confirm radio button.

  15. Click Process.

    When processing the Ship Confirm stage, you should wait until the concurrent program Interface Trip Stop has completed successfully before you click Refresh Logistics, to see the changed value of the Status.

    You can monitor the progress of the program by selecting Requests from the View menu on the toolbar, and selecting appropriate search criteria.

  16. Click Refresh Logistics.

    The purpose of this is to update the Status on the Move Out line, so that it reflects in Oracle Depot Repair the results of the procedures executed in other Oracle applications when you clicked Process.

    After the background concurrent process Interface Trip Stop has completed successfully, the Status changes to Shipped.

  17. Optionally, from the top menu, select Data > Activity to see the details of the Move Out transaction in the Activity window.

Record Billing Data in Repair Actuals

When you have completed the repair and have determined the final billing for materials, labor, and expenses that you want to bill your customer, you need to put the billing amounts in Repair Actuals. Sources of billing amounts in Repair Actuals can include the estimate, WIP Summary, Task Debrief, or manual entries.

Note: For WIP mode jobs, although it is not prohibited to create actuals from both WIP and Estimate sources, generally you will copy in from either WIP or Estimate sources.

Similarly, for Task mode jobs, although you can copy in lines from both Task and Estimate sources, generally you will copy in from either Task or Estimate sources.

When you record the billing entries in Repair Actuals, the system creates charge lines in the Repair Actuals area. In turn, the system can transfer the billing data to other modules for invoicing.

Note: The Debrief Report form does not let you apply contracts per charge line. If you are using Debrief Report form to generate charges, the system automatically applies the contract at the Service Request level to the charge line.

Topics that guide you through adding data into your Repair Actuals tab include:

See Also

the picture is described in the document text

Add WIP Summary to Repair Actuals

If your Repair Order is in WIP mode, you can add the WIP Summary as a source for your Repair Actuals.

When you add from the WIP Summary to your Repair Actuals, the system adds all material, labor, and expense lines from the WIP Summary into the Repair Actuals.

Generally, when adding in lines from WIP Repair Jobs:

After you add WIP Summary lines into the Repair Actuals, you can:

Upon importing the WIP Summary lines to the Repair Actuals, the system creates charge lines for each line.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must be processing a Repair Order.

Navigation

Repair Actuals tab

Steps

  1. In the Source field, click the right-hand end of the field, then click the ellipsis (...) button.

    A window opens and displays the possible sources from which you can add data to Repair Actuals.

    For a WIP mode repair, the options are WIP and Estimate.

    For a Task mode repair, the options are Task and Estimate.

  2. Select a Source and click OK.

  3. Click Add.

    The system automatically populates rows and fields on the Repair Actuals tab from the source that you selected. An information window appears which records any errors and information about the lines added

    The Source field shows the Source Name. You should review each line on the Repair Actuals tab to:

    • Determine if any lines require overrides.

    • Determine if any lines should be at no charge.

  4. (Not available for lines imported from Task Debrief.)

    If the profile option CSD: Allow Charge Override for Actuals is set to Yes, you override an amount on a line, as follows:

    1. Select Override Charge.

    2. In the Charge column, enter a new amount.

  5. (Not available for lines imported from Task Debrief.)

    To change a line to No Charge, select the No Charge check box.

  6. Click Save to record the changes.

View Line Details

On the Repair Actuals tab, you can view additional information about a charge line's details. Additional details include costing and charge information. You can access a charge line's details by selecting a charge line and clicking the Line Details button. An expanded window shows the detailed information.

See Also

Add Task Debrief to Repair Actuals

If your Repair Order is in Task mode, you can import the Task Debrief as a source for your Repair Actuals.

When you import from the Task Debrief to your Repair Actuals, the system imports all material, labor, and expense lines from the Task Debrief into the Repair Actuals.

Note: The Debrief Report form does not let you apply contracts per charge line. If you are using the Debrief Report form to generate charges, the system automatically applies the contract at the Service Request level to the charge line.

After you import Task Debrief lines into the Repair Actuals, you can:

Upon importing the Task Debrief lines to the Repair Actuals, the system creates charge lines for each line.

Note: You cannot update lines whose Source is Task.

For procedural information on how to add Task Debrief data to the Repair Actuals, see the Steps in the topic Add WIP Summary to Repair Actuals.

See Also

Add Estimate to Repair Actuals

If your repair includes an estimate, you can use the Repair Estimate as a source for your Repair Actuals.

When you import from the Repair Estimate to your Repair Actuals, the system imports all lines from the Repair Estimate into the Repair Actuals.

After you import Repair Estimate lines into the Repair Actuals, you can:

Upon importing the Repair Estimate lines to the Repair Actuals, the system creates a charge line for each estimate line.

Note: After you have imported any estimate lines into Repair Actuals, any changes made to those source estimate lines are not automatically forwarded to the corresponding Repair Actuals lines. To take advantage of the new estimate changes, you must delete the corresponding Repair Actuals lines, and then re-import the changed source estimate lines.

For procedural information on how to add Estimate data to the Repair Actuals, see the Steps in the topic Add WIP Summary to Repair Actuals.

See Also

Create Manual Charges in Repair Actuals

In addition to adding billing data from other sources--such as the WIP Summary, Task Debrief, or Estimate--you can:

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must be processing a Repair Order.

Navigation

Repair Actuals tab

Steps

  1. To manually create a new charge line on the Repair Actuals line, select the new row on which you are adding a charge line.

    The Source Type field automatically indicates Manual.

  2. Enter or select the Billing Category, Item, Price List, Qty, UOM, Pricing Attributes fields, and optionally, the PO Num field.

  3. Optionally, complete the Contract Number field.

  4. If the profile option CSD: Allow Charge Override for Actuals is set to Yes, you override an amount on one line, as follows:

    1. Select Override Charge.

    2. In the Charge column, enter a new amount.

      Note: If you manually override the charge, then discounts associated with the contract are not applied.

  5. To change a line to No Charge, select the No Charge check box.

  6. Click Save to record the changes.

See Also

Book Repair Actuals

After you have recorded your billing data in Repair Actuals, from one or more sources, and possibly entered charge lines manually in Repair Actuals, you can book selected charge lines.

The following procedures describe how to book selected Repair Actuals charge lines.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must be processing a Repair Order.

You must have charge lines in Repair Actuals, either manually entered or added in from a Source of Estimate, WIP, or Task.

Navigation

Repair Actuals tab

Steps

  1. Select either individual charge lines or click Select All if you want to book all the charge lines in the Repair Actuals tab.

  2. Click Book Selected.

Comments

For lines whose Source is Task, the items used in the Debrief Report decrement inventory only after the Field Service concurrent program CSF: Update Debrief Lines is submitted. This concurrent program updates the Quantity On Hand (QOH) in the inventory.

Invoice a Customer

Note: Tax, Shipping, and Freight charges are not calculated within Oracle Depot Repair, but are calculated in Order Management when orders transfer to Order Management. For this reason, the charge totals in the estimate lines and lines from Task Debrief may be different from the value charged on the invoice.

The following procedures describe how to invoice a customer.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to invoicing the customer. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Accounts Receivable

Steps

  1. Invoice the customer by using normal business procedures.

    For more information, see the Oracle Receivables User Guide.

Close a Repair Order

The following tasks describe how to close a Repair Order.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to closing the Repair Order. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Repair Order for the item that you want to ship.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. Confirm that the quantity on the Repair Order is complete.

  4. Consult or create notes if necessary.

    For detailed instructions, see Create and Maintain Notes.

  5. In the Details tab of the Depot Repair Workbench, click Update Status.

    The Update Status window opens. In the Update Status window, you can update the Repair Order status. The Repair Order can remain Open, be on Hold, or Closed.

  6. Select Close by selecting the option button, and click OK to close the Repair Order line.

    You can select a Reason Code from the list of values, and enter additional details supporting the status update.

  7. Click the Save icon on the toolbar to save the record.

Close a Service Request

The following procedures describe how to close a Service Request.

Module

Oracle Applications Navigator

Responsibility

Depot Repair Super User

Prerequisites

You must complete all steps in the relevant business scenario prior to closing the Service Request. For more information, see Oracle Depot Repair Business Scenarios..

Navigation

Depot Repair > Repair Orders

Steps

  1. Retrieve the Service Request that you want to close.

    For more information, see Find Service Requests and Repair Orders.

  2. Select the relevant result from the Results area of the Find Repair Orders window, and click OK.

    The Depot Repair Workbench shows the selected Service Request and Repair Order details.

  3. In the Service Request Information area of the Depot Repair Workbench, change the status of the Service Request to Closed by selecting from the list of values.

  4. Enter the date closed.

  5. If required, create notes stating the reason for the Service Request closure.

    For detailed instructions, see Create and Maintain Notes.

  6. Click the Save icon to close the Service Request.

  7. Alternatively, if the Request Num hyperlink is enabled, you can click the Request Num link to launch the Update Service Request page. You can use this page to change the service request status and update the SR Resolution Code.

Create and Process an Internal Party Refurbishment

In Oracle Depot Repair, you can create and process items that need to be refurbished that belong to an internal party. In these cases, the items to be refurbished do not move from an external location, such as a Spares Management warehouse, they remain in the internal party location.

Note: Spares Management is a module of Oracle Field Service.

Create the Service Request

You must first create a Service Request, and explicitly choose an internal party for your customer.

An internal party is defined as a customer set up in at least one of the following ways:

For more information on setting up internal parties, see the Oracle Depot Repair Implementation Guide.

Create the Repair Order

When you create the Repair Order, you must select a Repair Type that has been set up with a Repair Type Ref of Refurbishment, and whose Internal Order check box has not been set.

For more information on setting up Repair Types, see the Oracle Depot Repair Implementation Guide.

Process the Repair Order

After the Repair Order has been created, the Logistics, Estimates, and Repair Actuals tabs are disabled, as is the tools option menu Tools > Coverage.

The main operations that you perform on internal party refurbishment items are repairs to be carried out through WIP Repair Jobs or Tasks.

The only special considerations that apply to the internal party items to be refurbished are as follows:

View Repair Orders in Oracle iSupport

Oracle Depot Repair customers can now search for their Repair Orders through a self-service user interface in Oracle iSupport.

Oracle iSupport authenticates the user and displays only the Repair Orders for accounts which the user is authorized to view. For each Repair Order, summary and detail information, including Repair Order status, can be displayed.

The procedure to view Repair Orders in Oracle iSupport is as follows:

  1. Login to Oracle iSupport.

  2. Click the Accounts tab.

  3. Select the Repair Orders menu item.

    The Repair Order Summary page appears.

  4. Click the Repair Order Number hyperlink for a Repair Order.

    The Repair Order Details page appears.

You can also use the Saved Searches function in Oracle iSupport to assist subsequent searches.

For more information, see the Oracle iSupport User Guide.

Third Party Flows

The repair centers interface with the third parties to execute many of customer's service requirements. They track the movement of products, work and financial obligation between all the parties involved in executing a repair.

The functions for managing repair operations across multiple parties consists of the following:

Third Party Logistics for Repairs

Broken products, repaired products, and exchanges are moved and tracked between service organization, customer, and third parties. The Depot Repair application supports the following models of third party repair logistics:

Setting Up Repair and Return with Third Party

  1. Navigate to the Repair Types page. The Repair Type Summary region displays the existing repair types in the system.

  2. To create a new repair type, click the New icon on the menu option.

  3. Enter the required information in the following fields:

    • Repair Type: Enter the name of the repair type.

    • Description: Enter description of the repair type.

    • Business Process: Select Depot Repair from the list of values.

    • Repair Mode: The default value is Work In Process. The other available options are Task Mode and None.

      Note: You must select WIP Mode to use the Repair Technician Portal.

    • Repair Type Ref: It defaults if you select a seeded Repair Type.

    • Third Party Ship and RMA: Select the Ship and RMA Service Activity Billing Types from the list of values.

      The list of values displays the Service Activity Billing Types, which are setup in the Charges setup windows. These values must be associated with a third party RMA line and third party Ship line to indicate what OM line types to use, what operating unit to associate them with, what contract entitlements apply, and so on.

      You must set up the Service Activity Billing Types under the Pre-Repair and Post-Repair columns in order to have a RMA line under pre-repair, and a Ship line under post-repair.

    • Third Party checkbox: Selecting the check box creates a third party ship and RMA line at time of repair order creation if a Service Activity Billing Type is selected in the Third Party RMA and ship columns. If a Service Activity Billing Type is selected for the Ship column but not the RMA column, only a ship line will be created at time of repair order creation. Likewise, if a Service Activity Billing Type is selected for the RMA column but not the Ship column, only an RMA line will be created at time of repair order creation.

      If the third party flag is not checked, no Third party lines will be auto-created, even if service activities are entered in the Third Party Ship and RMA fields.

      Note: A repair type having third party lines can also have regular lines, provided the Service Activity Billing Types are set up for them in their respective columns.

  4. Click Save.

  5. In the Repair Type Details region, enter Service Activities in the Material, Labor, and Expense tabs. This is optional and is required only when a customer creates Estimate or Actual lines. They are not needed if no billing is done in Estimates or Actuals.

  6. Select Automatically enter and book RMA, and Automatically ship through options for third party shipments. This is optional and depends on the business process of the repair center. You can use any of the following options: auto-create, auto-enter, or auto-book. Automatically process through option enables the ship lines to create a charge line, or enter an unbooked line in OM, or book a line in OM.

    This is optional and depends on the business process of the repair center.

    the picture is described in the document text

  7. Click Save. Close the Repair Type form.

  8. Navigate to the Repair Orders page.

  9. Create a new Service Request.

  10. Create a new Repair Order.

    the picture is described in the document text

  11. Click Save.

  12. Navigate to the Logistics tab.

    You can view four lines in the Action Type column. Return and Ship lines for regular repair and return and Ship Third Party and Return Third Party lines for third party (RMA and Ship).

  13. Receive the item in inventory. For more information, see: Auto-Receive an Item.

  14. Select the row to ship an item to the third party and select the Process Trans check box.

  15. The third party account field should have defaulted at time of ship line creation if the disposition rules were set up correctly. You cannot change the account if the line is set to automatically book. Click the Ship radio button.

  16. Click the Process button. Item is shipped to the third party for repair and the status of the line shows Shipped.

  17. Receive the item from third party using third party RMA line. Item is received from third party and the status of the line changes to Received.

  18. Ship the item back to customer through regular ship line.

Invoice Third Party

Depot Repair allows sending repair invoices to a different party from that which logged the service request. Invoices can be sent to multiple parties for a single repair order.

Updating the Invoice Third Party Flow

  1. Navigate to the Depot Workbench and query for a repair order.

  2. Click the Repair Actuals tab. The tab displays the following information:

    • The Total column reflects the total charges associated with the repair order if the Actual Lines are billed to more than one party.

      the picture is described in the document text

    • The Default Bill To Account, Party, and Address default from the information entered on the Service Request.

    • You can change the default information. Changing the Default Bill To Account, Party, and Address will not impact the already created lines. It will impact the lines created after the change.

  3. Click the Line Details button to navigate to the Actual Line Details page.

    the picture is described in the document text

    The Actual Line Details page displays the following information:

    • Bill To Account, Party and Address details for each corresponding line, default from Actuals tab.

    • You can update the Bill To Account, Party or Address fields if you choose to bill a different party, account, or address than that specified on the Service Request for a specific charge line.

Supplier Warranty Claims

Organizations performing repairs on products manufactured by other companies need a mechanism for reporting and settling warranty claims with the Original Equipment Manufacturers (OEM) or suppliers. The mechanism consists of the following:

Capturing Warranty Claim Information

  1. Navigate to the Depot Repair Workbench and query for a repair order.

  2. Click the Repair Actuals tab.

  3. Click the Line Details button to navigate to the Actual Line Details page.

  4. To capture warranty claim information, select the Warranty Claim checkbox in the Actual Line Details region.

  5. Enter the Number and Status for the warranty claim. These fields are non editable if you do not select the Warranty Claim option.

  6. Select a Replaced Item from the list of values. Replaced item shows list of items belonging to the Organization. The replaced item information is sent along with the warranty claim information.

  7. Click Save.

Execute Outside Processing

A depot repair technician can trigger the creation of a purchase order for outside processing by completing an Outside Processing (OSP) operation in the Repair Technician Module. See: WIP Implementation Guide, for more information about setting up OSP operations.

Select Repair Parts from Dynamic Repair BOM Window

Depot Repair provides a new region in the Repair Technician module to enable a technician to view any bill of materials, or alternate bill of materials. This module also enables the technician to choose a routing. The technician can check off the removed, replaced, or repaired parts. You can add the selected parts first to a repair estimate, and then create a job from the estimate.

Select Repair BOM

The Dynamic Repair BOM screen enables the technician to quickly capture the parts required for a repair. Upon completion of the inspection, the selected parts are automatically added to the repair order estimate.

  1. Navigate to the Depot Repair Workbench and query an item.

  2. Click the Repair Estimate tab on the Repair Order page.

  3. Select the Select Materials button to navigate to the Expanded BOM window.

  4. In the Search region, enter a valid BOM item in the Item field or select an item from the list of values. You can also select an Alternate BOM from the list of values.

  5. Click Go. The Select From BOM Hierarchy regions displays those items in the BOM hierarchy which have billing type as Material defined in Inventory Item Master.

  6. Select the BOM components required in the repair. These materials appear as new estimates lines on the Repair Estimates tab at completion of triage.

    the picture is described in the document text

  7. The Select Additional Items region enables you to enter an Item and corresponding quantity required for repair. Add any items which are not in the existing BOM.

  8. You can select a routing to associate with the Repair Estimate in the Select a Routing region.

    Note: You can save only a single Routing at one time, and that Routing can only be viewed on the Select Material window. You can modify the saved routing if required. The routing is used to create a job from estimate.

  9. Click the Save and Process button to commit the selection of desired components. Close the window.

  10. Click OK on the alert to trigger the refresh in the Estimate tab.

  11. The following values default for Estimate lines created from the Expanded BOM window:

    • Source Type: Repair BOM

    • Billing Category: Material

    • Contract Number: Use the contract associated to the repair order if a contract exists

    • Price list: Default the Price lists selected on the Details tab

    the picture is described in the document text

Create Job from Estimate

Once the repair estimate is created, a repair manager works with the customer to approve the estimate. After the approval of the estimate, the repair manager initiates the repair by generating a repair job from the estimate.

To create job from estimate

Print Traveler Document

Depot Repair provides an out-of-box traveler document to enable the repair technicians to scan in maximum data thereby reducing the time consumed in data entry. Traveler documents allow easy identification and disposition of items in the repair shop. Bar coded serial numbers and repair order numbers allow technicians to quickly find repair records without typing.

To print a traveler document:

  1. Navigate to the Depot Repair Workbench.

  2. Create a Repair Order or retrieve an existing repair order.

  3. Select the Print Traveler option from the Data menu.

    the picture is described in the document text

    This command prints the traveler.

Depot provides a standard traveler format, and also a barcoded traveler, both of which can be tailored to a customer's preferences using XML Publisher.

View Service Bulletins using Depot Repair Workbench

Depot Repair automatically links a service bulletin to a repair order based on customer defined service bulletin rules. A number of pre-defined bulletin types are seeded in the product. You can add any additional bulletin types to fit your business needs. You can view service bulletins from the Depot Repair Workbench.

The Depot Repair Workbench enables the repair managers, coordinators, billing clerks, and other users to view service bulletins. The Depot Repair Workbench is enhanced to allow a user to view the service bulletins associated with a repair order from the Workbench.

To view a service bulletin from the Depot Repair Workbench

  1. Navigate to the Depot Repair Workbench.

  2. Create a Repair Order. Alternatively, you can search and retrieve an existing repair order.

    The Repair Orders page opens.

  3. Click the View Service Bulletins option from the Data menu.

    the picture is described in the document text

    The Service Bulletins page opens.

  4. The Service Bulletins page displays the existing service bulletins if the Retrieve Service Bulletins concurrent program is running. Click Retrieve New Service Bulletins button to display any additional new service bulletin.

    the picture is described in the document text

  5. Select the service bulletin and click Show to display the service bulletin details.

Related Topics

Define Triggers for Service Bulletins

View Service Bulletins from the Repair Technician Module

View Read Only Workbench

Oracle Depot Repair provides the ability to launch the Depot Workbench in read-only mode. The Depot Workbench provides numerous data and functionality that is not specific to any specific user type. It provides functions to repair managers, service representatives, receiving clerks, shipping clerks, billing clerks and many more. The read-only mode allows the users to access data that they need but restricts them from performing functions outside of their purview.

To view the Depot Workbench in read-only mode, set the profile option, CSD: Read Only Workbench, to Yes.

To Access a Read-only Depot Workbench

  1. Navigate to the Depot Workbench. The Workbench launches in read-only mode. You can only view data, but not execute any functions.

  2. The read-only mode allows you to click certain buttons and view menu options. The disabled functions/buttons are:

    • Create new service request

    • Create new contact

    • Create new repair order

    • Create Note - Details Tab

    • Change Status - Details Tab

    • Counters - Details Tab

    • Configuration - Details Tab

    • Process Transaction Checkboxes - Logistics Tab

    • Process Transaction Through Checkbox - Logistics Tab

    • Process button - Logistics Tab

    • Receive - Logistics Tab

    • Ship - Logistics Tab

    • Create Job - Repair Jobs Tab

    • Create Task - Repair Tasks Tab

    • Capture Quality Plan - Repair Tasks Tab

    • Create Estimate, Estimate Line - Repair Estimates Tab

    • Create Job from Estimate - Repair Estimates Tab

    • Submit Actuals - Repair Actuals Tab

    The disabled menu items are:

    • Reserve/Un-reserve Serial Number

    • Split Repair Order