Set Up the Oracle HCM Cloud Accelerator for Oracle Fusion Field Service

This topic shows you how you can set up the Oracle HCM Cloud accelerator for Oracle Fusion Field Service.

Step 1: Prerequisites

You must fulfil some prerequisites before you configure the accelerator.

The Oracle Fusion Field Service users and resources must be created as mentioned here before enabling the accelerator. The Worker availability and the job profile integrations will use the party ID from the mobile worker's external ID in Oracle Fusion Field Service to fetch the information from HCM to sync with Field Service.

Step 2: Oracle HCM API Duty Roles, Privileges and Data Security

Assign the required roles mentioned in https://docs.oracle.com/en/cloud/paas/integration-cloud/hcm-adapter/prerequisites-creating-connection.html#GUID-F2FB3123-1413-4101-BB66-500215959084 to the integration user to use the Oracle HCM Cloud adapter.

You must configure more duties as given in this table.

Duty Role	Description
Use REST Service - Public Workers Read Only	You can call the GET method associated with the Public Workers REST Service.
Use REST Service - User Accounts Read Only	You can call the GET method associated with the UserAccounts REST Service.
Use REST Service - Worker Availability Read Only	You can call the GET method associated with the worker availability REST service.
Use REST Service - Talent Person Profiles Read Only	You can call the GET method associated with the Talent Person Profile REST Service.
SOA operator Role	The SOA operator role.

You must configure more data security policies as given in this table.

Business Object	Policy Description	Policy Store Impelmentation
Public Person	This entity contains static biographical information about a person.	Privilege: Search Person Deferred; View Worker Contact Portrait Card; View Public Skill; View Person Deferred Data; View Person Career Planning; View Person Skills and Qualifications; Resource: PER_PERSONS
Public Assignment	This is a view on the current PER_ALL_ASSIGNMENTS_M table	Privilege: View Person Deferred Data; View Person Skills and Qualifications; View HCM Person Public Note; Search Person Deferred; Resource: PER_ASSIGNMENTS_V
Person Work Terms Assignment	This entity stores Work terms and Assignment records for Employee, Contingent Worker, Nonworkers, Pending Worker. Discriminator attribute for various types of records is Assignment Type.	Privilege: View Worker Availability; View Worker Calendar; Resource: PER_ALL_ASSIGNMENTS_M
User	Defines the parent entity within the User business object and holds the current details of a user. Only one record is maintained per user.	Privilege: View User Accounts; Resource: PER_USERS

Step 3: Configure Accelerator Connections

You must configure the below connections before you use the accelerator.

1. Oracle HCM Adapter Connection: Click the Connection Name - Oracle HCM Adapter Connection and configure the connection as shown in the screenshot:

   

2. Oracle HCM OFS Adapter Connection: Click the Connection Name - Oracle HCM OFS Adapter Connection and configure the connection as shown in the screenshot:

   

3. Oracle HCM OFS REST Connection: Click the Connection Name - Oracle HCM OFS REST Connection and configure the connection as shown in the screenshot:

   

4. Oracle HCM REST Connection: Click the Connection Name - Oracle HCM REST Connection and configure the connection as shown in the screenshot:

   

Step 4 - Configure the Lookups for the Accelerator

There are three lookups in the Oracle HCM Cloud-Oracle Fusion Field Service integration. Based on the nature of your businesses, the values can be different. You can configure these lookup tables according to your business needs and run them in Oracle Integration.

To configure lookups:

1. Sign in to Oracle Integration.

2. On the Home page, click Integrations > Lookups.

3. Click the name of the lookup that you want to configure and click the '+' icon to add more values. These lookups are available in the accelerator.

Oracle Integration Lookup	Oracle HCM Cloud Property	Oracle Fusion Field Service Property	Description
ORCL-BRT-HCM-OFS_NONWORKING_REASON	<<Absence type in HCM >> For example: Sick	<<Non working reason in OFS>> For example: illness	Map the Oracle HCM Cloud absence type such as Sick Leave, Earned Leave, Casual Leave with Oracle Fusion Field Service non-working reasons. For calendar events or holidays from Oracle HCM Cloud, the Oracle HCM Cloud value to be configured in the lookup is 'CAL' and the corresponding Oracle Fusion Field Service non-working reason can be mapped.
ORCL-BRT-HCM-OFS-CONFIG			This lookup holds the criteria and default values used in Oracle HCM Cloud to Oracle Fusion Field Service integrations.
ORCL-BRT-HCM-OFS_SUBINT_VERSION			This integration provides the capability to call a different version of a sub-integration that isn't part of the current package. It accepts the integration identifier as the key and version of the sub integration to be mapped as the value. If nothing is given, it will take the sub-integration from the same package.

Step 5: Integrations to be activated

1. You must activate the below integrations to sync the Worker availability:
   1. Oracle HCM Fusion FS Worker Availability
   2. Oracle HCM Fusion FS Worker Availability Helper
   3. Oracle HCM OFS Worker Availability Activity Type
   4. Oracle HCM OFS Worker Availability Activity Delete
   5. Oracle HCM OFS Worker Availability WS Delete
   6. Oracle HCM OFS Worker Availability Sync Helper
2. You must activate the below integrations to sync the Employee job profiles:
   1. Oracle HCM Fusion FS Work Skill Sync
   2. Oracle HCM OFS Employee Sync Helper
   3. Oracle HCM OFS Resource Work Skill Create
   4. Oracle HCM OFS User Type Util