Oracle HCM OFS Party Sync Integration

"Oracle HCM OFS Party Sync" integration transfers data for newly-hired employees from HCM to OFS.

When a new employee is added to HCM, a corresponding resource can be created in OFS. Whenever a new employee is hired, and if the partyID is created, then those resources will be sync'd to OFS.

Whenever a new employee is hired with a current or past hire date, then the TCA partyID is created. And for any future hires, the partyID is created after the ESS job "Maintain Party and Location Current Record Information" has been run. The latest versions of HCM integrations will create the employees in OFS only if a partyID is generated for the employee.

Extract Flow

• The Oracle HCM OFS Party Sync calls the Public Worker API to fetch all the ACTIVE employees in the given business units, given job codes and whose effective date is >= the current date - 2 days [the 'days' parameter is an integration property that can be modified]. And the sub integration, Oracle HCM OFS Party Sync Helper is triggered for each person.
• The Oracle HCM OFS Party Sync Helper checks if the partyID is available for the employee. If the partyID is not available, the integration terminates. If the partyID is available, it validates the resource bucket and prepares the data for resource creation in OFS and triggers the 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 with the name as the business unit name). The resource is also populated with locations that correspond to the employee's home address and assignment location.