OBJECTS_NOT_CHAR 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.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
The current statement is not supported for STRINGs.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
In statement <runtime parameter>, only character-type data objects are supported at
argument position <runtime parameter>, not strings (data types STRING and XSTRING).
In this case, operand <runtime parameter> has type <runtime parameter>.
In the current statement, only character-type data objects are
supported, not strings.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
OBJECTS_NOT_CHAR - objects not char OBJECTS_NOT_BYTELIKE - objects not bytelike OBJECTS_MOVE_NOT_SUPPORTED - objects move not supported OBJECTS_L_CLASS_NO_LOAD_OK - objects l class no load ok OBJECTS_LOCAL_INTF_NOT_FOUND - objects local intf not found OBJECTS_LOCAL_CLASS_NOT_LOCAL - objects local class not local