topic Re: Runtime Errors CONVT_NO_NUMBER in Application Development and Automation Discussions

Runtime Errors CONVT_NO_NUMBER

lalit_pawar — Mon, 30 May 2016 08:01:37 GMT

Dear All,

I am facing below dump in PRD server,

kindly give your valuable inputs t solve this.

Except. CX_SY_CONVERSION_NO_NUMBER

Short text

Unable to interpret "*71000.000" as a number.

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 and

therefore caused a runtime error.

The reason for the exception is:

The program attempted to interpret the value "*71000.000" as a number, but

since the value contravenes the rules for correct number formats,

this was not possible.

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"

"ZIRPT_PP_MCRI" or "ZIRPT_PP_MCRI"

"START-OF-SELECTION"

Regards

Lalit Pawar

Re: Runtime Errors CONVT_NO_NUMBER

Former Member — Mon, 30 May 2016 08:07:36 GMT

did you notice an asterisk (*) before the number, that's the issue

Re: Runtime Errors CONVT_NO_NUMBER

Former Member — Mon, 30 May 2016 08:14:05 GMT

Hi lalit,

Does your program have input file or input from selection screen? It gives dump because the number field has value of non numeric i.e. it contains * so giving dump.

Regards,

Pravin

Re: Runtime Errors CONVT_NO_NUMBER

lalit_pawar — Thu, 02 Jun 2016 05:18:09 GMT

dear Pravin,

its a customized product cost report for this we are giving input fields as plant number, date and material code only, for short period the report is working fine but for long period it is showing dump.

Regards

Lalit

Re: Runtime Errors CONVT_NO_NUMBER

Former Member — Thu, 02 Jun 2016 06:24:09 GMT

Hi,

Try increasing size of your field, Also Check what value system is calculating before display by debugging. Mostly * Symbol comes only when the value of field exceeds its length

Regards,

Venu

Re: Runtime Errors CONVT_NO_NUMBER

suresh_mamilla — Thu, 02 Jun 2016 06:48:25 GMT

Hi Lalit,

Check the note 1749518 to resolve the issue.

Regards

Suresh

Re: Runtime Errors CONVT_NO_NUMBER

pranay570708 — Thu, 02 Jun 2016 06:57:27 GMT

Hi,

Check the length of the amount field (which stores "*71000.000") in the report. May be for long period run, amount comes big and it is unable to accommodate that.

Re: Runtime Errors CONVT_NO_NUMBER

santanunayek — Thu, 02 Jun 2016 07:04:18 GMT

Hi, I think '*' is the problem. you may go like this.

REPLACE ALL OCCURRENCES OF '*' IN <VARIABLE> WITH space.

Regards,

Santanu