SAP SuccessFactors logoX4

HR to ITSM

SAP SuccessFactors to Xurrent integration: people, organisations and sites from Employee Central in Xurrent (4me)

With an integration between SAP SuccessFactors and Xurrent (formerly 4me), every employee from Employee Central is a person in Xurrent, with organisation, site, job title and manager, and KoppelHet creates a request from your Xurrent template for every hire, job change or termination. Every person carries the SuccessFactors person ID as source key, so a new work address never creates a second person.

What the integration does

Organisations with SuccessFactors Employee Central as HR source and Xurrent as service management platform often load people with a periodic import. Between two imports new colleagues are missing, and a changed work address sometimes creates a second person, because Xurrent uses the address as key.

  1. HR records a hire in Employee Central.
  2. KoppelHet makes sure company, department and work location exist as organisation and site in Xurrent.
  3. The employee is added as a person in Xurrent, with the person ID as source key.
  4. The onboarding template produces a request for the new colleague, submitted on behalf of the manager.
  5. On a termination an offboarding request follows; only once it is completed is the person disabled.
SAP SuccessFactors → KoppelHet → Xurrent (4me)SOURCESAP SuccessFactorsTARGETXurrent (4me)Xurrent (4me)KoppelHetmapping · logging · monitoringSAP SuccessFactors → KoppelHet → Xurrent (4me)SOURCESAP SuccessFactorsTARGETXurrent (4me)Xurrent (4me)KoppelHetmapping · logging · monitoring
Out: Person with work email, employee number, job title and language · Organisations per company and department · Sites per work location · Request from a template on hire, job change and termination

What to watch for with SAP SuccessFactors and Xurrent (4me)

  • Xurrent uses the work address as unique key and login. If the address changes in SuccessFactors, KoppelHet looks up the person by the person ID in the source key and only changes the address.
  • Only a user with the Account Administrator role may set the source key in Xurrent. The integration user gets that role, and otherwise only what is needed to create requests; in SuccessFactors it only reads.
  • Xurrent stores a person's language in at most five characters. SuccessFactors provides a code like nl_NL; KoppelHet converts it to the Xurrent notation, so notifications and the portal appear in the employee's language.
  • A job title in Xurrent may have at most 80 characters. If a title in SuccessFactors is longer, KoppelHet does not just cut it off, but reports it to HR, so no truncated titles end up in the service desk.
  • After a rehire SuccessFactors only shows the most recent termination. Because Xurrent allows the work address only once, KoppelHet re-enables the existing person instead of creating a new one.
  • Xurrent does not allow new records to be attached to a disabled person. After a termination in Employee Central the person therefore stays active until the offboarding request is closed; only then does KoppelHet set the disabled flag.
  • Archiving or deleting a person in Xurrent requires the Account or Directory Administrator role. KoppelHet does neither; disabling is enough and the history stays complete.

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, architecture and compliance

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.

Price indication · Basic

Leave your work email and you see the price indication right away.

We only use your address to follow up on your question about this integration.

Frequently asked questions

Do employees from all countries end up in Xurrent?

Only the companies that belong to your Xurrent environment. Managers from outside are added as people, without requests.

What if a start date moves?

KoppelHet then updates the desired date on the open request and adds a note.

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 and a read-only role. PerPerson, PerEmail, User (defaultLocale), EmpEmployment, EmpJob with fromDate and toDate for future records, EmpEmploymentTermination, FOCompany, FODepartment and FOLocation.
  • Xurrent through the REST API with an OAuth token and the X-Xurrent-Account header. /people with primary_email (required, at most 128, unique), employeeID, job_title (at most 80), organization, site, manager, locale (at most 5), disabled, source and sourceID; /organizations and /sites; requests through POST /requests with requested_for, requested_by and template. Rate limiting per user with 429 and retry-after.

Which fields are transferred

The key fields. The full mapping is agreed per customer.

Field in SAP SuccessFactorsField in Xurrent (4me)Notes
PerPerson.personIdExternalsource en sourceIDOnly an Account Administrator may set this
PerEmail (zakelijk)primary_emailUnique in the account and also the login
EmpEmployment.userIdemployeeID
EmpJob.jobTitlejob_titleAt most 80 characters
EmpJob.company en departmentorganization
EmpJob.location (FOLocation)site
EmpJob.managerIdmanager
User.defaultLocalelocaleAt most five characters

Related

Which systems do you want to connect?

Tell us which systems you use and what should happen automatically. Together we define the smallest working solution, with a clear design and a quote before building.