Database-dependent and disabled indexes


In the past, indexes defined in the ABAP Dictionary were normally created on the database during activation. It was not possible to deliver a disabled index without it automatically also being created on the database.

This function is required for indexes which are only meaningful for certain applications and for which the customer must decide (with the appropriate customizing support) whether or not the index should be brought to the database.

There are also some indexes which were only defined for certain database systems. Such indexes can now be defined in the ABAP Dictionary in the usual manner.

When you maintain an index in the ABAP Dictionary, you can define whether the index should be defined and if so, on which database systems.

The following settings are possible:

When an index is activated in the ABAP Dictionary, this information is analyzed. The index is only created on the database if this is allowed for the database system being used. Otherwise the index will be active in the ABAP Dictionary, but not created on the database.

With this function you can disable an index in the customer system without changing its definition in the ABAP Dictionary. The option 'Do not create index on the database' should be chosen in this case. If the index is then activated in the ABAP Dictionary, the corresponding database index is deleted.


This function is only allowed for non-unique indexes. Since the function of these unique indexes is to exclude duplicate entries of the index fields in addition to increasing performance, you may not disable such indexes.