Study guide
11.4 Configuring the Position Object
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.4 Configuring the Position Object
Key Takeaways Explain This Topic AI
The Position object is an effective-dated MDF object configured in Configure Object Definitions; each position links to a parent position whose incumbent becomes the direct manager.
Pending Data must be Yes on the Position object if workflows are used, and SAP advises triggering workflows by rules rather than object-level routing.
Position Control checks that incumbents' combined FTE does not exceed the position's FTE and blocks overstaffing.
With Position Management enabled, the incumbent field must be Not Visible; the assignment is made through the position field in Job Information.
The Position object's standard associations are parentPosition (One to One, Valid When) and positionMatrixRelationship (One to Many, Composite).
Last updated: September 2026
11.4 Configuring the Position Object
Quick Answer: Position is an effective-dated MDF object (Basic effective dating) with organization, job, and pay fields. You configure it in Configure Object Definitions : labels, visibility, defaults, custom fields, searchable fields, security, associations, the default screen, and rules. Key fields are Job Code , FTE , Standard Hours , Parent Position , To Be Hired , Multiple Incumbents Allowed , and Position Controlled .
What You Configure
In Configure Object Definitions > Object Definition > Position > Take Action > Make Correction you can:
- display or hide fields and rename labels (with translations)
- add custom fields and set default values
- configure searchable fields
- set security and associations
- assign a default screen (Configurable UI)
- assign workflows and other business rules
Custom field limits for Position: 30 custom String , 55 custom Number (mapped to Number, Boolean, Picklist, Translatable, Generic Object, Foundation Object), 20 custom Decimal , and 15 custom Date fields (Date, DateTime, Time). You get a warning at 80% of a limit and an error when exceeding it.
Object Details
- Detail Position value and guidance
- Code Position
- Effective Dating Basic
- MDF Version History Captures audit data when enabled
- Default Screen A Configurable UI
Workflow Routing Not recommended at object level . Use business rules to trigger workflows.
- Pending Data Must be Yes if workflows are used , so changes take effect only after approval
- To Do Category Read-only; Generic Object Change Requests for MDF objects
- Field Groups
Standard fields: code, external name, status, start date, and so on.
Business-relevant fields: organizational and job data shared with employees, such as Business Unit, Legal Entity (Company), Department, Job Code, FTE, Standard Hours, and Employee Class.
Position Management fields: Criticality, Position Controlled, Position Type, Target Capacity, Multiple Incumbents Allowed, To Be Hired, Parent Position, Right to Return. Some matter only for Succession.
MDF system fields: such as internalId and fields starting with mdfSystem . Do not change them or make them visible.
Custom fields.
Job Code
The Job Code field assigns the job classification. Common fields such as job title, job level, regular/temporary, employee class, and pay grade can fill in automatically. This propagation requires a business rule assigned to the jobCode field (Section 13.1).
FTE, To Be Hired, and Position Control
Target (planned) FTE is the workload of the position. An employee's current FTE follows from their hours. A 40-hour full-time employee is 1.0, while 25 hours out of 40 is 0.625 , so the position is understaffed .
Positions with no incumbent ( 0 / 1 FTE ), or with current FTE below planned, show the TBH (To Be Hired) icon if To Be Hired = Yes. A position can be marked not vacant even when understaffed.
Overstaffed means current FTE is above planned, for example 3/2 FTE.
Position Controlled (positionControlled): checks target FTE on assignment and prevents overstaffing . It is checked on hire, on MSS position or FTE changes, on History changes of position or FTE, when the position's FTE changes, and when the system searches for a position during transfer or reclassification. It also triggers stable headcount processing. SAP warns that position control can make Job Information imports slow , especially for positions with many incumbents, and recommends setting it to No in such cases.
Transition period: temporary overstaffing, for example during a handover, can be allowed globally or by position type (Section 11.5).
Standard Hours and FTE Calculation
A Calculate FTE rule on the standard-hours field in Job Information looks for standard hours from most to least specific : Job Information, Position, Job Classification, Location, Legal Entity . It then calculates FTE.
Parent Position
The higher-level position . When an employee is assigned a position, the incumbent of the parent position can become their supervisor . For Create Same-Level or Lower-Level Position , the parent is defaulted and not editable. Copy Position copies it. Technically it is a one-to-one association .
Incumbent
The incumbent field is only relevant for Succession Management . In Position Management, the assignment is made through the position field in Job Information . Visibility rules:
- Scenario Incumbent field visibility
- Position Management and Succession Not Visible
- Position Management only Not Visible
- Succession only Editable
With PM enabled, saving the object with the incumbent field Editable or Read-Only raises an error .
Other Fields
- Field Label Note
- vacant To Be Hired Shows TBH on the chart; can be updated automatically (Section 11.5)
- multipleIncumbentsAllowed Mass Position Allows more than one employee; enabled but default No
- type Position Type Changes standard behavior for groups of positions; use only if there is a business need
- Hiding External Codes
Use UI Field Renderer with displayGOWithoutExternalCode (generic objects) or displayPickListWithoutExternalCode (picklists) to show labels only.
Associations
- Name Multiplicity Destination Type
- parentPosition One To One Position Valid When
- positionMatrixRelationship One To Many Matrix Relationship For Position Composite
Parent position builds the hierarchy and defaults the parent when creating lower-level or same-level positions. Matrix relationships can sync to employees' Job Relationships and be used in RBP target restrictions. Field criteria on position fields (for example division filtered by business unit) keep positions consistent with the FO hierarchy (Section 6.4).
Security
Position is Secured = Yes , with Permission Category = Miscellaneous Permissions . Grant permissions and target criteria as described in Section 11.2, and set CREATE Respects Target Criteria as needed.
Configurable UI for Position
Manage Configuration UI (a Metadata Framework permission) creates a friendlier layout. Change labels, add or reorder fields, create groups such as Job Classification Details and Organizational Details , and set layout, visibility, required, rules, and links. Assign it as the Position object's Default Screen . It then appears in Manage Positions and in Show Details on the Position Org Chart.
Caution: the tool has no revert option . SAP advises organizing all fields and saving before deleting anything. Each new group creates a placeholder Input field, which you remove after moving fields in.