CALL_TRANSACTION_FAILED 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 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.
Name of variable... <runtime parameter>
Value of variable... <runtime parameter>.
Could not call transaction "<runtime parameter>".
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
An unexpected error has occurred while calling transaction <runtime parameter>.
Please see internal error 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_TRANSACTION_FAILED - call transaction failed CALL_SYSTEM_DISABLED - call system disabled CALL_RPERF_SLOGIN_READ_ERROR - call rperf slogin read error CALL_RPERF_SLOGIN_AUTH_ERROR - call rperf slogin auth error CALL_METHOD_RETURN_ERROR - call method return error CALL_METHOD_PARMS_ILLEGAL - call method parms illegal