3111526 - Operator's manager cannot see the Job Requisition or Job Requisition details - Recruiting Management

This article describes the reasons why an operator's manager (Recruiter's Manager - RM, Hiring Manager's Manager GM, Sourcer's Manager - SM, etc.) cannot see the Job Requisition in the Job Summary Page or can see it but cannot see the Job Requisition details.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP SuccessFactors Recruiting Management

Scenario 1. Managers cannot see the Job Requisition.

Being an operator's manager does not give a user implicit access or visibility to the requisitions. There are also no direct permissions for the visibility of the job requisitions in the Job Summary Page. 

A requisition will be visible to a user if they meet the following criteria:

a. If the user has been part of the job requisition approvers (in the route map) while it is in the preapproved status, which you can see in the Job Requisition history. Click on 'i' on the upper right hand side of the requisition and then look for the Routing Map or Audit Trail. You will see the approvers of the requisition while in the preapproved status.

b. If the user is assigned in any operator role e.g., recruiter, hiring manager, etc., or operator teams e.g., recruiter team, hiring manager team, etc. 

Note: Just because a recruiting group is linked to an operator team field in the job requisition template (like the example below) does not automatically mean that the group is assigned to the operator team field. 

<field-definition id="recruiterTeam" type="operatorTeam" required="false" custom="false" group-name="Recruiters - DO NOT CHANGE NAME">

In this example, the recruiting group 'Recruiters - DO NOT CHANGE NAME' is not automatically assigned to the operatorTeam field 'recruiterTeam.' This setting means that only the users defined in the recruiting group 'Recruiters - DO NOT CHANGE NAME' can be added in the field 'recruiterTeam' in the UI. 

A user or recruiting group has to be explicitly added in operatorTeam field (in the UI) to be considered as assigned to the operatorTeam field.  

Scenario 2. Managers can see the Job Requisition but not its details. 

a. They do not have read / write access to the requisition fields. 

For Example: 

<field-permission type="write">
  <description><![CDATA[Job code Permissions]]></description>
  <role-name><![CDATA[RM]]></role-name>
  <status><![CDATA[pre-approved]]></status>
  <status><![CDATA[approved]]></status>
  <status><![CDATA[closed]]></status>
  <field refid="jobTitle"/>
</field-permission>
  
b. The operator role assigned to them i.e., RM (Recruiter's Manager), GM (Hiring Manager's Manager) has been assigned as an approver of the requisition while it is in preapproved status but the manager was changed midway. 

Note: Route Maps are not updatable, even as the information changes they are static the moment the job requisition is created.

To make sure that a user regardless of their role can see the requisition and its details, the user has to be an operator or part of the operatorTeam and has to have read/write permissions to the fields. 

3197587 - Users cannot see the Job Requisition or Job Requisition details - Recruiting Management 

Job requisition, Requisition, Operator, operatorTeam, relational, hiring manager, manager, sourcer, recruiter, visibility, cannot see, not visible , KBA , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem