3662114 - SAP Cloud ALM - Update on the Data Reorganization process in Health Monitoring

This is an update regarding the data reorganization process in Health Monitoring

Identified Problems

1. Reorganization always used configured retention time
   Until now, the housekeeping and aggregation jobs always looked back only as far as the configured retention period, even if the data reorganization job failed for several days.
   • Example: If the retention for Raw Data is set to 30 days and the reorganization job fails for 10 consecutive days, once the job runs again it still only looks back 30 days. This results in older data not being reorganized properly.
2. Risk of data loss when shorter retention periods are configured
   In cases where the housekeeping job did not run for some time (e.g., during onboarding), as soon as it was triggered, it only looked back according to the configured retention period. If the customer had configured a shorter retention period than the default, older data was purged unintentionally.
   • Example: If a customer configures Raw Data retention as 7 days (instead of the default 30 days) and the housekeeping job did not run for 20 days, once the job runs, it only looks back 7 days. All data older than 7 days is then purged.

SAP Cloud ALM

Health Monitoring, SAP Cloud ALM, CALM, Retention, period, job, reorganization, data , KBA , SV-CLM-OP-HM , SAP Cloud ALM - Health Monitoring , Product Enhancement