Leave, absence and time
Oracle HCM to Quinyx integration: workers, assignments and approved absences from Oracle in scheduling
With an integration between Oracle HCM Cloud and Quinyx, every worker from Oracle appears automatically in Quinyx, in the unit of their location and with an agreement based on the normal and standard working hours of their assignment. Absence approved in Oracle appears as an absence in the schedule, and a withdrawn absence disappears from it again.
What the integration does
Organisations that manage staff in Oracle HCM Cloud and plan stores, branches or care locations in Quinyx enter every hire and every change in hours twice. Absence a manager approves in Oracle only reaches the planner when someone passes it on.
- HR records a hire or an assignment change in Oracle, including with a future date.
- KoppelHet reads Oracle's feeds and fetches the worker with their assignments.
- Quinyx receives the employee in the unit of the primary assignment, an agreement based on the working hours, and an extra role for every other assignment.
- When absence is approved in Oracle, KoppelHet enters it in Quinyx; a withdrawal removes the absence again and returns the shifts.
- On a termination or a cancelled work relationship, Quinyx receives the last working day or the future employee disappears from scheduling.
What to watch for with Oracle HCM Cloud and Quinyx
- Oracle records normal working hours with a frequency, per week or per month. Quinyx calculates agreements in hours per week. If an assignment in Oracle has hours per month, KoppelHet converts them to weekly hours using a rule we agree at the start, so the part-time factor in scheduling is right.
- Besides the employee's normal hours, Oracle also holds the standard working hours of a full working week. Quinyx needs exactly those two values in an agreement. KoppelHet takes the standard hours as the full working week and the normal hours as contract hours, without its own assumptions about what full-time is.
- An employee can have several assignments in Oracle, with one marked as primary. Quinyx allows an employee to hold several roles at the same time. KoppelHet sets the primary assignment as home unit and gives a role in that unit for each other assignment, so the employee can be scheduled in both places.
- Oracle reports a cancelled work relationship separately, for example when a candidate declines the offer or does not show up on the first day. Such an employee may already be scheduled in Quinyx for the coming weeks. KoppelHet ends the role and reports the planned shifts to the planner, so they are filled again.
- For an absence Oracle holds a separate duration for the first and the last day, for example half a day at the start. Quinyx books partial absence with a percentage, but refuses a percentage over the whole shift when the split per day is chosen. KoppelHet therefore picks the split per shift for half days and per day for full days.
- When an employee withdraws an absence in Oracle, it gets the status withdrawn there. KoppelHet removes the absence in Quinyx and asks Quinyx to give the original shifts back to the employee, so no gap appears in the schedule.
- Oracle also allows absence to be approved retroactively. If it falls in a period that Quinyx has already transferred to payroll, Quinyx refuses the absence with no way to override it. KoppelHet reports such a case to the planner with the period, so it is reopened deliberately or corrected in the next period.
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 clocked hours from Quinyx go back to Oracle?
Not in this integration. Hours to Oracle Payroll or a local payroll can be added later as an extension.
What if an Oracle location has no unit in Quinyx?
Then the employee is not created and an alert appears in the platform. The table is extended, after which the next round creates the employee.
Does this also work for contingent workers in Oracle?
Yes, Oracle publishes feeds for employees, contingent workers and pending workers. Per type we choose whether they are scheduled in Quinyx.
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 newhire (including future hires), empassignment, termination and cancelworkrelship, and the REST resource workers with the children workRelationships and assignments (NormalHours, Frequency, StandardWorkingHours, StandardFrequency, LocationCode, PrimaryAssignmentFlag, AssignmentCategory, EffectiveStartDate). Absence through GET /hcmRestApi/resources/11.13.18.05/absences with absenceStatusCd, approvalStatusCd, startDateDuration, endDateDuration, unitOfMeasure and lastUpdateDate.
- To Quinyx through the Employees API v3 (POST /hr/v3/employees) and /hr/v3/role-assignments with startDate and endDate; agreements through wsdlUpdateAgreementsV2. Absence through the v2 Absences API, POST /v2/schedule/groups/{groupId}/absences or /absences/part-time (absenceRate, absenceRateDirection, splitType Day or Shift; Day with WHOLE_SHIFT is refused). Deletion with reassignBackShifts; a locked period returns SALARY_PERIOD_LOCKED.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Quinyx | Notes |
|---|---|---|
PersonNumber | badgeNumber | |
names (FirstName, LastName, KnownAs) | personalInformation.firstName, lastName | |
Werk-e-mail | email | |
LocationCode van de primaire toewijzing | employment.homeGroupId | Through a table of Oracle locations to Quinyx units |
LocationCode van andere toewijzingen | Extra role-assignment in die unit | |
NormalHours en Frequency | Contracturen per week (agreement) | Monthly hours converted to weekly hours |
StandardWorkingHours en StandardFrequency | fullEmploymentHrs (agreement) | |
AssignmentCategory of WorkerCategory | extTemplateId (agreement-sjabloon) | |
Absence (approvalStatusCd goedgekeurd) | Absence, of part-time absence bij startDateDuration of endDateDuration |
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