Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Exception = CX_SY_CONVERSION_NO_NUMBER

Former Member
0 Likes
11,851

Hi,

May we ask for your assitance, why we are getting this error:

Error analysis:

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER',

was neither

caught nor passed along using a RAISING clause, in the procedure

"CONVERT_FISCPER_SELECTION" "(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

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

since the value contravenes the rules for correct number formats,

this was not possible.

Information on where terminated:

The termination occurred in the ABAP program "SAPLGUSL" in

"CONVERT_FISCPER_SELECTION".

The main program was "SBIE0001 ".

The termination occurred in line 406 of the source code of the (Include)

program "LGUSLF01"

of the source code of program "LGUSLF01" (when calling the editor 4060).

The program "SAPLGUSL" was started as a background job.

Processing was terminated because the exception "CX_SY_CONVERSION_NO_NUMBER"

occurred in the

procedure "CONVERT_FISCPER_SELECTION" "(FORM)" but was not handled locally, not

declared in the

RAISING clause of the procedure.

The procedure is in the program "SAPLGUSL ". Its source code starts in line 350

of the (Include) program "LGUSLF01 ".

Thanks.

Hi,

May we ask for your assitance, why we are getting this error:

Error analysis:

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER',

was neither

caught nor passed along using a RAISING clause, in the procedure

"CONVERT_FISCPER_SELECTION" "(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

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

since the value contravenes the rules for correct number formats,

this was not possible.

Information on where terminated:

The termination occurred in the ABAP program "SAPLGUSL" in

"CONVERT_FISCPER_SELECTION".

The main program was "SBIE0001 ".

The termination occurred in line 406 of the source code of the (Include)

program "LGUSLF01"

of the source code of program "LGUSLF01" (when calling the editor 4060).

The program "SAPLGUSL" was started as a background job.

Processing was terminated because the exception "CX_SY_CONVERSION_NO_NUMBER"

occurred in the

procedure "CONVERT_FISCPER_SELECTION" "(FORM)" but was not handled locally, not

declared in the

RAISING clause of the procedure.

The procedure is in the program "SAPLGUSL ". Its source code starts in line 350

of the (Include) program "LGUSLF01 ".

Thanks.

6 REPLIES 6
Read only

Former Member
0 Likes
6,215

are you using any conversion exit in your program, or if you are passing blank value to the conversion exit there is possibility.

Read only

0 Likes
6,215

If the SAP version you are using is upgraded then you might get these kind of dumps...

Raghav

Read only

Sandeep_Panghal
Product and Topic Expert
Product and Topic Expert
0 Likes
6,215

Search for SAP notes with the term "CX_SY_CONVERSION_NO_NUMBER"

Read only

Former Member
0 Likes
6,215

Hi,

When entering numbers if u give 2 3, this is not a valid number and when you assign this number to some variable or perform operation on the same,error will be raised.

This is because ,it cannot interpret that as a number and cannot perform operations.

Read only

Former Member
0 Likes
6,215

HI...

this error occur when we are trying to move data of charactor type or even SPACE or special charactor to NUMERIC type....

soloution to your problem....

only give numeric values in the selection screen or look for some user exit if available or go for enhancement framework.

this is a same kind of problem which i was getting

regards

Read only

former_member182537
Active Participant
0 Likes
6,215

Hi,

One of users is getting this error -An exception with the type CX_SY_CONVERSION_NO_NUMBER occurred, but was neither handled locally, nor declared in a RAISING while refreshing Custom workbooks but query is running fine.

In the selection we have only Calendar Year/Month as mandatory variable.

Any help on this apprecaited

Thanks

Nilesh