Afternoon all

Thought I'd share an unpleasant experience we had here at W-D a week or so ago, wherein we were attempting to terminate a rehired employee with the leaving reason 'R'.

The result was an error message to the effect that 'the person type usage of this type already exists at this date' - nice and cryptic....

Well after the customary pondering, investigating, casting of the rune stones, examining the entrails of a NAAFI pork pie etc this is evidently what happened:

1. Emp is terminated for the first time, with leaving reason 'R'. As a result, a person type usage of 'Retiree' is created from the date after the actual termination date.

2. Emp is rehired. 'Retiree' person type usage remains untouched.

3. Rehired emp is terminated with leaving reason 'R' once more. System sees existing 'Retiree' person type usage, and promptly spits its dummy out.

Interesingly, our military friends have changed the meaning of the 'R' leaving reason from the seeded 'Retirement Age' to 'Admin' or similar. What I don't understand is:
1. Why they would want to
2. Why the system let them change a seeded lookup meaning, albeit from an extensible lookup type

Just in case anyone else should stumble across this problem...