HR to ERP
Oracle HCM to Unit4 integration: Oracle workers as employees per Unit4 company, with department and cost centre on date
With an integration between Oracle HCM Cloud and Unit4 ERP, every new worker from Oracle becomes an employee in the Unit4 company that belongs to their legal employer, with department and cost centre as relations from the effective date in Oracle. A termination in Oracle terminates the employee in Unit4, and a cancelled hire removes the employment again.
What the integration does
Organisations that run HR in Oracle HCM Cloud and projects, hours and finance in Unit4 ERP set up new employees in Unit4 from an export or an email from HR. A transfer to another legal employer or a hire that falls through at the last moment is often processed late in Unit4, or not at all.
- Oracle reports a hire, change or termination in the Atom feeds; KoppelHet fetches the worker's details.
- KoppelHet determines the Unit4 company from the legal employer and first validates the employee without saving.
- The employee goes into Unit4 with employment, department and cost centre from the effective date in Oracle.
- A change of department or cost centre arrives as a new dated relation; the old one gets an end date.
- On a termination KoppelHet sets the employee in Unit4 to terminated; on a cancelled hire the employment is removed.
What to watch for with Oracle HCM Cloud and Unit4 ERP
- Oracle sends a separate notification when a work relationship is cancelled, for example on a no-show or a declined offer. KoppelHet then removes the employment in Unit4, so no employee remains who never started and on whom someone could accidentally book hours.
- A transfer to another legal employer gives a new work relationship in Oracle, while the person number stays the same. Unit4 keeps employees per company, so KoppelHet ends the employment in the old Unit4 company and opens one in the new company, with the same personId.
- Unit4 only accepts employees of the same company in one call. KoppelHet therefore processes an Oracle environment with legal employers in several countries per legal employer, and workers of legal employers without a Unit4 company are left out.
- Oracle records a corrected start date in the work relationship and reports it through its own feed. Unit4 does not let the start date of an employment move later; KoppelHet then ends the employment at the right point and sets it up again with the corrected date.
- An assignment in Oracle can have several dated rows, also in the future. Unit4 keeps department and cost centre as relations with a start and end date. KoppelHet sets up every row from Oracle as its own relation, so a reorganisation dated ahead takes effect in Unit4 by itself on that day.
- Oracle also reports pending workers, who have not been hired yet, in the same feeds. KoppelHet only creates a Unit4 employee once the hire is recorded in Oracle, so candidates do not appear in project administration.
- If Unit4 has an approval step on new employees, Unit4 stores a creation as pending approval. KoppelHet recognises that response and checks the employee again later, so it does not end up on the list as an error.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does salary from Oracle go to Unit4?
No. Unit4 does not need salary for hours and projects; finance manages hourly cost rates in Unit4.
Can projects or cost centres from Unit4 go back to Oracle?
That can be added later as an extension. In the first version only employees and their relations go from Oracle to Unit4.
What if we also have Oracle Fusion ERP?
Then Oracle ERP is often the more obvious choice. This integration is for organisations that use Oracle HCM for HR and Unit4 for projects and finance.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud through the employee Atom feeds (newhire, empassignment, workrelshipupdate, termination, cancelworkrelship) at /hcmRestApi/atomservlet/employee/, with details from the workers REST resource (names, emails, workRelationships with LegalEmployerName, assignments with DepartmentName and effective dates). The feeds cover employees, contingent workers and pending workers and are enabled in Manage HCM Atom Feeds.
- Unit4 ERPx through the Employees API with client ID and secret - POST /v1/employees/validate, POST /v1/employees/batch (at most 200, one companyId, otherwise 403), PATCH with AddOrReplaceById and RemoveById on relatedValues and employments, DELETE /v1/employees/{personId} sets the status to Terminate. 409 on a duplicate personId, 202 with an active workflow.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Unit4 ERP | Notes |
|---|---|---|
PersonNumber | personId | Automatic numbering in Unit4 off |
LegalEmployerName | companyId | Fixed table per legal employer |
names (FirstName, LastName, KnownAs) | nameInformation.firstName, surname, aliasName | |
emails (werkadres) | contactPoints | |
workRelationships (StartDate, TerminationDate) | employments (startDate, endDate) | |
assignments.DepartmentName (EffectiveStartDate) | relatedValues afdeling (dateFrom, dateTo) | |
Kostenplaats van de afdeling of costing | relatedValues kostenplaats (dateFrom, dateTo) | Which relationId differs per Unit4 setup |
WorkerType (E of C) | personnelType | Contractors only if agreed |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud