SAPSQL_AGGREGATE_LOB 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.
Usage of a string field in an aggregate function.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The running ABAP program wanted to execute a Open SQL statement in which
the database field "<runtime parameter>" is used in an aggregate function. In Open SQL,
a string field is not allowed to be used in an aggregate function. In
the existing case, the database field "<runtime parameter>" has the illegal type "<runtime parameter>".
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
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 RUNT_INTERNAL_ERROR - runt internal error RUNT_ILLEGAL_SWITCH - runt illegal switch