Symptom
Upon submitting a new Contingent Worker, Work Order Expiration Notification is not being stored in Manage Alerts and Notification.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Rule example:
Environment
- SAP SuccessFactors Employee Central
- SAP SuccessFactors HCM Suite
Reproducing the Issue
- Configure a business rule for Work Order Expiration Date Notification;
- Navigate to "Add Contingent Worker'';
- Fill in the required fields > Click on Submit;
- Navigate to Manage Alerts and Notifications;
- Notice that the Work Order Expiration Notification has not been set.
Cause
Off Cycle Event Batch logic needs to be used for Work Order Expiration Notification.
Resolution
As per our implementation guide, after configuring a business rule for Work Order Expiration Date Notification, it is required to create an Off Cycle Event Batch object to fetch expired work orders based on business requirements. After that, the business rule in place needs to be associated with it.
Step by step is documented in KBA 2524842 - How to Configure Business Rules for Work Order Alerts and Notifications?.
This logic has been enhanced by Centralized Services.
See Also
Keywords
work order, expiration date, expiry date, alert, notification, hire, work order alert not working, manage alerts and notifications, contingent worker, add contingent worker, employee central , KBA , LOD-SF-EC-CWF , Contingent Workforce , How To
Product
Attachments
Pasted image.png |