Operations in BWA 

To decide which analytic operations the system will perform in the SAP HANA database or on data indexed in SAP NW BWA in SAP NetWeaver BWA, you can make the relevant settings in the query property Operations in 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 Business Warehouse Accelerator. 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 there is a BWA index for the InfoProvider underlying the selected query. It also checks whether this BWA index can be used. If you are using a MultiProvider, the system checks each InfoProvider it contains.

If there are BWA indexes that can access the selected query, you can decide whether and for what purpose the system should use the BWA indexes (see Query Properties and Creating and Managing BWA Indexes in the BW System).

Choose one of the following options:

●      No operations in BWA: If you do not want the system to use a BWA index for the selected query, choose No Operations in 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 Operations in 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 via its BWA index.

●      Standard: The BWA index is used in the standard setting. For MultiProviders, the BWA indexes of all participating InfoProviders are accessed in one go.

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

●      Exception aggregation: You can also calculate exception aggregation (see Aggregation) in BWA.

If a MultiProvider is being used for part of the InfoProviders, and no BWA index can be used, the system reads these InfoProviders without BWA and copies their data to the BWA temporarily.

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

If Counter for All Detailed Values is selected for exception aggregation in the BWA, exception aggregation is performed for all key figure types. Otherwise, it is only performed for key figures without a unit or key figures with a fixed unit.

Calculating exception aggregation for a single key figure in BWA is not possible if the 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

Calculating exception aggregation for a query in BWA is not possible if the 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

If the system cannot calculate the exception aggregation in BWA because of the functions used, it uses the Standard option instead.