CALL_DIALOG_WRONG_TDCT_MODE 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: F - Installation Errors
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 installation error 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.
Incorrect table entry for dialog module <runtime parameter>.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
In the dialog module table TDCT, the entry for the
dialog module "<runtime parameter>" contains an invalid mode "<runtime parameter>".
Valid modes are "L" or " " for normal dialog modules and
"R" for dialog modules that run on a different computer.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
Please see installation error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_DIALOG_WRONG_TDCT_MODE - call dialog wrong tdct mode CALL_DIALOG_SCREEN/PROGRAM - call dialog screen-fs-program CALL_DIALOG_NO_CONTAINER - call dialog no container CALL_DIALOG_NOT_FOUND - call dialog not found CALL_DIALOG_NAME_TOO_LONG - call dialog name too long CALL_DIALOG_NAMELIST_EMPTY - call dialog namelist empty