CALL_DIALOG_ILLEGAL_CODE 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: I - Internal Kernel 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 illegal code for more details about the possible cause of this runtime error and how it could be avoided.
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.
Please see illegal code for more details about the possible cause of this runtime error and how it could be avoided.
The command counter has been moved by <runtime parameter> units.
Invalid program code in CALL DIALOG statement.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see illegal code for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_DIALOG_ILLEGAL_CODE - call dialog illegal code CALL_DIALOG_DATAAREA_NOT_EMPTY - call dialog dataarea not empty CALL_DIALOG_CONTAINER_MISSING - call dialog container missing CALL_DIALOG_CONNREAD_FAILED - call dialog connread failed CALL_DATABASE_NOT_SUPPORTED - call database not supported CALL_C_FUNCTION_PARM_MISSING - call c function parm missing