Skip to Content
author's profile photo Former Member
Former Member

BEX Query - Even more HANA optimized and faster with RSRT property ?

Hi out there on the globe,

I hope I can adress a real BW and HANA database Guru !

What feature of the HANA Database is used for opimizing or not optimizing
or exception aggregation
of a BEX Query ?

In the RSRT properties of a BEX Query
I wonder what HANA feature in detail is used to optimize or not optimize

a BEX Query with the settings of "Operations in BWA/HANA":

0-No optimized Operations in SAP HANA

3-Standard

6-Exception Aggregation

ThanXs a lot & Best !

Martin

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2014 at 06:09 AM

    Hi Martin,

    First Lets understand the Setting at RSRT side:

    Operations in SAP HANA/BWA

    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 (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 in the SAP HANA DB or BWA are possible for the InfoProvider that the selected query is based on. If you are using a MultiProvider, the system checks each InfoProvider in it.

    Choose one of the following options:

    • No optimized operations in SAP HANA/No BWA: If you want to prevent the system from using any optimized operations in the SAP HANA DB or BWA for the selected query, select 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 update to SAP NetWeaver 7.30 or higher, the system sets the No Optimized Operations in SAP HANA/No BWA option after performing the update.
    • Individual access for each InfoProvider (as in Release 7.0): SAP HANA DB and BWA are used as described under the Standard option. For MultiProviders though, a separate access is made for each participating InfoProvider.
    • Standard: In the default setting, optimized access to SAP HANA DB or BW is activated. If virtual characteristics or key figures are used in the query, a warning appears to inform you. For MultiProvider, joint optimized access is made to all participating InfoProviders.
    • Exception aggregation You can also calculate exception aggregation in the SAP HANA DB or BWA. If no optimized operations can be used for some of InfoProviders belonging to a MultiProvdier, these InfoProviders are read without optimized access, and their content is temporarily copied to the SAP HANA DB or BWA. If it is not possible to calculate exception aggregation in the SAP HANA DB or BWA due to the functionality used, the Standard option is used.
    • Exception aggregation in SAP HANA DB or BWA can be calculated for the following exception aggregations:
      • 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, 0 or errors:
      • Average
      • Average of values that are not null, 0, or errors
      • Calculating

    exception aggregation for an individual key figure in the SAP HANA DB or 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 aggregations for a query in the SAP HANA DB or BWA is not possible

    • if the 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 by the query either directly or indirectly (as an exception aggregation reference characteristic for example) and of which at least one is defined in such a way that the compound parent is supplied homogenously, and at least one of the participating InfoProviders does not contain the compound child. For more information about compounding problems, see SAP Note 1009987.
      • Virtual characteristics

    Operations at HANA side:

    BW / BEX Query Designer

    • is the design tool for the Analytic Manager

    Analytic Manager

    • has a wide variety of OLAP functions.
    • converts the query definition into a ABAP runtime object (BW Query)
    • Generates calculation scenarios for those BW Query operations which can be performed in HANA directly

    Pushing down BW Analytic Manager (OLAP) operations down to HANA provides

    • Excellent query performance
    • Additional business insights by overcoming existing ABAP based limits – deep granular data can now be analyzed (e.g. counters on order items level)

    OLAP Features pushed down to HANA in BW 7.3x

    •Hierarchy Handling Part I

    •Restricted key figures

    •Exception Aggregation CNT for quantity key figures without unit conversion

    •Exception Aggregation of currency key figures with optional currency conversion

    OLAP Features pushed down to HANA in BW 7.4 SP5

    •Processing of further query scenarios in HANA (Joins, Union, etc.)

    •Avoid intermediate result set materialization (e.g. Exception Aggregation)

    I think this answer might be helpful to you.

    Thanks & Regards

    A.Dinesh


    bex1.png (19.6 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 29, 2014 at 03:22 PM
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.