on 05-08-2009 7:38 AM
Dear Team,
When my Finanace Key user Posting a vature .he got a ABAP Dump.
Runtime Errors CONVT_OVERFLOW
Exception CX_SY_CONVERSION_OVERFLOW
Short text
Overflow when converting from "-1.03016e+11"
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLGLT0" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "SPLIT_FROM_BASIS" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
When attempting to convert the value "-1.03016e+11", an overflow occurred.
How to correct the error
If the error occurred in your own ABAP program or in an SAP
program you modified, try to remove the error.
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:
"CONVT_OVERFLOW" "CX_SY_CONVERSION_OVERFLOW"
"SAPLGLT0" or "LGLT0F61"
"SPLIT_FROM_BASIS"
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.
The exception must either be prevented, caught within proedure
"SPLIT_FROM_BASIS" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Moni
> When my Finanace Key user Posting a vature .he got a ABAP Dump.
> Runtime Errors CONVT_OVERFLOW
> Exception CX_SY_CONVERSION_OVERFLOW
Implement
Note 1167551 - Error message instead of CONVT_OVERFLOW dump in SAPLGLT0
to avoid the dump. Neverless, the number is too big to be handled.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1.03016e+11 is a huge number.
ask him to use a wider column size in excel... and change number format to make sure it does not use scientific numbers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.