CALL_TRANSACTION_NOT_FOUND 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.
Check whetehr the transaction just needs to be listed in the directory
or the program needs to be corrected.
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 field......................: <runtime parameter>.
Transaction "<runtime parameter>" is unknown.
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 does not contain an entry for transaction "<runtime parameter>". This could
be due to a program error (incorrect transaction code specified).
Note also that the system is case-sensitive.
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.
CALL_TRANSACTION_NOT_FOUND - call transaction not found CALL_TRANSACTION_MSG_NO_PAGING - call transaction msg no paging 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