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

Dump problem while remote FM call

Former Member
0 Likes
968

Hello Experts,

In R3 system there is a RFC Fm Z_SALESORDER_CREATE which is wrapper of standard FM SD_SALESDOCUMENT_CREATE. When we do remote call from CRM system for Z_SALESORDER_CREATE. Its given dump as follows:

Short text

"Unable to interpret 2,00 as a number."

What happened?

Error in the ABAP Application Program

The current ABAP program "Z_CREATE_ORDER_WITH_JOB_VRNT" had to be terminated

because it has

come across a statement that unfortunately cannot be executed.

The error occurred during an RFC call to another system.

In the target system, a short dump has been written as well.

More detailed information on the error cause can be found there.

Error analysis

An error occurred when executing a REMOTE FUNCTION CALL.

It was logged under the name "CONVT_NO_NUMBER"

on the called page.

We are not using 2,00 anymore...it is something changed format while compiling..

It cause dump in R3 also..dump desc in r3 as follows

Unable to interpret " 2,00" as a number.

What happened?

Error in ABAP application program.

The current ABAP program "SAPLSTS4" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Error analysis

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

. 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

"CONVERSION_EXIT_TSTRG_OUTPUT" "(FUNCTION)"

.

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

to occur, the running program was terminated.

The reason for the exception is:

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

since the value contravenes the rules for correct number formats,

this was not possible.

How to correct the error

The exception must either be prevented, caught within the procedure

"CONVERSION_EXIT_TSTRG_OUTPUT"

"(FUNCTION)", or declared in the procedure's RAISING clause.

To prevent the exception, note the following:

Integers are represented in ABAP using a sequence of digits and, in so

cases, a preceding sign.

The system offers the following options for displaying floating point

numbers:

[sign][mantissa]E[sign][exponent]

[sign][whole number part].[fractional part]

e.g. -12E+34, +12E-34, 12E34, 12.34

If the error occurred in one of your own programs or in an SAP program

that you modified, try to correct it yourself.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-


"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC

"SAPLSTS4" or "LSTS4U01"

"CONVERSION_EXIT_TSTRG_OUTPUT"

-


Please help me to solve ths problem as soon as possible..

thanks in advance for you quick response.

Anutosh

1 ACCEPTED SOLUTION
Read only

kesavadas_thekkillath
Active Contributor
0 Likes
666

it would be happening in condition statement.....the incoming parameter would be character type ......declare the parameter in CHAR format and check.

3 REPLIES 3
Read only

Former Member
0 Likes
666

Hi,

Check your input whether it is numeric or alpha numeric. The problelm in the dumb is kind of convertion problem. Check before the rfc strts to work

Suku

Read only

sreeramkumar_madisetty
Active Contributor
0 Likes
666

Hi

Check your defined data types which you are passing to FM and exact FM data types.

I hope that's the problem .

Regards,

Sree

Read only

kesavadas_thekkillath
Active Contributor
0 Likes
667

it would be happening in condition statement.....the incoming parameter would be character type ......declare the parameter in CHAR format and check.