Transaction codes for Database and Table handling

In this part of series, I am going to describe several original SAP transaction codes (reports and utilities) for handling tables and database.


This post is part of series about SAP transaction codes for ABAP Developers:

  1. Basic SAP transactions for ABAP developers
  2. How to modify and extend SAP applications
  3. Transaction codes for database and table handling
  4. How to analyse, debug and optimize your SAP programs with standard tools

Basic transactions for table management SE11 – ABAP DictionarySE16 – Data BrowserSE54 – Generate Table Maintenance are described in the first post of the series. Just to remind you, se11 is used for managing dictionary objects including database tables, se16 is used for browsing the data in a database table and finally se54 is used creating maintenance views where you can manage that data.

Apart from these basic transaction codes, there are several more advanced utilities which are used for specific database operations. Those transaction codes(t-codes) are as following.

SE14 – Database utility

Whenever you change the structure of a table which is derived from ABAP dictionary object (transparent table, physical table pool, table cluster, indexes or database views) , you also need to run the database utility in order to synchronize changes between ABAP Dictionary and database layer. Moreover, this utility allows you to maintain terminated conversions, administer modification requests and manage incremental conversions.

se14

SE16n – Table display

Transaction SE16N is actually an improved and more user-friendly data browser SE16 with ALV data grid. Until EHP5, it was possible to enter code &SAP_EDIT and edit data inside of tables, but due to security risk, this option is not available anymore. Anyway, there is still an option to turn on edit mode using debugger.

se16n

SM30, SM31 – Generate table maintenance dialog

Transaction SM30 allows you to run generated dialog where it is possible to view and change data in database tables and views. Those database objects must have set up the option Display/Maintenance allowed in ABAP Dictionary table management and have already generated table maintenance via SE54.

Transaction SM31 refers to the same program which SM30 does, so there is no difference between this transaction. The old SM31 transaction is available as transaction SM31_OLD.

sm30

DB02 – Database analysis

DB02 is a database analysis tools which displays various statistics of database and database objects. The purpose of this tool is to check whether there are missing indexes in database tables and check consistency of database objects.  Moreover, this tool can give you overview of data area occupancy (available/occupied space) of the whole database.

db02

 

That’s all from database maintenance, when you miss any transaction, let me know in comments.

 

 

Peter Marcely

ABAP, Python, JavaScript developer