Skip to content

ABAP Keyword Documentation →  ABAP - Reference →  Processing External Data →  ABAP - Database Accesses →  Open SQL →  Open SQL - Write Accesses →  DELETE dbtab 

DELETE dbtab - target

Short Reference

Other versions: 7.31 | 7.40 | 7.54


... {dbtab|(dbtab_syntax)} [CLIENT SPECIFIED] 
                           [CONNECTION {con|(con_syntax)}] ... .


1. ... dbtab
2. ... (dbtab_syntax)




The entries in target determine, statically or dynamically, which database table or which view is accessed, and control client handling.

Alternative 1

... dbtab


For dbtab, a database table defined in the ABAP Dictionary or a view defined in the ABAP Dictionary can be specified.

Only views that refer to a single database table, and whose maintenance status in the ABAP Dictionary permits change access can be specified.

Alternative 2

... (dbtab_syntax)


Instead of static specification, a bracketed data object dbtab_syntax can be specified, which must contain the name of the database table or the view when the statement is executed. A character-like data object or a standard table without secondary table keys and with a character-like line type can be specified for the data object dbtab_syntax. The syntax in dbtab_syntax is, as in the ABAP Editor, not case-sensitve.




This addition deactivates the automatic client handling of Open SQL. If the addition CLIENT SPECIFIED is used, the client identifier specified in source is taken into account. Without the addition CLIENT SPECIFIED, the ABAP runtime environment does not transfer the client identifier specified in source to the database system, but transfers the identifier of the current client instead.


Since each client represents a self-contained unit, automatic client handling should never be turned off in application programs. In systems that support multitenancy, this is ensured by the ABAP runtime environment.