dear Sir
we have window 7 for new oc as soon runned teh program cv01n i got run time error msg CX_SY_CONVERSION_OVERFLOW,plese guide
Runtime Errors CONVT_OVERFLOW
Except. CX_SY_CONVERSION_OVERFLOW
Date and Time 03.05.2010 14:26:31
Short text
Overflow when converting from "-1"
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLCV120" 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 "SYS_GET_WINDOW_SYSTEM" "(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", 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"
"SAPLCV120" or "LCV120F28"
"SYS_GET_WINDOW_SYSTEM"
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
"SYS_GET_WINDOW_SYSTEM" "(FORM)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "APP2"
Network address...... "132.147.166.13"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x IA64 Level 3"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "DB"
Database type..... "MSSQL"
Database name..... "ELP"
Database user ID.. "elp"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 23 2009 22:38:30"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "SQL_Server_8.00 "
Patch level. 221
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 29328880
Heap.... 0
Page.... 655360
MM Used. 3095760
MM Free. 1091456
User and Transaction
Client.............. 900
User................ "CPTN_SAPC5"
Language key........ "E"
Transaction......... "CV03N "
Transactions ID..... "C29156DF1F2DF180BE040017A4AB426D"
Program............. "SAPLCV120"
Screen.............. "SAPLCV110 0101"
Screen line......... 3
regards
kunal
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.