Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Hi, Have you searched for any relevant SAP notes? Note 1249888 is a possible solution Regards Sent from my Windows Phone
| | | ---------------Original Message--------------- From: Velayutham Sent: Monday, February 28, 2011 2:52 AM Subject: Dump after executing FB01 Hi Experts, Iser tried to give input through tcode-FB01, but it throws abap dump as follows, Runtime Errors MESSAGE_TYPE_X Date and Time 24.02.2011 12:33:39 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: System error (termination point SORT_2) Long text of error message: Diagnosis An internal error has occurred. System Response You cannot continue with processing. Procedure Contact SAP to establish whether the error can only be rectified by a program correction, or whether it can also be rectified by changes to the settings. There may also be an error in the updating of the data which must be resolved. Specify the following parameters when reporting the error: o Message : GLT0/000 o Program : SAPLGLT0 o Termination point : SORT_2 Technical information about the message: Message class....... "GLT0" Number.............. 000 Variable 1.......... "SORT_2" Variable 2.......... "SAPLGLT0" 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" " " "SAPLGLT0" or "LGLT0FER" "INTERNAL_ERROR" 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. User and Transaction Client.............. 230 User................ "UMESHM" Language key........ "E" Transaction......... "FB01 " Transactions ID..... "1CE43FE02552F136923D001AA01FE9B6" Program............. "SAPLGLT0" Screen.............. "SAPMF05A 0700" Screen line......... 47 Information on where terminated Termination occurred in the ABAP program "SAPLGLT0" - in "INTERNAL_ERROR". The main program was "SAPMF05A ". In the source code you have the termination point in line 38 of the (Include) program "LGLT0FER". Source Code Extract Line SourceCde 8* text 9* | | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | D. Caddick SAP Basis Top Contributor
Contributed the most posts in a group for 3 consecutive months to earn a Gold Achievement Most Popular White Papers In the Spotlight _.____.__ |