Issues with Job Requisition Creation and Recruiter Assignment in Position EC

[Veeko_Chen]

Hi Experts, 

We have a customer requirement where the hiring manager creates a job requisition from Position EC. Our process involves:

1. Hiring managers create job requisitions from Position EC without an assigned recruiter.
2. Customer requests to route the requisition to a recruiting team group for an available recruiter to self-assign to assist the manager in completing the job requisition and proceeding with the approvals. 
3. The route map designed for job requisition was initiated as a collaborative step between the hiring manager and the recruiter and then routed to the HR manager.

I've set the recruiter as a collaborative step in the draft and modify stage of the route map. However, the recruiter field is empty at creation, causing permission issues. Also, recruiting team users can view unapproved jobs but can't edit them until approval, so the job requisition will be stuck at the first stage.

Any advice or thoughts would be highly appreciated!

[mjmitra · Accepted solution]

Hi @Veeko_Chen,

Please see the following recommendations below:

"I've set the recruiter as a collaborative step in the draft and modify stage of the route map. However, the recruiter field is empty at creation, causing permission issues. Also, recruiting team users can view unapproved jobs but can't edit them until approval, so the job requisition will be stuck at the first stage." 

a. The recruiter field being empty at creation is expected, if you have not mapped the Recruiter in the Admin Center > Position Management Settings' mapping business rules, but this is not a problem. Just make sure that you use an isDraft function (isDraft="true") so that the system knows to skip the Recruiter role (leave it blank) if it is a required field. 

Check item no. 11 in the KBA provided below.

2878365 - Position Management in Recruiting - Implementation Tips & Tricks from Support - Recruiting Management
https://me.sap.com/notes/2878365 

b. Make sure that Hiring Managers, who will be read as [O] or originator of the requisition (since they created the requisition), has write permissions in the requisition template for all the required fields for the <pre-approved> status. The system will typically scan your requisition template and look for the required fields and ensure that you have mapped them in the rules and populate them on creation of the requisition. Else, you will get an error.

Also, make sure that you have mapped all those required fields in the Admin Center > Position Management Settings' mapping business rules, unless the fields are like the Recruiter field which you intend to populate later on. 

c. Make sure to check the option 'Allow users to view pre-approved requisitions without regard to route map status' in Manage Recruiting Settings. This will ensure all the approvers will see the requisition while in <pre-approved> status.

d. Just like the Hiring Manager, make sure to give your Recruiting team members, and whoever is in the collaborative step, write permissions to the requisition fields, especially the recruiterName field, for <pre-approved> status. This is important so that they could populate those fields especially the recruiterName field while the requisition is in <pre-approved>.

For example: 

<field-permission type="write">
<description><![CDATA[]]></description>
<role-name><![CDATA[S]]></role-name>
<role-name><![CDATA[R]]></role-name>
<status><![CDATA[pre-approved]]></status>
<field refid="fieldName"/>
</field-permission>

Note: The write permissions has to be provided for the <pre-approved> status so that users will have the ability to edit or populate fields while the requisition is in approval.

Note: You will see role names here like S (sourcer), or R (recruiter), etc. If your team is a recruiterTeam, they will inherit the permissions of the recruiter. So, if the recruiterName field has write permissions to the fields, the recruiterTeam will also have one. If your team is a hiringManagerTeam, they will inherit the permissions of the hiringManager. So, if the hiringManagerName has write permissions to the fields, the hiringManagerTeam will inherit those permissions. 

Here's the list of full operator designations:

https://help.sap.com/docs/SAP_SUCCESSFACTORS_RECRUITING/8477193265ea4172a1dda118505ca631/a594a0a633a...

Thank you,

Jubelle
SAP SuccessFactors Recruiting Management Support

*Please mark the answer as a solution, if it addresses your question.*