A candidate applied on a requisition and is then hired. When the internal profile of the candidate was created, the recruiter manually merged the candidates external and internal profiles – making the internal as active, and external as inactive.
Logs from the External to Internal Candidate Profile Conversion job still recognize these profiles for conversion, and throws an error message saying username:12345 already exists with active job Applications!
SuccessFactors Recruiting Management
The normal workflow is that when a candidate has applied to a job, and is then hired, the external to internal conversion scheduler should be the one to perform the conversion on the candidate's profile, wherein it will activate the candidate's internal profile while 'soft deleting' the external profile - which can be reactivated via the de-conversion process.
When doing a manual merge, it does not necessarily mean that the profile will already be excluded from the conversion. Since a manual merge has been performed, the external profile of the candidate will be deleted permanently. This is causing the error "Failed Conversions: XXXX - Internal Profile for matched username: XXXX already exists with active Job Applications!" since the job is still looking for the candidate's external profile, which is no longer available and retrievable.
The External to Internal Candidate Profile Conversion job will run only on new hires from the point the scheduled job is enabled; it is not retroactive to past hires. Existing duplicate external and internal Candidate Profiles are not affected when the conversion feature is enabled.
Hence, if the customer wants the error logs to be removed from the report, all they have to do is to disable and re-enable the job.
External to Internal Candidate Profile Conversion, Failed Conversions, Internal Profile for matched username: already exists with active Job Applications , KBA , LOD-SF-RCM-ADM , Admin Center, RBP, Permissions and Settings , How To