Runtime Error:Invalid interruption of a database selection

Question

Hi,
I have the above mentioned runtime error (short text of runtime error) while executuing FM with the runtime error DBIF_RSQL_INVALID_CURSOR and exception CX_SY_OPEN_SQL_DB.
the source code  for the cause of the error is as follows:
{       PERFORM fill_spras USING g_r_werks[]
                      CHANGING g_r_spras[].
      IF g_r_spras[] IS INITIAL.
  Please specify a value for Language.
        MESSAGE e003(yy_master_data).
        RAISE error_passed_to_mess_handler.
      ENDIF.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
      OPEN  CURSOR s_marc FOR SELECT *
      FROM  marc
      WHERE werks IN g_r_werks AND
            matnr IN g_r_matnr.
    ENDIF.                             "First data package
Fetch records into interface table.
  named E_T_'Name of extract structure'.
    FETCH NEXT CURSOR s_marc INTO TABLE gt_marc PACKAGE SIZE s_s_if-maxsize.
    IF sy-subrc = 0.
      DELETE ADJACENT DUPLICATES FROM gt_marc COMPARING matnr}
the pointer shown in the runtime analysis is at if sy-subrc EQ 0.
while debugging also it gives run time error when curson reaches the statement FETCH Next Cursor.
Any ideas?

Answer 1

Hi Simran,
if for whatever reason the process is interrupted between SELECT and ENDSELECT (or, in other words, after OPEN CURSOR between subsequent FETCHes), you will get this error: The Database is exspected to run within one logical unit of work.
If any screen is displayed waiting for user input (this also applies for debug screen), an implicit commit is is done that finishes the current LUW. The database will not like it....
That's why you should do only minor things between SELECT and ENDSELECT (OPEN/CLOSE CURSOR).
The E Message will also cause the end of the LUW.
Regards,
Clemens