Study guide
5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices
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.4 Cross-Entity Rules, Rule Context, and Rule Design Practices
Key Takeaways Explain This Topic AI
Cross-entity rules let a change in one employment entity set values in another, such as Job Information updating Compensation Information.
Cross-entity rules are supported only for Job Information, Job Relationship Information, Compensation Information, Recurring and Non-Recurring Pay Components, and Employment Information.
The History UI and imports support only onSave cross-entity rules; onChange cross-entity rules work when both entities appear on the UI.
You can have a maximum of five cross-entity rule scenarios for an HRIS entity.
Rule context applies only to onSave and onChange rules on HRIS elements; setting a context to No stops the rule for that situation.
Last updated: September 2026
5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices
Quick Answer: A cross-entity rule is triggered in a source entity (its base object) and changes a target entity. For example, a Job Information change can add an HR manager in Job Relationships. Only six employment entities are supported, with at most five cross-entity rule scenarios per entity. Rule context lets you switch a rule off for specific situations, such as mass changes, for onSave and onChange rules on HRIS elements.
Cross-Entity Rules
Cross-entity rules set values in a different entity from the one that triggered them. Supported entities:
- Job Information
- Job Relationship Information
- Compensation Information
- Recurring Pay Component
- Non-Recurring Pay Component
- Employment Information
Direction matters: the source element must be the base object of the rule. Common use cases:
- Source change Target update
- Job Information (company, location, employee class) Compensation Information
- Job Information Job Relationships
- Job Information (pay scale level, FTE) Create, update, or delete Recurring Pay Components
- Compensation Information (custom annual salary field) Amounts in a Recurring Pay Component
- Event Support and Limits
The History UI and imports support only onSave rules for cross-entity scenarios.
onChange cross-entity rules generally work only when both entities are displayed on the UI , as in the Manager Self-Service screen.
There can be a maximum of five cross-entity rule scenarios for an HRIS entity .
Worked Example from THR81
ACE Corporation wants Nancy Nash added automatically as the HR Manager for employees in legal entity Ace USA and business unit Corporate Industries .
- Setting Value
- Scenario Trigger Cross-Entity Rules
- Rule name / ID Assign Corporate Industries HR Manager / Assign_Corporate_Industries_HR_Manager
- Base object Job Information Model (the source)
- IF Company = Ace USA and Business Unit = Corporate Industries
- THEN Create or set a Job Relationship of type HR Manager = Nancy Nash
- Assignment BCUI > jobInfo > Trigger Rules: Job Information Model, onSave
To test, change the employee's department through Change Job and Compensation Info , submit, and approve the workflow steps by proxy. After final approval, a new Job Relationships entry for Nancy Nash appears. SAP suggests two ways to skip approvals during testing: temporarily disable the workflow rule in BCUI, or use the Job Information History with the Transfer event and Department Change reason.
Rule Context
Rule context narrows the situations in which a rule runs. The classic case: you do not want a workflow derivation rule to fire during a mass change , which could launch one workflow per employee.
Rule context applies to onSave and onChange rules only.
It applies to HRIS elements only , not MDF objects.
Every context defaults to Yes. Set a context to No to stop the rule in that situation.
This matters for Mass Data Management . SAP notes that it triggers all onSave and PostSave rules. If you do not want onSave rules such as workflow derivation to run, set the rule context for mass changes to No in Manage Business Configuration (Section 8.3).
Rule Design Practices
SAP's EC lessons repeat several design rules:
Fewer onSave rules perform better. Group related logic, such as all event reason derivation conditions, into one rule with several IF/ELSE IF branches where maintainability allows.
Split rules only when needed , for example when requirements are complex or change frequently. Splitting may cost some performance.
Rule IDs without spaces. SAP warns that ERD rules with spaces in the ID don't trigger correctly.
Always cover the fallback. For event reason derivation, add a catch-all ELSE or a final rule, otherwise users see "Unable to determine the event reason for the proposed changes" (Section 9.4).
Assign with the correct base object and event. A rule built on a Model base object must be assigned with that Model base object.
Order element-level rules deliberately in BCUI. The platform still runs ERD and workflow derivation last.
Remember scope: EC Quick Actions run rules assigned onSave, onChange, onView, and onPostSave for all fields, even fields not included in the template (Section 10.1).
Migrate Basic rules to application-specific scenarios. They are easier to build and less error-prone, and the Check Tool offers a migration check.
Choosing the Right Rule Mechanism
- Requirement Mechanism
- Update Compensation when Job Information changes Cross-entity rule, source Job Information Model
- Suppress an approval workflow during mass changes Rule context set to No for mass changes
- Derive the event reason automatically ERD rule, onSave, Job or Compensation Information Model (Section 9.4)
- Route the change for approval Workflow derivation rule, Trigger Workflows , onSave (Section 9.5)
- Default values when the hire page opens onInit hire rule (Section 5.3)
- Exam Tip
When a practical task says "when X changes, Y in another block must update", check first whether both blocks are among the six supported entities. Then check whether the change will be made through a UI that shows both entities (onChange works) or through History or an import ( onSave is required).