Study guide

9.4 Events, Event Reasons, and Event Reason Derivation

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

9.4 Events, Event Reasons, and Event Reason Derivation

Key Takeaways Explain This Topic AI

Events come from a standard picklist and cannot be added; event reasons are XML-based foundation objects that set the employee status.

Every Job and Compensation Information transaction requires an event and an event reason.

Event Reason Derivation (ERD) is an onSave rule on Job or Compensation Information Model; its first condition should stop processing if the event reason is not null.

Hire, rehire, and termination event reasons are selected manually and cannot be derived.

Insert New Record in History bypasses ERD and workflows; SAP calls this an HR Edit and reserves it for administrators.

Last updated: September 2026

9.4 Events, Event Reasons, and Event Reason Derivation

Quick Answer: Events (hire, promotion, transfer, termination) come from a standard picklist . You can relabel or deactivate events but cannot add new ones . Event reasons are XML foundation objects that explain the event and set the employee status . Event Reason Derivation (ERD) uses onSave rules to pick the reason automatically from the data change. SAP recommends ERD because it gives cleaner reporting.

Events and Event Reasons

Employee Central delivers a standard, exhaustive Events picklist. You cannot add a custom event , but you can deactivate or relabel event values. To distinguish why an event happened, you use the Event Reason foundation object. A promotion, for example, could be a lateral move without a pay change or a vertical move with an increase.

Events and event reasons let customers:

  • keep clear reports of what changed
  • comply with legal or corporate policy on employee changes

Every Job and Compensation Information change requires an event and an event reason.

Event Reason is an XML-based foundation object , managed in Manage Organization, Pay and Job Structures . Event reasons are tied to events and define the employee status , so do not modify or repurpose the employee-status picklist. The event reason can also carry termination settings such as Delete Future-Dated Records After Termination (Section 8.1).

With or Without Derivation

Without ERD With ERD (preferred)

The user chooses the event and reason manually Business rules set the event, event reason, and workflow from the data change

  • Business rules connect a workflow to the chosen reason Needs more initial setup
  • Quicker, simpler solution More accurate reporting and more user-friendly

When managers pick reasons manually, errors are common and reports become unreliable. With ERD, the system selects the reason and updates the employee status if needed . ERD needs careful design: every possible change in Job and Compensation Information must be anticipated and tied to a reason. If no rule sets the reason, the system raises an error the initiator cannot resolve.

Without ERD, for Job Information edit and history transactions, managers and admins see only events that have at least one event reason they have Edit permission for .

What Cannot Be Derived

Hire, rehire, and termination event reasons are always selected manually. You cannot create a derivation rule for them.

Setting Up an ERD Rule

Create a rule with the scenario Trigger Event Reason Derivation (EC Core).

Give a name and ID. Do not use spaces in the rule ID , or it will not trigger correctly.

The base object is limited to Job Information Model or Compensation Information Model .

First IF: event reason is not equal to null, with an empty THEN. This keeps a reason already supplied, by a user or an import, from being overwritten.

Add ELSE IF / THEN pairs for each change scenario. For example, if Standard Weekly Hours is not equal to its previous value, set the event reason. Use as many as needed.

Add a catch-all , either an ELSE in the last rule or a separate final rule.

Assign the rule as onSave to the right HRIS element (for example Job Information) in BCUI, with the same Model base object .

Only one event reason can be assigned to a transaction.

SAP's ERD Best Practices

Check for event reason not equal to null first , to avoid overwriting.

Group the derivation logic in a single rule for performance, because fewer onSave rules perform better. Split it only when complexity or maintenance requires it, accepting some performance cost.

Use a catch-all. Without one, MSS users can see "Unable to determine the event reason for the proposed changes" . This is a configuration issue.

Worked Example (THR81)

  • Setting Value
  • Scenario / ID Trigger Event Reason Derivation / ERD_JOBINFO
  • Base object Job Information Model
  • IF 1 Event Reason ≠ Null → no derivation
  • ELSE IF Is Eligible for Benefit ≠ previous value → Event Reason = Benefits Adjustment (PAYBEN)

Assignment BCUI > jobInfo > Trigger Rules: Job Information Model, onSave , placed above the existing jobInfoModel_ERD_migrated_rule so it is processed first

Changing Is Eligible for Benefit now saves with the Benefits Adjustment reason. Without a workflow rule, it saves without approval. Adding the WF_jobInfo rule derives the Data Change workflow as well (Section 9.5).

Bypassing ERD: the HR Edit

Even with ERD on, users with RBP rights to Insert New Record from the History of jobInfo and compInfo bypass derivation:

Through Take Action or the pencil icon, the system derives the event and reason and triggers a workflow if configured.

Through History > Insert New Record , the user chooses the event and reason manually , the change is saved immediately , and no workflow is ever triggered .

SAP calls this an HR Edit , and it should be given only to administrators.

ERD During Imports

To derive event reasons during imports, enable the permission Enable Business Rules for selected entities for imports. A value in the event reason column takes precedence over the onSave derivation. If the column is empty, the onSave rule derives the reason.

Country-Specific Event Reasons

Customers in many countries often have country-specific event reasons . Because each employee belongs to one legal entity and one country, the system can show only the relevant reasons on all screens with an event reason field. This helps large multi-country customers and customers with many country-specific reasons.

Change the Country/Region object to include a composite association with the Event Reason Wrapper .

In Manage Data , add the applicable event reasons per country, or import them with Import and Export Data.