ABAP runtime errors CONVT_NO_NUMBER

[yls177]

in my system log got this error
AB0 Run-time error "CONVT_NO_NUMBER" occurred


short dump error (there are over hundreds of these short dumps)

ABAP runtime errors CONVT_NO_NUMBER
Unable to interpret "*" as a number.

Error analysis
The program attempted to interpret the value "*" 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 by a series of numerals with a
sign in front of them if necessary.
The following floating point number representations are possible in
ABAP:
[sign][mantissa]E[sign][exponent]
[sign][whole number part].[fractional part]
z.B. -12E+34, +12E-34, 12E34, 12.34

If the error occurred in an ABAP program of your own or an SAP program
that you modified, try to correct it.

If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:


using this <Run-time error "CONVT_NO_NUMBER" occurred> as the search entry,
i have a list of oss notes which match <abap runtime "CONVT_NO_NUMBER" occurred>

any guidance to what is wrong?

thanks

[aaristondo]

Hi,
This is a program error.
You must check the entries for the ABAP report thaat crashes, if it is an standard report search for notes on this report and CONV_NO_NUMBER.
If it is a Z_report, then talk with your developpers.

[yls177]

pardon me for my ignorance...

but how do u know that it is an program error?

and now. my abap dumps have reached 390.

[aaristondo]

Hi,
As you worte (from the dump):
ABAP runtime errors CONVT_NO_NUMBER
Unable to interpret "*" as a number.

The system cannot understand the value "*" as a number, it is a charachter, but not a number.
In the Dump you can see the name of the abap report that is crashing. Contact SAP or look for notes on that report if it is standard one. Or contact your developpers if it is a Z report.
regards

[Nothing_else_to_do]

This can also be a user input error. We get this dump once in a while when a user inputs a non-numeric figure when the program expects to be given a number.

[VTHokie]

I realize this post is a million years old, but ran into this myself and though anyone else who was looking for a solution might benefit if they happened across this posting. ANYWAY...

Check to make sure that the value of the field is not too big for the field. For instance if you have the following:

DATA: x(2) type n.

x = x + 999.

and then you try to compare 'x' to anything you will get this error because the value will actually show up as '9*' showing that the value doesn't fit and that there are more significant values than what it is capable of showing.

Hope this helps someone somewhere...would have done me a heck of a lot of good a few weeks ago!

TB