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

Similar Messages

  • 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

    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 - Too many OPEN CURSOR

    When I try to train a Decision Tree Model via an APD process in RSANWB, I get a runtime error when my model is configured with too many parameter fields or too many leaves (with 2 leaves it works, with more it fails).
    By searching SAP Notes I see that there are many references to this kind of runtime errors. But no note on occurences of it in RSANWB / RSDMWB .
    Any information on this anyone?
    Claudio Ciardelli
    Runtime Errors         DBIF_RSQL_INVALID_RSQL
    Date and Time          29.07.2005 16:19:21
    |ShrtText                                                                                |
    |    Error in RSQL module of database interface.                                                   |
    |What happened?                                                                                |
    |    Error in ABAP application program.                                                            |
    |                                                                                |
    |    The current ABAP program "SAPLRS_DME_DECISION_TREE_PRED" had to be terminated                 |
    |     because one of the                                                                           |
    |    statements could not be executed.                                                             |
    |                                                                                |
    |    This is probably due to an error in the ABAP program.                                         |
    |                                                                                |
    |Error analysis                                                                                |
    |    The system attempted to open a cursor for a SELECT or OPEN CURSOR                             |
    |    statement but all 16 cursors were already in use.                                             |
    |    The statement that failed accesses table "/BIC/0CDT000030 ".                                  |
    |    The erroneous statement accesses table "/BIC/0CDT000030 ".                                    |
    |Trigger Location of Runtime Error                                                                 |
    |    Program                                 SAPLRS_DME_DECISION_TREE_PRED                         |
    |    Include                                 LRS_DME_DECISION_TREE_PREDU06                         |
    |    Row                                     103                                                   |
    |    Module type                             (FUNCTION)                                            |
    |    Module Name                             RS_DME_DTP_EVALUATE                                   |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                |
    |   73|* Prepare for Data evaluation                                                               |
    |   74|  CATCH SYSTEM-EXCEPTIONS OTHERS = 15.                                                      |
    |   75|    CREATE DATA ref TYPE (i_enum_dbtab).                                                    |
    |   76|    ASSIGN ref->* TO <fs_wkarea>.                                                           |
    |   77|    ASSIGN COMPONENT gv_class_dbposit OF STRUCTURE                                          |
    |   78|                      <fs_wkarea> TO <fs_class>.                                            |
    |   79|    CREATE DATA ref TYPE TABLE OF (i_enum_dbtab).                                           |
    |   80|    ASSIGN ref->* TO <ft_data>.                                                             |
    |   81|                                                                                |
    |   82|  ENDCATCH.                                                                                |
    |   83|  IF sy-subrc = 15.                                                                         |
    |   84|*   Error on Assignment.                                                                    |
    |   85|    CALL FUNCTION 'RS_DME_COM_ADDMSG_NOLOG'                                                 |
    |   86|      EXPORTING                                                                             |
    |   87|        i_type    = 'E'                                                                     |
    |   88|        i_msgno   = 301                                                                     |
    |   89|        i_msgv1   = 'EVALUATION_PHASE'                                                      |
    |   90|      IMPORTING                                                                             |
    |   91|        es_return = ls_return.                                                              |
    |   92|    APPEND ls_return TO e_t_return.                                                         |
    |   93|    EXIT.                                                                                |
    |   94|  ENDIF.                                                                                |
    |   95|                                                                                |
    |   96|* For the un-trained Rec-Ids, evaluate.....                                                 |
    |   97|  REFRESH lt_recinp.                                                                        |
    |   98|  APPEND LINES OF i_t_records TO lt_recinp.                                                 |
    |   99|  SORT lt_recinp .                                                                          |
    |  100|* Open Cursor..                                                                             |
    |  101|  DATA: l_curs TYPE cursor.                                                                 |
    |  102|  DATA: l_psize TYPE i VALUE 10000.                                                         |
    |>>>>>|  OPEN CURSOR WITH HOLD l_curs FOR                                                          |
    |  104|   SELECT * FROM (i_enum_dbtab)                                                             |
    |  105|     WHERE rsdmdt_recid NOT IN                                                              |
    |  106|        ( SELECT rsdmdt_recid FROM                                                          |
    |  107|             (i_learn_tab) ).                                                               |
    |  108|                                                                                |
    |  109|*  Start Fetch...                                                                           |
    |  110|  DO.                                                                                |
    |  111|    FETCH NEXT CURSOR l_curs                                                                |
    |  112|      INTO CORRESPONDING FIELDS OF TABLE <ft_data>                                          |
    |  113|      PACKAGE SIZE l_psize.                                                                 |
    |  114|    IF sy-subrc NE space.                                                                   |
    |  115|      EXIT.                                                                                |
    |  116|    ENDIF.                                                                                |
    |  117|                                                                                |
    |  118|*     Process records...                                                                    |
    |  119|    LOOP AT <ft_data> ASSIGNING <fs_wkarea>.                                                |
    |  120|                                                                                |
    |  121|*     Call Prediction Function.                                                             |
    |  122|      CALL FUNCTION 'RS_DME_DTP_PREDICT_STRUCTURE'                                          |

    Hi Claudio,
    well the message is very clear and I think in your case you need to split your model into a few somehow equal models, each not having more than 2 leaves.
    Another option might be to do more things serially instead of parallel.
    Hope it helps
    regards
    Siggi

  • 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,

  • 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

  • Runtime Error DBIF_RSQL_INVALID_RSQL on dataload to PSA

    Hi,
    Apologies for the long problem statement.
    We need to extract data from a non- SAP SQL system to our SAP Netweaver 7.01 (EhP1 SP5) BI system. We have established a UD Connection and connected to tables in the SQL system.
    After a few dataloads and data validity, some fields were changed in the source tables in the SQL system.
    Now, when we try to extract data into our PSA by triggering InfoPackage, it gives a Runtime Error with following messages:
    *Runtime Errors         DBIF_RSQL_INVALID_RSQL*
    *Exception              CX_SY_OPEN_SQL_DB*
    *Error in module RSQL of the database interface.*
    *An exception occurred that is explained in detail below.*
    *The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caugh*
    *in*
    *procedure "INSERT_ODS" "(FORM)", nor was it propagated by a RAISING clause.*
    *Since the caller of the procedure could not have anticipated that the*
    *exception would occur, the current program is terminated.*
    *The reason for the exception is:*
    *In a SELECT access, the read file could not be placed in the target*
    *field provided.*
    *Either the conversion is not supported for the type of the target field,*
    *the target field is too small to include the value, or the data does not*
    *have the format required for the target field.*
    We tried creating another datasource on the same table and we could extract data successfully. There a quite a few more DS that have the same issue. Is there another way to resolve this issue while retaining current DS.
    Also, for another table which has more number of rec (arnd 20K), the extraction keeps running even after creating new datasource.
    Please help.
    -Abhishek.
    Edited by: Abhishek Rajan on Sep 28, 2010 8:05 PM

    Hi Rajan,
    Please find this thread.
    I guess it may be useful. When datasource structrue changes , there will inconsistency in database and will not allow us to delete or do data load.
    This has resolved my problem.
    PSA Not Deleting, error : DDL time(___1):.....0 milliseconds
    Thanks
    Vamsi

  • 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

  • 1439467 SUIM| RSUSR70: Runtime error DBIF_RSQL_INVALID_RSQL is not availabl

    Currently SAP Note 1439467 SUIM| RSUSR70: Runtime error DBIF_RSQL_INVALID_RSQL is not available. When searching the note in http://service.sap.com/notes error message The requested SAP Note is either in reworking or is released internally only is displayed. It was available of couple of days ago.
    Does anyone know when it will be available again?
    Thanks for help,
    Jarmo Tuominen

    Hi
    Maybe never open the note, The note is only internal, It's that only SAP can see the note. Is likely that the note is being updated, in this case only wait.
    if you have any error with your system please paste logs for help or open OSS Ticket
    Hi I found this SAP  Note 1171653 - SUIM| RSUSR070 runtime error DBIF_RSQL_INVALID_RSQL
    Regards
    William Neira
    Edited by: William Leonardo Neira on Mar 4, 2011 5:52 PM

  • Effective Cropping in Aperture for large size prints

    hi all,
    any advice (in simple terms as I am new to digital slr photography - just assume I know very little) on the most effective way to crop photographs for large size prints. I just bought a Nikon D80 dslr - I have a photo of my daughter I really like and would to crop and then enlarge for a nice framed photograph. The original print is 3872 x 2592 and in cropped form it is 915 x 807 which appears quite small to me. Is there any chance of a decent large print. I used the aperture cropping tool - is there another way which preserves more resolution (not sure am using right word here) - or put differently what is the best way of getting a good cropped photo from this print. Apologies if that was a bit all over the place.

    mdockrell wrote:
    my main question are there methods of cropping pictures that enable one to keep as much detail as possible
    Usually, when you crop you simply discard those pixels outside of the area you wish to keep so nothing is lost. It looks worse as you enlarge it on the screen but the retained area should be exactly the same as it was before cropping - just smaller. There are ways to uprez a photo that make it look better when enlarged - but detail cannot be invented! In photoshop you can try to increase the resolution in 10% steps until the image is a size suitable for a larger print. I've seen this used to good advantage but sometimes it simply looks horrible. Give it a try, you can't lose anything.

  • Dump : Runtime Errors         DBIF_RSQL_INVALID_RSQL

    Hi Experts,
    I got a dump at the select statement in the production during the excution.The Details of the program are :
    DATA : BEGIN OF it_ekko OCCURS 0.
            INCLUDE STRUCTURE ekko.
    DATA : END OF it_ekko.
    START-OF-SELECTION.
    SELECT * FROM ekko            
               INTO TABLE it_ekko
               WHERE ebeln IN p_ebeln
                 AND aedat IN p_aedat 
                 AND bsart IN p_bsart 
                 AND lifnr IN p_lifnr.
    In ST22, the description of dump details is as follows.
    <b><u>What happened?</u></b>
    Error in ABAP application program.
    The current ABAP program "ZMMRP126_1" had to be terminated because one of the statements could not be executed.
    This is probably due to an error in the ABAP program.
    <b><u>Error analysis</u></b>
    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.                                                  
    <b><u>Source Code Extract</u></b>
    001830                                                                          
    >     SELECT * FROM ekko                   "read through purchase orders   
    001850              INTO TABLE it_ekko                                          
    001860              WHERE ebeln IN p_ebeln      "for order number               
    001870                AND aedat IN p_aedat      "created date                   
    001880                AND bsart IN p_bsart     "document type                   
    001890                AND lifnr IN p_lifnr.                                     
    001900                                                                          
    001910     LOOP AT it_ekko INTO ekko.                                           
    001920       PERFORM process_items.             "read, check and save line items
    001930     ENDLOOP.                                                             
    <b><u>Contents of system fields</u></b>
    SY field contents..................... SY field contents.....................                                                                               
    SY-SUBRC 0                             SY-INDEX 0                            
    SY-TABIX 1                             <b>SY-DBCNT 69682</b>                        
    SY-FDPOS 0                             SY-LSIND 0                            
    SY-PAGNO 0                             SY-LINNO 1                            
    SY-COLNO 1                             SY-PFKEY                              
    SY-UCOMM                               SY-TITLE Purchase Order Receipt Status
    SY-MSGTY I                             SY-MSGID SF                           
    SY-MSGNO 616                           SY-MSGV1 5000098347                   
    SY-MSGV2                               SY-MSGV3                              
    SY-MSGV4                                                                     
    Kindly help me to solve out this issue.
    Thanks & Regards,
    Krishna Kishore .K

    hi,
    I think you declared p_ebeln as parameter and used in where condition with IN operator.
    Could you change with EQ operator.
    Or If p_ebeln is select-oprions means check you are giving high range in the selection screen for the input values.
    try to check by giving 1 purchase order i.e p_ebeln = 'XXXX' only.
    dont give range.
    If output is big range means program goes to dump.
    are you trying to modify EKKO table in the program?
    Please reward if its useful.
    Thanks
    Sivaparvathi
    Or

  • Runtime error 1114 for visual c++/ win 7 professional

    After a restore in my pc, during the staring of windows I took a message 'run time error for visual C++' and just after that
    'Runtime error
    Program:C:\program files\iTunesHelpex.exe
    R6034
    An application has made an attempt to load the run time library incorrectrly.'
    I tried to open the iTunes but it seemed not working.
    I uninstalled and tried to reinstall iTunes.
    During the installation I took a message 'service "Apple Mobile Device" failed to start. Verify tat you have sufficed privileges to start system services.'
    I continued giving 'ignore' but the result was not that I wished.
    I applied to Microsoft and they consulted me to apply to you.
    Could you please help me to solve the problem?
    Thanks in advance
    vasps
    ([email protected])

    See Troubleshooting issues with iTunes for Windows updates.
    tt2

  • Runtime error LOAD_PROGRAM_NOT_FOUND for ARE document.

    Hi All,
    when I am creating or posting ARE document thru tcode J1IA101 & J1IA301 ,I am clicking on Printing check box & when I am going to save it .It is giving me error printing parameter is not set &
    after pressing enter it is giving runtime error, which is as follows:
    Runtime Errors         LOAD_PROGRAM_NOT_FOUND
    Exception              CX_SY_PROGRAM_NOT_FOUND
    What happened?
        There are several possibilities:
        Error in the ABAP Application Program
        The current ABAP program "SAPLJ1IEX" had to be terminated because it has
        come across a statement that unfortunately cannot be executed.
        or
        Error in the SAP kernel.
        The current ABAP "SAPLJ1IEX" program had to be terminated because the
        ABAP processor detected an internal system error.
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
         caught in
        procedure "J_1IEX_PRINT_ARE" "(FUNCTION)", nor was it propagated by a RAISIN
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        On account of a branch in the program
        (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
        or a transaction call, another ABAP/4 program
        is to be loaded, namely " ".
        However, program " " does not exist in the library.
        Possible reasons:
        a) Wrong program name specified in an external PERFORM or
           SUBMIT or, when defining a new transaction, a new
           dialog module or a new function module.
        b) Transport error
    Thanks,
    C Singh,

    hi all,
    please change the access sequence from J1ID to J1IB and include program for printing ARE-3 in program 2 of access sequence J1IB.
    regards,
    C Singh.

  • Runtime error -  question for experts

    hello  experts,
    I was trying to debug a program for unicode compatibility, and when I finally thought I had finished it.
    This runtime error shows up
    "Error analysis                                                                                |
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_READ_SRC_LINE_TOO_LONG', was
    not caught in
    procedure "K_KKB_FIELDCAT_MERGE" "(FUNCTION)", nor was it propagated by a
    RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    There was an attempt to read program "ZPM04_UPDATE_INFOREC_FROM_PO" from the
    database.
    The READ REPORT statement allows you to copy a program text into an
    internal table. The occupied line length in the program text must not
    exceed the width of the internal table.
    The internal table "\FUNCTION=K_KKB_FIELDCAT_MERGE\DATA=L_ABAP_SOURCE[]" is 72
    characters wide. The program line is
    |    78 characters wide."
    because the error occured in standard SAP programs, I am at loss..
    Please give your suggestions.
    Goldie.

    You need to Change the setting in the program ZPM04_UPDATE_INFOREC_FROM_PO, not in the program SAPLSBKH.
    SAPLSBKH read the Report ZPM04_UPDATE_INFOREC_FROM_PO and it gets error because some lines in the ZPM04_UPDATE_INFOREC_FROM_PO are longer than 72 characters.
    As suggested by other SDN members you have to follow this steps:
    Go to SE38.
    Enter ZPM04_UPDATE_INFOREC_FROM_PO and change.
    Utilities > Setting
    In the Editor Tab, set the checkbox "Downword Compatilbe line Length (72)". You can find out this checkbox in the last section of the Editor tab.
    Press Enter.
    In the Pop-Up, Say "YES" for the line breaks.
    Regards,
    Naimesh Patel

  • Getting runtime Error 'UC_OBJECTS_NOT_CHARLIKE'  for ALV grid

    Hi,
    When I call method SET_TABLE_FOR_FIRST_DISPLAY of ALV I get runtime error 'UC_OBJECTS_NOT_CHARLIKE'.
    Actually i have set in the fieldcatalog the field 'CHK' of internal table as checkbox.
    wa_fcat-fieldname = 'CHK' .
    wa_fcat-coltext = 'Clear' .
    wa_fcat-seltext = 'Clear' .
    wa_fcat-checkbox = 'X' .
    wa_fcat-edit = 'X' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    Field CHK is of type c.
    when i dont set the field as checkbox, I stop getting the error.
    Please find a solution.
    regards,
    auro

    Relevant parts of code are:
    Data Declaration:
    types:  begin of tt_revenue_det,
           chk type c,
           budat like zefit0006-zefibudat,
           racct_txt like skat-txt50,
           amount like zefit0006-zefihsl,
           pbar_txt like tgsbt-gtext,
           sgtxt like zefit0006-zefisgtxt,
           costcentertxt like cskt-ktext,
           bar_txt like skat-txt50,
           doctype like zefit0006-zefiblart,
           ch_flag type c,
           end of tt_revenue_det,
    data:    gt_revenue_det type table of tt_revenue_det.
    FIELD CATALOG
    *&      Form  set_fieldcatalog_rev_det
          text
         -->P_LT_FIELDCATALOG  text
    form set_fieldcatalog_rev_det  using    p_lt_fieldcatalog type lvc_t_fcat.
    data:wa_fcat type lvc_s_fcat.
    wa_fcat-fieldname = 'P_GT_REVENUE_DET-CHK' .
    wa_fcat-coltext = 'Clear' .
    wa_fcat-seltext = 'Clear' .
    wa_fcat-checkbox = 'X' .
    wa_fcat-edit = 'X' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'BUDAT' .
    wa_fcat-coltext = 'Posting Date' .
    wa_fcat-seltext = 'Posting Date' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'RACCT_TXT' .
    wa_fcat-coltext = 'Account Item Text' .
    wa_fcat-seltext = 'Account Item Text' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'AMOUNT' .
    wa_fcat-coltext = 'Amount' .
    wa_fcat-seltext = 'Amount' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'PBAR_TXT' .
    wa_fcat-coltext = 'Partner Business Area' .
    wa_fcat-seltext = 'Partner Business Area' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'SGTXT' .
    wa_fcat-coltext = 'Item Text' .
    wa_fcat-seltext = 'Item Text' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'COSTCENTERTXT' .
    wa_fcat-coltext = 'Cost Center' .
    wa_fcat-seltext = 'Cost Center' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'BAR_TXT' .
    wa_fcat-coltext = 'Business Area' .
    wa_fcat-seltext = 'Business Area' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'DOCTYPE' .
    wa_fcat-coltext = 'Type' .
    wa_fcat-seltext = 'Type' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    wa_fcat-fieldname = 'CH_FLAG' .
    wa_fcat-coltext = 'Split' .
    wa_fcat-seltext = 'Split' .
    APPEND wa_fcat to p_lt_fieldcatalog .
    endform.                    " set_fieldcatalog_rev_det
    CREATE ALV
    *&      Form  create_alv_revenue_det
          text
         -->P_GT_REVENUE_DET  text
    form create_alv_revenue_det  using    p_gt_revenue_det.
    ALV related data declaration
    DATA: lf_layout TYPE lvc_s_layo,  "alv layout
          lt_fieldcatalog type table of lvc_s_fcat, "field catalog internal table
          wa_fieldcatalog type lvc_s_fcat. "work area for field catalog
    create alv only if container is initial
    IF G_CUSTOM_CONTAINER_REV_DET IS INITIAL.
    lf_layout-no_toolbar = 'X'. " no toolbar
    lf_layout-sel_mode = 'B'.
    populate field catalog
    perform set_fieldcatalog_rev_det using lt_fieldcatalog.
    create instance of container class
        CREATE OBJECT G_CUSTOM_CONTAINER_REV_DET
               EXPORTING CONTAINER_NAME = G_CONTAINER_REV2.
    create instance of alv grid class
        CREATE OBJECT GR_ALVGRID_REV_DET
               EXPORTING I_PARENT = G_CUSTOM_CONTAINER_REV_DET.
    call method to display table in alv grid by passing layout and fieldcatalog
        CALL METHOD GR_ALVGRID_REV_DET->SET_TABLE_FOR_FIRST_DISPLAY
             EXPORTING
             is_layout = lf_layout
             CHANGING
             IT_OUTTAB        = p_gt_revenue_det
             IT_FIELDCATALOG  = lt_fieldcatalog.
      ENDIF.
    endform.                    " create_alv_revenue_det

Maybe you are looking for

  • Terminal server does not have any installed licenses

    Good morning! Faced with a some trouble while configuring Terminal Server (Windows Server 2012 based). I selected licensing mode "Per User" and now I see this message: "The Remote Desktop Session Host server is in Per User licensing mode and No Redir

  • How to access my library from another country

    My kids smashed my computer and my ipod.  I have a huge itunes library but haven't bought anything new since they did this in 2011. I am visiting a friend in the UK. I have bought an ipod here and want my stuff back on it. I can access my account but

  • How to automate the loading of Correspondence attachment and templates

    Under the "*Administration - Document*" screen, in our application ( version 8.0.0.3 Public Sector ) , we have 4 tabs / views , they are "*Correspondence Attachments*", "*Case Attachments*", "*Correspondence Templates*" and "*Literature*". We are goi

  • Hide Repeated Key Valuse is not useful in Broadcast Query

    Hi, I have a problem about the setting "Hide repeated key values" is not useful when broadcasting queries by format XML(MS Excel). Our server support package is SP19. Does anyone has the similar problem? Help. Thanks, Johnson

  • Standby db ORA-10567:

    Hi, We have data guard setup in 11.2 on aix.We got the following errors in standby db. Media Recovery Log +P10_ARCHGROUP01/P10/arch/arch_1_1763_815128087.arc Media Recovery Log +P10_ARCHGROUP01/P10/arch/arch_1_1764_815128087.arc Mon Jun 03 13:10:49 2