ABAP Dump:DBIF_RSQL_INVALID_CURSOR in SAP Query

Hello All,
We have a strange dump DBIF_RSQL_INVALID_CURSOR coming up in of our Custom Query in MM module. The Query goes in dump for some users and for other user it is working perfectly.
There has been no change done from ABAP side in the Query and it was working well before.
We analyzed the Dump in ST22 and found that dump is triggered at Select statement (Join statement for MARC)..However this is happening for some users.
There seems to be no ABAP error as nothing has been done on it.
Could any one let me know why this DUMP is coming..is it a KERNEL change issue or something in BASIS triggers it.
Please suggest!!
Thank you
Arvind

Hello,
Users are not in debugging mode and they are simply executing transaction which is attached to program name of ABAP Query.
here is the erroneous select:
select MARCAUFTL MARCBESKZ MARCBSTMI MARCBSTRF MARCDIBER MARCDISLS
       MARCMAABC MARCMATNR MARCMINBE MARCMMSTA MARCMTVFP MARCPERKZ
       T001WWERKS MARAGEWEI MARAMATKL MARAMATNR MARAMEINS MARAMSTA
       ZMM_MATCATEWERKS ZMM_MATCATEZXYZ MBEWBWKEY MBEWBWTAR MBEW~MAT
       T001KBUKRS T001KBWKEY T001BUKRS T001WAERS
into (MARC-AUFTL , MARC-BESKZ , MARC-BSTMI , MARC-BSTRF , MARC-DIBER , M
     , MARC-EISBE , MARC-EKGRP , MARC-MAABC , MARC-MATNR , MARC-MINBE ,
     , MARC-SOBSL , MARC-WEBAZ , MARC-WERKS , T001W-SPRAS , T001W-WERKS
     , MARA-MSTAV , MARA-MTART , MARA-NTGEW , MARA-PRDHA , ZMM_MATCATE-M
     , MBEW-BWTAR , MBEW-MATNR , MBEW-PEINH , MBEW-SALK3 , MBEW-STPRS ,
     , T001-BUKRS , T001-WAERS )
from ( MARC
       inner join T001W
       on T001WWERKS = MARCWERKS
       inner join MARA
       on MARAMATNR = MARCMATNR
       left outer join ZMM_MATCATE
       on ZMM_MATCATEMATNR = MARCMATNR
       and ZMM_MATCATEWERKS = MARCWERKS
       inner join MBEW
Thanks
Arvind
Edited by: Arvind Soni on Nov 26, 2009 12:26 PM

Similar Messages

  • Abap runtime error in sap query

    hi all,
    i was using a query to generate a specific report for quite some time. and it was running well. but since yesterday morning the query started giving the following error msg while executing:
    "variant STANDARD not created"
    i tried giving other variant but failed. so i decided to run te report witout variant. for this i went for CHANGE mode of query and i removed query and made the report RUN WITHOUT VARIANT. after tat system didnt asked for variant but while executing it started giving ABAP dump.
    where to check? please suggest
    Warm regards,
    BKR

    Hi,
    When it give dump,it is clearly display which & where it is unable to execute ststement.
    Take help ogf ABAPer.
    Kapil

  • ABAP DUMP - DYNPRO_FIELD_CONVERSION !!!

    Hii SAP Expert,
    I having a problem when diplaying the material document using reservation number, below is the abap dump error from sap, could anyone tell me what is the problem ?
    Runtime Error          DYNPRO_FIELD_CONVERSION
    Date and Time          31.12.2007 17:49:41
    <removed by moderator as the content doesnt help to understand the problem>
    Error analysis
    The program flow was interrupted and could not be resumed.
    Program "SAPLMIGO" tried to display fields on screen 0370. However, an
    error occurred while this data was being converted.
    How to correct the error
    A conversion error occurred while the program was trying to
    display data on the screen.
    The ABAP output field and the screen field may not have the
    same format.
    Some field types require more characters on the screen than
    in the ABAP program. For example, a date field on a screen needs
    two characters more than it would in the program. When attempting to
    display the date on the screen, an error will occur that triggers the
    error message.
    Screen name.............. "SAPLMIGO"
    Screen number............ 0370
    Screen field............. "GOITEM-VMENG"
    Error text............... "FX015: Sign lost."
    Further data:
    <removed by moderator as the content doesnt help to understand the problem>            |
    "DYNPRO_FIELD_CONVERSION" " "
    "SAPLMIGO" bzw. "LMIGOPBO"
    "PBO_DETAIL_RESERVATION"
    System environment
    SAP Release.............. "640"
    Application server....... "pecprd00"
    Network address.......... "192.168.1.122"
    Operating system......... "HP-UX"
    Release.................. "B.11.23"
    Hardware type............ "ia64"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 2
    Short dump setting....... "full"
    Database server.......... "pesbdbci"
    Database type............ "ORACLE"
    Database name............ "ECP"
    Database owner........... "SAPECP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Mar 21 2007 20:14:03"
    Created in............... "HP-UX B.11.23 U ia64"
    Database version......... "OCI_920 "
    Patch level.............. "175"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
    10.2.0.."
    SAP database version..... "640"
    Operating system......... "HP-UX B.11"
    Memory usage.............
    Roll..................... 16192
    EM....................... 33518720
    Heap..................... 0
    Page..................... 425984
    MM Used.................. 7977808
    MM Free.................. 399024
    SAP Release.............. "640"
    User and Transaction
    Client.............. 900
    User................ "GHAZALM"
    Language key........ "E"
    Transaction......... "/DBM/ORDER03 "
    Program............. "SAPLMIGO"
    Screen.............. "SAPLMIGO 0370"
    Screen line......... 0
    Information on where terminated
    The termination occurred in the ABAP program "SAPLMIGO" in
    "PBO_DETAIL_RESERVATION".
    The main program was "MB_CALL_MIGO_DIALOG ".
    The termination occurred in line 296 of the source code of the (Include)
    program "LMIGOPBO"
    of the source code of program "LMIGOPBO" (when calling the editor 2960).
    Source Code Extract
    Line
    SourceCde
    266
    ENDMODULE.                 " PBO_DETAIL_ORDER  OUTPUT
    267
    268
    *&      Module  PBO_DETAIL_TRANSFER OUTPUT
    269
    270
    MODULE pbo_detail_transfer OUTPUT.
    271
    CALL METHOD oref_detail_transfer->pbo.
    272
    ENDMODULE.                 " PBO_DETAIL_TRANSFER  OUTPUT
    273
    274
    *&      Module  PBO_BOM_POPUP  OUTPUT
    275
    276
    MODULE pbo_bom_popup OUTPUT.
    277
    CALL METHOD oref_bom->pbo.
    278
    ENDMODULE.                 " PBO_BOM_POPUP  OUTPUT
    279
    280
    *&      Module  PBO_DEFAULTS_LOOP  OUTPUT
    281
    282
    MODULE pbo_defaults_loop OUTPUT.
    283
    CALL METHOD oref_defaults->pbo_loop.
    284
    ENDMODULE.                 " PBO_DEFAULTS_LOOP  OUTPUT
    285
    286
    *&      Module  PBO_SEARCH_RES  OUTPUT
    287
    288
    MODULE pbo_search_res OUTPUT.
    289
    CALL METHOD oref_search->pbo.
    290
    ENDMODULE.                 " PBO_SEARCH_RES  OUTPUT
    291
    292
    *&      Module  PBO_DETAIL_RESERVATION  OUTPUT
    293
    294
    MODULE pbo_detail_reservation OUTPUT.
    295
    CALL METHOD oref_detail_reservation->pbo.
    >>>>>
    ENDMODULE.                 " PBO_DETAIL_RESERVATION  OUTPUT
    297
    298
    299
    *&      Module  PBO_DETAIL_TAKEIT  OUTPUT
    300
    301
    MODULE pbo_detail_takeit OUTPUT.
    302
    CALL METHOD oref_detail_takeit->pbo.
    303
    ENDMODULE.                 " PBO_DETAIL_TAKEIT  OUTPUT
    304
    305
    *&      Module  PBO_DETAIL_PARTNERS  OUTPUT
    306
    307
          Detail Tabstrip Partners
    308
    309
    MODULE pbo_detail_partners OUTPUT.
    310
    CALL METHOD oref_detail_partners->pbo.
    311
    ENDMODULE.                 " PBO_DETAIL_PARTNERS  OUTPUT
    312
    313
    *&      Module  PBO_DETAIL_DEST_SUB_SELECT  OUTPUT
    314
    315
    MODULE pbo_detail_dest_sub_select OUTPUT.
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    0
    SY-TABIX
    0
    SY-DBCNT
    1
    SY-FDPOS
    40
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    MIGO_STATUS
    SY-UCOMM
    SY-TITLE
    Display Material Document 4901380914 - Ghazali Musa
    SY-MSGTY
    E
    SY-MSGID
    DA
    SY-MSGNO
    300
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    3 MODULE (PBO) SAPLMIGO                            LMIGOPBO                              296
    PBO_DETAIL_RESERVATION
    2 FUNCTION     SAPLMIGO                            LMIGOU02                              225
    MIGO_DIALOG
    1 EVENT        MB_CALL_MIGO_DIALOG                 MB_CALL_MIGO_DIALOG                    37
    START-OF-SELECTION
    Chosen variables
    Name
    Val.
    No.       3 Ty.          MODULE (PBO)
    Name  PBO_DETAIL_RESERVATION
    %_DUMMY$$
    0000
    0000
    2222
    0000
    OREF_DETAIL_RESERVATION
    A0000005
    70000008
    No.       2 Ty.          FUNCTION
    Name  MIGO_DIALOG
    I_ACTION
    A04
    000
    000
    433
    104
    I_DEADEND
    X
    0
    0
    5
    8
    I_EBELN
    0000000000
    0000000000
    2222222222
    0000000000
    I_EBELP
    00000
    00000
    00000
    33333
    00000
    I_INBOUND_DELIV
    0000000000
    0000000000
    2222222222
    0000000000
    I_LEAVE_AFTER_POST
    0
    0
    2
    0
    I_MBLNR
    4901380914
    0000000000
    0000000000
    3333333333
    4901380914
    I_MJAHR
    0000
    0000
    0000
    3333
    0000
    I_NEW_ROLLAREA
    0
    0
    2
    0
    I_NOTREE
    X
    0
    0
    5
    8
    I_NO_AUTH_CHECK
    0
    0
    2
    0
    I_OKCODE
    OK_GO
    00000000000000000000
    00000000000000000000
    44544222222222222222
    FBF7F000000000000000
    I_ORDER_ITEM
    0000
    0000
    0000
    3333
    0000
    I_ORDER_NUMBER
    000000000000
    000000000000
    222222222222
    000000000000
    I_OUTBOUND_DELIV
    0000000000
    0000000000
    2222222222
    0000000000
    I_REFDOC
    R02
    000
    000
    533
    202
    I_RESERVATION_ITEM
    0000
    0000
    0000
    3333
    0000
    I_RESERVATION_NUMB
    0000000000
    0000000000
    0000000000
    3333333333
    0000000000
    I_SKIP_FIRST_SCREEN
    X
    0
    0
    5
    8
    I_SYTCODE
    /DBM/ORDER03
    00000000000000000000
    00000000000000000000
    24442454453322222222
    F42DFF24520300000000
    I_TRANSPORT
    0000000000
    0000000000
    2222222222
    0000000000
    I_TRANSPORTIDENT
    00000000000000000000
    00000000000000000000
    22222222222222222222
    00000000000000000000
    I_TRANSPORT_MEANS
    0000
    0000
    2222
    0000
    I_ZEILE
    0000
    0000
    0000
    3333
    0000
    SY
    #######################(###############j#########(#################################(#### C####
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000100
    0000000000000000000000020000000000000006000000000200000000000000000000000000010900020008240000
    000000010000000000000108010001000000000A0000000008000000000000000000000000000A000008000003000C
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_EBELP
    00000
    00000
    00000
    33333
    00000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_MBLNR
    4901380914
    0000000000
    0000000000
    3333333333
    4901380914
    SPACE
    0
    0
    2
    0
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_MJAHR
    0000
    0000
    0000
    3333
    0000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_ZEILE
    0000
    0000
    0000
    3333
    0000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_TRANSPORT
    0000000000
    0000000000
    2222222222
    0000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_ORDER_NUMBER
    000000000000
    000000000000
    222222222222
    000000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_ORDER_ITEM
    0000
    0000
    0000
    3333
    0000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_TRANSPORT_MEANS
    0000
    0000
    2222
    0000
    RL50E
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_TRANSPORTIDENT
    00000000000000000000
    00000000000000000000
    22222222222222222222
    00000000000000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_INBOUND_DELIV
    0000000000
    0000000000
    2222222222
    0000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_OUTBOUND_DELIV
    0000000000
    0000000000
    2222222222
    0000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_RESERVATION_NUMB
    0000000000
    0000000000
    0000000000
    3333333333
    0000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_RESERVATION_ITEM
    0000
    0000
    0000
    3333
    0000
    SY-REPID
    SAPLMIGO
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454444422222222222222222222222222222222
    310CD97F00000000000000000000000000000000
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_ACTIVE
    X
    0
    0
    5
    8
    ABAP_TRUE
    X
    0
    0
    5
    8
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_LEAVE_AFTER_POST
    0
    0
    2
    0
    LCL_MIGO_GLOBALS=>EXTERNAL_CALL_FIRST_ROUND
    0
    0
    2
    0
    GOSEARCH_RES
    00000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222333333332222222222222222222222222222222222222222222222
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    No.       1 Ty.          EVENT
    Name  START-OF-SELECTION
    I_NOTREE
    X
    0
    0
    5
    8
    I_IN_DEL
    0000000000
    0000000000
    2222222222
    0000000000
    I_LEAVE_
    0
    0
    2
    0
    VARI
    ###00000000000000      ############
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    2222222222222222222222222222222222222222222222222222222222200033333333333333222222000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    I_MBLNR
    4901380914
    0000000000
    0000000000
    3333333333
    4901380914
    I_MJAHR
    0000
    0000
    0000
    3333
    0000
    I_NEW_RO
    0
    0
    2
    0
    I_NO_AUT
    0
    0
    2
    0
    I_OKCODE
    OK_GO
    00000000000000000000
    00000000000000000000
    44544222222222222222
    FBF7F000000000000000
    %_I_ACTION_%_APP_%
    I_ACTION
    000000000000000000000000000000
    000000000000000000000000000000
    454454442222222222222222222222
    9F1349FE0000000000000000000000
    I_ORDERI
    0000
    0000
    0000
    3333
    0000
    I_ACTION
    A04
    000
    000
    433
    104
    I_ORDERN
    000000000000
    000000000000
    222222222222
    000000000000
    %_I_NOTREE_%_APP_%
    I_NOTREE
    000000000000000000000000000000
    000000000000000000000000000000
    454455442222222222222222222222
    9FEF42550000000000000000000000
    I_OUT_DE
    0000000000
    0000000000
    2222222222
    0000000000
    SY-XFORM
    CONVERSION_EXIT
    000000000000000000000000000000
    000000000000000000000000000000
    444545544454545222222222222222
    3FE65239FEF5894000000000000000
    I_REFDOC
    R02
    000
    000
    533
    202
    %_I_NO_AUT_%_APP_%
    I_NO_AUT
    000000000000000000000000000000
    000000000000000000000000000000
    454454552222222222222222222222
    9FEFF1540000000000000000000000
    I_RES_IT
    0000
    0000
    0000
    3333
    0000
    I_RES_NU
    0000000000
    0000000000
    0000000000
    3333333333
    0000000000
    I_SKIP_F
    X
    0
    0
    5
    8
    I_SYTCOD
    /DBM/ORDER03
    00000000000000000000
    00000000000000000000
    24442454453322222222
    F42DFF24520300000000
    SY-LDBPG
    SAPDB__S
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    5454455522222222222222222222222222222222
    31042FF300000000000000000000000000000000
    I_TRANSP
    0000000000
    0000000000
    2222222222
    0000000000
    %_I_REFDOC_%_APP_%
    I_REFDOC
    000000000000000000000000000000
    000000000000000000000000000000
    455444442222222222222222222222
    9F2564F30000000000000000000000
    I_TR_IDE
    00000000000000000000
    00000000000000000000
    22222222222222222222
    00000000000000000000
    I_TR_MEA
    0000
    0000
    2222
    0000
    I_ZEILE
    0000
    0000
    0000
    3333
    0000
    %_DUMMY$$
    0000
    0000
    2222
    0000
    %_I_SKIP_F_%_APP_%
    I_SKIP_F
    000000000000000000000000000000
    000000000000000000000000000000
    455445542222222222222222222222
    9F3B90F60000000000000000000000
    SY-REPID
    MB_CALL_MIGO_DIALOG
    0000000000000000000000000000000000000000
    0000000000000000000000000000000000000000
    4454444544445444444222222222222222222222
    D2F31CCFD97FF491CF7000000000000000000000
    SY-SUBRC
    0
    0000
    0000
    %_SSCR[]
    Table IT_0[24x492]
    \PROGRAM=MB_CALL_MIGO_DIALOG\DATA=%_SSCR[]
    Table reference: 0
    TABH+  0(20) = C000000251801770000000000000000000000000
    TABH+ 20(20) = 000000000000000000000018000001ECFFFFFFFF
    TABH+ 40(16) = 04000000000003B000202CC021000000
    store        = 0xC000000251801770
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 0     (0x00000000)
    label        = 0     (0x00000000)
    fill         = 24    (0x00000018)
    leng         = 492   (0x000001EC)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000006
    occu         = 32    (0x00000020)
    access       = 1     (ItAccessStandard)
    idxKind      = 1     (ItIndexLinear)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 0
    collHash     = 0
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000002518A66C0
    pghook       = 0x0000000000000000
    idxPtr       = 0xC000000251801B50
    refCount     = 2     (0x00000002)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 32    (0x00000020)
    lineAlloc    = 32    (0x00000020)
    store_id     = 2     (0x00000002)
    shmIsReadOnly = 0     (0x00000000)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    hsdir        = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    Internal notes
    The termination occurred in the function "dynpconv.c" of the SAP
    Basis System, specifically in line 701 of the module
    "//bas/640_REL/src/krn/dynp/dybas.c#5".
    The internal operation just processed is "ENDM".
    The internal session was started at 20071231174940.
    Application server....... "pecprd00"
    Network address.......... "192.168.1.122"
    Operating system ........ "HP-UX"
    Release.................. "B.11.23"
    Hardware type............ "ia64"
    Database server.......... "pesbdbci"
    Database type............ "ORACLE"
    Database name............ "ECP"
    Database user ID......... "SAPECP"
    triggers this error message.
    Screen name.............. "SAPLMIGO"
    Screen number............ 0370
    Screen field............. "GOITEM-VMENG"
    Error text............... "FX015: Sign lost."
    Additional data:
    Application server....... "pecprd00"
    Network address.......... "192.168.1.122"
    Operating system......... "HP-UX"
    Release.................. "B.11.23"
    Hardware type............ "ia64"
    Database server.......... "pesbdbci"
    Database type............ "ORACLE"
    Database name............ "ECP"
    Database user ID........ "SAPECP"
    Active Calls in SAP Kernel
    Lines of C Stack in Kernel (Structure Differs on Each Platform)
    (0)  0x40000000017dab60  CTrcStack2 + 0x1b0  [dw.sapECP_DVEBMGS10]
    (1)  0x40000000017da970  CTrcStack + 0x30  [dw.sapECP_DVEBMGS10]
    (2)  0x4000000002373150  Z16rabaxCStackSavev + 0x1d0  [dw.sapECP_DVEBMGS10]
    (3)  0x400000000236f3b0  ab_rabax + 0x2d20  [dw.sapECP_DVEBMGS10]
    (4)  0x40000000017efdf0  dyHandleError + 0x300  [dw.sapECP_DVEBMGS10]
    (5)  0x40000000018ec770  dypcnvoXt + 0x3410  [dw.sapECP_DVEBMGS10]
    (6)  0x40000000018e9330  dypcnvo + 0x30  [dw.sapECP_DVEBMGS10]
    (7)  0x40000000018b29c0  dynpdco0 + 0x1e0  [dw.sapECP_DVEBMGS10]
    (8)  0x40000000018b91c0  dynprctl + 0x390  [dw.sapECP_DVEBMGS10]
    (9)  0x40000000018a5c30  dynpen00 + 0x910  [dw.sapECP_DVEBMGS10]
    (10) 0x4000000001513620  Thdynpen00 + 0x460  [dw.sapECP_DVEBMGS10]
    (11) 0x40000000014e3b60  TskhLoop + 0x46d0  [dw.sapECP_DVEBMGS10]
    (12) 0x40000000014da820  tskhstart + 0x3a0  [dw.sapECP_DVEBMGS10]
    (13) 0x40000000013b6e50  DpMain + 0x490  [dw.sapECP_DVEBMGS10]
    (14) 0x40000000013b1b40  main + 0x70  [dw.sapECP_DVEBMGS10]
    (15) 0xc00000000002fb20  main_opd_entry + 0x50  [/usr/lib/hpux64/dld.so]
    List of ABAP programs affected
    Index
    Ty.
    Program
    Group
    Date
    Time
    Size
    Lang.
    0
    Prg
    MB_CALL_MIGO_DIALOG
    0
    18.09.2001
    10:17:04
    55296
    E
    1
    Prg
    SAPMSSY0
    1
    10.08.2006
    17:27:06
    83968
    E
    2
    Prg
    SAPMSSYD
    1
    10.08.2006
    17:30:43
    20480
    E
    3
    Prg
    SAPFSYSCALLS
    1
    06.11.2003
    20:52:59
    7168
    E
    4
    Prg
    RSDBRUNT
    0
    12.11.2004
    14:03:37
    254976
    E
    5
    Typ
    RSSCR
    0
    : m:15
    5120
    6
    Prg
    RSDBSPBL
    0
    06.11.2003
    20:56:48
    72704
    E
    7
    Prg
    SAPDB__S
    0
    06.11.2003
    20:52:58
    18432
    E
    8
    Typ
    VARID
    0
    12.05.1997
    16:51:30
    5120
    9
    Prg
    %_CSYDB0
    0
    06.11.2003
    20:52:42
    35840
    E
    10
    Prg
    RSDBSPVA
    0
    10.08.2006
    17:09:03
    129024
    E
    11
    Typ
    RSVAMEMKEY
    0
    07.05.1997
    13:07:49
    2048
    12
    Prg
    RSDBSPMC
    0
    10.08.2006
    16:45:25
    78848
    E
    13
    Typ
    DDSHDESCR
    0
    03.09.1997
    03:05:16
    4096
    14
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    15
    Typ
    SPPARAMS
    0
    07.05.1997
    13:10:38
    2048
    16
    Prg
    SAPLICON
    16
    12.11.2004
    13:50:21
    27648
    E
    17
    Prg
    %_CICON
    16
    16.03.2004
    20:13:52
    100352
    E
    18
    Prg
    SAPLSABE
    18
    06.11.2003
    20:53:04
    13312
    E
    19
    Prg
    SAPLSECU
    19
    10.08.2006
    17:27:59
    76800
    E
    20
    Typ
    RSSUBINFO
    0
    14.10.1999
    22:01:03
    3072
    21
    Typ
    RSEXFCODE
    0
    13.08.1997
    12:52:57
    2048
    22
    Prg
    SAPLDSYA
    22
    06.11.2003
    20:53:01
    45056
    E
    23
    Prg
    SAPFSDS1
    22
    06.11.2003
    20:53:24
    52224
    E
    24
    Typ
    TDCLD
    0
    02.11.1998
    09:51:35
    5120
    25
    Prg
    SAPLSDOD
    25
    10.08.2006
    17:29:56
    45056
    E
    26
    Typ
    DOKIL
    0
    12.05.1997
    16:46:17
    3072
    27
    Prg
    SAPCNVE
    27
    06.11.2003
    20:52:58
    8192
    E
    28
    Prg
    SAPLLANG
    28
    06.11.2003
    20:53:03
    10240
    E
    29
    Typ
    T002
    0
    14.02.1998
    10:24:58
    2048
    30
    Prg
    SAPFSPOR
    0
    11.08.2006
    10:35:34
    14336
    E
    31
    Typ
    RSPARINT
    0
    10.04.1995
    09:58:38
    2048
    32
    Prg
    SAPLKGJH
    32
    06.11.2003
    20:53:03
    10240
    E
    33
    Prg
    SAPLSCNT
    33
    06.11.2003
    20:53:04
    30720
    E
    34
    Typ
    DYCBOX
    0
    20.08.1998
    11:16:53
    3072
    35
    Prg
    SAPLSVSM
    35
    10.08.2006
    17:26:59
    29696
    E
    36
    Prg
    SAPLSGUI
    36
    12.11.2004
    13:59:56
    76800
    E
    37
    Prg
    SAPLSTTM
    37
    10.08.2006
    16:44:18
    86016
    E
    38
    Prg
    SAPLSBDC
    38
    10.08.2006
    16:54:12
    45056
    E
    39

    Hi,
    In the screen 370 of your module pool, go to the properties of the field which is having a negative value displayed.. (Ex: Currency fields), we see a text with all underscores. ___________
    Change it to _________V
    Remove last underscore and put V
    Hope it solves your problem.
    Regards
    Sailaja.

  • Abap dump solution

    Dear Team,
    I am facing abap dump  "  TABLE_ILLEGAL_STATEMENT  "   and    " DBIF_REPO_SQL_ERROR  "
    why these dump is comming   and how I search the solution of ABAP Dump on   Service.sap.com
    Plaese help
    Manu

    Hi Manu,
    1) *TABLEILLEGAL_STATEMENT*_
    This is because of user attempted to change the line in the internal table, but no valid cursor exists for the table.
    Possible reasons:
    1. The relevent ABAP/4 statement does not include the addition
    "...INDEX...", although the statement is not
    inside a "LOOP...ENDLOOP" loop processing this table.
    2. The relevent ABAP/4 statement was called from within a
    "LOOP...ENDLOOP" loop after a DELETE.
    Please search in the link https://websmp105.sap-ag.de/notes there should be some corrective note for your problem.
    Regards,
    kanthi Kiran

  • Is SAP Query (SQ01) supported by Visual Composer?

    Do you know if it is possible to easily integrate a query developed in an ABAP backend system via SAP Query (transaction SQ01) in Visual Composer?
    Sergio

    Hi Jorn,
    I must go, but I copy you a Link from a presentation. I don't have the time to control it.
    Hope it helps.
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/2f/741a403233dd5fe10000000a155106/frameset.htm">sap.help.com</a>
    Best Regards,
    marcel

  • Reading Archived Data Through SAP Query Report

    Dear SAP Gurus,
    My client archived their SAP data in a particular year range and all the Z reports have to modified to read these archive data. Normal ABAP reports can be modified to read the archive data without no problem.
    But there are two Z SAP query reports which should be modified the same way so it will be able to read archive data.
    What is the best method for this? Does SAP Query tool provide facility to read archive data? or do I have to append the code?
    Thank you in advance for your help
    Regards,
    Isuru Fernando

    >
    Isuru U Fernando wrote:
    > hi Manthan,
    >
    > Yes I used these FMs and read the data without any problem for normal ABAP reports.
    >
    > But SAP query report is the problem. Is it advisobale to modify the SAP query generated report source code? since it is a system generated report.
    >
    > Regards,
    > Isuru
    No, do not adapt the SAP generated report source. The reason is: every time someone re-generates the query from tx. SQ01 your changes will be lost.
    You could add the functionality Manathan gave you to add to the infoset of said query - but to be honest: in my opinion that is shooting nuclear rockets at flies. Also you run the risk that every change of the infoset (add a join/delete a join) requires adjustment of said coding you applied ... and where will you be then? Fancy repairing the same query over and over again? Try talk sense to your client - go for a Z-report here ...

  • ABAP DUMP duirng generating query

    I have an issue regarding the sap query.We are doing upgrade from ECC5 to 6.0.This problem generates in the new version of TST.
    scenario is the client has DEV system and TST system.
    After you create a query using transaction SQ01 it goes to custom  transaction code which when excuted calls the sap program which generates sap query.When you execute the custom transaction code in DEV sys it is working fine and  the Program is working fine.
    But when you execute SQ01 in TST  and execute it 
    it shows an ABAP dump saying the program AZ===*====is not in the library.(which is behind the custom transaction code)
    In DEV we generated a query and released to TST but the program is not availabale in TST.Will the query be transported from one server to another.
    there is one more to tell
    When we go to transaction SQ01 and create a query it says correct the ranked list 01 first. this happens in both DEV and TST
    do you think this is leading to ABAP dump.
    Please help in fixing this problem as i am new to sap query
    Please it is urgent experts please help.

    Hi,
    The above solution will work if you assign the transaction in one server, If you want this will not work in quality/production boxes when transported the query..the program name will not be the same in all the servers...
    For this. Do the below:
    In SE93, Create a Paramter Transaction
    -> Transaction = Start_report
    -> In default values, give the below details:
         D_SREPOVARI-REPORTTYPE = AQ
         D_SREPOVARI-EXTDREPORT = Name of the Query
         D_SREPOVARI-REPORT = User Group
    Save the transaction..Now if the program is generated with different names in the quality/proudction, this will still work..
    Regards
    Vijay Hebbal

  • Dump in SAP query report

    Dear All,
    I have written some development in SAP Query report.
    The main aim is to assign to own defined parameter par1  combination of version and object-partner (internal order with defined order type).
    The text is following:
    DATA: it_aufk like aufk
          occurs 10 with header line.
       DATA: p-auart like aufk-auart.
       select * from AUFK into table it_aufk
         where AUFNR = coep-parob1+2(12).
      if sy-subrc = 0.
       if coep-versn = '000'.
        par1 = 1.
       elseif coep-versn = 'GR0'.
        par1 = 2.
      endif.
    endif.
      if coep-versn = 0 and ( p-auart = 'V112' or p-auart = 'V114' ) .
        par1 = 1.
      endif.
    I have performed check and generated this info-set successfully.
    Than I have generated program in queries - other function- generate program.
    I execute report and get dump.
    What did I miss?
    With best regards,
    Kamila.

    Category               ABAP Programming Error
    Runtime Errors         CONVT_NO_NUMBER
    ABAP Program           AQICZCO=========QUE_KZHAKEN_01
    Application Component  Not Assigned
    Date and Time          15.12.2011 16:18:35
    Short text
         Unable to interpret "GR0" as a number.
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "AQICZCO=========QUE_KZHAKEN_01" had to be termi
          because it has
         come across a statement that unfortunately cannot be executed.
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
         Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    Error analysis
         An exception occurred that is explained in detail below.
         This exception cannot be caught in the context of the current statement.
         The reason for the exception is:
         The program attempted to interpret the value "GR0" as a number, but
         since the value contravenes the rules for correct number formats,
         this was not possible.
    How to correct the error
        Whole numbers are represented in ABAP as a sequence of numbers, possibl
         with an algebraic sign.
        The following are the possibilities for the representation of floating
        point numbers:
          [algebraic sign][mantissa]E[algebraic sign][exponent]
          [algebraic sign][whole number part].[fraction part]
        For example, -12E+34, +12E-34, 12E34, 12.34
        If the error occurred in your own ABAP program or in an SAP
        program you modified, try to remove the error.
        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:
        "CONVT_NO_NUMBER" " "
        "AQICZCO=========QUE_KZHAKEN_01" or "AQICZCO=========QUE_KZHAKEN_01"
        "START-OF-SELECTION"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
        3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       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.

  • SAP Query format issue (with ABAP list)

    Hi All,
    I had a requirement to remove all unecessary formatting and text from a SAP query report which can be read by a third party software system. We need only Header line and  report data (spaced by Tab).
    I have removed all formatting from the report and changed the output format from "SAP list viewer" to "ABAP list" .
    The issue is that the report shows material number with 12 digits in output but when we download to file then it adds extra six "0" and makes the Material Number field as 18 digit.
    we have already maintained new length as 12 againts the standard length 18 for material number(under field output option)
    Please suggest how to get rid of extra digits generated during downloading.
    Please help,
    Thanks,
    Rohit

    Hi Brad,
    Currently we execute query with SQ01 and from the output screen the user direclty saves the file as "local file..."
    The output format is "abap list". We are able to get the exact format but the only problem is with material number. I cant make changes in the program. Is there a way to download it without changing the 12 character ( as displayed on the report output)
    Thanks for help.
    Rohit

  • Declarations in SAP QUERY generated ABAP Programs

    hi,
    i had created a ABAP Program through ABAP Query (SQ01,SQ02,SQ03) but i have a issue that when i transport it to the PRD server i got the run time error. The Z program which i had created is the copy of the SQ01 generated program and i had done all the includes declarations in this program. but there is a problem that it is consist of the declarations of the structures,quries .
    I want to know is it necessary to always transport the Infoset and user group and the structure which is present in the program generated .
    Please provide me guidelines for this problem  .
    Edited by: ricx .s on Jul 6, 2009 5:31 AM
    Edited by: ricx .s on Jul 6, 2009 8:07 AM

    hi,
    i had copied the program bcoz i want to chekc that it is really necessary to transport the user group and infoset so that it can achieve functionality similar to the SAP QUERY.
    is there any other way without whichi can ahieve the functionality of SAP QUERY generated program and take it into the ABAP Porgram?

  • SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed  with abap dump LOAD_PROGRAM_NOT_FOUND

    Dear Experts,
    Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed  with abap dump LOAD_PROGRAM_NOT_FOUND.
    As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
    Finished Job log
    Job started
    Step 001 started (program RSCOLL00, variant , user ID Bharath)
    Clean_Plan:Cleanup of DB13 Plannings
    Clean_Plan:started by RSDBPREV                       on server
    Clean_Plan:Cleaning up jobs of system DEV
    Clean_Plan:finished
    Job finished
    Failed Job Log
    Job started
    Step 001 started (program RSCOLL00, variant , user ID Bharath)
    Internal session terminated with a runtime error (see ST22).
    Kindly suggest on this..
    Thanks,
    Bharath.

    Dear Divyanshu,
    Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
    |Short text                                                                                        |
    |    Program "RSORA811" not found.                                                                 |
    |What happened?                                                                                    |
    |    There are several possibilities:                                                              |
    |                                                                                                  |
    |    Error in the ABAP Application Program                                                         |
    |                                                                                                  |
    |    The current ABAP program "RSCOLL00" 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 "RSCOLL00" program had to be terminated because the                          |
    |    ABAP processor detected an internal system error.                                             |
    |What can you do?                                                                                  |
    |    Note down which actions and inputs caused the error.                                          |
    |                                                                                                  |
    |                                                                                                  |
    |    To process the problem further, contact you SAP system                                        |
    |    administrator.                                                                                |
    |                                                                                                  |
    |    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
    |    at and manage termination messages, and you can also                                          |
    |    keep them for a long time.                                                                    |
    |Error analysis                                                                                    |
    |    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 "RSORA811".                                                           |
    |                                                                                                  |
    |    However, program "RSORA811" 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                                                                            |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
    |     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
    |    The main program was "RSCOLL00 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 535                                 |
    |    of the (Include) program "RSCOLL00".                                                          |
    |    The program "RSCOLL00" was started as a background job.                                       |
    |    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
    |    Job Initiator.. " bharath"                                                                       |
    |    Job Number..... 18243400
    Kindly check and suggest..
    Thanks,
    Bharath.

  • SAP Query giving dump

    Hi all,
    I have a sap query. When query is called using T.code its working fine and if i execute the query through SQ01 then its giving me dump.
    Message is  Error when attempting to IMPORT object "PARVW".
    It says the object in the dataset had a different type from the target object in the program
    So, I thought the problem may be with the Query Variant. I tried to change the query variant through Sq01->goto->maintain variant
    provided the Variant name(only 1 variant is available). selected radio button VALUES and click on Display or Change button here also its giving the same dump.
    Then I tried to remove the PARVW from selection field in SQ01 in change mode ->Basic list, on the left hand side displays the field and 2 check boxes are there one for LIst field and other of Selection. But the check box for Selection is input disabled.
    Can anyone please let me know how can i avoid the dump.
    I gave a search  in SCN and google, but couldn't find any appropriate solution.

    Query  area  is Global Area (Cross Client).
    I'm able to solve the dump probelm. Now i want to design a selection screen for my query. suppose the selection is as follows in one block
    program selections.
    field1
    field2
    field3
    I want it to be displayed in 2 different blocks block 1 and block2
    General Data selection
    field1
    Program Specific
    field2
    field3
    how can we do this one?
    thanks in advance
    Edited by: Mr A on Mar 5, 2010 8:37 PM
    Edited by: Mr A on Mar 5, 2010 8:40 PM

  • Abap coding in SAP query (SQ01)

    Hi,
    By using the a table like for MSEG if i want to retrieve data for the movement type 101 (receipts from vendor), i can build a query using this table and retrieve data - my problem starts when the system shows individual line items instead of cumulated result as mentioned in the following example.
    Example :-
    for the date 01.07.2007 - i have 10 entries (101 movement) of quantity 1,2,3,4,5,6,7,8,9,10 against a vendor V1. - the query lists all the 10 entries.
    But what is required is the cumulated entry against the vendor like shown below
    vendor    receipt
    V1         55.
    What abap coding should be written (provide the sample code) and the where should it be written in the query transaction SQ01
    Regards,
    M.M

    Hi Magesh,
    If you do not wish to see the detail lines, then you do not need to create them.  Just create the Statistics portion only.
    If you wish to see 'summarized Vendor quantity by day', then you might sort on Vendor first, then posting date second.  Or, vice versa, depending on your business requirement.  I would think that you might also wish to include Material in the sort, since each Material is probably valued differently.
    For more info on creating statistics in SAP Query, refer to
    http://help.sap.com/erp2005_ehp_02/helpdata/en/d2/cb4256455611d189710000e8322d00/frameset.htm
       Regards,
       Bruce

  • SAP Query Custom Field with ABAP Code

    Hi All,
    I have a custom field in my SAP query which has some ABAP code under it. The code finally writes some value to a variable. My question is do i need to explicitly link the variable in the ABAP code to the custom field OR it's done automatically. For some reason i don't see any value for this custom field. Thanks.

    Thanks Sandra

  • ABAP Reports and SAP Query

    Hi Experts,
    I have question regarding ABAP Reports, SAP Query, and Transaction with variant.  How are we securing one the above reports that we assign them through pfcg.  We can secure custom program by custom transaction or define the auth group in S_PROGRAM auth object but in this case we have to assign SA38 in production. is that correct?
    Please help me understand difference between the ABAP reports and SAP query. Is the ABAP reports same as Program or they are different.
    Thanks in advance
    Faisal
    Edited by: Faisal on Jun 30, 2009 11:06 PM

    Hi,
    1) End user security (role matrix coordinate with process team)
    This role Matrix design is most important where we can put restrictions and use SoD.
    2) Secure Table (by auth group)
    Table TDDAT and use of transaction se54 for security tables to right auth Groups. Secure s_tabu_dis, s_tabu_cli.
    3) Secure program (as you said ABAP reports are referred to Program)
    Use of table TPGP and program RSCSAUTH for assignment of groups to Program. SA38 Running of SA38 requires a minimum SUBMIT in user Action. A user having SA38 is dangerous as he/she is now enabled to run any report. Hence protection in Auth Group is needed. Verify each and every program is having authority check statement and Auth Group or not before assigning sa38. As you mentioned its best to avoid SA38 and create CUSTOM TXN for each report.
    (We should also SECURE S_DEVELOP in Production properly along with ur points. Please Note).
    4) Secure some batch jobs roles for batch job
    Secure by s_btch* objects and less access to se36.
    5) Create support roles for cutover activity during Go-live
    That is always needed. Go ahead.
    6) Emergency roles & IT roles for support
    This is very much needed as a role of Mitigation and Fire Fighting for Temporary access. Ensure to enable ur audit parameters in RZ10 (rsau* sm20,RSLG* for sm21). Give emergency access but enable audit via sm19 and get audit reports from sm20 and sm21 immediately after the use of emergency access.
    There are also other auth objects we need to be care ful which is a long list and hope every body ensures that (s_cts,a_admi,s_trans, tables ssm_cust, prgn,t000) etc and a host of others. Besh wishes. Let us know if any issue.
    Regards
    Aveek.

Maybe you are looking for