DBIF_RSQL_INVALID_RSQL CX_SY_OPEN_SQL_DB

Hi friends,
I searched in sdn , i came t o know that it is because of select query with select-options ( Having large number of single values )   .
My select query will be like this..
   SELECT abelnr akunnr abukrs azuonr axblnr ahbkid abudat avbeln arebzg admbtr ablart ashkzg bbktxt axzahl aumskz agjahr
           INTO CORRESPONDING FIELDS OF TABLE it_bsid
            FROM bsid AS a INNER JOIN bkpf AS b ON abelnr EQ bbelnr AND  agjahr EQ bgjahr
            WHERE  a~bukrs EQ p_bukrs
            AND    a~kunnr  IN s_ekunnr
            AND    a~budat  IN s_erdat
            AND    a~hbkid  IN s_hbkid
             AND  a~gjahr  EQ p_gjahr
           AND ( ablart EQ c_blart OR ablart EQ 'DA' ) .
s_ekunnr-low contains customer numbers .. when i debug , i came to know that 10,200 customers are there ..
kindly provide any solution , how to rectify this ..
thanks & regards,
raghul

types: begin of w_kunnr  ,
           kunnr type lfa1-lifnr  ,
           end of w_kunnr .
data : it_kunnr type standard table of w_kunnr with header line .
select kunnr into corresponding fields of table  it_kunnr
from table  X
if it-kunnr[] is not initial  .
SELECT abelnr akunnr abukrs azuonr axblnr ahbkid abudat avbeln arebzg admbtr ablart ashkzg bbktxt axzahl aumskz agjahr
INTO CORRESPONDING FIELDS OF TABLE it_bsid
for all entries in it_kunnr 
FROM bsid AS a INNER JOIN bkpf AS b ON abelnr EQ bbelnr AND agjahr EQ bgjahr
WHERE a~bukrs EQ p_bukrs
AND a~kunnr  = it_kunnr-kunnr 
AND a~budat IN s_erdat
AND a~hbkid IN s_hbkid
AND a~gjahr EQ p_gjahr
AND ( ablart EQ c_blart OR ablart EQ 'DA' ) .
endif.
Regards
Deepak.

Similar Messages

  • Runtime error - DBIF_RSQL_INVALID_RSQL, CX_SY_OPEN_SQL_DB in a fixed period

    hi
    i get a Runtime error - DBIF_RSQL_INVALID_RSQL, Exception - CX_SY_OPEN_SQL_DB when i run a periodic background program which is defined by myself
    i find that there are many threads refer to this problem
    but mine have something special,that is it would be cancelled because of the reason mentioned above in a fixed period(00:00am-08:30am) everyday (p.s. our company's standand work time begins at 08:30am),and in other time period of the day,it could run successfully.
    so i am confused ,what possible reasons would lead to this problem?what should i do to hand it ?
    waiting for your answer ,thanks very much.
    vita

    clemens
    thanks,i have tried your ways,but i think i am too new in this feild to get a point from the dump
    i will appriciate it if you could help me to analysis the dump info
    here are those info ,hope it is useful
       >>>>>     SELECT vbpaVBELN vbpaKUNNR  into TABLE it_kno FROM vbpa  WHERE  vbpaPARVW  ='WE' AND vbpaVBELN  IN  r_VBELN9.
         SORT it_kno by KUNNR .
         delete ADJACENT DUPLICATES FROM it_kno .
         LOOP at it_kno .
            r_KUNNR-sign   = 'I'.
            r_KUNNR-option = 'EQ'.
            r_KUNNR-low    = it_kno-KUNNR.
            COLLECT r_KUNNR.
            CLEAR r_KUNNR.
          ENDLOOP .
    系统字段的内容
    Name             Val.
    SY-SUBRC      0
    SY-INDEX       0
    SY-TABIX     42
    SY-DBCNT    230
    SY-FDPOS     0
    SY-LSIND     0
    SY-PAGNO   0
    SY-LINNO      1
    SY-COLNO    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE      订单执行跟踪表_后台程序
    SY-MSGTY   I
    SY-MSGID    SF
    SY-MSGNO  616
    SY-MSGV1  ZSDRD_17
    SY-MSGV2  RE
    SY-MSGV3  ZH
    SY-MSGV4
    SY-MODNO   0
    SY-DATUM   20091117
    SY-UZEIT     000015
    SY-XPROG    SAPCNVE
    SY-XFORM   CONVERSION_EXIT

  • Dump DBIF_RSQL_INVALID_RSQL

    Dear all
    I am facing a problem related to abap program, when I run the program like zmatlist
    When I give Material Number in selection option ( for example 20000 Material Number )
    In one go then abap report give me the following DUMP
    DBIF_RSQL_INVALID_RSQL
    CX_SY_OPEN_SQL_DB
    And when in give selection option in chunk the that report run fine
    After the dump I check dev_w0 file it shows like that
    *C *** ERROR => max. statement length (65536) exceeded*
    http://dbsloci.c 5759
    C Dumping statement ...
    C 0 | TEXT | 6 | SELECT
    C 1 | TEXT | 4 | T_00
    C 2 | TEXT | 1 | .
    C 3 | IDENTIFIER | 5 | BISMT
    So on
    C 17481 | TEXT | 3 | AND
    C 17482 | TEXT | 4 | T_02
    C 17483 | TEXT | 1 | .
    C 17484 | IDENTIFIER | 5 | WERKS
    C 17485 | TEXT | 1 | =
    C 17486 | MARKER(8588)| 0 | NULL
    C token_cnt=17487, input_cnt=8589, marker_cnt=8589, stmt_length=86128
    B ***LOG BYK=> current SQL statement exceeds a database limit dbtran#5 @ 7261 dbtran 7261
    B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
    thankx
    Rayyan

    Hi Shahid,
    Please refer OSS note:
    Note 48230 - Parameters for the SELECT ... FOR ALL ENTRIES statement
    which explains the various option to solve your problem.
    The dump is occuring because of too many inputs(20000 material number) in the select option.
    Please let me know if this helpful, by rating.
    Regards
    Prashanth

  • Short dump in SAP R/3: SQL statement buffer overflow?

    Hello,
    I hope someone can help us with the following problem:
    A short dump in SAP R/3 (DBIF_RSQL_INVALID_RSQL, CX_SY_OPEN_SQL_DB)
    occurred during a delta load, which worked fine for several month.
    The custom code crashes at a FETCH NEXT CURSOR statement.
    I assume, it might be a SQL statement buffer overflow in SAP R/3?
    The problem can be reproduced by RSA3, and is therefore not time-dependent.
    The problem did not occur before or on the quality assurance system.
    Cursor code:
          Read all entries since last transfer (delta mechanism)
            OPEN CURSOR WITH HOLD s_cursor FOR
              SELECT * FROM ekko
                WHERE ebeln IN t_selopt_ekko.
    t_selopt_ekko has up to 60.000 data sets, which worked fine in the past.
    It is very likely that the amount of data during the first crash did not exceed this.
    SQL-Trace of RSA3 call:
    It seems that 25150 data set can be processed via fetch before the short dump occurs
    After that object SNAP is written:
    "...DBIF_RSQL_INVALID_RSQL...dynpen00 + 0xab0 at dymain.c:1645 dw.sapP82_D82
    Thdyn...Report für den Extraktoraufruf...I_T_FIELDS...Table IT_43[16x60]TH058FUNCTION=
    RSA3_GET_DATA_SIMPLEDATA=S_S_IF_SIMPLE-T_FIELDSTH100...shmRefCount  = 1...
    ...> 1st level extension part <...isUsed       = 1...isCtfyAble   = 1...> Shareable Table Header Data
    <...tabi         = Not allo......S_CURSORL...SAPLRSA3...LRSA3U06...SAPLRSA3...
    During dump creation the following occurs:
    "...SAPLSPIAGENTCW...CX_DYNAMIC_CHECK=...CRSFH...BALMSGHNDL...
    DBIF_RSQL_INVALID_RSQL...DBIF_RSQL_INVALID_RSQL...DB_ERR_RSQL_00013...
    INCL_ABAP_ERROR...DBIF_INCL_INTERNAL_ERROR...INCL_INTERNAL_ERROR...
    GENERAL_EXC_WITHOUT_RAISING...INCL_SEND_TO_ABAP...INCL_SEARCH_HINTS...
    INCL_SEND_TO_SAP...GENERAL_EXC_WITHOUT_RAISING...GENERAL_ENVIRONMENT...
    GENERAL_TRANSACTION...GENERAL_INFO...GENERAL_INFO_INTERNAL...
    DBIF_INCL_INTERNAL_CALL_CODE..."
    Basis says, that the Oracle data base works fine. The problem seems to be a SAP R/3 buffer.
    Does anyone had a similar problem or knows where such a buffer might be or how it can be enlarged?
    Best regards
    Thomas
    P.S.
    Found a thread that contains part of the dump message "dynpen00 + 0xab0 at dymain.c:1645":
    Thread: dump giving by std prg contains -> seems not to be helpful
    Found a similar thread:
    Thread: Short dump in RSA3 --Z Data Source -> table space or somting else?
    Edited by: Thomas Köpp on Apr 1, 2009 11:39 AM

    Hi Thomas,
          Its due to different field length.
    Just check it out in code after FETCH NEXT CURSOR what internal table you have mention.
    that internal table shoul deffined by taking refrence of ekko, because your code is
    OPEN CURSOR WITH HOLD s_cursor FOR
    SELECT * FROM ekko
    WHERE ebeln IN t_selopt_ekko.
    hope you got solution.
    Regards,

  • BI ABAP  Dump Error

    Hi Experts
      ABAP Error in BI
      calling PSA table to my program it contains more than 200000 records also applying grouping in select statement
    But it showing dump  .
    please correct me if any wrong in my code.
    BREAK-POINT.
        DATA : BEGIN OF ITAB4 OCCURS 0,
          REPORT_TYPE LIKE /BIC/B0007048000-REPORT_TYPE,
          JV_NO LIKE  /BIC/B0007048000-JV_NO,
           AMOUNT LIKE /BIC/B0007048000-AMOUNT,
          RECORD_COUNT LIKE /BIC/B0007048000-RECORD,
          END OF ITAB4.
    DATA:  WTAB4 LIKE ITAB4.
    SELECT REPORT_TYPE JV_NO SUM(  AMOUNT ) COUNT(*)
           INTO TABLE ITAB4 PACKAGE SIZE 5000
           FROM /BIC/B0007048000
           GROUP BY REPORT_TYPE JV_NO.
         ENDSELECT.
    BELOW is the dump error
    solution please
    Check the entries in the developer trace of the relevant work process
    (transaction ST11).
    Here you can find detailed information about the type and length of the
    database field as well as the ABAP field into which the field was to be
    imported.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_INVALID_RSQL" "CX_SY_OPEN_SQL_DB"
    "ZREVRECON" or "ZREVRECON"
    "START-OF-SELECTION"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program

    Hi,
    I believe the short-dump is due to the excessively large amount of data that is being fetched. A direct SELECT on the database will not help, even though you are appending in a PACKAGE SIZE.
    You could try out the statement OPEN CURSOR to fetch the data. I have used this procedure before.
    Please try as per the example given below:
    OPEN CURSOR: lv_cursor FOR SELECT  pstng_date ucrate_cat ucdeeinvdn
                                FROM  /bic/azsod00200 FOR ALL ENTRIES IN li_source_package
                               WHERE ucdeeinvdn = li_source_package-ucdeeinvdn.
          DO.
            IF lv_flag NE 'X'.
              FETCH NEXT CURSOR lv_cursor INTO TABLE li_zso002 PACKAGE
              SIZE 5000.
              IF sy-subrc <> 0.
                CLOSE CURSOR lv_cursor.
                lv_flag = 'X'.
              ENDIF.
            ENDIF.
          ENDDO.

  • How to get the Database Type quan in my internal table?

    Hi, I have the following problem, I have a Database Table with a column foo (QUAN with length 15 and 3 dec). Now I want to read this field into a Internal Table and the corrospoding field is:
    foo(19) TYPE C,
    But this is not working I'm getting the dump:
    DBIF_RSQL_INVALID_RSQL
    CX_SY_OPEN_SQL_DB
    What is the correct abap type in my structure to put this QUAN in my internal table?

    Hi Michael,
         when you know your data base field name then u can define your variable f00 of your db field type like
         foo type <dbtabname>-<fieldname)  -----ex -- j_1iexcdtl-menge
         or define foo as packed no
         data : foo(19) type p decimals 3.
    Regards

  • Baseline Activation problem

    I'm activating a baseline on an erp. I was fine until i get this error:
    Runtime Errors         DBIF_RSQL_INTERNAL_ERROR
    Short text
        Internal error when accessing a table.
    What happened?
        The current ABAP/4 program terminated due to
        an internal error in the database interface.
    Error analysis
        An internal error in the database interface occurred during access to
        the data of table "T090NS ".
        The situation points to an internal error in the SAP software
        or to an incorrect status of the respective work process.
        For further analysis the SAP system log should be examined
        (transaction SM21).
        For a precise analysis of the error, you should supply
        documents with as many details as possible.
    Trigger Location of Runtime Error
        Program                                 SAPLATST
        Include                                 LATSTF00
        Row                                     1.675
        Module type                             (FORM)
        Module Name                             DB_UPD_V_T090NS_1
    SM21 and ST22 show the same errors.
    Please i need an answer i search already on sapnotes, sdn, google and nothing.
    Thanks a lot..
    Edited by: pamelitius on Feb 18, 2010 8:40 PM

    HI, Im facing exactly the same problem . Iwas activating baseline peru using /smb/bbi and then suddenly while activating it shows a dump Error in module RSQL of the database interface.
    DBIF_RSQL_INVALID_RSQL
    CX_SY_OPEN_SQL_DB
    Program                                 SAPLATST
    Include                                 LATSTF00
    Row                                     1,675
    Module type                             (FORM)
    Module Name                             DB_UPD_V_T090NS_1
    Can you help if you solved this issue??
    Regards Franklin

  • Runtime error - DBIF_RSQL_INVALID_RSQL, Exception - CX_SY_OPEN_SQL_DB

    Hi,
    Following code is working fine in Development system and in Production system I am getting a runtime error. Only difference I am finding is in r_lifnr value. In development system I have few lifnr and in Production system it's not so... am I getting error because of it? Is there any restriction to no. of items populated in a range? Or Basis person need to change any parameter? Enclosed the detail dump below the code...
    Advance thanks.
    Regards,
    Balaji Viswanath.
    Code:
      SELECT bukrs
             lifnr
             augdt
             augbl
             zuonr
             gjahr
             belnr
             buzei
             waers
             dmbtr
             wrbtr
             zlsch
             shkzg
             blart
             gsber
             sgtxt
      INTO TABLE t_bsak_tmp
      FROM bsak CLIENT SPECIFIED
      WHERE mandt = sy-mandt AND
            lifnr IN r_lifnr AND
            bukrs IN s_bukrs AND
            augdt IN s_augdt AND
            blart IN s_blart.
      IF sy-subrc <> 0.
      No data found for selection criteria
        MESSAGE i018.
        LEAVE LIST-PROCESSING.
      ENDIF.
    Dump:
    Runtime Errors         DBIF_RSQL_INVALID_RSQL
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     14.11.2005 at 14:35:22
    Error in the module RSQL accessing the database interface.
    What happened?
    Error in ABAP application program.
    The current ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P" had to be terminated
    because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    Error analysis
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "GET_CLRD_VEN_DATA" "(FORM)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    The SQL statement generated from the SAP Open SQL Statement violates a
    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 ...
    You can usually find details in the system log (SM21) and in the
    developer trace of the work process (ST11).
    If an error occurs the developer trace often informs you about the
    current restrictions.
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "GET_CLRD_VEN_DATA"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    The SAP Open SQL statement must be divided into several smaller units.
    If the problem occurred due to the use of an excessively large table
    in an IN itab construct, you can use the addition FOR ALL ENTRIES
    instead.
    When you use this addition, the statement is split into smaller units
    according to the restrictions of the database system used.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
    "/DS1/FI_CR_REPT_PGSR802_VEND_P" or "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    "GET_CLRD_VEN_DATA"
    If you cannot solve the problem yourself, please send the
    following documents to SAP:
    1. A hard copy print describing the problem.
       To obtain this, select the "Print" function on the current screen.
    2. A suitable hardcopy prinout of the system log.
       To obtain this, call the system log with Transaction SM21
       and select the "Print" function to print out the relevant
       part.
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, you can either use the "PRINT" command in the editor or
       print the programs using the report RSINCL00.
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    System environment
    SAP Release.............. "620"
    Application server....... "ztm1003"
    Network address.......... "145.26.160.103"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C004DC4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 6
    Short dump setting....... "full"
    Database server.......... "ztm1003"
    Database type............ "ORACLE"
    Database name............ "A94"
    Database owner........... "SAPR3K"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Aug 7 2005 20:44:35"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "85"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
    10.1.0.."
    SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
    User, transaction...
    Client.............. 110
    User................ "INBVI0"
    Language key........ "E"
    Transaction......... "SE38 "
    Program............. "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
    Information on where terminated
    The termination occurred in the ABAP program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    in "GET_CLRD_VEN_DATA".
    The main program was "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
    The termination occurred in line 503 of the source code of the (Include)
    program "/DS1/FI_CR_REPT_PGSR802_VEND_P"
    of the source code of program "/DS1/FI_CR_REPT_PGSR802_VEND_P" (when calling
    the editor 5030).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "GET_CLRD_VEN_DATA" "(FORM)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "/DS1/FI_CR_REPT_PGSR802_VEND_P ". Its source
    code starts in line 501
    of the (Include) program "/DS1/FI_CR_REPT_PGSR802_VEND_P ".
    Source code extract
    004730   &----
    004740   *       get country names from t005t
    004750   ----
    004760   FORM get_country_names.
    004770
    004780     t_lfa1_land[] = t_lfa1[].
    004790     SORT t_lfa1_land BY land1.
    004800     DELETE ADJACENT DUPLICATES FROM t_lfa1_land COMPARING land1.
    004810
    004820     IF NOT t_lfa1_land[] IS INITIAL.
    004830       SELECT land1
    004840              landx
    004850       INTO TABLE t_t005t
    004860       FROM t005t
    004870       FOR ALL ENTRIES IN t_lfa1_land
    004880       WHERE spras = sy-langu AND
    004890             land1 = t_lfa1_land-land1.
    004900       REFRESH t_lfa1_land.
    004910       SORT t_t005t BY land1.
    004920     ELSE.
    004930       MESSAGE i014 WITH 'No vendor data fetched'(001).
    004940     ENDIF.
    004950   ENDFORM.                    " get_country_names
    004960   &----
    004970   *&      Form  get_clrd_ven_data
    004980   &----
    004990   *       Cleared vendor data
    005000   ----
    005010   FORM get_clrd_ven_data .
    005020
    >     SELECT bukrs
    005040            lifnr
    005050            augdt
    005060            augbl
    005070            zuonr
    005080            gjahr
    005090            belnr
    005100            buzei
    005110            waers
    005120            dmbtr
    005130            wrbtr
    005140            zlsch
    005150            shkzg
    005160            blart
    005170            gsber
    005180            sgtxt
    005190     INTO TABLE t_bsak_tmp
    005200     FROM bsak CLIENT SPECIFIED
    005210   * the order of the fields are as in the secondary Index.
    005220     WHERE mandt = sy-mandt AND
    Contents of system fields
    SY field contents..................... SY field contents.....................
    SY-SUBRC 0                             SY-INDEX 0
    SY-TABIX 1                             SY-DBCNT 59
    SY-FDPOS 0                             SY-LSIND 0
    SY-PAGNO 0                             SY-LINNO 1
    SY-COLNO 1                             SY-PFKEY
    SY-UCOMM
    SY-TITLE Vendor Payment  Details for IRD
    SY-MSGTY I                             SY-MSGID SF
    SY-MSGNO 616                           SY-MSGV1 /DS1/FI_CR_REPT_PGSR802_VEND_P
    SY-MSGV2 RE                            SY-MSGV3 EN
    SY-MSGV4
    Active calls / events
    No.... Type........ Name..........................
           Program
           Include                                  Line
           Class
         2 FORM         GET_CLRD_VEN_DATA
           /DS1/FI_CR_REPT_PGSR802_VEND_P
           /DS1/FI_CR_REPT_PGSR802_VEND_P             503
         1 EVENT        START-OF-SELECTION
           /DS1/FI_CR_REPT_PGSR802_VEND_P
           /DS1/FI_CR_REPT_PGSR802_VEND_P             135

    Hi Balaji,
    Here is what the dump said and my answers are right below them.
    <i>Possible errors:</i>
    o The maximum size of an SQL statement has been exceeded.</i>
    This may not be the reason in your case. This usually happens when you use the option FOR ALL ENTRIES
    <i>o The statement contains too many input variables.</i>
    Most likely this is your issue. I think your r_lifnr is filled with all the vendors in your system and filled as single values. In that case you may be exceeding a limit set on the system. Instead of trying to remove this setting, what I would suggest is to do the following.
    Define a select-option for LIFNR on your selection screen. This way users can have the flexibility of specifying certain vendors. If they don't enter anything, it is still ok. Don't fill it with single values.
    Use this select-option in your select statement. After the select statement, do a delete from itab where the vendors are not in your r_lifnr as below.
    DELETE t_bsak_tmp WHERE NOT lifnr IN r_lifnr.
    Also, avoid using client. You don't need that unless you really want to select from a different client other than your logon client. Your select statement is using logon client anyway, so you don't need to specify that.
    <i>o The space needed for the input data exceeds the available memory.</i>
    If the above changes are made and the problem is still there, then this is the next thing to look at.
    Srinivas

  • RunTime error DBIF_RSQL_INVALID_RSQL while updating infotype 0035

    Dear Experts,
    I am delimiting(changing the end date from future date to current date) the HR objects in IT 0035 using FM RH_CUT_INFTY. It is delimiting the records as per required.
    To do this update we have developed a report where we read the Object ID and the PERNR on the selection screen and inside the program we update IT35.
    The program executes in three steps:
    1. Lock HR Object
    2. Update(in synchronous mode) the records for the specified Object ID-PERNR pair using FM RH_CUT_INFTY
    3. Release HR object and go to next HR object and go back to step 1.
    The report is executing good when there are less number of records for an HR object. But, when the number of (PERNR)records for an HR object is more then the report is giving a po-up "Update was terminated" and when I checked the dump for the same in ST22, it gives the following details:
    Runtime Errors : DBIF_RSQL_INVALID_RSQL
    Exception         : CX_SY_OPEN_SQL_DB
    I would be grateful if anyone can please help me resolve this issue.
    Thanks,
    Jiten

    Hi Jiten,
    I don't know how much I can help you on this.
    But I found an FM: RH_CUT_INFTY_GENERIC
    This FM seems to be designed for mess process of CUT INFTY.
    I check the source code, the VTASK is set to 'B' when calling RH_CUT_INFTY in a loop.
        CALL FUNCTION 'RH_CUT_INFTY'
             EXPORTING
                  LOAD               = ' '
                  GDATE              = GDATE
                  HISTO              = HISTO
                  DEL_SUCC           = DEL_SUCC
                  VTASK              = 'B'
                  ORDER_FLG          = ORDER_FLG
                  COMMIT_FLG         = COMMIT_FLG
                  AUTHY              = AUTHY
              PPPAR_IMP          =
                  KEEP_LUPD          = KEEP_LUPD
                  WORKF_ACTV         = WORKF_ACTV
             TABLES
                  INNNN              = action_tab
               ILFCODE            =
             EXCEPTIONS
                  ERROR_DURING_CUT   = 1
                  NO_AUTHORIZATION   = 2
                  GDATE_BEFORE_BEGDA = 3
                  CUT_OF_TIMCO_ONE   = 4
                  CORR_EXIT          = 5
                  OTHERS             = 6.
    And when all the objects have been submitted to delimitation, call FM RH_UPDATE_DATABASE at last.
    I think this could be a workaround for your issue.
    Cheers,

  • DBIF_RSQL_INVALID_RSQL when creating a Purchase Order (ME21N)

    Hi,
    The system is generating a short dump DBIF_RSQL_INVALID_RSQL when a user tries to create a purchase order.
    what could be the cause of this? i have analysed the short dump in st22 and looked at sm21 and st11 and they are giving very little detaill.
                                                                                    Error in the module RSQL accessing the database interface.                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLZMM_GET_ACT" had to be terminated because one of    
    the                                                                               
    statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                          
    and make a note of the actions and input that caused the                          
    error.                                                                               
    To resolve the problem, contact your SAP system administrator.                    
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer          
    termination messages, especially those beyond their normal deletion              
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below  
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was  
    neither                                                                  
    caught nor passed along using a RAISING clause, in the procedure          
    "ZMM_GET_ACT_PLN" "(FUNCTION)"                                           
    Since the caller of the procedure could not have expected this exception  
    to occur, the running program was terminated.                            
    The reason for the exception is:                                          
    The SQL statement generated from the SAP Open SQL Statement violates a    
    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 ...                                                                               
    You can usually find details in the system log (SM21) and in the          
    developer trace of the work process (ST11).                               
    If an error occurs the developer trace often informs you about the        
    current restrictions.                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure             
    "ZMM_GET_ACT_PLN"                                                              
    "(FUNCTION)", or declared in the procedure's RAISING clause.                    
    To prevent the exception, note the following:                                   
    The SAP Open SQL statement must be divided into several smaller units.          
    If the problem occurred due to the use of an excessively large table            
    in an IN itab construct, you can use the addition FOR ALL ENTRIES               
    instead.                                                                        
    When you use this addition, the statement is split into smaller units           
    according to the restrictions of the database system used.                                                                               
    You may able to find an interim solution to the problem                         
    in the SAP note system. If you have access to the note system yourself,         
    use the following search criteria:                                                                               
    "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC                                     
    "SAPLZMM_GET_ACT" or "LZMM_GET_ACTU01"                                          
    "ZMM_GET_ACT_PLN"                                                               

    Hi,
    Wherever you have used SQL statement please do check all the fields here as some of the fields are not in correct order as they are required per the actual table in dictonary, to just verify that you can use addition of "INTO CORRESPONDING FIELDS OF INTERNALTABLE" in your SQL statement as this will not require the fields to be in order but this may cause performance issue.
    Thanks and Regards
    Sudharshan

  • Exception CX_SY_OPEN_SQL_DB while executing a BSP page

    Hi,
    I have created a BSP app'n with 2 pages. In one page i am using a class interface within that one method. In that method im firing a select query.
    If i run the BSP page, im getting the CX_SY_OPEN_SQL_DB exception with DBIF_RSQL_INVALID_RSQL error.
    I am not able to understand this issue. If any one had any idea, please reply me. I am very thankful if you do this.
    Thanks,
    Kumar

    Nitin,
    First , check if the Query is correct , then check the backed DB for any additional details , and also you might get more help if you post the same question in the BSP forums.
    How are you calling the query , do you have any internal tables or resultset where you store the values ?
    Arun

  • Runtime error DBIF_RSQL_INVALID_RSQL on BW Idoc archiving.

    Hi Experts,
    I am facing one issue while performing IDOC archiving in BW system.
    While running write program with RSEXARCA, I am getting ABAP dump DBIF_RSQL_INVALID_RSQL
    with a exception CX_SY_OPEN_SQL_DB. 'Error in RSQL module of database interface' as a short text.
    Please let me know what could be the problem.
    Regards,
    Mohan.

    Hi,
    You can try to implement the latest DBSL patch in order to solve this. You can implement the latest Kernel and DBSL patches from the links below.
    -> http://service.sap.com/patches
    -> Support Packages and Patches - Entry by Application Group
      -> Additional Components
       -> SAP Kernel
    Regards,
    Rafael

  • Runtime Error # DBIF_RSQL_INVALID_RSQL for large size BOMs

    Hi All,
    I am facing problem running a custom report for Routing summary. When Executing the report gives the above runtime error.
    ShrtText: Error in RSQL module of database interface. 
    Error analysis :
    An exception occurred. This exception is dealt with in more detail below                      
        . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was neither caught nor passed along using a RAISING clause, in the procedure                              
         "CP_SC_MTK_LOAD_COMPLEX_BY_TSK" "(FUNCTION)"                                                 
    Since the caller of the procedure could not have expected this 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.
    How to correct the error                                                                               
    The SAP Open SQL statement must be divided into several smaller units.                        
        If the problem occurred due to the use of an excessively large in an IN itab construct, you can use the addition FOR ALL ENTRIES                             
        instead.  When you use this addition, the statement is split into smaller according to the restrictions of the database system used.                                                                               
    You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself,                       
        use the following search criteria:                                                                               
    "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC                                                   
        "SAPLCPSC" or "LCPSCU03"                                                                      
        "CP_SC_MTK_LOAD_COMPLEX_BY_TSK"   
    This report uses SAP standard Function module "CP_SC_MTK_LOAD_COMPLEX_BY_TSK" in the select statement.
    When Analysed, We found that since the BOM size for routing is large(More than 2000 components), this dump is coming. for rest of the routings, the report works fine.
    I could not found any SAP note relevant for this.
    This is definitely related to large BOM size, if anybody of you came across such problem and how to correct it now.

    Hi,
    We did solve this problem. This problem usually comes when there is very large records in internal table (More than 2000 Approx).
    We need to split that select statement and make multiple statements so that the memory overflow doesn't happen. refer SAP note: 13607.
    We modified the coding as follows by splitting the SELECT statementu2026
    SELECT DISTINCT MANDT PLNTY PLNNR PLNAL MATNR WERKS VBELN POSNR
            INTO CORRESPONDING FIELDS OF TABLE E_MTK_IDENT
            FROM MAPL FOR ALL ENTRIES IN I_TSK_IDENT
            WHERE PLNTY =  I_TSK_IDENT-PLNTY    AND
                  PLNNR =  I_TSK_IDENT-PLNNR    AND
                  PLNAL =  I_TSK_IDENT-PLNAL    AND
                  MATNR IN I_CPSC_MTK_SEL-MATNR AND
                  WERKS IN I_CPSC_MTK_SEL-WERKS AND
                  VBELN IN I_CPSC_MTK_SEL-VBELN AND
                  POSNR IN I_CPSC_MTK_SEL-POSNR AND
                 (FREE_WHERE-WHERE_TAB).
      SELECT MANDT PLNTY PLNNR PLNAL MATNR WERKS VBELN POSNR
             INTO CORRESPONDING FIELDS OF TABLE E_MTK_IDENT
             FROM MAPL FOR ALL ENTRIES IN I_TSK_IDENT
             WHERE PLNTY =  I_TSK_IDENT-PLNTY    AND
                   PLNNR =  I_TSK_IDENT-PLNNR    AND
                   PLNAL =  I_TSK_IDENT-PLNAL    AND
                  (FREE_WHERE-WHERE_TAB).
      Delete E_MTK_IDENT where matnr NOT in I_CPSC_MTK_SEL-MATNR.
      Delete E_MTK_IDENT where werks NOT in I_CPSC_MTK_SEL-WERKS.
      Delete E_MTK_IDENT where VBELN NOT in I_CPSC_MTK_SEL-VBELN.
      Delete E_MTK_IDENT where POSNR NOT in I_CPSC_MTK_SEL-POSNR.
    Hope this helps you.
    Regards, Madhu

  • Runtime Error DBIF_RSQL_INVALID_RSQL

    Hello Gurus,
    One of the ABAP programs failed in the process chains with a short dump.
    The details are as follows:
    Could you help me resolve this?
    Thanks and best wishes,
    raj
    Runtime Error          DBIF_RSQL_INVALID_RSQL
    Exception              CX_SY_OPEN_SQL_DB
           Occurred on     02.07.2008 at   20:55:20
    What happened?
    Error in ABAP application program.
    The current ABAP program "Z_GENERATE_PLAN" had to be terminated
    because one of the
    statements could not be executed.
    This is probably due to an error in the ABAP program.
    What can you do?
    Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
    is especially useful if you want to keep a particular message.
    Error analysis
    An exception occurred. This exception will be dealt with in more detail
    below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not
    caught, which
    led to a runtime error. The reason for this exception is:
    The SQL statement generated from the SAP Open SQL Statement violates a
    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 ...
    You can usually find details in the system log (SM21) and in the
    developer trace of the work process (ST11).
    If an error occurs the developer trace often informs you about the
    current restrictions.
    How to correct the error
    The SAP Open SQL statement must be divided into several smaller units.
    If the problem occurred due to the use of an excessively large table
    in an IN itab construct, you can use the addition FOR ALL ENTRIES
    instead.
    When you use this addition, the statement is split into smaller units
    according to the restrictions of the database system used.
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_INVALID_RSQL" CX_SY_OPEN_SQL_DBC
    "ZGENERATE_PLAN" or "Z_GENERATE_PLAN"
    "START-OF-SELECTION"
    Thanks and best wishes,
    raj

    Tried this solution:
    The current size of one of the input datasets was breaking the maximum length of the SQL statement (which is generated dynamically).  Adjust edthe program to handle situations when the input is too large.
    Will update you.
    Thanks,
    Raj

  • Runtime error "DBIF_RSQL_INVALID_RSQL" during unicode preconversion SPUMG

    Hi experts,
    I was performing the unicode preconversion with spumg on ECC 5.0. The system environment is HP-UX 11.31 and Oracle 10g.
    During  the scan lever 2: tables without language info, there's always an error when scan table "VBSEGK", meanwhile the runtime error "DBIF_RSQL_INVALID_RSQL" raised in ST22. Below is some information regarding to this error.
    Runtime error:
    Runtime Error          DBIF_RSQL_INVALID_RSQL
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          30.05.2011 05:44:42
    Error in ABAP application program.
    The current ABAP program "UMG_SCANNER" had to be terminated because one of the statements could not be executed.
    This is probably due to an error in the ABAP program.
    An exception occurred. This exception is dealt with in more detail below
    .The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was neither caught nor passed along using a RAISING clause, in the procedure "FETCH_NEXT"
    "(METHOD)".
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    The data read during a SELECT access could not be inserted into the
    target field.
    Either conversion is not supported for the target field's type or the
    target field is too short to accept the value or the data are not in a
    form that the target field can accept.
    Thanks and Regards,
    Kevin Yu

    Hi Kevin,
    this is probably caused by one or more incorrect / corrupt  entries in table VBSEGK.
    UMG_SCANNER reads the content of this table and is unable to do so for a specific  entry.
    Now it is necessary to find out, which entry causes this issue ...
    Maybe your colleagues from the according application (FI-GL-GL-X) can help you ?
    Best regards,
    Nils Buerckel

Maybe you are looking for

  • RE:Some trasactions are rejected in XI system

    Hi  Guys, I found a bug in the process between XI and BW. Some rejected records occur when a transaction has a Voided line item. I think I've found what may be a large part of what's contributing to these rejected records. It looks like if a transact

  • How do I add currency to duration in Numbers '09

    Hi there! I'm in way over my head when it comes to using formulas (other than the quick calculations) and I could do with some of your expertise if possible? I'm a freelance graphic designer and I'm trying to produce a quoting system to calculate cos

  • Mail sends mail prematurely

    Since the last iPhone OS update (Oct 09) my 3G sometimes acts as if I've hit SEND in the middle of typing an email message. The SEND key is way up on top right when keyboard is in use but it must come from accidentally touching return or backspace ke

  • Where is XML generated from PO Output for Communication

    I looked in $COMMON_TOP/admin/out and opened orequestid.out file, but its not xml can someone tell me where does it get stored ? thanks

  • [DW-8]No me funciona la funcion captcha

    Hola, estoy probando poniendo captcha en mi web, pero estoy haciendo pruebas y no me funciona, lo que hago es el en form, es llamar a una funcion Comprobar que tiene en esa misma pagina, pero no me funciona, os pongo el codigo asi se ve mejor <body>