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

DELETE dbtab - target

Short Reference

Syntax

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


Alternatives:

1. ... dbtab

2. ... (dbtab_syntax)

Addition:

... CLIENT SPECIFIED

Effect

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

Alternative 1

... dbtab


Effect

A database table or view defined in ABAP Dictionary can be specified for dbtab.

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

Alternative 2

... (dbtab_syntax)


Effect

Instead of static specification, a parenthesized 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 row type can be specified for the data object dbtab_syntax. The syntax in dbtab_syntax is, as in ABAP Editor, not case-sensitive.

Security Note

If used wrongly, dynamic programming techniques can present a serious security risk. Any dynamic content that is passed to a program from the outside must be checked thoroughly or escaped before being used in dynamic statements. This can be done using the system class CL_ABAP_DYN_PRG or the predefined function escape. See SQL Injections Using Dynamic Tokens.

Addition

... CLIENT SPECIFIED

Effect

This addition deactivates automatic client handling in Open SQL. If the addition CLIENT SPECIFIED is used, the client ID specified in source is respected. Without the addition CLIENT SPECIFIED, the ABAP runtime environment does not pass the client ID specified in source to the database system, but passes the ID of the current client instead.

Notes