Operations in SAP HANA/SAP NetWeaver BW Accelerator

The system always checks whether optimized operations can be performed in the SAP HANA or the SAP NetWeaver BW Accelerator for the InfoProvider that the selected query is based on.

If you are using a MultiProvider or CompositeProvider, the system checks each InfoProvider they contain.

The following options are available:

• No optimized operations in SAP HANA/no SAP NetWeaver BW Accelerator (0)

  If you do not want the system to use optimized operations in the SAP HANA or the SAP NetWeaver BW Accelerator 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 SAP NetWeaver BW Accelerator 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 HANASAP HANA/no SAP NetWeaver BW Accelerator (0) 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.

  Note

  If the obsolete field Do not use SAP NetWeaver BW Accelerator: 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 SAP NetWeaver BW Accelerator (0) after the upgrade.

• Individual Access per InfoProvider (2):

  This is the standard option for optimized access to the SAP NetWeaver BW Accelerator. You can also choose the Individual Access per InfoProvider (2) option manually if using the SAP HANA database. The SAP HANA or the SAP NetWeaver BW Accelerator are used with this option as with the Optimized Access (3) option.

  For CompositeProviders or MultiProviders however, a separate access is made for each participating InfoProvider.

  Note

  To switch from what was previously Optimized Access (3) in SAP NetWeaver BW Accelerator 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.

  Caution

  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.

• Optimized Access (3):

  For CompositeProviders or MultiProviders, joint optimized access is made to all participating InfoProviders.

  Note

  If virtual characteristics or key figures are used in the query, a warning appears.

• Exception Aggregation (Standard) (6): This is the standard option for optimized access to the SAP HANA. You can also calculate the exception aggregation in the SAP NetWeaver BW Accelerator.
  Note

  If it is not possible to use optimized operations for some of the InfoProviders contained in a CompositeProvider or MultiProvider, the system reads these InfoProviders without optimized access and temporarily copies the data read in them to the SAP HANA or in the SAP NetWeaver BW Accelerator.

  If the exception aggregation cannot be calculated in the SAP HANA or in the SAP NetWeaver BW Accelerator because of the functionality used, the Optimized Access (3) option is used.

• Formulas calculated in the SAP HANA (7): This option allows you to calculate formulas with exception aggregation in the SAP HANA. This requires SAP HANA 1.0 SP11 (or higher). In addition, all prerequisites that apply to the option Exception Aggregation (Standard) (6) must be fulfilled. Formula calculation after aggregation is also supported.