on 12-28-2009 12:17 PM
Dear all,
today i got CONVT_NO_NUMBER error in Production Server (the same error i got 212 times)
28.12.2009 17:33:51 PRDCIXI_IRP_01 SAPSYS 000 C CONVT_NO_NUMBER
CX_SY_CONVERSION_NO_NUMBER 0 4B38A7FF9B7C0103E10080000A369120
System environment
SAP-Release 700
Application server... "PRDCIXI"
Network address...... "10.54.145.32"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "000184CAD400"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "PRODORADB"
Database type..... "ORACLE"
Database name..... "IRP"
Database user ID.. "SAPSR3"
Terminal................. " "
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jul 14 2008 22:03:01"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 169
please provide any suggestion
Regards
Hi,
Please provide some more information. Check with ABAPer for this error.
Regards,
Ranjith
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Shah,
still i am getting the same error below details for your refereence
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Date and Time 29.12.2009 09:28:52
Short text
Unable to interpret 0 as a number.
What happened?
Error in the ABAP Application Program
The current ABAP program "RSDSPROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Regards
Dear all
i got the below issue in Production Server .
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Date and Time 29.12.2009 09:28:52
Short text
Unable to interpret 0 as a number.
What happened?
Error in the ABAP Application Program
The current ABAP program "RSDSPROC" 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_NO_NUMBER', was not
caught in
procedure "AL_PRC_REPORT_VALUES" "(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:
The program attempted to interpret the value 0 as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Whole numbers are represented in ABAP as a sequence of numbers, possibly
with an algebraic sign.
The following are the possibilities for the representation of floating
point numbers:
[algebraic sign][mantissa]E[algebraic sign][exponent]
[algebraic sign][whole number part].[fraction part]
For example, -12E+34, +12E-34, 12E34, 12.34
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_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"
"RSDSPROC" or "RSDSPROC"
"AL_PRC_REPORT_VALUES"
Regards
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.