The system always checks whether optimized operations can be performed in the SAP HANA DB or the BWA for the InfoProvider that the selected query is based on. If you are using a MultiProvider, the system checks each InfoProvider it contains.
The following options are available:
If you do not want the system to use optimized operations in the SAP HANA DB or the BWA for the selected query, choose this option. This may be necessary, for example, if queries use virtual characteristics or key figures and the calculations of these characteristics or key figures depend on a specific summarization level. If optimized operations are executed in SAP HANA or in BWA in these cases, then this can lead to unexpected results. The system displays a warning message to inform you of this. If the option No optimized operations in SAP HANA/no BWA is selected, the system then reads the data for calculating the virtual characteristics or key figures directly from the database in the relevant summarization level.
If the obsolete field Do not use BWA: There are virtual chars/key figures is selected (see SAP Note 1161525 ) before an upgrade to SAP NetWeaver 7.3 or higher, the system makes the setting No Optimized Operations in SAP HANA/No BWA after the upgrade.
To switch from what was previously Optimized Access (3) in BWA to the new Individual Access per InfoProvider mode (2), you can use report RSDG_MPRO_CHANGE_TREXOPS. When this report runs, all MultiProviders that currently have mode "3" are switched to mode "2". This is performed for modified versions and for active ones too. There is also the option of having all BI Content objects modified too.
If the mode has been changed manually, this manual setting can still be used - regardless of whether this was done in the query or directly in the InfoProvider.
If virtual characteristics or key figures are used in the query, a warning appears.
If it is not possible to use optimized operations for some of the InfoProviders contained in a MultiProvider, the system reads these InfoProviders without optimized access and temporarily copies the data read in them to the SAP HANA DB or BWA.
If the exception aggregation cannot be calculated in the SAP HANA DB or in the BWA because of the functionality used, the Optimized Access (3) option is used.
Calculation of exception aggregation in the SAP HANA DB or BWA is possible for the following exception aggregations:
Exception aggregation cannot be calculated in the SAP HANA DB or BWA for a single key figure if this key figure uses one of the following functions:
Exception aggregation cannot be calculated in the SAP HANA DB or BWA for a query if this query uses one of the following functions:
If it is possible to calculate an exception aggregation in the SAP HANA DB or BWA, the following calculations are performed in the SAP HANA DB or BWA even if they are not in an exception aggregation: