Study guide
5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log
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.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log
Key Takeaways Explain This Topic AI
Business rules are built in Configure Business Rules from a rule scenario, a rule ID without spaces, a start date, and a base object.
A rule runs only after it is assigned; assigned rules cannot be deleted until the assignment is removed.
For MDF objects, Initialize rules run before all other rules and only when a new record is created; field-level assignment supports only onChange.
Validate rules run before Save rules and also run during import validation in Import and Export Data.
A Business Rule Execution Log trace can run for at most two days and traces the user who executes the rule.
Last updated: September 2026
5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log
Quick Answer: A business rule is created in Configure Business Rules from a rule scenario . It has a base object , IF conditions, THEN (and optional ELSE ) actions, and it runs only when assigned to an object, field, or setting with a rule event . For MDF objects the events are Initialize, Validate, Save, Post Save, onChange (field level), Delete, On Load, and UI rules. The Business Rule Execution Log traces rules for troubleshooting.
What Rules Are Used For
Rules add application logic without code. THR80 lists typical uses:
- Workflow: pick the right approval workflow, for example an alternate workflow if a salary increase exceeds 10%
- Propagation: copy data from one field to another, for example the job code into a position
- Calculations: for example current age from date of birth
- Validation: check input before saving, for example FLSA status required when the country is USA
- Eligibility: for example who is eligible for a compensation or variable pay form
- Defaulting values: for example new hires in a given company are eligible for stock with a default grant
The rules engine is technically based on MDF but has its own tool, Configure Business Rules . MDF must be enabled ( Enable Generic Objects in Provisioning), and the administrator needs Metadata Framework > Configure Business Rules .
Separating View and Edit Rights for Rules
To distinguish viewing from editing rules, open the Rule object in Configure Object Definitions . Set Secured = Yes , Permission Category = Business Rules Object Permissions , and CREATE Respects Target Criteria = Yes . Then grant View Rules (View Current, View History) or Edit Rules (plus Create, Insert, Correct, Delete). Field-level overrides are not respected here. Target criteria can separate rule authorizations by area, for example Time Management admins versus Recruiting admins.
Creating a Rule
Choose + (Create New Rule) , pick a rule scenario , and fill in:
Rule Name: the label shown in search.
Rule ID: the unique identifier. The name is copied in automatically, but best practice is no spaces in the ID ; an ERD rule with spaces in its ID won't trigger correctly.
Start Date: the rule applies only from this date. The default is 01/01/1900 .
Rule Type: optional grouping for Basic rules, from the RuleType picklist.
Description: optional business context.
Base Object: the object whose fields and related objects the rule can use. Application-specific scenarios define or limit the base object.
Rule scenarios are rule templates grouped by application (Employee Central Core, Metadata Framework, Position Management, and so on). You see only scenarios for enabled applications. Legacy Basic rules can be migrated to application-specific scenarios one at a time ( Change Scenario ) or in bulk through the Check Tool ( Migration > Business Rules Application ).
Building the Logic
Statements follow the pattern left expression – operator – right expression .
Left expression: base-object data, functions, additional MDF objects, variables, Current User , or Effective Date .
Right expression: a field type or value, fields of the same type, functions for that type, variables, Current User, Effective Date, or Null .
- Operator Field types
- is equal to / is not equal to all types
- is greater than, is less than, greater than or equal, less than or equal Number, Decimal
- is before, is on or before, is after, is on or after Date
Collection filters select one value from a list where a parent-child relationship exists. For example, Job Relationship is a child of Job Information, so a filter picks the HR Manager relationship ( Select… where… ).
IF defines the condition, THEN the action, and ELSE the action when the condition is false. Setting IF to Always True makes the THEN run every time the rule is triggered.
MDF Rule Events
For MDF objects, rules are assigned in Configure Object Definitions , at object level or in a field's details. Only onChange can be used at field level.
- Event When it fires Typical use
- Initialize Before all other rules, only when a new record is initialized Default values
Validate After submit, before save. Also runs during import validation in Import and Export Data. Validate input and raise errors
- Save When the user saves Set values from input before saving
- Post Save After the change is saved Alerts; not for setting values
- onChange When a specific field changes (field level) Populate another field
- Delete After a record is deleted Follow-up logic
- On Load When a UI loads Calculate displayed totals
- UI rules Only in a Configurable UI screen Show, hide, or require fields; not applied on import
Warning messages from Validate and Save rules appear before workflow confirmation messages.
Assigning Rules
A rule is only triggered when it is assigned. Depending on the scenario, you assign it to an object, a business process, an event, a screen, or a setting. The rule list shows an assignment icon: a green check means assigned, grayed out means not assigned, and empty (white) means no assignment information (for example Basic rules). The icon opens a wizard that links to the right assignment page. Assigned rules cannot be deleted ; remove the assignment first. You can export the list of rules with their assignments as a CSV.
The Business Rule Execution Log
The Business Rule Execution Log traces a rule's execution. It needs the Access to Business Rule Execution Log permission. There are separate permissions to create a trace and to create and view logs; SAP advises limiting viewing because logs can contain sensitive data.
Choose Create New > Rule Trace , enter a name and code, a start and end date ( maximum two days ), the user who executes the rule (not the user whose data changes), and optionally specific rules (blank traces all rules for that user).
Reproduce the transaction, then Download the CSV log.
Each log file is limited to 5 MB . When the limit is reached, no more entries are written until the file is deleted. Deleting the log keeps the trace definition.
For EC transactions, the Diagnostic Tool adds a rule execution view (Section 10.2).