topic Re: assertion_failed dump error while executing QA11 as per enclosed error file in Application Development and Automation Discussions

assertion_failed dump error while executing QA11 as per enclosed error file

former_member732290 — Mon, 10 May 2021 06:47:22 GMT

Dear experts,

I stuck with this dump for t-code QA11. please provide any solution .

assertion_failed dump error while executing QA11 as per enclosed error file

Here is the ST-22 dump analysis

Information on where terminated The termination occurred in ABAP program "SAPLSDH3", in "F4_GET_RESULT". The main program was "SAPMQEVA". In the source code, the termination point is in line 125 of (Include) program "LSDH3U03". Source Code Extract LineSourceCde 95* gearbeitet werden, um die DB-Wildcards % und _ zu maskieren. 96 PERFORM check_escape_allowed USING x030l_wa CHANGING escape. 97 98 CALL FUNCTION 'F4_CONV_SELOPT_TO_WHERECLAUSE' 99 EXPORTING 100 escape_allowed = escape 101 IMPORTING 102 where_clause = where_clause 103 TABLES 104 selopt_tab = iselopt. 105 106 CREATE DATA result_ref TYPE STANDARD TABLE OF (sel_method). 107 ASSIGN result_ref->* TO <itab>. 108 109* The following SELECT is done with oracle hint 110* %_HINTS ORACLE '&SUBSTITUTE LITERALS&' due to internal 111* message 1826019/2006 112* changed to '&SUBSTITUTE VALUES&' due to changed kernel behaviour 113* since 720 kernel 04/2012, note 1711474 114* Changed again to '&FIRST_ROWS(n)' to trigger the database optimizer 115* with note 2567844 116 117* security check for dynamic select 118 lv_devclass = 'DUMMY'. 119 insert lv_devclass into table lt_packages. 120 try. 121 sel_method = cl_abap_dyn_prg=>check_table_or_view_name_tab( 122 val = sel_method 123 packages = lt_packages ). 124 catch cx_abap_not_a_table. >>>>> assert 1 = 2. 126 catch cx_abap_not_in_package. 127* Package check is not relevant here, only the existence of the table 128* needs to be checked. Therefore using 'DUMMY' 129 endtry. 130 131 IF cursor-with_cursor NE space. 132 IF cursor-c IS INITIAL. 133* Nur den Cursor öffnen. Der Fetch wird vom Aufrufer gemacht. 134** Weil dabei die DB-Schnittstelle den UP TO N ROWS nicht mehr 135** mitbekommt, muß der first_rows hint manuell mitgegeben 136** werden. 137 IF cursor-with_cursor EQ 'P'. 138* in this case we need to select without UP TO xx ROWS because the next 139* fetch can not be done if max_select is fullfilled 140 IF sort = space. 141 OPEN CURSOR cursor-c FOR 142 SELECT * FROM (sel_method) 143 WHERE (where_clause) 144 %_HINTS ORACLE '&SUBSTITUTE VALUES&'..

Thanks,

External

Re: assertion_failed dump error while executing QA11 as per enclosed error file

ziolkowskib — Mon, 10 May 2021 09:16:16 GMT

Hi sasr,
Have you tried to use SAP Knowledge Base Search?

I can see there is an SAP note 2938009 that more or less describes the shortdump you pasted here.

Regards,
Bartosz

Re: assertion_failed dump error while executing QA11 as per enclosed error file

former_member732290 — Mon, 10 May 2021 09:24:52 GMT

Dear ziolkowskib,

Thanks for the reply. But the note 2938009 is applied for s/4 hana and my issue is occured on ECC. Is there any clue apart from that.

Thanks,

External

Re: assertion_failed dump error while executing QA11 as per enclosed error file

ziolkowskib — Mon, 10 May 2021 09:36:06 GMT

Well, you did not enclose any information about the system 🙂

Did you stumble upon this one?

2867802 - F4: consider selection methods without TADIR entries

Regards,
Bartosz

Re: assertion_failed dump error while executing QA11 as per enclosed error file

former_member732290 — Mon, 10 May 2021 10:18:41 GMT

Thank U.

As it's not possible to customize the code solution part because this is a standard program. But I got a clue to import the specified support package. I just started to do that.

Re: assertion_failed dump error while executing QA11 as per enclosed error file

Sandra_Rossi — Mon, 10 May 2021 11:50:25 GMT

It's very easy if you encounter any "assertion_failed" error, it means that the developer thought that this condition can never occur but it did. So it's a programming error, and you have to ask the developer to fix the bug. -> SAP Support if it's standard?