‎2009 Oct 07 11:38 AM
Hi Friends,
below description is short dump for standard program.
Please see the below and help me how to correct the program.
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:
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
-
How 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, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
-
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
Thanks & Regards,
Sree
Edited by: adepus on Oct 7, 2009 12:39 PM
Edited by: adepus on Oct 7, 2009 12:39 PM
‎2009 Oct 07 11:45 AM
Hi,
For such Message Type X error, search for the OSS notes and implement them.
Regards,
Aditya
‎2009 Oct 07 11:45 AM
Hi,
For such Message Type X error, search for the OSS notes and implement them.
Regards,
Aditya
‎2010 Nov 03 9:06 AM
HI aditya,
could you please tell me the OSS note we need to use for above issue.
Thanks,
Pavan
‎2010 Nov 03 10:57 AM
>
> HI aditya,
>
> could you please tell me the OSS note we need to use for above issue.
>
> Thanks,
> Pavan
Holy sh... can't you look it up yourself?
‎2010 Nov 03 11:27 AM
Hi pavan,
let it dump. Enter debugger, see where you are and what caused the error.
You try to execute a report writer report. Something may have been changed or it did not work from the beginning. Re-Generation may help. Analysis may also help.
Note: SAP standard programs can dump if the data have not been configured consistently.
Regards,
Clemens
‎2010 Nov 09 9:27 AM
Hi Clemens,
I am getting a dump error as shown below. Could you please find some resolution for this issue. we just made some changes to the transaction GS02(Just added a GL account to one of the sets).
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.
Regards,
Pavan
‎2010 Nov 09 9:54 AM
Hi pavan,
sorry, I never worked with GS02, found a Note that says you must re-generate the source code for sets in validation/substitution. Don't know if it helps.
Regards,
Clemens
‎2010 Nov 09 2:04 PM
‎2009 Oct 07 12:48 PM
Hi Adepus,
Message X214 appears many times in form F80_FILL_COL_TAB of include FGRWEF80_F80_FILL_COL_TAB. And it corresponds to different kind of errors.
So could you precise the line of which the error occurs (it is displayed in the dump text) and the context (which transaction, ...) in order to help us.
Best regards,
Samuel