In the "Purge Master Data" job, is there any option to get an attachment file with "Review" option?

[SoniaMoraza]

In the "Purge Master Data" job, is there any option to get an attachment file with "Review" option?

This way we can check in advance - before running the job without simulation - all affected master data types also during the review execution for "Purge Master Data" job. If we run without "Review" (simulation) option then we can get this detailed log, otherwise not. It will be great having this during the "Review" or "Simulation" execution as well. 

Thanks.

Kind regards,

Sonia

[ZoltanMBiro]

Hi Sonia,

Thanks for the question.

There is a preview mode for the Purge Master Data job.
In that case a file will be attached to the job log informing you about the master data that would get deleted.

Please see here:
https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/feae3cea3cc549aaa9d9de7d363a83e6/ebbf4953...

Please keep in mind that the list is not comprehensive. The preview will not contain related master data, like compound master data that would get deleted as well. 
For example, if you are running the job in preview mode for purging locations, the attachment will contain only locations that would be deleted in a normal run. The attachment will not contain however the location-product master data. When running the purge master data job in a normal run, purging locations would result also in removing some dependent location-products due to the deleted locations.

Kind regards,
Zoltan Biro.

[SoniaMoraza]

Hello Zoltan,

We would like to get a more detailed log in our "preview" execution mode where we can see not only the Master Data entries from the main Master Data type selected but also all the dependent master data (all the other affected master data entries from compound master data).

Considering that by using this "Purge Master Data" job we are taking care of critical and very sensitive data (also affecting planning objects information, transactional data...) I think the most detailed log we get the best for us to be on the safe side and to avoid any risk.

We experienced in the past, with this same purge job that the defined filter was not properly taken by the system and as consequence more entries than expected were removed from our system... causing a great harm in our system. This is what we wanted to avoid. So by including this detailed log in the "Review" mode we can make sure that the execution is working as expected and therefore we can safely run it on real mode ensuring the scope of our data. 

Best regards, 

Sonia