Symptom
You are using SAP HANA as database for SAP BW or an BW Accelerator
and you would like to understand the OLAP push down functionalities.
Other Terms
OLAP runtime, Performance, OLAP engine, HANA optimized query runtime
Reason and Prerequisites
You are running an SAP BW system starting with SAP BW 7.0 with an BW
Accelerator or starting with SAP BW 7.3 and SAP HANA as database. The
defined query operations are defined via standard functionalities and
are not custom written ABAP exits. In the query properties the
operations in BWA/HANA is set to "6 - Operations in BWA/HANA".
Solution
With SAP HANA as database for SAP BW it is possible to optimize many
different OLAP operations. In a few cases the same applies for BW
Accelerator.
For certain operations the Analytic Manager generates a so called “calculation scenario” within SAP HANA. Due to this it is possible to push down the data intensive operations to SAP HANA and to avoid data transfer as well as materializations in the application server, which will speed up the query runtime. In general this is offered for standard OLAP functionalities; if you use ABAP logic in custom exits it is not possible to push the calculations down to SAP HANA.
The list below indicates which operation is been optimized in combination with the starting release.
*BWA functionality is fully covered by SAP HANA, not vice versa
For certain operations the Analytic Manager generates a so called “calculation scenario” within SAP HANA. Due to this it is possible to push down the data intensive operations to SAP HANA and to avoid data transfer as well as materializations in the application server, which will speed up the query runtime. In general this is offered for standard OLAP functionalities; if you use ABAP logic in custom exits it is not possible to push the calculations down to SAP HANA.
The list below indicates which operation is been optimized in combination with the starting release.
Analytic Manager operation |
Release* |
Aggregation |
BW 7.0 + BWA 7.00 |
Cell-based calculations (FEMS) |
BW 7.0 + BWA 7.00 |
Hierarchy-processing (part 1) |
BW 7.0 + BWA 7.00 |
MultiProvider-UNION |
BW 7.3 + BWA 7.20 |
Exception aggregation COUNT |
BW 7.3 + BWA 7.20 |
Exception aggregation for keyfigures w/o currency/unit conversion |
BW 7.3 + BWA 7.20 |
Exception aggregation for keyfigures w/ currency conversion |
BW 7.3 + BWA 7.20 |
Exception aggregation for keyfigures w/ unit conversion without reference InfoObject |
BW 7.3 + BWA 7.20 |
Time-dependent currency conversion |
BW 7.3 (SP10) on HANA |
Avoid intermediate result set materialization (Layer ”Q” virtualization) |
BW 7.4 (SP05) on HANA |
“Current member” calculation |
BW 7.4 (SP05) |
CompositeProvider (e.g. JOIN between fact data) |
BW 7.4 (SP05) on HANA |
Stock coverage keyfigures |
BW 7.4 (SP06) |
Unit conversion with Reference InfoObjects (see SAP Note 2001947 to switch off) |
BW 7.4 (SP08) on HANA |
Parts of Handling of inventory keyfigures (see SAP Note 2001947 to switch on) |
BW 7.4 (SP08) on HANA |
Leverage HANA hierarchy processing |
BW 7.5 (SP01) on HANA |
List-based calculations (like conditions) |
under discussion |
Time-Series calculations |
under discussion |
Temporal Hierarchy JOIN |
planned |
Internal Business Volume elimination |
under discussion |
Formula exception aggregation for non-dimensional keyfigures |
planned |
Formula exception aggregation |
planned |
Header Data
Released On | 16.11.2015 08:48:41 |
Release Status | Released for Customer |
Component | BW-BEX-OT OLAP Technology |
Priority | Correction with medium priority |
Category | Consulting |
No comments:
Post a Comment