Limitations of the Accelerator

This topic lists the scenarios that are currently not handled in the accelerator.

Integration: Oracle HCM-OFS Worker Availability

Scenario 1

Multiple partial leaves on the same day within the work schedule is not supported. Only half-day leaves are supported in this release.

Example:

The work schedule of an employee for a day is from 8 AM to 5 PM. The employee goes to Oracle HCM Cloud and applies for partial leave from 10 AM to 11 AM and then from 3 PM to 4 PM on the same day.

When the integration runs, it syncs only the last partial leave applied for the day. In this example, an internal activity is created in Oracle Fusion Field Service from 3 PM to 4 PM.

A workaround to handle this scenario is to use resource exceptions, instead of absences to indicate multiple non-available time slots on the same day.

Scenario 2

Let's assume that the work schedule of an employee is from 8 AM to 5 PM. Now the employee decides to perform overtime work from 7 PM to 10 PM on the same day. This scenario is not handled in the current worker availability integration. This setup creates a single working schedule from 8 AM to 10 PM in Oracle Fusion Field Service . In the actual scenario, the employee is not available for work from 5 PM to 7 PM. This information is not tracked in Oracle Fusion Field Service.

Scenario 3

Schedules with more than one shift for a day with a time gap in between are represented as a single shift in Oracle Fusion Field Service.

Example:

In Oracle HCM Cloud, create a work schedule with two shifts for a day:

Shift 1: 7 AM to 11 AM

Shift 2: 12 PM to 3 PM

When the integration runs, this is represented as a single shift from 7 AM to 3 PM in Oracle Fusion Field Service. However, in the actual scenario, the employee is not available for work from 11 AM to 12 PM.

Scenario 4

Let's assume that an employee has an overnight work schedule from 7 PM to 3 AM on the next day and the employee is on this schedule from the Jan 1, 2023 to Dec 31, 2023. If we run the scheduled integration for ten days from the Jan 10, 2023 to Jan 20, 2023, we would see the schedule for each day being updated as 7 PM to 3 AM in Oracle Fusion Field Service. On the last day, that is Jan 20, the schedule is updated as 7 PM to 11:55 PM. The schedule for the next day, that is Jan 21, from 12 AM to 3 AM is not updated in Oracle Fusion Field Service. This is because, we have scheduled the integration to pull data from Oracle HCM Cloud only for 10 days, which in this example would be from the Jan 10 to Jan 20.