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:
- No Optimized Operations in SAP HANA/No BWA (0): If you do not want the system to use optimized operations in the SAP HANA DB or the BWA for the selected query, choose No Optimized Operations in SAP HANA/No BWA. 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.
- Individual Access per InfoProvider(2): This is the standard option for optimized access to the BWA. Each InfoProvider participating in a MultiProvider is accessed separately.
To switch from what was previously Standard mode (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.
You can also choose the Individual Access per InfoProvider option manually if you are using the SAP HANA database.
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.
- Standard (3): This is the standard option for optimized access to the SAP HANA DB. For MultiProviders, joint optimized access is made to all participating InfoProviders.
If virtual characteristics or key figures are used in the query, a warning appears.
- Exception Aggregation (6): You can also have the exception aggregation calculated in the SAP HANA DB or BWA.
If it is not possible to use optimized operations for some of the InfoProviders contained in a MultiProvider, these InfoProviders are read without optimized access, and the data read in them is temporarily copied to the SAP HANA DB or BWA.
If it is not possible to calculate the exception aggregation in the SAP HANA DB or BWA because of the functions used, the system uses the Standard option.
Calculation of exception aggregation in the SAP HANA DB or BWA is possible for the following exception aggregations:
- Counter for all detailed values
- Constants with exception aggregation total
- Multiple-dimensional exception aggregation total for a constant
- Counter for all detailed values that are not null, that are null or contain errors
- Average of values that are not null, that are null or contain errors
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:
- Non-cumulative key figures
- Key figures with elimination of internal business volume
- Virtual key figures
- Quantity conversion
- Formula calculation before aggregation
Exception aggregation cannot be calculated in the SAP HANA DB or BWA for a query if this query uses one of the following functions:
- Determination of time-dependent hierarchies for an event (temporal hierarchy join)
- MultiProviders with compound characteristics that are used either directly or indirectly by the query (as a reference characteristic for exception aggregation for example), at least one of which is defined in such a way that the compounding parent is supplied with homogenous data, but at least one of the contained InfoProviders does not contain the compounding child (compounding problem, see SAP Note 1009987 ).
- Virtual characteristics
- Artificial characteristic "currency/unitt" (1CUDIM)