UNCAUGHT_EXCEPTION_NOTE 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.
Refer to note <runtime parameter>.
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.
A nonexistent exception was raised.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Note <runtime parameter> describes possible causes for the exception.
The exception of the class '<runtime parameter>' was raised from the ABAP runtime environment. However, this class does not exist in the database and the exception could therefore not be caught.
Since excpetions represent error situations, the running ABAP program '<runtime parameter>' had to be terminated.
UNCAUGHT_EXCEPTION_NOTE - uncaught exception note UNCAUGHT_EXCEPTION - uncaught exception UC_STRUCLENG_INCONSISTENT - uc strucleng inconsistent UC_OBJECTS_TL_NOT_CHARLIKE - uc objects tl not charlike UC_OBJECTS_TABLINE_NOT_CHAR - uc objects tabline not char UC_OBJECTS_NOT_NUMLIKE - uc objects not numlike