This article describes the steps to configure Position Management Settings in order to create a requisition from Position Org Chart. The information in this document is supplementary to the implementation guide. This document provides a check list of the settings needed to create requisitions from position org chart.
"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 (RCM)
Check the Implementation Guide for the standard configuration for Position Management Settings. The information in this document is supplementary to the implementation guide. This document provides a check list of the settings needed to configure position management integration between RCM and EC to create requisitions from position org chart.
Position Management allows permitted users to create ONE requisition from a position via the Position Org Chart. Details from position (EC) are auto populated to the requisitions created. This takes advantage of business rules.
Once created, if you preview the position details again, you should be able to see the requisition details of the requisition created.
1. Go to Admin Center > Position Management Settings > Under Integration.
a. The field Use Recruiting Integration has to be set to Yes
b. The field Rule for Deriving Job Requisition Template ID has to be set to the Business Rule you want to run.
c. The field Rules for Mapping Fields Between Position and Job Requisition has to be set to Business Rule you want to run.
2. Go to Admin Center > Position Management Settings > Integration.
a. When you create a Requisition from Position Org Chart the Rule for Deriving Job Requisition Template ID runs first to get the template details for the requisition being created.
b. Then, the Rule for Mapping Fields Between Position and Job Requisition runs to get the field values to be mapped from Position to the Requisition.
Note: When you open the Rules from the Position Management Settings via the view icon they don’t open Full Screen.
3. Go to Admin Center > Configure Business Rules > Search for the Rule Name.
4. If the Job Requisition template field is mapped to the Template ID, the business rules integration is using SFAPI. Note: As SFAPI is already deprecated, it is highly encouraged to switch to ODATA.
a. When the Template is mapped to the Template ID, the business rules is using SFAPI.
b. When the Template is mapped to the Template Name, the business rules is using ODATA.
c. Make sure the ID and the template name corresponds to the ones in Provisioning and the template should be active.
5. If the Job Requisition template field is mapped to the Template Name, the business rules integration is using ODATA.
6. Go to Admin Center > Manage Position > Positions > Search for the Position ID.
a. FTE (Full-time employment) of at least 1.
b. To Be Hired should be set to Yes.
c. Status should be Active.
d. Vacant should be set to True.
Additional Note: The target FTE (full-time equivalent) expresses the amount of accumulated FTE that may be assigned to this position. If you want the system to control this capacity for overcharging, please set the positionControlled attribute to True.
7. Go to Admin Center > Manage Position > Positions > Search for the Position ID. Make sure the Business Unit, Department, Location, and Division tagged to the position has active users in the User Data File (UDF).
8. Go to Admin Center > Employee Export > Download User Data File. Note: Employee Export may have a different label in your instance.
9. Open the User Data File output (.csv) and make sure there is at least 1 active user in the Department, Division, or Location that is assigned to the Position. Else, you will get an error on requisition creation saying, the Department is invalid with index 0 or Location is invalid, index 0.
10. Make sure all the fields marked as required=“true” in the job requisition templates are mapped in the Rule for Mapping Fields Between Position and Job Requisition. Else, you will get an error saying a certain field is required. The error is specific enough to tell you what required field is missing.
Note: This is true for all methods of Job Requisition creation via API. All the required fields have to be filled out on requisition creation.
11. To overrule the restriction due to the required fields in the template, use the isDraft function. If you use an isDraft function, the requisition will be created although not all fields are mapped in the business rules.
(1) Use isDraft value when you don’t need all the required fields in the requisition template to be populated from position. This means the recruiting users will have to manually fill out these fields AFTER the requisition is created.
(2) When you use the isDraft function, even if not all required fields in the template are mapped in the business rules, the requisition will still be created without errors.
Note: This feature is also use as a workaround if you have issues with creating requisition from position org chart due to a specific field/s. For example, your department is deemed invalid and you cannot fix it at the moment. In order to be able to create a requisition even without the department field, you can use the isDraft function and not map the department field in the business rules (even though it is a required field in the requisition template).
12. This is how you can map isDraft in the business rules.
13. Go to Admin Center > Manage Permission Roles > [Role Name] > Permissions. This should be granted to the users that will create the requisition from position org chart.
a. Under General User Permission > Permission to Create Forms > Either select All or just the job requisition templates.
b. Under Manage Position > Select the following permissions.
Job Requisition in Position Organization Chart
Create Job Requisition in Position Organization Chart
c. Under Manage Job & Skill Profile Visibility > JobReqJobProfile > View, Edit, Import/Export.
d. (Optional) Under Recruiting Permissions, check the following, in order to prevent users from creating requisitions manually outside position org chart.
Hide "Copy Existing Job Requisition" option on the create requisition page.
Hide "Browse Families & Roles" option on the create requisition page.
Hide "Create New Job Requisition from Blank Template" option on the create requisition page.
14. Number of Openings for the requisition is not controlled in the requisition template but in the the position value for Multiple Incumbents Allowed (in Manage Position). If the field Multiple Incumbents Allowed is set to Yes (or True), the Number of Openings field will be editable and the number of candidates to be hired can be more than 1. If it is set to No (or False, the the Number of Openings field will not be editable and the number of candidates to be hired can only be one.
Multiple Incumbents Allowed - This attribute controls whether the system allows the assignment of more than one employee to this position at any point in time. In EC Position Management, we recommend that you set this attribute to True.
Position Management, Position Management, Position Org Chart, Recruiting Management, RCM, EC, Integration, SFAPI, ODATA, API, Business Rules, Configuration , KBA , LOD-SF-RCM-INT , Integrations & Intelligent Services , How To