Employee Work Availability
The Employee Work Availability from Oracle HCM Cloud to Oracle Fusion Field Service integration extracts the resource availability per day including the resource work schedule, absences, holidays, and exceptions. This integration gets the availability of a resource for a period of time and syncs the record to Oracle Fusion Field Service.
This is a scheduled integration that is recommended to be run once per day. The
availability of a resource is calculated by accounting for absences, exceptions,
holidays, and work schedules. Some of the key use cases supported by the integration
using resource availability are:
- Handling resource work schedules: A work schedule defines an employee's availability for work, which includes work patterns, shifts, and so on. You can configure work schedules in Oracle HCM Cloud by referring to this link for more information. The integration looks for all of the work schedule configurations and updates the availability of a resource as a custom work schedule in the Oracle Fusion Field Service resource's calendar.
- Handling resource exceptions in between work schedules: A 'resource
exception' is a deviation in a resource's availability from a work schedule or
schedule assignment. A resource exception defines when a resource is
unavailable. For example, a worker may be attending a training or is on a lunch
break, and therefore is unavailable within a specific time interval of a day.
These examples describe resource exceptions:
- Resource exception example #1: An employee is not available for working
on activities within a particular time interval (for example, trainings
or breaks). You can configure exceptions like these against a work
schedule in Oracle HCM Cloud. The integration updates these
exceptions as internal activities in Oracle Fusion Field Service.Note: The internal activity type "ResourceExceptions" is used as the default activity type for all the internal activities. This activity type is created automatically as part of the scheduled data transfer from Oracle HCM Cloud to Oracle Fusion Field Service. The default activity type is configured in the lookup table, Oracle_HCM_OFS_IntegrationVariablesLookup as OFS_DefaultActivityType.
- Resource exception example #2: An employee is working on a non-working day. You can configure an exception for an employee working on a non-working day under a work schedule in Oracle HCM Cloud. The integration updates these exceptions as custom work schedules, against the selected resource for the selected date and time in Oracle Fusion Field Service.
- Resource exception example #1: An employee is not available for working
on activities within a particular time interval (for example, trainings
or breaks). You can configure exceptions like these against a work
schedule in Oracle HCM Cloud. The integration updates these
exceptions as internal activities in Oracle Fusion Field Service.
- Handling holidays: Holidays are created as calendar events in Oracle HCM Cloud. The integration will look for all the calendar events defined in Oracle HCM Cloud that will be transferred to Oracle Fusion Field Service. These will be created as non-working days at the resource level.
- Handling absences: Integration will support half day/full day absences of an employee in Oracle Fusion Field Service. The integration will look for all absences configured in Oracle HCM Cloud. All of the half-day absences will be defined as internal activities in Oracle Fusion Field Service. Full-day absences will be treated as non-working days at the resource level.