Symptom
- The system assigns employee IDs sequentially during onboarding (for example, incrementing by 1).
- Onboarding processes for some candidates are put on hold or canceled.
- Concern whether the next hire receives the next sequential ID or if previously assigned IDs are reused.
- Expectation that once an employee ID is assigned, it is not reused, even if onboarding is paused or canceled.
- Confirmation requested on standard behavior and whether configuration exists to prevent ID reuse.
Environment
SAP SuccessFactors Onboarding
Reproducing the Issue
- Initiate onboarding for multiple candidates and observe sequential employee ID assignment.
- Put those onboarding processes on hold or cancel them.
- Start onboarding for a new candidate.
- Check whether the system assigns the next sequential ID or reuses previously assigned IDs.
Cause
The system is designed to assign employee IDs sequentially based on the defined sequence (nextValue); the sequence does not reset when onboarding is paused or canceled, and IDs already assigned are not reused.
Resolution
- Proceed with onboarding; the system will assign the next sequential employee ID based on the sequence’s nextValue.
- Do not reset or alter the sequence; IDs already assigned to earlier onboarding processes are not reused for other hires.
- If previously paused candidates are later hired, they retain their originally assigned IDs; other hires continue with subsequent IDs in sequence.
- There is no configuration to change this standard behavior or to add additional prevention mechanisms for ID reuse beyond the default design.
See Also
Keywords
employee id sequence, sequential id assignment, id reuse, onboarding id, recruiting integration, nextValue, userId sequence, pause onboarding, cancel onboarding, do not reuse ids, numbering range, sap successfactors onboarding, hire process, ec mph hire, onboarding sequence behavior , KBA , LOD-SF-OBX-EC , Integration EC - MPH, Hire , Problem
Product
SAP SuccessFactors Onboarding 2511
SAP Knowledge Base Article - Public