DYN_CALL_METH_PARAM_LITL_MOVE SAP ABAP Runtime Error dyn call meth param litl move

DYN_CALL_METH_PARAM_LITL_MOVE is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: A - ABAP Programming Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

DYN_CALL_METH_PARAM_LITL_MOVE ABAP Runtime Error

The actual parameter to be overwritten is a formal parameter of another method or is a field symbol:

Declare the parameter as a VALUE. Alternatively, either enter a help field that already contains the constant or assign this help field to the field symbol instead of the constants. Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Error in submitted parameter: Overwriting of a protected field. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

An attempt was made to assign an actual parameter to formal parameter <runtime parameter> of method <runtime parameter> of class <runtime parameter>. This parameter is protected against changes however.

The following are protected against changes:
- Character literals or numerical literals,
- Constants (CONSTANTS),
- Parameters of category IMPORTING REFERENCE in functions and methods,
- Untyped field symbols that have not been assigned a field using ASSIGN,
- TABLES parameters, if the actual parameter is protected against changes.
- USING reference parameters and CHANGING parameters in FORMs, if the actual parameter is protected against changes.
- Field symbols, if the field assigned with ASSIGN is protected against changes. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.