Administering Employees and Related Entities

Employees under a Service Region with Engine = OFS will be synchronized to Oracle Field Service automatically through Workflow Policies by invoking OIC integration outbound REST. Along with Employee record, their Address (Home or Depot), Skills, Exception hours (Leave, meetings, and so on) will also be synchronized to Oracle Field Service.

Ensure that the schedule mapped to the employee has been created in Oracle Field Service. Once an employee has been added, a corresponding Resource and User will be created in Oracle Field Service by the corresponding OIC integration workflow policy.

Transfer of Siebel employee address to Oracle Field Service Resource Location

The work start and work end location of an Oracle Field Service resource will get updated based on the start and end home addresses or depot address. The integration will update the resource start location as the start depot address if the employees shift start is configured as a depot or if it's blank. In all other conditions, the start location will be the location associated with start home address. Similarly, the end location will be the end depot address if the employees end of shift is configured as depot or if it's blank. In all other conditions, the end location will be the location associated with the end home address.

Transfer of Siebel employee skill to Oracle Field Service Resource Skill

The employee skill will be updated as a resource skill in Oracle Field Service as part of the employee skill integration.

Transfer of Siebel employee work schedule to Oracle Field Service Resource Schedule

As a prerequisite of this integration, an OFS admin user will have to create a schedule as an OFS calendar configuration with the same name as the Siebel schedule name. As part of the employee data transfer workflow, Siebel will share the schedule name associated with the employee and it will be updated as a schedule in the OFS resource's calendar. In cases where there is no matching schedule in OFS that corresponds to the Siebel schedule, a resource will be created in OFS without a schedule and an error message will be updated in Siebel.

Transfer of Siebel employee exception hours

This integration treats holidays, working exceptions (for example, meetings, trainings), in some scenarios Field technicians may have to work on a non-working day for example, no work on Sunday from 6:00 A.M. to 12:00 A.M. in a 7x12 schedule, in Siebel this can be configured as exception to normal work schedule. Exception hours (holidays) - If the schedule in Siebel contains any holiday exception, the integration will apply this holiday to the OFS resource calendar as a non-working day. Working exception hours - If the employee in Siebel contains any working exception hours (such as meetings, trainings), an internal activity will be created during this period so that the field technician's availability can be updated accordingly.

Overtime on a non-working day - If the employee in Siebel contains any overtime exception, the integration will apply it as a schedule in the Oracle Field Service resource's calendar for that non-working day.

Below is the transfer process flow for Employee Data Synchronization between Siebel, Oracle Integration Cloud (OIC) and Oracle Field Service.

Incremental Update of Service Regions and Associated Data

Apart from the initial migration of the service region, when a business administrator updates the zip code or holiday exception associated with the service region, that data also will get updated in Oracle Field Service. Similarly, when a business administrator updates the following information associated with an employee, that then will get updated in Oracle Field Service in an incremental manner.

• Employee basic information

• Employee location

• Service region associated with that employee

• Work skill associated with that employee

• Working exception and Non-working exception hours associated with that employee