Study guide
9.3 Employee Central Alerts and Notifications
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.3 Employee Central Alerts and Notifications
Key Takeaways Explain This Topic AI
Alerts notify users of upcoming events, such as an expiring work visa, in the system and by e-mail.
An alert needs three elements: an alert message, alert recipients defined in a workflow record, and an alert rule.
Workflow approvers receive alerts in the system, CC roles receive them only by e-mail, and contributors are not used.
EC alert rules use the Generate Alerts scenario and are assigned as saveAlert on an alert-supported element.
A recurring EC Alerts and Notifications job in Provisioning creates and sends the alerts.
Last updated: September 2026
9.3 Employee Central Alerts and Notifications
Quick Answer: Alerts warn users about upcoming events, such as a work visa about to expire. An EC alert needs three elements : an alert message (Manage Data), alert recipients (defined in a workflow record), and an alert rule (scenario Generate Alerts , assigned as saveAlert ). A recurring EC Alerts and Notifications job in Provisioning creates and sends them.
Where Alerts Are Supported
Alerts are supported for:
- Employee Central data
- Compensation Information
- Employment Information
- Job Information
- Pay Component Recurring
- Pay Component Non-Recurring
- Work Permit
- Global Assignment
- MDF data
Depending on configuration, users see alerts in the system (for example in the For You Today area of the Home Page) or receive e-mail.
Element 1: The Alert Message
The Alert Message object is pre-delivered. Create records in Manage Data with a name and external code. You can localize the header and description. The message field ( alertDescription ) is 255 characters by default and can be increased up to 4,000 .
Tags act as placeholders:
- Tag Use
- [[SUBJECT_USER]] The employee concerned
- [[EVENT_REASON]] EC data
- [[EFFECTIVE_DATE]] The effective date
- [[OBJECT_TYPE]] MDF data (person- and object-based)
- [[OBJECT_NAME]] MDF data (object-based)
[[VIEW_BLOCK_ON_PROFILE]] A deep link in e-mail to the right People Profile block (EC alert-supported entities only)
Element 2: The Alert Recipients
Recipients are defined in a workflow configuration record ( Manage Organization, Pay and Job Structures ):
Approvers receive the alert in the system .
CC roles receive the alert only by e-mail .
Contributors are not used for alerts.
In THR81's visa example, the employee is both an approver (system alert) and a CC role (e-mail), and so is the employee's manager.
Element 3: The Alert Rule
Generate Alerts is the EC Core rule scenario for EC data alerts:
IF: the condition, for example document country = Canada and expiration date not null.
THEN:
- Alert.Workflow Information: the recipient workflow
- Alert.effective date: when the alert is sent
- Alert.Alert Message: the message created in Manage Data
Assign the rule as saveAlert at element level of the alert-supported entity in Manage Business Configuration. Remember that saveAlert fires when changes to jobInfo, compInfo, employmentInfo, or workPermitInfo are saved (Section 5.2).
For MDF data , the steps are the same, except that you use the Alert purpose in the Rules for MDF Based Objects scenario and assign the rule as a Post Save rule.
The Recurring Job
Create a recurring job in Provisioning ( Manage Scheduled Jobs > Create New ), job type EC Alerts and Notifications , typically daily . The job checks which records qualify under the rule's IF conditions and sends the alerts on the effective date or due date set in the THEN statement. Use Run it now to test.
Managing Pending Alerts
The Manage Alerts and Notifications dashboard lets administrators filter, view, and delete pending EC alerts and To-Dos. An advanced filter narrows them by criteria.
Worked Example: Visa Expiry Alert (THR81)
Step Configuration
1. Message Manage Data > Alert Message: name, external code, localized header and description, tags such as [[SUBJECT_USER]]
2. Recipients Workflow record: employee as approver (system alert) and CC role (e-mail); the manager likewise
3. Rule Generate Alerts; base object Personal Document Information Model ; IF document country = Canada and expiration date is not null; THEN set message, workflow, and alert date
- 4. Assignment BCUI: assign the rule to the element as saveAlert
- 5. Job Provisioning: recurring EC Alerts and Notifications job, daily
- Alerts for MDF Data, Including Positions
MDF objects use the same three building blocks with two differences: the rule is built in Rules for MDF Based Objects with the purpose Alert , and it is assigned in Configure Object Definitions as a Post Save rule. The tags [[OBJECT_TYPE]] and [[OBJECT_NAME]] identify the MDF record in the message. THR79 lists Configure MDF Alerts and Notifications as one of the uses of Rules for MDF Based Objects with Position as the base object, so position-related reminders follow this MDF pattern (Section 13.1).
Design Checklist
Decide who must be warned and how : in-system (approver) or e-mail only (CC role).
Decide when : the THEN statement's effective date or due date sets when the alert is sent.
Keep the IF narrow enough to avoid noise, for example only expiring documents of one country.
Write the message with tags, lengthening alertDescription beyond 255 characters if needed.
Assign the rule with the right event: saveAlert for EC data, Post Save for MDF data.
Create and test the recurring job , then check the For You Today area and the recipients' e-mail.
Alerts Versus Workflows Versus Admin Alerts
- Feature Purpose
- EC alerts Remind employees or managers of upcoming data events (expiring visas, contract end dates)
- Workflows Approve data changes before they take effect
Admin Alerts Inform administrators of system issues such as stalled workflows or failed follow-up processes (Section 2.4)
Common Pitfalls
Creating the message and rule but no recurring job , so no alerts are generated.
Putting recipients only in the contributor role, which alerts do not use.
Assigning the rule as onSave instead of saveAlert for EC data.
Forgetting to lengthen alertDescription for long messages beyond 255 characters.