Study guide

5.3 Propagation Rules and Hire/Rehire Rules

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

5.3 Propagation Rules and Hire/Rehire Rules

Key Takeaways Explain This Topic AI

Propagation rules copy data from one field or object to another, such as the timezone from the selected location.

In THR81, propagation from Job Classification uses the scenario Trigger onChange Rules for HRIS Elements with base object Job Information Model.

Propagation rules are assigned at field level with the onChange event in Manage Business Configuration.

Hire/Rehire rules can use only Employee Information or Employee Information Model as base objects and run only on Add New Employee.

An onInit hire rule can prefill fields such as National ID country and card type when the Add New Employee page opens.

Last updated: September 2026

5.3 Propagation Rules and Hire/Rehire Rules

Quick Answer: A propagation rule copies data from a source, usually a foundation object, into employee data so it is maintained in one place. It is typically an onChange rule on the driving field. For example, changing Job Classification sets Pay Grade and Employee Class . Hire/Rehire rules use the special base objects Employee Information or Employee Information Model and run only on the Add New Employee form. They typically use onInit to prefill fields as the page opens.

Why Propagation Matters

Employee records depend on foundation data. THR81 stresses that corporate (foundation) data must be set up before employee data , because the job classification holds the job code, job title, pay grade, and standard weekly hours that employee records reuse. Once the foundation data exists, propagation rules fill parts of the employee record automatically. This reduces data entry errors. If Engineer (ENG) is chosen as the job classification during a hire, the related pay grade and weekly hours are filled in.

Typical propagation use cases from THR81:

Update job codes: whenever the job code changes, retrieve all job-related data from the job foundation objects.

Propagate FLSA status: if the country is USA and the job classification changes, set the FLSA status in Job Info.

Propagate standard hours: if the legal entity changes in Job Info, set the standard hours.

Propagate timezone: when the location changes, copy the location's timezone into Job Info.

Building a Propagation Rule

THR81's exercise copies Employee Class and Pay Grade from the selected Job Classification:

  • Setting Value
  • Rule scenario Trigger onChange Rules for HRIS Elements
  • Rule name / ID Propagate Job Classification to Job Info / Propagate_Job_Classification_to_Job_Info
  • Start date 01/01/1900
  • Base object Job Information Model
  • IF Always True (or a condition such as job classification not null)
  • THEN Set Job Information Model.Employee Class and Pay Grade = the values of the selected Job Classification

Assign it at field level: in Manage Business Configuration > jobInfo , open the job-code field's Details , and in Trigger Rules select base object Job Information Model , event type onChange , and the rule. Save, and accept any data model adjustments.

Test it: open Actions > Change Job and Compensation Info for an employee, choose Job Information with today's date, change the job classification, and confirm that the pay grade now changes. Cancel so nothing is saved.

In the timezone example, the rule is assigned to the location field with onChange , with IF set to Always True . The user's timezone always follows the location's timezone when the location changes.

Why onChange and not onSave? onChange fires the moment the driving field changes, so the user sees the propagated values while completing the form. An onSave rule would set the values only when the page is saved.

A Related Scenario: Save Changes to Foundation Objects

When the logic belongs to a foundation object record , use the scenario Save Changes to Foundation Objects . SAP's example defaults the standard weekly hours on a location. FO records created in Manage Organization, Pay and Job Structures can also use onInit rules to set defaults as the new record opens.

Hire/Rehire Rules

For Employee Central, SAP created special base objects, Employee Information and Employee Information Model , for rules that should run only on the Add New Employee form . They also make every EC object included in the hire form available to the rule.

Setup steps:

Create a rule with an Employee Central Core scenario: Rules for Hire/Rehire or Trigger onInit Rules for Hire/Rehire .

Choose Employee Information or Employee Information Model as the base object.

Assign the trigger to the HRIS element being affected on the form. Rules that trigger workflows for new hires must be assigned in jobInfo .

Worked Example: Default the US National ID

Most of ACE Corp's hires are in the United States and use a Social Security Number. THR81's rule prefills the National ID section:

  • Setting Value
  • Scenario Trigger onInit Rules for Hire/Rehire
  • Rule name / ID USA National ID / INIT_NAT_ID
  • IF Always True

THEN Set National ID Information. Country .Value = USA ; Set Is Primary .Value = Yes ; Set National ID Card Type .Value = ssn

Assignment BCUI > nationalIdCard > Trigger Rules: Base Object Employee Information , Event Type onInit

Two details from SAP's exercise often decide success:

The order of the expressions matters: Country, then Is Primary, then Card Type. The card type list depends on the country.

Text values are case-sensitive: USA and ssn must match the stored codes.

Because the event is onInit , the defaults appear as soon as the administrator opens Add New Employee , before anything is entered. Other hire screens are not affected because the base object is Employee Information.

Choosing Between the Patterns

Requirement Pattern

Fill job details the moment a job classification or location is chosen Propagation rule, onChange on the driving field

  • Prefill or hide fields when the hire wizard opens Hire/Rehire rule, onInit , Employee Information (Model)
  • Default a value on a new FO record onInit or Save Changes to Foundation Objects
  • Keep position and incumbent data in sync Position Management sync rules (Section 13.2)
  • Common Mistakes

Creating the rule but not assigning it, so nothing happens.

Assigning an onChange rule at element level. onChange works only at field level .

Choosing a different base object in BCUI from the one used to build the rule.

Forgetting permissions for newly propagated or enabled fields, so users cannot see the results.