SAP ABAP Data Element RSRTREXOPS (Operations in SAP HANA/BWA)
Hierarchy
☛ SAP_BW (Software Component) SAP Business Warehouse
   ⤷ BW-BEX-OT (Application Component) OLAP Technology
     ⤷ RSROA_MISC (Package) OLAP: Various
Basic Data
Data Element RSRTREXOPS
Short Description Operations in SAP HANA/BWA  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type RSRTREXOPS    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 BWA Ops 
Medium 20 SAP HANA/BWA Ops 
Long 40 Operations in SAP HANA/BWA 
Heading 55 Operations in SAP HANA/BWA 
Documentation

Definition

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

Use

Dependencies

Example

History
Last changed by/on SAP  20141013 
SAP Release Created in 730