Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

DBIF_RSQL_INVALID_CURSOR : Error extracting records in RSA3 for 2LIS_02_ITM

Hi

I'm extracting the data in R/3 system using tcode RSA3 for transaction datasource (2LIS_02_ITM). When i extracted the transaction data , it was giving time out error. Then i went into debug mode to find the error. While debugging the code it gave me a DBIF_RSQL_INVALID_CURSOR short dump.

NOTE : Data extraction is working for all 02 transaction data like 2LIS_02_SCL , 2LIS_02_S012. It s failing for only 2LIS_02_ITM only.

I have pasted the eror message below for reference. Urgent help required.

From

Bobby

ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR

***********************************

Runtime Errors DBIF_RSQL_INVALID_CURSOR

Except. CX_SY_OPEN_SQL_DB

Date and Time 09.04.2008 12:47:09

-


-


Short text

Invalid interruption of a database selection.

-


-


What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLMCEX" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Unable to perform database selection fully.

-


-


Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "MCEX_BW_LO_API" "(FUNCTION)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

One of the database selections included a database Commit.

The selection was then supposed to continue. Before a

database commit, however, all outstanding database selections

must be concluded.

Possible causes in the application program:

While a read process from a database cursor is taking place

(within a loop SELECT/LOOP/EXEC SQL or before a FETCH command),

one of the following statements is used:

- MESSAGE (apart from MESSAGE S...)

- COMMIT WORK

- ROLLBACK WORK

- BREAK-POINT

- WAIT

- CALL FUNCTION ... DESTINATION (synchronous RFC)

- CALL FUNCTION ... STARTING NEW TASK

- RECEIVE RESULTS

- CALL DIALOG

- CALL SELECTION-SCREEN

- CALL TRANSACTION

- CALL SCREEN, or any other statement that results in the display of a

new screen

Whenever a program runs in debugging mode, a "COMMIT WORK" can

possibly be triggered during database selection. This abnormal

termination can also occur in debugging mode even with a correct

program.

A "COMMIT WORK" during debugging may be due to the following reasons:

1. A program or screen was regenerated during debugging

and updated in the database.

2. Each user needs a separate process in debugging mode, but

the number of available processes is restricted. If this

limit is exceeded, each debugging step then requires a

"COMMIT WORK".

The error occurs in a statement in which the table "MC02M_0ITMSETUP " is

accessed.

-


-


Missing RAISING Clause in Interface

Program SAPLMCEX

Include LMCEXU06

Row 1

Module type (FUNCTION)

Module Name MCEX_BW_LO_API

-


-


Trigger Location of Exception

Program SAPLMCEX

Include LMCEXU06

Row 220

Module type (FUNCTION)

Module Name MCEX_BW_LO_API

-


-


Source Code Extract

-


Line

SourceCde

-


190

at end of fieldnm. "PI 2000.2 SP_353722

191

if not <fs_field> in cond_select_tab.

192

cond_select = false.

193

refresh cond_select_tab. "PI 2000.2 SP_353722

194

exit.

195

endif.

196

refresh cond_select_tab. "PI 2000.2 SP_353722

197

endat. "PI 2000.2 SP_353722

198

endloop.

199

if cond_select eq true.

200

append &2 to e_t_data.

201

add 1 to counter.

202

endif.

203

endloop.

204

if s_maximum_size le counter.

205

exit.

206

endif.

207

else.

208

close cursor g_cursor.

209

s_flg_no_more_data = true.

210

exit.

211

endif.

212

enddo.

213

END-OF-DEFINITION.

214

          • end macro *****

215

216

CASE s_estruc.

217

  • extractstruc internal table setup table

218

*-- MM-PUR

219

sel 'MC02M_0HDR' mc02m_0hdr_tab mc02m_0hdrsetup.

>>>>>

sel 'MC02M_0ITM' mc02m_0itm_tab mc02m_0itmsetup.

221

sel 'MC02M_0SCL' mc02m_0scl_tab mc02m_0sclsetup.

222

sel 'MC02M_0SGR' mc02m_0sgr_tab mc02m_0sgrsetup.

223

sel 'MC02M_0SCN' mc02m_0scn_tab mc02m_0scnsetup.

224

sel 'MC02M_0CGR' mc02m_0cgr_tab mc02m_0cgrsetup.

225

sel 'MC02M_0ACC' mc02m_0acc_tab mc02m_0accsetup.

226

*-- Application '03' (Inventory Management)

227

sel 'MC03BF0' mc03bf0_tab mc03bf0setup.

228

sel 'MC03BX0' mc03bx0_tab mc03bx0setup.

229

sel 'MC03UM0' mc03um0_tab mc03um0setup.

230

*-- Application '04'

231

sel 'MC04P_0MAT' mc04p_0mat_tab mc04p_0matsetup.

232

sel 'MC04P_0ARB' mc04p_0arb_tab mc04p_0arbsetup.

233

sel 'MC04P_0COM' mc04p_0com_tab mc04p_0comsetup.

234

sel 'MC04PE0MAT' mc04pe0mat_tab mc04pe0matsetup.

235

sel 'MC04PE0ARB' mc04pe0arb_tab mc04pe0arbsetup.

236

sel 'MC04PE0COM' mc04pe0com_tab mc04pe0comsetup.

237

*-- Application '05' (Quality Management)

238

sel 'MC05Q1_0INSP' mc05q1_0insp_tab mc05q1_inspsetup.

239

sel 'MC05Q2_0INSP' mc05q2_0insp_tab mc05q2_inspsetup.

-


Former Member
Not what you were looking for? View more on this topic or Ask a question