The functions Create database table, Delete database table and Activate and adjust database are provided for transparent tables. To go to the Utilities for Database Tables screen, perform the following:
The Utilities for Database Tables screen appears.
To execute one of the functions described above (Create database table, Delete database table or Activate and adjust database), select the processing type and press the corresponding button.
The runtime object must already exist.
The system creates the table in the database with its active version and the primary index. The system also creates active secondary indexes in the database if this was not explicitly excluded when the index was defined (see Creating Secondary Indexes ).
The table and all its indexes are deleted from the database. The runtime object and all ABAP Dictionary sources remain.
The revised version of the table is activated and the database table is adjusted to this modified table definition. You can select the Save data or the Delete data radio button. With Delete data, the table is deleted in the database and created again with the new definition. Data in the table is lost. With Save data, the system attempts to perform an adjustment with an ALTER TABLE statement. If this is not possible, a table conversion is triggered.
Since pooled and cluster tables are not separate tables in the database, the functions Create database table and Delete database table are not applicable to these table categories. The Delete data function is offered instead. It deletes the table data from the corresponding physical table pool or table cluster.
Functions for Indexes
To go to the Utility for Database Indexes screen, open the Database Utility screen for the required object and choose Indexes. A list of all the indexes that exist for this Dictionary object appears. Select the required index by double-clicking it. The following functions are offered on the next screen:
Create a secondary index or the primary index of a transparent table in the database.
Delete a secondary index of a transparent table in the database.
The definition of the index in the ABAP Dictionary remains.
The primary index of a transparent table created in the database cannot be deleted as long as the table still exists in the database.
The index is deleted from the database. The revised version of the index is activated. After that the system creates the index and builds it again in the database.
The database utility also offers a number of check and repair functions for tables.
Storage Parameters that influence the database settings (such as extent sizes or partitioning) for the table can be maintained for transparent tables. You can display the corresponding maintenance screen with Storage Parameters.
You can compare the table definition in the database with the runtime object of the table by choosing Extras → Database object → Check. The indexes on the table in the ABAP Dictionary are compared with the indexes on the database. You can compare the runtime object of the table with the information entered in the ABAP Dictionary maintenance screen with Extras → Runtime object → Check. Both definitions are displayed. The differences found are highlighted. In both cases you can switch between a delta (only differences) or full (all information) display of the check results.
To check if the table contains data, choose Table → Data exists?. The system selects the data for all clients. This function is of use for example to check whether a table is empty prior to a conversion. You can display the data in the logon client by choosing Table → Table contents.
To list the structure of the table in the database and the indexes defined for the table, choose Extras → Database object → Display. This function is useful for database tables without an ABAP Dictionary definition.
To display the runtime object of the table, choose Extras → Runtime object → Display.
To display more information about interpreting the displayed data, choose .
You can trigger a table conversion with Extras → Force conversion. This function is useful, for example, if only the storage parameters of the table were modified, but the table structure was not changed. Some of the modified settings can only take effect in the database once the table has been converted.
A table conversion cannot be triggered with the Activate and adjust database function in this case because the table structure has not changed.
You can create a suitable runtime object for the database table by choosing Table → Reconstruct. This runtime object contains only the information about the table that is available in the database, such as the field name and data types. It does not contain other information about the table that exists in the ABAP Dictionary, such as specifications for buffering. Only user DDIC has the authorization to execute this function.
Use this function only to correct inconsistencies temporarily (if the database status and runtime object differ) and be sure to adjust the table in the usual way in the ABAP Dictionary and activate it there.