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