MOVE_TO_LIT_NOTALLOWED_NODATA dump

[Former Member]

Hi,

I am getting dump MOVE_TO_LIT_NOTALLOWED_NODATA in the program SAPLKKBL and the inlude program is LKKBLF01where the dump is occuring.

Please see the dump occured.

011060 if rs_layout-no_hotspot is initial.

011070 format hotspot on.

011080 endif.

011090

011100 concatenate 'RS_HEADER-TEXT' r_col into l_field.

011110 assign (l_field) to <hf>.

> <hf> = l_char. --->

011130

011140

011150 l_tabname = g_tabname.

011160

I could not get any information because this is a standard program.

Regards,

Jyothi CH.

[Former Member]

Hi,

Please refer sap note 561767.

Reason and Prerequisites

In FORM CHECK_FOR_DIFFERENCES of report SAPF070 (is called by SAPF190 via SUBMIT), the FM REUSE_ALV_BLOCK_LIST_DISPLAY dumps because field catalog FIELDCAT_UMS is inconsistent due to the missing field HWAE2 in structure LIST_UMS.

Solution

Implement the correction in accordance with the correction instructions or import the corresponding R/3 support package.

[former_member206439]

Can you please let me know at what time your getting this DUMP.

Means steps and also include the program names listed in SHORT DUMP.

Thanks

Naresh

[Former Member]

These are the steps

Runtime Error MOVE_TO_LIT_NOTALLOWED_NODATA

Occurred on 17.05.2010 at 05:00:24

Assignment error: Overwriting a protected field.

What happened?

Error in ABAP application program.

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

statements could not be executed.

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

How to correct the error

The field you want to overwrite is a parameter or a field symbol:

Declare the parameter as a VALUE parameter or pass an auxiliary field

to which you assigned the value from the constant before the call.

Alternatively, you can assign the auxiliary field to the field symbol

instead of the constant.

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:

-

---

"MOVE_TO_LIT_NOTALLOWED_NODATA" C

"SAPLKKBL" or "LKKBLF01"

"HEADER_FIELD_OUT"

-

---

Information on where terminated

The termination occurred in the ABAP program "SAPLKKBL" in "HEADER_FIELD_OUT"

The main program was "YMM8G_DVFORECAST_SEND_001 ".

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

program "LKKBLF01"

of the source code of program "LKKBLF01" (when calling the editor 11120).

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

Source code extract

010820

010830 elseif ( rs_fieldcat-just = 'C' or not rs_fieldcat-symbol is initia

010840 and rs_fieldcat-reptext(1) ne '@'

010850 rs_fieldcat-reptext+3(1) ne

010860 *<<<Y6BK023178

010870 l_ffset = l_lendisplay - l_leninm + rs_fieldcat-outputlen.

010880 write rs_fieldcat-reptext to l_char(l_ffset)

010890 centered.

010900 *<<<Y6BK023178

010910 else.

010920 if rs_fieldcat-reptext(1) = '@' and

010930 rs_fieldcat-reptext+3(1) = '@'.

010940 lflg_icon = 'X'.

010950 write rs_fieldcat-reptext to l_char(4)

010960 as icon left-justified.

010970 else.

010980 *<<<Y6BK023178

010990 l_ffset = l_lendisplay - l_leninm + rs_fieldcat-ou

011000 write rs_fieldcat-reptext to l_char(l_ffset)

011010 left-justi

011020 *<<<Y6BK023178

011030 endif.

011040 endif.

011050

011060 if rs_layout-no_hotspot is initial.

011070 format hotspot on.

011080 endif.

011090

011100 concatenate 'RS_HEADER-TEXT' r_col into l_field.

011110 assign (l_field) to <hf>.

> <hf> = l_char.

011130

011140

011150 l_tabname = g_tabname.

011160

011170 g_tabname = rs_fieldcat-tabname.

011180 hide g_tabname.

011190 if lflg_icon is initial.

011200 ">>Y9CK034230

011210 if not cl_gui_alv_grid=>m_multibyte is initial

011220 or g_sli eq 'MULTIBYTE'.

011230 if l_len > rs_fieldcat-outputlen.

011240 data:

011250 im_pos_vis type i,

011260 im_pos_tech type i,

011270 ex_pos_vis type i,

this is the run time analysis.

Regards,

Jyothi CH.

[SuhaSaha]

Looks like there is something wrong with the fieldcatalog of the ALV.

Try running the ALV consistency check & see if there are any errors in the fieldcatalog.

Read this blog by Rainer on ALV Consistency check: [/people/rainer.hbenthal/blog/2009/09/25/sos--my-alv-report-is-not-working]