Fusion Field Service Work Orders Overview

Starting in 26A, because Field Service is now in Fusion, there's a new work order type called Fusion Field Service Work Order. Oracle still supports Generic and Oracle Field Service work orders (which use the Oracle Integration Cloud accelerator), but the new Fusion Field Service work order doesn’t need an accelerator.

Data is no longer duplicated, synced, or mapped into Field Service. Fusion Field Service uses a single, unified setup. Field Service setup and Work Order setup both reference the same data.

The work order defines what needs to be done, and that scope can be split into one or many activities in Fusion Field Service. Think of the work order as the header, and the activities as the child records.

Work order data is also what the technician sees in Fusion Field Service. When you update fields on the work order, those changes show up immediately on the related activities. So if three activities share the same work order, they’ll all show the same common data. For example, changing the contact on the work order updates it on all three activities automatically.

If you’re deciding where to add a custom field, ask: should this value be the same for every activity under the same work order? If yes, add it to the work order so it rolls down to all activities. If it needs to be different for each activity, add it to the activity instead.