
Business Scenario
The expectation is that, throughout an employee's life cycle, rehiring will be the sole authorized event after termination. This implies that if termination occurs prior to a promotion or data modification, it will result in complications when integrating with the payroll system.
Currently, it is required to manually review the employee's Job Information to determine if any future dated records have been produced and to implement the necessary adjustments or deletions to finalize the action in the event of termination.
Requirements from multiple customers are as follows:
Solution Overview
To fulfill this requirement, one possible approach is to create a termination rule that makes sure that there are no future dated records in Job Info regarding the termination date. Understanding how termination action is handled in Employee Central is key to accomplishing this.
Configuration Details
Considering the system behavior mentioned before, we can create an OnSave rule within employment details to determine whether the termination record being generated in Job Info contains an end date of 31.12.9999 (indicating no future records) or if it does not match 31.12.9999 (indicating future records).
By implementing this simple rule, we can ensure that the new termination record is validated against any potential future records in the Job Info section.
Now, let's examine how this solution behaves in various scenarios:
Scenario 1: Termination with no future records in Job Info.
For this scenario we have an employee with only a hire record (01.01.2023), if we add a termination record on 04.01.2023 the end date for this new termination record will be 12.31.9999.
In this case the condition is not met (no future records) and no error message will be triggered.
Scenario 2: Termination with future records.
For this scenario we have an employee with two records, a hire record (01.01.2023) and a promotion (02.01.2024), if we add a termination record on 04.01.2023 the end date for this new termination record will be 01.31.2024, one day before the start date of the future promotion record.
In this case the condition is met (there are future records) and the error message will be triggered.
Scenario 3: Termination posterior to future records.
For this scenario we have an employee with two records, a hire record (01.01.2023) and a promotion (04.01.2023), if we add a termination record on 02.01.2024 the end date for this new termination record will be 12.31.9999.
In this case the condition is not met (no future records) and no error message will be triggered.
Additional notes:
Conclusions
Meeting specific requirements often leads to deep analysis of customer needs and good understanding of SuccessFactors solution behavior as well as the available tools, such as business rules. Sometimes, complex requirements can be addressed with simple solutions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
9 | |
7 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |