DyLeave, absence and time
SAP SuccessFactors to Dyflexis integration: Employee Central employments as contracts in scheduling
With an integration between SAP SuccessFactors and Dyflexis, every employee from Employee Central arrives in Dyflexis automatically, with a contract per employment, the site, contract hours and the termination date. Changes HR records ahead of time are in scheduling on time, so planners work with the same data as HR.
What the integration does
Organisations that run HR in SAP SuccessFactors and plan their Dutch locations in Dyflexis add new employees to Dyflexis by hand per location. Someone temporarily working in another country is sometimes in it twice, and the planner only sees a change in hours from next month once the schedule is already done.
- HR records the hire or change in Employee Central, with an effective date.
- KoppelHet fetches the changed person, employment and job record, including records that only take effect later.
- In Dyflexis one employee arrives with a contract per employment, with site, contract type and hours.
- An administrator links the new employee once in Dyflexis; after that the integration follows Employee Central.
- On termination the end date is in Dyflexis, so the employee cannot be scheduled after it.
What to watch for with SAP SuccessFactors and Dyflexis
- In SuccessFactors one person can have several employments, for example during a temporary assignment to another country, each with its own user ID. Dyflexis has one employee with several contracts. KoppelHet uses the person ID for the employee and the user ID per employment for the contract, so nobody appears twice in scheduling.
- A plain request to SuccessFactors returns the job record valid today. An hours change or transfer from next month would then only come through on that day. KoppelHet also requests future records, so Dyflexis already has the new contract when the planner schedules ahead.
- Person, employment and job record are separate parts in SuccessFactors, each with its own change timestamp. Dyflexis processes an employee and their contracts as a whole. KoppelHet combines the changes per person into one delivery, so Dyflexis never receives half an employee.
- A Dyflexis contract needs contract hours and average working days per week. Employee Central has fields for both in the job record, but not every environment fills the working days. Where that field is empty, KoppelHet derives the days from the work schedule with a table maintained by scheduling.
- Locations and companies are master data with their own code in SuccessFactors. Dyflexis has sites with their own number and a free employer reference. KoppelHet translates location to site and passes the company as employer, so the hours can later go to payroll per Dutch entity.
- Dyflexis contract types indicate whether someone has a fixed base or works on call. SuccessFactors records this as employee class or contract type, with codes that differ per country. The translation table maps each code to the Dyflexis contract type, so an on-call worker does not enter the schedule with fixed hours.
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 SuccessFactors?
No. The hours from Dyflexis belong to Dutch payroll, not to Employee Central. An integration from Dyflexis to that payroll system can be added later as an extension.
Can time off from SuccessFactors reach scheduling?
The public Dyflexis API has no entry point for supplying time off. That is why time off stays outside this integration. If Dyflexis offers that entry point, we add it later.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Employee Central is read through the OData API (v2) with OAuth 2.0 (SAML bearer assertion) on lastModifiedDateTime, for PerPerson, PerPersonal, EmpEmployment and EmpJob. Future records of effective-dated entities with fromDate and toDate; without those parameters the API returns only the record valid today.
- Dyflexis is written through POST /api2/external-employees/{employeeReference} and POST /api2/external-employees/{employeeReference}/contracts (contractReference, office, type, start, end, hours, days). Both are upserts on the reference, so resending is safe; scope external_employees. Contract types with their fixedBase through GET /api2/contract-types.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Dyflexis | Notes |
|---|---|---|
personIdExternal | employeeReference | One Dyflexis employee per person |
userId (per dienstverband) | contractReference en personnelNumber | Each employment its own contract |
PerPersonal firstName, lastName | firstName, lastName | |
EmpEmployment startDate en endDate | employmentStart en employmentEnd | |
EmpJob location | office | Through a translation table |
EmpJob company | employerReferenceId | |
EmpJob standardHours | hours | |
EmpJob workingDaysPerWeek | days | |
EmpJob employeeClass | type (contracttype) | Through a translation table to Dyflexis contract types |
EmpJob costCenter | costCenter |
Related
Ashby → SAP SuccessFactors
Ashby to SAP SuccessFactors integration: hire as a new employee in Employee Central
Bullhorn → SAP SuccessFactors
Bullhorn to SAP SuccessFactors integration: placements as employees or contingent workers in Employee Central
Carerix → SAP SuccessFactors
Carerix to SAP SuccessFactors integration: successful placement as a new employee in Employee Central
Greenhouse → SAP SuccessFactors
Greenhouse to SAP SuccessFactors integration: a hire as a new employee in Employee Central