Study guide
12.4 Terminations with Position Management and Position Workflows
SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations
1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources
2 Chapter 2: Security, Proxy, and System Administration
2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager
3 Chapter 3: User Experience Configuration
3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations
4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework
4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security
5 Chapter 5: Business Rules
5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices
6 Chapter 6: Foundation Objects and Corporate Data Models
6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects
7 Chapter 7: Employee Data Structures and Permissions
7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators
8 Chapter 8: Employee Transactions and Data Maintenance
8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions
9 Chapter 9: Workflows, Alerts, and Event Reasons
9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation
10 Chapter 10: Optional Employee Central Configurations
10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central
11 Chapter 11: Position Management Setup
11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions
12 Chapter 12: Position Management in the Employee Lifecycle
12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows
13 Chapter 13: Position Management Rules, Integrations, and Company Structure
13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview
12.4 Terminations with Position Management and Position Workflows
Key Takeaways Explain This Topic AI
After a termination is saved, follow-up processes run in sequence: hierarchy adaptation, matrix-to-job relationship sync, To Be Hired adaptation, and position deactivation.
If a follow-up process fails, the initiator gets an e-mail and an admin alert is created; retriggering reruns the failed and later processes.
Reassign Direct Reports According to Position Hierarchy can be No, Yes – Optional, or Yes – Always; only direct reports move, not positions.
The Deactivate Position option appears on termination only if the position has no other incumbents, no active child positions, no future right to return, and no pending workflows or requisitions.
In position workflows, use the Position Relationship approver type; Position should never be used as a Role.
Last updated: September 2026
12.4 Terminations with Position Management and Position Workflows
Quick Answer: When a termination is saved, PM runs follow-up processes : hierarchy adaptation , matrix-to-job relationship sync , To Be Hired adaptation , and position deactivation . Direct reports can be reassigned by position hierarchy . Position changes are protected by workflows , which can route to position relationships (position, parent position, grandparent position) or position-based dynamic roles .
Termination in Position Management
Terminating ends the employment and sets the employee to inactive . With Position Management, employees can be terminated from the Position Org Chart , with the reason, the date, and details such as the final salary date.
Follow-Up Processes
When a termination is saved through the UI ( Centralized Services ) and succeeds, these processes run in the background, in this order :
Hierarchy adaptation: with the position hierarchy leading, transfer direct reports according to the position hierarchy. This runs in the background when Reassign Direct Reports… is Yes – Always , otherwise synchronously.
Matrix relationships to job relationships sync: relationships of a terminated job-relationship manager move to another manager. The default is everyone to the upper manager, with options for a different manager, ending all relationships, or individual transfer.
To Be Hired status adaptation for the position.
Deactivate position , if chosen.
If a process fails , the initiator gets an e-mail and an admin alert is created, and later processes do not run . Retriggering the admin alert reruns the failed process and all later ones.
Transferring Direct Reports
In Position Management Settings > Hierarchy Adaptation , Reassign Direct Reports According to Position Hierarchy on Termination Screen :
- Option Behavior
- No (default) The termination screen does not offer transfer by position hierarchy
- Yes – Optional Transfer by position hierarchy is the default, and users can change it
Yes – Always The Transfer Direct Reports section is hidden, and users are only told that reports were reassigned by position hierarchy
Key points:
Everyone to upper manager is a user decision independent of the position hierarchy . Everyone according to position hierarchy chooses the incumbent of the next available position .
It works only if all direct reports and the manager have positions and the supervisors are in sync with the position hierarchy. Otherwise manual correction is needed.
Only direct reports are transferred, not positions. The leaver's position stays on the chart, now empty. To move positions, do it manually or with a mass change.
If the target position has several incumbents , reports go to the first incumbent the system finds .
With Automated Daily Hierarchy Adaptation , transfers made outside the position hierarchy are corrected on the next run. The threshold setting also applies.
Everyone according to position hierarchy uses the Transfer Event Reason from Position Management Settings, unless ERD is enabled .
Job Relationships for Vacant Matrix Positions
When a leaver's position is referenced by other positions' matrix relationships , the setting Synchronize Job Relationships for Vacant Matrix Positions decides:
No: the relationships pointing to the leaver are not updated . For mass positions, they move to another incumbent chosen at random.
Delimit Job Relationships: the relationships are ended . For mass positions, another incumbent is used.
To Incumbent On Next Higher Level Position: the relationships move to the next higher-level incumbent .
Deactivating the Position on Termination
With Show "Deactivate Position" Option in Employee Termination Screen = Yes , the termination screen can also deactivate the position. The field is visible and editable only if all of these hold:
- the employee has a position, and it is active
- the position has no other incumbents , now or in the future
- it has no active child positions , now or in the future
- it has no future right to return
- it is not referenced in other positions' matrix relationships in the future
- the user can edit the position's Effective Status (Correct or Insert, depending on the operation)
- it has no pending or active job requisitions (Recruiting integration)
- there are no pending workflows for the position or for Job Information referencing it
- Workflows in Position Management
A position is both a foundation object (it exists without an incumbent) and a transaction object , so it gets many updates. SAP's leading practice is to protect positions with workflows for changes, creation or copying, and position-to-Job-Information synchronization . The rules that trigger them are in Section 13.3.
Position-Based Approvers
Position Relationship approver type: the approver is the incumbent of the Position , Parent Position , or Parent Parent Position . Choose the Relationship to Approver :
- Employee Position (the subject user's position)
- Initiator Position (the initiator's position)
- Position (the Position MDF object, for workflows on the position object)
Never use Position as a Role. A position is an object instance with incumbents, not a user, so the system cannot resolve the role. Use Position Relationship instead.
For position creation , use Context = Target and Relationship to Approver = Position . Otherwise creation workflows will not reach the approver.
Dynamic Roles Based on Position
A dynamic role based on position can be used only for MDF Position workflows and uses the changed position data to resolve the approver. For example, if a position moves from the US to Canada but is still used in a US dynamic role, US approvals keep going to that position's incumbent in Canada.
It needs the Base Object field on the dynamicRole element of the Corporate Data Model . Export it in Admin Center > Import/Export Corporate Data Model , point the DTD to corporate-datamodel.dtd , add this field to the dynamicRole element, validate, and import: <hris-field max-length="128" id="baseObjectType" visibility="both">
- <label>Base Object</label>
- </hris-field>
SAP notes that customers without Provisioning use the Admin Center import, which is the only customer-accessible way.
Approver Replacement Exception
Approver replacement (Section 9.1) does not apply to workflows for the Position MDF object .