The authorizations for Succession Planning are stored in the authorization profiles of the
SAP E-Recruiting
roles.
For more information about the role profiles, see the respective role descriptions.
You can use the authorization object
P_RCF_APPL
(Applications in
SAP E-Recruiting
) to control access to start pages and applications.
Authorization object PLOG (Personnel Planning)
You can use the authorization object PLOG , which is used for personnel planning data, to control which infotypes and objects a user can access. For example, you can block the display of demographic data for persons not belonging to the HR department.
SAP E-Recruiting
uses the following object types:
US (User), CP (Central Person), P (Person), O (Organizational Unit), S (Position), C (Job); NA (Candidate), NB (Requisition), NC (Posting), ND (Application), NE (Candidacy), VA (Appraisal Template, in
SAP E-Recruiting
: Questionnaire Template), VB (Criteria Group, in
SAP E-Recruiting
: Question), VC (Criterion, in
SAP E-Recruiting
: Response).
(Note: Object types NC and ND are only relevant for
Recruitment
.)
SAP E-Recruiting
uses the active plan version only and all planning statuses.
SAP E-Recruiting
uses the following infotypes:
Infotypes 50* (Questionnaires)
Infotypes 51* (
SAP E-Recruiting
infotypes)
Infotypes 1000, 1001, 1002
Subtypes are active
A special authorization check is performed for qualifications. In the authorization object
P_TCODE
, you must enter the value
PP
in the
Transaction Code
field (TCD).
Certain restrictions exist, depending upon the context. For example, a candidate can view and maintain his or her own profile only. These connections are not checked using authorization objects; instead, they are checked within the relevant application.
SAP E-Recruiting
manages personal data using
SAP Business Partner
. For this reason, you must assign all users the basic authorizations for
SAP Business Partner
.
The following authorization objects are relevant:
B_BUPA_ATT (Business Partner: Authorization Types)
B_BUPA_FDG (Business Partner: Field Groups)
B_BUPA_GRP (Business Partner: Authorization Groups)
B_BUPA_RLT (Business Partner: BP Roles)
The authorization object
P_RCF_POOL
(
Direct Access to Talent Pool
) is checked in
SAP E-Recruiting
when candidates are accessed directly in the Talent Pool.
In Succession Planning, the Talent Pool can be accessed directly in the following ways:
Using the
Candidate Overview
scenario.
By searching by name, a candidate can be identified and all relevant data can be displayed. Example: A candidate requests information by telephone.
If you have to change candidate data retroactively. For example,
if the candidate reveals during an interview relevant information that was not included in the candidate's profile.
Depending on the scenario, you enter the following authorizations in the field RCF_POOL (
Permitted Access Mode
):
DIRECT_ACC (Status-Independent Access to Candidates)
CAND_MAINT (Maintenance of Candidate Data)
You use the authorization object
P_RCF_STAT
(
Object Status in E-Recruiting
) to assign the authorizations for status changes for objects.
The field OTYPE (
Object Type
) contains the relevant object types, the field RCF_STATUS (
Generic Object Status
) contains the statuses permitted.
In Succession Planning, the following object types and statuses are relevant:
Object |
Possible Status |
---|---|
Candidate |
Profile Released, Profile Locked |
Candidacy |
In Process, Withdrawn, Rejected, To Be Hired |
Requisition (succession plan) |
Draft, Released, Completed, To Be Deleted, On Hold |
Questionnaire |
Draft, Released, Do Not Use |
You can use the authorization object P_RCF_VIEW to assign the authorizations to display data overviews.
In Succession Planning, the following activities are used for the authorization to display data overviews:
ACT_DOVR (Overview of the activity)
CAND_DOVR (Overview of the candidate profile)
CDCY_DOVR (Overview of the candidacy data)
TG_DOVR (Overview of the talent group)
The user has access to all overviews that are stored in the field RCF_VIEW (
Data Overview
) for his or her role.
For all other data overviews, each application that displays a data overview checks whether the user has authorization to view the overview. These checks are different for each application.
In Succession Planning, the system performs the following checks:
Application displaying an overview |
Checks |
---|---|
Candidate (hrscp_cand_dovr) |
Does the user call his or her own profile? Is the user a member of the support team for the succession plan to which the candidate is assigned? |
Candidacy (hrrcf_cdcy_dovr) |
Is the user a member of the support team for the candidate’s succession planning? Is the user a member of the support team for the succession plan to which the candidate is assigned? |
Succession Plan (hrscp_req_dovr) |
Is the user a member of the support team for the succession plan? |
You use the authorization object P_RCF_ACT (Activities in E-Recruiting) to determine the types of access to activities that are possible for a user. An activity in SAP E-Recruiting is therefore identified through the assigned process and through the activity type.
The following access types to an activity can be stored using the authorization field ACTVT (Activity):
Add or Create
Change
Delete
To be able to create candidates, you must use the authorization object S_USER_GRP (User Master Maintenance: User Groups) to assign authorization for creating the relevant user.