SAPSQL_DISTINCT_STAR_DEEP 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.
Using SELECT DISTINCT * on tables with strings.
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 attempted to execute an Open SQL statement in
which "SELECT DISTINCT" should be used to select from the table "<runtime parameter>".
Due to the fact that the table "<runtime parameter>" contains at least one string field,
the addition "DISTINCT" is not allowed here.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_DISTINCT_STAR_DEEP - sapsql distinct star deep SAPSQL_DISTINCT_AND_LOB - sapsql distinct and lob SAPSQL_DELETE_WA_TOO_SMALL - sapsql delete wa too small SAPSQL_DELETE_TAB_TOO_SMALL - sapsql delete tab too small SAPSQL_DEEP_WA_INCOMPATIBLE - sapsql deep wa incompatible SAPSQL_CURSOR_ALREADY_OPEN - sapsql cursor already open