Real-Time Integration Service for External Payroll

An ESS daemon process executes continuously to monitor the new-hire data created in Oracle HCM Cloud. You must start this ESS job once and define a schedule to execute the job at a defined frequency.

Consider these points while determining the frequency:

• How often the new-hire data is created in Oracle HCM Cloud?

• How often the new-hire data should be sent to ADP Global Payroll?

These considerations will help you determine the scheduling frequency of this ESS job. A frequency of 15 or 30 minutes would meet the common requirements of the new-hire data created or delivered to ADP Global Payroll within the 15 or 30 minutes of the new-hire creation and approval in Oracle HCM Cloud.

The ESS job reads the ATOM feeds generated by the new-hire transactions in HCM Cloud to:

• Identify and publish the ATOM feeds to ADP Global Payroll

• Process the new-hire assigned to the payroll for which you enabled integration on the Payroll Integrations page

If you create the new-hire data using HCM Data Loader, include the SET command in the data file to generate ATOM feeds for the new-hire being created.

SET ENABLE_INCREMENTAL_LOAD_EVENTS Y

Here are few points before you start the ESS job:

• HCM Extracts processes any new-hire record entered before you start the ESS job.

• The real-time integration doesn't process any future dated hires to ADP Global Payroll, but HCM Extracts processes and publishes the records.

• When you enable the integration, all the newly created new-hire transactions are processed. You must manually stop these transactions from being sent to ADP Global Payroll when the real-time integration isn't required for a subset of data and you want it to be processed by HCM Extracts.