Structure of the TMS Index

For the fast localisation of individual objects in CTS requests and tasks, Conigma uses special indices. These have to be built up after the initial installation of Conigma. Depending on the age of the SAP system and the extent of changes made in the system, this process can take several hours. The continuous updating of the indices is done automatically by Conigma. Since only deltas not yet included in the index are processed here, this process does not normally involve any noticeable waiting time.

Procedure

Make sure that your user is assigned to the Conigma user role /GAL/CCM_CONIGMA_USER as well as the Conigma administrator role /GAL/CCM_CONIGMA_ADMIN. Execute the report /GAL/TMS_INDEX_BUILDER using transaction SA38 (or SE38). The following selection screen is then displayed:

If some of the indices have already been built up in the past, the option "Update" is activated and pre-selected for the indices concerned. If these indices are to be deleted and rebuilt, the option "Rebuild" must be explicitly activated. If you want to exclude a certain index from consideration, select the option "No action" for this index.

Normally, the automatically determined pre-selection should lead to the desired result, so that the report can simply be started via the menu item Programme -> Run in background or via the F9 key. If possible, do not start this report in the foreground, as this usually leads to a program abort due to runtime overrun.

Special Options 

To avoid problems with very large systems, the observation of historical data can be divided into small blocks for indices 1 and 2. In the default setting, the changes in periods of 365 days are considered in each case. Reducing this interval leads to a shortening of the period of use of individual database cursors, but also to a higher runtime. Increasing this interval can shorten the runtime, but can lead to problems due to the high usage periods for individual database cursors. The maximum size of database transactions can be limited to a certain number of data records. The default setting here is 10,000 data records. Since index 03 generally contains only a small number of data records, the two options for this are not useful.

When rebuilding one or more indices, existing data records may have to be deleted from the corresponding index tables. This is normally done in the present report with the help of a DELETE command via the standard ABAP Open-SQL interface. With very large tables, this can lead to long runtimes or terminations on the database side. In this case, the option "TRUNCATE for table emptying" can be used to activate the emptying of the relevant tables via native database SQL. The exact implementation (TRUNCATE or DROP … CREATE …) depends on the supported command set of the database used.

We recommend that you only adapt these options after consulting our product support.