Runtime Error in SQL command ..

Question

Hi everybody
I have a report wich terminates with a dump message.
The error is in an SQL command, here the program aborts:
SELECT KUNNR KKBER KLIMK SAUFT SKFOR SSOBL
    INTO TABLE I_KNKK
    FROM KNKK
   WHERE KUNNR IN R_KUNNR
     AND KKBER IN R_KKBER
     AND SBGRP IN S_SBGRP.
DATA: BEGIN OF I_KNKK OCCURS 0,
      KUNNR LIKE KNKK-KUNNR,
      KKBER LIKE KNKK-KKBER,
      KLIMK LIKE KNKK-KLIMK,
      SAUFT LIKE KNKK-SAUFT,
      SKFOR LIKE KNKK-SKFOR,
      SSOBL LIKE KNKK-SSOBL,
      SBGRP LIKE KNKK-SBGRP,
      END OF I_KNKK.
In first moment, i saw the table and SQL filter have the SBGRP field but the SQL fields selection has not this field. But, these same program works good with others selection parameters, in fact this SQL only terminates the program for the bigest company, wich causes the program make many BD access because all previous SQL.
The dump log says:
Runtime errors         DBIF_RSQL_INVALID_RSQL
Exception              CX_SY_OPEN_SQL_DB
Occurred on            23.05.2006 at   17:27:15
Error in the module RSQL accessing the database interface.
An exception occurred. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB',  neither caught nor passed along using a RAISING clause, in the procedure "(FORM)" . Since the caller of the procedure could not have expected this except to occur, the running program was terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL Statement violates restriction imposed by the database system used in R/3.
Possible errors:
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.
o ...
How can i be sure the dump is for a lot of BD access for all the SQL commands ?
If these is the error, does somebody knows how can i eliminate this error ?
Please help ..
Regards
Frank

Answer 1

I think the field discrepancy is a red herring here. Not guilty! I agree that using the 'CORRESPONDING FIELDS OF' is safer though.
The error could be happening because your range variables have lots of entries in them which makes the generated sql huge.
To break it up you could use the 'package size' option of the select. This will work it's way through the input in chunks (or packages) of the size you specify.
You could change it to:
SELECT KUNNR KKBER KLIMK SAUFT SKFOR SSOBL 
INTO TABLE I_KNKK package size 2000 "or a variable value      
FROM KNKK                                  
WHERE KUNNR IN R_KUNNR                     
AND KKBER IN R_KKBER                       
AND SBGRP IN S_SBGRP.                      
process current contents of i_knkk here                                           
endselect.     
or ,
SELECT KUNNR KKBER KLIMK SAUFT SKFOR SSOBL 
appending TABLE I_KNKK package size 2000       
FROM KNKK                                  
WHERE KUNNR IN R_KUNNR                     
AND KKBER IN R_KKBER                       
AND SBGRP IN S_SBGRP.                      
endselect.