Operations in SAP
HANA/BWA
To decide which
analytic operations the system will perform in the SAP HANA database or on
data indexed in SAP NetWeaver Business Warehouse Accelerator NW BWA in SAP
NetWeaver BWA, you can make the relevant settings in the query property
Operations
in SAP HANA/BWA (for
information on how to use the various software components, see
Analytic Engine).
If you are using the SAP HANA database, the same parameters are relevant as when using any other database with a SAP NetWeaver BWA. The selection made for this query property therefore has the same effects on a SAP HANA DB as on a BWA.
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.
Choose one of the following options:
● No optimized operations in SAP HANA/no BWA: 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.
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.30 or higher, the system makes the setting “No Optimized Operations in SAP HANA/No BWA“ after the upgrade.
● Individual Access per InfoProvider: The SAP HANA database or BWA is used as described under Standard. If there is a MultiProvider however, each InfoProvider is accessed separately.
● Standard: In the standard setting, optimized access to SAP HANA DB/BWA BWA is activated. For MultiProviders, joint optimized access it made to all participating InfoProviders.
If virtual characteristics or key figures are used in the query, a warning appears to inform you.
● Exception aggregation: 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.
The following exception aggregations can be calculated in BWA:
○ Counter for all detailed values
○ Constants with exception aggregation total
○ Multiple-dimensional exception aggregation total for a constant
○ Total
○ Minimum
○ Maximum
○ Counter for all detailed values that are not null, that are null or contain errors
○ Average
○ 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)
○ MultiProvider 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
Additional Information
Creating and Managing
BWA Indexes in the BW System