Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

ABAP dump when using OO ALV grid

Former Member
0 Kudos
1,289

Hi Experts,

I have created a screen using OO ALV. i can add, delete and save records using the screen and i can perform validations for each and every cell and display errors wherever necessary. However sometimes i get the below ABAP dump message. Can anyone reply me why this dump happens. Because its not appearing everytime.

Short text
    The current application triggered a termination with a short dump.

What happened?
    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).

What can you do?
    Note down which actions and inputs caused the error.


    To process the problem further, contact you SAP system
    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.

Error analysis
    Short text of error message:


    Long text of error message:

    Technical information about the message:
    Message class....... "0K"
    Number.............. 000
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "

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" " "
"CL_GUI_ALV_GRID===============CP" or "CL_GUI_ALV_GRID===============CM02X"
"SAVE_DATA"

If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

   To save the description, choose "System->List->Save->Local File
(Unconverted)".

2. Corresponding system log

   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which
actions and input led to the error.

System environment
    SAP-Release 701

    Application server... "aix182"

.

SourceCde


      if l_index ne ls_good_cells-tabix.
        clear lflg_adjust.

*... Read data copy to which new info is to be added
        read table <tab2> into <ls_wa> index ls_good_cells-tabix.
        read table <tab1> index ls_good_cells-row_id assigning <ls_wa1>.
        l_subrc = sy-subrc.

        if l_subrc ne 0.
*... This Row does not exist in the data table -> append to output table
          read table mr_data_changed->mt_protocol into ls_msg
                     with key msgty  = 'E'
                              row_id = ls_good_cells-row_id.
          if sy-subrc eq 0.
            assign component ls_msg-fieldname
                             of structure <ls_wa> to <l_field>.
            if sy-subrc ne 0.
              message x000(0k).
            endif.
            clear <l_field>.
          endif.
          append <ls_wa> to <tab1>.

          l_tabix = sy-tabix.

*... Read the original rowID from frontend table
          read table mt_roid_front into ls_row_no
                     with key row_id = ls_good_cells-row_id.
          if sy-subrc ne 0.

  >>>>>>> message x000(0k).
          endif.

*... Adjust the automatically generated ID from Backend ID
          ls_conversion-row_id = ls_row_no-row_id.
          ls_row_no-row_id = l_tabix.
          modify mt_roid_front from ls_row_no index sy-tabix.

          read table lt_conversion
                          with key row_id = ls_conversion-row_id
                                   sub_row_id = l_tabix
                     transporting no fields.
          if sy-subrc ne 0.
            ls_conversion-sub_row_id = l_tabix.
            append ls_conversion to lt_conversion.
          endif.


Kind regards,

Vivek

9 REPLIES 9

former_member184569
Active Contributor
0 Kudos
230

Hi,  change the message type from X to E or something else.

message E000(0k).

If this is part of standard program,  you may have to share more info on your program.

0 Kudos
230

Hi Susmitha,

Thanks for your reply..

But the dump happens under the standard code.

Former Member
0 Kudos
230

Hi,

Check the fieldnames in the fieldcatalog. If fieldnames are correct, check whether you have put the fieldnames in upper-case.

Dump extract is from a standard ALV program. You cannot change the message from 'X' to 'E'.

Regards,

DPM

0 Kudos
230

Hi,

Thanks for your reply..

I checked the fieldnames in the fieldcatalog. all the fieldnames are correct and maintained in UPPER case. But still the dump occurs.

0 Kudos
230

Hi,

Check whether the fieldnames declared in fieldcatalog and that in the internal table are same or not.

Regards,

DPM

GirieshM
Active Contributor
0 Kudos
230

Hi Vivek,

Can you please share your code. The dump happens in the standard code but the root cause for the dump is in the custom program.

With Regards,

Giriesh M

Former Member
0 Kudos
230

HI,

Can you please check whether the message class , message number exist or not..

Thanks And regards,

Vijay vikram

0 Kudos
230

Hi Vijay,

message class exists but the message number does'nt exists..should i maintain any config..

Former Member
0 Kudos
230

Hi,

Check whether same row number is repeated twice.

Thanks & Regards,

Akshay Ruia