End - to - End Guide for using Multi-Select Position Generic Object on Job Requisition

[arunsingh222]

Hello SAP Community,

 

As, we have feature to use Multi-Select of Position to hire Multiple Candidates on different positions by creating only One Job Requisition.

In this blog I am sharing end-to-end step to Configure the Multi-Select Feature and the limitation
And also my experience when I got the requirement, which is common but not feasible in standard way

By creating a single requisition for multiple positions, recruiters can reduce the administrative overhead of maintaining multiple requisitions for a similar role position.​

Configuration:

Let's start the configuration, we have to setup Position generic object with the appropriate attributes and ensure Position Generic object should be configured in both template Job Requisition and Offer detail template

For that please see the below XML code

1. Ensure that you have the std_position_obj configured with multi-select set to True:

  <field-definition id="std_position_obj" type="object" required="false" custom="false" object-type="Position" multiselect="true">

  <field-label mime-type="text-plain"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="en_GB"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="en_US"><![CDATA[Position]]></field-label>

  <field-description><![CDATA[Position]]></field-description>

  <field-description lang="en_GB"><![CDATA[Position]]></field-description>

  <field-description lang="en_US"><![CDATA[Position]]></field-description>

      </field-definition>

 

2. Also, make sure that your std_position_obj field is mapped to the Job Offer from the Job Requisition :

  <field-definition id="std_position_obj" type="object" required="false" template-type="job-req" anonymize="false">

  <field-label mime-type="text-plain"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="en_GB"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="en_US"><![CDATA[Position]]></field-label>

  <field-description><![CDATA[Position]]></field-description>

  <field-description lang="en_GB"><![CDATA[Position]]></field-description>

  <field-description lang="en_US"><![CDATA[Position]]></field-description>

      </field-definition>

 

Limitations:

There are a couple of limitation which we have keep in mind when we get this type of requirement and need to provide the comment so customer can have clear understanding about the feasibility.  So when "std_position_obj" standard generic object field is defined on a Job Requisition template with multiselect="true" attribute value, here the some below important point which we have to explain to the customer as per requirement:

1. When we define position standard generic object field "std_position_obj" with multiselect="true" attribute value on Job Requisition template, then we cannot write any Business Rules for this field (Will not showcase in Business Rules).


2. When we define position standard generic object field "std_position_obj" with multiselect="true" attribute value on Job Requisition template, then position Quick Card will not show (Which normally appear right side of Object field Value).


3. When the "std_position_obj" field is defined as multiselect="true", then it will not have any search option (Normally we get the option to search the values).


4. If user have write permission, As standard it's not possible to limit to see only specific Position for users. For users all position will be visible in this Position Object field.

 

For complete information of the behavior and limitations of "std_position_obj" field, please follow this KBA >>>

So, when we propose this feature with Customers, they really like this because it can reduce the administrative overhead of maintaining multiple Job Requisitions for similar role position.​

But we always stuck on a point where customer ask to maintain this position field list on the Job Requisition form as per the Primary Position
E.g. Only those position will show which have the same data as Legal Entity, Business Unit, Division, Department, Location, Pay Grade or Cost Center etc. as per the Primary Position (Position on which Job Requisition Created)

So when I explained this feature with one Customer, I got some different requirement to reduce the list of position on the Job Requisition Form as per the following Criteria

Scenarios:

1. 
   

   Only same manager hierarchy positions will list down in the dropdown for Hiring Manager

   
   


2. 
   

   Only position will list down which have the same data as per the Primary Position

   
   

 

Solution for (1): Only same manager hierarchy positions will list down in the dropdown for Hiring Manager

It will be managed by the Role Based Permissions

Steps:-

1. Admin Center >>> Manage Permission Role >>> Select the Manager Permission Role >>> Go to "Grant this role to..."


2. On the required target population grant  Include access to Position in the hierarchy below the Granted User's Position -> Parent Position = All level(s) down
   

For More Information, follow this KBA - How to restrict user to see Higher Level Position

Solution for (2): Only position will list down which have the same data as per the Primary Position

It will be managed by the Job Requisition Template

Limitation and Behavior:-

1. If you are doing the configuration from admin center, then we can add only one Field Criteria.
   


2. From Provisioning, we can add multiple field Criteria


3. Only object field can be added as a field criteria in the Job Requisition XML Template


4. But if we have added multiple field criteria from provisioning, then you cannot Save or Publish the Job Requisition Template in Admin Center. And we did it then, only one field criteria will be remaining which was on top others will be removed.


5. If any of the field (added in field criteria) mapped to Position Job Requisition Integration (In Position Management field mapping rule) and that field data is not filled for the Position for which going to create the Job Requisition, then you will get the Error.


6. User should have Read or Write permission of all the field criteria field in the Job requisition Template and Offer Detail Template

Steps:-

Please log in to Provisioning ->> Go to Managing Recruiting ->> Click on Import/Update/Export Job Requisition Template and Download and edit the Job Requisition Template
In the field criteria section of Position Object Field add criteria field and their destination field Id

For detail information of field criteria configuration, please follow this link Field Criteria Definition in Job Requisition

  <field-definition id="std_position_obj" type="object" required="true" custom="false" object-type="Position" multiselect="true">

  <field-label mime-type="text-plain"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="ar_SA"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="en_GB"><![CDATA[Position]]></field-label>

  <field-label mime-type="text-plain" lang="en_US"><![CDATA[Position]]></field-label>

  <field-description><![CDATA[Position]]></field-description>

  <field-description lang="en_GB"><![CDATA[Position]]></field-description>

  <field-description lang="en_US"><![CDATA[Position]]></field-description>

<field-criteria sourceFieldName="cust_jobFamily" destinationFieldValue="custJobFamily_obj"/>

<field-criteria sourceFieldName="jobCode" destinationFieldValue="custJobcode_obj"/>

<field-criteria sourceFieldName="company" destinationFieldValue="legalEntity_obj"/>

<field-criteria sourceFieldName="costCenter" destinationFieldValue="costCenter_obj"/>

  </field-definition>

Conclusion:

As demonstrated by this blog post, you are now able to understand configuration, limitations, and challenges related to use Multi-Select Positions feature on Job Requisition feature

It helps you to hire multiple candidate from a single job requisition on the different position

I hope this post will help you to understand and providing your suggestions to customer for the different scenarios and highlighting the limitation.

If you found this post to be useful, please follow and press the like button and share your feedback or thoughts in a comment !

 

Thanks

Best Regards,
Arun Singh Rajput