Study guide
13.2 Synchronization Rules and Mass Change Runs for 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
13.2 Synchronization Rules and Mass Change Runs for Positions
Key Takeaways Explain This Topic AI
The Position to Job Information sync rule is created with Synchronize Position Changes to Incumbents and registered in Position Management Settings.
Position synchronization never works when a position is updated through Manage Data.
Company should be mapped in the sync rule only when the company filter for positions is set to No.
In the sync rule, foundation objects must follow hierarchy order: Business Unit, then Division, then Department.
A Mass Change Run uses an Update Rule for Mass Change Run with SET statements only, and can Simulate before it Runs.
Last updated: September 2026
13.2 Synchronization Rules and Mass Change Runs for Positions
Quick Answer: Maintaining the same fields on positions and on incumbents is cumbersome, so Position Management synchronizes them with rules. Position → Job Information uses Synchronize Position Changes to Incumbents . Job Information → Position uses Synchronize Incumbent's Changes to Position . Both are registered in Position Management Settings > Synchronization . For bulk updates, a Mass Change Run applies an Update Rule for Mass Change Run to many positions and can Simulate first.
Synchronizing Position Changes to Incumbents
Administrators define which common fields flow from the Position object to the incumbents' Job Information when a position changes in the Position Org Chart (Edit or Manage) or in Manage Positions . Position synchronization never works when the position is updated through Manage Data.
Setup steps:
Create a rule with the scenario Synchronize Position Changes to Incumbents , for example Position_to_JobInfo_Sync .
Set the fields to sync in the THEN. A good description is "Assigned to jobInfo, Position field, onChange; and to Position Management Settings/Synchronization".
Register it in Position Management Settings > Synchronization > Rule for Synchronizing Position to Job Information .
Choose Position to Job Information Synchronization : Automatic , User Decision , User Decision If Required , or Never (not recommended).
The rule should also be triggered when the position field changes in Job Information , so a newly assigned employee receives the position's data.
Field Order
Field order is essential , especially for foundation objects. Because Business Unit is above Division, and Division above Department, the rule must set Business Unit, then Division, then Department .
Fields Not to Use in the Position → Job Information Rule
The system checks for these and shows an error:
- Company (see below)
- any attachment field
- Position
- sequence number
- workflow configuration
- start date
- event reason
- FTE
- effective latest change
- Supervisor
- Matrix Manager
- PositionCostAssignmentItems
Company/Legal Entity may be mapped only if Use Company Filter for Positions in Manager Self-Service Job Information, History, and Quick Actions is No (KBA 2386613).
Worked Example
With User Decision If Required , edit Sales Director, NE in the Position Org Chart effective today and change the job title to Sales Director, North East Area . A Synchronize Incumbents dialog lists the incumbents, and you confirm with Yes. The incumbent's Job Information and profile header show the new title. Setting the option back to Automatic removes the dialog.
Synchronizing Position Imports
Imports through Import and Export Data do not sync by default . Add a technicalParameters column with SYNC (or sync) for the rows to synchronize. Other rows update the position only. The field is Not Visible by default. Either add the column by hand, or make it Editable and hide it with a Field Level Override (No Access) so the template includes it.
Synchronizing Incumbent Changes to the Position
The reverse rule, Synchronize Incumbent's Changes to Position , is less common . SAP recommends it only for strict 1:1 employee-to-position setups . It lets managers change volatile, lower-impact data at employee level, for example Department, Cost Center, Location, and Job Code , which then updates the position. It applies only to changes the system treats as Position Reclassification or Position Transfer .
Fields not to use: attachments, Matrix Relationships , PositionCostAssignmentItems, Position Type , Source of Creation , Position Controlled , To Be Hired , and Workflow Configuration . Change Reason, Criticality, Higher-Level Position, Incumbent, Multiple Incumbents Allowed, Pay Range, and Status are excluded from the THEN by design.
The Mass Change Run
Manage Mass Changes for Metadata Objects updates many positions at once with a rule that defines both the target positions and the changes .
Permissions: the Mass Change Run object is secured by default . Grant Miscellaneous Permissions > Mass Change Run (View, Edit, Import/Export) and Administrator Permissions > Metadata Framework > Manage Mass Changes for Metadata Objects .
Fields of a Mass Change Run:
- Field Meaning
- Code / Name Identifier and translatable name
- Object Type To Be Changed Position, or a time object
Change Date Effective date. All records valid from this date (active, inactive, pending) that match the rule's IF are included.
Synchronize To Incumbents Whether to sync. Only fields in the registered Position → Job Information rule sync.
Select and Update Rule A rule from Update Rule for Mass Change Run . IF limits the objects, and THEN supports only SET statements.
- Execution Mode Simulate (nothing saved; results in the log) or Run
- Execution Status / Log Scheduled, In Progress, Executed, Failed, and the details
SAP recommends Use Rule Cache = Yes . The useRuleCache field is hidden by default, so set it to Editable in Configure Object Definitions > Mass Change Run .
THR79 example: a rule selects Engineer positions in the USA and sets the position title and job title to Software Engineer . Create PosMassChangeRun (Position, today, Synchronize To Incumbents = Yes, the rule, Simulate , Use Rule Cache = Yes). Refresh until Success , check the log CSV, switch to Run with Make Correction , and verify: five positions updated, The record was inserted successfully .