DyLeave, absence and time
Oracle HCM to Dyflexis integration: assignments as contracts in scheduling, also ahead of time
With an integration between Oracle HCM Cloud and Dyflexis, the workers of the sites that schedule in Dyflexis come from Oracle into scheduling automatically, with a contract per assignment, the right site and the contract hours per week. A hire or transfer that HR records ahead of time in Oracle is already in Dyflexis before it takes effect.
What the integration does
Organisations that use Oracle HCM Cloud worldwide and have their Dutch or Belgian sites schedule in Dyflexis add new workers to Dyflexis by hand. A transfer to another site or an hours change only reaches the planner if HR remembers to pass it on.
- HR records a hire or change in Oracle, possibly with a future date.
- KoppelHet reads the feed and fetches the worker with work relationships and assignments.
- Only assignments at locations that schedule in Dyflexis go through, each as its own contract.
- An administrator links a new worker to a Dyflexis employee the first time.
- On termination or transfer the contract closes on the date from Oracle.
What to watch for with Oracle HCM Cloud and Dyflexis
- Oracle reports a new worker as soon as HR records the hire with a future date. KoppelHet then puts the contract into Dyflexis straight away with that start date, so the planner can schedule the new colleague weeks ahead.
- Oracle has a separate feed for a cancelled work relationship, for example when someone drops out before the start. KoppelHet then ends the prepared contract in Dyflexis, so no shifts remain for someone who never arrives.
- An assignment in Oracle records working hours with a frequency, per week or per month. Dyflexis works in hours per week. KoppelHet converts monthly hours to a week, so a contract of 130 hours a month does not enter scheduling as 130 hours a week.
- A Dyflexis contract also needs the average number of days per week, and an Oracle assignment has no such field. KoppelHet derives it from the work pattern, or from a table per contract type maintained by scheduling.
- On a transfer to another legal employer Oracle creates a new work relationship. In Dyflexis it stays the same employee; KoppelHet closes the old contract and opens a new one with the new employer, so the hours later reach the right payroll.
- Without a date header Oracle only returns today's state. KoppelHet requests assignments with a date range, so an hours change from next month is already in Dyflexis as a follow-on contract and the planner does not plan ahead with the old number of hours.
- Oracle also sends the feeds for contingent workers and pending workers. Whether contingent workers enter Dyflexis is up to you; KoppelHet looks at the worker type and only includes the agreed types.
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 worked hours go back to Oracle?
Not in this integration. Hours usually go to local payroll; that is a separate flow that can be added later as an extension.
What if someone has two assignments?
Then the employee gets two contracts in Dyflexis, each at its own site. Both sites can schedule them.
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 (also for a future date), empassignment, termination and cancelworkrelship, and then the workers resource with the children names, workRelationships and assignments (AssignmentNumber, LocationCode, NormalHours, Frequency, StandardWorkingHours, FullPartTime, AssignmentCategory, PrimaryAssignmentFlag, EffectiveStartDate, EffectiveEndDate). Future records with the Effective-Of header (RangeMode, RangeStartDate, RangeEndDate).
- To Dyflexis through POST /api2/external-employees/{employeeReference} and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days); upserts with scope external_employees. Sites and contract types through GET /api2/offices and GET /api2/contract-types.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Dyflexis | Notes |
|---|---|---|
PersonNumber | employeeReference en personnelNumber | |
names (FirstName, LastName, KnownAs) | firstName, lastNamePrefix, lastName | |
AssignmentNumber | contractReference | Each assignment its own contract |
LocationCode | office | Through a translation table |
NormalHours en Frequency | hours (per week) | Month converted to week |
AssignmentCategory of FullPartTime | type | Through a table to Dyflexis contract types |
Werkpatroon of tabel | days | |
Legal employer van de werkrelatie | employerReferenceId | |
EffectiveStartDate en einddatum | start en end |
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