This document outlines the Push elements of the SAP SuccessFactors ATS integration. Please see the table below detailing the data synced between the SAP SuccessFactors → Beamery CRM.
|
Data Type |
SFSF → BM | BM → SFSF |
|---|---|---|
| Vacancies | |
|
| Candidates | |
|
| Applications | |
|
| Attachments | |
|
The only data entity Beamery currently pushes is "Candidates".
| Beamery Field Reference | Beamery Field Name | SuccessFactors Field Reference | SuccessFactors Field Name | SuccessFactors Field type |
|---|---|---|---|---|
|
contacts.education.degree |
Degree |
Candidate.education. CandidateBackground_ Education.degreeNav. PicklistOption.localeLabel |
Degree | Pick list custom field |
|
contacts.education.endDate |
End date |
Candidate.education.CandidateBackground_ Education.endDate |
End Date |
Pick list custom field |
| contacts.education.major | Field of Study |
Candidate.education.CandidateBackground_Education. majorNav.PicklistOption.localeLabel |
Major | Pick list custom field |
| contacts.education.organisationName | School |
Candidate.education.CandidateBackground_ Education.school |
School | Pick list custom field |
| contacts.education.startDate | Start Date |
Candidate.education.CandidateBackground_ Education.startDate |
Start Date | Pick list custom field |
|
contact.PrimaryEmail (Mandetory) |
Primary Email | Candidate.contactEmail | Primary Email | Standard (Mandatory field) |
| contacts.experience.endDate | End Date |
Candidate.outsideWorkExperience.CandidateBackground_ OutsideWorkExperience.endDate |
End Date | Pick list custom field |
| contacts.experience.organisationName | Company |
Candidate.outsideWorkExperience.CandidateBackground_ OutsideWorkExperience.presentEmployer |
Company Name | Pick list custom field |
| contacts.experience.role | Role |
Candidate.outsideWorkExperience.CandidateBackground_ OutsideWorkExperience.startTitle |
Title | Pick list custom field |
| contacts.experience.startDate | Start Date |
Candidate.outsideWorkExperience.CandidateBackground_ OutsideWorkExperience.startDate |
Start Date | Pick list custom field |
| contact.firstName | First Name | Candidate.firstName | First Name | Standard |
| contact.integrations.successfactors.id | ATS ID | Candidate.candidateID | Candidate ID | Standard |
| contact.lastName | Last Name | Candidate.lastName | Last Name | Standard |
| contact.location.StreetAddress (see note) | Address | Candidate.Address | Address | Standard |
| contact.location.postalCode | Post Code | Candidate.zip | Zip Code | Standard |
|
contact.PrimaryPhoneNumber (Mandetory) |
Primary Phone | Candidate.cellPhone | Cell Phone | Standard |
| Global.Tag | Global Tag | tag | Candidate Tag | Standard |
Contact.Location.StreetAddress is a new field in Beamery, so before we can enable the bidirectional integration, we'll need to perform a historical data pull to populate this field from SuccessFactors.
Creation or Update of Candidate on Push
Whether we create or update a candidate will depend on whether we have an ATS ID for the contact in question.
If no ATS ID, then SuccessFactors will create a new Candidate . If there is an ATS ID, and it matches and existing ATS ID, then that contact will be updated.
If no ATS ID but there is a matching email address, then that contact will be updated.
Created Contacts
We are unable to create an ATS ID ourselves, so when we push a candidate to SuccessFactors, SuccessFactors will generate an ATS ID.
We can then receive that ATS ID via two ways:
immediately via a feedback in the UI from SuccessFactors
on the next Candidate Pull (whenever that is next scheduled).
Push Triggers
The current implementation of Candidate Push has only one way of triggering - via Recipes in Beamery CRM.
Users can create Recipes with specific parameters to determine when to Push a Candidate. Every time those parameters are met, then the PUSH will be triggered.
i.e. The following Recipe parameters:
- When a Contact is added to a Pool in Beamery
- “add to SuccessFactors”
This would result in contacts being PUSHED to SuccessFactors when/if a contact is added to a pool.
However, if nothing has changed to that Candidate record, but the Recipe parameters are met, then we will not trigger a PUSH.
A key difference here to our Workday integration, is that we do not PUSH updates to SuccessFactors. The Recipe has to be met for any changes to be pushed.