Submit Labor Hours to Oracle Time and Labor

For project-based activities, Debrief can use the associated project and task information when creating or updating time entries. For team or crew-based project activities, Debrief can submit individual labor entries for each crew member against the same project task.

For a Maintenance Work Order activity, labor hours can also be submitted to Oracle Time and Labor when the applicable OTL configuration is available. Added and returned parts for a Maintenance Work Order continue through the Maintenance material transaction flow. The Maintenance Work Order flow doesn't use the project-based crew requirements described in this topic.

To submit labor for a project-based activity:

Open a project-based activity from My Route and select Debrief.
Review the prepopulated labor hours.
- For a regular activity, review your own labor entry.
- For a team or crew activity, review the labor entries for each crew member.
Delete and re-enter labor entries if corrections are required.
Add labor for any missing crew member or for a different work type, if needed.
In Work type, select the appropriate payroll time type or expenditure type.
Submit Debrief.

OTL Time Card Population

For team or crew-based activities, OTL time card entries are created or updated for each crew member. Each entry uses the crew member’s identity, the selected work type, the labor duration, and the project and task associated with the activity.

Submitting populates standard OTL fields as shown below:

Field	Source/Value
Assignment Number	Person's OTL assignment number
Primary Assignment ID	Person's primary OTL assignment ID
Project Number	Activity-associated project
Task Number	Activity-associated task
Expenditure Type Name	Selected Work type name
Expenditure Type Class	Selected Work type class
Expenditure Type / Time Type / Payroll Time Type	Selected Work type value
Time (Duration)	Labor hours from Debrief
Date of Time Entry	Activity date
Field Resource Name / Person ID	Mobile worker identity

Note: If the time card is already available for the same day/resource, labor hours will get updated to the existing time card. If not, a new time card is created.

Offline Handling

Debrief defers posting when offline. Upon reconnection, application auto-retries for 24 hours (configurable by admins). Failed validations (for example, unmapped Work type, missing assignment) trigger retries.

Important:

Ensure Project and Task display on activities; see "Configure Activity Page to Display Project Task" in the Administrative Guide.
Non project activities (for example, from Fusion Service/Maintenance work orders) are unsupported.
OTL manages approvals and audits per security policies.
Activities created from Fusion Service work orders or Maintenance work orders aren't supported.
Team-based OTL updates are supported only for activities that use Teamwork.
If an OTL time card already exists for the same day and crew member, the time entry is updated. Otherwise, a new time entry is created.

For Maintenance Work Orders, when OTL processing is configured, labor hours are submitted to Oracle Time and Labor, while added and returned parts continue through the Maintenance material transaction flow. This behavior is documented in Oracle Time and Labor Processing for Work Orders in Administering Oracle Fusion Field Service.