Symptom
This article explains the functionality of the "HiringNotCompleted" flag within the Onboarding logic, specifically focusing on the conditions under which this flag gets updated during various hiring stages. As well, including the Manage pending hires step, employee rehire scenarios and onboarding practices.
Environment
SAP SuccessFactors Onboarding
Resolution
- Definition of "HiringNotCompleted" Flag:
- The "HiringNotCompleted" flag is an internal system field that indicates the status of a candidate in the hiring process. It is set to true when the hiring process is incomplete and false when hiring process is complete.
- The "HiringNotCompleted" flag is an internal system field that indicates the status of a candidate in the hiring process. It is set to true when the hiring process is incomplete and false when hiring process is complete.
- Flag Update Timing:
- The flag is automatically updated only after the Manage Pending Hires step is completed.
- The flag is automatically updated only after the Manage Pending Hires step is completed.
- Initial User Flow:
- When a candidate is initiated but still in the Manage Pending Hires process without completion, the flag remains set to true.
- Once the Manage Pending Hires step is completed successfully, the flag is updated to false, indicating that the candidate has been hired.
- New hire, rehire with new employment and crossboarding scenarios:
- The same flag updating process applies for scenarios involving external or internal rehire and crossboarding.
- The same flag updating process applies for scenarios involving external or internal rehire and crossboarding.
- Rehire with old employment scenario:
- If an employee resigns (or terminated) and is then rehired (with old employment), the system treats them as an active employee, and during this time, the "HiringNotCompleted" flag is not verified for the previous records.
- It's recommended to use the OnboardingInfo object for these cases.
- The lifecycle of the OnboardingInfo object is maintained in Onboarding and depends on the different stages of the onboarding processes. It is automatically purged from the system at the end of its lifecycle, which can occur because of one of the following reasons:
-
Onboarding process for a candidate is canceled.
-
A no-show is triggered.
-
New hire is converted to an employee.
-
New hire data is purged.
-
The ONB2Process close job is completed.
-
See Also
Keywords
obx, onb, hiring, not, completed, flag, internal, system, hiring, process, ec, onboarding , KBA , LOD-SF-OBX-EC , Integration EC - MPH, Hire , How To