Documentation View

We are hiring and constantly growing! Have a look through our vacancies to find the right role for you!

ABAPMODIFY_DBTAB_OBSOLETE - MODIFY DBTAB OBSOLETE

ABAPMODIFY_DBTAB_OBSOLETE - MODIFY DBTAB OBSOLETE

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

MODIFY dbtab, VERSION

Short Reference



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

Effect

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

The addition VERSION dictates that the database table or view dbtab is not processed, and the table whose name is made up of "T" and the content of vers is processed instead. vers expects a data object with a maximum of four characters, of type c. The row content is still taken 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 follow the naming conventions specified above.

Notes

  • The addition VERSION is not allowed in classes. Instead, the database table or view should be specified 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.





rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 2467 Date: 20230207 Time: 213957     sap01-206 ( 47 ms )