CATCH_ECAT_MISSING 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.
Internal error: ENDCATCH control block not found
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
A SYSTEM-EXCEPTION has been triggered. After that, the related
ENDCATCH control block could not be found in the current event.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
CATCH_ECAT_MISSING - catch ecat missing CATCH_CATC_WRONG_OFFSET - catch catc wrong offset CALL_XMLRFC_BACK_REJECTED - call xmlrfc back rejected CALL_USING_MNNEXT_FAILED - call using mnnext failed CALL_TRANSACTION_USING_NESTED - call transaction using nested CALL_TRANSACTION_NOT_FOUND - call transaction not found