3627023 - [Onboarding] Internal hires are being selected as primary coming through as Concurrent Employment.

Internal hires are being selected as primary in the applications that are coming through to Manage Pending Recruits (MPR) as Concurrent.

Disclaimer:

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

SAP SF Onboarding 1.O

• Navigate to SAP SuccessFactors HCM and go to Onboarding>manage data>OnboardingCandidateInfo>filter the candidates and check the fields>Concurrent Employment and is primary.
  
  
• Navigate to SAP SuccessFactors HCM and go to Onboarding>Manage Pending Recruits (MPR)>filter the candidates and check the fields>Concurrent Employment.

• In the case of an internal hire, keys from the old record are transferred to the new record. The primary employment is initiated from RCM, and the concurrent user ID is copied from the previous record, which was created earlier. 
  
  
• This process occurs only when there is an internal hire and the older record has a populated concurrent user ID key. 

• This issue can be avoided by creating the Rule (as shown in ConcurrentUserIdSaveRule.png) and associating it with the "OnSave" event of the OCI object through the "Configure Object Definition" option.
  
  This way, even if a user ID is passed in the post PHV call, it will not be considered.

Onboarding ,OnboardingCandidateInfo,Concurrent Employment is primary, ConcurrentUserIdSaveRule, Internal hire employment, Concurrent Employment. , KBA , LOD-SF-OBD-SCR , Software Changes, Services, Provisioning etc. , Problem