CALL_TRANSACTION_LOCKED 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.
Variable name...........: <runtime parameter>.
Transaction <runtime parameter> is locked.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Please see call transaction for more details about the possible cause of this runtime error and how it could be avoided.
Table TSTC (Transactions) contains a lock flag for Transaction
"<runtime parameter>". This flag may be temporary in order to allow changes to be
made to the transaction or the data.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
CALL_TRANSACTION_LOCKED - call transaction locked CALL_TRANSACTION_IS_MENU - call transaction is menu 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