Symptom
You are using the Obsolete Business Partner Removal Run feature to handle obsolete business partners, however there are specific entries that are not removed, despite already being on the removal range.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Go to the Data Protection & Privacy work center.
- Enter the Common Tasks view.
- Click on Administer Obsolete Business Partner Removal Runs.
- Create or edit an existing run, setting a date offset for the business partner removal.
After the execution of the run, some business partners which were in status Obsolete for longer than the date offset are still in the system.
Cause
This behavior happens since the business partner was modified after the change of status to obsolete.
As an example, consider a business partner removal run which is configured to remove partners which are obsolete, with an offset date of 10 days - meaning that partners which are more than 10 days in status obsolete should be picked for removal.
In case a business partner status is changed on May 1st, for example, this partner will be picked for removal if the run is executed after May 10th.
However, in case the partner was changed on May 5th - even though the status was not changed from obsolete - the run will not pick is for removal.
Resolution
The system works as expected.
Keywords
information lifecycle, data removal, personal data removal , KBA , AP-RC-ILM , ByD,C4C,Travel: Information Lifecycle Management , Problem