Hello.
I want to shre the idea of blocking obsolete reports from execution and ask for your ideas.
In our core ERP system there are a lot of Z reports (>8k) with transactions attached to them.
And I want to lock the oldest of them from execution.
So when user start the ZABC transaction, or ZDEF report from SE38(SA38), or when user schedule background job there will be a message 'The report ZABCD is locked because ...".
Who knows the best way to do it without changing ABAP code of reports?
For example we store the names of locked reports in custom database table and any report before execution should be checked.
If it is in the table, a popup message should be shown and execution should be stopped.
Locking via SM01 is not convinient, because only transactions are being locked, so this doesn't help.
I have found several standart function modules which can be enhanced with custom code to check the locking of an reports. They are
1) JOB_SUBMIT - can stop background schedule
2) AUTH_CHECK_TCODE - can check transaction code
3) SUBMIT_REPORT - can stop execution from SE38(SA38)
I have locked 30% of our Z reports. They all are obsolete. But 3 enhancements are too much. And they cannot check for execution of function modules.
Maybe you know only one standart object that can be enhanced to check execution of reports/function modules?
Or maybe there is standart BADI for it?
Is there any fresh ideas?
Thanks is advance.
Anatoliy Stypshin,
Custom Code Management Tead Lead.