SAP Knowledge Base Article - Public

2697132 - EC Alerts: How to correct stored Alert after the Business Rule has been changed

Symptom

Alerts have been triggered by an Alert rule. After the Pending Alert is created, the rule logic is then changed. You don't want the original Pending Alerts to be sent and instead you want to delete these Alerts and retrigger the rules to create new alerts.

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 HCM Suite
  • SAP SuccessFactors Employee Central

Resolution

After updating the rule, run the EC Alert and Notification job with a specific (run from) date to include all scanned records again.

The process is:

  • The  previous job ran  on Sept 23 2018, all the records have been scanned up to the time the job ran.  Pending Alerts are created (for any records modified during the period based on the rules) or existing Pending Alerts are sent (where they are Effective from Today or from a past date).
  • The  next job ran on Sep 24 2018, only the record changed after 09/23 will be  scanned.
  • Create a job setting from using “last successful ran date” to  “specify a date =  01/01/2018 (example, select a date in the past - but advise that you do not go too far back else the volume of records to be checked might be very massive).  This way all the records are involved in the job again and evaluate with the current version of the rule.

                        The old alert will be removed. new alert with new effective date will be set.

AlertJob.png

 

Job Execution Logic

For more information on how the EC Alerts and Notifications schedule job works, please refer to the following chapter from Guide: Implementation and Administration

Note: As confirmed by EC Alert Developer team, above content is correct.

  • For all related existing module entity(e.g. job info entity), all the old related alerts will be deleted and the new alerts will be created with new alert rules if rerun the job from the start date.

Note: Post 1H 2021 ReleaseDelete Old Pending Alert Flag

  • Using this new rule setting, you can delete unwanted pending alerts for several HRIS effective-dated entities when creating a new alert.

    After a new alert is created following a data change, old pending alerts become irrelevant and are not expected to be sent. You can update your alert rules by including the new setting Delete Old Pending Alert Flag. This will delete unwanted pending alerts and prevent them from being sent for future data changes. Three HRIS effective-dated entities are supported now: job information, compensation information, and pay component recurring.

    Guide and Chapter:New Rule Setting for Deleting Unwanted Pending Alerts for Effective-Dated Entities 


Important Note: You cannot just run the job by clicking 'Run It Now', as this job has to be submitted in order to run properly.

See Also

  • 2315275 - Employee Central - Workflows & Alerts
  • 2799601 - EC Alert Job with specify date 
  • 2677124 - EC Alerts: System Logic for when a saveAlert Rule is Removed or Changed
  • 2462997 - EC Alerts and Notification Job Failing 
  • 2757863 - Manage Alerts and Notifications tool
  • 2431478 - Example Configuration of an EC Alert and Notification Rule.
  • 2856599 - 1911 - Rule Scenario Base Objects Used in Alert Triggering Rules for Employee Central Data Objects - Generate Alerts for Employee Central Data
  • Guide: Employee Central Workflows: Implementation and Administration

Keywords

Alerts job, ec alerts, rule, change, update, alert, modify, business rule, EC alert, modify,  Delete Old Pending Alert Flag , KBA , LOD-SF-EC-ALR , Alerts & Notifications (saveAlert - EC Core only) , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , Problem

Product

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HCM Suite all versions