HR to ERP
Oracle HCM to AllSolutions integration: employees per legal employer from Oracle in the right AllSolutions company
With an integration between Oracle HCM Cloud and AllSolutions, every employee of a Dutch legal employer in Oracle automatically reaches the AllSolutions company that belongs to that employer, with department, job and start date. A termination in Oracle becomes an end date in AllSolutions, and a hire cancelled in Oracle disappears from AllSolutions again as long as no hours are booked on it.
What the integration does
Organisations that run HR globally in Oracle HCM Cloud and projects, hours and invoicing in AllSolutions in the Netherlands enter new colleagues there by hand. If a candidate withdraws just before the start, an empty employee remains in AllSolutions and turns up in every project plan.
- HR records a hire or change in Oracle for a Dutch legal employer.
- KoppelHet reads the new entries from the Oracle feeds and fetches the employee.
- KoppelHet switches to the AllSolutions company of that employer and creates or updates the employee.
- On a termination KoppelHet sets the end date; on a cancelled hire it removes the employee if nothing has been booked on them.
What to watch for with Oracle HCM Cloud and AllSolutions
- Oracle reports a cancelled work relationship separately, for example when someone does not show up on the start date or still declines an offer. KoppelHet then deletes the employee in AllSolutions, but only if no hours or projects are on it and the integration user may delete; otherwise they get an end date equal to the start date.
- If the hire date of an active employee is changed in Oracle, it appears in a separate feed for work relationship changes. KoppelHet sets the new date in AllSolutions, so hours from the real start date are not refused and hours before it are not wrongly accepted.
- In Oracle an employee has a work relationship per legal employer. Every Dutch employer belongs to its own AllSolutions company. AllSolutions only lets the integration user switch company if the login-company function is also exposed through the REST API; we set that up with the application administrator.
- In Oracle the assignment feed also reports salary and manager changes. AllSolutions only needs department and job for hours and projects. KoppelHet compares every entry with the previous state and only sends AllSolutions a change if department or job is really different.
- AllSolutions exposes free fields through the REST API, with a label of your own. KoppelHet stores the Oracle person number in such a free field. That way the employee can still be found if the number in AllSolutions differs or a name changes.
- Only one view per browser can be active for the REST API in AllSolutions, and which fields KoppelHet sees depends on it. If someone activates another view, fields suddenly go missing. KoppelHet checks on every run that the expected labels are present and otherwise stops with an alert.
- Oracle also sends entries on changes to passport, citizenship and national identifier. AllSolutions has no use for them. On such an entry KoppelHet only fetches name and work email and leaves personal data AllSolutions does not need in Oracle.
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 go to AllSolutions too?
Only if they book hours in AllSolutions. Oracle reports them in the same feeds, so we choose per worker type what is included.
What if a department does not exist in AllSolutions yet?
AllSolutions then refuses the employee. KoppelHet reports which department is missing and tries again once finance has created it.
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, also for a future-dated hire; empassignment; empupdate; termination; cancelworkrelship; workrelshipupdate for, among other things, a changed hire date) and the workers REST resource with workRelationships, assignments and names. Feeds apply to employees, contingent workers and pending workers.
- AllSolutions through the REST API: POST /api/v1/Login with a signature (SHA1 of user, client ID and secret) and then the token in every call; GET on the active view, POST to create, PUT with only changed fields, DELETE under the integration user's authorisation. Switching company through the login companies function (MWZBDR), which must itself also be exposed through the REST API. Free fields with a REST API label.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in AllSolutions | Notes |
|---|---|---|
PersonNumber | Vrij veld met REST API-label | Fixed key next to the AllSolutions number |
names (FirstName, LastName) | Naam | |
WorkEmail | E-mailadres | |
workRelationships.LegalEmployerName | AllSolutions-bedrijf (inlogbedrijf) | Through a table |
assignments.DepartmentName | Afdeling | |
assignments.JobName | Functie | |
workRelationships.StartDate | Datum in dienst | |
workRelationships.TerminationDate | Datum uit dienst |
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