Creation of Requisition Request through MSS

The document contents SPRO configuration steps, Adobe Interactive form, BADI implementation and Workflow to customize standard functionality of 'Create Requisition through MSS' application to suit Customer Requirement.

Screen shots of the process are as follows

These screen shots are different from the standard application. 

* Create New Requisition Request link.

Click of the above mentioned link.

* Select Parameters and Default Values

The below screen is restricted only to Positions but in standard functionality request can be created based on 'Position', 'Job', 'Previous Request', 'Start without Reference'.

* Last column (Vacant) has been customized to meet the customer requirement.

This can be achieved by changing the Function module attached to column content in 'Define Column' node for any column.

* Next Step is to fill the form.

On completion of the form, click on 'Review' button. Request can be created only for 'Vacant' positions. This validation has been implemented in BADI 'HRWPC_EREC_RECRUITER'. The respective Interactive form is a custom one.

Below screen is a continuation of above form.

* Click on 'Send' button and will get a success message as follow.

The 'Send' button will create a Request for Requisition in E-Recruitment system by triggering workflow. This workflow has been customized not only to create a Requisition but also a Posting of the job in E-recruitment system.

Customization steps

1) Create Scenario

First step is to define scenario where you need to specify the Notification Type and Interactive form. To do this use transaction 'QISRSCENARIO'.

Best practice is to copy the existing scenario e.g. 'SRQ1' to 'ZRR1' scenario.

Note: - Authorization requires for Notification 82 is 'SAP_CA_NO_NOTIF_ISR'. Also if not available add transaction code 'IQS1' to the list.

By clicking on 'Additional Data for Scenario' you can specify the workflow which will get triggered for this scenario. You can specify the column contents for 'Additional Columns' by providing field names from characteristics of the scenario.

Note:- Workflow will not get trigger by mentioning in this configuration. But it will trigger based on the event attached to the workflow.

Click on 'Additional Data for Scenario' button and add New Entry

Add 'Characteristics' to scenario; go back to scenario screen and click on 'Characteristics'.
List of new and existing entries 

Below screenshot explains how to add characteristic to scenario. If the field is a dropdown then it should have key and label placeholder.

2) Configuration of Recruitment node.

SPRO -> Integration with Other mySAP.com Components -> Business Packages / Functional Packages -> Manager Self-Service (mySAP ERP) -> Recruitment

a) Define Manager Groupings

Which Manager Grouping will be selected is written by implementing BADI 'HRWPC_EREC_MGR_GRP'.

b) Define Form Types for Staff Requisitions

c) Group Form Types

Specify the Request Form Type, Manager Grouping we have created just now and the ISR Scenario which will be used for it.

d) Define Attributes for Request Scenarios

There are four options to select Recruiter based on selected 'Recruiter Logic Type'

1)     Manual entry by the Manager
2)     Vacancy Table (T750X)
3)     Org assignment infotype (IT0001)
4)     Custom Logic (Business Add-In)

We have kept option 1. Logic for selecting Recruiter Id has been written in BADI implementation 'HRWPC_EREC_RECRUITER'.

e) Assign Start Mode

Here we define which all options will be available to create Requisition.

f) Assign E-recruiting System Name

Note: - The RFC destination user should be assigned to PERNR.

3) Hiding Column from Requisition Request Screen

Click on 'Define Column Groups' node

Select 'Check Standard assignment of Column to Column Group' option
Hide 'Valid to' column from 'Create Requisition Form' screen.      

 4) Adobe Interactive form

The form used in respected scenario is a customized one.
How to create and assign customized Adobe Interactive Form?
Transaction 'SFP'

Copy form 'ISR_FORM_SRQ1' and related interface 'ISR_IF_SRQ1' to 'z' form and interface. All our customization is similar to scenario 'SRQ1' so most of the functionality is copied from this scenario.

Add all the fields to interface which you have added to characteristic of your scenario and assign type as 'QISR_TAB_TYPE'.

Adding Interface variables to Form context
Open form and go to Context tab. Drag and drop all the desired fields to the context of a form. By this way all the context variable will be available on form layout for binding and for further processing of data.

5) BADI Implementation (Transaction SE19)

We have implemented two BADI respectively 'HRWPC_EREC_MGR_GRP' and 'HRWPC_EREC_RECRUITER'.

HRWPC_EREC_MGR_GRP
This BADI decides which Manager Group will be used while creating the Request for Requisition.

HRWPC_EREC_RECRUITER
With this BADI implementation we have initialized and validated form fields, populated drop downs for Recruiter or Currency fields.

6) Workflow

'WS16900009' and 'WS16900010' workflow replaces the old workflows 'WS12200021' and 'WS12200022'

Please refer note '949625'.

We have copied and customized the workflows to suit customer requirements. 

This workflow gets triggered for event