Ansicht
Dokumentation
ABAPDELETE_TARGET - DELETE TARGET
PERFORM Short Reference PERFORM Short ReferenceThis documentation is copyright by SAP AG.
DELETE dbtab - target
Syntax
... {dbtab|(dbtab_syntax)} [CLIENT SPECIFIED]
[CONNECTION {con|(con_syntax)}] ... .
Alternatives:
1. ... dbtab
2. ... (dbtab_syntax)
Addition:
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:
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)
Effect:
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.
Addition
... CLIENT SPECIFIED
Effect:
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.
Note
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.
-
A DELETE statement with the addition CLIENT SPECIFIED that does not specify which rows are deleted deletes the data of all client in a client-specific table.
Example
The following two DELETE statements produce the same result. The first statement uses the addition USING CLIENT to show the variant recommended for accessing a particular client. The second statement, on the other hand, uses CLIENT SPECIFIED to disable automatic client handling, which means it has to contain a WHERE condition for the client field.
DELETE FROM demo_expressions USING CLIENT '800'
WHERE id = 'X'.
DELETE FROM demo_expressions CLIENT SPECIFIED
WHERE mandt = '800' AND id = 'X'.
rdisp/max_wprun_time - Maximum work process run time SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 4942 Date: 20240329 Time: 031510 sap01-206 ( 72 ms )