Symptom
How to update OnboardingCandidateInfo, below are the common triggers why it needs to be update
- Hiring Manager is changed for respective candidate
- A hiring manager left the company
- Changing of Information
- A candidate was recently restored in Onboarding 1.0
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Onboarding
Resolution
Export OnboardingCandidateInfo
- Navigate to Admin Center > Import and Export Data
- Choose the action to perform (Export Data)
- Select Generic Object OnboardingCandidateInfo and Select all data records as No for a specific user(s)
- Click the Export Button
- To download the file, navigate to Admin Center > Monitor Job
- Open the downloaded file & update the CSV file with all of the following:
- fName
- lName
- hrManagerId
- jobReqId
- candidateId
- applicantId
- hireDate
- Kmsuserid (HRDataId)
- Save the file as CSV
Note:
- Use the correct date format. See KB article 2694367
- managerId and hrManagerId, please use 'User ID' and both should be an active user in SAP SuccessFactors HXM
- Use Notepad++ or Windows Notepad when making changes to values. Why?
- MS Excel may change dates into the format used by your PC (Windows or Apple)
- For USERID (Candidate's, HRManager, HiringManager), Excel will drop leading zero's in a prefix
- If using Excel, be certain to save the file in the correct format of the date and other fields
Import OnboardingCandidateInfo
- Navigate to Admin Center > Import and Export Data
- Select the action to perform (Import Data) and click CSV tab
- Select Generic Object OnboardingCandidateInfo
- Choose the file in the source destination
- Confirm all other attributes
- Click the Import button
Confirm Changes OnboardingCandidateInfo
- Navigate to Admin Center > Manage Data
- Use search and select OnboardingCandidateInfo and look for the candidate
- Verify the information reflects the update
Note:
- Updating OCI manually is not intended functionality. If you need to change the Hire date, then it should be triggered and propagated from an Onboarding 1.0 process flow.
- Once Onboarding process is finished, after update OCI this new data will not synchronize with data in Super Admin due there is no integration anymore. This new data will be only reference to the candidate in MPH for example, change of manager.
See Also
KBA Article 2694367 -OnboardingCandidateInfo Import Fails Because of an Invalid Date Format in Onboarding 1.0
Keywords
OCI, Manage, Data, MDF, Import, Export, OnboardingCandidateInfo, Monitor, Jobs, Manager, MPH, Candidate, Info, Change, Update, Onboarding , KBA , #sfobdintegrationbizx , #sfobdhowto , #sfobdoci , #sfobdneedtopublished , LOD-SF-OBD-INT , Integrations with Onboarding , How To