Runtime Errors CONVT_NO_NUMBER

[Former Member]

Hi,

I am below dump. Kindly do the needful.

Runtime Errors CONVT_NO_NUMBER

Exception CX_SY_CONVERSION_NO_NUMBER

Date and Time 28.09.2009 18:15:50

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, +12E34, 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 nonmodified 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"

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

"AL_PRC_REPORT_VALUES" "(FORM)", or its possible occurrence must be declared in

the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAPRelease 700

Application server... "sapbwpapp"

Network address...... "10.10.88.40"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "00CF4CEC4C00"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "sapbwpdb"

Database type..... "ORACLE"

Database name..... "KBP"

Database user ID.. "SAPSR3"

Terminal................. " "

Char.set.... "C"

SAP kernel....... 700

created (date)... "Jan 23 2008 21:25:00"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 144

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 16192

EM...... 12569544

Heap.... 0

Page.... 16384

MM Used. 1287792

MM Free. 2899456

User and Transaction

Client.............. 000

User................ "SAPSYS"

Language key........ "E"

Transaction......... " "

Transactions ID..... "4AC099D78D84004BE10080000A0A5828"

Program............. "RSDSPROC"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

[markus_doehr2 · Accepted solution]

> Runtime Errors CONVT_NO_NUMBER

> Exception CX_SY_CONVERSION_NO_NUMBER

If you search notes for the program name "RSDSPROC", you'll find

Note 1144644 - CCMS: Process monitoring in ABAP returns incorrect data

which describes exactly your problem.

Markus

[lalit_pawar]

This message was moderated.

[Former Member]

If you read the dump, it says:

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, +12E34, 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 nonmodified 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"

This means that the system can not handle the value 0 since it expecting floating point and just 0 is not floating point.

Search for a [SAP Note|http://service.sap.com/notes] with the above keywords.