Study guide
12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return
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.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return
Key Takeaways Explain This Topic AI
With the position hierarchy leading, changing a position's parent changes the incumbent's supervisor, and changing the employee's position defaults the next available supervisor.
Changing the supervisor directly in Job Information causes inconsistency; SAP recommends making manager changes in Manage Positions.
Position Transfer relates to a manager change, while Position Reclassification relates to changed job attributes such as location or cost center.
In a shared position, reclassification does not change the position; the system looks for or creates a peer position.
Right to Return holds a position for an employee on a leave of absence or global assignment.
Last updated: September 2026
12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return
Quick Answer: Job Information is where employees are assigned to positions . With the position hierarchy leading , move positions to change reporting lines, and do not edit supervisors directly in Job Information. When incumbents' job data changes, the system may run a Position Transfer (manager change) or Position Reclassification (attribute change), guided by the Job Information to Position sync rule. Right to Return keeps a position for employees on leave or global assignment.
- Ways to Change an Incumbent's Job Information
- MSS: Take Action > Change Job and Compensation Info , or the pencil icon on the block
- Job Information History: Edit, Delete, or Insert New Record in the past, present, or future
- Position Org Chart: select the incumbent, open the profile preview, then All Actions
- Add New Employee for new hires
- Import Employee Data with the Job Information entity
When editing, you pick a position from the list (optionally only vacant ones) and can check its place in the hierarchy with the org chart icon. History is for administrators. Inserting requires an event and event reason. Validations such as position status, multiple incumbents, and FTE run through Centralized Services for History edits and imports.
Manager Changes with the Position Hierarchy Leading
Parent position changes (in the position record or Position Org Chart) change the supervisor .
Supervisor changed directly in Job Information: the position hierarchy is not updated correctly, which creates inconsistency between the Position Org Chart and the reporting structure.
Position changed in Job Information: the supervisor defaults to the next available supervisor in the position hierarchy.
Moving a Position Under a New Manager
When the supervisor is updated in Job Information, users can choose to move the assigned position below the new manager's position . With Yes , the position moves with all lower-level positions and incumbents , and for mass or shared positions all incumbents move. With No , only the employee moves. Prerequisites:
the permission Option to Move Position to New Manager on Job Info Change (SAP's permission list also calls it …to New Supervisor… ; see Section 11.2)
- View Current on the Position object
- the position hierarchy leads
- the employee has a position that is not being changed
- the new supervisor has a position
- the change is made in MSS
- the supervisor field is part of the job information section in BCUI
SAP recommends making manager changes for a position in Manage Positions , not from the incumbent's Job Information, as the Position Management IDP documents.
Position Transfer and Reclassification
Synchronize Job Information to Position is a rule that decides which common fields flow from Job Information to the position. It applies only when the system treats the change as a Position Transfer or Position Reclassification .
Position Transfer (Manager Change)
When the employee's manager changes, the employee needs a position under the new manager. By default, the system searches for a matching To Be Hired position below the new manager. If one exists, the employee is assigned to it. If none exists, a new position is created below the new manager's position. The transferring employee's direct reports then report to the previous manager . If another position was selected manually, no transfer happens , and the previous position is not automatically marked To Be Hired.
Position Reclassification (Attribute Change)
The incumbent stays in the same position, but its attributes change, for example location or cost center:
Single incumbent: the position record is updated from the Job Information data, using the Job Information to Position sync rule.
Shared position (several incumbents): the position is not changed . The system searches for a To Be Hired peer position under the same parent. If one matches, the employee is assigned. Otherwise a new peer position is created. Direct reports and lower-level positions are not affected.
The system matches only fields in the sync rule. Higher-impact changes such as Department or Business Unit should flow from the position to the incumbent, not the other way around. Managers should make volatile, lower-impact changes such as location or cost center through self-service.
Concurrent Employment and Global Assignments
Concurrent employment: a person holds more than one active employment. In Position Management they have a primary position and secondary positions .
Global assignment: manages expatriates with home and host assignments. Prerequisites include:
enabling Global Assignment Management in Manage Employee Central Settings
enabling globalAssignmentInfo fields ( assignment-type, planned-end-date, company, end-date, start-date ) and the global_assignment_type picklist (short-term, long-term)
adding the events Add Global Assignment (GA) , End Global Assignment (EGA) , Obsolete (OGA) , Away on Global Assignment (AGA) , and Back from Global Assignment (BGA) with matching event reasons
adding the employee-status values Discarded and Dormant . Dormant is recommended for an employee away on a global assignment.
Global Assignment Details can be shown on the position card.
Right to Return
Right to return guarantees an employee on a global assignment or leave of absence a way back to their original position. The position shows a right-to-return icon, and details appear in the side panel.
Leave of absence: the leave unassigns the position and creates a right to return tag. On return, the employee goes back to the original position.
Global assignment: creating the assignment automatically updates the home assignment and creates the tag, so the position is held in the home country.
Configure rules and event reasons in Position Management Settings > Right to Return (Section 13.3).
Considerations:
Changing the leave or assignment start date also changes the start date in the Right to Return object.
An employee unassigned from a position still reports to the same supervisor .
If a supervisor is unassigned, their direct reports report to the next available manager in the position hierarchy for the duration, if the position hierarchy leads. Otherwise the reporting line is unchanged.
If the supervisor's leave or assignment dates change later, the hierarchy is not reset to the new start date.
Transition Periods
A transition period lets a successor be assigned before the leaver departs, so the position is temporarily overstaffed by incumbent or FTE. Set it in Position Management Settings > Transition Period with a Period and a Unit (days or months), globally or through position types .