HR to ITSM
SAP SuccessFactors to Ivanti integration: employees from Employee Central and service requests for joiners and leavers
With an integration between SAP SuccessFactors and Ivanti Neurons for ITSM, every employee from Employee Central is an employee in Ivanti, with department, location and manager, and KoppelHet submits a service request from your Ivanti template for every hire or departure. A hire with a start date far ahead also reaches IT in time, because KoppelHet deliberately reads SuccessFactors on future dates as well.
What the integration does
Organisations with SuccessFactors Employee Central and Ivanti as service desk often only get new employees into Ivanti once they have started. A service request for laptop and accounts can only be submitted once the employee exists, so IT hears about it too late or through an email from the manager.
- HR records a hire in Employee Central, with a start date in the future.
- KoppelHet reads Employee Central with a date range far into the future and sees the hire straight away.
- The new employee is added as an employee in Ivanti, with department, location and manager.
- KoppelHet submits the onboarding request on behalf of that employee, with the time zone of their work location.
- A termination produces an offboarding request; after the end date the employee is set to inactive.
What to watch for with SAP SuccessFactors and Ivanti
- Through OData SuccessFactors returns only today's state by default. A hire starting next month then stays invisible. KoppelHet queries Employee Central with a date range far into the future, so the employee is in Ivanti before the onboarding request is submitted.
- A service request in Ivanti requires the internal number of an existing employee and their location, and rejects the request if a required field is missing. KoppelHet therefore always writes the employee first and only then submits the request.
- Ivanti asks for the offset from UTC in minutes on every request. KoppelHet determines it from the employee's SuccessFactors location, so a start date in Singapore or São Paulo does not shift by a day.
- After a rehire SuccessFactors only shows the most recent termination. KoppelHet keeps track itself of which Ivanti employee belongs to which person, and sets a returning colleague back to active instead of creating a second employee.
- If a new employee does not show up, HR records a termination for which SuccessFactors does not return the related job record. KoppelHet then reads the job record separately, adds a note to the open onboarding request and sets the employee to inactive.
- Ivanti returns at most one hundred records per query. For the first comparison of all SuccessFactors employees with the employees in Ivanti, KoppelHet works in blocks of one hundred, and after that only with changes.
- SAP is ending sign-in to the SuccessFactors APIs with username and password. KoppelHet reads Employee Central with OAuth and read-only rights; we restrict Ivanti's fixed API key to the IP address of the KoppelHet platform.
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
Do we need SAP Integration Suite?
No. KoppelHet reads Employee Central directly through OData. An existing integration platform stays as it is.
What if a start date moves?
KoppelHet then sees the changed job record and adds a note with the new date to the open request.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- SuccessFactors Employee Central through the OData API (v2) with OAuth 2.0 (SAML bearer assertion) and a read-only role. PerPerson, PerPersonal, PerEmail, EmpEmployment and EmpJob with fromDate and toDate for future records; EmpEmploymentTermination with jobInfoNav for the event reason, or EmpJob directly for a no-show.
- Ivanti through the OData REST API on /api/odata/businessobject/employees (POST, PATCH on the RecID; $top at most 100). Service requests through POST /api/rest/ServiceRequest/new with subscriptionId, strUserId, strCustomerLocation, localOffset and parameters; all fields in the example are required. REST API key in its own key group, restricted by IP address.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in SAP SuccessFactors | Field in Ivanti | Notes |
|---|---|---|
PerPerson.personIdExternal | Personeelsnummer van de employee | One employee per person, also with multiple employments |
PerPersonal (voornaam, achternaam) | Voornaam en achternaam | |
PerEmail (zakelijk) | Primair e-mailadres | |
EmpJob.jobTitle | Functie | |
EmpJob.department (FODepartment) | Afdeling | |
EmpJob.location (FOLocation) | Locatie en localOffset | Offset from UTC in minutes per request |
EmpJob.managerId | Leidinggevende | |
EmpJob.eventReason | Keuze van het sjabloon | Through your own event reasons |
- Ivanti – Create a Service Request
- Ivanti – Get Business Object by Number of Records
- Ivanti – Using REST API Key
- Ivanti Neurons – connectoren
- SAP KBA 2920680 – OData: alle historische en toekomstige records
- SAP KBA 3153070 – EmpEmploymentTermination na herindiensttreding
- SAP KBA 3339090 – No-show en jobInfoNav
- SAP – Planned retirement of HTTP Basic Authentication
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