Setting up Tables for Finding Objects

All assigned characteristic values for all class types are always saved to table AUSP. You can also save assigned values to generated tables. This lets you find objects more quickly.

To save the assigned values a second time, you generate a table for the class. The table contains all characteristics that are defined as index characteristics in the class, forming an index for these characteristics, to allow faster access to the assigned values.

The names of the tables are saved to system tables GEN_TABLES_MAIN and GEN_TABLES_SUB.

• On the Char. tab of the class, the Index relevant indicator is set for each characteristic you want to include in the generated table.

• The characteristics used are all assigned to the class. Inherited characteristics are ignored. This means that you may need to assign a characteristic to several classes in a class hierarchy, even though it is inherited.

• Settings in Customizing:

In the Implementation Guide (IMG) for cross-application components, choose  Classification System   Classes   Maintain Object Types and Class Types.  Select the relevant table and choose Class Types. Double-click on the relevant class type to go to the details, where you ensure that the following settings are defined:

• Generated tables must be selected.

• Multiple objs allowed must be selected.

• ECH (parameter) must notbe set.

1. From the classification menu, choose  Environment  Reorganization  Set Up Tables for Search. 

2. Enter the class type and the class for which you want to create a table. The valid-from date is only relevant if the characteristics or class have been processed with engineering change management.

3. Choose Execute to generate and fill the table.

Restrictions

• Table generation cannot be used for variant class types (class type 300).

• You can select up to 12 characteristics per table for finding objects.

• You can select reference characteristics, but the search can only use the reference characteristics if data is stored redundantly in table AUSP (for example, batches).

• If you change existing index characteristics or create new index characteristics in characteristics management, you must regenerate the table to avoid inconsistencies.