ABAPDELETE_DBTAB_OBSOLETE - DELETE DBTAB OBSOLETE

CPI1466 during Backup   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

DELETE dbtab, VERSION

DELETE ${ dbtab $| *dbtab $} VERSION vers.

Effect

This variant of the statement DELETE works essentially like the short form of the statement, but belongs, along with the addition VERSION, to the number of obsolete access statements, for which for dbtab, the name of a DDIC database table or a DDIC table view must be specified, beginning with "T" and comprising no more than five characters.

The use of addition VERSION means that the database table or view dbtab is not processed. Instead the table whose name is made up of "T" and the content of vers is processed. vers expects a data object with a maximum of four characters, of type c. The content of the key fields will continue to be obtained from the table work area dbtab or dbtab*. The statement is not executed if the database table or view does not exist or if it does not meet the name conventions specified above.

Notes

• The VERSION addition is not allowed in classes. Instead, specify the database table or view dynamically in its operand position in .

• None of the additions possible in can be specified with VERSION.

• The obsolete access statements do not support automatic client handling. The client identifier of a database table must be specified explicitly. The application programs are only to work with data for the current client. In systems with multitenancy, this is checked by the ABAP runtime environment.
  

Example

TABLES t100.
DATA vers TYPE c LENGTH 4.
...
vers = '100'.
...
t100-sprsl = 'E'.
t100-arbgb = 'BC'.
t100-msgnr = '100'.
DELETE t100 VERSION vers.

The syntax to be used instead reads:

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 2640 Date: 20230208 Time: 185555     sap01-206 ( 48 ms )