SAPSQL_TWICE_DEFINITION 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 sapsql internal 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.
A specification has been made twice for a LOB column
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
Only one definition pro LOB column can be made in the CREATING addition.
You should note that redundant specifications are not permitted
either. The superfluous specification is "<runtime parameter>".
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_TWICE_DEFINITION - sapsql twice definition SAPSQL_TOO_MANY_TABLES - sapsql too many tables SAPSQL_TABNAME_TOO_LONG - sapsql tabname too long SAPSQL_SUBQUERY_ILL_TABLE_TYPE - sapsql subquery ill table type SAPSQL_STREAMS_NOT_SUPPORTED - sapsql streams not supported SAPSQL_STMNT_TOO_LARGE - sapsql stmnt too large