We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

[sap-basis] Dump after executing FB01

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Posted by Velayutham
on Feb 28 at 2:51 AM
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*----------------------------------------------------------------------*
10FORM internal_error USING errorcode.
11
12* Local fields
13 DATA:
14 subseq_flag TYPE glt0_flag.
15
16* Error?
17 CHECK sy-subrc <> 0.
18
19* Get subsequent posting flag
20 PERFORM subsequent_posting USING space
21 CHANGING subseq_flag.
22
23 IF errorcode = gc_clrbal.
24 IF subseq_flag = xon.
25 PERFORM message_send USING 'A000'
26 errorcode
27 sy-msgv2
28 sy-msgv3
29 sy-msgv4.
30 ELSE.
31 MESSAGE x000 WITH errorcode sy-msgv2 sy-msgv3 sy-msgv4.
32 ENDIF.
33 ELSE.
34* Subsequent posting -> message handler, else -> dump
35 IF subseq_flag = xon.
36 PERFORM message_send USING 'A000' errorcode sy-repid space space.
37 ELSE.
>>>>> MESSAGE x000 WITH errorcode sy-repid.
39 ENDIF.
40 ENDIF.
41
42ENDFORM. " INTERNAL_ERROR
43
44*----------------------------------------------------------------------*
45*&---------------------------------------------------------------------*
46*& Form MESSAGE_STORE
47*&---------------------------------------------------------------------*
48* text
49*----------------------------------------------------------------------*
50FORM message_store.
51
52 CALL FUNCTION 'MESSAGE_STORE'
53 EXPORTING
54 exception_if_not_active = space
55 arbgb = sy-msgid
56 msgty = sy-msgty
57 txtnr = sy-msgno
Active Calls/Events

No. Ty. Program Include Line
Name

10 FORM SAPLGLT0 LGLT0FER 38
INTERNAL_ERROR
9 FORM SAPLGLT0 LGLT0F01 21
SORT_ACCIT_EX
8 FUNCTION SAPLGLT0 LGLT0U01 678
G_BEB_SPLIT_DOCUMENT
7 FUNCTION SAPLFAGL_SPL_SERVICES LFAGL_SPL_SERVICESU01 139
FAGL_RWIN_SPLIT
6 FORM SAPLFACG LFACGU03 698
CALL_SPLITTER
5 FORM SAPLFACG LFACGU03 188
PROCESS_PROJECT
4 FUNCTION SAPLFACG LFACGU03 43
FI_DOCUMENT_PROCESS
3 FORM SAPMF05A MF05AFF0_FCODE_BEARBEITUNG 1098
FCODE_BEARBEITUNG
2 FORM SAPMF05A MF05AFF0_FUSSZEILE_VERARBEITEN 149
FUSSZEILE_VERARBEITEN
1 MODULE (PAI) SAPMF05A MF05AI00_FUSSZEILE_BEARBEITEN 46
FUSSZEILE_BEARBEITEN

LOOKING FOR SOLUTION...THANKS IN ADVANCE..
__.____._
Copyright © 2011 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
View this online
  
Most Popular White Papers

In the Spotlight
Overcome the Top Inhibitors to Cloud Computing. View the IBM Cloud Briefing, Available on Demand.
_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language