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

SQL DUMP

Former Member
0 Likes
1,267

Hi Friends

i have declared one internal table like this it like pa0001 occurs 0 with header line ,

and am using SQL query like this ,

select pernr endda begda werks persg persk btrtl orgeh plans ename

from pa0001 into corresponding fields of table

it where pernr in pnppernr and

endda ge sy-datum and

begda le sy-datum and

werks in pnpwerks and

persg in pnppersg and

persk in pnppersk and

btrtl in pnpbtrtl and

( ( orgeh in pnporgeh ) or

( orgeh in pnpobjid ) ).

but am getting dump some time when so many records are there and dump saya that too many input parameters and no more space for input parameters

What i shd do to correct this ?

Regards

Smeeta

8 REPLIES 8
Read only

jaideepsharma
Active Contributor
0 Likes
1,143

Hi,

Can you please send us screenshot of your code including the data declaration part ?

KR Jaideep,

Read only

former_member219399
Active Participant
0 Likes
1,143

Hi,

This could be because of more numbe rof entries with the select options or ranges that you are using.

Try to reduce the number of entries in these and do another filter.

May be this will resolve the short dump.

With regards,

Vamsi

Read only

Former Member
0 Likes
1,143

Check if you can add subty, objps and sprps as aditional search parameters, this way you'll be using almost all the table key and thus receive a great speed bump, so the search will not timeout even if it has many entries.

Perhaps you'll need to remove some of your parameters to pull this off (if there are too many parameters), and the postprocess the internal table to add the missing filters.

Read only

Former Member
0 Likes
1,143

Most probable cause: Length of your SQL when converted to Native SQL it lengthy by supported by database. Tyr reducing the lenth. IN clause increases SQL length significantly.

Read only

Former Member
0 Likes
1,143

Dear Friends-

Problem is i have to match with all Selection Screen parameters so am using those so many IN in SQL query to get the exact matching record i can't reduse them so is there any other valuable suggestion i can use ?

Regards

Smeeta

Read only

0 Likes
1,143

As I've mentioned, you can remove some of those parameters from the original select, receive more records and then use the removed parameters in a loop over the resulting records to postprocess and eliminate those records that are not needed as per selection.

Read only

Former Member
0 Likes
1,143

Hi,

Please chk whether u r passing the values in the same order in the selection query

as in the Internal table.

And also as u r selecting many fields check the range of the fields

Read only

Former Member
0 Likes
1,143

ok