Hello -
Anytime you are changing and of the STAT fields on infotype 0000, you will need an individual action. For example, you could not combine a leave action that changes someone to inactive status with a leave action that leaves someone in active status .
So, technically, you could have one action that changes people to to active (or inactive), regardless of the reason. You could then use action reasons to identify whether the person is returning from leave, being rehired, or something else.
I agree with Ajay that these all appear to be events in the life of an employee. Therefore I would not recommend condensing them too much. You may be able to combine the "return from leave" since they will make a person active regardless of what their status was before.
A couple other things to consider: What are the reporting needs, and do you need to have different infotypes processed based on the action type?
If the infotypes processed are different based on the action type, it's easier to leave them as separate actions. That way you just have different infogroups. If you combined the actions, and need to have different infotypes processed, then you need to us dynamic actions, which can be a bit more difficult to configure/test.
..Danialle
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.