Are you someone who’s trying to create requisitions using EC Position Org Chart and running into issues? Or looking for information on what it supports and what it doesn’t?
Then you’ve come to the right place. We’re going to tell you how to use this integration to auto-populate the Recruiter Operators on the requisition and address some common issues one might encounter.
First things first, you’ll need to have implemented EC Position Management and Recruiting Management.
You’ll need to ensure that you have numberOpenings and positionNumber fields on your requisition template. You do not need to include these in the mapping rule.
It is important to match the field types when configuring the rule. For example, a string field in EC must relate to a text field on the requisition template. Otherwise the integration will fail.
The RCM implementation guide has a wealth of information on how to set this up. The EC Position Management guide also contains a lot of information on the setup.
We’ll deal with specific scenarios here.
The following snippet allows fetching of the person occupying the position that manages the position for which you want to create the requisition.
The following snippets show fetching of persons whose positions are matrix-related to the position for which you are trying to create the requisition. This allows for fetching of any person using the relationships between positions.
Note that is is not possible to fetch relationships for the person trying to create the requisition - the system can fetch relationships only for the position for which the requisition is being created.
To find out the list of errors, use the Check Tool. This is available from the Admin Center.
Let’s look at some of the common errors and how to fix them:
Department does not have any active employee assigned. This condition of having at least one active employee assigned is scheduled to be addressed in release 1705.
This is because the job title is not mapped or mapped incorrectly. Use jobReqLocale.jobTitle. In some cases, you might need to specify the locale, like below:
Position.Position Title.English (United Kingdom)
With SFAPI, the system didn’t check if the requisition template had any mandatory fields and one didn’t have to include all those fields in the mapping rule.
However, with OData API, the system requires that all the mandatory fields on the requisition template be included in the mapping rule.
If you have a long list of mandatory fields and don’t want to include all of them in the rule, use the IsDraft clause to get around the system requirement.
Either the requisition template doesn’t have the field defined or is of a different type. For example, the position field is string and the requisition field is a picklist.
Also, if the requisition field type is picklist, then your mapping rule must refer to the external code of the picklist value, for example, custPayGrade.externalCode
Many organizations do not want the Hiring Managers to be able to select the template to create a requisition from a position. Reasons vary from the risk of selecting an incorrect template to additional work on the part of the Hiring Managers.
With a few simple settings, one can easily control if a requisition template can be selected at all. One can also ensure that only requisition can be created for a position.
Let’s look at this scenario and its setup in action.
That’s it!
Now whenever a user tries to create a requisition from a position, s/he will see which requisition template is be used but won’t be able to switch to another template.
Observe that the Job Requisition Template field has a default value and is read-only!
In addition, if an active requisition exists for the position, the user won’t be able to create another requisition. Observe that there's no option to create a requisition, as an active one already exists.
Then you’ve come to the right place. We’re going to tell you how to use this integration to auto-populate the Recruiter Operators on the requisition and address some common issues one might encounter.
Prerequisites
First things first, you’ll need to have implemented EC Position Management and Recruiting Management.
You’ll need to ensure that you have numberOpenings and positionNumber fields on your requisition template. You do not need to include these in the mapping rule.
It is important to match the field types when configuring the rule. For example, a string field in EC must relate to a text field on the requisition template. Otherwise the integration will fail.
Setup
The RCM implementation guide has a wealth of information on how to set this up. The EC Position Management guide also contains a lot of information on the setup.
We’ll deal with specific scenarios here.
Auto-populate Manager of position:
The following snippet allows fetching of the person occupying the position that manages the position for which you want to create the requisition.
Auto-populate roles from position’s matrix relationship:
The following snippets show fetching of persons whose positions are matrix-related to the position for which you are trying to create the requisition. This allows for fetching of any person using the relationships between positions.
Note that is is not possible to fetch relationships for the person trying to create the requisition - the system can fetch relationships only for the position for which the requisition is being created.
Relationships of a position:
Specifying the matrix relationships in the mapping rule:
Result:
Common Issues
To find out the list of errors, use the Check Tool. This is available from the Admin Center.
Let’s look at some of the common errors and how to fix them:
department invalid, with the index 0
Department does not have any active employee assigned. This condition of having at least one active employee assigned is scheduled to be addressed in release 1705.
Job Title says [Not translated in selected language]
This is because the job title is not mapped or mapped incorrectly. Use jobReqLocale.jobTitle. In some cases, you might need to specify the locale, like below:
Position.Position Title.English (United Kingdom)
formDueDate required, jobReqLocale/jobTitle is required for jobReqLocale/locale en_GB…..
With SFAPI, the system didn’t check if the requisition template had any mandatory fields and one didn’t have to include all those fields in the mapping rule.
However, with OData API, the system requires that all the mandatory fields on the requisition template be included in the mapping rule.
If you have a long list of mandatory fields and don’t want to include all of them in the rule, use the IsDraft clause to get around the system requirement.
Requisition has no field with this name that refers to a simple data type
Either the requisition template doesn’t have the field defined or is of a different type. For example, the position field is string and the requisition field is a picklist.
Also, if the requisition field type is picklist, then your mapping rule must refer to the external code of the picklist value, for example, custPayGrade.externalCode
This blog was written in collaboration with neelesh.kamath
The following update is being brought to you in collaboration with Anurag Nayak from SAP Labs India.
Control which templates a Hiring Manager can select while creating a job requisition from Position
Many organizations do not want the Hiring Managers to be able to select the template to create a requisition from a position. Reasons vary from the risk of selecting an incorrect template to additional work on the part of the Hiring Managers.
With a few simple settings, one can easily control if a requisition template can be selected at all. One can also ensure that only requisition can be created for a position.
Let’s look at this scenario and its setup in action.
- First, adjust the template selection rule GetReqTemplate to suit your condition(s). The result of this rule will be a single template that is presented to the Hiring Manager as default.
- Adjust the permission that allows one to select the requisition template. Deselect it for this scenario. Admin Center > Manage Permission Roles > Choose Role > Manage Position > Select Job Requisition Template in Position Organization Chart
- Navigate to Admin Center > Position Management Settings > ‘To Be Hired’ Status Adaptation. Use the following combination of settings to prevent creation of a second requisition while one is still active for a position.
That’s it!
Now whenever a user tries to create a requisition from a position, s/he will see which requisition template is be used but won’t be able to switch to another template.
Observe that the Job Requisition Template field has a default value and is read-only!
In addition, if an active requisition exists for the position, the user won’t be able to create another requisition. Observe that there's no option to create a requisition, as an active one already exists.
- SAP Managed Tags:
6 Comments
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
