X4HR to ITSM
Oracle HCM to Xurrent integration: people, organisations and requests on hire and termination
With an integration between Oracle HCM Cloud and Xurrent, every employee from Oracle is a person in Xurrent, with organisation, site and manager, and a hire, transfer or departure in Oracle sets up a request from the right template. Xurrent has no Oracle HCM integration of its own; KoppelHet reads the Oracle feeds and writes through the Xurrent REST API.
What the integration does
Organisations with Oracle HCM Cloud as HR system and Xurrent for IT and facilities services often maintain people in Xurrent with a periodic CSV export from Oracle. Hires and departures run through email or a form, and the source key in Xurrent differs from the person number in Oracle.
- HR records a hire in Oracle; it appears straight away in the newhire feed.
- KoppelHet creates the manager if they are not a person yet, then the new employee, with the person number as sourceID.
- A request from the onboarding template is submitted for the new employee, by the manager, with the start date as desired date.
- A transfer from the assignment feed updates organisation and site and produces a request for access at the new place.
- A termination produces an offboarding request; once completed, KoppelHet disables the person.
What to watch for with Oracle HCM Cloud and Xurrent (4me)
- KoppelHet reads the Oracle Atom feeds with an integration user that can only read, and writes people and requests through the Xurrent REST API.
- In Xurrent the work email is a person's unique key and login name. Oracle reports a new work email in the empupdate feed; because KoppelHet records the person number as sourceID, the same person gets the new address and no duplicate is created.
- A request in Xurrent always needs who it is for and who submits it. Oracle adds a hire to the feed as soon as HR records it, often weeks before the start, so KoppelHet creates the person straight away to submit the request in time, with the Oracle manager as submitter.
- A disabled person may no longer be linked to new records in Xurrent. If Oracle reports through cancelworkrelship that someone is not coming, KoppelHet first adds a note to the open onboarding request and only then disables the person.
- Oracle feeds come for employees, contingent workers and pending workers. KoppelHet picks a different Xurrent template per worker type, so a contingent worker only gets accounts and no laptop order.
- Each legal employer from Oracle becomes an organisation in Xurrent with the departments beneath it. A global transfer to another employer moves the person to the new organisation on the effective date, with the same sourceID.
- Sites in Xurrent have a time zone. KoppelHet links the person to the site of their Oracle work location, so the desired date of a request is on the first local working day.
This integration is also part of joiner, mover, leaver.
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 Xurrent have an Oracle HCM integration?
We have not found one. KoppelHet uses the Oracle feeds and the regular Xurrent REST API.
Can the CSV import of people stay?
It is dropped; otherwise two sources write to the same people. For a large reorganisation KoppelHet can deliver an import file itself.
Does salary data go to Xurrent?
No. The assignment feed also reports salary changes, but KoppelHet only takes job title, organisation, location, manager and dates.
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 Atom feeds at /hcmRestApi/atomservlet/employee/{collection} (newhire, empassignment, empupdate, termination, cancelworkrelship) and the workers through the HCM REST API, with a read-only integration user.
- Xurrent through the REST API with an OAuth token. People through /people (primary_email required, employeeID, job_title, organization, site, manager, disabled), organisations through /organizations, sites through /sites with time_zone; source and sourceID only by an Account Administrator. Requests through POST /requests with subject, category, team, requested_for, requested_by, template and desired_completion_at. Rate limiting per user with HTTP 429.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Xurrent (4me) | Notes |
|---|---|---|
PersonNumber | source en sourceID | Only an Account Administrator may set them |
WorkEmail | primary_email | Unique and the login name |
DisplayName | name | |
Job van de primaire assignment | job_title | |
Legal employer en Department | organization (met parent) | |
Location | site (met time_zone) | |
Manager van de assignment | manager | |
Startdatum of laatste werkdag | desired_completion_at van het verzoek |
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