11.2 Enabling Position Management and Setting Role-Based Permissions

11.2 Enabling Position Management and Setting Role-Based Permissions

Quick Answer: Enabling Position Management takes two steps. (1) Switch it on in Manage Employee Central Settings (or Provisioning Company Settings). (2) Enable the position field in the jobInfo element in Manage Business Configuration. Then grant permissions for the position field, the secured Position object (Miscellaneous Permissions), the Manage Position category, and MDF tools, with target criteria where access must be limited.

Prerequisites

Position Management requires the Metadata Framework and basic Employee Central Core settings. SAP recommends reviewing SAP SuccessFactors Employee Central Position Management: Design Considerations and Recommendations in the Implementation Design Principles before starting. Most PM setup is done in the instance by an administrator. Anything that needs Provisioning must be done by an implementation partner, or Product Support if no partner is engaged.

The Two Enablement Steps

1. Switch on Position Management: in Manage Employee Central Settings, under Others, set Position Management to ON and save. The alternative is Provisioning > Company Settings. If the tool is missing, grant Manage System Properties > Employee Central Feature Settings.
2. Enable the position field: in Manage Business Configuration > jobInfo, confirm there is a field with identifier position and Enabled = Yes. Add it from the drop-down if missing. THR79's exercise relabels it from Position ID to Position. You can also do this in the SDM XML, but importing requires Provisioning.

Permissions

1. The Position Field (Job Information)

In Employee Central Effective Dated Entities > Job Information > Position, grant the levels needed: View Current, View History, Edit/Insert, Correct, Delete. Position appears in this list only after the field is enabled in BCUI.

2. The Position Object (Miscellaneous Permissions)

The Position MDF object is secured, so access is granted in Miscellaneous Permissions > Position: View Current, View History, Create, Insert, Correct, Delete, and Import/Export. Field Level Overrides can make fields No Access or Read Only, for example FTE read-only, or Job Level and Position Controlled hidden. Do not select mandatory fields for field level overrides, because it can cause application issues.

3. Metadata Framework

Relevant Metadata Framework permissions: Configure Object Definitions, Configure Business Rules, Import/Export Permission on Metadata Framework, Manage Configuration UI, Manage Mass Changes for Metadata Objects, and Manage Sequence (auto-generated position codes).

4. Manage Position

Create Fieldglass Job Requisition in Position Organization Chart exists for customers with the Fieldglass integration.

Target Population Restrictions for Positions

In the role's Assignments > Edit > Define Target Criteria > Miscellaneous Permissions > Position, choose Restrict Target Criteria to. Four options:

1. By field criteria ("Include access to Position with the following criteria"), with operators =, !=, is null, is not null, in. Example: positions in company Ace_USA.
2. Hierarchy below the granted user's position, by Parent Position = 1, 2, 3, or all levels down.
3. Matrix relationship to the granted user's position, based on the positionMatrixRelationship association.
4. Hierarchy below a given position, for example Code = Pos_ID7 and Parent Position = 2 levels down.

Exclude access to Granted User's Position removes the user's own position when any of these restrictions apply.

Making Create Respect the Target

By default, the Create permission lets the user create any position. Target criteria are not respected for Create. To enforce them, set CREATE Respects Target Criteria = Yes in the Position object's Security section (Configure Object Definitions).

Example: managers may view all positions but create positions only below their own:

1. Set CREATE Respects Target Criteria = Yes on the Position object.
2. Role A: Position View Current and View History, target all positions.
3. Role B: Position Create, target hierarchy below the granted user's position, all levels.

The Create check happens when the position is saved or the workflow submitted. Without permission, the system does not allow saving. In THR79's exercise, a manager who picks a parent position outside their hierarchy gets a No Permission error.

Recommended Role Settings from THR79

Insert is required for some Quick Actions for Positions, where managers update positions from My Team Positions (Section 12.3). THR79's exercise gives the Employee Self-Service role Access Position Organization Chart with Parent Position = 1 level down. The system warns that the access population is large, so confirm. Employees then see only their own position and cannot change the display date.