Ansicht
Dokumentation

ABAPUPDATE_TARGET - UPDATE TARGET

ROGBILLS - Synchronize billing plans   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

UPDATE 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:

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.

Example

Modifies a row in a different client. The first UPDATE statement shows the recommended method with the addition USING CLIENT. In the second UPDATE statement, automatic client handling is disabled using CLIENT SPECIFIED and the client field must be filled explicitly.

DELETE FROM demo_update CLIENT SPECIFIED.
INSERT demo_update USING CLIENT '800'
       FROM @( VALUE #( id = 'X' ) ).

UPDATE demo_update USING CLIENT '800'
       FROM @( VALUE #( id = 'X' col1 = 100 ) ).

DELETE FROM demo_update CLIENT SPECIFIED.
INSERT demo_update CLIENT SPECIFIED
       FROM @( VALUE #( client = '800' id = 'X'  ) ).

UPDATE demo_update CLIENT SPECIFIED
       FROM @( VALUE #( client = '800' id = 'X' col1 = 100 ) ).

PERFORM Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 5072 Date: 20240423 Time: 130545     sap01-206 ( 67 ms )