HR to ERP
Oracle HCM to 4PS Construct integration: employees of the construction companies from Oracle in the right 4PS company
With an integration between Oracle HCM Cloud and 4PS Construct, every employee of a legal employer that works in 4PS automatically reaches the matching 4PS company, with job, work email, start date and cost centre. A termination in Oracle sets the end date in 4PS, and a hire cancelled in Oracle is deleted in 4PS as long as no hours are booked on it.
What the integration does
Organisations that run HR for the whole group in Oracle HCM Cloud and have their construction or installation companies run on 4PS Construct enter technicians and site managers into 4PS by hand. A hire that falls through at the last moment stays there as an employee and keeps coming back in plans and timesheets.
- HR records a hire or change in Oracle at an employer that works in 4PS.
- KoppelHet reads the Oracle feeds and fetches the employee with their assignment.
- KoppelHet creates the employee in the 4PS company of that employer, or updates them.
- Department and cost centre go on the employee as a default dimension, if the value exists in 4PS.
- On a termination KoppelHet sets the end date; after the last working day the status changes to terminated.
What to watch for with Oracle HCM Cloud and 4PS Construct
- If a candidate withdraws or someone does not show up on the first day, Oracle reports a cancelled work relationship. The standard API under 4PS can delete an employee. KoppelHet only does that if no time registrations are on the employee yet; otherwise they become inactive, so booked hours stay correct.
- Every legal employer in Oracle belongs to its own 4PS company. The API under 4PS works per company. KoppelHet only includes work relationships of employers in the table, so employees of offices or countries without 4PS never end up in it.
- Oracle's assignment feed also reports salary and manager changes. The employee card under 4PS has no field for salary or manager. After a comparison KoppelHet leaves such entries aside and only updates 4PS when job, department or cost centre changes.
- In Business Central, which 4PS runs on, the address on an employee is the one that appears on documents. Oracle reports address changes in the same feed as name and work email. KoppelHet deliberately does not copy the home address from Oracle, so it does not appear on work orders or other documents.
- Dimension values such as cost centres are read-only in the standard API. Oracle can create a department before finance has the cost centre in 4PS. KoppelHet then creates the employee without that dimension and tells finance which code is missing; the dimension follows in the next round.
- A change under 4PS requires the employee's version tag; an outdated tag is refused. If a 4PS administrator updates the card in between, KoppelHet reads the new version and compares first, so their adjustment is not overwritten by an old Oracle entry.
- Oracle already reports a hire when it is recorded with a future date. KoppelHet then puts the employee into 4PS straight away with that start date, so work planning sees them in the schedule before they start.
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
Do contingent workers reach 4PS too?
Only if they book hours in 4PS. We agree that per employer.
Is anything written back to Oracle?
No. Oracle stays the source. Hours or costs from 4PS to Oracle can be added later as an extension.
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 under /hcmRestApi/atomservlet/employee/ (newhire, empassignment, empupdate, termination, cancelworkrelship) and the workers REST resource with workRelationships, assignments and names.
- To 4PS through the Business Central API v2.0 per company: POST, PATCH and DELETE on employees (number, givenName, middleName, surname, jobTitle, email, employmentDate, terminationDate, status Active, Inactive or Terminated), with If-Match required on PATCH and DELETE. timeRegistrationEntries per employee to check beforehand; defaultDimensions with parentType Employee. dimensionValues is read-only.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in 4PS Construct | Notes |
|---|---|---|
PersonNumber | number | |
names (FirstName, MiddleNames, LastName) | givenName, middleName, surname | |
WorkEmail | email | |
assignments.JobName | jobTitle | |
workRelationships.LegalEmployerName | 4PS-administratie (company) | Through a table |
workRelationships.StartDate | employmentDate | |
workRelationships.TerminationDate | terminationDate en status Terminated | |
assignments.DepartmentName en kostenplaats | defaultDimensions | Existing dimension values only |
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