Comments
ABAP OPEN SQL TARGET Statement syntax, information and example SAP source code
INCLUDE
ABAP Syntax
[ CONNECTION con|(con_syntax) ] ... .
ABAP_ALTERNATIVES:
1 ... dbtab
2 ... (dbtab_syntax)
ABAP_ADDITION:
... CLIENT SPECIFIED
What does it do? The entries in target determine, statically or dynamically, which database table or which view is accessed, and control client handling .
ABAP_ALTERNATIVE_1 ... dbtab
What does it do? 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.
ABAP_ALTERNATIVE_2 ... (dbtab_syntax)
What does it do? 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. See SQL Injections Using Dynamic Tokens .
ABAP_ADDITION ... CLIENT SPECIFIED
What does it do? 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.
Latest notes: Since each client represents a complete unit, automatic client handling should never be turned off in application programs. This is checked by the ABAP runtime environment in multitenancy systems.
(See also Cross-Client Database Access
).
Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved
