UNCAUGHT_EXCEPTION 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.
An exception has occurred that was not caught.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
This exception is closely related to a previous exception <runtime parameter>, which
was raised in program <runtime parameter>, in line <runtime parameter> of (include) program <runtime parameter>. The
reason for the exception occurring was:
Exception '<runtime parameter>' was raised, but it was not caught anywhere along the
call hierarchy.
Since exceptions represent error situations, and this error was not
adequately responded to, ABAP program '<runtime parameter>' had to be terminated.
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 UC_OBJECTS_NOT_CONVERTIBLE - uc objects not convertible