Barcode entry giving a dump

[Former Member]

Hello Everybody,

In a module pool program all the desc and other relavent data is getting displayed for all the barcodes(ean11) except for ean11 8850124035967 (a 13 digit no ) .Its working fine for other 13 digit number, but only for this ean11 its giving as conversion error.

There was a conversion error in the output of fields to the screen.

The formats of the ABAP output field and the screen field may not match ( Why for only this EAn its giving the dump and there a field besides get from dict and in that xmask fix,modif'd is selected from many other options .What does it do )

Screen name.............. "ZLM03"

Screen number............ 0400

Screen field............. "MARM-UMREZ"

Error text............... "FX020: Data lost."

thanks,

[Former Member]

Have you tried isolating the EAN problem at all e.g. does the following report work OK for you?

report zlocal_jc_ean11_test.

parameters:
  p_ean11               type ean11
    default '8850124035967'.

start-of-selection.
  write: / p_ean11.

The EAN11 data domain has a conversion exit on it, so you could also try executing those by themselves in SE37 to see what results you get (CONVERSION_EXIT_EAN11_OUTPUT / CONVERSION_EXIT_EAN11_INPUT).

However, the error you have indicated in your message is that the UMREZ field is the cause of the crash .. so what material is returned by the EAN, and can you see this OK in SE16 when browsing MARM? Your screen field should be 6 bytes long (per the definition of domain UMBSZ).

Jonathan

[Former Member]

Have you tried isolating the EAN problem at all e.g. does the following report work OK for you?

report zlocal_jc_ean11_test.

parameters:
  p_ean11               type ean11
    default '8850124035967'.

start-of-selection.
  write: / p_ean11.

The EAN11 data domain has a conversion exit on it, so you could also try executing those by themselves in SE37 to see what results you get (CONVERSION_EXIT_EAN11_OUTPUT / CONVERSION_EXIT_EAN11_INPUT).

However, the error you have indicated in your message is that the UMREZ field is the cause of the crash .. so what material is returned by the EAN, and can you see this OK in SE16 when browsing MARM? Your screen field should be 6 bytes long (per the definition of domain UMBSZ).

Jonathan

[Former Member]

Thanks Mr Coleman,

Yes ,I realised where the problem is , After browsing the umrez field of marm table , It says it has sign value attached . So though the field length is 5 digit long its giving a dump for 3 digits UMREZ value I guess its reserving some places for sign. Is there way to suppress this.

Thanks,

[Former Member]

I don't think the extra byte is for a sign, but for a decimal point... if you try the following code you will see that if you try to enter a negative, SAP gives you an error "Negative values not allowed"... if you try 6 digits, it says "Entry too long (please enter in the format __,__~)". Entering 99999 works fine.

Jonathan

report zlocal_jc_umrez.

parameters:
  p_umrez               like marm-umrez.

start-of-selection.
  write: / p_umrez.

[Former Member]

Thanks Jonathan,

I passed the value into a user defined work field then moved the 3 digits with no signs to marm-umrez its working fine