3757648 - empId field becomes Null in User Data File after external to internal profile conversion job run - Recruiting Management

"empId" field becomes Null in User Data File after external to internal profile conversion job run.

SAP SuccessFactors Recruiting Management

1. Hire a candidate into SF system
2. Verify that the empId field in the User Data File contains a value
3. Wait until the external to internal profile conversion job runs after the candidate's start date 
4. Observe that the empId field in the User Data File becomes null
5. Confirm that the empId field value is restored by the Employee Central HRIS Sync job

This behavior is expected.

When the following sm-mapping is configured in the Candidate Profile Template: <sm-mapping field-id="employeeId" map-to="empId" />, the system maps an empty value to the Employee Profile if the field is null or empty within Recruiting Management. 

The empId field can be updated via the HRIS sync between Employee Central and Employee Profile.

To prevent the reverse sync, remove the sm-mapping for the field. Note that this will also stop the normal sync for the field.

3033802 - Employee Profile fields display incorrect data in People Profile after New Hire/Rehire

conversion job, external to internal, employee ID, empId, UDF, blank , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem