Study guide
11.6 Creating, Maintaining, Importing, and Mass-Changing Positions
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.6 Creating, Maintaining, Importing, and Mass-Changing Positions
Key Takeaways Explain This Topic AI
Positions can be created in Manage Positions, the Position Org Chart, Copy Position, Import and Export Data, My Team Positions, Joule, or Manage Data (not recommended).
Position to Job Information synchronization runs for changes made in the Position Org Chart or Manage Positions, never for changes made in Manage Data.
To synchronize imported position changes to incumbents, add a technicalParameters column with the value SYNC.
Follow-up processes after imports need an active Centralized Services HRIS Event Publishing Configuration record and the Import tab settings.
Mass Change Run updates positions through a business rule, while Mass Data Management uses a UI without rules.
Last updated: September 2026
11.6 Creating, Maintaining, Importing, and Mass-Changing Positions
Quick Answer: Administrators create positions in Manage Positions , the Position Org Chart , Copy Position , or by import . Managers create them from My Team Positions or Joule . Records are effective-dated: insert new records, correct , or permanently delete . Changes made in the Position Org Chart or Manage Positions can sync to incumbents , but changes made in Manage Data never do . Bulk updates use Import and Export Data , a rule-based Mass Change Run , or UI-based Mass Data Management .
Why a Separate Manage Positions Tool
Managing positions works like other EC objects (correct or insert effective-dated records). Manage Positions lets an administrator work with positions only through the Access Manage Positions permission, without the general Manage Data permission for all MDF objects. Other targeted permissions follow the same idea, such as Manage Sequence and Manage Mass Changes for Metadata Objects .
Ways to Create Positions
- Method Notes
- Manage Positions Admin tool for one or more positions
- Manage Data Possible, but not recommended
Position Org Chart Create Position from scratch, or Create Same-Level / Lower-Level Position from a source. The parent is defaulted, and a rule can copy attributes.
Copy Position Up to 100 at once. All attributes except the code are copied, and Set To Be Hired is hard-coded in the dialog. Needs Mass Copy of Position in Position Organization Chart .
- Import and Export Data Mass creation by CSV
- My Team Positions Managers use Create Same-Level Position (Copy Rule) or (Copy All Fields) (Section 12.3)
- Joule The same two transactional use cases
THR79's example creates Director of Marketing (DIR_MKT) under VP, Sales with To Be Hired = Yes, 40 standard hours, FTE 1, Position Controlled = Yes, plus organizational fields. It then sets a matrix relationship so the future incumbent becomes the Matrix Manager of another position's incumbent.
Maintaining Existing Positions
In Manage Positions , search the position and use Take Action :
- Make Correction
- Permanently Delete Entry: delete one history record, or the whole position if only one record remains
- Add to Transport Bundle: with the Configuration Transport Center , to move data between instances
- Insert New Record: a new effective-dated record, keeping the history
From the Position Org Chart , Show Details > Edit inserts a change, and Manage corrects or deletes. Changing the parent position changes the reporting line. When THR79 moves Account Manager, NE under Sales Director, NC , the incumbent's supervisor changes automatically, with the event reason Supervisor Change Only derived by ERD.
Synchronizing Position Changes to Incumbents
Synchronize Position to Job Information is a business rule that decides which common fields flow from a changed position to its incumbents' Job Information. Position Management Settings decide whether the sync is automatic or a user decision (Sections 11.5 and 13.2). Position sync occurs only when the position is updated from the Position Org Chart or Manage Positions. Updates through Manage Data never sync.
Importing Positions
Position is an MDF object, so use Import and Export Data : download the Position template, fill it, choose Validate , check the result in Scheduled Job Manager ( View Result ), then Import .
Include dependencies = Yes downloads a ZIP with related entities, such as Position Type, Position-Matrix Position, Legal Entity, and Division.
To sync imported changes to incumbents, add a technicalParameters column with the value SYNC (or sync) for the rows that should sync. Rows without it update the position only.
The technicalParameters field is Not Visible by default. Either add the column manually, or make the field Editable and hide it with a Field Level Override (No Access) , so the template includes it automatically.
Follow-Up Processes After Imports
These need an active Centralized Services HRIS Event Publishing Configuration record (HrisSLEventPublishConfiguration) in Manage Data with Enable Event Publish = Yes . Customers using PM before 1H 2025 already have it. Then set Position Management Settings > Import :
- Adapt Reporting Hierarchy After Position Import
- Validate Position Assignment During Job Information Import: status active, multiple incumbents, FTE capacity
- Adapt Position "To Be Hired" Status After Job Information Import
- Execute Reclassification or Transfer After Job Information Import
- Defaulting of the Manager or Position and Hierarchy Adaptation After Imports
- Execute Job Relationship Sync After Imports , and the Job Relationship on Position Assignment option
- Mass Change Run
A Mass Change Run updates many positions through a business rule . The IF selects the positions, for example in one legal entity, and the THEN sets new values, for example pay grade or location. Create it in Manage Mass Changes for Metadata Objects and assign the rule. Changes are effective-dated and can sync to incumbents (Section 13.2).
Mass Data Management for Positions
Mass Data Management is UI-based and replaces the traditional method of rules and scheduled jobs . You filter and sort positions, modify many with one request, review highlighted changes, save and share drafts, download logs, and filter by matrix relationship. Limits: 999 positions per request , Effective Date is the only mandatory filter, and up to 8 filters (Section 8.3).
- Mass Change Run Mass Data Management
- Selection Business rule IF UI filters
- Change definition Rule SET statements Editable fields in the UI configuration
- Test mode Simulate Review draft