Configuring the MDF Position Object

Objective

After completing this lesson, you will be able to understand and configure the MDF position object.

Metadata Framework Platform Overview

The MDF position nomination method uses the Metadata Framework (MDF). This framework is a generic platform that enables users to define their objects, configure object relationships, create rules and workflows, and offers a rich configurable user interface. You can create, modify, and delete extensions that are often referred to as generic objects. MDF complements XML-based configuration options but largely removes the requirement to use Provisioning to modify configurations, and it offers the following benefits:

Focus Areas	Metadata Framework Key Benefits
Effective Dated Platform	Objects defined in the Metadata Framework are automatically effective dated, providing richer functionality to customers without additional resources (for example, effective dated positions).
Custom Fields	Customer administrators can extend application functionality through custom fields and objects.
Expanded Permissions	Flexible permission options designed with the Role-Based Permissions model mean that you can configure field and object permissions to meet complex business requirements.
Consistent User Experience	Users get a constant and standard administrative experience. It brings consistency to suite-wide products. To be further enhanced by the launch of a configurable UI.
API Access	MDF objects are automatically accessible through the Open Data Protocol (OData) API framework for systems integration and extensibility.

Note

The Succession Org Chart only reflects the current state of position data. So, while the MDF position object handles effective dating, the SOC only displays the data accurately for the current date and time.

Note

For more information about the Metadata Framework, review the Metadata Framework (MDF) guide on help.sap.com.

If you don't have Employee Central Position Management, keep your Position Model updated by using the sync process or by importing positions, detailed later.

MDF Position Object Configuration

Implementing the MDF position-based nomination method requires some additional steps beyond the baseline Succession Planning configuration. If you’re upgrading from another nomination method to MDF Position, perform the first four steps before migrating to MDF positions:

Define and secure the position object, including label translations as needed.
Define (or import) Generic Object picklists and set up related data for the necessary fields in your MDF position object.
Configure permissions to apply to the desired employee fields and permissions, including RBP target permissions for positions.
Select which position fields to present in the position information block for People Profile, if any.
Build ad hoc reports to use the "Succession planning with EC position" or the "Succession planning without EC position" family of report builder views.

Configuring Permissions for the Metadata Framework

The administrators role must have Metadata Framework permissions in order to configure the Position Object.

Navigate to Manage Permission Roles using action search.
Select the Administrator role.
Choose Edit and change the basic information if necessary.
Choose Next and navigate to the Administrator Permissions section.
Select Metadata Framework.
Choose Select All for the Admin role.
Choose Next, review the role’s permissions, and choose Save.

Choose Metadata Framework to configure Admin permissions.

Position Object Configurations

Once the necessary Metadata Framework admin permissions are set, changes can be made to the Position Object using Configure Object Definitions. To edit the Position Object:

Navigate to Configure Object Definitions using action search.
Select Object Definition and then Position for the object.
Select Take Action and then Make Correction.
Make your changes to the object and then save it.

Select Take Action>Make Correction to edit the position object.

To understand the sections within the MDF Position Object, review this chart:

Sections	Purpose
Fields	Displayed on the Position UI based on visibility settings
Associations	Associates other MDF Objects with the Position
Searchable Fields	Adds position fields and allows keyword search in SOC and Position Tile view
Business Key Fields	Not required for Succession
Security	Required to associate MDF Position object with Role-Based Permissions
Rules	Not required for Succession without Employee Central

Typical Position Fields for Succession without Employee Central:

Field Name	Purpose	Required	Visible
Code	External position code visible to users	Yes	Yes
externalName	Free form text for position title	Not required/ Recommended	Yes
effectiveStatus	Indicates whether position is active	Yes	Yes
effectiveStartDate	Indicates when the position becomes effective for Succession Planning	Yes	Yes
effectiveEndDate	Autogenerated by system	Yes	Yes
positionCriticality	Indicates whether the position is a "key position".	Yes	Yes
Incumbent	Indicates the incumbent for the position. Leave field blank if position is vacant	Yes	Yes

Hint

The field positionCriticality is a picklist field, and the picklist code that must be referenced in the Valid Values Source must be written: PositionCriticality. This code is case-sensitive and it has to be written in one word with a capital P and a capital C. Do not use lower case like positioncriticality or positionCriticality. Moreover, for the PositionCritcality picklist, do not use letters for values. The external codes should be numeric values, otherwise you'll receive an error in the Position Tile View. Besides, as a best practice, please start with 0.

Field Visibility

The visibility of fields is changed by editing the field details.

Screenshot of the Details section: Editable is selected from the Visibility dropdown.

Visibility options are as follows:

Terms	Definitions
Editable	The field becomes editable for anyone that has Create/Insert/Correct permission on the Position object.
Not Visible	This value sets the field to invisible and not available on the UI or the import file.
Read Only	This makes the field read only on the UI but still importable using the MDF import.

Changing Field Labels

Follow the same steps as in the previous lesson to navigate to the field details within the MDF Position Object.

Locate the Label box within the field details screen and click inside the text area to edit it. To add translations to the label, select the icon to the right of the Label box.

A screnshot of the Details section with Position Criticality in the Label box

Make any necessary changes and select Done and Save.

Defining and Securing the MDF Position Object

You also need to configure the security settings for the position object. Setting up the MDF position object with Miscellaneous Permission settings for RBP allows the administrator to assign read or write permissions on the MDF position object.

Navigate to Configure Object Definitions using Action Search.
In the first search box, select Object Definition, and in the second box, type Position. From the resulting list, choose the Position object.
Choose Take Action→Make Correction.
In the Security section, select Yes for Secured. Then select Miscellaneous Permission for Permission Category.
Save your changes.

Assigning Visibility and Action Permissions for MDF Positions

Navigate to Manage Permission Roles using action search.
Select the role for which you’re editing permissions.
Choose Edit and change the basic information if necessary.
Choose Next and navigate to the User Permissions section.
Select Miscellaneous Permissions.
Find the section for Position and select the Visibility options you want to set for the role. Succession planners should have, at a minimum, View Current assigned.
Select the Action options you want to set for the role:
1. Create: The role can create new positions.
2. Insert: The role can insert a new effective dated record to an existing position.
3. Correct: The role can make corrections to position values.
4. Delete: The role can soft delete positions with an effective end date.
5. Import/Export: The role can import and export the positions using Import and Export Data. Note that the options in Position Management: Import Positions and Position Management: Export Positions are both dedicated to the legacy position nomination method and do not apply to the MDF position-based nomination method.
Choose Next, review the role’s permissions, and choose Save.

Check the Position options in Miscellaneous Permissions.

Managing Individual Positions

Once the Position Object has been configured, individual positions can be added and managed by navigating to Manage Positions. Select the position to edit, then choose Take Action and Make Correction.

Note

The action settings defined in Miscellaneous Permissions do not grant permission to edit or delete the actual Position Object. These settings only grant permission to the role to manage the positions.

Choose Take Action and then Make Correction to manage individual positions.

Configuring RBP Target Populations for MDF Positions

With MDF Positions, you have more control over your permission settings and can extend your permissions beyond user-based attributes. The advantage of the position-level target population is that permissions are independent of the position’s incumbent. If a user has access to a position, they continue to enjoy the same access even if the incumbent changes on the position. This permission capability also provides better control over vacant position-level permissions and eliminates the need for a placeholder TBH user record. This level of control is critical during succession planning.

For example, a succession planner has permissions to do planning for the finance organization. When an employee moves from finance to accounting, the access permission remains on the position. This allows the succession planner to continue accessing the finance position the employee vacated and to continue managing its plans.

There are a few points to understand about how target populations work with MDF Positions:

A target population based on positions is required for the MDF position-based nomination method where key succession planning permissions are applied to positions.
The option to choose a target population based on positions is available when any of the visibility or action permissions for positions are assigned.
The following succession planning permissions only work with position-level target populations when the MDF position-based nomination method is used:
- Succession Planning: Access to the position is required to add or delete successors for that position. At a minimum, the View Current visibility permission is required.
- Succession Management and Matrix Reports: At minimum, the View Current visibility permission is required to view the successors for a position.
- Succession Approval: Access to the position is required to approve or reject a pending successor for that position. At minimum, the View Current visibility permission is required.
Regardless of the target population settings, succession planners should have, at a minimum, the View Current permission for positions.
A position-level target population defaults to All positions. We can adjust the target population to ensure that users only have access to view or manage the positions they are intended to view or manage.
You can also choose to have that target population based on position attributes.

Note

If multiple inclusion criteria are selected, only the positions that meet all the criteria are the permitted target population.

You can prevent the logged-in user from seeing and from planning their own successors. There are two options that must be activated in the target population in RBP:

For 3: Define a Target Population, make sure that the option Exclude Granted Users from having the same access to themselves is activated.
For 4: Define Target Criteria, make sure that the option Exclude access to Granted User's Position is activated.

When selected, the users are not permitted to plan or view the succession for their own positions. This applies even if they have succession planning permission over their organization areas in which this position belongs. For example, an HR user responsible for succession planning in the HR department should not see the successors for their own position.

As succession nominations are very sensitive data for many organizations, this is a classic best practice approach.

To define target populations and criteria:

Navigate to Manage Permission Roles using action search.
Select the role for which you’re editing permissions.
Select the Assignments tab.
Select Edit.
Choose Next or scroll through the sections and edit the assignments.
Review the role’s permissions and choose Save.

Modify the Position Object Label

In this simulation, you will change the label of the MDF Position Object.

ExerciseStart Exercise

Steps

Use action search to navigate to Configure Object Definitions.
In the Search dropdown, select Object Definition.
In the second dropdown, type Position and then select it.
Select Take Action and then Make Correction.
In the Label field, change Position to Position HR841.
Select Save.
Verify the new label appears in the second dropdown as well as in the name after Object Definition (for example Object Definition: Position HR841).
Use Action Search to navigate to Manage Permission Roles .
Select the System Admin Permission Role.
Select Edit and then Next.
Select Miscellaneous Permissions.
Select Person and check View and Edit.
Select Next and then Save.
Log out of the instance for the permissions to take effect, and then log back in as the administrator.
Select Succession from the main dropdown menu.
Select the Succession Org Chart tab.
In the search window (Search by), make sure the People radio button is selected. Then enter Carla Grant and select her name.
Select the VP Sales position to open the Position Card.
In the upper right corner of the position card, select the 3-line icon and choose Show and Edit Position.
Verify the new label displays in the top of the window.

Next lesson