2019 Aug 08 9:18 AM
I am trying to use cl_salv_bs_runtime_info in order to get the ALV data in memory after using SUBMIT in a standard report.
The code for the above is:
REPORT ztest1.
FIELD-SYMBOLS <lt_pay_data> TYPE ANY TABLE.
DATA lr_pay_data TYPE REF TO data.
cl_salv_bs_runtime_info=>set(
EXPORTING display = abap_false
metadata = abap_false
data = abap_true ).
SUBMIT rfts7000
AND RETURN.
TRY.
cl_salv_bs_runtime_info=>get_data_ref(
IMPORTING r_data = lr_pay_data ).
ASSIGN lr_pay_data->* TO <lt_pay_data>.
CATCH cx_salv_bs_sc_runtime_info.
MESSAGE `Unable to retrieve ALV data` TYPE 'E'.
ENDTRY.
cl_salv_bs_runtime_info=>clear_all( ).
When it is run the program rfts7000 runs and prompts for data selection.
ST22 extract:

After submitting the selection screen i get:

2019 Aug 08 9:55 AM
Hi,
i executed report RFTS7000 from se38 and encountered abap dump 'SYSTEM_ABAP_ACCESS_DENIED'
Pls go through below snote
2392358 - Avoid unnecessary read/write access to classic CM totals tables
Regards,
Mukhtar
2019 Aug 08 9:55 AM
It means that the program is blacklisted in S/4HANA, you cannot use it. Check SAP documentation and notes to find out what solution replaced it.
2019 Aug 08 10:22 AM
2249880 - Dump SYSTEM_ABAP_ACCESS_DENIED caused through Blacklist Monitor in SAP S/4HANA on premise
2019 Aug 08 10:38 AM
So the system protected me from running an obsolete program and i shouldn't be using it.
Moreover i found that note 2249880 offers a way out of this but suggests that you ask SAP for your specific case and if they approve there is a procedure to exclude the program from the blacklist...
So is it safe to assume that it was probably a mistake to start using this way of getting our liquidity position? (this is the purpose of this report).
I guess It is one of these things that will be on our heads for the following years until SAP finishes the transformation.