How to test destruction object via ILM_DESTRUCTION
- Step1 Create a new Audit Area via tcode ILMARA
- Step2 Destruction rule maintenance
- Step3 Launch destruction object
In the previous blog we have discussed how to implement destruction object.
In this article, we will look into how to test the destruction object SOCIAL_DESTRUCTION.
ILM Retention Management is a licensed product, which is really due to the fact that the predecessor to full ILM capability was data archiving which was always included as part of the core suite.
Step1 Create a new Audit Area via tcode ILMARA
Never forget to mark the checkbox “Object Assigned” to make your destruction object assigned to the new Audit area.
Step2 Destruction rule maintenance
Maintain destruction rule for your destruction object in tcode IRMPOL.
If for specified Audit area, there is already rule created for it, press Continue (it means you want to edit the existing rule). Or else press New for creation.
Just maintain the policy new and save it.
Below screenshot is a sample for retention rule maintenance. It means all social posts which are created ONE YEAR ago must be destroyed.
After you finish the rule edit, please make sure the policy status is set to “Live”, or else it will be ignored by rule engine in the runtime.
Step3 Launch destruction object
There are several variants which you can use to launch destruction functionality provided by destruction object.
Variant1 – Directly execute destruction program CRM_SOCIAL_ILM_DES on line via SE38
Test Mode: Under this mode, destruction program only does analysis on social post and list for each post, whether it could be destroyed according to resident time maintained in IMG activity and rules maintained in IRM rule maintenance view. No real deletion would be done.
Production Mode: Do the same analysis as Test Mode. The only difference is the real deletion would be done, if a social post is judged as destructible.
The execution result is output as example displayed below:
2. Application Log
The output will not be output directly to screen but written into application log instead.
You can review all logs by following below steps:
- transaction code ILM_DESTRUCTION, maintain the following settings and F8:
b. click button “Protokolle”:
Just specify the user name and execute selection:
Then you can view all logs generated during destruction run:
3. List and Application log
The output consists of both List output and Application log record.
Comment: This is an indicator for the current destruction run, which can help you identify the logs of the destruction run which you are interested with.