1. Integrating with Oracle HCM Cloud Using an Oracle Integration Accelerator
  2. Oracle HCM OFS Employee Extract Integration

Oracle HCM OFS Employee Extract Integration

"Oracle HCM OFS Employee Extract" integration is used to upload employee details from Oracle HCM Cloud to Oracle Fusion Field Service using HCM extract.

The accelerator uses the HCM extract to upload employee details from HCM to OFS. Details about the employee extract and setup configurations are explained here.

The accelerator extracts the following employee information as part of the "Oracle HCM OFS Employee Extract integration flow":
  • Employee basic details: These are basic details of the employee such as person number, first name, last name, person email address, phone number, and home address.
  • Employee assignment details: These are employee assignment details such as assigned business unit, job code, department, user details, and location.

Extract Flow

  • The extract process will filter all employee with a job code corresponding to field mobile worker, business unit and assignment status as "active".
  • The extracted employee details will be created in OFS if a corresponding resource is not available in OFS. Otherwise it will update the resource details in OFS based on the mapping and lookup configurations in OIC.
  • The "Oracle HCM OFS Employee Extract" scheduled integration reads the extract files and filters out the employees with a given business units, given job codes and status as "active". Then it triggers the child integration "Oracle HCM OFS Extract Helper" for each person.
  • The "Oracle HCM OFS Extract Helper" checks if the partyID is generated or not. If the partyID is not available, it terminates the integration. Otherwise, it will prepare the data required for the OFS resource creation and trigger the helper integration "Oracle HCM OFS Employee Sync Helper".
  • The Oracle HCM OFS Employee Sync Helper is a common helper integration that will take care of the resource creation, user creation, resource locations and assignment location creations.
  • The resource and user are mapped under a bucket (the bucket is defined in the lookup; if there is no mapping available, then the resources are placed under the organization unit that has the same name as the business unit). The resource is also populated with resource locations which correspond to the employees home address and employee assignment locations.

If any OFS resource is available with the same external ID as the HCM Person Number, then the external ID is updated with 'partyID'.