Workflow Substitutions - Force Validity End Date

Question

Is there a way I can configure Business Workplace Substitution Validity date from and to dates to fall within a specific range?  Can I prevent someone from using the default 12/31/9999 date when creating a substitute?

Answer 1

Hi Mark,
Well for starters a lot depends on:
a) What release/environment are you using?
b) What type of substitution - user to user or position to person are you using?
If you are using position to person, that's HR infotype A210 so you could use HR Structural Authorisations to only allow the infotype to be created e.g. up to the end of the current year.
If you are using user to user, its a bit harder.  In that case its based on table HRUS_D2, which only checks the end date is a valid date.
So you would really have to code in an additional check from wherever you are maintaining the data.
So now the question is, how do your users maintain substitutions? i.e. in which release/environment? using which maintenance tool?  Then you need to check out how that tool works.
E.g. you might be using the API SAP_WAPI_SUBSTITUTE_MAINTAIN or the table maintenance generated for HRUS_D2.
E.g. if its just the table maintenance view, you could add a table maintenance generation "event" with your additional check (go to the table maintenance generation and try menu Environment > Modification > Events).
Unfortunately the other maintenance tools use function modules - none of which currently offer any BADIs or user exits for adding additional checks.  So at this stage it would be a mod.  But a good thing to ask for in a development request perhaps.
Regards,
Jocelyn