Deleting expired application logs is key to improving mass activity performance issues

Question

During mass activity runs reference is made to the system's application logs during the process of line item selection. Performance based issues can be overcome by deleting old/expired application logs from the system, and rebuilding the affected table index. Based on my analysis on these issues, there has been a significant observation of 90% improvement in performance.

Answer 1

Dear Astrid,
Depending on the performance trace observed using transaction ST12, if for instance the SELECT on a particular table takes the most time, deleting all expired application logs and rebuilding the table index will result in a significant performance improvement.
Yes 90% improvement will be observed across the entire mass activity run. In my example below I use table BALHDR.
1. Run report SBAL_DELETE to delete all expired
application logs from table BALHDR
    1.1. At the selection screen of report
SBAL_DELETE, set the radio button for the expiry date to 'Only logs which have
reached their expiry date’
    1.2. Under the tab for 'Selection
conditions', enter the affected transaction code. e.g FPVA
    1.3. To delete the entries, set the radio
button under the Options tab to 'Delete immediately'
    1.4. Finally, execute or use shortcut F8 to
delete logs
2. Rebuild index 1 on table BALHDR (create a
secondary index on the table).
I hope this helps.
Kind Regards,
Adrian