Study guide
11.5 Position Management Settings
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
11.5 Position Management Settings
Key Takeaways Explain This Topic AI
Position Management Settings needs the permissions Manage System Properties > Manage Employee Files and Manage Position > Access Position Management Settings.
The General tab controls position types, external code generation by onSave rule, and To Be Hired status adaptation.
Hierarchy Adaptation sets the leading hierarchy (Position, Reporting, or None); the job-run threshold must be between 5 and 20.
Position to Job Information synchronization can be Automatic (recommended), User Decision, User Decision If Required, or Never.
The Check Tool includes Position Management checks such as mandatory settings, the position code rule, the sync rule, and the Pending Data flag.
Last updated: September 2026
11.5 Position Management Settings
Quick Answer: Position Management Settings controls PM behavior without back-end access. The General tab covers position types, code generation, and To Be Hired adaptation. Hierarchy Adaptation sets the leading hierarchy and manager defaulting. Synchronization covers position and Job Information sync, Matrix Synchronization covers matrix and job relationships, and UI Customizing covers filtering and copy rules. Transition Period , Right to Return , Integration , and Import complete the tool.
Access requires Manage System Properties > Manage Employee Files and Manage Position > Access Position Management Settings in Admin Center .
General Tab
Use Position Types: define different behavior for groups of positions (defaults Regular and Shared ), for workflows, reporting-line adaptation, or transition periods. Set it to No if all positions should behave the same.
Position External Code Generation by onSave rule: Yes means codes are generated by a business rule (Section 13.3).
To Be Hired Status Adaptation: automatically set or reset To Be Hired when an incumbent is assigned or unassigned, when the position's FTE changes, or when an incumbent's FTE changes. THR79's settings are Set TBH if incumbent is unassigned: only if current FTE is below planned value and Reset TBH if incumbent is assigned: only if planned FTE is reached , with Yes for both FTE options.
Hierarchy Adaptation Tab
Leading Hierarchy:
Position Hierarchy (default and recommended): position-to-position relationships determine and update the reporting line.
Reporting Hierarchy: manager-to-direct-report relationships lead.
None: neither hierarchy updates when the other changes.
Reassign Direct Reports According to Position Hierarchy on Termination Screen and Internal Hire Screen: No, Yes – Always (leading practice), or Yes – Optional (Section 12.4).
Defaulting of the Manager or the Position on the Hire UI, MSS Job Information, and Job Information History: with the position hierarchy leading, set Yes , so selecting a position defaults the manager. No lets the hierarchies diverge.
Threshold for Running Adoption of Reporting Line and Job Relationships as a Job: when the number of incumbents of child or matrix positions reaches the threshold ( 5 to 20 ), updates run as a scheduled job . Below it, they run immediately. 0 means never as a job. It applies only when the position hierarchy leads.
Automated Daily Hierarchy Adaptation: a daily job checks whether each position-assigned employee's supervisor matches the position hierarchy and fixes it. Changes effective today sync immediately, future-dated ones sync on their date, and past-dated ones sync at the next run, but with the job's date as the effective date. It cannot be set to Yes unless a daily Position Management Daily Hierarchy Adaptation job exists (Scheduled Job Manager).
Synchronization Tab
Position to Job Information Synchronization: Automatic (recommended, runs in the background), User Decision (a pop-up after every change), User Decision If Required (a pop-up only when position and incumbents are out of sync), or Never .
Rule for Synchronizing Position to Job Information and Rule for Synchronizing Job Information to Position (Section 13.2).
Search for Position in Position Reclassification / Position Transfer: Yes means the system first looks for a To Be Hired position before creating one.
Stable Headcount Area for Position Control Mode: SAP recommends No Selection .
Automated Position to Job Information Synchronization: with the Position to Job Information Synchronization job in Scheduled Job Manager, set Use Automated Job to Yes so future records stay in sync. Offset in Days is 0 to 30 . With 0 or blank, the job considers only records starting on the run date.
Matrix Synchronization Tab
Synchronize Position Matrix Relationships to Job Relationships of Incumbents: Always (recommended), Never, only when the position assignment changes, or only when the matrix relationships change.
Synchronize Job Relationships for Vacant Matrix Positions:
No: transfer options appear on the Termination and Internal Hire pages.
Delimit Job Relationships: if no other incumbent exists, the relationship ends on the termination date.
To Incumbent On Next Higher-Level Position: the search moves up the hierarchy until an incumbent is found.
Automated Position Matrix Relationship to Job Relationship Synchronization , with an offset of 0 to 30 days.
UI Customizing Tab
Rule for Defining Copy-Relevant Position Fields: a Default Position Attributes rule for lower-level and peer positions (Section 13.1).
Respect Workflow at Copy Position in Position Organizational Chart: usually No .
Use Company Filter for Positions in MSS Job Information, History and Quick Actions: filters positions by legal entity. The Hire process always filters by company.
Allow Selection of only Positions that have Status "To Be Hired" in MSS, Hire, and Quick Actions. This does not apply to Job Information History.
Display "Enter Manager to Filter Positions" field in Hire, MSS, History, and Quick Actions.
Show "Deactivate Position" Option in Employee Termination Screen (Section 12.4).
Transition Period Tab
Use Transition Period = Yes , with a Period and a Unit (days or months), allows temporary overstaffing by incumbent or FTE, for example a successor starting before the leaver departs. It can be global or by position type. If multiple incumbents are allowed or FTE is shared, Position Controlled must be Yes.
Other Tabs
Right to Return: rules and event reasons for leaves of absence and global assignments (Section 12.2).
Integration: Recruiting integration and rules (Section 13.4), and Raise events in Intelligent Services when positions are created or updated.
Import: follow-up processes after imports (Section 11.6). Often set to No during the initial load for performance, then Yes.
Position Management Checks in the Check Tool
Under System Health , choose the application Position Management . The tool defaults to errors and warnings; add Success to see all checks.
- all mandatory PM settings are made
- matrix picklist values match the job relationship picklist
- the position code generation rule is consistent with the settings and the code field's editability
- the Position to Job Information sync rule does not set supervisor , or company when the company filter is used
- Pending Data is active on the Position object
- mandatory fields are filled on active positions
the Recruiting mapping rule fields exist in the Job Requisition OData object, using dot notation such as hiringManager.usersSysId