- 7 Posts
- 799 Views
We are curious as to what our peers in the community are doing for Employees that are hired into the system (and assigned an Empl ID), yet don't start. Either they are no-shows on the start day, or notify us of their change of mind just before they are set to start. We had been deleting the IDs, but there are some downstream system issues that we are working through, so hopefully seeing what some of you are doing could steer us in a better direction. Thanks in advance.
@shama-sivalingam We insert a term row on the same date as the hire date. This has caused no downstream impacts for us.
@shama-sivalingam We utilize the ID Delete delivered functionality. While there are some downstream system impacts, we have an e-mail distribution that notifies the affected areas.
@shama-sivalingam We are also dealing with the same issue. We had been deleting them but then the downstream folks (like IT) who look up the person can't find them. So, we came up with an action reason of DNS for Did not start but what I don't like about that is putting the term row on them makes them look as if they did work for us for 1 day, which is inaccurate, of course. We've not come up with anything better as of yet.
After verifying their start date should not be changed, a termination row is added in Job Data with the same effective date as the hire row, with an Action of termination and Reason of "no-show". This provides a record that an offer was made but the employee did not show up.
@shama-sivalingam We have the same issue and have also been deleting the IDs. Where applicable, downstream data consumers are manually notified in this case.
@shama-sivalingam We have the same issue and are also deleting EMPLIDs, which are causing downstream issue. I am also curious how others are handling this? Thank you.