Show TOC

Further Changes to Recruitment

Change system parameters in customizing

Change system parameters in customizing

1. New screen headers in standard system
As of Release 3.0 the standard system contains a revised version of the screen headers. The screen headers are stored in view "Screen Header Definition" (T588J). Check how much of the new standard you want to adopt. For further information please refer to Change screen headers.
2. Enhancement of dynamic events
View "Dynamic Events" (View V_T588Z) contains functional enhancements for infotypes 4000, Applicant Events , 4001, Applications and 4002, Vacancy Assignment.
If you change the applicant status using the event "Put applicant on hold" or "Reject applicant", the system automatically changes the status in all the applicant's vacancy assignments (infotype 4002) to that now recorded in infotype 4000, Applicant Events.
Check if you want to adopt this functionality.
If up to now you have used the standard settings for the dynamic event for the infotypes (4NNN), you can Transfer entries. Otherwise you should compare your entries with the standard settings manually.
3. Change to features PRELR and PRELI
A personnel number is saved at various points in the Recruitment system. For example, if the candidate is an internal applicant, his/ her personnel number can be recorded, or the person responsible for an action is recorded along with his/her personnel number in the action. Features PRELR and PRELI enable you to determine whether a personnel number entered in the Recruitment system is to be checked against the employee database. As of Release 3.0 these checks are no longer carried out according to the applicant's organizational assignments, and as of 3.0 you can determine for the whole system whether checks or not checks are to be carried out at all. For this reason the following fields are no longer to be used for checks in features PRELR and PRELI:
If you have modified the feature, please check whether you are using any of the above fields for checks. You may have to Change features.
4. New feature STATU
Feature STATU controls a change to the vacancy assignment status is compatible with the current overall status.
Admissibility of overall status and vacancy assignment status

Further notes

The Recruitment tables are connected to general view maintenance (SM30). The names of the views are listed below:

Table View Title

--------------------------------------------------------------------

T750A V_750A_B Vacancy published in advertisement
T750B V_T750B Advertisement
T750C V_T750C Recruitment instrument
T750D T750D Medium
T750E T750K Text for applicant group
T750F V_T750F Text for applicant range
T750G T750G Unsolicited application group
T750H T750D Text for medium
T750I T750G Text for unsolicited application group
T750J T750J Action type
T750K T750K Applicant group
T750P T750J Text for action type
T750X V_T750X Vacancy
T751A T751A Applicant status
T751B T751A Text for applicant status
T751C V_T751C Status reason
T751D V_T751D Admissible combination of status and reason
T751E V_T751E Applicant event
T751F V_T751F Text for applicant event

These views can all be accessed from the "Recruitment" implementation guide.