Application Development 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: 

Dump Error in Z table

Former Member
0 Kudos

I have created a Z table for the Data Element 'A' with

Data Type - QUAN

Length - 13

Decimals - 3.

Previously it was,

Data Type - NUMC

Length - 8

Decimals - 0.

When i execute in 200 it is working well i can create entries from the table and also through Table maintenance transaction.

But, in Quality Server

I am getting a Dump Error. It is as follows:

Runtime Errors: DYNPRO_FIELD_CONVERSION
Short Text: Conversion Error
Screen Name: "SAPLZTEST"
Screen Number: 0001
Screen Field: "ZTEST-VALUE"
Error Text: "FX020 : Data Lost."

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

It seems that the table contains tha data wich has range more than what the SAP screen can handle.

Applying latest Basis and Abap Patches might help.check the dump st22.

Regards,

Nandha

3 REPLIES 3

Former Member
0 Kudos

Hi,

It seems that the table contains tha data wich has range more than what the SAP screen can handle.

Applying latest Basis and Abap Patches might help.check the dump st22.

Regards,

Nandha

former_member1245113
Active Contributor
0 Kudos

Hi VInnela,

As your variable length earlies was 8 and of type numc and now changed to type p of lenght 13 and decimals 3 it will not have any problem as you increased the lenght.

Please try adjusting the table using Tcode SE14

Here select activate and adjust the table by selecting the radio button SAVE DATA, otherwise you will your data. so please ensure you select the SAVE DATA radio button.

i hope this will meet your requirement.

Thanks and regards

Ramchander Rao.krishnamraju

Former Member
0 Kudos

Hai Friends,

Thanks for your reply. The data type length wha i have given is not enough to hold the value. My value was 10,500.000. Here comma and '.' is also inclusive.

I have changed the data type as CURR with length 13 and decimal as 2. Now it is capturing.

Thanks.