DBSQL_TABLE_UNKNOWN
highDatabase Table Does Not Exist in the Physical Database
Module: ABAP / DBI
What this means
DBSQL_TABLE_UNKNOWN means the ABAP program referenced a table in a SELECT, INSERT, UPDATE, or DELETE statement, and that table does not exist as a physical object in the database. The ABAP Dictionary (SE11) may show the table definition, but if the table has not been activated or the activation did not create the physical database object, the runtime will throw this error. Typical causes: a transport carrying a new table arrived but the table was never activated in SE11; a database object was deleted at the database level without corresponding ABAP Dictionary cleanup; or the program references a database synonym or view that no longer exists.
Check SE11 for the table name. If the table exists in the Dictionary, check its activation status — if inactive, activate it. If it is active in the Dictionary but the physical table is missing, use SE14 (Database Utility) to adjust the table in the database. Check STMS to confirm whether the transport carrying the table arrived before the transport carrying the program that references it.
Quick Info