Entering content frameBackground documentation Index Support for Drilldown Reports Locate the document in its SAP Library structure

In the section Index Support for Determination of Segment Numbers, we only looked at a single secondary index for the segment table intended to help the system find the profitability segment number for a given combination of characteristic values. In drilldown reporting and in other areas, however, the system queries the segment table in other ways. It therefore makes sense to support these queries with an appropriate secondary index as well.

Following the introduction of multipurpose summarization levels in Release 3.0C, the system should only need to access the segment table directly in rare instances. Still, it does need to read the segment table under the following circumstances:

Caution

If more than one index exists for the segment table, the optimizer of the database system may decide to use the "wrong" index. As a result, performance in finding segment numbers may worsen after you create a second secondary index. If this happens, check whether the right index (index ID 1) is being used. See also How to Check Whether an Index Is Being Used.

 

How to construct an efficient structure of secondary indexes for the segment table depends greatly on which database and which optimizer you use (rule-based or cost-based).

For detailed information about how to use summarization levels, see note 83204 in SAPNet.

If you are using report-specific summarization data in drilldown reporting, be sure to read note 21773 in SAPNet as well.

 

 

 

 

 

Leaving content frame