topic Re: Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order in Application Development and Automation Discussions

Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order

former_member642554 — Mon, 29 Jun 2015 13:02:08 GMT

Dear Experts,

While creating an order with reference to contract (Via t-code VA42 or VA43) ,system is getting runtime error 'DYNPRO_FIELD_CONVERSION'.

Error analysis

The program run has been interrupted and cannot be resumed. The program

"SAPMV45A" tried to output fields on screen 4900. During the conversion of the

data an error occurred.

And the error analysis is clearly showing that the problem while passing value from ABAP program to screen variable.

How to correct the error

A conversion error occurred when displaying fields on the screen.

The formats of the ABAP output field and the screen field may not

correspond.

Some field types require more spaces on the screen than in the ABAP

program. For example, a date output field requires two more spaces on

the screen than the corresponding field in the ABAP program. In the

attempt to display the date on the screen, an error occurs that

triggers this error message.

Screen name............... "SAPMV45A" Screen number............. 4900 Screen

field.............. "RV45A-KWMENG" Error text................ FX015: Sign lost.

Other data:

But the source code extract is showing some different thing as below.

Line SourceCde

1 *---------------------------------------------------------------------*

2 * Einteilungsdatum ausgeben. *

3 *---------------------------------------------------------------------*

4 MODULE VBEP-EDATU_AUSGEBEN OUTPUT.

6 CALL FUNCTION 'PERIOD_AND_DATE_CONVERT_OUTPUT'

7 EXPORTING INTERNAL_DATE = VBEP-EDATU

8 INTERNAL_PERIOD = VBEP-PRGRS

9 IMPORTING EXTERNAL_DATE = RV45A-ETDAT

10 EXTERNAL_PERIOD = RV45A-PRGBZ.

>>>>> ENDMODULE.

I am getting confused why and where exactly the system is going for runtime error?

I searched in SDN and other sites also. But no luck.

If any one faced same situation, help me.

Thanks and regards,

Aumprakasharya T

Re: Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order

Jelena_Perfiljeva — Mon, 29 Jun 2015 19:04:30 GMT

The message is self-explanatory:


    Screen name............... "SAPMV45A" Screen number............. 4900 Screen
    field.............. "RV45A-KWMENG" Error text................ FX015: Sign lost.
    Other data:

The short dump occurs because of the screen field, not because of the specific ABAP code, so it just dumps at the end of module. In any case, it's not unusual when the code shown in short dump is not the exact root cause (e.g. in case of a time-out). We always need to evaluate the whole short dump text carefully and do some analysis.

If memory serves, KWMENG is the quantity field, nothing to do with the date from what I see.

Re: Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order

Juwin — Mon, 29 Jun 2015 20:52:32 GMT

Are you in some way changing the quantity field of the order (RV45A-KWMENG)? If not, can you check the value of VBAP-KWMENG field in database, for this order?

The dump says error text as "Sign lost". This is because the domain used for RV45A-KWMENG doesn't support signs; i.e., it always expects a positive value for KWMENG field. If some user exit changes the value of KWMENG to be negative, system cannot display that on screen and causes a dump.

Thanks,

Juwin

Re: Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order

former_member642554 — Tue, 30 Jun 2015 04:38:07 GMT

Hi Juwin,

There is no sign for the quantity in VBAP-KWMENG.

Thanks and regards,

Aumprakasharya T

Re: Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order

Private_Member_7726 — Tue, 30 Jun 2015 05:02:35 GMT

Hi,

Go into debug mode and try to set a watchpoint on RV45A-KWMENG < 0 in SAPMV45A. There are several OSS notes related to this bug, but they all are very old.

cheers

Jānis

Re: Runtime error 'DYNPRO_FIELD_CONVERSION' while creating order

former_member642554 — Tue, 30 Jun 2015 08:41:18 GMT

Thank you all for the support.

It is working fine now.. we did nothing for that. Might be it was random error in the system.

But it is better to know the root cause for this issue... experts please share your finding on this issue, that will help us and others in the future.

Thanks and regards,

Aumprakasharya T