topic Re: Regarding sql error.....ABAP Dump in Application Development and Automation Discussions

Regarding sql error.....ABAP Dump

Former Member — Mon, 15 Dec 2008 11:46:02 GMT

Hi Gurus...

The Dump is as below:

Error in RSQL module of database interface

o The maximum size of an SQL statement has been exceeded.

o The statement contains too many input variables.

o The space needed for the input data exceeds the available memory.

I am taking the values in a range for a buffer table

Logic written as follows.

SELECT vbfa_{vbelv vbrk}vbeln INTO TABLE i_vbfa_vbrk

FROM ( vbfa INNER JOIN vbrk

ON vbfa_{vbeln = vbrk}vbeln )

WHERE vbfa~vbelv IN r_buff_rcbal[]

AND vbfa~vbtyp_n = c_invoice

AND vbfa~vbtyp_v = c_delivery.

Please Advice for the the above problem.

Thanks in Advance...

Gaurav

Re: Regarding sql error.....ABAP Dump

matt — Mon, 15 Dec 2008 11:59:26 GMT

How many records do you have in VBFA, VBRK and r_buff_rcbal[].

Re: Regarding sql error.....ABAP Dump

ThomasZloch — Mon, 15 Dec 2008 12:00:21 GMT

r_buff_rcbal[] probably contains too many single entries, try splitting these into blocks of e.g. 1000, or - if only single entries are involved - also investigate using FOR ALL ENTRIES with an internal table instead of the range.

Thomas

Re: Regarding sql error.....ABAP Dump

Former Member — Mon, 15 Dec 2008 12:38:30 GMT

it is a typical dump with ranges, guess there are more than 1000 or 2000 lines in r_buff_rcbal

Use FOR ALL ENTRIES instead of your range:

WHERE vbfa~vbelv IN r_buff_rcbal[]

Siegfried

Re: Regarding sql error.....ABAP Dump

Former Member — Tue, 16 Dec 2008 07:09:38 GMT

I think the dump is because of range r_buff_rcbal[] . Check the range for values and also use a input variable for the screen. Sometimes timeout dump will occur because of this

regards

Shiva

Re: Regarding sql error.....ABAP Dump

Former Member — Tue, 16 Dec 2008 08:47:54 GMT

Hi, Gaurav.

Check the query statement using T-Code 'ST05'.(You can scan native sql using 'ST05')

When open sql statement returns native sql, IN Ranges clause returns the

union of the solution sets of all select statements that would result if you wrote

a separate statement for each line of the ranges.

SELECT vbfa~vbelv vbrk~vbeln INTO TABLE i_vbfa_vbrk
FROM ( vbfa INNER JOIN vbrk
ON vbfa~vbeln = vbrk~vbeln )
WHERE vbfa~vbelv IN r_buff_rcbal[]
AND vbfa~vbtyp_n = c_invoice
AND vbfa~vbtyp_v = c_delivery.

maybe returns native sql like this,

SELECT vbfa~vbelv vbrk~vbeln INTO TABLE i_vbfa_vbrk
FROM ( vbfa INNER JOIN vbrk
ON vbfa~vbeln = vbrk~vbeln )
WHERE ( vbfa~vbelv = r_buff_rcal-vbelv1 or
             vbfa~vbelv = r_buff_rcal-vbelv2 or
             vbfa~vbelv = r_buff_rcal-vbelv3 or
                 .... as many as count(r_buff_rcal)
AND vbfa~vbtyp_n = c_invoice
AND vbfa~vbtyp_v = c_delivery.

Namely, Ranges r_buff_rcbal has too much values.

That's why short dump arise.

Regards

Kyung Woo.

Re: Regarding sql error.....ABAP Dump

Former Member — Tue, 16 Dec 2008 10:15:15 GMT

Hi ,

I think the error is with r_buff_rcbal[].

if that doesnot contain any values all the entries will be fetched.

before this select statement check forr_buff_rcball entries.

the best method would be to use for all entries.

SELECT vbfa_{vbelv vbrk}vbeln INTO TABLE i_vbfa_vbrk

FROM ( vbfa INNER JOIN vbrk

ON vbfa_{vbeln = vbrk}vbeln )

for all entries in r_buff_rcball

WHERE vbfa~vbelv = r_buff_rcball-vbelv

AND vbfa~vbtyp_n = c_invoice

AND vbfa~vbtyp_v = c_delivery.

Re: Regarding sql error.....ABAP Dump

rainer_hbenthal — Tue, 16 Dec 2008 10:36:21 GMT

The in clause will result in abif SQL if there are many entries. use FAE and check the blocking factor.

Goto ST05 and check your SQL statement and see how big they will be.