A lot of you would be aware that with HR Renewal 1.0 feature pack 1, new substitution functionality is available in MSS. A very good overview of all the features offered with this functionality can be found here. Important thing to note is that substitution is now enabled not only for workflow based approvals but also for non-workflow based approvals (like - CATS approval) and MSS applications (like – homepage, team page, process and form applications etc.). Also a new Substitution Overview page is available which makes it easy for a substitute to work on behalf of substituting manager. It offers the view of team of the substituting manager and the delegated applications that could be launched on behalf.
In this blog I would like to outline all the steps needed to configure/setup the substitution functionality in MSS. I also hope that it helps comprehend all the aspects of substitution functionality in MSS.
First Things First
In order to use the this functionality in MSS, some of the basic things that you need to carry out are as follows:
Configurations for setting up Substitution
All the configuration steps for setting up Substitution functionality can be found under following path in IMG:
IMG -> Personnel Management -> Manager Self-Service(WDA) -> Substitution
The substitution profiles defined here are available to the user while creating a substitution rule in "Manage Substitution Rules" application as seen in screenshot below. So when a user creates a substitution rule to another user with a specific substitution profile, all the workflow tasks/MSS applications classified using corresponding task classes get delegated to the substitute.
2. In the next step configure a repository of MSS applications which could be delegated in your organization. This is done in launchpad customizing under role MSS and instance SUBSTITUTION. Classify these MSS application by assigning task classes as defined in above step. Example – If the “Process Browser” application in process and forms area is one of the applications which could be delegated then put this as part of this Launchpad. Set the parameter “SUBST_CLASSIFICATION” to appropriate task class defined before.
Note –
3. Activate the default implementation of BAdI HRMSS_SUBSTITUTION. The "Substitution Overview" application calls this BAdI to get the active substitution rules and list of applications substituted by user. You can read the IMG documentation and BAdI documentation to know more about this step.
4. Optionally implement and activate BAdI WF_SUBSTITUTE. This BAdI is called when substitution rules are created or deleted by user in the "Manage Substitution Rules" application. In this BAdI implementation,for example, you could write code for sending email notifications.
5. Last but not the least, define authorizations with regard to substitution. You can consider assigning the light weight MSS role SAP_MANAGER_MSS_SUBST_SR_NWBC to substitute users who are not managers. Define appropriate values for authorization objects in this role. Additionally if you use structural authorization then a new structural profile could be created for substitute users. The profile could be configured with function module HRMSS_SUBST_GET_ORG_ASSIGNMENT which reads the active substitution rules and determines the root organization units.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
28 | |
6 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |