1. Using Core Application
  2. Working with Debriefing

Working with Debriefing

The Debriefing page lets you accurately log all work, labor, expenses, added parts, and returned parts associated with an activity for invoice reports and downstream processing. To streamline processing, the Debrief plug-in temporarily stores transaction details in your browser (and supports offline entry until reconnected) before automatically routing them directly to the appropriate Oracle Fusion application—such as Oracle Service Logistics, Oracle Fusion Cloud Maintenance, Oracle Fusion Cloud Project Management, or Oracle Fusion Cloud Time and Labor. Verify your application configurations and custom workflows before submitting a debrief, as transaction records are no longer created or updated in the Oracle Fusion Field Service Inventory entity. After recording the details, you can save them, capture a customer signature, and generate an invoice PDF attached to the activity's file properties for easy sharing via email or messaging apps.

Supported Activity Contexts

An Oracle Fusion Field Service activity can be associated with a Service Work Order, Maintenance Work Order, Project, or Project Task. The activity context identify how Debrief processes each transaction:

  • Service Work Order: Debrief uses the Service Logistics processing flow.

    • Labor and Expenses: Retrieves applicable Service Activity Codes directly from Service Logistics, billing items from Product Information Management (PIM), and units of measure from the Fusion item definition. The billing types associated with the selected Service Activity Code identify available labor or expense items. If Oracle Time and Labor processing isn't configured, Debrief submits labor and expense details through Service Logistics. If configured, labor hours route to Oracle Time and Labor.

    • Parts: Added and returned parts continue through the Service Logistics processing flow.

  • Maintenance Work Order: Debrief uses the Maintenance processing flow to send details directly through standard resource and material transaction APIs without requiring the Oracle Integration Maintenance Cloud Accelerator.

    • Labor and Expenses: If Oracle Time and Labor processing isn't configured, labor is posted as a resource transaction, and expenses are processed according to the configured resource mapping. If configured, labor hours route to Oracle Time and Labor.

    • Parts: Added parts result in material issue transactions, and returned parts result in material return transactions.

  • Project or Project Task: Debrief provides labor time information for Payroll, Project expenditure processing (requires a Project identifier), or both depending on the plug-in configuration. A Project or Project Task alone doesn't provide a destination for parts; if the activity also links to a Service or Maintenance Work Order, parts process through that applicable work order.

Note: You can open and review the Debrief page for an activity that lacks a supported Oracle Fusion Cloud application context. However, you can submit a transaction only after linking the activity to a supported context in Oracle Fusion Cloud Service Logistics, Oracle Fusion Cloud Maintenance, Oracle Fusion Cloud Project Management, or Oracle Fusion Cloud Time and Labor.

Key Debrief Features and Inventory Integration

In addition to Service Logistics flows, Oracle Fusion Field Service supports searching and recording Fusion inventory directly from configured Fusion Service Logistics stocking locations without relying on an Oracle Integration Cloud (OIC) accelerator. When adding a part, mobile workers can view relevant Fusion Inventory details, including subinventory information.

Because labor and expense selection lists are dynamically retrieved and cached from Fusion (Service Activity Codes from Service Logistics, billing items from PIM, and eligible UOMs from Fusion item definitions), administrators no longer need to maintain separate Field Service enumeration properties for these lists.

Record and Submit Debrief Information

  1. Open an ongoing activity and select Debrief.

  2. Record the applicable details across the available sections:

    • Labor: Captures travel and working time (measured in hours), displaying Billing Item, description, start time, end time, and duration.

    • Expenses: Captures extra charges (for example, tolls, parking), displaying Billing Item, amount, description, and currency (when multiple currencies are available).

    • Added Parts and Returned Parts: Captures materials and parts used or returned during performance using standard transaction flows.

  3. Select Add Charges to add another labor, expense, or part entries as needed.

  4. Select Submit Debrief and complete the activity. Debrief evaluates the activity context and configuration, then routes the transactions to the downstream Oracle Fusion applications.