Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Select - Endselect gives a dump

Former Member
0 Likes
2,661

Hi Folks,

In our code we are using Select-Endselect. These a piece of code inside this select-endselect. Certain table has say 4 records corresponding to this query. Then the select-endselect works fine for 4 iterations. But then it dumps at the fifth one (when ideally it should should just skip to end-select). There are no breakpoints or commit statements inside the select-endselect.

Could you please suggest what could be the reason for this?

Thanks

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
1,748

Debugging a SELECT.... END SELECT statement, always leads to dump.

So don't debug a SELECT... ENDSELECT statement.

Regards,

Pavan P.

Eventually we had split up the query.

Regards,

Munish

11 REPLIES 11
Read only

Former Member
0 Likes
1,748

hi Munish,

Please place the dump details here

Regards,

Santosh

Read only

0 Likes
1,748

Hi Santosh,

The details are following:

The dump type is 'DBIF_RSQL_INVALID_CURSOR'.

From the details:

The error occurred in a statement in which table "FKKVKP " is accessed

The code:

008230 FROM fkkvkp AS ca

008240 JOIN ever AS c

008250 ON cavkont = cvkonto

008260 JOIN eanl AS i

008270 ON canlage = ianlage

008280 JOIN evbs AS p

008290 ON ivstelle = pvstelle

008300 JOIN iloa AS fl

008310 ON phaus = fltplnr

008320 JOIN adrc AS a

008330 ON fladrnr = aaddrnumber

> WHERE ca~gpart = t_partner-partner.

008350

Regards,

Munish

Read only

Former Member
0 Likes
1,749

Debugging a SELECT.... END SELECT statement, always leads to dump.

So don't debug a SELECT... ENDSELECT statement.

Regards,

Pavan P.

Read only

0 Likes
1,748

Hi Pavan,

The statement dumps even without debugging (with the same error). For testing, the breakpoint was set at the beginning (on the select ) only & not inside the select-endselect.

Regards,

Munish

Read only

0 Likes
1,748

Hi,

Can you just paste your code.

Regards,

Atish

Read only

Former Member
0 Likes
1,748

Hi !

Do you have code construction that causes implicid COMMIT WORK

(i.e. a function module that hase one, a call screen or a popup message ... ??)

That won't work within a SELECT-ENDSELECT.

In that case you'll have to change your code to a LOOP-ENDLOOP.

Regards

rainer

Some Reware points would be nice if that helped a bit...

Read only

0 Likes
1,748

Hi Rainer,

Theres a concatenation statement & a couple of other select statements inside select-endselect. Moreover it seems to work perfectly for first 4 iterations. (when there are only 4 corresponding records in the db table)

Regards,

Munish

Read only

Former Member
0 Likes
1,748

hi check out ur code

1> if you have used corresponding then the feilds shld be declared in the same order

2> check your data element for which it is giving u the dump is the declaration same as declared in database tabel.

please check these 2 points i hope u will get rid of the dump

also if it doesnt helps you paste your code here

thnkx

bhanu

Read only

0 Likes
1,748

Eventually we had split up the query.

Regards,

Munish

Read only

0 Likes
1,748

Eventually we had split up the query.

Regards,

Munish

Read only

Former Member
0 Likes
1,748

Hi,

In debugging mode Select- End select will go for dump most of times,

Come out of debugging and try..