SAPSQL_ALIASNAME_TOO_LONG 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 abap error for more details about the possible cause of this runtime error and how it could be avoided.
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.
Alternative field name in SQL statement is too long.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The SELECT clause was specified at runtime in an internal table.
In this table, the alternative name "<runtime parameter>" for a field or the
result of an aggregate function contains more than <runtime parameter> characters.
This is too many.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_ALIASNAME_TOO_LONG - sapsql aliasname too long SAPSQL_AGGREGATE_NOT_ALLOWED - sapsql aggregate not allowed SAPSQL_AGGREGATE_LOB - sapsql aggregate lob SAPSQL_AGGREGATE_ILL_TABTYPE - sapsql aggregate ill tabtype SAPSQL_ACCESS_TO_RHS_TABLE - sapsql access to rhs table SAPGUI_NO_EVENT_DESCRIPTION - sapgui no event description