Study guide

5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects

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.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects

Key Takeaways Explain This Topic AI

HRIS elements support six rule events: onChange, onInit, onSave, onView, saveAlert, and onPostSave.

onChange is assigned only at field level; the other events are assigned at HRIS element level.

A Model base object (such as Job Information Model) is required to set field properties like Required and Visibility.

onView rules cannot be used for changes on the Add New Employee screen.

onSave rules run in the configured order, except that event reason derivation and workflow derivation rules run after all other rules.

Last updated: September 2026

5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects

Quick Answer: In Employee Central, rules are assigned to HRIS elements and fields in Manage Business Configuration under Trigger Rules . Six events exist: onChange (field level), onInit , onSave , onView , saveAlert , and onPostSave (element level). Use a Model base object when a rule must set field properties . On save, event reason derivation and then workflow derivation run after all other onSave rules .

What a Rule Consists Of

THR81 describes three parts:

Condition (IF): logic that must be met. Use Always True when the action should always run.

Action (THEN): how the system reacts. Some scenarios need no THEN.

Trigger (rule event): which user action starts processing. Without a trigger, nothing is evaluated.

THEN actions include:

  • SET: propagate or set a value
  • Raise message: an information or error pop-up
  • Create: a child object, such as a new pay component
  • Delete: remove data, for example a pay component when an employee leaves London
  • Execute: carry out a specified action
  • Add to: add items to a collection, such as several learning courses for new hires

ELSE IF combines conditions in one rule, and ELSE handles the case when no condition is met.

The Six HRIS Rule Events

  • Event Assigned at Triggered when Use it to
  • onChange Field level only A field value changes React immediately to a field change, such as propagation

onInit HRIS element Hire or rehire opens Add New Employee , or a new FO record is created in Manage Organization, Pay and Job Structures Set field properties or defaults as soon as the page opens

  • onSave HRIS element The page is saved Validate entries, derive event reasons and workflows
  • onView HRIS element Transient fields are viewed Calculate transient values, such as age

saveAlert HRIS element A change to jobInfo, compInfo, employmentInfo, or workPermitInfo is saved Send reminders of upcoming events, such as visa or contract expiry

  • onPostSave HRIS element After the change is saved Trigger events for Intelligent Services
  • Employee Central Core Rule Scenarios

SAP provides scenarios for the most common EC use cases. Each scenario limits the base objects and events you can use:

  • Scenario Purpose and limits
  • Generate Assignment ID External Generates Assignment ID External from MDF sequences; create only one rule

Generate Employee ID for Hire/Rehire Generates the User ID from an MDF sequence during hire or rehire with new employment

Rules for Hire/Rehire Rules that fire in hire scenarios; base object Employee Information or Employee Information Model

Trigger onInit Rules for Hire/Rehire Initializes HRIS elements in all hire and rehire processes; Employee Information Model; onInit only

  • Trigger Event Reason Derivation Derives event reasons; base object Job or Compensation Information Model
  • Generate Employee Central Alerts Creates alerts for EC data
  • Enforce New Employment for Rehire Validates changes, for example of legal entity, and enforces new employment
  • Trigger Workflows Triggers approval workflows; onSave only
  • Display Internal Job History Filters the Internal Job History block
  • Validate HRIS Elements Validations and alert messages
  • Calculate Full-Time Equivalent (FTE) Calculates FTE with the Job Information Model
  • Trigger onPostSave Events for Job Information Events or alerts after Job Information saves; onPostSave only
  • Trigger Cross-Entity Rules Changes in one entity update another; limited entities

Trigger onChange Rules for HRIS Elements Field-change rules such as propagation from Job Classification; onChange only

Trigger onSave Rules for HRIS Elements Rules on save; onSave only

Trigger an Off Cycle Event Batch / Trigger Event for Off Cycle Event Batch Rules run by the Off Cycle Event Batch job (SET or EXECUTE)

Trigger onView Rules for HRIS Elements Defaults, field properties, and transient calculations; onView only

Save Changes to Foundation Objects Rules on FO saves, for example defaulting standard weekly hours on a location

Standard Versus Model Base Objects

Unlike MDF objects, EC objects have a standard and a model base object , for example Job Information and Job Information Model . The base object determines what the rule can do and which events are allowed when it is assigned in the data model.

To set field properties you must use a Model base object. Model base objects support these properties:

  • Property Use
  • Required Set a field required (true) or not (false)
  • Visibility Set None , Edit , or View
  • Value Combine a property change with a default or conditional value

Previous Value Compare the old value with the new one, for example FTE.Value is not equal to FTE.Previous Value

Also note: you cannot use onView events for changes on the Add New Employee screen. When assigning a rule in BCUI, select the same base object the rule was created with. If the rule uses Job Information Model, choose Job Information Model in the Trigger Rules row.

The Order of onSave Rules

The system processes onSave rules in the order defined in Manage Business Configuration , with one exception: event reason derivation and workflow derivation rules run after all other rules.

Personal Information (no ERD): National ID rules, then workflow derivation rules.

Job Information: Job Information rules, then event reason derivation, then workflow derivation.

Manager Self-Service saving Job and Compensation Information together: Job Information rules, Compensation Information rules, ERD for Job Information, workflow derivation for Job Information, ERD for Compensation Information, and workflow derivation for Compensation Information.

Because of this order, the workflow rule can test the event reason the ERD rule just set (Section 9.5).

Assigning EC Rules in BCUI

In Manage Business Configuration , open the element ( Take Action > Make Correction ):

Element-level events: in the element's Trigger Rules section, choose the base object, the event type, the rule, and Enabled . Use the up and down arrows to order rules.

onChange: open the field's Details and add the rule in that field's Trigger Rules.

Save, and accept any data model adjustments BCUI proposes.