Study guide
13.1 Position Management Rule Scenarios and Rules for Position Data Entry
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.1 Position Management Rule Scenarios and Rules for Position Data Entry
Key Takeaways Explain This Topic AI
Most Position Management rule scenarios are registered in Position Management Settings before they take effect.
Propagation from Job Classification to Position uses Rules for MDF Based Objects (base object Position, purpose Evaluate), assigned to the jobCode field.
Default values for new positions come from a rule under Initialize Rules on the Position object, or from the field's Default Value for simple data types.
The Define Copy-Relevant Position Fields rule works for Create Lower-Level and Create Same-Level Position, but not for Copy Position.
Parent Position must never be included in the copy rule, because the system derives it from the hierarchy.
Last updated: September 2026
13.1 Position Management Rule Scenarios and Rules for Position Data Entry
Quick Answer: Position Management uses application-specific rule scenarios (sync, copy-relevant fields, mass change, right to return, Recruiting, and Fieldglass), most of which are registered in Position Management Settings . It also uses general Rules for MDF Based Objects with Position as the base object for propagation, defaults, code generation, workflows, and alerts. Three rules automate data entry: Job Classification → Position propagation , defaults on creation , and Default Position Attributes for new lower-level or same-level positions.
How Rules Work in Position Management
Business rules add logic: if this data changes in a certain way, the system reacts in this way . They are not delivered out of the box , because requirements vary. As a reminder, a rule has IF conditions (or Always True ), THEN statements, optional ELSE IF and ELSE (catch-all) branches, an assignment , and an event . For example, a propagation rule assigned to the Position object's jobCode field fires onChange , before the position is saved.
Position Management Rule Scenarios
Scenario Purpose Where it is registered
Synchronize Position Changes to Incumbents Sync position changes to incumbents' Job Information. Also trigger it when the position field changes in Job Information. PM Settings > Synchronization > Rule for Synchronizing Position to Job Information
Synchronize Incumbent's Changes to Position Sync Job Information changes back to the position PM Settings > Synchronization > Rule for Synchronizing Job Information to Position
Define Copy-Relevant Position Fields Default values for new lower-level or same-level positions and the Create Same-Level Position (Copy Rule) Quick Action PM Settings > UI Customizing > Rule for Defining Copy-Relevant Position Fields
Update Rule for Mass Change Run Select and update positions in a Mass Change Run The Mass Change Run request in Manage Mass Changes for Metadata Objects
Unassigned Incumbent from Position for Right to Return Whether to unassign the incumbent PM Settings > Right to Return > Unassign from Position
Create Right to Return for Incumbent Whether to create a right to return PM Settings > Right to Return > Create Right to Return
Derive Job Requisition Template in Recruiting Integration Which requisition template to use PM Settings > Integration > Rule for Deriving Job Requisition Template ID
Map Fields from Position to Job Requisition in Recruiting Integration Field mapping to the requisition PM Settings > Integration > Field Mapping Rule to Create Job Requisition from Position
Map Fields from Position to External Job Requisition in Fieldglass Integration Field mapping to a Fieldglass requisition PM Settings (Fieldglass mapping rule)
Rules for MDF Based Objects with Position
The general Metadata Framework scenario, with Position as the base object, is used to:
- generate position codes automatically from a sequence (Section 13.3)
- set default values when a new position is created
- trigger workflows when positions are created or changed (Section 13.3)
- configure MDF alerts and notifications
- Rule 1: Propagate Job Classification Data to the Position
When the Job Code changes, related fields such as job level and pay grade fill in from the job classification. This works during creation and change.
Configure Business Rules > + > Metadata Framework > Rules for MDF Based Objects.
Name and ID: Propagate_Job_Classification_to_Position . Start date 01/01/1900. Base Object: Position. Purpose: Evaluate.
Build the IF/THEN, for example setting the position's job title, job level, and pay grade from the selected job classification.
Assign it with the rule's assignment icon ( This rule can be assigned at the field level for object "Position" ), or in Configure Object Definitions > Position > Take Action > Make Correction . Open jobCode > Details > Rules and select the rule.
Test in Manage Positions > Create New > Position : pick a job code and watch the fields fill in. Cancel without saving.
Because the rule sits on a field, it fires onChange : when the job code changes from null or from another value.
Rule 2: Default Values When a Position Is Created
For fields common to many positions that do not come from the job classification, such as FTE, To Be Hired, Mass Position, Position Controlled, and Change Reason , a rule can set defaults:
Create a Rules for MDF Based Objects rule with IF Always True , and set the values in THEN.
Assign it in the Position object's Rules section under Initialize Rules , and save.
New positions then open with the defaults, for example a common legal entity, standard hours, or incentive plan. Alternative: the field's Default Value in the object definition. It works only for String, Number, Date, and Boolean fields. THR79's practice system defaults new positions to To Be Hired with FTE 1 this way.
Rule 3: Default Position Attributes (Copy-Relevant Fields)
When users Create Lower-Level or Create Same-Level Position from the Position Org Chart, this rule copies chosen values from the source position into the new position . It also works for Create Same-Level Position (Copy Rule) from My Team Positions and from Joule .
It does not work for Copy Position , which copies all fields.
Never include Parent Position in this rule. The system derives it from the hierarchy.
Create Same-Level Position (Copy All Fields) ignores the rule and copies everything.
Example: open Default_Position_Attributes , choose Insert New Record effective today, and add THEN expressions: Set New Position.Pay Grade = Source Position.Pay Grade and Set New Position.Incentive Plan = Source Position.Incentive Plan . Register the rule under PM Settings > UI Customizing .
Test: in the Position Org Chart, open Sales Director, NE (DIR_SALESNE) and choose Create Same-Level Position . Enter DIR_SALESEU, Sales Director, Europe , To Be Hired, 38 hours, Ace Germany, and Frankfurt. The rule fills in the rest before saving, and the parent position is assigned automatically .