Dump MOVE_TO_LIT_NOTALLOWED_NODATA occurs after implementing kernel with release > 7.72
Cause of this Error:
In kernel releases < 7.72, an error in the write protection check of the ABAP runtime can cause components of an internal table that is actually write-protected to be overwritten anyway. The table itab must have the type STANDARD TABLE and be addressed via a dref->itab data reference.
The following statements are affected:
- READ TABLE dref->itab ... ASSIGNING <line> ... and/or
- READ TABLE dref->itab ... REFERENCE INTO lr_line ...
The write protection was not correctly transferred to the field symbol <line> or the row reference lr_line. Therefore it was possible to overwrite row components using <line>-comp or lr_line->comp.
- LOOP AT dref->itab ... ASSIGNING <line> ... and/or
- LOOP AT dref->itab ... REFERENCE INTO lr_line ...
The write protection was not correctly transferred to the field symbol <line> or the row reference lr_line. Therefore it was possible to overwrite row components using <line>-comp or lr_line->comp.
CALL TRANSFORMATION ... PARAMETERS (dref->itab)
Although the parameter table dref->itab of the transformation was write-protected, but the parameter values could be overwritten by the transformation.
Solution
For Kernel Release 7.72
In order to restore the correct behavior, the SAP profile parameter abap/runt/write_check_fix with the default value 'ON' has been introduced. The value of this profile parameter should only be set 'off' with the help transaction RZ11 in rare cases and only temporarily (only on individual application servers if possible).
For instance, following the implementation of a kernel release >= 7.72, a central program unexpectedly encounters the runtime error MOVE_TO_LIT_NOTALLOWED_NODATA.
The actual cause of the write protection infringement is an ABAP programming error that must be rectified. Afterwards, the profile parameter must be reset to the default value "on" on all application servers.
Kernel releases > = 7.73
The previously mentioned SAP profile parameter is no longer available in this release. The actual cause of the write protection infringement is an ABAP programming error that must be rectified.