Dump error MESSAGE_TYPE_X in Standard Program

[Former Member]

Hi Experts,

I am getting below dump error when i am using transaction GR55 for Report Group..

Runtime Error MESSAGE_TYPE_X

ShrtText

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?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

Error analysis

Short text of error message:

Internal error: Program , include , form .

Technical information about the message:

Diagnosis

An unexpected error has occurred.

Procedure

If you can reproduce the error, contact the SAP Hotline quoting the

error number.

Message classe...... "GR"

Number.............. 214

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

Variable 3.......... " "

Variable 4.......... " "

to correct the error

Probably the only way to eliminate the error is to correct the program.

-

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"MESSAGE_TYPE_X" C

"SAPFGRWE" or "FGRWEF80_F80_FILL_COL_TAB"

"F80_FILL_COL_TAB"

-

---

If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)".

2. A suitable printout of the system log

To obtain this, call the system log through transaction SM21.

Limit the time interval to 10 minutes before and 5 minutes

after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, select the Editor function "Further Utilities->

Upload/Download->Download".

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

Source Code

79 MESSAGE x214.

80 ENDIF.

81 PERFORM e08_read_object_index(sapfgsb0)

82 USING fcolumns-dim_index.

83 IF c-subrc <> 0. MESSAGE x214. ENDIF.

84 c_dsentry = c-tval-from.

85 IF c_dsentry <> '='.

86 READ TABLE data_fields BINARY SEARCH

87 WITH KEY tab = rep_table

88 dsentry = c_dsentry.

>>>> IF sy-subrc <> 0. MESSAGE x214. ENDIF.

90 ENDIF.

91 WHEN OTHERS.

92 c_dsentry = '*'.

93 ENDCASE.

94 ENDIF.

Moderator message: don't just dump dumps, look for SAP notes yourself before asking.

Edited by: Thomas Zloch on Nov 4, 2010 10:04 AM

[nirajgadre]

Hi Pavan,

Check the SAP Note 137971.