Study guide

9.5 Workflow Derivation Rules and How They Work with 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.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

Key Takeaways Explain This Topic AI

Workflow derivation rules use the Trigger Workflows scenario and are assigned only as onSave rules.

The THEN statement sets wfConfig, the field that stores the workflow to run; only one workflow can be assigned to a transaction.

Without a workflow derivation rule, the system saves the data directly without approval.

Workflow derivation for new hires must be assigned under the jobInfo element.

A workflow rule can test the derived event reason because ERD runs before workflow derivation on save.

Last updated: September 2026

9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

Quick Answer: A workflow derivation rule (scenario Trigger Workflows , assigned onSave ) sets the wfConfig value, which is the workflow record that must approve the transaction. Without such a rule, EC saves the change directly, with no approval. Because ERD runs before workflow derivation, the workflow rule can branch on the derived event reason .

Purpose

Workflow derivation rules define the conditions that start a specific workflow. For example, when an employee's salary increases, a salary-approval workflow starts. With ERD in place, the combination is powerful. If the system derives Promotion with Pay Change , the workflow rule can route that reason to the matching approval chain.

Setting Up a Workflow Derivation Rule

Create a rule with the scenario Employee Central Core > Trigger Workflows . In BCUI, rules from this scenario can be assigned only as onSave .

Choose the relevant standard or model base object for the element.

Build IF / ELSE IF conditions, for example IF Event Reason.Value = Promotion with Pay Change .

In each THEN, set wfConfig , the field that stores the workflow record to run.

Assign the rule in Manage Business Configuration under the element's Trigger Rules as onSave .

Only one workflow can be assigned to a transaction.

  • Elements That Support Workflows
  • National ID Card
  • Home Address
  • Personal Information
  • Global Information
  • Personal Relationship Info
  • Work Permit Information
  • Job Information
  • Job Relationship Information
  • Employment Information
  • Compensation Information
  • Pay Component Recurring
  • Pay Component Non-Recurring
  • Foundation Objects
  • SAP's Recommendations

Prefer one rule with several IF statements over many single rules.

On the UI, the element's onSave rule is evaluated, and the workflow in the THEN runs when the condition is met. If no workflow configuration is assigned by the onSave rule, the system saves the data without approval.

Workflow derivation rules for new hires must be assigned under the jobInfo element.

Approval is not triggered for changes made in History , because History actions never start workflows (Sections 7.5 and 9.4).

Execution Order: Why ERD Comes First

On save of Job Information, the order is: Job Information rules, then event reason derivation , then workflow derivation . When MSS saves 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 (Section 5.2). The workflow rule therefore always sees the final event reason.

Worked Example 1: ERD and Workflow Together

THR81's optional step assigns the existing WF_jobInfo rule (base object Job Information Model, onSave) to Job Information next to ERD_JOBINFO . When Is Eligible for Benefit changes, ERD sets Benefits Adjustment (PAYBEN) , and the workflow rule derives the Data Change (DTACHNG) workflow. SAP also suggests an alternative: add ELSE IF branches to the existing jobInfoModel_ERD_migrated_rule and WF_jobInfo rules instead of creating a separate ERD rule, which keeps the logic grouped.

Worked Example 2: A Workflow for Job Relationships

ACE wants approval when job relationships change, except when System Administrators make the change.

Step 1 – Workflow record ( Manage Organization, Pay and Job Structures ):

  • Field Value
  • Workflow ID / Name JobRelWorkFlow / Job Relationship WF
  • Is Delegate Supported No
  • Step 1 Approver Type Role , Approver Role Manager Manager
  • Step 2 Approver Type Dynamic Role , Approver Role HR Approval

Step 2 – Rule:

  • Setting Value
  • Scenario / ID Trigger Workflows / WF_JobRel
  • Base object Job Relationships Model

IF Job Relationship Type or Name ≠ previous value and user is in Permission Group ≠ "System Administrators" → Set wfConfig = JobRelWorkFlow

  • ELSE IF Same change and user is in Permission Group = "System Administrators" → no workflow
  • Assignment BCUI > Job Relationships > Trigger Rules, onSave

Step 3 – Test: proxy as a manager (Sean Arnold) and add a Matrix Manager relationship for an employee. The workflow is triggered. As the administrator, the same change saves without approval.

This example shows two useful techniques: comparing a field with its previous value (Model base object), and branching on the current user's permission group .

Workflows Beyond HRIS Elements

Foundation objects can also be protected by workflows, as the element list shows.

MDF objects such as Position use MDF rules with the Workflow purpose, assigned as a Save rule on the object, plus Pending Data = Yes (Section 13.3).

Troubleshooting Checklist

Symptom Check

Change saves without approval Is a Trigger Workflows rule assigned onSave to this element, and does a branch match? Was the change made in History?

Wrong workflow chosen Does the rule test the derived event reason? Is the ELSE IF order right?

Hire has no approval Is the hire workflow rule assigned in jobInfo ?

The rule never fires Is the base object in BCUI the same Model object used to build the rule? Does the rule ID contain spaces?