SAP Knowledge Base Article - Public

3761162 - Pre-Onboarding Rehire Verification not triggered if preferred name is mapped to application first / last name - Onboarding

Symptom

Pre-Onboarding Rehire Verification not triggered post initiation from Recruiting, there is a third-party integration layer for Candidate and Application creation.

Environment

SAP SuccessFactors Onboarding

Reproducing the Issue

  1. Use an external integration that maps preferred first / last name into the Application’s standard firstName / lastName fields.
  2. Initiate Onboarding from Recruiting.
  3. Pre‑Onboarding Rehire Verification did not trigger.

Cause

Inconsistent data mapping in the Application payload, preferred names are passed in place of legal names for the standard firstName/lastName fields.

Resolution

  1. The Application payload should be updated to align with the Candidate payload by passing legal names in the standard fields.
  2. To assist further with custom configuration issues, consulting resources might be needed.

See Also

KBA 2706322 - What is Support – What is Consulting: Cloud Solutions

Keywords

rehire verification not triggered, pre‑onboarding, preferred name mapping, legal name mapping, application payload, recruiting to onboarding, name mismatch, onboarding dashboard rehire, rehire check not running, candidate application fields, firstName lastName mapping, external integration mapping, snapshot behavior , KBA , LOD-SF-OBX-RHM , Rehire Mechanism , LOD-SF-RCM-ONB , Onboarding integration , Problem

Product

SAP SuccessFactors Onboarding