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

Similar Messages

  • 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

  • Short Dump while maintaining conditions in Product master

    Hi Experts,
    We are getting short dump while we want to maintain conditions in the product master.
    The dump message is as follows -
    CREATE DATA: The specified type "/1CN/WS_ID_300PRODUCTBBP_SKU_T" is no valid 
    An exception occurred that is explained in detail below.                         
    The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not     
    caught in                                                                       
    procedure "/SAPCND/MNT_INIT_OW" "(FUNCTION)", nor was it propagated by a         
    RAISING clause.                                                                 
    Since the caller of the procedure could not have anticipated that the            
    exception would occur, the current program is terminated.                        
    The reason for the exception is:                                                 
    The dynamically specified type "/1CN/WS_ID_300PRODUCTBBP_SKU_T" at CREATE DATA   
    is no valid data type.                                                                               
    The type is either unknown or an object type.                                    
    I checked for OSS note but could not get success and also i could not explore in SDN. Can anybody help me in this.
    Thanks a lot in advance!!
    Thank You
    Abhinandan

    Hi
    <b>Please go through the following SAP OSS Notes, which will definitely help -></b>
    <u>Note 930816 - Cond. Maint. group not generated after remote client copy</u>
    <u>Note 1051896 - Cond. group WS deleted in source aft. remote client copy</u>
    Note 971825 - Short dump caused by dynamic working set
    Note 969475 Short dump after applying notes 966127&966197
    Note 661287 - Name of the condition maintenance group
    Note 1009001 - ShortDump when Creating Mkt-Obj by Copying
    Do let me know.
    Regards
    - Atul

  • Short Dump with ALV Report

    Hi
    I have one Zreport which gives the result in ALV form.
    After getting the result(1 row with 33 columns) when I tried to export the ALV results to spread sheet using the option : List-> Export-> Spread Sheet OR by click on Excel icon in the display screen,I'm getting the short dump with the description "No more storage space available for extending an internal table" .
    After analysis ,find that dump is raising in the FM : F4_GET_RESULT of Include Program : LSDH3U03.
    Can anyone provide us some clue .
    Thanks & Regards,
    Sreeram

    Hi,
    If the display is in ALV grid format, then you can try another approach to save the data in a spreadsheet.
    - Right-click on any output cell.
    - Select 'Spreadsheet' from the drop down list
    - radio-button 'All available formats'
    - Excel (In existing XXL format)
    Thanks!
    VS.

  • TIME_OUT Short Dump for SAPLDSVAS_PROC report - BPM activation

    Hello SOLMAN Experts,
    I'm trying to activate BPM Business Process Monitoring and getting the following short dump:
    Runtime Errors         TIME_OUT
    Short text
         Time limit exceeded.
    What happened?
         The program "SAPLDSVAS_PROC" has exceeded the maximum permitted runtime without
        interruption and has therefore been terminated.
    Any advice please?
    Thanks,
    123

    Hello,
    For the time being (Temporarily), you can try to increase the parameter rdisp/max_wprun_time to some higher value and then try activation process. This parameter is I think 'dynamic' and so can be updated without system restart. You can verify this from rz11.
    After you done, revert the value.
    Thanks

  • Short dump when executing report.

    Dear all,
    I’m running a web template report which is calling a multiprovider and within the multiprovider are 9 cubes. All cubes have aggregates and are optimize for performance. Lately, for the past 2 days, users have been complaining that they keep getting error 500, a time out error. This happens only to certain users and not all. Some users are able to query for data more the 5 years where as some not even 1 day. Below is the error which BW is throwing back to us. Can you please help me analyze the error?
    Error analysis
        After a certain length of time, the program is terminated. In the case
        of a work area, this means that
        - endless loops (DO, WHILE, ...),
        - database accesses producing an excessively large result set,
        - database accesses without a suitable index (full table scan)
        do not block the processing for too long.
    Trigger Location of Runtime Error
        Program                                 SAPLRSDRS
        Include                                 LRSDRSF04
        Row                                     116
        Module type                             (FORM)
        Module Name                             FETCH_DATA_OPENSQL
      103
      104     IF <l_s_data>      IS NOT ASSIGNED OR
      105        <l_s_data>      IS NOT ASSIGNED OR
      106        <l_s_data_olap> IS NOT ASSIGNED .
      107       RAISE EXCEPTION TYPE cx_rs_program_error
      108          EXPORTING
      109            method = 'FETCH_DATA_OPEN_SQL-2-'.
      110     ENDIF.
      111   ENDIF.
      112
      113
      114   IF i_pkgsize <= 0.
      115 *   Reading all data with one single fetch
    >>>>>     FETCH NEXT CURSOR i_cursor
      117       INTO CORRESPONDING FIELDS OF TABLE <l_t_data>.
      118     e_eof = rs_c_true.
      119   ELSE.
      120 *   Reading only one package
      121     FETCH NEXT CURSOR i_cursor
      122       INTO CORRESPONDING FIELDS OF TABLE <l_t_data>
      123       PACKAGE SIZE i_pkgsize.
      124
      125 *   If less than 'i_pkgsize' many tuples are read
      126 *   => end-of-data is reached
      127     DESCRIBE TABLE <l_t_data> LINES l_count.
      128     IF l_count <> i_pkgsize.
      129       e_eof = rs_c_true.
      130     ENDIF.
      131   ENDIF.

    Hi SCHT.
    Error itself says that
    <i>"database accesses producing an excessively large result set,
    - database accesses without a suitable index (full table scan)
    do not block the processing for too long."</i>
    I believe there should be some change in query which causes aggregates to be excluded from selection.
    Try running query from RSRT with option Execute + Debut ->Aggergates section select "Display aggregates found" and see the out put ..and watch whether aggregates are actually used.
    Also some time this error happens because of network traffic , try running query in Bex Analyzer and see the run time.
    Hope that helps.
    Regards
    Mr Kapadia
    Assigning points is the way to say thanks in SDN.

  • Short dump in Production system !!!

    Hi Experts,
        We have getting a short dump for all actions in Production system. Suppose if we use se38 and tried to press display it shows a short dump error. Despite when we tried to use tcodes or using LSMW or try to execute a program or like this all type of actions its throws a short dump error. Dont know what is the reason behind that since the short dump is not the defined the reason for the dumb. Have any of you experts got this type of experience?. Pls give your ideas. Thanks in advance.

    Hello Kavi,
    Contact your basis team. SNAP is a table which holds all ABAP dump. It looks like SNAP table is full and cannot accomodate new entries.
    In any production enviornment, the SNAP entires will be deleted regularly and only dumps for the last 8 days will be available
    Check if any job(SM36 or table tbtcp) is running for this program RSSNAPDL in your production system.
    Thanks

  • 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

  • What is Short Dump Analysis and  secendry index  ?

    Dear Experts .
    1.) What is purpose of T-codes SE30 and ST22 ?
    What is Short Dump Analysis ?
    2.) What is secendry index , How to use it ? How it effects the Performance of a report ?
    Please it is urgent ...
    Regards : Rajneesh

    Hi
    A dump analysis is a comprehensive list that should enable you to identify the causes and possible solutions of program errors. The ABAP Workbench generates a short dump whenever a report or transaction terminates due to a serious error. The system enters the error in the system log and writes a snapshot of the program at the moment when it terminated into a special database table called SNAP.
    Dump analyses give the user or programmer information about the causes of the error that has caused the program to terminate. Experienced users can use them to identify very quickly where and why this occurred. He or she can them solve the problem.
    The snapshot contains the following information:
    Why the program has terminated
    What caused the program termination
    Where in the program code the termination occurred
    What you can do to correct the error
    The values of the relevant system fields when the program terminated
    The calls or events that were active when the program terminated
    Any other programs that are affected.
    http://help.sap.com/saphelp_nw70/helpdata/en/c6/617d0ce68c11d2b2ab080009b43351/content.htm
    Index: Technical key of a database table.
    Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
    Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
    Structure of an Index
    An index can be used to speed up the selection of data records from a table.
    An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
    When creating indexes, please note that:
    An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
    Only those fields whose values significantly restrict the amount of data are meaningful in an index.
    When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
    Make sure that the indexes on a table are as disjunctive as possible.
    (That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
    Accessing tables using Indexes
    The database optimizer decides which index on the table should be used by the database to access data records.
    You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
    The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
    If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
    When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated

  • How to locate the repository table relevant to my custom report. ?

    Hi
    I have to develop custom user  report  in  SAP GTS.
    User wants custom report with product, classification and tariff details.
    Please tell me, How do I locate the relevant  table and field from the the GTS SAP repository ?
    BTW, Where do I go from here and do some more research and understand the GTS schema or repository database understand the different tables and its purpose and also its relation, etc.
    Any pointers ?
    Your help is much appreciated. Many thanks in advance.
    -siva

    hi,
    open ur transaction and in menu goto system status and find program name.
    then in se37 open GET_TABLES func module.give program name and execute.
    u will get all tables related to that transaction.use the tables which have ur required fields.

  • Bdc short dump

    what do you do when you encounter short dump during execution report or bdc

    After getting a dump, first read the dump analysis. It ll tell you what exactly the problem is.
    Then move ahead to find the "Source code extract" which shows you at which line of your code the problem occurs.
    Click the icon left to Deburgger button to get the list of options available.
    1    What happened?
    2    What can you do?
    <b>3    Error analysis</b>
    <b> 4    How to correct the error</b>
    5    System environment
    6    User, transaction...
    7    Information on where terminated
    <b>8    Source code extract</b>
    9    Contents of system fields
    10    Active calls / events
    11    Chosen variables
    12    Application Calls
    13    Application Information
    14    Internal notes
    15    Active calls in SAP kernel
    16    List of ABAP programs affected
    17    List of internal tables
    18    Directory of Application Tables
    19    Directory of Application Tables (Administrative Information)
    20    ABAP control blocks CONT
    21    End of runtime analysis
    Reward points if helpful
    Thanks
    vinsee

  • Initial customizing loads (DNL_*) causing short dumps in R/3

    Hi,
    I'm trying to run the initail loads for the DNL_* customizing objects.  When I start a load in R3AS and check the status in R3AM1, it shows "Running".  In the CRM oubound queue (SMQ1), there is an entry for the load with status SYSFAIL.  The detailed status message is "The current application triggered a termination with a short dump". 
    The short dump in R/3 shows an error "No external system (such as CRM) connected" which occurs in function module CRM_FIRST_CALL_OPERATIONS.  Looking at the code, there seems to be a problem with the CRMRFCPAR table.  I had only one record in this table for object CUSTOMER_MAIN, so I tried adding a record with Object Name "*" and Load Type "I", but this had no effect. 
    What is the proper configuration of table CRMRFCPAR for customizing loads?  Is it possible that this error is related to some other config or a problem with the RFC connection?  These loads work fine in our quality system which is configured the same as production (as far as I can tell).
    Thanks.
    Martin

    hi,
    Maintaining Table CRMRFCPAR (SAP R/3)
    The parameters in this table indicate the RFC destinations which receive data. The required parameters include, for example: consumer, client, object name, and download type.
    You can send data to a certain consumer only in an initial download and not in a delta download by making the appropriate specifications for the data exchange.
    User- That uses the OLTP plug-in functions as data receivers
    Object name -Object name
    Destination -Specifies the destination of the CRM server
    Load Type -Restricts CRMRFCPAR entries to the initial (I) or delta (D) download.
    Out Queue - Name RFC outbound queue
    In Queue -Name RFC inbound queue
    BAPI name
    INFO -Information/Comments
    InQueue flag- Controls whether qRFC inbound queues are used on the CRM server
    Send XML -XML supports (Should data be sent in XML format?)
    Stop data -Causes the OLTP System to place data into the outbound queue.
    Regards
    sri

  • CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test

    Hello,
    I'm getting the follwoing short dump in production when I run the program which writes the data to application server. I have open data set and close data set. Same program when I in development and test I do not get any short dump. Can any know what could be cause for this.
    CX_SY_FILE_OPEN_MODE
    Copy paste of error analysis from ST22 short dump -
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
         caught in
        procedure "DATA_UPLOAD_APP_SERVER" "(FORM)", nor was it propagated by a RAISING
         clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        When accessing the file "/bw/FTPOUT/BPR/OTHER/test.csv", the system recognized
         that this file is
        not open. Therefore, the file cannot be accessed.

    The file could not be OPENed in your production system for a variety of reasons - no authorization, file doesn't exist etc. You should have check sy-subrc right after OPEN DATASET and if not zero, yous should not TRANSFER or READ the file and instead you should have given a message with sy-msgid and sy-msgno which would give you the reason. The dump here is simply saying that OPEN is unsuccessful, so any subsequent READ or TRANSFER would throw runtime dump, if done after an unsuccessful OPEN.

  • 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 when I do total or sub total in the ALV report

    Hi,
    When I do total or sub-total on the currency field in the ALV report, it'll give a short dump like
    " 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)".
       Short text of error message:
       Technical information about the message:
       Message classe...... "0K"
       Number.............. 000
       Variable 1.......... " "
       Variable 2.......... " "
       Variable 3.......... " "
       Variable 4.......... " "
       Variable 3.......... " "
       Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLSLVC
        Include                                 LSLVCF36
        Row                                     2,726
        Module type                             (FORM)
        Module Name                             FILL_DATA_TABLE
    sometime when I do the page down on the ALV report, the same short dump is coming.
    Can anyone help me out.
    Thanks
    Selva

    Hi,
    I'm getting this short dump in the standard program.
    I'm getting ALV report display perfectly. the problem is, when I do total or subtotal on the currency fields.
    2704
    2705 ************************************
    2706 * Column per Fieldcat Entry
    2707 ************************************
    2708         ls_lvc_data-value = space.
    2709         clear ls_lvc_data-style.
    2710         loop at it_fcat_local assigning <ls_fcat>
    2711                 where tech ne 'X' and no_out ne 'X'.
    2712           if l_invisible eq 'X'.
    2713             clear l_invisible.
    2714             if <ls_fcat>-do_sum is initial.
    2715               continue.
    2716             else.
    2717               clear ls_lvc_data-col_pos.
    2718             endif.
    2719           endif.
    2720
    2721           add 1 to ls_lvc_data-col_pos.
    2722
    2723           assign component <ls_fcat>-fieldname
    2724                            of structure <ls_data> to <l_field_value>.
    2725           if sy-subrc ne 0.
    >>>>>             message x000(0k).
    2727           endif.
    2728
    in this standard program, I'm getting the dump. the line is mentioned above in the code.

Maybe you are looking for