1. Administering Oracle Fusion Field Service
  2. Integrating with Oracle Fusion Cloud HCM Time and Labor (OTL) for Debrief Posting

Integrating with Oracle Fusion Cloud HCM Time and Labor (OTL) for Debrief Posting

Oracle Fusion Field Service integrates with Oracle Fusion Cloud HCM Time and Labor (OTL) to post labor hours directly from Debrief activities. When mobile workers submit Debrief for project-based activities created in Oracle Fusion Field Service, the application creates or updates time card entries in OTL. For team or crew-based activities, the labor hours of individual crew members can be submitted as separate OTL time entries against the same project task.

Note: This topic describes posting labor information from Debrief to Oracle Fusion Cloud HCM Time and Labor. Starting in Oracle Fusion Field Service 26D, Maintenance Work Order activities can also use Debrief to send applicable labor, expense, added-part, and returned-part information to Oracle Fusion Cloud Maintenance. For information about configuring the Oracle Fusion Field Service part of Maintenance Work Order Debrief, see Configure Maintenance Work Order Debrief.
Advantages

  • Eliminates duplicate time entry across separate apps.

  • Ensures compliance through OTL validations and approval workflows.

  • Makes approved time immediately available for payroll and project costing.

  • Captures labor for each crew member on team-based project activities.
  • Improves project costing accuracy by posting each crew member’s labor against the associated project task.
  • Reduces duplicate entry for crew leads and crew members.

Prerequisites

Before configuring Time and Labor for debrief posting, ensure the following:

  • Oracle Fusion Field Service is deployed and operational
  • Oracle Fusion Cloud HCM Time and Labor is licensed and configured
  • Oracle Fusion Applications connectivity has been established and successfully tested.
  • User identities are synchronized between systems
  • Project-based activities are configured in Field Service

Before using team-based OTL posting, ensure that:

  • The activity is based on a Oracle Fusion Project task.
  • The activity uses the Teamwork feature.
  • Each crew member has a valid Field Service resource identity mapped to the corresponding HCM/OTL person identity.
  • The Debrief plugin is configured for OTL posting.
  • The laborItemNumberForRegLabor plugin parameter is configured if you want labor hours to be automatically populated for crew members.
    Note: The laborItemNumberForRegLabor plugin parameter is also used to provide the default regular-labor item for Maintenance Work Order Debrief. Maintenance Work Order Debrief can also use the laborItemNumberForTravel parameter to provide the default travel-labor item. For information about configuring these parameters for Maintenance Work Order activities, see Configure Maintenance Work Order Debrief.

To ensure successful posting and validation, complete these steps in OTL:

  • Time Entry Layout Components
    • Expose the Payroll Time Type and/or Expenditure Type fields that mobile workers must select during time entry.
  • User Profile Configuration
    • Assign appropriate time entry layouts and enable payroll time types or expenditure types for each person profile expected to submit time from Debrief.
  • Project/Task Availability
    • Confirm required project and task attributes are available and valid for accounts that will use project costing.

Process Labor for a Project or Project Task

For activities associated with a Project or Project Task, Debrief can create time information for Oracle Time and Labor.

Plugin Configuration Processing Behavior
pjcExpenditureTypeConfig Debrief provides the information required to process labor as a Project expenditure. A Project identifier is required.
payrollTypeConfig Debrief provides the information required to process labor for Payroll.
Both parameters Labor time information can be used for both Payroll and Project expenditure processing. A Project identifier is required for Project expenditure processing.

These parameters control labor-time classification and destination. They don't configure added part or returned part processing.

If an activity also has a work order context, parts associated with a Service Work Order are processed through Service Logistics, and parts associated with a Maintenance Work Order are processed through Maintenance. A Project or Project Task by itself doesn't provide a destination for added part or returned part transactions.

Oracle Time and Labor Processing for Work Orders

When Oracle Time and Labor processing is configured for a Service Work Order:

  • Labor hours are submitted to Oracle Time and Labor.
  • Added and returned parts continue through Service Logistics.
  • Other supported transactions follow the Service Work Order configuration.

When Oracle Time and Labor processing is configured for a Maintenance Work Order:

  • Labor hours are submitted to Oracle Time and Labor.
  • Added and returned parts continue through the Maintenance material transaction flow.
  • Other supported transactions follow the Maintenance Work Order configuration.