2340915 - MDF Position configuration

SAP Knowledge Base Article - Public

2340915 - MDF Position configuration

Symptom

Configuration needed to enable MDF Position from the front end

Resolution

Once the Provisioning set-up is complete, log into Admin tools and complete the following steps:

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

       

Position Field

User Entered / Value Assigned by system

Purpose

Field Visibility for Succession without EC

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 Positions and without EC are code, externalName.en_US, effectiveStatus, effectiveStartDate, positionTitile, criticality, incumbent

 2. Define Associations, Searchable Fields, and rbpConfig on the Position object

        a.  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

     b. Searchable Fields: Any fields that the customer desires to search on. This impacts the “Position” search panel on the Succession Org Chart. At the minimum, the following two attributes should be added “positionTitile”, and “externalName”. You can optionally add incumbent, code and other position fields

     c.  RBP Config: Choose the following configuration

securedByRBP

Yes

permissionCategory

Miscellaneous Permission

   Note: Selecting “Miscellaneous Permission” will enable the Miscellaneous Permission settings on RBP admin screens allowing administrators to provide read / write permission on the MDF object

3. Optional: Only if you are using the following fields you need to define the picklists. This step is usually not required for non-EC customers. Define generic object picklists, including label translations as needed. Picklist values can be imported with the generic object import tool. The picklists that need to be defined are:

    1. Change Reason (Reason for changing positions)  (Sample values are Position Change, Position New, Reorganization etc.). This maps to field “changeReason”.
    2. Employee Class (Sample values are Consultant, Temp, Apprentice, Intern, Employee etc.). This maps to field “employeeClass”.
    3. Job Level (Sample values are Director, Manger, Supervisor, Individual Contributor etc.). This maps to field “jobLevel”
    4. Regular Temporary ( Sample values are Regular, Temporary etc.). This maps to field “regularTemporary

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

4. Configure RBP permissions rules & roles to apply to position objects. Target populations of positions can be defined with position attributes, once you enable a relevant permission for the role such as Succession Planning.

                1. Create permission groups and permission roles as per customer needs
                2. Assign relevant Succession Permissions from “Succession Planners” permission list in RBP
                3. Select “Miscellaneous Permission” from the left panel of Permission settings and assign permission on the Position object. These include:

             

Permission Group

Description

Value

Visibility 

Controls if the role has permission to view the position history

View Current

View History

Actions

Controls ability to add / edit / delete positions (note: this doesn’t allow delete / edit to 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

Recommended Misc. 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

MDF1.png

5. Select which position fields to present (read-only) in the popup dialog on the succession org chart, for users that do not have direct RBP permission to view or edit position fields. To achieve this go to Admin Tools > Org Chart Configuration > Position Dialogue and select the position attributes

MDF2.png

6. Select which position fields to present in the position information portlet for the profile/scorecard (if any), by going to Admin Tools > Configure Employee Files > {Profile} > Insert Portlet > Position

7. If migrating from legacy Succession position model, rebuild ad hoc reports with the “Succession planning by EC position” family of report builder views. 

8. Position Management when customer has an Employee Central license has many different configuration settings. Please refer to EC Position Management implementation guide for the      same.

The following table summarizes the key differences in configuration while configuring MDF Positions with or without Employee Central

Succession with EC

Succession without EC

EC Only

Add Position to the “jobInfo” HRIS element

Not required

Add Position to the “jobInfo” HRIS element

Permission “Manage Position” in RBP permission settings

“Manage Position” is unavailable in RBP

Permission “Manage Position” in RBP permission settings

Set “Incumbent” field to Invisible

Set “Incumbent” field to Visible

Set “Incumbent” field to Not Visible

Set “PositionTitle” to Visible

Set “PositionTitle” to Visible

Set “PositionTitle” to Not Visible

Set “Criticality” to Visible

Set “Criticality” to Visible

Set “Criticality” to Not Visible

Set “targetFTE” to Visible

Set “targetFTE” to Not Visible

Set “targetFTE” to Visible

Set “externalName” to Visible

Set “externalName” to Not Visible

Set “externalName” to Visible

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 NotVisible

Can set MultipleIncumbentsAllowed field to Visible

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

Succession Management MDF Position configuration , KBA , LOD-SF-SCM , Succession Management , How To

Product

SAP SuccessFactors HCM Suite 1605