This article describes how to report Employee ID in Recruiting and explains how Employee ID is visible in Candidate Profiles.
"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
Employee ID values are populated from EC when an external candidate is to be hired. It corresponds to the following standard field in the candidate profile template.
<field-definition id="employeeId" type="text" required="false" custom="false" anonymize="false" sensitive="false">
<field-label mime-type="text-plain"><![CDATA[EC Employee ID]]></field-label>
Employee ID values can only be seen for External Candidate Profiles of candidates with applications that are marked to be hired.
After the external candidate is hired, usually via Manage Pending Hire, and the Internal Candidate Profile is created by the External to Internal Candidate Conversion Job or imported or manually created, the Employee ID will no longer be seen in the Internal Candidate Profile.
a. How to Report the Employee ID in Recruiting?
You can report the employee ID from Ad Hoc Reports using Recruiting V2 > Candidate > User Sys ID. When this field is populated, it indicates that the candidate profile that you are reporting is internal.
b. How about the Employee ID field under Candidate, can we use the Employee ID field under the Candidate entity?
Yes, but it may be confusing. Just like in the UI, the Employee ID would only be populated for external Candidate Profiles that are to be hired and not for internal Candidate Profiles. Internal Candidate Profiles, would have the User Sys ID (userSysId) contain the Employee ID value and the actual Employee ID field would be blank.
You may confused this with other external Candidate Profiles that have no Employee ID values as they are not yet marked for hiring and thus not assigned an employee ID.
c. Why do some internal candidate profiles contain both employee ID and userSysId in the reports?
Employee ID and User Sys ID values would be populated for internal Candidate Profiles converted by the External to Internal Candidate Profile conversion job. Meanwhile, some internal Candidate Profiles are either imported or created manually, hence do not have the employee ID field populated, since their profiles did not come from an external Candidate Profile.
However, regardless of how the candidate profile is created, the userSysId will always be populated for true internal Candidate Profiles, while the employee ID field being populated is highly variable, depending on whether it is an external candidate profile that is to be hired or an internal candidate profile converted from an external candidate profile.
3191244 - What are the Available Reporting data for Recruiting in Recruiting V2 and ODATA API - Recruiting Management
2249476 - External to Internal Candidate Profile conversion - Recruiting Management
Employee ID, User Sys ID, employeeID, empId, userSysId, Report Employee ID, Report, Blank Employee ID, No Employee ID in Candidate Profile, Candidate Profile, Ad hoc, Recruiting V2, Recruiting Management, RCM , KBA , LOD-SF-RCM-REP , Reporting & Analytics, Data Imports & Exports , How To