SCN Wiki upgrade to version 6.13 on Tuesday 19.11.2019 - beginning 07:30 am CET

During upgrade process new content will not be transported to new Wiki version

Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

The Database Utility [Transaction SE14]  is the interface between the ABAP Dictionary and the relational database underlying the R/3 System.

You can use the database utility to edit all the database objects that are generated from objects of the ABAP Dictionary. These are database tables that are generated from transparent tables or physical table pools or table clusters, indexes, database views.

It is mainly used when a  table is changed in the ABAP Dictionary.At that time,we must ensure that the database structure of the table is adjusted to the change in the ABAP Dictionary during activation.

You can call the database utility from the initial screen of the ABAP/4 Dictionary(SE11) with Utilities -> Database utility or using T-code SE14.

The database structure of a table can be adjusted to its changed ABAP Dictionary definition in three ways:

  • By deleting and recreating the database table The table is deleted in the database. The revised version of the table is then activated in the ABAP Dictionary and created again in the database. Data in the table is lost during this process.
  • By changing the database catalog (ALTER TABLE) Only the definition of the table is changed in the database. Data in the table is retained. The indexes on the table might have to be rebuilt.
  • By converting the table . The database table is renamed and serves as a temporary buffer for the data. The revised version of the table is activated in the ABAP Dictionary and created in the database. The data is reloaded from the temporary buffer to the new database table (with MOVE-CORRESPONDING) and the indexes on the table are built.

The database utility provides a number of options for administering and monitoring requests for database modifications. You can perform these functions directly in the initial screen of the database utility.

You can:

  • Schedule jobs for mass processing
  • Display requests for mass processing
  • Display logs for mass processing
  • Display temporary tables without restart logs