Debriefing Work Completion

Field Service technicians use the Debrief module to view their task assignment details, accept or reject assignments, update task statuses, capture travel related information, and report on material, labor time, and expenses for their individual task assignments. Data gathered is used for generating customer invoices, updating the installed base, and maintaining the service vehicle trunk stock.

Field Service managers use Debrief to capture, access, and update debrief information on behalf of Field Service technicians. For more information, see Overview: Administrator Portal Dashboard.

This chapter provides procedures for performing Debrief using the Field Service Technician Portal (Dashboard).

This chapter covers the following topics:

• Understanding Debrief Procedures
• Capturing Travel Information
• Adding a Labor Line
• Adding a Material Line
• Using Loaner Transactions
• Adding an Expense Line
• Recording Counter Readings
• Updating Task Details and Notes
• Viewing a Pro Forma Invoice
• Searching e-Record Evidence Store
• Updating Owned Asset Install Base Records
• Reverse Logistics
• Using Parts Return
• Viewing Transaction History
• Scheduling Tasks
• Creating and Scheduling Follow-Up Tasks

Understanding Debrief Procedures

A technician accesses Debrief by clicking the Debrief icon on the Field Service Technician Dashboard, or by clicking the Update Tasks icon on the dashboard and then clicking the Debrief tab.

This action brings up the Update Task page to the Debrief sub tab, where the technicians can view or create new labor, material, and expense lines.

After the required information is entered on the Debrief sub tab, the user can either click Apply to commit the record details that were just entered, or click Add Another Row to create additional lines.

After these debrief lines have been created, the user has the option to either update or delete these lines, as long as they have not been submitted to charges.

The Oracle Field Service Technician Portal enables several debrief procedures:

• Capture Travel Information

• Add a Labor Line

• Add a Material Line

• Add an Expense Line

• Record Counter Readings

• Update Task Details and Notes

• Create a Follow-Up Task

Capturing Travel Information

The Field Service Technician Portal enables capture of travel related information for technicians individual task assignments.

Profile Option - CSF: Capture Travel Information

You enable this feature by setting the CSF: Capture Travel Information profile option.

This profile can be set with one of these values:

• None

• Time

• Distance

• Time and Distance

The Update Task page, Debrief sub tab displays fields relating to the profile option value selected. For example, if the profile option is set to 'Time', then the page displays the start and end time fields, but not the distance field.

The fields rendered for capturing travel time are not mandatory. This means, for example, that even though the profile is set to 'Time', the user is not required to enter the start and end time, even though these fields display on the page.

Use this procedure to enter travel time and distance.

Steps

1. Navigate to the Field Service Technician Dashboard.

   The dashboard appears to the selected default view.

2. In the row for the task to be debriefed, click the Debrief icon.

   The Update Task page appears displaying the Debrief sub tab.

3. (Optional) In the header region of the Debrief sub tab, enter the Travel Distance, Travel Start Time, and Travel End Time.

4. Click Apply.

Adding a Labor Line

Use Debrief labor line functionality to record time spent on a task.

You can create multiple labor lines for a task assignment. Labor lines are uploaded to Charges when the CSF: Update Debrief Lines concurrent program completes successfully. The technician cannot modify labor lines after they have been submitted to Charges. Technicians can however, still add new labor lines for the task as long as the task assignment status is not 'Closed'.

For more information about Task Assignment Status, see Task Status and Task Assignment Status Flow.

Profile Option - CSF: Allow Overlapping Labor Lines

By default, a technician cannot enter overlapping actual start and end times for various assignments during a work shift. If you want to enable overlapping labor times, set the CSF: Allow Overlapping Labor Lines profile option to 'Yes'.

Note: While creating error correction debrief labor lines, the above mentioned profile option is ignored.

Use this procedure to add a debrief labor line to a task:

Steps

1. Navigate to the Field Service Technician Dashboard.

2. From the Dashboard, click the Debrief icon for the task for which you want to add debrief lines.

   The Update Task page appears displaying the Debrief sub tab.

3. Click the "+" icon to expand the labor region.

4. In the Labor region, click Add Another Row.

   This expands the Labor region, where the technician can enter information to create a labor line. Existing labor lines associated with this task assignment appear in the summary table of the labor region.

5. In a new labor line, choose a Service Activity code from the drop down list of values.

6. The schedule start and end times appear by default in the Start Time and End Time fields. The technician can modify the start and end times.

   • The start date and time must be greater than the earlier of the incident report date and time or the service request creation date and time.

   • The start date and time must be less than or equal to the system date.

7. (Optional) Override the time spent working in the Duration field.

   The end time recalculates according to the start time plus the duration time.

8. The planned effort unit of measure for the task appears by default in the UOM field. The technician can choose a different unit of measure from the list of values.

9. (Optional) Enter an item that the labor line is being logged against, if applicable.

   The Item Description appears.

10. (Optional) Enter a Reason for the labor line.

11. The schedule start date appears by default in the Service Date field. The technician can select a different date.

    • The service date and time must be greater than the earlier of the incident report date and time or the service request creation date and time.

    • The service date and time must be less than or equal to the system date.

12. To save the labor line, click Apply.

    For information on correcting labor lines, see Reviewing and Correcting Debrief information.

Adding a Material Line

Reporting of items installed and recovered is necessary to plan for the supply of service parts, to maintain the installed base, and to generate an invoice for material used. Material information is entered at the line level, and updates Oracle Inventory, Install Base, and Charges for that specific line.

You can create multiple material lines for a task assignment. The technician cannot modify material lines that have been submitted to Charges. Technicians can however, still add new material lines for the task as long as the task assignment status is not Closed.

Replacements need two material transaction lines, one for the part taken out or removed, and one for the part put back in or installed.

The Material line region of the Update Task: Debrief sub tab area is divided into two parts: Install and Return.

• The Install section is used to capture debrief lines with a line type of Order for all transactions where the item is installed at the customer site.

• The Return section is used to capture debrief lines with a line type of Return for transactions where items are removed from the customer site. If the technician has an assigned default defective sub-inventory assigned, the item appears by default in that sub-inventory field for return transactions.

Use this procedure to add a Debrief Material line:

Prerequisites

• At least one service request and task to report on exist.
• Resources have sub-inventories assigned to them.
• Setups for the Business Process and Service Activity Code are complete.

• Profile Option: CSF: Default Business Process

• Profile Option: CSF: Default Debrief Service Activity Code

• Item setups are complete:

• The Service Billable attribute is set to Material.

• The Item Transactable check box is selected.

• In the case of trackable items, the instance numbers are generated.

• Price lists are associated with the items.

Steps

1. Navigate to Field Service Technician Dashboard.

2. From the Field Service Technician Dashboard, click the Debrief icon for the task for which you want to add debrief lines.

   The Update Task page appears displaying the Debrief sub tab.

3. Click the + icon to expand the Material region.

   This action expands the Material region to display two parts: Install and Return.

Reporting Installed Material

4. Existing Material - Install lines associated with this task assignment appear in the summary table of the Material - Install section. Click Add Another Row.

   This expands the Material - Install line, where the technician can enter information to create a material line.

5. Select a Business Process.

   • The Business Process default value appears when the Service Request Type has an associated Business Process.

   • If no Business Process is associated, then the Business Process default value is set to the value of the profile option CSF: Default Business Process.

   • If no Business Process is associated, and if the profile option CSF: Default Business Process is not set, then the technician must select the Business Process from the list of values.

6. Select a Service Activity code.

   This is the activity for the material you are reporting. The item you are able to select is filtered based upon the Service Activity code and sub-inventory you select.

   • If the profile option CSF: Default Service Activity Code is set with a value that has the Line Type: Order, then that value is the default for this field.

   • If the profile option CSF: Default Service Activity Code is not set, then the technician must select the Service Activity code from the list of Service Activity codes that are associated to the Business Process selected in the previous step.

7. Select the Subinventory. The list of values for the Sub-inventory field depends on the Line Category Code defined in the Service Activity Code setup window.

   • If the Line Category Code is defined as Order the sub-inventory populates with the default usable sub-inventory. The list of values displays all usable sub-inventories.

   • If the Line Category Code is Return the sub-inventory populates with the default defective sub-inventory. If the default defective sub-inventory is not identified, then the default usable sub-inventory is populated. The list of values for the Sub-inventory field displays both usable and defective sub-inventories.

8. Select the Item number by clicking the Search for Item icon.

   When you click the Search for Item icon the Search and Select: Item page appears. Enter the item search criteria and click Go. You can search by Item, Item Description, Subinventory, or Revision. In addition to the items that are listed on the page, you will be able to view for each item the Recovered Part Disposition (if applicable), Subinventory, Revision, Onhand Qty, and Available Qty.

   Select the item by one of these methods:

   • Select the select radio button for the item and click Select.

   • Click the Quick Select icon for the item.

   The system populates the Item field in the Material section, with the one selected on the Search and Select: Item page.

   The list of Items that display depend on the Service Activity code setup:

   • If the Update IB check box is checked for the selected Service Activity Code in the IB transactions subtype, then the Item list displays both trackable and non trackable items. Otherwise, the Item list displays only non trackable items.

   • In case an item is Installed Base trackable and the Line Category Code on the Service Activity Code setup window is Order, the Parent Instance and the Recovered Instance fields are enabled.

     • The Parent Instance field displays the list of all the instances installed at the customer location.

     • Additionally, the operational status of the part or asset instances being installed into another piece of equipment (the parent) automatically inherit the operational status of the parent instance.

     • When the part or asset installed is without reference to a parent, in other words, it is a stand alone part or asset, then the technician needs the ability to enter and update its Install Base operational status. The operation status contains these values:

       • Not Used

       • Installed

       • In Service

       • Out of Service

       The operational status of the part or asset being installed is updated when the Material Debrief is posted.

   • In case of line category code Return, the Recovered Instance field is enabled.

9. The UOM, Operational Status, and Service Date fields default once you select the Item.

   • The UOM field appears by default from the selected item UOM attribute. You can select a different unit of measure from the list of values, if necessary.

   • The Service Date appears by default from the system date and time. The technician can select a Service Date from the date list of values.

     • The service date and time must be greater than the earlier of the incident report date and time or the service request creation date and time.

     • The service date and time must be less than or equal to the system date.

10. Enter the quantity for the item installed in the Quantity field.

    In the case of serialized items, Quantity is set equal to 1, and the Quantity field is disabled.

11. Enter the Serial Number, Lot, Locator, Revision, and Instance Number details depending on the item attributes.

    The list of values for these fields are validated based upon the item and sub-inventory combination.

12. (Optional) Select a Reason for the material transaction from the list of values.

Reporting Returned Material

The Material - Return section is similar to the Material - Install section. The Return section includes a Return Reason field, (in addition to the Reason field), which is required to be completed if a return is being processed.

13. In the Material section - Return, click Add Another Row.

    This expands the Material - Return line, where the technician can enter information to create a return material line.

14. Select a Business Process.

15. Select a Service Activity code.

16. Select a Subinventory. The list of values for the Sub-inventory field depends on the Line Category Code defined in the Service Activity Code setup window.

    • If the Line Category Code is defined as Order the sub-inventory populates with the default usable sub-inventory. The list of values displays all usable sub-inventories.

    • If the Line Category Code is Return the sub-inventory populates with the default defective sub-inventory. If the default defective sub-inventory is not identified, then the default usable sub-inventory is populated. The list of values for the Sub-inventory field displays both usable and defective sub-inventories.

17. Select the Item number by clicking the Search for Item icon.

    When you click the Search for Item icon the Search and Select: Item page appears. Enter the item search criteria and click Go. You can search by Item, Item Description, Subinventory, or Revision.

    The system populates the Item field in the Material section, with the one selected on the Search and Select: Item page.

18. The UOM, Operational Status, and Service Date fields default once you select the Item.

19. Enter the quantity for the item returned in the Quantity field.

    In the case of serialized items, Quantity is set equal to 1, and the Quantity field is disabled.

20. Enter the Serial Number, Lot, Locator, Revision, and Instance Number details depending on the item attributes.

    The list of values for these fields are validated based upon the item and sub-inventory combination.

21. (Optional) Select a Reason for the material transaction from the list of values.

22. Select the Return Reason from the list of values.

23. Click Apply.

    The material line is saved.

Using Loaner Transactions

Some field service operations provide temporary parts to a customer in place of a part that must be repaired. There is no change of ownership, as the loaned part is still owned by inventory and not by the customer. Field Service Debrief supports this scenario by capturing equipment usage details of loaner equipment.

Loaner transactions are identified in Debrief based upon the Service Activity code assigned to them. When a technician logs a material line with a Service Activity code that supports a loaner transaction, such as Type 'Loaner', the material line has an enabled Return Date field. The technician enters the expected date that the loaned part should be retrieved from the customer.

Once the material line is logged, the installed base is updated to reflect that the "instance" owner is still inventory, but the location is the customer site.

Prerequisites

• A service request and task to report on.
• The setup for Service Activity Code is complete.
• The item setup is complete and the items have the Service Billable attribute set to 'Material'.
• The Return Required check box in Installed Base Transaction type is enabled to identify the Service Activity Code as a loaner.
• The Change Owner must be cleared and the Change Owner To field must be blank.

Steps

The steps to log a material line for a loaner part are the same as those used to log a regular material line. See Adding a Material Line.

Adding an Expense Line

You can create multiple expense lines for a task assignment. The technician cannot modify expense lines that have been submitted to Charges. Technicians can however, still add new expense lines for the task as long as the task assignment status is not 'Closed'.

Use this procedure to add a debrief expense line:

Prerequisites

• A task having a status that enables reporting expenses.

Steps

1. From the Dashboard, click the Debrief icon in the row for the task for which you want to add debrief lines.

   The Update Task page appears.

2. Click the "+" icon to expand the Expense region.

   Existing expense lines associated with this task assignment appear in the summary table of the expense region.

3. Click Add Another Row.

   This expands the Expense region, where the technician can enter information to create an expense line.

4. Select a Business Process.

   • The Business Process default value appears when the Service Request Type has an associated Business Process.

   • If no Business Process is associated, then the Business Process default value is set to the value of the profile option CSF: Default Business Process.

   • If no Business Process is associated, and if the profile option CSF: Default Business Process is not set, then the technician must select the Business Process from the list of values.

5. Choose an Activity from the list of values associated to the business process selected in the preceding step. This is the activity you are going to perform for the expense you are reporting on.

6. Select the Item for which you are going to create an expense line.

   The Item Description field populates with an extended description for the item. The unit of measure is defaulted after selection.

7. Enter either the Quantity and UOM, or the Amount and Currency. Quantity and Amount are mutually exclusive.

8. The Currency field default value is based on the currency set for the profile option: JTF_PROFILE_DEFAULT_CURRENCY. You can change it, if necessary.

9. Select a Service Date from the date list of values.

   The system date appears by default.

10. (Optional) Choose a Justification for the expense from the list of values.

11. To temporarily save the expense line to your debrief, click Add Another Row.

12. To save this line to the permanent record, click Apply.

    For information on correcting expense lines, see Reviewing and Correcting Debrief Information.

Recording Counter Readings

Optionally, you can record counter readings. Counter readings can only be recorded for customer products defined in the installed base that have a counter assigned to them. When no counter is associated with the product, the counters region does not display.

For Service Requests created against a product that has a counter associated with it, upon completion of the task assignment, debrief generates an alert reminder to the technician that the product has a counter. Debrief generates this alert when the task assignment status is changed to either 'Completed' or 'Closed'.

In the case where a single task has been assigned to multiple resources, the alert message is displayed as long as the counters have not been updated between the scheduled start time and the system time by any one of the assigned resources.

Use this procedure to capture counter readings.

Prerequisites

• The installed base item against which a service request has been created must have a counter group setup and counters associated with it.

Steps

1. From the Dashboard main page, click the Debrief icon in the row for the task that you want to add debrief lines.

2. In the Counters region, click the "+" icon to expand the Counters region.

   This displays counters available for the item in the service request.

3. Enter a value for the counter reading.

4. To roll over the counter value, select the Roll over check box.

Details

5. Click the Show/Hide link in the Details column.

6. (Optional) Enter comments for the new reading.

7. To enter adjustment details for the counter reading, select the adjustment type, and then enter the adjustment value.

8. To reset the counter reading, enter the reset value.

9. (Optional) Enter comments for the reset.

10. To include the target reset, check the Include target check box.

11. Click Apply.

Updating Task Details and Notes

At any time during the processes of scheduling service requests, assigning tasks, or debriefing, a Field Service technician or call center agent can add a note to a task. A Field Service technician can not only add a note to a task, but can also view notes that have been associated with a service request. This feature enables a consolidated view of a task and all the related notes added during the task life cycle.

The user also has an option to search for additional notes by clicking the Find on the menu, and then specifying search criteria. For example, to search on Install Base notes, enter the source as "installed base", and then click Enter.

Use this procedure to update task details and notes.

Steps

1. From the dashboard, click the Update icon in the row for the task you want to update.

   The Update Task page appears displaying the Details sub-tab.

2. If you want to add or change the description for the task, enter text in the Description text box.

3. To add a note, in the Add Note region select a Note Type from the list of values (for example, Callback, General Note, and so on).

4. Select the Visibility level for the note from the list of values. Options include: Public, Private, or Publish.

5. Enter the text of the note in the Note text box.

6. Click Apply to save your work.

7. To view your note or any other notes attached to the task, expand the Notes History region (click the + sign to the left of heading).

   This expands the note. From there, you can modify the Note Type or Visibility level of the note.

Viewing a Pro Forma Invoice

Invoking a Pro Forma Invoice enables technicians to review a report that details all the charges entered for the tasks performed at a customer site. The report includes details such as the customers name, bill to address, service request number, item name, quantity, and amount. You can print the report to send hard copy to the customer.

Use this procedure to access the Pro Forma Invoice.

Prerequisites

• A task must be completed.
• For this report to have significance, charges must be entered.

Steps

1. Navigate to the Update Task page for a completed task.

2. From the Update Task page, expand the Show Service Request region.

3. Click Pro Forma Invoice.

   The Service Request Charges Report page appears. In the header information, this report displays service request information. It also displays charges-related information, such as a summary of the charges and details of the charges, including estimate charges, submitted charges, and non submitted charges.

4. To print this page, use the browser's print functionality.

Searching e-Record Evidence Store

Oracle Field Service supports electronic records and approvals so service providers can comply with the US FDA’s CFR Part 11 regulation. The basic FDA requirements are to store electronic records of key application transactions, and to retrieve the records during FDA audits. More specifically, CFR Part 11 is the FDA guideline for trustworthy electronic records that requires companies to employ procedures and controls designed to ensure the authenticity, integrity, and where appropriate, the confidentiality of electronic records, and to ensure that the signer cannot readily repudiate the signed record as not genuine. CFR Part 11 applies to the manufacture and service of certain medical devices, such as heart valves and X-Ray machines.

Support for electronic records and approvals is provided in the Administrator and Technician Portals. This entails creation of eRecords and capturing the approvers ID and password. The key application transaction being recorded is task debrief and closure.

When Field Service technicians complete work on medical devices, they report labor, material, and expenses used, and mark the tasks as complete. The next steps are: approving work performed, capturing an electronic signature of the approver, and closing the task.

Stored records can be reviewed by selecting the Search Erecord Evidence Store link within the Quick Links region of the Field Service Technician Portal or the Field Service Administrator Portal.

When enabled, this functionality creates an electronic record at task closure with the following components:

• The Service Request, Task, and Debrief record, known as the Task Closure Record

• The electronic signature of the approver

• Acknowledgement details

• Additional information

• Related E-Records

• This Task Closure Record, with the approvers signature, can subsequently be recalled from the Oracle Electronic Records and Electronic Signatures (ERES) system.

• The application supports CFR Part 11 Compliance for Debrief initiated through the Portals.

Process Flow

The process is executed as follows:

• When the debrief begins Labor, Material and Expense debrief details are captured.

• Once these details are captured, the debrief is posted as 'Completed', 'Canceled', 'Closed', or 'Rejected'.

• When the Debrief is posted it invokes the Applications Programming Interface to raise a business event.

  • If the Business event is not raised, then an error has occurred.

  • If the Business event is raised, then the Service Erecord is created.

• Service Erecord creation evaluates the Approval Management Engine rule.

• When the debrief is approved, capture the approvers ID and password as the electronic signature.

• Signature capture ends this process.

Setup

Setting up this feature in the Field Service Administrator Portal and in the Field Service Technician Portal requires these key setup steps:

• Set profile option EDR: E-records and E-Signatures value to ‘Yes’

• Set transaction variables ‘eRecord Required’ and ‘eSignature Required’ values to ‘Yes’

• Enable the ERES work flow business event

• Enable the ERES work flow business event subscription and set in ‘Synchronous’ mode

• Define one rule for the Approval Management Engine. When the task assignment status is changed to either ‘Completed’, ‘Rejected’, or ‘Closed’, the approval process succeeds with the approval process showing the list of approvers matching the defined Approval Management Engine rule.

For more information about the Oracle Electronic Records and Electronic Signatures System, see the Oracle E-Records Implementation Guide.

Updating Owned Asset Install Base Records

Some field service organizations provide service for assets owned by the organization, as well as customer products. Typical examples include product based assets, such as trade show, demonstration, and training equipment, and dispersed or mobile assets, such as cell towers and mobile MRI vans.

Support for Non Trading Community Party Addresses

To support this requirement, the TeleService Service Request window supports creation of Field Service tasks when the incident addresses are not associated to a party or customer.

Direct Access to Update Install Base Records

The Technician and Administrator Portals provide access to the Install Base page to directly update the Install Base record referenced on the service request for the equipment being serviced. This functionality streamlines owned asset and customer product moves and operational status tracking. You can also record the operational status of parts and equipment being installed or recovered.

Prerequisites

• Service request and task with reference to an instance number of an item must exist.

Steps

1. When an item instance is associated with a service request, an icon displays in the Field Service Technician Dashboard Install Base column. To invoke a view only page of the instance record, click the Install Base icon.

2. To access the Install Base page for recording location changes, updating instance status, or making corrections, click the Update Task icon.

   The Update Task page appears. In the header region of the Update Task page, there are two drop down lists located to the right of the Instance Action field label.

3. To perform an action on the instance associated with the service request, in the first (left) of the two fields, select 'This Instance' from the drop down list of values.

4. From the second (right) drop down menu, select the desired action, such as 'Put into Service', 'Take Out of Service', 'Install', 'Move', or 'Uninstall'.

5. Click Go.

   The Install Base page appears.

6. To update the operational status of instances at this location that are installed or recovered through material debrief, in the first (left) of the two fields, select 'All Instances' from the drop down list of values.

7. Click Go.

8. Search for and select the instance.

9. For an installed instance, select one of the following operational statuses:

   • Installed

   • In Service

   • Out of Service

   • Not Used

10. In the case of recovered instances, the value of the operational status is seeded as: 'Out of Service'.

Reverse Logistics

The Oracle Field Service Technician Portal provides the Parts Return option to return the excess and unused (defective) parts to the warehouse. The excess parts are repositioned at a higher level in the supply chain to facilitate a greater level of utilization.

The technician can send parts that are defective directly to multiple repair suppliers depending on the part and the country. In addition to sending the parts to repair suppliers, the technician can also route the defective parts to other destinations, such as, warranty recovery, defective on installation analysis, and scrap.

In Repair and Return process the field service organization owns the parts throughout the entire reverse logistics cycle, including the time the parts are stored at the repair supplier.

The Parts Return functionality enables the technician, dispatcher or other field service user to return defective or excess parts to predefined destinations. The destinations are defined for using the Return Routing Rules setup.

The Return Routing module uses business rule parameters that include a source, which is an inventory location, or territory; return type, part category and item. The business rules are used to determine the destinations from any point in the supply chain. It is from anywhere to anywhere approach.

Excess is defined as available parts, which are in excess of maximum (Max) levels. Spares Management uses a program to define excess parts and business rules are optionally applied to filter the excess list. For defectives, all available quantity is considered to be excess. Max levels are not applied on defective parts.

This process is often referred to as Reverse Logistics or sending the parts back to the supply chain or to the appropriate destination.

For information about returning excessand defective parts, see Using Parts Return.

Using Parts Return

Return Routing Rules

Spares Management return routing rules are used to display the destination for a parts return task in the Field Service application. A parts return routing rule is defined by a source, a routing parameter and a destination.

Refer to the Overview: Parts Return section in the Oracle Spares Management User Guide for more information.

Spares Management has the capability to return excess parts to multiple destinations. The technician from a defective sub-inventory or a supply chain warehouse can execute the returns. The customer through integration with the Spares Management returns module must supply the return to locations.

Parts return process includes the following steps:

• Run the concurrent program: Create Excess Lists

• Select a source

• Select a destination

• Select the Items and quantity

• Create the return order

The response for the return request defines the destination. The location is defined as either an Inventory Organization or a Sub-inventory Organization.

Steps

1. Navigate to the Field Service Technician Dashboard.

2. From the Quick Links section, click the Parts Return link.

   The Parts Return page appears. This page displays the Source, Consolidation, and Destination Summary associated with the technicians sub-inventories.

3. Click the Destination link. The Parts Return: Destination Details page displays the Source, Destination, and Defective Return items associated with the destination selected.

4. Select the Select check box next to the item that you want to return.

5. Verify that the quantity to be returned is correct. If it is not correct, for example, if you only want to return a portion of the excess, edit this field to reflect the quantity you want to return.

6. Click Return.

   The Parts Return: Create Order window appears. This table displays pertinent information, such as the Source organization, Source sub-inventory, Destination Organization, and Destination Sub Inventory.

7. Click Finish.

   This confirms the transfer and returns you to the Field Service Technician Dashboard.

Viewing Transaction History

The technician or dispatcher can search and view transaction history of parts that are returned to reconcile shipments made by the technician but not received at the destination.

To View the Transaction History

1. Navigate to the Field Service Technician Dashboard.

   The Dashboard appears.

2. From the Quick Links section, click the Transaction History link.

   The Transaction History page appears. This page enables you to enter search parameters such as; Subinventory, Transaction Type, Destination Organization, Destination Subinventory Transaction Date, Transaction Date Range, Transaction in Last Number of Days, and Item associated with the technicians sub-inventories.

3. Click the Search button. The Transaction History: Results page displays.

   This page displays the transaction results based on your search parameters, with the following information:

   • From: Subinventory

   • Transaction Type

   • Destination

   • Time

   • Item

   • Quantity

4. Click Finish.

   This returns you to the Field Service Technician Dashboard.

Scheduling Tasks

Using Advanced Scheduler functionality, you can reschedule existing tasks that already display in the Field Service Technician Dashboard and you can schedule follow-up tasks that you create in the Create Follow-Up Task page.

You can schedule any task that has a status that has been defined as Schedulable. When you define the task statuses you indicate whether that specific task status is schedulable or not. If you try to schedule a task that contains a status that is not schedulable the system will display a message stating that the task cannot be scheduled. For information on defining task statuses, see Confirming Setup of Tasks in the Oracle Field Service Implementation Guide.

The Schedule Task page can be accessed from the Field Service Technician Dashboard using these methods:

• Click the Schedule icon for a task in the dashboard of the main Field Service Technician Dashboard page.

• Click the Schedule button on the Update Task page.

• Click the Save and Schedule button on the Create Follow-Up Task page.

  For more information on scheduling a follow-up task, see Creating and Scheduling Follow-Up Tasks.

Before you can use the scheduling functionality in the Field Service Technician Dashboard you will need to:

• Install and set up the Advanced Scheduler.

  For more information on the Advanced Scheduler, see Overview of Advanced Scheduler, Oracle Advanced Scheduler User Guide.

• Set up these profile options:

  • CSFW: Technicians Schedulable Options

    Profile Meaning	Access for User
    No Scheduling Permission	No scheduling options for user.
    Work On It	User is able to self assign tasks.
    Self Schedule	User is able to schedule tasks using self schedule and intelligent options.
    Window to Promise	User is able to schedule tasks using self schedule, intelligent and window to promise (WTP) options.

  • Maximum no. of Plan Options

    This parameter value further restricts the maximum number of plan options to display for the results section in the Schedule Task page.

  For more information on these profile options, see the Profile Options Appendix in the Oracle Field Service Implementation Guide and the Task Scheduling and Assignment section in the Implementing Mobile Field Service - Wireless chapter in the Oracle Mobile Field Service Implementation Guide.

Prerequisites

• Oracle Advanced Scheduler is installed and set up.
• Profile options CSFW: Technicians Schedulable Options and Maximum no. of Plan Options parameter are set.
• An existing service request and task must be assigned to the technician.

Steps

1. Navigate to the Schedule Task page from the Field Service Technician Dashboard.

   The Schedule Task page appears.

2. Select the Scheduler Option and click Go. Options are:

   • Intelligent

   • Self Schedule

   • Window To Promise

   The Scheduler API is called and displays in the Result table all the plan options for the resources that meet the scheduling option. The number of options that display are further restricted by the Maximum no. of Plan Options parameter.

   If you selected Intelligent, all plan options for all available resources will be displayed with resource name and the Schedule Start Date and Time and the Schedule End Date and Time.

   If you selected Self Schedule, all plan options will be displayed for the existing technician with Schedule Start Date and Time and the Schedule End Date and Time. The Resource name does not appear for this selection.

   If you selected Window To Promise, all plan options will be displayed in the various window options.

3. Select the option next to the plan option and click Schedule or click the Quick Select icon for the plan option.

   The Update Task page appears with a confirmation message that the task was scheduled successfully.

   In addition, if the technician schedules a task to another technician (Intelligent or Window to Promise), the system will change the Assignment Status for the task for the scheduling technician to Cancelled.

Creating and Scheduling Follow-Up Tasks

Field Service technicians can create and schedule follow-up tasks from the Update Task page.

Use this procedure to create and schedule a follow-up task.

Prerequisites

• A task must be assigned to the technician.
• If you want to schedule the follow up task, Advanced Scheduler must be installed and these profile options need to be set up:

• CSFW: Technicians Schedulable Options

  Select the Self Schedule or Window to Promise value.

• Maximum no. of Plan Options parameter.

For more information on the Advanced Scheduler, see Overview of Advanced Scheduler, Oracle Advanced Scheduler User Guide.

For more information on these profile options, see the Profile Options Appendix in the Oracle Field Service Implementation Guide and the Task Scheduling and Assignment section in the Implementing Mobile Field Service - Wireless chapter in the Oracle Mobile Field Service Implementation Guide.

Steps

1. Navigate to the Update Task page.

2. From the Update Task page, click Create Follow-Up Task.

   The Create Follow-Up Task page appears.

   For field definitions see the table: Update Task Field Definitions

3. Enter a Subject for the task.

4. Select a task assignment Status such as, Assigned or In Planning.

5. Select the Type of task from the list of values, such as Diagnostic, Dispatch, or Callback.

6. Select a Priority level for the task, such as high, medium, or low.

7. Enter Planned Start Time and Planned End Time.

8. Enter the estimated time for the task in the Planned Effort fields.

   Enter a numeric value in the free text field and then choose a qualifier from the list of values, such as minutes, hours, or days.

9. Enter a Description of the task.

10. (Optional) To add a note, choose a Note Type from the list of values.

11. Choose a Visibility level from the list of values.

12. Enter the note in the text box.

To Save the Task Without Using the Scheduling Functionality

13. Click Apply.

    The Update Task page appears with a confirmation message stating that the task was successfully created in the upper portion of the page. This message also displays the task number that was created.

    Plus, the task will be scheduled to the technician that created the follow-up task. The scheduling portion does not utilize the scheduling functionality.

To Save and Schedule the Task

14. Click Save and Schedule.

    The Schedule Task page appears. At the top of the page is confirmation message stating that the task was created successfully. This message also displays the task number that was created.

    Plus, the Scheduler Options will appear that are associated with profile option CSFW: Technicians Schedulable Options. If you selected Self Schedule for the profile value then Self Schedule and Intelligent will appear as Scheduler Options. If you select Window to Promise as the profile value, then Intelligent, Self Schedule, and Window to Promise options will appear as Scheduler Options. If you select No Scheduling Permission or Work On It as the profile value then you will not be able to schedule the task using the Scheduler API. The Save and Schedule button will not appear on the page.

15. Select the Scheduler Option and click Go. Options are:

    • Intelligent

    • Self Schedule

    • Window To Promise

    The Scheduler API is called and displays in the Result table all the plan options for the resource that meet the scheduling option. The number of options that display are further restricted by the Maximum no. of Plan Options parameter.

    If you selected Intelligent, all plan options will be displayed with resource name and the Schedule Start Date and Time and the Schedule End Date and Time.

    If you selected Self Schedule, all plan options will be displayed for the existing technician with Schedule Start Date and Time and the Schedule End Date and Time. The Resource name does not appear for this selection.

    If you selected Window To Promise, all plan options will be displayed in the various window options.

16. Select the Select option next to the plan option for the resource and click Schedule or click the Quick Select icon for the plan option.

    The Update Task page appears again with a confirmation message that the task was scheduled successfully.