Symptom
- Rule on Work Permit Expiration not triggering
- Rule Trace shows no entries
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental
Environment
SAP SuccessFactors Employee Central - Alerts and Notifications
Reproducing the Issue
- Create a saveAlert rule on base object: Work Permit Model base object.
- Set the THEN statement to trigger an Alert.
- Make a change to Work Permit Expiration Date for an Employee to meet the conditions that should trigger the rule and send the alert.
- Run a 'EC Alerts and Notifications' job.
- No alert sent. Rule Trace shows no entries.
Cause
- Wrong base object Work Permit Model base object
- Work Permit is NOT an effective dated entities
- They cannot contain a value check condition in the IF statement, similar to the below
- Value Check is not supported for Work Permit or National ID
Resolution
Step:
-
Navigate to Configure Business Rules > Employee Central Core > Trigger Rules to Generate Employee Central Alerts
-
Select the base object and fill other required details and click on Continue.
-
Base object: Personal Documents Information or Personal Documents Information Model
- view Guide Employee Central Workflows Work Permit Alert but do not use Basic scenario
- We recommend that you use the Trigger Rules to Generate Employee Central Alerts scenario while creating new rules instead of the Basic scenario.
-
You can use this scenario to create rules that generate Employee Central alerts for HRIS Elements. In Manage Business Configuration, rules created using this scenario can be registered only for the saveAlert event type.
Example
Example
Example
FAQ - Additional Information
Q) Where can I get more information?
A) Guide Employee Central Workflows Work Permit Alert
Q) What is a base object for work permit Alert rule?
A) Base object: Personal Documents Information or: Personal Documents Information Model
2856599 - 1911 - Rule Scenario Base Objects Used in Alert Triggering Rules for Employee Central Data Objects - Generate Alerts for Employee Central Data
Q) Please provide some example?
A) Example:
On September 1, 2012, Susan updates her work permit info in the system.
Work Permit Ireland expiration date 15.2.2017
So, Susan's manager will receive an alert on January 15, 2017 (effective date of the alert). Technically, the alert is generated on September 1, 2012 with an effective date of January 15, 2017.
Alternative Scenario - Extension
On January 2, 2017, Susan updates the expiration date of her work permit in the system.
Work Permit Germany expiration date 15.2.2020
So, the original alert created for January 15, 2017 is no longer needed. The system deletes the previous alert and creates a new one for the new effective date of January 15, 2020.
Alternative Scenario - Reduction
On January 2, 2017, Susan updates the expiration date of her work permit in the system.
Work Permit Germany expiry date 10.1.2017.
The alert will be triggered on January 2nd. The system deletes the previous alert, creates a new alert with an effective date of January 2nd, and sends it immediately.
Alternative Scenario - Extension
On February 1, 2017, Susan updates the expiration date of her work permit in the system.
Work Permit Ireland expiration date 10.1.2020
So, the original alert created for January 15, 2017 was triggered and sent. There is no automatic updates or deletion however. The system generates a new alert and creates a new one for the new effective date of December 10, 2019.
See Also
Keywords
Work Permit, Value Check, Expiration, Rule, Alert, Not Triggering, Rule Trace,Personal Documents Information , Personal Documents Information Model. , KBA , LOD-SF-EC-ALR , Alerts & Notifications (saveAlert - EC Core only) , LOD-SF-EC-PER-WRK , Work Permit - Config, Rules, RBP, UI , LOD-SF-EC-RUL , DO NOT USE - Business Rules & Event Derivation , Problem