Exception Reporting failure due to short dump UNCAUGHT_EXCEPTION

Hi everyone,
Exception Reporting called u201CPO Price Deviationu201D failure due to short dump UNCAUGHT_EXCEPTION.
Need your reply on this urgently.
Thank you,
Prasad

Hi Andrew Zhou,
Actually the Exception reporting step failed because there was no applicable data for the selection criteria mentioned in the BEx report. And the data was stuck in the source system. We got it solved my contacting the R/3 cosultant.
I am giving you points for the response. And I would like to know one thing about RSRT if I select "use aggregates" option for a query it is showing aggregates while debuging even though there are no aggregates created on the Cube.
Thank you

Similar Messages

  • Infopackage in process chain failing due to short dump on regular basis.

    HI Experts,
    There is a daily process chain in which one of the element (infopackage) fails due to short dump on regular basis (At least twice in a week) please find the message below
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Short text                                                                               
    SQL error in the database when accessing a table.
    And in job log it is showing ARFCSTATE = SYSFAIL
    We are able to resolve it just manual update and the process goes fine no issues but my question here is what is the exact reason for this and how to resolve it permanently or decrease the frequency of the error.
    Please if any one can tell the root cause and the solution to avoid the issue in future on regular basis.
    and also can any one elaborate what is ARFCSTATE = SYSFAIL,for trfc check we don't have access to SM58 in ECC side
    and trfc is fine in bw side
    Appreciate for not giving the general solutions like repeated solutions already posted in SDN
    with regards,
    musai

    You can contact your BASIS person he can help you reg table space issue. it says used space is 98% and free space is 1.03%.
    ask your basis to set a threshold to check the space and send a mail notification to all daily regarding the space allocation and utilization.
    ARFCSTATE = SYSFAIL means the TRFC did not processed properly to the BW system from source.
    Monitoring object with information about tRFC and qRFC calls that are waiting to be executed in this system; after they have been executed, they are deleted from table ARFCRSTATE.
    Are there any hung TRFCs which are not processed to BW side. have you checked it
    first check
    load monitor -- menu -- environment -- job overview -- status of job(is it finsihed or not?) - check the job log -- ther try to find out the hung TRFc
    press find --tyep "sysfail" ok -- it will display all the hung or fialed TRFCs which are not processed to BW system.
    if you find the hung TID with respect to your load.. next goto SM58 trasaction to process the trfcs manually or use the load monitor menu -- environment -- transaction RFC -- source sys -- it will take you to same SM58 screen -- click F8 it will display the hung TRFc in that duration.
    select the TRFc and click on F6 to process them manually.
    also check the loackwaits anddead locks in ST04/DB6COCKPIT.( ask basis to check) if any dead locks are there they will take care of it.
    check for short dumps in st22 if any and try to analyse.
    Check the SM21 system logs.

  • How to catch the error if an RFC fails due to short dump

    Hi All,
      I was calling the RFC Function module in parallel processing depends on the number of work processors available. I am getting the return message from the Function module using the perform statement
       PERFORMING task_return ON END OF TASK
    But I am not able to catch the errors if the RFC has been terminated due to the dump or manually killing the RFC while running.
    I need how to handle the RFC if the call has been terminated due to the dump or system failure. Does the RFC return the sy-subrc at this time or can we able to catch the error in any other way.
    Thanks & regards,
    Vijay

    Hello Vijay,
    If you're calling RFC from outside SAP using the OCX-SAPFunctions-Library, then you can catch the dump or any other exception occuring in your SAP-Function.
    Assuming that, objRFCFunc is the RFC-Function you can get the Excepetion-Code through objRFCFunc.Exception.
    It returns a String. If the error was a dump, the String is "SYSTEM_FAILURE". If it is a "regular" Exception you'll get the Exceptioncode. E.g. "NO_DATA_FOUND".
    If you need any sample code e.g. VBA-code for use in Office-Applications, let me know.
    regards
    Sven

  • Any way to catch exceptions from asynchronous call that short dumps?

    Hi,
    We have a requirement for a program that we know will occasionally short dump under normal conditions. We want to use an asynchronous call to let it plow ahead. To that end I've created a test program that calls a divide by zero func that short dumps. It tests fine because it proceeds afterward. Better yet would be a way to capture some information from the function where the dump happens and raise it to the calling program. Any ideas?
    Thanks,
    Doug
    Example:
    REPORT  ZJUNK2
    data: junkdone TYPE c VALUE space,
    write: / 'before'.
    CALL FUNCTION 'ZJUNK2'
      STARTING NEW TASK 'z_junktask'
      PERFORMING junk ON END OF TASK
          EXCEPTIONS
             communication_failure = 1
             system_failure        = 2
             other_exception = 3.
    Receive remaining asynchronous replies
      wait until junkdone = 'X'.
    write: / 'after'.
    FORM junk  USING taskname.
    RECEIVE RESULTS FROM FUNCTION 'ZJUNK2'
          EXCEPTIONS
             communication_failure = 1
             system_failure        = 2
             other_exception = 3.
      junkdone = 'X'.
    ENDFORM.
    FUNCTION ZJUNK2.
    ""Local Interface:
    data: i type i.
    i = 1 / 0.
    ENDFUNCTION.

    Hey Doug.  You need to catch the class exception cx_root in your function, then pass back the message.  This will catch a lot of system exceptions, but probably not all.
    DATA: junkdone TYPE c VALUE space.
    DATA: lv_message TYPE char255.
    WRITE: / 'before'.
    CALL FUNCTION 'ZJUNK2'
      STARTING NEW TASK 'z_junktask'
      PERFORMING junk ON END OF TASK
      EXCEPTIONS
        communication_failure = 1
        system_failure        = 2
        other_exception       = 3.
    * Receive remaining asynchronous replies
    WAIT UNTIL junkdone = 'X'.
    WRITE: / 'after'.
    IF lv_message IS NOT INITIAL.    "<-- Check for error and write message
      WRITE:/ lv_message.
    ENDIF.
    *&      Form  junk
    FORM junk USING taskname.
      RECEIVE RESULTS FROM FUNCTION 'ZJUNK2'
           IMPORTING
                e_message = lv_message   "<-- Import the message
           EXCEPTIONS
                communication_failure = 1
                system_failure = 2
                other_exception = 3.
      junkdone = 'X'.
    ENDFORM.                    "junk
    FUNCTION zjunk2.
    *"*"Local Interface:
    *"  EXPORTING
    *"     VALUE(E_MESSAGE) TYPE  CHAR255
      DATA: lo_exception TYPE REF TO cx_root.
      DATA: i TYPE i.
      TRY.
          i = 1 / 0.
        CATCH cx_root INTO lo_exception.
          e_message = lo_exception->get_text( ).
      ENDTRY.
    ENDFUNCTION.
    Regards,
    Rich Heilman

  • Load getting failed due to short dump

    Hi All,
    Process Chain is getting failed due to following short dump Include Report LFZI_CA_PCA_DERIVATIONSU37 not found. Please suggest on rectifying this dump. Its a delta load.
    Regards,
    Asim

    Hi All
    As requested please find details short dump below. And datasource name is this GECPC_GLPCP and its extractor is ZPCC_V_GLPCP.
    Short text
       Syntax error in program "SAPLZFI_CA_PCA_DERIVATIONS ".
    hat happened?
       Error in the ABAP Application Program
       The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
        because it has
       come across a statement that unfortunately cannot be executed.
       The following syntax error occurred in program "SAPLZFI_CA_PCA_DERIVATIONS " in
        include "LZFI_CA_PCA_DERIVATIONSUXX " in
       line 77:
       "INCLUDE report "LZFI_CA_PCA_DERIVATIONSU37" not found"
       The include has been created and last changed by:
       Created by: "SAP* "
       Last changed by: "SAP* "
       Error in the ABAP Application Program
       The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
        because it has
       come across a statement that unfortunately cannot be executed.
    What can you do?
        Please eliminate the error by performing a syntax check
        (or an extended program check) on the program "SAPLZFI_CA
        You can also perform the syntax check from the ABAP Edito
        If the problem persists, proceed as follows:
        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 lo
        at and manage termination messages, and you can also
       keep them for a long time.
    Error analysis
        The following syntax error was
        "INCLUDE report "LZFI_CA_PCA_DE
    How to correct the error
        Probably the only way to elimin
        If you cannot solve the problem
        notification to SAP, include th
        1. The description of the curre
           To save the description, cho
        (Unconverted)".
        2. Corresponding system log
    Display the system log by callin
    Restrict the time interval to 10
    ter the short dump. Then choose "
    nconverted)".
    If the problem occurs in a probl
    ogram: The source code of the pro
    In the editor, choose "Utilities
    ilities->Upload/Download->Downloa
    Details about the conditions und
    tions and input led to the error.
    Information on where terminated
        Termination occurred in the ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" - in
         "START_ROUTINE".
        The main program was "RSBATCH_EXECUTE_PROZESS ".
        In the source code you have the termination point in line 102
        of the (Include) program "ZFICA_DERIVE_PCA_OBJECTS_S".
        The program "GP9IQHCDEPFH201E24O25IAYXXW" was started as a background job.
        Job Name....... "BIDTPR_6726959_1"
        Job Initiator.. "ALEREMOTE"
        Job Number..... 17271800
    Line  SourceCde
       72 ASSIGN 'L_DERIVE_CHRT_ACCTS-UPD_CHRT_AC
       73 assign (<derive_chrt_accts_field>) to
       74 IF <derive_chrt_accts> IS ASSIGNED.
       75   zzi_attributes_upd-chrt_accts_upd = '
       76 ENDIF.
       77 zzi_attributes_upd-/bic/gactivity_upd
       78 zzi_attributes_upd-/bic/gfactv_upd
       79 zzi_attributes_upd-/bic/gglobacct_upd
       80 zzi_attributes_upd-/bic/ggforacc_upd
       81 zzi_attributes_upd-/bic/ggrracc_upd
       82 zzi_attributes_upd-/bic/ggra_code_upd
       83 zzi_attributes_upd-/bic/gsegmtion_upd
       84 zzi_attributes_upd-/bic/ggaapflg_upd
       85 zzi_attributes_upd-/bic/gsub_item_upd
       86 zzi_attributes_upd-/bic/gsegmnt_upd
       87 zzi_attributes_upd-/bic/gacctgrp_upd
       88 zzi_attributes_upd-comp_code_details_up
       89 zzi_attributes_upd-gbfi0600_upd
       90 zzi_attributes_upd-/bic/zaccsuf_upd
       91 zzi_attributes_upd-/bic/gconunit_upd
       92 zzi_attributes_upd-/bic/gtpunit_upd
       93 *--------------------------------------
       94 * Store a copy of the source fields if
       95 *--------------------------------------
       96 MOVE-CORRESPONDING <source_fields> TO z
       97 CLEAR zze_attributes.
    Runtime Errors         SYNTAX_ERROR
    Date and Time          04.08.2014 17:27:39
        98 *----------------------------------------------------------------------*
        99 * Derive all PCA fields for reporting
       100 *----------------------------------------------------------------------*
       101
    >>>>> CALL FUNCTION 'ZFI_CA_DERIVE_PCA_ATTRIBUTESII'
       103   EXPORTING
       104     i_zfi_ca_pca_attributes     = zzi_attributes
       105     i_zfi_ca_pca_attributes_upd = zzi_attributes_upd
       106     msgty                       = 'I'
       107     recno                       = <source_fields>-record
       108   IMPORTING
       109     e_zfi_ca_pca_attributes     = zze_attributes
       110   TABLES
       111     monitor_recno               = lt_monitor_recno.
       112
       113 *----------------------------------------------------------------------*
       114 * On the recurrsive load delete entries where the data is the same
       115 *----------------------------------------------------------------------*
       116 IF zzg_realignment_run = 'X'.
       117   IF  zzi_attributes = zze_attributes.
       118     DELETE  source_package INDEX la_tabix.
       119   ELSE.
       120     MOVE-CORRESPONDING zze_attributes TO <source_fields>.
       121   ENDIF.
    SY-SUBRC 0
    SY-INDEX 3
    SY-TABIX 1
    SY-DBCNT 10
    SY-FDPOS 0
    SY-LSIND 0
    SY-PAGNO 0
    SY-LINNO 1
    SY-COLNO 1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE Execute Batch Proces
    SY-MSGTY E
    SY-MSGID R7
    SY-MSGNO 057
    SY-MSGV1 ZBAL_LC
    SY-MSGV2 A
    SY-MSGV3
    SY-MSGV4
    SY-MODNO 0
    SY-DATUM 20140804
    SY-UZEIT 172720
    SY-XPROG SAPCNVE
    SY-XFORM CONVERSION_EXIT
    No.   Ty.          Program                             Include                             Line
          Name
        8 FUNCTION     GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
          START_ROUTINE
        7 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
          LCL_TRANSFORM=>START_ROUTINE
        6 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         GP9IQHCDEPFH201E24O25IAYXXW          1299
          LCL_TRANSFORM=>EXECUTE
        5 METHOD       CL_RSTRAN_TRFN_CMD============CP    CL_RSTRAN_TRFN_CMD============CM005    70
          CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
        4 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM00Q    93
          CL_RSBK_PROCESS=>PROCESS_REQUEST
       3 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM002    13
          CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
        2 FUNCTION     SAPLRSBATCH                         LRSBATCHU13                           437
          RSBATCH_EXECUTE_PROCESS
        1 EVENT        RSBATCH_EXECUTE_PROZESS             RSBATCH_EXECUTE_PROZESS               374
          START-OF-SELECTION
    REQUEST
        DTPR_1FR9TKO2U6M616ATG9C2EYKRH
        455553453544353433345434345454
        4402F16294BF256D61614793259B28
        000000000000000000000000000000
        000000000000000000000000000000
    DATAPACKID
        000001
        333333
        000001
        000000
        000000
    MONITOR
        Table[initial]
    SOURCE_PACKAGE
        3000000001012P2013K4AU0ACD 2013005          00                                               0
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013001000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013002000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013003000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
        3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
        300000000101202013B415013402013004000000000000000000000000000000000000000000000000000000000000
      00000000000000000000000000000000000
      00000000000000000000000000000000000
      33333333333335333343453444233333332
      300000000101202013B4150134020130050
      00000000000000000000000000000000000
      00000000000000000000000000000000000
      Table IT_110723[600000x1144]
      {A:114*\TYPE=%_T00003S00000115O0000
      Table reference: 3570
      TABH+  0(20) = 90A161080000000060C1
      TABH+ 20(20) = F20D000083B00100C027
      TABH+ 40(16) = 03730000242D00000400
      store        = 0x90A1610800000000
      ext1         = 0x60C1190C00000000
      shmId        = 0     (0x00000000)
      id           = 3570  (0xF20D0000)
      label        = 110723 (0x83B00100)
      fill         = 600000 (0xC0270900)
      leng         = 1144  (0x78040000)
      loop         = 128   (0x80000000)
      xtyp         = ROL.115.11556
      occu         = 4     (0x04000000)
      accKind      = 1     (ItAccessStand
      idxKind      = 0     (ItIndexNone)
      uniKind      = 2     (ItUniNo)
      keyKind      = 1     (default)
      cmpMode      = 8     (cmpManyEq)
      occu0        = 1
      stMode       = 0
      groupCntl    = 0
      rfc          = 0
      unShareable  = 0
      mightBeShared = 1
      sharedWithShmTab = 0
      isShmLockId  = 0
      isUsed       = 1
      isCtfyAble   = 1
      hasScndKeys  = 0
      hasRowId     = 0
      scndKeysOutdated = 0
      scndUniKeysOutdated = 0
      ----- Shareable Table Header Data -----
      tabi         = 0xB008190C00000000
      pgHook       = 0x404CE73B00000000
      idxPtr       = 0x0000000000000000
      id           = 61767 (0x47F10000)
      shmTabhSet   = 0x0000000000000000
      refCount     = 1     (0x01000000)
      tstRefCount  = 0     (0x00000000)
      lineAdmin    = 606204 (0xFC3F0900)
      lineAlloc    = 600004 (0xC4270900)
      shmVersId    = 0     (0x00000000)
      shmRefCount  = 2     (0x02000000)
      rowId        = 18446744073709551615
      scndKeyAdmin = 0x0000000000000000
      ----- 1st level extension part --------
      regHook      = 0xC8C0190C00000000
      collHook     = 0x0000000000000000
      ext2         = 0x0000000000000000
    RI-CLUSTR
       0
       00
       00
    ZE_ATTRIBUTES
                         00000
       22222222222222222233333
       00000000000000000000000
       00000000000000000000000
       00000000000000000000000
    ZI_ATTRIBUTES
       AU0A    070221000020130
       45342222333333333333333
       15010000070221000020130
       00000000000000000000000
       00000000000000000000000
    ZI_ATTRIBUTES_UPD
       XXXXX XXXXXX  XX XXXX
       55555255555522552555522
       88888088888800880888800
       00000000000000000000000
       00000000000000000000000
    SOURCE_FIELDS>-RECORD
       1
       0000
       1000
    T_MONITOR_RECNO
       Table[initial]
    ZG_REALIGNMENT_RUN
       2
    Regards,
    Asim
    GECPC_GLPCP   

  • Short dump while executing report group.

    Hi,
    We are upgrading to ECC6.0 from 4.6C
    Now while testing the report group i got short dump.
    This is due to to the 'Exception condition "LOAD_PROBLEMS" raised.'
    Error analysis
        A RAISE statement in the program "SAPLSLDB" raised the exception
        condition "LOAD_PROBLEMS".
        Since the exception was not intercepted by a superior
        program, processing was terminated.
        Short description of exception condition:
        For detailed documentation of the exception condition, use
        Transaction SE37 (Function Library). You can take the called
        function module from the display of active calls.
    Function module 'SELOPTS_AND_PARAMS' in this that statement was there.
    Can some one help me out. what i have to do further.
    Thanks in advance.
    Regards,
    Deepak.

    Hi Hemanth,
    Actually what I analysed is what ever the exception raised due to this sy-subrc that exception i think the superior program is not receiving. I think due to this it is going for short dump.
    Let me know if you have any idea further.
    Thanks,
    Deepak.
    Message was edited by:
            Deepak Kudaravalli

  • REGARDING ALV REPORT SHORT DUMP

    hI ALL,
    IAM GETTING FOR THE FOLLOWING CODE,
    PLEASE WHY THE ERROR IN ECC 6.0
    TABLES AND DATA DECLARATION.
    *TABLES: mara,makt.",marc.
    data syrepid like sy-repid.
    data sydatum(10). " LIKE sy-datum.
    data sypagno(3) type n.
    WHEN USING MORE THAN ONE TABLE IN ALV WE NEEED TO DECLARE THE TYPE
    GROUP (TYPE-POOLS--------->SLIS)
    type-pools : slis.
    INTERNAL TABLE DECLARATION.
    INTERNAL TABLE TO HOLD THE VALUES FROM THE MARA TABLE
    data: begin of t_mara occurs 0,
    matnr like mara-matnr,
    meins like mara-meins,
    mtart like mara-mtart,
    matkl like mara-matkl,
    end of t_mara.
    INTERNAL TABLE TO HOLD THE CONTENTS FROM THE EKKO TABLE
    data : begin of t_marc occurs 0,
    matnr like mara-matnr,
    werks like marc-werks,
    minbe like marc-minbe.
    data: end of t_marc.
    INTERNAL TABLE TO HOLD THE VALUES FROM MAKT TABLE.
    data : begin of t_makt occurs 0,
    matnr like mara-matnr,
    maktx like makt-maktx,
    spras like makt-spras,
    end of t_makt.
    INTERNAL TABLE WHICH ACTUALLY MERGES ALL THE OTHER INTERNAL TABLES.
    data: begin of itab1 occurs 0,
    matnr like mara-matnr,
    meins like mara-meins,
    maktx like makt-maktx,
    spras like makt-spras,
    werks like marc-werks,
    minbe like marc-minbe,
    end of itab1.
    THE FOLLOWING DECLARATION IS USED FOR DEFINING THE FIELDCAT
    AND THE LAYOUT FOR THE ALV.
    HERE AS slis_t_fieldcat_alv IS A INTERNAL TABLE WITHOUT A HEADER LINE
    WE EXPLICITELY DEFINE AN INTERNAL TABLE OF THE SAME STRUCTURE AS THAT
    OF slis_t_fieldcat_alv BUT WITH A HEADER LINE IN THE DEFINITION.
    THIS IS DONE TO MAKE THE CODE SIMPLER.
    OTHERWISE WE MAY HAVE TO DEFINE THE STRUCTURE AS IN THE NORMAL SAP
    PROGRAMS.
    IN THE FIELDCATALOG TABLE WE ACTUALLY PASS THE FIELDS FROM ONE OR
    MORE TABLES AND CREATE A STRUCTURE
    IN THE LAYOUT STRUCTURE WE BASICALLY DEFINE THE FORMATTING OPTIONS
    LIKE DISPLAY IN THE ZEBRA PATTERN ,THE HOTSPOT OPTIONS ETC.
    data: fieldcatalog type slis_t_fieldcat_alv with header line,
    fieldlayout type slis_layout_alv.
    DECLARING THE EVENTTABLE INTERNL TABLE FOR USING EVENTS LIKE
    TOP-OF-PAGE ETC.
    data : eventstab type slis_t_event with header line.
    DECLARING AN INTERNAL TABLE TO HOLD THE DATA FOR THE TOP-OF-PAGE
    data : heading type slis_t_listheader with header line.
    data : heading1 type slis_t_listheader with header line.
    data : heading2 type slis_t_listheader with header line.
    data : heading3 type slis_t_listheader with header line.
    data : heading4 type slis_t_listheader with header line.
    data : heading5 type slis_t_listheader with header line.
    data : heading6 type slis_t_listheader with header line.
    data : heading7 type slis_t_listheader with header line.
    data : heading8 type slis_t_listheader with header line.
    STRUCTURE TO PASS THE COLOR ATTRIBUTES FOR DISPLAY.
    data : colorstruct type slis_coltypes.
    INITIALIZATION. *
    initialization.
    syrepid = sy-repid.
    sypagno = sy-pagno.
    clear fieldcatalog.
    START-OF-SELECTION. *
    start-of-selection.
    SUBROUTINE TO POPULATE THE COLORSTRUCT
    perform fill_colorstruct using colorstruct.
    SUBROUTINE TO POPULATE THE FIELDS OF THE FIELD CATALOGUE
    perform populate_fieldcatalog.
    SUBROUTINE TO SELECT DATA FROM VARIOUS TABLES AND POPULATE IT IN THE
    INTERNAL TABLE.
    perform selectdata_and_sort.
    SUBROUTINE TO POPULATE THE LAYOUT STRUCTURE.
    perform populate_layout using fieldlayout.
    SUBROUTINE TO CALL THE FUNCTION MERGE TO ENSURE PROPER DISPLAY.
    perform merge_fieldcatalog.
    SUBROUTINE TO POPULATE THE EVENTSTAB.
    perform fill_eventstab tables eventstab.
    SUBROUTINE TO POPULATE THE HEADING TABLES.
    perform fill_headingtable tables heading using 'HEADING'.
    perform fill_headingtable tables heading1 using 'HEADING1'.
    perform fill_headingtable tables heading2 using 'HEADING2'.
    perform fill_headingtable tables heading3 using 'HEADING3'.
    perform fill_headingtable tables heading4 using 'HEADING4'.
    perform fill_headingtable tables heading5 using 'HEADING5'.
    perform fill_headingtable tables heading6 using 'HEADING6'.
    perform fill_headingtable tables heading7 using 'HEADING7'.
    perform fill_headingtable tables heading8 using 'HEADING8'.
    SUBROUTINE TO DISPLAY THE LIST.
    perform display_alv_list.
    FORMS
    IN THIS SUBROUTINE WE POPULATE THE FIELDCATALOG TABLE WITH THE NAMES
    OF THE TABLE,FIELDNAME,WHETHER IT IS KEY FIELD OR NOT,HEADING AND
    COLUMN JUSTIFICATION.
    form populate_fieldcatalog.
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'MATNR' 'X' .
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'MEINS' ' '.
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'MAKTX' ' ' .
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'MTART' ' ' .
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'MATKL' ' ' .
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'SPRAS' ' ' .
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'WERKS' ' ' .
    perform fill_fields_of_fieldcatalog tables fieldcatalog
    using 'ITAB1' 'MINBE' ' ' .
    endform. " POPULATE_FIELDCATALOG
    FORM FILL_FIELDS_OF_FIELDCATALOG *
    --> FIELDCATALOG *
    --> P_TABNAME *
    --> P_FIELDNAME *
    --> P_KEY *
    --> P_KEY *
    form fill_fields_of_fieldcatalog tables fieldcatalog
    structure fieldcatalog
    using p_tabname
    p_fieldname
    p_key.
    p_no_out.
    fieldcatalog-tabname = p_tabname.
    fieldcatalog-fieldname = p_fieldname.
    fieldcatalog-key = p_key.
    fieldcatalog-emphasize = '1234'.
    *fieldcatalog-no_out = p_no_out.
    append fieldcatalog.
    endform. " FILL_FIELDSOFFIELDCATALOG
    FORM POPULATE_LAYOUT *
    --> FIELDLAYOUT *
    form populate_layout using fieldlayout type slis_layout_alv.
    fieldlayout-f2code = '&ETA' .
    fieldlayout-zebra = 'X'.
    FOR THE WINDOW TITLE.
    fieldlayout-window_titlebar = 'ALV with Events'.
    fieldlayout-colwidth_optimize = 'X'.
    fieldlayout-no_vline = ' '.
    *fieldlayout-no_input = 'X'.
    fieldlayout-confirmation_prompt = ''.
    fieldlayout-key_hotspot = 'X'.
    This removes the column headings if the flag is set to 'X'
    fieldlayout-no_colhead = ' '.
    *fieldlayout-hotspot_fieldname = 'MAKTX'.
    fieldlayout-detail_popup = 'X'.
    fieldlayout-coltab_fieldname = 'X'.
    endform. " POPULATE_LAYOUT
    FORM SELECTDATA_AND_SORT *
    form selectdata_and_sort.
    select matnr meins mtart matkl from mara
    into corresponding fields of t_mara
    up to 500 rows .
    select matnr maktx spras from makt
    into corresponding fields of t_makt
    where matnr = t_mara-matnr and
    spras = sy-langu.
    select matnr werks minbe from marc
    into corresponding fields of t_marc
    where matnr = t_mara-matnr.
    append t_marc.
    endselect.
    append t_makt.
    endselect.
    append t_mara.
    endselect.
    perform populate_itab1.
    sort itab1 by matnr.
    endform. " SELECTDATA_AND_SORT
    FORM MERGE_FIELDCATALOG *
    form merge_fieldcatalog.
    call function 'REUSE_ALV_FIELDCATALOG_MERGE'
    exporting
    i_program_name = syrepid
    i_internal_tabname = 'ITAB1'
    i_structure_name = 'COLORSTRUCT'
    I_CLIENT_NEVER_DISPLAY = 'X'
    i_inclname = syrepid
    changing
    ct_fieldcat = fieldcatalog[]
    exceptions
    inconsistent_interface = 1
    program_error = 2
    others = 3.
    endform. " MERGE_FIELDCATALOG
    IN THIS FUNCTION THE MINIMUM PARAMETERS THAT WE NEED TO PASS IS AS
    FOLLOWS:-
    i_callback_program --> CALLING PROGRAM NAME
    i_structure_name --> STRUCTURE NAME.
    is_layout --> LAYOUT NAME.
    it_fieldcat ---> BODY OF THE FIELD CATALOGUE INTERNAL TABLE
    form display_alv_list.
    call function 'REUSE_ALV_LIST_DISPLAY'
    exporting
    I_INTERFACE_CHECK = ' '
    i_callback_program = syrepid
    I_CALLBACK_PF_STATUS_SET = ' '
    I_CALLBACK_USER_COMMAND = ' '
    i_structure_name = 'ITAB1'
    is_layout = fieldlayout
    it_fieldcat = fieldcatalog[]
    IT_EXCLUDING =
    IT_SPECIAL_GROUPS =
    IT_SORT =
    IT_FILTER =
    IS_SEL_HIDE =
    I_DEFAULT = 'X'
    THE FOLLOWING PARAMETER IS SET AS 'A' INORDER TO DISPLAY THE STANDARD
    TOOL BAR
    i_save = 'A'
    IS_VARIANT = ' '
    it_events = eventstab[]
    IT_EVENT_EXIT =
    IS_PRINT =
    I_SCREEN_START_COLUMN = 0
    I_SCREEN_START_LINE = 0
    I_SCREEN_END_COLUMN = 0
    I_SCREEN_END_LINE = 0
    IMPORTING
    E_EXIT_CAUSED_BY_CALLER =
    ES_EXIT_CAUSED_BY_USER =
    tables
    t_outtab = itab1
    exceptions
    program_error = 1
    others = 2.
    endform. " DISPLAY_ALV_LIST
    *& Form POPULATE_ITAB1
    text
    --> p1 text
    <-- p2 text
    form populate_itab1.
    loop at t_mara.
    loop at t_makt where matnr = t_mara-matnr.
    loop at t_marc where matnr = t_mara-matnr.
    move-corresponding t_mara to itab1.
    move-corresponding t_makt to itab1.
    move-corresponding t_marc to itab1.
    append itab1.
    endloop.
    endloop.
    endloop.
    endform. " POPULATE_ITAB1
    *& Form FILL_EVENTSTAB
    text
    -->P_EVENTSTAB text *
    form fill_eventstab tables p_eventstab structure eventstab.
    WHEN THE FOLLOWING FUNCTION IS CALLED THE SYSTEM POPULATES THE
    INTERNAL TABLE EVENTSTAB WITH A LIST OF EVENTS NAME.
    AS SHOWN BELOW WHEN USING I_LIST_TYPE = 0 THE FUNCTION RETURNS 14
    EVENTS NAME.
    call function 'REUSE_ALV_EVENTS_GET'
    exporting
    i_list_type = 0
    importing
    et_events = p_eventstab[]
    exceptions
    list_type_wrong = 1
    others = 2.
    BY CALLING THE ABOVE FUNCTION WE FIRST POPULATE THE EVENTSTAB WITH
    THE PREDEFINED EVENTS AND THEN WE MOVE THE FORM NAME AS SHOWN BELOW.
    WE ASSIGN A FORM NAME TO THE EVENT AS REQUIRED BY THE USER.
    FORM NAME CAN BE ANYTHING.THE PERFORM STATEMENT FOR THIS FORM
    IS DYNAMICALY CALLED.
    read table p_eventstab with key name = slis_ev_top_of_page.
    if sy-subrc = 0 .
    move 'TOP_OF_PAGE' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_top_of_coverpage.
    if sy-subrc = 0 .
    move 'TOP_OF_COVERPAGE' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_end_of_coverpage .
    if sy-subrc = 0 .
    move 'END_OF_COVERPAGE' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_foreign_top_of_page.
    if sy-subrc = 0 .
    move 'FOREIGN_TOP_OF_PAGE' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_foreign_end_of_page.
    if sy-subrc = 0 .
    move 'FOREIGN_END_OF_PAGE' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_list_modify.
    if sy-subrc = 0 .
    move 'LIST_MODIFY' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_top_of_list.
    if sy-subrc = 0 .
    move 'TOP_OF_LIST' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_end_of_page.
    if sy-subrc = 0 .
    move 'END_OF_PAGE' to p_eventstab-form.
    append p_eventstab.
    endif.
    read table p_eventstab with key name = slis_ev_end_of_list .
    if sy-subrc = 0 .
    move 'END_OF_LIST' to p_eventstab-form.
    append p_eventstab.
    endif.
    endform. " FILL_EVENTSTAB
    *& Form FILL_HEADINGTABLE
    text
    -->P_HEADING text *
    form fill_headingtable tables p_heading structure heading
    using tablename.
    case tablename.
    when 'HEADING'.
    p_heading-typ = 'H'.
    concatenate
    ' REPORT NAME:-' syrepid
    ' ABB Industry Pte Ltd' into p_heading-info.
    append p_heading.
    write sy-datum using edit mask '__/__/____' to sydatum.
    concatenate
    ' DATE:-' sydatum ' USER: ' sy-uname 'PAGE NO:' sypagno
    into p_heading-info.
    append p_heading.
    when 'HEADING1'.
    p_heading-typ = 'H'.
    p_heading-info = 'TOP-OF-COVER-PAGE'.
    append p_heading.
    when 'HEADING2'.
    p_heading-typ = 'H'.
    p_heading-info = 'END-OF-COVER-PAGE'.
    append p_heading.
    when 'HEADING3'.
    p_heading-typ = 'H'.
    p_heading-info = 'FOREIGN-TOP-OF-PAGE'.
    append p_heading.
    when 'HEADING4'.
    p_heading-typ = 'H'.
    p_heading-info = 'FOREIGN-END-OF-PAGE'.
    append p_heading.
    WHEN 'HEADING5'.
    P_HEADING-TYP = 'H'.
    P_HEADING-INFO = 'LIST-MODIFY'.
    APPEND P_HEADING.
    when 'HEADING6'.
    p_heading-typ = 'H'.
    p_heading-info = 'END-OF-PAGE'.
    append p_heading.
    when 'HEADING7'.
    p_heading-typ = 'H'.
    p_heading-info = 'END-OF-LIST'.
    append p_heading.
    when 'HEADING8'.
    p_heading-typ = 'H'.
    p_heading-info = 'TOP-OF-LIST'.
    append p_heading.
    endcase.
    endform. " FILL_HEADINGTABLE
    FORM TOP_OF_PAGE *
    form top_of_page.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading[]
    exceptions
    others = 1.
    endform.
    *& Form FILL_COLORSTRUCT
    text
    -->P_COLORSTRUCT text *
    form fill_colorstruct using p_colorstruct type slis_coltypes .
    p_colorstruct-heacolfir-col = 6.
    p_colorstruct-heacolfir-int = 1.
    p_colorstruct-heacolfir-inv = 1.
    endform. " FILL_COLORSTRUCT
    FORM TOP_OF_COVERPAGE *
    form top_of_coverpage.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading1[]
    exceptions
    others = 1.
    endform.
    FORM END_OF_COVERPAGE *
    form end_of_coverpage.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading2[]
    exceptions
    others = 1.
    endform.
    FORM FOREIGN_TOP_OF_PAGE *
    form foreign_top_of_page.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading3[]
    exceptions
    others = 1.
    endform.
    FORM FOREIGN_END_OF_PAGE *
    form foreign_end_of_page.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading4[]
    exceptions
    others = 1.
    endform.
    FORM LIST_MODIFY *
    *FORM LIST_MODIFY.
    CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
    IT_LIST_COMMENTARY = HEADING5[]
    EXCEPTIONS
    OTHERS = 1.
    *ENDFORM.
    FORM END_OF_PAGE *
    form end_of_page.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading6[]
    exceptions
    others = 1.
    endform.
    FORM END_OF_LIST *
    form end_of_list.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading7[]
    exceptions
    others = 1.
    endform.
    FORM TOP_OF_LIST *
    form top_of_list.
    call function 'REUSE_ALV_COMMENTARY_WRITE'
    exporting
    it_list_commentary = heading8[]
    exceptions
    others = 1.
    endform.
    SHORT DUMP IS
    This error may occur if
    - You address a typed field symbol before it has been set with
       ASSIGN
    - You address a field symbol that pointed to the line of an
       internal table that was deleted
    - You address a field symbol that was previously reset using
       UNASSIGN or that pointed to a local field that no
       longer exists
    - You address a global function interface, although the
       respective function module is not active - that is, is
       not in the list of active calls. The list of active calls
       can be taken from this short dump.
    PLEASE GIVE ME ANSWER.
    REGARDS

    HI I MADE SOME CHANGES TO UR CODE...
    RUN IF THIS IS THE REQ ...
    IN SELECT QUERIES OF RETRIEVING DATA..
    form selectdata_and_sort.
      select matnr meins mtart matkl from mara
      into corresponding fields of TABLE t_mara
    WHERE MATNR = T_MARA-MATNR.
      up to 200 rows .
      IF SY-SUBRC = 0.
        MESSAGE I001 WITH ' DATA RET FROM MARA'.
      ENDIF.
      IF T_MARA[] IS NOT INITIAL .
    select
           matnr
           maktx
           spras
           From
           makt
           into corresponding fields of TABLE t_makt
            FOR ALL ENTRIES IN T_MARA
           where matnr = t_mara-matnr and
           spras = sy-langu.
      ENDIF.
      IF SY-SUBRC = 0 .
      MESSAGE I001 WITH ' DATA RET FROM MAKT'.
      ENDIF.
      IF T_MAKT[] IS NOT INITIAL.
          select matnr
                 werks
                 minbe
                 from marc
                 into corresponding fields of  TABLE t_marc
                 FOR ALL ENTRIES IN
                 T_MAKT where matnr = t_maKT-matnr.
        ENDIF.
    ENDFORM.                    "selectdata_and_sort
    JUST TRY THIS CODE..

  • BOBJ report failed in SAP 6.0.   "/CRYSTAL/OSQL_EXECUTE".*. short dump in S

    We have a set of crystal reports that run correctly in SAP4.6C. During the upgarde, we are unable to run any report against the new sap 6.0 but the same report run correctly against SAP4.6C. Whenever we run the bobj report, a short dump is created in SAP ECC6.0 as follow:
    Information on where terminated
        Termination occurred in the ABAP program "/CRYSTAL/OSQL_EXECUTE" - in
         "START-OF-SELECTION".
        The main program was "/CRYSTAL/OSQL_EXECUTE ".
        In the source code you have the termination point in line 48
        of the (Include) program "/CRYSTAL/OSQL_EXECUTE".
    We are using BOBJ XI SP2. SAPGUI 6.2. SAP ECC6.0 SERVER. The following sets of transports from BOBJ integration kit SP4 have been imported into SAP.
    Open SQL Connectivity transport
    Row-level security definition transprot
    cluster definition transport
    Infoset Connectivity transport
    Authenticaton helpers tranport
    BOBJ support has been unable to help so far..

    Roland, we tried using the IP address to connect and create report and the same short-dump still occurs. We also applied BOBJ SP4 and it still didn't help. Please let us know if you have other thoughts. Thank you.
    Here is a snapshot of the sap short-dump.
    Error analysis                                                                                |
    Short text of error message:
    Syntax error in code: Error line #: 1 Message: REPORT/PROGRAM statement
    missing, or program type
    Long text of error message:
    Technical information about the message:
    Message class....... "AD"
    Number.............. 010
    Variable 1.......... "Syntax error in code: Error line #:"
    Variable 2.......... 1
    Variable 3.......... "Message:"
    Variable 4.......... "REPORT/PROGRAM statement missing, or program type"
    How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    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:
    "MESSAGE_TYPE_X" " "
    "/CRYSTAL/OSQL_EXECUTE" or "/CRYSTAL/OSQL_EXECUTE"
    "START-OF-SELECTION"
    |----
    System environment
    SAP-Release 700
    Application server... "ldcnadtc301"
    Network address...... "20.22.185.84"
    Operating system..... "SunOS"
    Release.............. "5.10"
    Hardware type........ "sun4u"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "ldc-nadtc301-db.ldco"
    Database type..... "ORACLE"
    Database name..... "DEV"
    Database user ID.. "SAPR3"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Feb 3 2008 21:08:24"
    create on........ "SunOS 5.9 Generic_117171-13 sun4u"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 146
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "SunOS 5.9, SunOS 5.10"
    User and Transaction
    Client.............. 200
    User................ "CRYSTAL"
    Language Key........ "E"
    Transaction......... " "
    Transactions ID..... "48BE892424F37464E10000001416B954"
    Program............. "/CRYSTAL/OSQL_EXECUTE"
    Screen.............. "SAPMSSY0 1000"
    Screen Line......... 6
    Information on caller of Remote Function Call (RFC):
    System.............. "DEV"
    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 1)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 200
    User................ "CRYSTAL"
    Transaction......... " "
    Call Program........."/CRYSTAL/SAPLOPENSQL"
    Function Module..... "/CRYSTAL/OSQL_EXECUTE_INTERNAL"
    Call Destination.... "NONE"
    Source Server....... "ldcnadtc301_DEV_00"
    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 "/CRYSTAL/OSQL_EXECUTE" - in
    "START-OF-SELECTION".
    The main program was "/CRYSTAL/OSQL_EXECUTE ".
    In the source code you have the termination point in line 48
    of the (Include) program "/CRYSTAL/OSQL_EXECUTE".
    Source Code Extract
    Line
    SourceCde
    18
    EXPORTING
    19
    PROGID                            = P_PROGID
    20
    GWHOST                            = P_GWHOST
    21
    GWSERV                            = P_GWSERV
    22
    IMPORTING
    23
    DESTINATION                       = DESTINATION
    24
    EXCEPTIONS
    25
    INVALID_PROGRAM_ID                = 1
    26
    CONNECT_TO_GATEWAY_FAILED         = 2
    27
    SERVER_NOT_REGISTERED             = 3
    28
    CONNECT_TO_REG_SERVER_FAILED      = 4
    29
    EXCLUSIV_NOT_SUPPORTED            = 5
    30
    OTHERS                            = 6
    31
    32
    IF SY-SUBRC <> 0.
    33
    write   / 'Did not Connect to reg server'.
    34
    write : / 'SY-SUBRC', SY-SUBRC.
    35
    EXIT.
    36
    ENDIF.
    37
    38
    IMPORT IMG_GETDATA_SOURCE[] FROM DATABASE INDX(ZA) ID P_JNAME.
    39
    DELETE FROM DATABASE INDX(ZA) ID P_JNAME.
    40
    41
    GENERATE SUBROUTINE POOL IMG_GETDATA_SOURCE
    42
    NAME PROGNAME
    43
    MESSAGE SYNTAX_CHECK_MESSAGE
    44
    LINE ERROR_LINE_NO.
    45
    IF SY-SUBRC <> 0.
    46
    WRITE: / 'Syntax error, message', SYNTAX_CHECK_MESSAGE.
    47
    WRITE: / 'in line', ERROR_LINE_NO.
    >>>>>
    MESSAGE ID 'AD' TYPE 'X' NUMBER 010 WITH
    49
    'Syntax error in code: Error line #:'
    50
    ERROR_LINE_NO
    51
    'Message: '
    52
    SYNTAX_CHECK_MESSAGE.
    53
    ENDIF.
    54
    55
    PERFORM GETDATA IN PROGRAM (PROGNAME)
    56
    using p_fname p_pksize p_progid p_gwhost p_gwserv destination.

  • Short dump while filtering an ALV report

    Hi ,
    I have an ALV report which gives me short dump when I filter any of the 'P' type field. I tried to implement sap note 839839 in debug mode but in vain. Should I implement this note first and then check the chnage?
    the short dump error "..........
    Error in ASSIGN: Memory protection error.                                                                               
    The current program "SAPLSSEL " uses the ASSIGN statement.              
    However, the offset of the segment (20208) plus the length (69)         
    is greater than the length of the segment (20264).                      
    This is not allowed.                                                                               
    If the error is in one of your own ABAP programs or an SAP program that          
    you have modified, try to correct it.                                            
    Reduce the offset and/or length that you are using.                                                                               
    If the error occurred in a non-modified SAP program, you may be                  
    able to find a solution in the SAP note system.                                  
    If you have access to the note system yourself, use the following                
    search criteria:                                                                               
    "ASSIGN_OFFSET+LENGTH_TOOLARGE"                                   
    "SAPLSSEL " or "LSSELFDI "                                        
    "FILL_DYN_FROM_FIELD_SEL"               ........."
    I appreciate ur inputs.
    thanks in advance,
    regards,
    shan

    Hi Guys,
    I found the answer. I had to define all P type fields with eaxact length of 16 . Its working fine.
    thanks for all your help.
    regards,
    shan

  • Short dump after AC_FLUSH_CALL

    Hi all,
    I'm using Netweaver 04 and I've developed a report that displays a dynpro containing a dynamic document and it auto-refreshes itself through the CL_GUI_TIMER class.
    After a period of correct working the report crashes with a short dump about the wrong exit of AC_FLUSH_CALL function module (CL_GUI_CFW->FLUSH method). sy-subrc = 2.
    Can you help me? Thanks in advance.
    Angelo

    My monitoring application accesses each second a DB table to check if its contents are changed and dispay a particular record on the dynpro.
    FILL_HEADER is fixed and FILL_VALUES can change.
    This is most of PBO code:
      SET PF-STATUS 'STATUS1100'.
      SET TITLEBAR  'TITLE1100'.
      CLEAR flag.
      IF first = 'X'.     " prima display
        CLEAR:   i_text, is_ma_data.
        REFRESH: i_text, is_ma_data.
        CREATE OBJECT head_cont
           EXPORTING container_name = top_screen.
        CREATE OBJECT values_cont
           EXPORTING container_name = values.
        CREATE OBJECT fill_header
          EXPORTING no_margins = 'X'.
        CREATE OBJECT fill_values
          EXPORTING no_margins = 'X'.
        CALL METHOD fill_header->initialize_document.
        PERFORM fill_field_names.
        CALL METHOD fill_header->merge_document.
        CALL METHOD fill_header->display_document
          EXPORTING
            parent             = head_cont
            container          = 'FILL_HEADER'
            reuse_control      = 'X'
            reuse_registration = 'X'.
        first = ' '.
      ENDIF.
        CALL METHOD fill_values->initialize_document
          EXPORTING
            background_color = bg_color.
        PERFORM fill_field_values.
    merge document
        CALL METHOD fill_values->merge_document.
        CALL METHOD fill_values->display_document
          EXPORTING
            parent             = values_cont
            container          = 'FILL_VALUES'
            reuse_control      = 'X'
            reuse_registration = 'X'.
      ENDIF.
    refresh
      CREATE OBJECT gui_timer.
      SET HANDLER event_handler->on_finished FOR gui_timer.
      gui_timer->interval = timeout.
      CALL METHOD gui_timer->run.
      CALL METHOD cl_gui_cfw=>update_view.
    Thanks.
    Angelo

  • Short dump in VF01 - Syntax error in program "RKEAK9RECP3000001"

    Helo all,
    We recently copied our production client to a QA client and when we try to save an SD invoice (VF01), we get a short dump titled - Syntax error in program "RKEAK9RECP3000001".
    The dump long text states:
    "The Dictionary structure or table "K9RECP3000001" is either not active"
    " or does not exist."
    and
    NOTE in case of a SHORT DUMP:
    if the following perform statement should lead to a short dump, then
    the report stated in the short dump is missing (RKEAK9Rsssmmmnnnn)
    Check if table K9Rsssmmmnnn exists. If not it should be transported
    from the original system.
    Regenerate the missing reports by using transaction SE37, entering
    function KEDR_REGENERATE_ALL_REPORTS and pressing button 'Test' and
    'Execute'.
    but I tried to run function KEDR_REGENERATE_ALL_REPORTS in SE37 and the problem persists.
    Maybe I'm not running it correctly - there is no execute option when pressing "Test" so I enter the function and press F8, which takes me to a screen titled "Test function module" and then I execute.
    My suspicion is that table "K9RECP3000001" cannot be created or generated since it it a system specific naming convention K9RSSSCCC0001 in which SSS is system ID (in our case ECP is production and ECQ is QA) ans CCC is client number (300 in prod, and should be 286 in ECQ).
    Has anyone encountered this type of a problem and knows how to fix it?
    Needless to say, I looked at OSS notes, but did not find the solution there.
    Any thought will be appreciated,
    Yoel.

    Shalom Yoel,
    This problem may be caused by the fact that some derivation rules
    that were originally created once in a system have been transported
    into target system without transporting the dependent objects
    as well (the generated tables for the derivation rule entries).
    You can see this by execution of program RKEDRCHECK with only
    parameter 'Check in all clients' marked. You will then get
    inconsistent derivation steps (which refer to a generated table
    table for the rule entries that doesn't exist because it was
    not transported).
    There are two ways to solve the problem:
    1.) If you don't need these steps any more in derivation you can get
        rid of them by executing program RKEDRCHECK with both parameters
        marked ('Check in all clients' and 'Delete inconsistent steps').
    2.) If these steps should remain you have to retransport the missing
        tables from the source system in which these tables have to exist
        (creating transport requests for the customizing of derivation by
        pushing on the 'Transport' icon in the source system in transactions
        KEDR and KEPC).
    For each derivation step,the system generates a program RKEAK9R *
    and a table K9R+ System ID+ Mandant+ a number of five figures
    from the object number in KEDR.
    br, Guido

  • Short dump 'DBIF_RSQL_SQL_ERROR' in R/3 system

    Hi,
    In the daily extraction process in BW a load process(infopackage) fails due to short dump "DBIF_RSQL_SQL_ERROR" in the source system(R/3) side.
    The load getting the 20000 records but the process failed due to above error. i have made the request red and delete the request from the respective data target and repeate the load, it isthrowing same error "DBIF_RSQL_SQL_ERROR" with 0 records.
    my question is if i solve the error and repeate the load can i get previous delta records with the latest delta.
    Can any one give a solution.
    Thanks

    Hi,
    If you are marking the dataload as "RED" in monitor before deleting the request, you will get the same delta with next load.
    You can verify this in next load  @ monitor. It will show you the request type as 'Repeat of last delta' and normal requests will be shown as 'Delta'.
    In case you are manually running the infopackage, system will prompt the message something like' last detla request was incorrect, repeat the last delta'.
    Regards,
    Pratap Sone

  • Short dump in report CLEAN_REQREQ_UP

    Hi,
    I'm in classic scenario with SRM 5.5 . I've created a PO in backend and when I run this report, a short dump  appears
    Have anybody any idea?
    Thanks in advance
    Best Regards

    hi dinesh
    my business steps are :
    I'm in srm server 5.5. and sap ERP 6.0
    I'm in classic scenario with plan driven procurement.
    I replicate my PR from PS to SRM, create a bid invitation. Receive bids and when I accept one of them I create a PO in backend.
    These steps work fine, but I can't run this report.
    The dump is as follows:
    - " UNCAUGHT_EXCEPTION"
    -  "The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere along the call hierarchy"
    - Since exceptions represent error situations and this error was not adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be terminated.
    Do you need anything more?
    Thanks in advance
    Best Regards

  • Short Dump generating reports of EWA

    Hi Experts,
    I get the short dump MESSAGE_TYPE_X when I tried to see the Ewa report?
    Any Idea?
    Thanks in advance.

    Hi,
    Mi ST 400 level is 17.
    Here is mi dump:
    Err.tmpo.ejec.         MESSAGE_TYPE_X                                                              
    Fecha y hora           10.08.2009 09:37:50                                                                               
    Texto breve                                                                               
    The current application triggered a termination with a short dump.                           
    ¿Qué ha sucedido?                                                                               
    The current application program detected a situation which really                            
        should not occur. Therefore, a termination with a short dump was                             
        triggered on purpose by the key word MESSAGE (type X).                                       
    Anál.errores                                                                               
    Short text of error message:                                                                 
        La creación de evento para la sesión EA0000000000881 ha fallado                                                                               
    Long text of error message:                                                                  
         Diagnóstico                                                                               
    La creación de un evento ha fallado.                                                    
         Actividades en el sistema                                                                   
             La transacción actual se cancela.                                                       
         Procedimiento                                                                               
    Procedimiento para la gestión del sistema                                                   
             El problema puede estar en el rango de números DSVASEVENT.                              
             Verifique si el intervalo "01" está creado y si tiene números                           
             libres. Notifique los resultados de esta exploración a SAP.                                                                               
    Technical information about the message:                                                     
        Message class....... "DSVAS"                                                                 
        Number.............. 093                                                                     
        Variable 1.......... "EA0000000000881"                                                       
        Variable 2.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
    Posición desencadenante de error tiempo ejecución                                                
        Programa                                SAPLDSVAS_RPGEN                                      
        Include                                 LDSVAS_RPGENU03                                      
        Línea                                   672                                                  
        Tp.módulo                               (FUNCTION)                                           
        Nombre módulo                           DSVAS_RPGEN_REPORT_GET_DATA                          
    Detalle código fuente                                                                            
    Lín.       Txt.fte.                                                                               
    642        lf_chapno_old = 0.                                                                       
      643      * Fehlende Kapitelnummern verdichten                                                       
      644        LOOP AT report_structure.                                                                
      645          AT NEW chapter.                                                                        
      646            IF lf_chapno_old <> report_structure-chapter.                                        
      647              lf_chapno_old = report_structure-chapter.                                          
      648              ADD 1 TO lf_chapno.                                                                
      649            ENDIF.                                                                               
    650          ENDAT.                                                                               
    651          report_structure-chapter = lf_chapno.                                                  
      652          MODIFY report_structure.                                                               
      653        ENDLOOP.                                                                               
    654                                                                               
    655                                                                               
    656      * Ereignis "Reportgeneriert" vermerken                                                     
      657        DATA: ls_dsvassessinstid TYPE dsvassessinstid,                                           
      658              lf_event_parameter TYPE dsvasevent-event_parameter.                                
      659      * AH 'SL' wird durch Aufrufer erst spaeter ausgeloest                                      
      660        if lf_iCount = 0 or sy-batch is initial.                                                 
      661          ls_dsvassessinstid-sessitype = sessitype.                                              
      662        ls_dsvassessinstid-sessno    = sessno.                                                   
      663        lf_event_parameter           = ls_dsvassessinstid.                                       
      664        CALL FUNCTION 'DSVAS_EVENT_RAISE'                                                        
      665             EXPORTING                                                                           
      666                  pf_event_type      = 'SL'                                                      
      667                  pf_event_parameter = lf_event_parameter                                        
      668             EXCEPTIONS                                                                          
      669                  failed             = 1                                                         
      670                  OTHERS             = 2.                                                        
      671        IF sy-subrc <> 0.                                                                        
    >>>>>          MESSAGE x093(dsvas) WITH ls_dsvassessinstid.                                           
      673      *     Ereigniserzeugung für Sitzung &1 fehlgeschlagen                                      
      674          ENDIF.                                                                               
    675        endif.                                                                               
    676      * AH                                                                               
    677                                                                               
    678        CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'                                                
      679             EXPORTING                                                                           
      680                  TEXT = space.                                                                  
      681      ENDFUNCTION.                                                                               
    Thanks in advance!

  • Short dump in custom report in production

    Hi Experts,
      I have a custom report which is run through SM37 as a background job. it takes long time to run and then get canceled with       short dump in production but it runs fine in development.
    description of short dump.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Date and Time          03.05.2010 11:33:06
    Short text
    |    SQL error in the database when accessing a table.

    Hi,
    Please go through the below notes
    [Note 1379839 - RuntimeError DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1379839]
    [Note 1098183 - RunErr dbif_rsql_sql_error with exception CX_SY_OPEN_SQL_DB|https://service.sap.com/sap/support/notes/1098183]
    [Note 1410849 - Runtime error DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"|https://service.sap.com/sap/support/notes/1410849]
    This is mainly program error and need corrections...
    Compare the Patch level on both DEV and PRD server. Also make sure, whether program you are using on developement is modified (Corrected) or standard one.
    If you search for the SAP Notes with "DBIF_RSQL_SQL_ERROR Exception CX_SY_OPEN_SQL_DB" string, you will get several hits. See the notes which are applicable in your scenario...
    Regards.
    Sumit Nene

Maybe you are looking for

  • Link in the Table

    Dear All,               I am having a requirement of hyper link in the Table. The table is getting populated with the link but if i click the link it should navigates to the URL specified there. What should i make it to work like that... Thanks in ad

  • Keys jammed

    Two keys 5 and 6 are jammed on my laptop. Any solution?

  • Does the adobe photoshop elements 11 come with an instruction manual

    does the adobe photoshop elements 11 come with an instruction manual

  • CA-42 Com port issues - Commonfx.sys

    So installed CA-42 cable,  wont connect to phone or come up "enhancement not supported" even, However have found that when I go to nokia connection manager to set the com port it comes up as....commonfx.sys....which is a file used by my sound card...

  • PS6 is suddenly crashing.

    Photoshop CS 6 crashed twice this evening. Enclosed is the crash report: Log Name:      Application Source:        Application Error Date:          10/26/2012 6:36:58 PM Event ID:      1000 Task Category: (100) Level:         Error Keywords:      Cla