DBIF_RSQL_INVALID_CURSOR , CX_SY_OPEN_SQL_DB

this above error is coming while processing select - endselect statement in ECC 6.0

Hi,
If you are debugging then
select
endselect
if sy-subrc eq 0. " <<< put the break-point here. if not
please paste the code in between select and endselect

Similar Messages

  • ABAP dump in ECC 6.0 - Need OSS notes

    ABAP dump is coming when retriving data between select-endselect.
    Runtime Errors         DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    The problem cannot be resolved without correcting the application
    program.
    The statements MESSAGE, COMMIT WORK, ROLLBACK WORK, CALL SCREEN,
    BREAK-POINT, WAIT, CALL FUNCTION ... DESTINATION, CALL FUNCTION ...
    STARTING NEW TASK, RECEIVE RESULTS, CALL SELECTION-SCREEN, CALL
    DIALOG, CALL TRANSACTION cannot be used within a database
    loop.
    You can collect the data needed for these statements together in an
    internal table and process them
    in a loop.
    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_CURSOR" "CX_SY_OPEN_SQL_DB"
    Can you please give the OSS notes no. if anything is available.

    Hi Sreedevi..
    In the dump report, the piece of code where the dump occured will be shown
    something with >>>>>> sign in the line...
    Please copy and paste this peice of code..
    Thanks and Best Regards,
    Vikas Bittera.
    **Reward if useful**

  • Convert SAPSCRIPT forms to PDF

    We need to do a report that can generate several pdfs from a payment run (SAP-FI), so we need to have one pdf  for each payment in the run (they are in SAPSCRIPT form).
    The program that we use is copy of "J_1AF012" and the we use "SX_OBJECT_CONVERT_OTF_PDF" function to obtain the pdf form, but the changes that we did in the standard were:
    a) in the "OPEN_SAPSCRIPT"
    *&      Form  OPEN_SAPSCRIPT
          text                                                           *
    FORM OPEN_SAPSCRIPT.
      ITCPO-TDIMMED    = '*'.              " kz sofort drucken
      ITCPO-TDDELETE   = '*'.              " kz freigbe nach Druck
      ITCPO-TDLIFETIME = '7'.              " verfalltage
      ITCPO-TDPREVIEW  = 'X'.              " druckansicht
    Setting the options
      w_options-tdcopies = 1 ."Number of copies
      w_options-tdnoprev = c_x."No print preview
      w_options-tdgetotf = c_x."Return of OTF table
      w_options-tddest =   c_locl."Spool: Output device
      CALL FUNCTION 'OPEN_FORM'            " open form for output
           EXPORTING FORM    = S_FORM
                     DIALOG  = 'X'
                     LANGUAGE = 'S'
                   OPTIONS = ITCPO
                     OPTIONS = w_options
                    DEVICE  = 'PRINTER'
                     DEVICE  = c_printer
           IMPORTING
                     RESULT  = W_RES.
    ENDFORM.                               " OPEN_SAPSCRIPT
    b) In the "CLOSE_SAPSCRIPT" :
    FORM CLOSE_SAPSCRIPT.
      C_ORDEN = C_ORDEN + 1.
      shift C_ORDEN left deleting leading space.
      CONCATENATE C_PATH C_NAME1 C_ORDEN C_EXTENSION INTO C_NAME.
      CALL FUNCTION 'CLOSE_FORM'
      IMPORTING
              RESULT = w_res
              TABLES
                    otfdata = i_otf
              EXCEPTIONS
                    unopened = 1
                    bad_pageformat_for_print = 2
                    send_error = 3
                    spool_error = 4
                    codepage = 5
                    OTHERS= 6.
      IF sy-subrc <> 0.
          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                  WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    c) And we added these functions:
    Converting OTF data to single line
      LOOP AT i_otf INTO w_otf.
            CONCATENATE w_otf-tdprintcom w_otf-tdprintpar
                                                  INTO w_pdf.
            APPEND w_pdf TO i_content_txt.
      ENDLOOP.
    Converting to PDF Format
      CALL FUNCTION 'SX_OBJECT_CONVERT_OTF_PDF'
      EXPORTING
                format_src = c_otf
                format_dst = c_pdf
                devtype = c_printer
            CHANGING
                transfer_bin = w_transfer_bin
                content_txt = i_content_txt
                content_bin = i_content_bin
                objhead = i_objhead
                len = v_len_in
            EXCEPTIONS
                err_conv_failed = 1
            OTHERS = 2.
      v_size = v_len_in.
    Downloading the PDF File
      CALL FUNCTION 'GUI_DOWNLOAD'
            EXPORTING
                bin_filesize = v_size
                filename = c_name
                filetype = c_bin
            TABLES
                data_tab = i_content_bin.
    When we run the program the error is a dump with:
    "DBIF_RSQL_INVALID_CURSOR
    CX_SY_OPEN_SQL_DB        "
    and aparenttly is due to the cursor in BKPF table is closed (or missing) in some of those functions.
    We use the "open_form" and "close_form" for each payment document, and we could generate only the first pdf and then the program cancel (to the second pdf) with this mentioned error.
    We are on R/3 4.70, 620, and Informix Database.
    Please, could you kindly help us???
    Best regards,

    Hola Grisel!
    Estoy tratando de armar en pdf las órdenes de pago, pudiste hacerlo? Como lo lograste?
    Gracias de antemano por cualquier info que me puedas brindar.
    Saludos
    Eduardo Puricelli
    Hi Grisel,
    I'm trying to build in pdf payment orders, could you? As you did it?
    Thanks in advance for any info you can give me.
    Greetings
    Eduardo Puricelli

  • CL_GUI_FRONTEND_SERVICES in select loop

    Hi all,
    I have a problem using CL_GUI_FRONTEND_SERVICES=>FILE_EXIST within a select loop. I want to loop through a databasetable with filenames and if the file exists, do some stuff with it. The method works good, but when the loop is executed and the next SELECT is executed I get a short dump:
    DBIF_RSQL_INVALID_CURSOR
    CX_SY_OPEN_SQL_DB
    Invalid interruption of a database selection.
    This is my code:
    SELECT file FROM files  INTO l_file.
                   WHERE EXTID = p_extid AND UNAME = sy-uname.
    CALL METHOD CL_GUI_FRONTEND_SERVICES=>FILE_EXIST
                    EXPORTING
                      FILE                 = l_strfloc
                      RECEIVING
                      RESULT               = l_result.
    ENDSELECT.

    Better select data into table.
    then use
    LOOP AT ITAB.
       CALL GUI_FRONT END SERVICES.
    ENDLOOP.
    OTHER WISE......you cannot interfere the Prsentation (Desktop) Servier Logic with the DATA BASE LOGIC ....SELECT ENDSELECT.
    Vijay

  • DBIF_RSQL_INVALID_CURSOR : Error extracting records in RSA3 for 2LIS_02_ITM

    Hi
    I'm extracting the data in R/3 system using tcode RSA3 for transaction datasource (2LIS_02_ITM). When i extracted the transaction data , it was giving time out error. Then i went into debug mode to find the error. While debugging the code it gave me a DBIF_RSQL_INVALID_CURSOR short dump.
    NOTE : Data extraction is working for all 02 transaction data like 2LIS_02_SCL , 2LIS_02_S012. It s failing for only 2LIS_02_ITM only.
    I have pasted the eror message below for reference. Urgent help required.
    From
    Bobby
    ERROR MESSAGE DUMP for DBIF_RSQL_INVALID_CURSOR
    Runtime Errors         DBIF_RSQL_INVALID_CURSOR
    Except.                CX_SY_OPEN_SQL_DB
    Date and Time          09.04.2008 12:47:09
    Short text
    Invalid interruption of a database selection.
    What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLMCEX" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    Unable to perform database selection fully.
    Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
    in
    procedure "MCEX_BW_LO_API" "(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:
    One of the database selections included a database Commit.
    The selection was then supposed to continue. Before a
    database commit, however, all outstanding database selections
    must be concluded.
    Possible causes in the application program:
    While a read process from a database cursor is taking place
    (within a loop SELECT/LOOP/EXEC SQL or before a FETCH command),
    one of the following statements is used:
    - MESSAGE (apart from MESSAGE S...)
    - COMMIT WORK
    - ROLLBACK WORK
    - BREAK-POINT
    - WAIT
    - CALL FUNCTION ... DESTINATION (synchronous RFC)
    - CALL FUNCTION ... STARTING NEW TASK
    - RECEIVE RESULTS
    - CALL DIALOG
    - CALL SELECTION-SCREEN
    - CALL TRANSACTION
    - CALL SCREEN, or any other statement that results in the display of a
    new screen
    Whenever a program runs in debugging mode, a "COMMIT WORK" can
    possibly be triggered during database selection. This abnormal
    termination can also occur in debugging mode even with a correct
    program.
    A "COMMIT WORK" during debugging may be due to the following reasons:
    1. A program or screen was regenerated during debugging
    and updated in the database.
    2. Each user needs a separate process in debugging mode, but
    the number of available processes is restricted. If this
    limit is exceeded, each debugging step then requires a
    "COMMIT WORK".
    The error occurs in a statement in which the table "MC02M_0ITMSETUP " is
    accessed.
    Missing RAISING Clause in Interface
    Program                                 SAPLMCEX
    Include                                 LMCEXU06
    Row                                     1
    Module type                             (FUNCTION)
    Module Name                             MCEX_BW_LO_API
    Trigger Location of Exception
    Program                                 SAPLMCEX
    Include                                 LMCEXU06
    Row                                     220
    Module type                             (FUNCTION)
    Module Name                             MCEX_BW_LO_API
    Source Code Extract
    Line
    SourceCde
    190
    at end of fieldnm.                   "PI 2000.2 SP_353722
    191
    if not <fs_field> in cond_select_tab.
    192
    cond_select = false.
    193
    refresh cond_select_tab.         "PI 2000.2 SP_353722
    194
    exit.
    195
    endif.
    196
    refresh cond_select_tab.             "PI 2000.2 SP_353722
    197
    endat.                               "PI 2000.2 SP_353722
    198
    endloop.
    199
    if cond_select eq true.
    200
    append &2 to e_t_data.
    201
    add 1 to counter.
    202
    endif.
    203
    endloop.
    204
    if s_maximum_size le counter.
    205
    exit.
    206
    endif.
    207
    else.
    208
    close cursor g_cursor.
    209
    s_flg_no_more_data = true.
    210
    exit.
    211
    endif.
    212
    enddo.
    213
    END-OF-DEFINITION.
    214
    end macro *****
    215
    216
    CASE s_estruc.
    217
              extractstruc   internal table    setup table
    218
    *-- MM-PUR
    219
    sel 'MC02M_0HDR'   mc02m_0hdr_tab    mc02m_0hdrsetup.
    >>>>>
    sel 'MC02M_0ITM'   mc02m_0itm_tab    mc02m_0itmsetup.
    221
    sel 'MC02M_0SCL'   mc02m_0scl_tab    mc02m_0sclsetup.
    222
    sel 'MC02M_0SGR'   mc02m_0sgr_tab    mc02m_0sgrsetup.
    223
    sel 'MC02M_0SCN'   mc02m_0scn_tab    mc02m_0scnsetup.
    224
    sel 'MC02M_0CGR'   mc02m_0cgr_tab    mc02m_0cgrsetup.
    225
    sel 'MC02M_0ACC'   mc02m_0acc_tab    mc02m_0accsetup.
    226
    *-- Application '03' (Inventory Management)
    227
    sel 'MC03BF0'      mc03bf0_tab       mc03bf0setup.
    228
    sel 'MC03BX0'      mc03bx0_tab       mc03bx0setup.
    229
    sel 'MC03UM0'      mc03um0_tab       mc03um0setup.
    230
    *-- Application '04'
    231
    sel 'MC04P_0MAT'   mc04p_0mat_tab    mc04p_0matsetup.
    232
    sel 'MC04P_0ARB'   mc04p_0arb_tab    mc04p_0arbsetup.
    233
    sel 'MC04P_0COM'   mc04p_0com_tab    mc04p_0comsetup.
    234
    sel 'MC04PE0MAT'   mc04pe0mat_tab    mc04pe0matsetup.
    235
    sel 'MC04PE0ARB'   mc04pe0arb_tab    mc04pe0arbsetup.
    236
    sel 'MC04PE0COM'   mc04pe0com_tab    mc04pe0comsetup.
    237
    *-- Application '05' (Quality Management)
    238
    sel 'MC05Q1_0INSP' mc05q1_0insp_tab  mc05q1_inspsetup.
    239
    sel 'MC05Q2_0INSP' mc05q2_0insp_tab  mc05q2_inspsetup.

    Hi Bobby,
    Did you already find a solution for this 'issue'?
    I encounter the same problem. In my humble opinion this has nothing to do with the difference between structures.
    When loading data in normal modus, there is no problem. When loading in debug, there is an error.
    I also tested with other data sources and the same issue occurs there while nothing has changed.
    If someone knows how to solve this issue, please reply.
    Thanks!
    Kind regards,
    Bart

  • Short dump error DBIF_RSQL_INVALID_CURSOR

    Hi
    From Past few days, I am facing a peculiar issue
    I am getting a short dump when the batch run to load to the Infocubes(Full Load). The load runs fine ones I deletes the failed request and load again.
    The short dump and the exception are as below
    Name of runtime error     DBIF_RSQL_INVALID_CURSOR
    Exception     CX_SY_OPEN_SQL_DB
    I have also checked with the basis team and no indication of a failure within SAP (no errors suggesting time-outs, buffers filling, tables filling etc)
    Kindly let me know what could be root cause

    Hi Pavan,
    Are you trying to load the infocube from a DSO.We had the same issue whlle loading a cube from DSO and OSS note 339080 solved our issue.In case you are not able to access the note,find below the cause and solution provided in the note for this issue.
    Cause and prerequisites
    Customizing: the number of parallel processes for sending data was set to 0 in the ROIDOCPRMS table. For this reason, the system uses the process, in which the extraction takes place, for sending the data. A 'commit work' is performed in the sending process which causes an interruption of the running database selection in the extraction process.
    Solution
    Set the parameter 'maximum processes' in the ROIDOCPRMS table (or of the ROIDOCPRMS maintenance view) to a value> 0 for its connection with the BW.
    Regards,
    Bhagyarekha.

  • Regarding runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB

    Hi All,
    I am loading a COPA cube from a DSO.
    There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
    When i checked in SM21 transaction code, i got the following message
    10:41:52 BTC  018 500 AMRUKV                     BY  O Deadlock occurred
    10:41:53 BTC  018 500 AMRUKV                     BY  4 Database error 60 at INS access to table /BIC/FCSDV
    10:41:53 BTC  018 500 AMRUKV                     BY  0 > ORA-00060: deadlock detected while waiting for resource
    10:41:54 BTC  018 500 AMRUKV                     AB  0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
    10:41:58 BTC  018 500 AMRUKV                     AB  1 > Short dump "080818 104154 s0173bel PB100 " generated
    10:41:58 BTC  018 500 AMRUKV                     D0  1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
    In transaction code ST22 i got the following message:
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          18.08.2008 10:41:54
    Short text
         SQL error in the database when accessing a table.
    What happened?
         The database system detected a deadlock and avoided it by rolling back
         your transaction.
    What can you do?
         If possible (and necessary), repeat the last database transaction in the
          hope that locking the object will not result in another deadlock.
         Note which actions and input led to the error.
         For further help in handling the problem, contact your SAP administrator
         You can use the ABAP dump analysis transaction ST22 to view and manage
         termination messages, in particular for long term reference.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
          in  procedure "WRITE_ICFACT" "(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:
         The database system recognized that your last operation on the database
         would have led to a deadlock.
         Therefore, your transaction was rolled back
         to avoid this.
         ORACLE always terminates any transaction that would result in deadlock.
         The other transactions involved in this potential deadlock
         are not affected by the termination.
    How to correct the error
        Database error text........: "ORA-00060: deadlock detected while waiting for
         resource"
        Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
        Please check the entries in the system log (Transaction SM21).
        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_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
        "GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
        "WRITE_ICFACT"
        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
           In the editor, choose "Utilities->More
        Utilities->Upload/Download->Download".
        4. Details about the conditions under which the error occurred or which
        actions and input led to the error.
        The exception must either be prevented, caught within proedure
        "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
        RAISING clause of the procedure.
        To prevent the exception, note the following:
    Can anybody suggest on what can be done?
    Thanks in Advance,
    Regards
    A.T

    Hi ,
    This is a table space issue....
    u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
    U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
    This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
    Thanks
    Sandeep

  • CX_SY_OPEN_SQL_DB Need Help !

    Hi I'm Getting this Dump
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          01/25/2008 05:30:05
    Short text
    SQL error in the database when accessing a table.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    How to correct the error
    Database error text........: "POS(4477) Too complicated SQL statement (too much
    data)"
    Internal call code.........: "[RSQL/OPEN/ZBBP_CONF_VIEW ]"
    Please check the entries in the system log (Transaction SM21).
    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_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "SAPLZ3P_CLC_FG01" or "LZ3P_CLC_FG01U01"
    "Z3P_CLC_CONFIRMATION_DETAILS"
    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
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "Z3P_CLC_CONFIRMATION_DETAILS" "(FUNCTION)", or its possible occurrence must be
    declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
    System environment
    SAP-Release 700
    Application server... "pwdf1918"
    Network address...... "10.17.99.25"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x AMD64 Level"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "pwdf4324"
    Database type..... "ADABAS D"
    Database name..... "IBP"
    Database user ID.. "SAPR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Oct 1 2007 00:34:30"
    create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
    Database version. "SQLDBC 7.6.1.015 CL 147649 "
    Patch level. 130
    Patch text.. " "
    Database............. "MaxDB 7.6, MaxDB 7.7"
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
    NT 6.0"
    Memory consumption
    Roll.... 16192
    EM...... 4189840
    Heap.... 0
    Page.... 0
    MM Used. 1496416
    MM Free. 2690800
    User and Transaction
    Client.............. 001
    User................ "EBP_ISP"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "FCF9CADCE4F4F16DB8ED0017A44BD489"
    Program............. "SAPLZ3P_CLC_FG01"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "ISP"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "synchron and non-transactional (emode 0, imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 001
    User................ "I802084"
    Transaction......... "SE38"
    Call Program........."Z3P_CLC_MAIN01"
    Function Module..... "Z3P_CLC_CONFIRMATION_DETAILS"
    Call Destination.... "EBP_IBPCLNT001"
    Source Server....... "pwdf4106_ISP_33"
    Source IP Address... "10.21.24.140"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
    Information on where terminated
    Termination occurred in the ABAP program "SAPLZ3P_CLC_FG01" - in
    "Z3P_CLC_CONFIRMATION_DETAILS".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 410
    of the (Include) program "LZ3P_CLC_FG01U01".
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "Z3P_CLC_CONFIRMATION_DETAILS" "(FUNCTION)", but it was neither
    handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLZ3P_CLC_FG01 "; its source code begins in line
    307 of the (Include program "LZ3P_CLC_FG01U01 ".
    Source Code Extract
    Line
    SourceCde
    380
    END OF TAB1 .
    381
    DATA DAT1 TYPE STANDARD TABLE OF ZBBP_WF_STRUC WITH HEADER LINE .
    382
    DATA OUT_DATES2 TYPE STANDARD TABLE OF Z3P_STR03 WITH HEADER LINE .
    383
    384
    DATA : TAB2 LIKE TAB1 OCCURS 10 WITH HEADER LINE.
    385
    DATA : TAB3 LIKE TAB1 OCCURS 10 WITH HEADER LINE.
    386
    387
    RANGES : REF_DOC FOR BBPD_PD_INDEX_H-REF_DOC_NO.
    388
    389
    CHECK NOT IN_TAB IS INITIAL.
    390
    *Appending the range
    391
    LOOP AT IN_TAB INTO WA_IN.
    392
    *out_dates-dedat = '19791003'.
    393
    *Append out_dates.
    394
    395
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
    396
    EXPORTING
    397
    INPUT         = WA_IN-CONFIRMATION
    398
    IMPORTING
    399
    OUTPUT        = WA_IN-CONFIRMATION
    400
    401
    402
    REF_DOC-SIGN = 'I'.
    403
    REF_DOC-LOW(10) = WA_IN-CONFIRMATION.
    404
    REF_DOC-OPTION = 'EQ'.
    405
    APPEND REF_DOC.
    406
    ENDLOOP.
    407
    408
    *Select Query
    409
    >>>>>
    SELECT REF_DOC_NO itm_vper_start Z_VPER_START Z_VPER_END itm_product_type zexpensetype zinvo
    411
    OBJECT_TYPE
    412
    OBJECT_ID
    413
    V~GUID
    414
    FROM zbbp_conf_view AS v "
    415
    LEFT OUTER JOIN bbp_pdisc AS b
    416
    ON vclient  = bclient
    417
    AND vitm_guid  = bguid
    418
    INTO CORRESPONDING FIELDS OF TABLE   TAB1
    419
    WHERE
    420
    object_type   = 'BUS2203'
    421
    AND
    422
    itm_itm_type ne 'HIER'
    423
    and
    424
    ref_doc_no  IN REF_DOC.
    425
    426
    *LOOP AT REF_DOC.
    427
    *SELECT REF_DOC_NO itm_vper_start Z_VPER_START Z_VPER_END itm_product_type zexpensetype zinv
    428
    *OBJECT_TYPE
    429
    *OBJECT_ID
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    0
    SY-FDPOS
    0
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC and RFC Control
    SY-MSGTY
    SY-MSGID
    SY-MSGNO
    000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080125
    SY-UZEIT
    053005
    SY-XPROG
    SAPLZ3P_CLC_FG01
    SY-XFORM
    Z3P_CLC_CONFIRMATION_DETAILS
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    4 FUNCTION     SAPLZ3P_CLC_FG01                    LZ3P_CLC_FG01U01                      410
    Z3P_CLC_CONFIRMATION_DETAILS
    3 FORM         SAPLZ3P_CLC_FG01                    LZ3P_CLC_FG01U01                      307
    Z3P_CLC_CONFIRMATION_DETAILS
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       4 Ty.          FUNCTION
    Name  Z3P_CLC_CONFIRMATION_DETAILS
    IN_TAB[]
    Table IT_0[1019x146]
    \FUNCTION-POOL=Z3P_CLC_FG01\FORM=Z3P_CLC_CONFIRMATION_DETAILS\DATA=%_%_IN_TAB
    Table reference: 0
    TABH+  0(20) = 70292557FE07000070252557FE07000000000000
    TABH+ 20(20) = 0000000000000000FB03000092000000FFFFFFFF
    TABH+ 40(16) = 04010000E003000010000000C1248101
    store        = 0x70292557FE070000
    ext1         = 0x70252557FE070000
    shmId        = 0     (0x00000000)
    id           = 0     (0x00000000)
    label        = 0     (0x00000000)
    fill         = 1019  (0xFB030000)
    leng         = 146   (0x92000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000006
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 1
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0493757FE070000
    pgHook       = 0xB08C3957FE070000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 4     (0x04000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 2032  (0xF0070000)
    lineAlloc    = 1072  (0x30040000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x00252557FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xA0242557FE070000
    delta_head   = 0100000001000000CE0000000100000004010000100400009200000001000000000000000500000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    OUT_DATES[]
    Table IT_1[0x54]
    \FUNCTION-POOL=Z3P_CLC_FG01\FORM=Z3P_CLC_CONFIRMATION_DETAILS\DATA=%_%_OUT_DATES
    Table reference: 1
    TABH+  0(20) = 000000000000000000533757FE07000000000000
    TABH+ 20(20) = 01000000010000000000000036000000FFFFFFFF
    TABH+ 40(16) = 04010000A004000010000000C1248101
    store        = 0x0000000000000000
    ext1         = 0x00533757FE070000
    shmId        = 0     (0x00000000)
    id           = 1     (0x01000000)
    label        = 1     (0x01000000)
    fill         = 0     (0x00000000)
    leng         = 54    (0x36000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000010
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 1
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0x00673857FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x10D43757FE070000
    delta_head   = 0100000002000000CD0000000200000004010000D00400003600000001000000000000000500000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    OUT_DETAILS[]
    Table IT_2[0x244]
    \FUNCTION-POOL=Z3P_CLC_FG01\FORM=Z3P_CLC_CONFIRMATION_DETAILS\DATA=%_%_OUT_DETAILS
    Table reference: 2
    TABH+  0(20) = 000000000000000070673857FE07000000000000
    TABH+ 20(20) = 020000000200000000000000F4000000FFFFFFFF
    TABH+ 40(16) = 040100004004000010000000C1248101
    store        = 0x0000000000000000
    ext1         = 0x70673857FE070000
    shmId        = 0     (0x00000000)
    id           = 2     (0x02000000)
    label        = 2     (0x02000000)
    fill         = 0     (0x00000000)
    leng         = 244   (0xF4000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000008
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 1
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xE0B23957FE070000
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0x80B23957FE070000
    delta_head   = 0100000003000000CC000000030000000401000070040000F400000001000000000000000500000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    %_DUMMY$$
    2222
    0000
    0000
    0000
    SYST-REPID
    SAPLZ3P_CLC_FG01
    5454535544454433222222222222222222222222
    310CA30F3C3F6701000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SY-XPROG
    SAPLZ3P_CLC_FG01
    5454535544454433222222222222222222222222
    310CA30F3C3F6701000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    SY-TABIX
    0
    0000
    0000
    SCREEN
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    SY
    ##############################################################################T#########  ####
    000000F000000000000000000000000000000090000000000000000000000000000000000000105000000010220000
    100000B000000000000000001000100000000020000000000000000000000000000000000000604000000000000500
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    00000030000000000000000000000000000000000000000000000000000000000000000000000000000000E000000C
    <%_TABLE_BBP_PDHGP>
    %_SPACE
    2
    0
    0
    0
    SY-MANDT
    001
    333
    001
    000
    000
    <%_TABLE_BBP_PDISC>
    REF_DOC[]
    Table IT_3[1019x70]
    \FUNCTION=Z3P_CLC_CONFIRMATION_DETAILS\DATA=REF_DOC[]
    Table reference: 3
    TABH+  0(20) = 50FE3957FE070000000000000000000000000000
    TABH+ 20(20) = 0300000003000000FB03000046000000FFFFFFFF
    TABH+ 40(16) = 04010000100D00000A000000C1048001
    store        = 0x50FE3957FE070000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 3     (0x03000000)
    label        = 3     (0x03000000)
    fill         = 1019  (0xFB030000)
    leng         = 70    (0x46000000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000055
    occu         = 10    (0x0A000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0x70FB3957FE070000
    pgHook       = 0x30FB3A57FE070000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 5     (0x05000000)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 1950  (0x9E070000)
    lineAlloc    = 1054  (0x1E040000)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x01000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    TAB1[]
    Table IT_4[0x256]
    \FUNCTION=Z3P_CLC_CONFIRMATION_DETAILS\DATA=TAB1[]
    Table reference: 4
    TABH+  0(20) = 0000000000000000000000000000000000000000
    TABH+ 20(20) = 04000000040000000000000000010000FFFFFFFF
    TABH+ 40(16) = 04010000700A000010000000C1248001
    store        = 0x0000000000000000
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 4     (0x04000000)
    label        = 4     (0x04000000)
    fill         = 0     (0x00000000)
    leng         = 256   (0x00010000)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000041
    occu         = 16    (0x10000000)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    TAB1
    000000000000000000000000                                          00
    2222222222222222222222222233333333333333333333333322222222222222222222222222222222222222222233
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    DAT1-GUID
    2222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000
    TAB1-GUID
    0000000000000000
    0000000000000000
    No.       3 Ty.          FORM
    Name  Z3P_CLC_CONFIRMATION_DETAILS
    %_ARCHIVE
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    %_%_IN_TAB
    Table IT_0[1019x146]
    %_%_OUT_DATES
    Table IT_1[0x54]
    %_VIASELSCR
    0
    4
    %_%_OUT_DETAILS
    Table IT_2[0x244]
    No.       2 Ty.          FORM
    Name  REMOTE_FUNCTION_CALL
    HEADER
    000000000000
    000000000000
    TYPE
    3
    0000
    3000
    SY-XPROG
    SAPLZ3P_CLC_FG01
    5454535544454433222222222222222222222222
    310CA30F3C3F6701000000000000000000000000
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    RC
    0
    0000
    0000
    SY-XFORM
    Z3P_CLC_CONFIRMATION_DETAILS
    535544454444454454445445444522
    A30F3C3F3FE692D149FEF45419C300
    000000000000000000000000000000
    000000000000000000000000000000
    %_SPACE
    2
    0
    0
    0
    No.       1 Ty.          MODULE (PBO)
    Name  %_RFC_START
    %_PRINT
    000                                                                                0###
    2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    RFCTYPE_INTERNAL
    3
    0000
    3000
    Internal notes
    The termination was triggered in function "HandleRsqlErrors"
    of the SAP kernel, in line 764 of the module
    "//bas/700_REL/src/krn/runt/absapsql.c#8".
    The internal operation just processed is "SQLS".
    Internal mode was started at 20080125053005.
    Internal call code.........: "[RSQL/OPEN/ZBBP_CONF_VIEW ]"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    SAP (R) - R/3(TM) Callstack, Version 1.0
    Copyright (C) SAP AG. All rights reserved.
    Callstack without Exception:
    App       : disp+work.EXE (pid=1568)
    When      : 1/25/2008 5:30:5.129
    Threads   : 2
    Computer Name       : PWDF1918
    User Name           : ibpadm
    Number of Processors: 4
    Processor Type: AMD64 Family 15 Model 33 Stepping 2
    Windows Version     : 5.2 Current Build: 3790
    State Dump for Thread Id 2238
    FramePtr         ReturnAd         Param#1          Function Name
    0000000007ccb730 0000000077d7047f 0000000056355570 ntdll!NtWaitForSingleObject
    0000000007ccb7d0 0000000001722861 00000000000002a0 kernel32!WaitForSingleObjectEx
    0000000007ccba20 0000000000610ec5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
    0000000007ccba50 0000000000afbbec 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
    0000000007ccbaa0 0000000000b00e10 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7091)]
    0000000007ccc480 0000000000a1153c 0000000001c934c0 disp+work!ab_rabax [abrabax.c (1231)]
    0000000007ccc520 00000000009e2656 0000000000000000 disp+work!ab_rsqlerr [abdberr.c (787)]
    0000000007ccc630 00000000009e4761 0000000000000003 disp+work!HandleRsqlErrors [absapsql.c (765)]
    0000000007ccc820 00000000009f5543 000000000000003b disp+work!SqlsExecuteCall [absapsql.c (7466)]
    0000000007ccc8d0 00000000008339b2 0000000000000001 disp+work!ab_jsqls [absapsql.c (1414)]
    0000000007ccca50 0000000000a0e8b7 0000000000000008 disp+work!ab_extri [abextri.c (554)]
    0000000007cccaa0 0000000000acb06c 0000000000000008 disp+work!ab_xevent [abrunt1.c (281)]
    0000000007cccb30 000000000066f0a8 0000000000000008 disp+work!ab_dstep [abdynpro.c (492)]
    0000000007ccccb0 0000000000672c7d 000007fe5730c890 disp+work!dynpmcal [dymainstp.c (2403)]
    0000000007cccd40 000000000067267a 000007fe572514a0 disp+work!dynppbo0 [dymainstp.c (543)]
    0000000007cccdf0 0000000000631ed5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
    0000000007ccfc30 00000000004d71d3 0000000000000003 disp+work!dynpen00 [dymain.c (1629)]
    0000000007ccfeb0 000000000042d5a6 0000000007d58600 disp+work!TskhLoop [thxxhead.c (4467)]
    0000000007ccfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1121)]
    0000000007ccff10 00000000019c7781 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
    0000000007ccff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
    0000000007ccffa0 0000000000000000 00000000019c7610 kernel32!BaseProcessStart
    State Dump for Thread Id 374c
    FramePtr         ReturnAd         Param#1          Function Name
    000000000de0fe40 0000000077d5f651 0000000000000000 ntdll!NtFsControlFile
    000000000de0feb0 00000000018ad9af fffffffffffffffe kernel32!ConnectNamedPipe
    000000000de0ff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
    000000000de0ff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
    000000000de0ffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
    List of ABAP programs affected
    Index
    Typ
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    SAPMSSY1
    0
    05/27/2005
    16:45:10
    22528
    E
    1
    Prg
    SAPLZ3P_CLC_FG01
    1
    01/25/2008
    02:47:42
    33792
    E
    2
    Typ
    Z3P_STR01
    0
    11/03/2007
    07:50:03
    3072
    3
    Typ
    Z3P_STR03
    0
    11/03/2007
    07:50:03
    2048
    4
    Typ
    Z3P_STR02
    0
    01/25/2008
    02:47:42
    4096
    5
    Prg
    SAPLALFA
    5
    02/08/2005
    13:13:24
    8192
    E
    6
    Typ
    ZBBP_CONF_VIEW
    0
    09/07/2007
    05:21:21
    10240
    7
    Typ
    BBP_PDISC
    0
    12/06/2007
    04:04:51
    12288
    8
    Prg
    CX_SY_OPEN_SQL_DB=============CP
    8
    07/01/2005
    18:22:20
    12288
    E
    9
    Typ
    SCX_SRCPOS
    0
    02/08/2005
    13:13:15
    2048
    10
    Prg
    CX_SY_OPEN_SQL_ERROR==========CP
    10
    07/01/2005
    18:22:20
    10240
    E
    11
    Prg
    CX_SY_SQL_ERROR===============CP
    11
    07/01/2005
    18:22:20
    10240
    E
    12
    Prg
    CX_DYNAMIC_CHECK==============CP
    12
    07/01/2005
    18:22:20
    10240
    E
    13
    Prg
    CX_ROOT=======================CP
    13
    11/03/2007
    02:55:47
    11264
    E
    14
    Prg
    CX_NO_CHECK===================CP
    14
    07/01/2005
    18:22:20
    10240
    E
    15
    Prg
    CX_SY_NO_HANDLER==============CP
    15
    07/01/2005
    18:22:20
    10240
    E
    16
    Typ
    SYST
    0
    01/23/2005
    00:05:42
    31744
    17
    Typ
    ZBBP_WF_STRUC
    0
    09/07/2007
    05:21:20
    2048
    Directory of Application Tables
    Name                                     Date       Time       Lngth
    Val.
    Program  SAPMSSY1
    SYST                                       /  /       :  :     00004612
    \0\0\0\0\0\0#\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0
    ABAP Control Blocks (CONT)

    What is your database/livecache version?
    Check note 1001257 - SQL error -1105 Too complicated SQL statement
    Markus

  • DBIF_RSQL_INVALID_CURSOR error when using PA20/PA30 transactions

    Has anyone encountered ABAP error DBIF_RSQL_INVALID_CURSOR while trying to use transaction PA20 or PA30. We started seeing this error this morning and we currently cannot figured why.
    Please see the information below and from ST22 and SM21.
    <b>----
    //ST22
    </b>
    ABAP runtime errors    DBIF_RSQL_INVALID_CURSOR
           Occurred on     27.02.2007 at 15:45:31  
    Invalid interruption of a database selection.  
    <b>What happened?                                                    
                                                                      </b>
    The current ABAP/4 program "SAPFP50P " had to be terminated because
    one of the statements could not be executed.                                                                               
    This is probably due to an error in the ABAP/4 program.           
    Unable to perform database selection fully.                       
    <b>Source code extract                                                              
                                                                                    </b>
    004540         dbname = t777d-dbtab.                                 "QNOK019092 
    004550   *   IF t582a-dbidn CA pspar-tclas.                          "QNOK019092 
    004560         psinfo-dbidn = pspar-tclas.                                       
    004570       ELSE.                                                               
    004580         MESSAGE i016 WITH 'Infotyp '(inf) fps_infty 'nicht erlaubt '(not).
    004590         APPEND psinfo.                                                    
    004600         EXIT.                                                             
    004610       ENDIF.                                                              
    004620       CLEAR prel_db.                                                      
    004630                                                                           
    004640   * Herausfinden ob irgendwelche Erweiterungs-FBs verfuegbar sind.        
    004650   *    CALL FUNCTION 'HR_INFOTYPE_EXTENSION_GET'            "XYVAHRK039990
    004660   *         EXPORTING                                       "XYVAHRK039990
    004670   *              INFTY                    = FPS_INFTY       "XYVAHRK039990
    004680   *         IMPORTING                                       "XYVAHRK039990
    004690   *              SELECT_MODULE            = SELECT_MODULE   "XYVAHRK039990
    004700   **              UPDATE_MODULE            =                "XYVAHRK039990
    004710   *              HAS_EXTENSION            = HAS_EXTENSION   "XYVAHRK039990
    004720   *         EXCEPTIONS                                      "XYVAHRK039990
    004730   *              EXTENSION_DOES_NOT_EXIST = 1               "XYVAHRK039990
    004740   *              INTERNAL_ERROR           = 2               "XYVAHRK039990
    004750   *              OTHERS                   = 3.              "XYVAHRK039990
    004760   *    IF NOT SY-SUBRC IS INITIAL.                          "XYVAHRK039990
    004770   *      CLEAR HAS_EXTENSION.                               "XYVAHRK039990
    004780   *    ENDIF.  " NOT SY-SUBRC IS INITIAL.                   "XYVAHRK039990
    004790                                                                           
    <u><b>004800       SELECT * FROM (dbname) INTO  prel_db                                
    004810                              WHERE pernr EQ fps_pernr                     
    004820                              AND   begda LE fps_endda                     
    004830                              AND   endda GE fps_begda                     
         >                              ORDER BY PRIMARY KEY.  </b> </u>                     
    004850                                                                           
    004860   *      IF HAS_EXTENSION = 'X'.                            "XYVAHRK039990
    004870   *        CALL FUNCTION SELECT_MODULE                      "XYVAHRK039990
    004880   *             CHANGING                                    "XYVAHRK039990
    004890   *                  PREL_DB = PREL_DB.                     "XYVAHRK039990
    004900   *      ENDIF.  " HAS_EXTENSION = 'X'.                     "XYVAHRK039990
    004910                                                                           
    004920         MOVE-CORRESPONDING prel_db TO prelp.                              
    004930         CLEAR prel_db.                                                    
    004940         MOVE fps_infty TO prelp-infty.                                    
    004950                                                                           
    004960         MOVE prelp TO fps_pskey.                                          
    004970         READ TABLE ps WITH KEY fps_pskey BINARY SEARCH.                   
    004980         IF sy-subrc NE 0.                                                 
    004990           MOVE sy-tabix TO fps_tabix.                                     
    <b>----
    //SM21
    </b>
    DIA 00 002         PA30 BY7 Database selection with invalid cursor 1                
    DIA 00 002         PA30 R68 Perform rollback                                        
    DIA 00 002         PA30 AB0 Run-time error "DBIF_RSQL_INVALID_CURSOR" occurred      
    DIA 00 002         PA30 AB1 > Short dump "070227 122859 daladg45 RIYER " generated  
    DIA 03 600         PA30 BY7 Database selection with invalid cursor 1                
    DIA 03 600         PA30 R68 Perform rollback                                        
    DIA 03 600         PA30 AB0 Run-time error "DBIF_RSQL_INVALID_CURSOR" occurred      
    DIA 03 600         PA30 AB1 > Short dump "070227 123001 daladg45 RIYER " generated  
    <b>----
    //ADDITIONAL SYSTEM INFORMATION
    </b>
    SAP Release:  4.6C
    Database:        DB2
    SP Level:         Basis 53, ABAP 53, APPL 53, HR B8
    Kernel Level:    4.6D patch level 2265
    Thank you in advance.

    The issue has been resolved and turned out to be as a programming error. The developer had corrected the issue. Unfortunately I don't have the details as far as which part of the code was fixed.

  • Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB

    Hi,
    i need some guides to solve this problem.
    The program works fine in client DEV. However, when it's in QAS, we encounter  short dump: Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
    info from short dump:
    An SQL error occurred when accessing a table.
    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
    "FILL_T_DATA_TABLE" "(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:
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "FILL_T_DATA_TABLE"
    "(FORM)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-24371: data would not fit in current prefe
    buffer"
    Internal call code.........: "[RSQL/FTCH/VBUK ]"
    Please check the entries in the system log (Transaction SM21).
    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_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "ZSDR_SHIPPING_REPORT" or "ZSDR_SHIPPING_REPORT"
    "FILL_T_DATA_TABLE"
    If you cannot solve the problem yourself, please send the...
    Information on where terminated
    The termination occurred in the ABAP program "ZSDR_SHIPPING_REPORT" in
    "FILL_T_DATA_TABLE".
    The main program was "ZSDR_SHIPPING_REPORT ".
    The termination occurred in line 3561 of the source code of the (Include)
    program "ZSDR_SHIPPING_REPORT"
    of the source code of program "ZSDR_SHIPPING_REPORT" (when calling the editor
    35610).
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the
    procedure "FILL_T_DATA_TABLE" "(FORM)" but was not handled locally, not
    declared in the
    RAISING clause of the procedure.
    The procedure is in the program "ZSDR_SHIPPING_REPORT ". Its source code starts
    in line 3468
    of the (Include) program "ZSDR_SHIPPING_REPORT ".
    source code:
    035490
    035500   *get all open sales orders (those that are deemed open at the Sales
    035510   *Order "Header" level)
    035520     clear open_orders.
    035530     refresh open_orders.
    035540     select * into corresponding fields of table open_orders
    035550       from vbuk
    035560       where ( vbtyp = 'C' or vbtyp = 'I' )
    035570         and ( gbstk = 'A' or gbstk = 'B' ).
    035580
    035590   *get all open deliveries(some sales orders may be closed yet the
    035600   *associated Delivery is not yet PGI'd)
         >     clear open_deliveries.
    035620     refresh open_deliveries.
    035630     select * into corresponding fields of table open_deliveries
    035640       from vbuk
    035650       where vbtyp = 'J'
    035660         and ( wbstk = 'A' or wbstk = 'B' ).
    035670
    035680   *get sales orders associated with the Open deliveries
    Please advice.
    Thanks.

    Thanks for the response.
    Hi Renga,
    The error happens in second selection.
    this is the souce code:
    data: begin of open_orders occurs 0,
            vbeln like vbuk-vbeln,
            gbstk like vbuk-gbstk,
            vbtyp like vbuk-vbtyp,
          end of open_orders.
    data: begin of open_deliveries occurs 0,
            vbeln like vbuk-vbeln,
            wbstk like vbuk-wbstk,
            vbtyp like vbuk-vbtyp,
          end of open_deliveries.
    *get all open sales orders (those that are deemed open at the Sales
    *Order "Header" level)
      clear open_orders.
      refresh open_orders.
      select * into corresponding fields of table open_orders
        from vbuk
        where ( vbtyp = 'C' or vbtyp = 'I' )
          and ( gbstk = 'A' or gbstk = 'B' ).
    *get all open deliveries(some sales orders may be closed yet the
    *associated Delivery is not yet PGI'd)
      clear open_deliveries.
      refresh open_deliveries.
      select * into corresponding fields of table open_deliveries
        from vbuk
        where vbtyp = 'J'
          and ( wbstk = 'A' or wbstk = 'B' ).
    Hi Prabhu,
    how to identify the problem in DB02?
    Please advice.
    Thanks.
    regards.

  • SAP Web Service error text : The database returned a value containing an error , type  CX_SY_OPEN_SQL_DB

    Hello Guru's,
    we are creating sales order in SAP from a quote created in .NET,  through Web Service created in SAP, and consumed in .NET.
    When ever a order is created in SAP for a given quote, SAP returns the sales order number to .NET.
    Orders are getting created as expected, but once in a while we are getting the following error from webservice :
    Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
    But the problem is order is getting created in SAP for the perticular quote for which we are getting the above error and this order number is not getting returned to .NET.
    Upon analysis in TCODE  SRT_UTIL for the above transaction ID, has the following details , which are hardly help full to resolve the error.
    ----TYPE                                  CX_SY_OPEN_SQL_DB
    ----ERROR_TEXT                   The database returned a value containing an error
    ----CX_SY_NO_HANDLER
    -----CLASSNAME                     CX_SY_OPEN_SQL_DB
    This Exception raised by Web Service application
    Could you please help in resolving this issue or alteast provide an approach for the same.
    Thank you,
    Suresh.

    Thank you Bhaskar,
    How can we clarify whether the error is from SAP or Web part.
    I have checked ST22, but there is not entry for the perticular  exception transaction ID
    My exception time stamp is
    -------------------START-------------6/9/2014 1:34:33 PM
    Error :Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
    -------------------END-------------6/9/2014 1:34:33 PM
    In al11, i found the following for the perticular exception time stamp
    **** Trace file opened at 20140609 133431 Eastern Daylight Time, by disp+work
    **** Versions SAP-REL 720,0,500 RFC-VER U 3 1442251 MT-SL
    XRFC> Begin of user trace
    XRFC> ---------------------------------------------------------------------
    XRFC>                                                                     <
    XRFC> TRACE SOAP RUNTIME - header                                         <
    XRFC>                                                                     <
    XRFC> ------------------------------------------------------------------  <
    XRFC> REQ_SIZE   : 2685                                                   <
    XRFC> RESP_SIZE  : 0                                                      <
    XRFC> PARENT_ID  : ROOT_CALL_ID                                           <
    XRFC> TRC_KEY    : 40FCEFE3BD6EF184B5CE00155D0B4530                       <
    XRFC> REQ_BASED  :                                                        <
    XRFC> SESSION_ID : 0003925540FCEFE3BD6EF17DB5CE00155D0B4530               <
    XRFC> TS_CALL    : 20140609173408.2880000                                 <
    XRFC> SY_UNAME   :                                            <
    XRFC> HOSTNAME   :                                              <
    XRFC> SY_SID     : PRD                                                    <
    XRFC> SY_MANDT   : 300                                                    <
    XRFC> SYS_NR     : 19                                                     <
    XRFC> APPLSERVER :                                      <
    XRFC> ISPRESCHED : X                                                      <
    XRFC> DURATION   : 21810                                                  <
    XRFC> NETHDRTIME : 21810                                                  <
    XRFC> CALL_STATE : 2                                                      <
    XRFC> ERRORTYPE  : APPLFAIL                                               <
    XRFC> ERRORAREA  : APPL                                                   <
    XRFC> CTXDP_TYPE : SOAP_RUNTIME                                           <
    XRFC> SYNC_ASYNC : S                                                      <
    XRFC> LOCATION   : P                                                      <
    XRFC> DIRECTION  : I                                                      <
    XRFC> REQ_ID     : 91C57815916E421CA9F3D652FFACE9C7                       <
    XRFC> RESP_ID    : 00155D0B45301EE3BBFF89A0267EB5CE                       <
    XRFC> MSG_STATE  : 114                                                    <
    XRFC> IF_NAME_I  : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> IF_NS_E    : urn:sap-com:document:sap:soap:functions:mc-style       <
    XRFC> IF_NAME_E  : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> ISSHORTCUT :                                                        <
    XRFC> TRC_PATT   : WSTEST                                                 <
    XRFC> TRC_SSID   : PRD_19                                                 <
    XRFC> TRC_USER   :                                           <
    XRFC> TRC_TS     : 20140609173409                                         <
    XRFC> TRC_COUNT  : 99                                                     <
    XRFC> TRC_EXT    :                                                        <
    XRFC> COMPLETE   : OK                                                     <
    XRFC> CALLEDPROG : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> SOAP_APPLI : urn:sap-com:soap:runtime:application:rfc:710           <
    XRFC> CONF_ID    : 00155D0B45301EE3AEFDAD78756555CE                       <
    XRFC> BIND_ID    : 00155D0B45301EE3AEFDAD787565B5CE                       <
    XRFC> OP_NAME    : ZsdCsCreateSalesorder                                  <
    XRFC> COMM_PATRN : Method:ZsdCsCreateSalesorder                           <
    XRFC> OP_NS      : urn:sap-com:document:sap:soap:functions:mc-style       <
    XRFC> REMADDRESS : 172.16.11.43                                           <
    XRFC> DT_OBJ     : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> MEMCONSUMP : 296291                                                 <
    XRFC> WSHOST     :                                                        <
    XRFC> WSPORT     :                                                        <
    XRFC> WSPROT     :                                                        <
    XRFC> WSCLIENT   :                                                        <
    XRFC> WSPATH     :                                                        <
    XRFC> PXYHOST    :                                                        <
    XRFC> PXYPORT    :                                                        <
    XRFC> USEDRFCDES :                                                        <
    XRFC> BONAME     :                                                        <
    XRFC> PROCCOMP   :                                                        <
    XRFC> DEPLOYUNIT :                                                        <
    XRFC> ------------------------------------------------------------------  <
    XRFC>                                                                     <
    XRFC> TRACE SOAP RUNTIME - trace records                                  <
    XRFC>                                                                     <
    XRFC> ------------------------------------------------------------------  <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING Exception handling for IF "ZSD_CS_CREATE       <
    XRFC> _SALESORDER_SERVI" OP name "ZsdCsCreateSalesorder" MSG ID           <
    XRFC> "91C57815916E421CA9F3D652FFACE9C7" user "STULZWEBSERV"              <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7240000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SOAP_ROOT : An exception has occurred. |    <
    XRFC> program: CL_SOAP_RUNTIME_ROOT==========CP include: CL_SOAP          <
    XRFC> _RUNTIME_ROOT==========CM004 line: 120                              <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SY_NO_HANDLER : An exception with the type  <
    XRFC> CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor    <
    XRFC> declared in a RAISING clause | program: SAPLSTXD include: LSTXDFDB  <
    XRFC> line: 200                                                           <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SY_OPEN_SQL_DB : The database returned a    <
    XRFC> value containing an error | program: SAPLSTXD include: LSTXDFDB     <
    XRFC> line: 227                                                           <
    XRFC>                                                                     <
    XRFC> ---------------------------------------------------------------------
    XRFC> End of user trace

  • DBIF_RSQL_INVALID_CURSOR: Invalid interruption of a database selection.

    I have created an external program that extracts a very large table from SAP 7.0 through RFC using the NetWeaver SDK APIs. This program repeatedly calls an RFC-enabled function written in ABAP. On the first
    call the function does "OPEN CURSOR WITH HOLD" and a "FETCH". On each subsequent call the function does a "FETCH". The cursor is declared as "STATICS".
    When I run the program I am getting the following error:
    DBIF_RSQL_INVALID_CURSOR: Invalid interruption of a database selection.
    This error manifests itself in two ways.
    1) When time interval between RfcInvoke() calls is about 0.5 sec., it takes 30 sec. to 90 sec. for the error to come out.
    2) When time interval between RfcInvoke() calls is about 0.2 sec. or lower, it takes 8 min. to 17 min. for the error to come out, but sometimes the program completes successfully in 25 min.
    1) What is causing this error?
    2) If it has something to do with SAP configuration, how it be modified to extract this particular table.
    3) Is it possible in general to extract a table of any size (on the magnitude of gigabytes) using such an approach, that is, a "pull".
    4) If the answer is negative, what approach do you think is appropriate.
    Any help will be appreciated.

    Hi Andrew Coleman  ,
                                     This error sounds like problem is in the way you are calling the RFC Function module (n -number of times). Looks like during the subsequent calls the Select / ENDSELECT  is failing need to check that logic.
    Thanks,
    Greetson

  • 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

  • "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB" while updating the custom table

    hi friends...
    i am posting fico document using bapi BAPI_ACC_GL_POSTING_POST.
    after that i am updating the document number to my custom table.
    but in some cases while updating the document in my custom table i am getting the fallowing dump..
    in ST22
    How to correct the error:
    Database error text........: "[1205] Transaction (Process ID 66) was deadlocked
    on lock resources with another process and has been chosen as the deadlock
    victim. Rerun the transaction."
    Internal call code.........: "[RSQL/UPDT/ZIF004_PKT ]"
    Please check the entries in the system log (Transaction SM21).
    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_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "ZFI_01_MONTHLY_RESULT_FRM_PKT" or "ZFI_01_MONTHLY_RESULT_FRM_PKT"
    "UPLOAD_SAP"
    Source Code Extract
    LOOP AT i_zif004_pkt_sum .
    UPDATE zif004_pkt SET xblnr = i_zif004_pkt_sum-xblnr ---> i am getting DUMP here
                              gjahr = i_zif004_pkt_sum-gjahr
                              sap_flag_posting = i_zif004_pkt_sum-sap_flag_posting
                          WHERE compcode = i_zif004_pkt_sum-compcode
                         AND ccode = i_zif004_pkt_sum-ccode
                          AND wbselement = i_zif004_pkt_sum-wbselement
                          AND kostl = i_zif004_pkt_sum-kostl
                          AND code = i_zif004_pkt_sum-code
                          AND month1 = l_ltx
                          AND year1 = p_year.
        IF sy-subrc = 0.
          WRITE :/ 'Document ', i_zif004_pkt_sum-xblnr, 'is posted for ', i_zif004_pkt_sum-code.
        ENDIF.
      ENDLOOP.
    kindly give some inputs..
    regards
    Selva

    Hi,
    You will face this issue if your oracle data base is lack of work processes. try to check the work processes and increase them if possible with the helps basis guys.
    check the below thread.
    DI job failed ORA-12537: TNS:connection closed.
    Regards,
    Venkatesh

  • SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB in VA02

    Hi Experts,
                  I have an issue when tried to update the reason for rejection for a particular line item.
    When updated the reason for rejection..and press save  ,system prompts to select the schedule line, when it is selected...program says update terminated..
       With error as
    "SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DB
    "SAPLV45U" or "LV45UF0V"
    "VBEP_BEARBEITEN"
    Report-LV45UF0V
    Row 257
    Source code...
    INSERT VBEP FROM TABLE DA_XVBEPI.
    while debugging, it is not prompting to that Insert statement.

    In order to reach the debugger you have switch on update debugging that is first thing.
    My question to you is have you implemented any code in sales order exits or some one else has done it.
    Does it happen for all the different sales order..?
    Please check whether in MV45AFZZ some code has been done in the sub routine like USEREXIT_SAVE_DOCUMENT_PREPARE etc
    Please search on service.sap.com for the same dump
    Most probably its the custom enhancement coded in a wrong way is the reason.
    Nabheet

Maybe you are looking for

  • Parameter WDA - Workflow

    Hi All. I seen couples thread in this forum talking about WDA and WF. Especially related with SWFVISU transaction where WF can sent work item id to WDA. Is there any way for us to send some data back to caller (workflow task) thru one of WDA paramete

  • DBconsole is terminated with signal 99 from time to time in 10g RAC!!

    Hi, all. The database is 2 node RAC 10.2.0.2.0 on 32-bit Windows 2003 EE SP1. We are not using Grid Control. I installed Enterprise Manager by using DBCA. From time to time, Console and agent processes are restarted "automatically". --> emdb.nohup --

  • Mobile me movies

    I published my home movies to my "mobile me gallery" a year or two ago.  Is there any way I can find these movies?  I didn't keep any copies.

  • Processor field in Purchase Requisition

    Hello. I am using user exit to determine the agents for my Purchase Requisition workflow. The workflow is working fine and work items are going to the right agents. However, the PROCESSOR field (under the Release Strategy tab) has the name of the wor

  • Advanced Web Gallery CS4

    I have recently upgraded from CS2. I have a handful of these galleries on the same site I created using CS2. I have modified them heavily from what CS2 would do. In reality I only used the Thumbnails, Images and the XML file that were created. Even t