topic Re: Runtime error “SYSTEM_ABAP_ACCESS_DENIED” when using SUBMIT via custom report in Application Development and Automation Discussions

Runtime error “SYSTEM_ABAP_ACCESS_DENIED” when using SUBMIT via custom report

e4rthdog — Thu, 08 Aug 2019 08:18:20 GMT

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:

Re: Runtime error “SYSTEM_ABAP_ACCESS_DENIED” when using SUBMIT via custom report

Mohamed_Mukhtar — Thu, 08 Aug 2019 08:55:46 GMT

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

Re: Runtime error “SYSTEM_ABAP_ACCESS_DENIED” when using SUBMIT via custom report

Sandra_Rossi — Thu, 08 Aug 2019 08:55:49 GMT

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.

Re: Runtime error “SYSTEM_ABAP_ACCESS_DENIED” when using SUBMIT via custom report

FredericGirod — Thu, 08 Aug 2019 09:22:30 GMT

2249880 - Dump SYSTEM_ABAP_ACCESS_DENIED caused through Blacklist Monitor in SAP S/4HANA on premise

Re: Runtime error “SYSTEM_ABAP_ACCESS_DENIED” when using SUBMIT via custom report

e4rthdog — Thu, 08 Aug 2019 09:38:09 GMT

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.