SAP Knowledge Base Article - Public

2340915 - MDF Position nomination method configuration - Succession Management

Symptom

This article provides necessary information on the configuration needed to enable MDF Position on Admin Center.

NOTE: If you're using Employee Central to manage your positions, then you should only use MDF position-based nominations. In this situation, the same position object is shared between Employee Central and Succession Planning.

Environment

SAP SuccessFactors Succession Management

Resolution

Once MDF Position nomination method is enabled and configured on Provisioning, it is necessary to complete the following steps on Admin Center > Configure Object Definitions > Position object:

  1. Define generic objects for positions, including label translations and field visibility as needed, in Position object. Set the desired level of effective dating to use for position records (basic or multiple changes per day);


Position Field

Value Assigned by System / User


Purpose

Field Visibility (without Employee Central)

rowId

System

Technical Need

Invisible

mdfSystemRecordStatus

System

Technical Need

Invisible

internalId

System

Technical Need

Invisible

code

User

External Position Code that is visible users

Visible

externalName.en_US

User

Business Name of the Position

Visible

effectiveStatus

User

Indicates whether the position is active

Visible

effectiveStartDate

User

Indicates the date when the position becomes effective for Succession Planning

Visible

effectiveEndDate

System

Auto generated end date for the position object

Visible


positionTitle


User

Free form text for Position title. Make sure that the title is accurate as this is used in various Succession functionality


Visible


criticality


User

Indicates whether the position is a “key position” (Note that till 1302 this accepts a numeric value. In future releases this will be converted to a dropdown)


Visible

comment

User

Free form text to add comment

Invisible


incumbent


User

Field indicating the incumbent user for the position. Although EC doesn’t use this field, this is needed for Succession functionality. Leave field blank if the position is vacant


Visible

changeReason

User

 Dropdown indicating the reason for changes to the position. Configured by picklist “Change Reason”

Invisible

description

User

 Free form text to describe the position

Invisible

jobCode

User

 Use search to fill job code

Invisible

jobTitle

User

 Free form text to enter jobTitle of the incumbent

Invisible

jobLevel

User

 Dropdown value derived from the picklist “Job Level”

Invisible

employeeClass

User

Dropdown value derived from the picklist “Employee Class”

Invisible

regularTemporary

User

Dropdown value derived from the picklist “Regular Temporary”

Invisible


targetFTE


User

Numeric value indicating the number of FTEs for the position. Note that Succession does not support positions with multiple incumbents


Invisible

vacant

User

Boolean field indicating whether the position is vacant or filled

Invisible

company

System

EC Foundation Object

Invisible

businessUnit

System

EC Foundation Object

Invisible

division

System

EC Foundation Object

Invisible

department

System

EC Foundation Object

Invisible

location

System

EC Foundation Object

Invisible

costCenter

System

EC Foundation Object

Invisible

createdBy

System

EC Foundation Object

Invisible

createdDate

System

Technical Need

Invisible

lastModifiedBy

System

Technical Need

Invisible
lastModifiedDate

System

 Technical Need Invisible
mdfSystemObjectType

System

 Technical Need Invisible

NOTE: The only fields required for Succession Planning with MDF Position nomination method enabled, without Employee Central, are code, externalName.en_US, effectiveStatus, effectiveStartDate, positionTitile, criticality and incumbent.

  1. Define Associations, Searchable Fields, RBP Permission Security and optional settings on Admin Center > Configure Object Definitions > Position object;
    1. Associations: Before an "Association" can be defined, the MDF Position object needs to be created. This is because the "Association" references the Position object itself. Once the object is defined, use the "Make Correction" function to define the Association.

Name

parentPosition

Type

Valid When

Multiplicity

One To One

DestObjectId

Position

Required

No

Visibility

Editable

Label

parentPosition
    1. Searchable Fields: Any fields that the customer desires to search on. This impacts the "Position" search panel on Succession Org Chart. At the minimum, the following two attributes should be added "positionTitle", and "externalName". You can optionally add incumbent, code and other position fields.
    1. RBP Config: Choose the following configuration:

securedByRBP

Yes

permissionCategory

Miscellaneous Permission

NOTE: Selecting "Miscellaneous Permission" will enable the Miscellaneous Permission section on Role-Based Permissions, allowing administrators to provide read and/or write permission for the MDF object.

    1. Optional Setting: If the following fields are being used, then, it is necessary to define the picklists. This step is usually not required for non-EC customers.
      Define generic object picklists, including label translations, as needed, on Admin Center > Configure Object Definitions > Create New: Picklist. The picklist values can be imported with the generic object import tool on Admin Center > Import and Export Data > Import Data > Picklist. The picklists to be defined are:
      • Change Reason: This maps to field "changeReason". Reason for changing positions. Sample values are Position Change, Position New, Reorganization, etc;
      • Employee Class: This maps to field "employeeClass". Sample values are Consultant, Temp, Apprentice, Intern, Employee, etc;
      • Job Level: This maps to field "jobLevel". Sample values are Director, Manger, Supervisor, Individual Contributor, etc;
      • Regular Temporary: This maps to field "regularTemporary". Sample values are Regular, Temporary, etc.

NOTE: Employee Class, Job Level, and Regular Temporary are only required if the corresponding fields on position object are being used.

  1. Configure Role-Based Permission rules and the roles to apply to position objects. Target populations of positions can be defined within position attributes, once you enable a relevant permission for the role such as Succession Planning.
    1. Create or edit permission roles as required;
    2. Assign relevant Succession Permissions from "Succession Planners" section;
    3. In the section "Miscellaneous Permission", on the left panel of permission settings, assign permissions for the Position object. The object permission includes the following:


Permission Group


Description


Value



Visibility



Controls the permission to view the position history


View Current

View History






Actions



Controls ability to add, edit and delete positions.


NOTE: this permission does not allow to delete and/or to edit the actual position object.

Create: creates a new position.

Insert: inserts a new effective dated record to an existing position.

Correct: allows to edit position values.

Delete: soft deletes position with an effective end date.

 

Roles with permission

Suggested Miscellaneous permission




Administrative Privileges
  • Create
  • Insert
  • Correct
  • Delete
  • View Current
  • View History



Succession Planning
  • Create
  • Correct
  • Delete
  • View Current


Other Succession Permissions
    • View Current
    • View History
    1. Select which position fields to present (read-only) in the pop-up dialog on succession org chart, for users that not have set permission to view or edit position fields. You can configure this setting in Admin Tools > Org Chart Configuration > Position Dialogue > Select the position attributes > Save changes.
    2. Select which position fields to present in the position information portlet in Employee Profile (if configured), in Admin Tools > Configure Employee Files > {Profile View Name} > Insert Portlet > Position.
    3. If migrating from Legacy Position nomination method, re-build the existent Ad Hoc Reports with "Succession planning by EC position" family of report builder views.
    4. Position Management feature, when customer has an Employee Central license, has different configuration settings. Please refer to Employee Central Position Management Implementation Guide, for more information.

    The following table summarizes the key differences in configuration for MDF Positions with and without Employee Central:


    Succession with Employee Central


    Succession without Employee Central


    Employee Central Only


    NOTE


    Add Position to the jobInfo HRIS element


    Not required


    Add Position to the jobInfo HRIS element


    Permission "Manage Position" in RBP settings


    "Manage Position" is unavailable in RBP


    Permission "Manage Position" in RBP settings



    Set "Incumbent" field to Not Visible



    Set "Incumbent" field to Visible



    Set "Incumbent" field to Not Visible

    In EC Position Management, the assignment between a position and the incumbent is made using the position field on Job Information.


    Set "PositionTitle" to Visible


    Set "PositionTitle" to Visible


    Set "PositionTitle" to Not Visible

    In EC Position Management, this is a deprecated field. Please use externalName instead.



    Set "Criticality" to Visible



    Set "Criticality" to Visible



    Set "Criticality" to Not Visible

    This field is relevant for Succession Management only and should only be set to visible if Succession Management is used.





    Set "targetFTE" to Visible





    Set "targetFTE" to Not Visible





    Set "targetFTE" to Visible

    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.



    Set "externalName" to Visible



    Set "externalName" to Not Visible



    Set "externalName" to Visible

    In EC Position Management, externalName is the position title, also shown in the position org chart.


    Define rules for propagating Job Code from Position to Job Code


    No propagation rule required


    Define rules for propagating Job Code from Position to Job Code

    Define rules for keeping the Position and JobInfo objects in sync


    No rule definition required

    Define rules for keeping the Position and JobInfo objects in sync




    Can set "MultipleIncumbentsAllowed" field to Visible




    Set "MultipleIncumbentsAllowed" field to Not Visible




    Can set "MultipleIncumbentsAllowed" field to Visible

    This attribute controls whether the system allows the assignment of more than one employee to the position at any point in time. This is only supported with EC Position Management.


    Add both "externalName" and "positionTitle" to searchable fields


    Add both "externalName" and "positionTitle" to searchable fields


    Only add "externalName" to searchable fields (this will be available by default, no manual steps needed)

    Keywords

    SuccessFactors, Success Factors, Succession Management, SCM, MDF, Position, configuration, position model, setup, setting, employee central, EC, permission, permissions, configure object definitions , KBA , LOD-SF-SCM-ADM , Admin Center, RBP, Permissions and Settings , How To

    Product

    SAP SuccessFactors Succession & Development all versions