Query Properties 

Use

In the Query Properties dialog box in the query monitor, you can specify the following data for a BEx query: the read mode, the cache mode, the selection of structure elements and the optimization mode. You can deactivate the default Parallel Processing for queries on a MultiProvider. For queries with virtual characteristics or key figures, you can activate cache use, which is deactivated by default. You can also deactivate the SAP NetWeaver Business Warehouse Accelerator, which is used by default. If you select the Generation Log indicator, when you choose the Generation Log pushbutton in the query monitor, you can display a log in which reasons why the query was regenerated are listed.

Prerequisites

You have created the relevant query in BEx Query Designer. The settings specified in Customizing for the InfoProvider that the query is based on, or the settings specified earlier in the Query Monitor, are applied to the query.

Procedure

Specifying Default Settings for an InfoProvider

In the InfoProvider maintenance transaction, default settings for query and cache-specific settings are made for an InfoProvider. To do this, choose Extras ® InfoProvider Properties ® Display or Change ® Query/Cache tab (transaction code RSDIPROP).

More information: InfoProvider Properties.

The property from the InfoProvider properties is applied to the query by default. The InfoProvider Setting option is then selected for the relevant property in the Query Properties dialog in the Query Monitor.

If the setting is changed on the InfoProvider, this change is applied to all queries where the InfoProvider Setting option is selected for the relevant property.

If you do not want this as the default setting, you can set the property explicitly by deselecting the option InfoProvider Setting and then configuring the required property for the relevant query.

Some options are always available, while others are only available for queries based on certain InfoProviders.

Changing Read and Cache Mode for Existing Queries

For InfoProviders whose data cannot be changed in the BW system (such as VirtualProviders and DataStore objects for direct update), you can specify the cache validity - i.e. the data retention period -in the cache.

You can change the InfoProvider-specific settings again in the Data Warehousing Workbench by choosing Current Settings in Administration.

In the Query Monitor, you can change the standard settings for the read mode (see Read Mode) and cache mode (see Cache Mode) for existing queries. You can only specify the cache validity for InfoProviders in Customizing.

Specifying the integrity of the data and access to the data stored in the near-line storage

The settings are usually configured in Query Designer.

These query properties were set in the back end prior to Release SAP NetWeaver 7.3, but now need to be set in BEx Query Designer. If you have upgraded from BW 3.5 to BW 7.3, you now have to upgrade your front end to Release SAP GUI 7.10 Patch 5 to be able to work with these settings.

The same applies if you have upgraded form BW 7.0 to BW 7.3 and still used Query Designer (SAP BW 3.x) in Release 7.0 .

You only need to configure the setting (in the Query Monitor ) for standard queries with names with the format InfoProvider/!InfoProvider, in other words, names that contain at least an “!’’.

●      By selecting the setting Data Integrity(previously also known as request status), you can specify up to which request the data should be included for the selected query.

●      If data has been stored in the near-line storage for the selected query, you can set the indicator Read Near-Line Storage As Well.

Note that you cannot set any variables for the settings made in the Query Monitor.

For more information on individual settings and how to configure settings in Query Designer, see Specifying Data Integrity and Reading Stored Data.

Using the Delta Cache Process

When the data basis changes, you can optimize the cache performance for suitable InfoProviders using the delta cache process (see Activating Delta Caching); you can also optimize the cache performance for queries based on MultiProviders by specifying a grouping (see Specifying the InfoProvider Grouping for Delta Caching).

Use Selection of Structure Elements

The Use Selection of Structure Elements option influences system performance. This function should therefore normally be activated. It does not have any affect on the data displayed. Technically speaking, the system only passes to the database the selections and key figures of the columns (or structure elements, to be more precise) currently used to filter the query. If you deactivate this function, the data is read for the entire structure or for both structures from the database. Therefore this function cannot be activated if the query has the read mode 'A' (see Read Mode).

You can expect a significant improvement in performance from using this function in the following scenarios:

●      You are using SAP NetWeaver BW Accelerator.

●      You are using queries that contain a large number of selections or restricted key figures, which are not all displayed in the initial drilldown.

●      You execute a lot of operations where you filter using selections or restricted key figures, such as the function Filter and Drill Down By.

Deactivating this function does not normally bring any advantages.

Calculating with High Accuracy

By setting a specific accuracy, you decide which number format is used internally for calculating key figures. The level of calculation accuracy can be set in the InfoObject maintenance transaction for each key figure (system-wide), and in the query monitor for all key figures of a query (see Calculating with High Accuracy).

Deactivating Parallel Processing

A query based on a InfoProvider is split internally into subqueries. These are automatically processed in parallel. In most cases, parallel processing improves performance. In some cases however, query performance can be better improved by using sequential processing (see Processing Queries).

You can deactivate parallel processing for a query based on a MultiProvider in the Query Monitor. (See Not Using Parallel Processing.)

You can deactivate parallel processing for MultiProviders on the screen InfoProvider: Edit Properties (transaction code RSDIPROP).

Operations in BWA

To decide which operations the system will perform in the SAP HANA database or on data indexed in SAP NetWeaver Business Warehouse Accelerator in SAP NetWeaver BWA (see Creating and Managing BWA Indexes in the BW System), you can make the relevant settings in the query property Operations in BWA.

If the system is operated with an SAP NW BWA to improve performance when running queries, the system checks in each case if there is a BWA index for the InfoProvider that the query is based on, and whether it can be used. If you are using a MultiProvider, the system checks each InfoProvider it contains.

More information: Operations in BWA.

Query as InfoProvider

On the Query Properties screen in Query Monitor, you can stipulate whether the selected query should be used as an InfoProvider.

This setting makes it possible to perform high-performance analyses, especially on queries that are simple but contain a very large amount of data, i.e. over a million cells.

You can still index data from all InfoProviders based on the query using query snapshots in SAP NetWeaver Business Warehouse Accelerator (see Creating and Managing BWA Indexes in the BW System and Indexing BW Data in SAP NetWeaver BW Accelerator). You can get an overview of the BWA Indexes in the system for the query snapshot by pressing Query as InfoProvider in BWA Index Maintenance (transaction RSDDB). The system uses a BWA index for a query snapshot when its timestamp is not older than the InfoProvider that the query is based on (see BWA Index Settings Tab Page).

The following are two scenarios for using a query as an InfoProvider:

●      You can use a query as the data source for an analysis process and use SAP NetWeaver Analysis Process Designer to create analytical indexes on it (see Data Sources for an Analysis Process).

●      You can use a query - especially if it contains mass data – over the Analytic Server’s relational interface as a data source for the SAP BusinessObjects Data Federator (see Data Federator) and perform analyses with this, for example in SAP BusinessObjects Web Intelligence.

If you want to use the selected query as an InfoProvider, set the relevant flag. The system checks whether this is possible. Press  to call the Display Logs dialog box. The system displays whether the selected query can be used as an InfoProvider.

For more information about the conditions for using query as an InfoProvider, see Query as InfoProvider.

Generation Log

This function is used for test and support purposes. In certain cases, queries have to be generated again. If the Generation Log option is selected, the system writes entries to the application log. These entries provide information on why the query was generated again.

Specifying the Optimization Mode

This setting describes how to optimize the memory requirements of the OLAP processor.

If you do not make any other settings, the OLAP processor defines the optimal memory requirements for the data processed in the OLAP processor. This is done after the query is first executed and again after a period of 31 days since the last optimization. A report is generated automatically.

You can implement, modify, or deactivate this function in the Query Properties dialog box in Query Monitor. Choose one of the following options:

●      Query Will Be Optimized after Generation (0): Default setting

●      Query Optimization with Individual Periods in Days(1) You can specify the optimization period as required. You can use this setting if the InfoCube data is periodically fully reloaded or rebuilt.

●      Query Optimization Inactive (9): This setting is usually only used for test and support purposes or in exceptional cases.

More information: SAP Note 1137994.

Permitting Cache Use Despite Virtual Characteristics and Key Figures

The calculation of the virtual characteristics or key figures is usually dependent on variable sizes. This means that the query result is not always the same.

Calculating age based on date of birth and current date.

Therefore if virtual characteristics or key figures are used in the query, the cache is deactivated. If the virtual characteristics or key figures that you use display the same result for every calculation, you can activate the cache by choosing the option Cache Use Despite Virtual Characteristics/Key Figures in the Query Monitor.

Do Not Use BWA Index due to Virtual Characteristics/Key Figures

In the default setting, the BWA index is also used for queries with virtual characteristics or key figures.

If these characteristic or key figure calculations are not dependent on a specific summarization level, using the SAP NetWeaver BW Accelerator can produce unexpected results. To avoid this, you can select this option. The system then reads the data for calculating the virtual characteristics or key figures directly from the database in the relevant summarization level.

Statistics Details

The system displays the Detail Level setting for BEx query runtime statistics as set in the maintenance of statistics properties (transaction RSDDSTAT) for the Query object type (for more information, see Maintenance of Statistics Properties and the section Statistics Detail Level for the Query Object Type).