Employee Central P

Management Config
Workbook v2H

Co
Kic
Go
 Central Position
nt Configuration
kbook v2H 2024
Company:
Company ID:
Kick Off Date:
Go Live Date:
 Document History
Revision Date Summary of Changes
12/16/2019 1911 Version - updated position org chart configuration options & RBP
8/4/2020 2005 Version - update with more details on the Object page & UI worksheet
7/5/2021 2105 Version - update to Position Management settings
5/12/2022 2205 Version - update to Position Object
28th July 2023 H2 2022 and H1 2023 release updates
2/2/2024 H2 2023 release updates
1/7/2025 H1 and H2 2024 updates

Approvals
Name Title Date
ory
Revised By
P Nathan Wilkinson
ksheet Nathan Wilkinson
Nathan Wilkinson
Henriette Beek
Tanya Page
Tanya Page
Tanya Page
Iteration 2 Change
Iteration 3 Change
JUMP BACK TO TOC

Name SF Label Type Max Length

code Code String 255

externalName Title Translatable 255

effectiveStatus Status Enum 255

effectiveStartDate Start Date Date

effectiveEndDate End Date Date

type Type Generic Object

positionTitle Position Title String 255

positionCriticality Criticality Pick_list 255

positionControlled Position Controlled Boolean 255

multipleIncumbentsAllowed Multiple Incumbents Allowed Boolean 255

comment Comment String 255

incumbent Incumbent User 255

changeReason Change Reason Pick_list 255

description Description String 255

jobTitle Job Title String 255

Foundation
jobCode Job Code 255
Object

jobLevel Job Level Pick_list 255

employeeClass Employee Class Pick_list 255

regularTemporary Regular Temporary Pick_list 255

Foundation
payGrade Pay Grade 255
Object

targetFTE FTE Number 255

vacant Vacant Boolean 1

standardHours Standard Hours Decimal 255

 Foundation
company Company 255
Object

Foundation
businessUnit Business Unit 255
Object

Foundation
division Division
Object

Foundation
department Department 255
Object

Foundation
location Location 255
Object

Foundation
costCenter Cost Center 255
Object

createdBy Create By String 255

createdDate Created Date DateTime 255

lastModifiedBy Last Modified By String 255

lastModifiedDate Last Modified Date DateTime 255

parentPosition Parent Position Generic Object

Foundation
payRange Ray Range 255
Object

positionMatrixRelationship Position Matrix Relationship Generic Object

cust_

Default Screen
Searchable Fields

Busines Key Fields

Security
Security Yes
Permission Category Miscellaneous Permissions
CREATE Respects Target Criteria Yes/No
Pending Data Yes/No
Base Date Field For Blocking Date
Rules
Initialize Rules

Validate Rules

Save Rules

Post Save Rules

Delete Rules
 Customer Label (specify alternative label to "Position" if required)
Position
Visibility Customer Label Required Data Source

Editable Yes

Editable Yes

com.successfactors.fo.bean.eo.StatusEn
Editable Yes
um

Editable Yes

Not Visible No

Editable No

Not Visible No

Editable No Picklist “PositionCriticality”

Editable No

Editable

Editable No

Not Visible No list of users

Editable No picklist: ChangeReason

Editable No Yes / No

Editable No

Editable No Job Classification Foundation Object

Editable No picklist: JobLevel

Editable No picklist: EmployeeClass

Editable No picklist: RegularTemporary

Editable No Pay Grade Foundation Object

Editable No

Editable No

Editable No
Editable No Legal Entity Foundation Object

Editable No Business Unit Foundation Object

Editable No Division Foundation Object

Editable No Department Foundation Object

Editable No Location Foundation Object

Editable No Cost Center Foundation Object

Editable No

Editable No

Editable No

Editable No

Association

Read Only No

Association
Rules Decimal Precision Comments
The position code is the unique identifier for
the position. You can have the system
generate the code automatically.

This is the position title also shown in the

position organization chart. It can be
translated into other languages.

The position status indicates whether this

position is active and can be staffed and used
in processes. Setting a position to inactive is
not possible when, for example, the position
has an incumbent or active lower-level
positions are available.
The date from which the position changes
are effective in the system.

This is a technical field that could be set to

read only but must never be set to editable.

You can use position types to drive different

behavior for positions.
This is a deprecated field. Please use
externalName instead.

This field is relevant for Succession

Management only and should only be set to
visible if Succession Management is used.

This attribute controls whether the target

FTE is checked when an employee is assigned
to this position. In addition, the attribute
triggers the stable headcount processing
when an employee is assigned to a new
position during Position Transfer or Position
Reclassification.

This attribute controls whether the system

allows the assignment of more than one
employee to this position at any point in
time. In EC Position Management, we
recommend that you set this attribute to
True.

You can use this field to add comments.

This field is not relevant when Position
Management is active, it is for use in
Succession Planning without Position
Management
This field is relevant for Succession
Management only and should only be set to
visible if Succession Management is used.

You can use this field to enter a description

for the position.
This is the standard field for the job title on
job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the job

classification on job information and position
and can be included in the synchronization
between position and employee. When set,
the job classification can propagate other
job-related fields.

This is the standard field for the job level on

job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the employee

class on job information and position and can
be included in the synchronization between
position and employee.

This is the standard field for the type of

employment (regular or temporary) on job
information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the pay grade on

job information and position and can be
included in the synchronization between
position and employee.

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.

This field indicates whether anyone will be

hired for this position. It is shown on the
position organization chart if set to True.

This is the standard field for the standard

hours on job information and position and
can be included in the synchronization
between position and employee. In this case,
the employee's FTE value will be calculated
based on the standard hours inherited from
the employee's assigned position.
This is the standard field for the company on
job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the business unit

on job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the division on

job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the department

on job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the location on

job information and position and can be
included in the synchronization between
position and employee.

This is the standard field for the cost center

on job information and position and can be
included in the synchronization between
position and employee.
This field holds the user who created the
position.
This field holds the date when this position
was created.
This field holds the user who last modified
the position.
This field holds the date when this position
was last modified.
This is the higher-level position for this
position.
This is a transient field, showing the pay
range for a position.
This represents a relationship of this position
to another position of a specific job relation
type.

MDF allows additional fields to be added

(max 55). Types can be: String, Number, Auto
Number, Decimal, Boolean, Date, DateTime,
Time, Picklist, Translatable, Data Source,
Enum, Generic Object, Foundation Object,
Attachment, User, CLOB and Auto Complete
Learn More about this functionality:
Position Generic object stores all the positions defined in a company and
attributes associated to these positions.

Example of Position

Admin Center -> Company Processes & Cycles -> person(Employee Files) ->
Manage Positions
 JUMP BACK TO TOC
All rules
Iteration 2 Change
Iteration 3 Change
RULE Description Fields

JOBECODETOPOS Fields held on job code are Job Title

propagated to position when a
job code is selected

InitPosition Sets values when a position is FTE=1

created from manage position

PositionCopyOver Copies creating fields when a Legal Entity

position is created from Position Business Area
Org chart view with 'Create Peer'
or 'Lower Level position' Division
Department
Location
Cost Centre

PosToJobInfo Copies data from Position and Business Area

maps this data to the job when a Division
new position is assigned to an
employee Department
Location
Jobcode

POSAPPROVAL Sets workflow for position

approval

jobtoposition Updates position data with Location

changes to the following fields
when a change is made on the
employee using the Position
reclassification.

Accnture to provide event

reasons will trigger position
SetExtCode Sets codereclassification
of position
 Notes

Needs to set on change of jobcode

Set on the object

Set in Position Management settings

Set in Position Management settings

Set on the object

Set in Position Management settings

Set on the object

 WORKFLOW TRIGGER CRITERIA

Initaitor Change Type Field Trigger Workflow Name Workflow Step 1

Approver
Approver
Type
Type
Value
 WORKFLOW CONTENT DETAILS

orkflow Step 1 Workflow Step n Role CC Role 1 CC Role n Contributor Role 1

Edit Edit
Approver Approver Approver
Transactio Approver Transactio Approver Approver Approver
Type Type Type
n Type n Type Type Type
Value Value Value
Capability Capability
 WORKFLOW SETTINGS

After how many days

Should delegation be possible
Contributor Role 1 Contributor Role n should approver be
with this workflow
reminded to approve

Approver Approver
Approver
Type Type
Type
Value Value
General Settings
Use Position Types

Is the Position External Code Auto Generated?

Reset 'To Be Recruited' Status if Incumbent is Assigned to a Position

Set 'To Be Recruited' Status if Incumbent is Unassigned from a

Position

Set or Reset 'To Be Recruited' Status if Position 'FTE' is Changed

Set or Reset 'To Be Recruited' Status if an Incumbent's 'FTE' is
Changed

Hierarchy Adaption
Leading Hierarchy

Reassign Direct Reports According to Position Hierarchy on

Termination Screen

Default The Supervisor Or The Position In Recruit, MSS Job

Information And History
.
Threshold for running Adoption of Reporting Line and Job Relations
as a job

Event Reason for Assigning Employees to New Manager (note this is

not if you have event derivation)

Yes if you want the system to automatically adapt the hierarchies

using a daily job if they are not in sync.
Note: This option can only be used if the position hierarchy is the
leading hierarchy.

Synchronization
Position to Job Inforrmation Synchronisation
Rule for Synchronising Position to Job Information

Rule for Synchronising Job Information to Position

Search for Position in Position Reclassification

Search for Position in Position Transfer

Stable Headcount Area for Position Control Mode

Automated Position to Job Info Synchronisation

Yes/No
Offset in Days
Matrix Synchronization
Synchronize positon matrix relationship to job relationship of
incumbents
Synchonize job relationships for vacant matrix positions

Automated position matrix relationship to job relationship

synchronization
Yes/No
offset in days

UI Customizing
Rule for Defining Copy-Relevant Position Fields

Respect Workflow at Copy Position in Position Organisational Chart

Use Company Filter for Positions in Manager Self-Service Job

Information, History, and Quick Actions

Allow Selection of only Positions that have Status “To Be Hired” in

Manager Self-Service Job Information, Hire, and Quick Actions

Display “Incumbent of Parent Position” in Hire, MSS Job

Information, History, and Quick Actions

Show the ‘Deactivate Position’ option on the Employee Termination

Screen

Right to Return
Right to return for leave of absence
Unassigned from Position

Create Right to Return

right to return for global assignment

Unassigned from Position

Create Right to Return

Event Reason for unassigned Position

Event Reason for assign Position

Transition Period

Use Transition Period

Period
Unit
Import
Adapt Reporting Hierarchy During Position Import

Adapt Hierarchy During import of Leave Of Absence Records

Validate Position Assignment During Job Information Import

Adapt The Position 'To Be Recruited' Status During Job Information

Import

Execute Reclassification Or Transfer During Job Information Import

Adapt The Non-Leading Hierarchy

Event Reason For Supervisor/Position Assignment Change

Recruitment Integration
Raise Events
Use Recruitment Integration
Rule for deriving Requisition Template ID
Rule for mapping fields between position and requisition
Information
If you want to use Position Types you need to set the value to Yes.

If you are generating the position external code automatically you need to set the field to 'Yes'.

Choose Yes if you want to set or reset the position To Be Recruited status if the position FTE is changed.
Choose Yes if you want to set or reset the position To Be Recruited status if an incumbent's FTE is changed in
the Manager Self Service (MSS) or Job Information Import. If the Position assignment changes, this setting is
not relevant.

Information
You can define which hierarchy is leading in the system. If the leading hierarchy is changed, the changes are
automatically adopted in the other hierarchy.
No: This is the default. When terminating a manager, the Transfer Direct Reports section does not include
transferring directs according to the position hierarchy.
Yes - Optional: If this is chosen, the Transfer Directs According to Position Hierarchy option is set as the default
for the Transfer Direct Reports section on the Termination screen. The user can accept this default or change
it.
Yes - Always: This will completely hide the Transfer Direct Reports section on the Termination screen. A text
will inform the user that the direct reports were reassigned based on the position hierarchy. The user will not
be able to select another option.
Note: This option can only be used if the position hierarchy is the leading hierarchy.

If the position hierarchy is the leading hierarchy or if there is no leading hierarchy, the system defaults the
supervisor when selecting a position. If the reporting hierarchy is the leading hierarchy, the system defaults the
position when selecting the supervisor. Select Yes to switch on defaulting.
Once the number of incumbents of either child positions or matrix positions hits this number, the updates to
the hierarchy or job relation will be carried out as a scheduled job. If the number falls below the number, then
the update will happen immediately. Please note number must be between 5-20, otherwise it will display an
error. Also, this setting is only relevant if the position hierarchy is the leading hierarchy.

The event reason you select here is used:

- When assigning employees to a new recruit
- When assigning employees to the higher-level manager after the current manager was transferred to another
position

Yes/No
Offset in Days

Information
Use this option to determine how synchronisation of incumbents in the position organisational chart is carried
out.

- User Decision: If you choose this, a popup appears after every position change asking whether the
incumbents should be synchronised.
- User Decision If Required: If you choose this, a popup only appears if synchronisation-relevant fields are
being changed.
- Automatic: If you choose this, synchronisation takes place in the background.
- Never: If you choose this, no synchronisation takes place.
The rule you select here is used when the position is changed in the Position Organisational Chart or via import
and the changes are synchronised to the incumbent's job information

The rule you select here is used to determine which common fields between Job Information and Position are
synchronised when job information is changed and this leads to a position reclassification or position transfer.

Choose Yes if you want the system to first search for a position that has status To Be Hired before creating a
new position.
Choose Yes if you want the system to first search for a position that has status To Be Hired before creating a
new position.
You can define an area in which the headcount should keep stable in case an employee is assigned to a new
position in a reclassification or transfer.
Note that the headcount will only be adopted if the "leaving" position is subject to position control.
Choose “Yes” if you want the system to automatically synchronize Position to Job Information using a job if
they are not in sync.

Information
You can use this option to determine whether and how the synchronization of position matrix relationships
and job relationships is executed.

The possible options are:

- “Always”: Synchronization takes place every time when the position assignment of the employee is changed
or when the matrix relationships of the position are changed.
- “Never”: No synchronization takes place
- “Only when position assignment of the employee is changed”: Position matrix relationships are only
synchronized to job relationships of incumbents when the position assignment of the employee is changed.
- “Only when Matrix Relationships of the position are changed”: Position matrix relationships are only
synchronized to job relationships of incumbents when the matrix relationships of the position are changed.
You can use this option to determine how to synchronize job relationships for vacant matrix positions. You can
use one of the following options:

“No” :
- When the setting is set to No, the options for transferring job relationships are shown on the Termination and
Internal Hires pages.
“Delimit Job Relationships” :

- When this setting is set, the options for transferring job relationships are no longer shown on the Termination
and Internal Hire pages. This setting checks if there is another incumbent available for a given matrix position,
for example, if the job relationship manager's employment is terminated.
- If there is another incumbent available, this user is assigned as the new job relationship manager.

- If there is no other incumbent available for this matrix position, then the given job relationship type is
delimited (this means that the system sets an end date for the job relationship that is equal to the termination
date.)

“To Incumbent On Next Higher-Level Position” :

- When this setting is set, the options for transferring job relationships are no longer shown on the Termination
and Internal Hire pages. This setting checks if there is another incumbent available for a given matrix position,
for example, if the job relationship manager's employment is terminated.

- If there is another incumbent available, this user is assigned as the new job relationship manager.

- If there is no other incumbent available for this matrix position, the search proceeds to the higher-level
positions of the user whose employment is terminated until the system finds an incumbent. This incumbent is
assigned as the new job relationship manager.

Choose “Yes” if you want the system to automatically synchronize Position Matrix Relationships to Job
Relationships using a job if they are not in sync.

Information
The rule you select here is used to determine which position fields are copied when you create a new position
in the position organisational chart.
You can use this option to respect configured workflows while copying a position in the position organisational
chart. If set to No, the copied positions are created without respecting any workflow. Note: For each new
position a separate workflow request will be created.
If you want to filter positions by company in the Manager Self Service (MSS) job information and history you
need to set the value to Yes. If you select No, the positions will still be filtered by company in the recruitment
process.
If you only want to show positions that have status To Be Hired in the Manager Self Service (MSS) Job
Information UI and Hire UI, you need to set the value here to Yes. Even if you do this, all positions, whatever
their status, are shown in the Job Information History UI.
Choose Yes to display the Positions Under Employee field in New Recruit, Manager Self Service (MSS) Job
Information, and History UI. Choosing an employee in this field ensures that the Position field provides only
lower-level positions of the position of the chosen employee. Choose No to hide the Positions Under Employee
field, that means, all positions are offered in the Position field.

Information
The rule you select here is used to decide whether the employee shall be unassigned from the position in the
leave of absence period

The rule must have 'Job Information' as base object and 'Position Management Decision' as parameter with
code 'Decision'.

The rule you select here is used to decide whether a Right to Return to the employee's position shall be
created in the leave of absence period

The rule must have 'Job Information' as base object and 'Position Management Decision' as parameter with
code 'Decision'.

The rule you select here is used to decide whether the home employee shall be unassigned from the position
in the Global Assignment period or not.

The rule must have 'Job Information' as base object and 'Position Management Decision' as parameter with
code 'Decision'.

The rule you select here is used to decide whether a Right to Return to the home employee's position shall be
created in the Global Assignment period or not.

The rule must have 'Job Information' as base object and 'Position Management Decision' as parameter with
code 'Decision'.

The event reason you select here is used for assigning the home employee from the position in the Global
Assignment period.
The event reason you select here is used for assigning the home employee again to the position after the
Global Assignment period.
Information - You can use the options on this tab to determine whether a transition period for positions is
allowed or not. With a transition period, you can define a period in which a position can be overstaffed by
incumbent or FTE. This means that you can assign a successor to a position while the employee who is
leaving the position is still assigned even if the position is overstaffed as a result. You can either switch on
this feature globally for all positions with this option or you can use the options in the Position Type if the
feature should only be relevant for a group of positions.

If you want to use transition periods, you need to set the value to Yes.

Information
Choose Yes if you want the system to trigger adaptation of the reporting hierarchy when you are importing
positions.
Note that this option is only relevant if the position hierarchy is the leading hierarchy. If you have chosen No
the system will not respect the setting in field Adapt Reporting Line if Position Hierarchy is changed? of an
assigned position type if the position hierarchy was changed via a position import.

Choose Yes if you want the system to trigger adaptation of the non-leading hierarchy when you are importing
Leave of Absence records.
Note that this option is only relevant if you use Right To Return and if the employee will be unassigned from
the position in the Leave of Absence period.

Choose Yes if you want the system to validate the position assignment when you are importing Job History data.

Choose Yes if you want the system to trigger adaptation of the To Be Recruited status of the affected positions
when you are importing Job History data.
Note that this option is only relevant if you have specified that the To Be Recruited status of a position has to
be adapted if an employee is assigned to a position, if the employee's assignment is removed and/or if the
incumbent's FTE is changed.

Choose Yes if you want the system to trigger a Position Reclassification or Transfer when you are importing job informatio
Choose Yes if you want the system to trigger adaptation of the non-leading hierarchy when you are importing
Job History data.
Note that this option is only relevant if you have specified a leading hierarchy.
The event reason you select here is used when the supervisor assignment (if the position hierarchy is leading)
or the position assignment (if the reporting hierarchy is leading) is changed during the import of Job History
data. If you do not select an event reason here, the event reason from the Job Information import file will be
reused.
Note that this option is only relevant if you enter Yes in the Adapt The Non-Leading Hierarchy field.

Information
Options Client Option SAP Leading Practice
Yes/No No

Yes/No Yes
Never/Always/Only if planned Only if planned FTE value is reached
FTE value is reached

Never/Always/Only if current Only if current FTE is below Planned

FTE is below Planned value is value is reached
reached
Yes/No Yes
Yes/No Yes

Options Client Option Options

Position/Reporting/None Position

No Yes - Always
Yes - Optional
Yes - Always

Yes/No Yes

Yes
Offset in Days = 0

Options Client Option Options

User/User Decision if Always
Required/Always/Never
PosToJobInfo PosToJobInfo

JobinfoToPos JobinfoToPos

Yes/No No

Yes/No No

Refer to instance for drop down No Selection

list

Yes/No Yes
Offset in Days = 0

Options Client Option Options

Always Always
Never
Only when positoin assignment
of the employee is changed
Only when matrix relationships
of the position are changed
No No
Delimit Job Relationships
to Incumbent on next higher
level position

Yes/No Yes
Offset in Days = 0

Options Client Option Options

PositionCopyOver PositionCopyOver

Yes/No No

Yes/No Yes

Yes/No Yes

Yes/No No

Yes/No No

Options Client Option Options

Rule Rule

Rule Rule

Rule Rule

Rule Rule

Event Reason Event

Event Reason Event

Options Options

Yes/No Yes
3
Months
Options Client Option Options
Yes/No Yes
It is recommended to set this to No
during the initial import at go live

Yes/No Yes
It is recommended to set this to No
during the initial import at go live

Yes/No Yes
It is recommended to set this to No
during the initial import at go live
Yes/No Yes
It is recommended to set this to No
during the initial import at go live

Yes/No No
Yes/No Yes

Options Client Option Options

Yes/No No
Yes/No Yes
Rule
Rule
UI Default Screen UI

Manage UI Rule - Name Purpose

onInitUI Rules

onInsertUI Rules

onLoad Business Rules

Field Level Rules

Miscellaneous Permissions - Position Object Employee Manager
View Current X
Create X
Insert
View History (also need Metadata Framework that give Admin tools
link in UI) X

Correct (also need Metadata Framework that give Admin tools link
in UI)
Delete
Field Level Overrides
Please define position field to be read on invisible
Respects Target Criteria Only Position
below their role

Manage Position Employee Manager

Access Position Organization Chart X
Change Display Date of Position Organization Chart X
Mass Copy of Position in Position Organization Chart
Option to move Position to New Supervisor on Job Info Change X
View Job Requisition in Position Organization Chart X
Create Job Requisition in Position Organization Chart X
Select Job Requisition Template in Position Organization Chart
Create Fieldglass Job Requisition in Position Organization Chart
Create Position from Position Organization Chart X
Access Position Management Settings in Admin Center
X
HR Admin Recruiter Role
X X X
X X
X X

X X X

X X

Within their taget All

group

HR Admin Recruiter Role

X X X
X X X
X
X X
X X X
X X
X X X

X X X
X
X
 MassChangeJobConfiguration
ExternalID
Name
TargetGOType Position
minRecordLimitToTriggerJob

Field configurations
FieldDefinition defaultFilter filterable editable
Yes/No Yes/No
 Employee Central Quick Action Template(Employe
Iteration 2 Change
Iteration 3 Change

Quick Action Use Case

Use Case Code Base Object Status
Name Identifier

Create
Creae Same- CREATE_NEW_POSITI
Same-Level Position
Level ON_FROM_GIVEN_P Active
Position Information
Position OSITION
(Copy Rule)

Employee Central Quick Actions for Positions | SAP Help Portal

ntral Quick Action Template(EmployeeCentralQuickActionTemplate)

Field1 Field2 Field3 Field4 Field5 Field6 Field7 Field8

standardHou
jobCode targetFTE
rs
Customer
Comments
© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for

any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice.

Some software products marketed by SAP SE and its distributors contain

proprietary software components of other software vendors. National product
specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any kind, and
SAP or its affiliated companies shall not be liable for errors or omissions with
respect to the materials. The only warranties for SAP or SAP affiliate company
products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein
should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an SAP
affiliate company) in Germany and other countries. All other product and service
names mentioned are the trademarks of their respective companies.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices