SAP Netweaver Business Intelligence BI / BW

Symptom

A query that has a numeric variable with a replacement path attribute takes a long time to run. Large volumes of data are processed both in the data manager and in the online analytical processing (OLAP) processor.

Other terms

Query, FAGGR, replacement path

Reason and Prerequisites

The OLAP processor must read the data so that the reference characteristic of the relevant attribute is drilled down (see also Notes 1228378 and 1385580; you can display these required drilldowns by choosing RSRT -> Technical Information -> Not Visible Drilldown Characteristics).

Solution

Logic was implemented in Release 3.X so that this background drilldown is only carried out if the variable is used in a basis formula (FST_K, see Note 379832). Since this implicit switch is very difficult to control and to understand, it is no longer supported as of Release 7.0, and an automatic drilldown is always carried out.
As of Release 7.0, however, the system contains a replacement path hierarchy attribute, and such a numeric variable is always replaced after the aggregation (see Notes 1385580 and 1384942).
Therefore, you can decide between the following:
1. The numeric variable is always replaced if you select the option of replacement path from attribute (FLAGR=’4′). However, this may negatively affect performance, memory space, and runtime. This corresponds to the 3.x case if the attribute variable is used in a basis formula (FST_K).2. The numeric variable is only to be replaced if the reference characteristic is drilled down or explicitly filtered. The replacement then has almost no negative effects, but in all other cases, it delivers a NOT_EXIST. This corresponds approximately to the 3.x case if the attribute variable is used in a formula element (FST_F). You achieve this if you select the option to replace with hierarchy attribute (FLAGR=’6′) in the replacement path.