05-26-2011 7:04 AM
Runtime Errors MESSAGE_TYPE_X
Date and Time 26.05.2011 12:29:13
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).
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.......... " "
Trigger Location of Runtime Error
Program SAPLSLVC
Include LSLVCU10
Row 36
Module type (FUNCTION)
Module Name LVC_SORT_COMPLETE
Source Code Extract
Line SourceCde
05-26-2011 7:10 AM
Hi,
Please provide us sufficient information example, what you are doing , how you get this dump..
Regards,
Nagaraj
05-26-2011 7:19 AM
Hi,
I am very new to SAP and now testing Fieldcat, Layout and sort in a program.
Please help with SAP.
Best regards
05-26-2011 7:22 AM
Hi,
As others suggested..Please check your field catalog and see the field which you are sorting is there or not.
Regards,
Nagaraj
05-26-2011 8:01 AM
Hi,
please check, that all field names are UPPER CASE also in SORT table!
Regards,
Klaus
05-26-2011 7:10 AM
Hi,
to get more informations set a break-point in fm LVC_SORT_COMPLETE in line
READ TABLE IT_FIELDCAT ASSIGNING <LS_FIELDCAT>
WITH KEY FIELDNAME = LS_SORT-FIELDNAME BINARY SEARCH.
Check the field name to find out the field which causes the issue. Maybe there is a problem with the field name for SORT.
Regards,
Klaus
05-26-2011 7:14 AM
Hi,
I think the field used for sorting does not exist in the field catalog of your ALV.
Regards,
Srini.
05-26-2011 7:18 AM
Check your Field Catalog.. line by line, character by character. You will realise there's something amiss this. And if im not wrong, you got this Short dump when you try to do a Summation.
pk
07-28-2011 2:25 PM
07-30-2011 4:09 PM
Hi Thandar,
if you are new to SAP then you should not stay to outdated technology.
99,9 % of all ALV dump errors like yours are related to field catalog issues. One of the most frequent reason is the useless try of building a field catalog yourself without using standard functions like REUSE_ALV_FIELDCATALOG_MERGE and or the use of display tables without structure defined in data dictionary.
You can get rid of all those and many more troubles if you start with the actual ALV object model using CL_SALV_TABLE class.
Start with the excellent article series of Rich Heilman:
[ALV Object Model - Simple 2D Table - The Basics|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/eac1fa0b-0e01-0010-0990-8530de4908a6]
[ALV Object Model - Simple 2D Table - Event Handling|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/cda3992d-0e01-0010-90b2-c4e1f899ac01]
The object model does not use a (visible) field catalog. Almost all functions achieved by field catalog modification can be done by simple transparent and understandable method calls. This makes the programs maintenance friendly.
Regards
Clemens