SAPSQL_SELECT_DBTAB_CHANGED 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: R - Error at ABAP Runtime
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 try again for more details about the possible cause of this runtime error and how it could be avoided.
Database table changed at program runtime.
Please see runtime error for more details about the possible cause of this runtime error and how it could be avoided.
In an Open SQL select, the output area where the selected records will
be placed must be at least as wide as the database table whose records
are to be read.
Since the work area was checked already when the program was compiled,
but was too short when executed, the database table was probably
changed at program runtime.
In the present case, the database table has a width of <runtime parameter> bytes,
whereas the output area has a widfth of just <runtime parameter> bytes.
The database table to be accessed during the current SELECT was changed
at program runtime.
SAPSQL_SELECT_DBTAB_CHANGED - sapsql select dbtab changed SAPSQL_PROJVIEW_NO_STREAMS - sapsql projview no streams SAPSQL_PARSE_ERROR - sapsql parse error SAPSQL_PARSER_TODO_WARNING - sapsql parser todo warning SAPSQL_PACKAGE_NEGATIVE - sapsql package negative SAPSQL_OTHER_ONLY_AT_THE_END - sapsql other only at the end