Symptom
New hire not showing in manage pending hires after complete the Onboarding.
Environment
SAP SuccessFactors Onboarding 1.0
Cause
There are several causes why a newly hired candidate is missing in Manage Pending Hires, see below for the partial list:
- readyToHire flag in Onboarding 1.0 CandidateInfo object set to No
- managerID is populated with a deactivated or purged user
- User who is trying to locate the new hire in Manage Pending Hires is not the assigned managerID in Onboarding 1.0 CandidateInfo object
- User who is trying to locate the new hire in Manage Pending Hires does not include the assigned managerID as part of the target population in Manage Permission Roles (RBP)
- readyToHire flag in Super Admin is not set for the Onboarding process
- "OnboardingCandidateInfo" MDF object was customized and made secured
- "stepToMarkReadyToHire" field was not sent as part of SF integration calls (postphv, papeworkdone)
Resolution
For Live Customer(s)
See below solutions for the respective cause on why new hires are missing in Manage Pending Hires.
- Problem: readyToHire flag in OnboardingCandidateInfo object set to No
- Solution: Manually update the readyToHire flag of candidate with help of KBA 2419074; this is usually done if there is a time-out error which fails the post-PHV notification to be sent to BizX
- Problem: managerID is populated with a deactivated or purged user
- Solution: Manually update the managerID field with an active user with help of KBA 2419074
- Problem: User who is trying to locate the new hire in Manage Pending Hires is not the assigned managerID in OnboardingCandidateInfo object
- Solution: Manually update the managerID field with the correct assignee with help of KBA 2419074
- Problem: User who is trying to locate the new hire in Manage Pending Hires does not include the assigned managerID as part of the target population in Manage Permission Roles (RBP)
- Solution: Update the assigned permission role or permission groups in Admin Center to include the assigned managerID in the target population of the expected user who will hire in Manage Pending Hires with help of KBA 2333005
- Problem: "OnboardingCandidateInfo" MDF object was customized and made secured, but permissioning afterwards was not done.
- Solution: If "OnboardingCandidateInfo" object is made secured in the configure object definition tool, than you also have to go into RBP and make sure Role based permissions are set on the "OnboardingCandidateInfo". (new object permission can be found in Miscellaneous permissions section).
For Partners
For this case Super Admin (Onboarding Backend) access is needed
- Problem: readyToHire flag in Super Admin is not set for the Onboarding process
- Solution: Go to Super Admin > Find the process and set the flag to one step
-
Problem: "stepToMarkReadyToHire" field was not sent as part of SF integration calls (postphv, papeworkdone)
Solution: Go to superadmin -> Account -> Import/Export settings -> Debug Instance Specific Configuration then look for xml.processes file and ensure that stepToMarkReadyToHire has value. If readytohire flag is already set in the Processes (SuperAdmin) and if there is empty value of stepToMarkReadyToHire in the xml, then re-update the Process, this will put value in the xml file.
Keywords
Manage, Pending Hires, Ready, Hire, Missing, OCI, OnboardingCandidateInfo, Paperwork, Inactive, Manager, Candidate, MPH, Hire, Onboarding, Onb, Obd, readytohire, Flag, Step , KBA , LOD-SF-OBD-INT , Integrations with Onboarding , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , Problem