How to import Candidate Profile into the system using Legacy Data Migration under Provisioning
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
SAP SuccessFactors Recruiting Management - All Versions
Data Import is done via CSV file import. The import files must be hand-created by the Professional Services representative.
Best practices tips:
- You cannot update the uploaded records. Please make sure that .csv files contain all correct information before importing data to the system.
- Please review the following Knowledge Base Article regarding file encoding and please follow the best practices when working with .CSV files: 2320676
- Test the import with a small set of data and confirm that the date is properly imported before proceeding with the main import.
- File can contain 10.000 records at once.
- During the import jobs there should be no changes to the data performed in the user interface
- If you find any errors in the Provisioning - Monitor Job, you can verify the details of the error and try to import again with the errors fixed. A few commons error are:
- FTP transport failed to get data file from FTP server: (FTP Server) - The job was not able to find the file inside the server due to a mismatch with the name. Please, verify the file name and be sure the extension ".csv" are set correctly in both sides (Provisioning and SFTP server).
- Invalid field(s): The following fields-IDs are not declared in the Candidate Profile. Make sure the import file contain only valid fields from the CPT.
- Missing required field(s) : The following fields-ID are required inside the CPT, but were not declared within the import file. Make sure to declare all the mandatory fields, otherwise the system will be not able to create the Candidate Profile.
- Missing required field(s) : country: The field "country" will be required, even thought it's not required in the CPT.
Buliding the Job
- In Provisioning, go to Manage Schedule Jobs
- Create new Job
- Type the Job Name and select the Job Owner
- In the Job Type dropdown, select "Candidate Import"
- On Job Parameters, choose "Candidate Profile Information"
- Enter the SFTP server that the file will be hosted
- Fill the FTP Login and Password
- On the file path, you need to set where the file was storage inside the server. For e.g. "/files/employee_info" .
- In File Name, type as exactly the file name (With the extension ".csv).
- Define the Occurrence for the job and the Notification configuration
- Create Job.
- If the Job does not have recurrence, the job needs to be executed under Manage Schedule Jobs
After executing the Job, you can check in Monitor Jobs what were the results. If the job was executed successfully, you can click on "Details" and check the following scenario.
If after importing the candidate using Legacy Import and the import was executed fine, but the candidate is not available, please check this KBA: 2279481
NOTE: If the field-id "Resume" is required and an attachment should be uploaded, on the section "resume" inside the job, you must define the attachment name, for e.g. "resume.doc" inside the file and upload the attachment with the file in the same location. For e.g., if the file was upload in "/files/candidateimport", the attachment should be upload as well in "/files/candidateimport", otherwise the system will be not able to identify and upload the attachment.
Please find the Legacy Import template file attached to this KBA.
2582786 - Candidate profile import and resume parsing
2279481 - Candidate imported via Legacy Data Migration but is not visible in the system - RCM
2520582 - How to Import Candidate Background Elements
2320676 - Platform - File encoding and impact on import jobs. Tips & Tricks from Support
2341614 - Legacy Data Migration - Importing Candidates, Requisitions, Applications via Provisioning - Recruiting Management
Candidate Import; Import Candidate; Legacy Import; , KBA , LOD-SF-RCM-CAP , Candidate Profiles , How To