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

Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

Former Member — Thu, 20 Oct 2011 07:47:23 GMT

Hi Experts

I am getting a dump as follows

Short text

Unable to interpret "/ 000000" as a number.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSZA19" 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 "ADDR_TIMESTAMP_IS_VALID" "(FUNCTION)", 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 "/ 000000" 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, poss

with an algebraic sign.

The following are the possibilities for the representation of floati

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

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the followi

keywords:

"CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"

"SAPLSZA19" or "LSZA19U01"

"ADDR_TIMESTAMP_IS_VALID"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

Please advise.

Thanks in advance

Baisakhi

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

Former Member — Thu, 20 Oct 2011 08:18:32 GMT

Hello,

in which transaction do you have this dump ?

The exception is quite clear.

Is there any place where you put some numbers or data ?

Of course you can aviod the dump by CATCH ENDCATCH statemets, but this is not a solution I suppose ?

f.e:


CATCH SYSTEM-EXCEPTIONS convt_no_number = 1.
   COMPUTE x = y + 1.
ENDCATCH.

IF sy-subrc EQ 1.
   MESSAGE ...
ENDIF.

Regards.

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

Former Member — Thu, 20 Oct 2011 08:25:59 GMT

The error is got when a job with program name RBDAPP01 is run in production server.

Thanks

Baisakhi

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

Former Member — Thu, 20 Oct 2011 08:28:38 GMT

The error is got at

FUNCTION addr_timestamp_is_valid.

*"----

""Lokale Schnittstelle:

*" IMPORTING

*" VALUE(IV_TIMESTAMP) TYPE AD

*" EXCEPTIONS

*" ZERO_TIMESTAMP

*" ILLEGAL_TIMESTAMP

*"----

DATA: lv_timestamp_p TYPE timesta

lv_timezone TYPE timezon

lv_date TYPE sydatum

IF iv_timestamp IS INITIAL.

EXIT.

ENDIF.

IF iv_timestamp = c_timestamp_zer

MESSAGE a614 WITH iv_timestamp

ENDIF.

>>>> lv_timestamp_p = iv_timestamp.------error

CLEAR lv_timezone.

CONVERT TIME STAMP lv_timestamp_p

TIME ZONE lv_timezone

INTO DATE lv_date.

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

Former Member — Thu, 20 Oct 2011 09:29:21 GMT

Hello

As I understood you should check the input parameters of the program RBDAPP01 which set in SM36/SM37 as a job (for example take a look in specif variant)

In my opinion there is an error in "Created at" field at RBDAPP01 saved as a variant.

Take a look and let me know.

Daniel.

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

deepak_dhamat — Thu, 20 Oct 2011 09:35:04 GMT

Hi ,

Check whether you are passing number with value '/' or , .

regards

Deepak.

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

deepak_dhamat — Thu, 20 Oct 2011 09:48:33 GMT

Hi ,

are you passing Data to BDC .

regards

Deepak.

Re: Runtime Errors CONVT_NO_NUMBER Exception CX_SY_CONVERS

Former Member — Thu, 20 Oct 2011 11:44:48 GMT

It would appear that your program is looking for a timestamp, which are stored in SAP tables as DEC 15 fields. They display like 10/20/2011 07:36:00, but they are stored like 20111020073600. It is quite obvious that / 00000000 is not a number, because it contains both a slash and a space. From your display, it appears that you have a timestamp that is not populated, and therefore the display looks like: / / 000000.

Somewhere the program is not converting a date and time to a timestamp, or you have a time stamp field displayed for user input, and the user doesn't understand how to input a time stamp, which would be keyed into a screen variablelike:

10/20/2011 07:36:00

If you are just starting with a date, look at your CONVERT DATE....TIME into TIMESTAMP .... TIME ZONE statement.... for example, if the user has a variable on screen that contains only a type D field, I would do something like:

get time.

convert date p_datefield "or sy-datum

time sy-uzeit

into time stamp time_stamp_var

time zone sy-zonlo.

regardless, the error you posted occurs on a true numeric field which has had characters other than digits, a decimal and a sign input to the field.