The SAP HANA/BWA Index Settings tab contains information on the last data modification (name of last user who made changes, date and time of last change) made to SAP HANA indexes for VirtualProviders and query snapshots.
If the SAP HANA index is for a query snapshot, the system displays the date and time of the last modification to the index in Data Modification, together with the date and time of the last modification to the InfoProvider that the query is based on. If the time stamp of the snapshot index is not older than the time stamp of the InfoProvider that the query is based on, the system uses the index at query runtime. Otherwise the data is read is from the query as an InfoProvider.
The Status screen area contains information on the status of the relevant index for reporting.
Under Status, you can find the following information:
The system indicates whether the SAP HANA index is assigned to a BW workspace.
In Edit mode, you can activate or deactivate the SAP HANA index of a VirtualProvider for access using queries.
The following areas are available for VirtualProviders:
The system indicates whether the SAP HANA index is activated or deactivated for access using queries.
In Edit mode, you can assign the SAP HANA index to a BW Workspace. If you choose , the system displays a list of all existing assignments. By double-clicking on a workspace, you can call BW Workspace Maintenance (transaction RSWSPW, see BW Workspace). You can also select the SAP HANA index here and assign it to the workspace.
The system shows the query behavior related to the index status. In Edit mode, you can specify how the query should behave when the relevant index is inactive or not available.
An index can be set to Inactive manually in SAP HANA/BWA Index Maintenance. An index can also be inactive temporarily, for example, if a data update has just been performed in the indexes when deleting a report. The index is then set to active again shortly afterwards.
An index does not exist if you have not created an index in SAP HANA/BWA Index Maintenance or you have deleted the index.
In Edit mode, you can use the Query Behavior Dependent on State of BWA Index option to specify how the query reacts if the associated SAP HANA index for a VirtualProvider is inactive or does not exist. You have the following options:
Query terminates if SAP HANA/BWA index is inactive or does not exist
If the SAP HANA index is inactive or does not exist, the query is terminated (NOBIANOQUERY = 'C')
Query terminates if SAP HANA/BWA index is inactive
If the SAP HANA index is inactive, the query is terminated (NOBIANOQUERY = 'X')
Query is sent to the database if the SAP HANA/BWA index is inactive
If the SAP HANA index is inactive, the data is read from the database (NOBIANOQUERY = ' ').
Use the system setting
Optional Settings for VirtualProviders
For VirtualProviders, you also have the option of defining a class in Optional Settings, which you can use to control delta downloads to the SAP HANA index and to control indexing parallelization. If you do not define any classes, the following rules apply:
Delta downloads to the SAP HANA index are not possible. Indexing always takes place in Initial Filling mode.
Indexing takes place in one background process. There is no parallelization over various background processes during indexing.
If you want to define a class of your own, proceed as follows:
Create a copy of ABAP class CL_RSDDB_BVIP_SUPER.
To allow delta downloads to the VirtualProvider's SAP HANA index, overwrite method IF_RSDDB_BVIP_DELTA~GET_READPOINTER.
To allow parallelization of the initial indexing process, overwrite method IF_RSDDB_BVIP_PARALLEL~GET_RANGES.
For further information, see the comment for these methods.
In the Characteristic for Delta Determination field, enter a characteristic of the VirtualProvider that you want delta determination to be based on. The characteristic should be numerical and grow monotonously.
If method IF_RSDDB_BVIP_DELTA~GET_READPOINTER is implemented in the class, a read status (READPOINTER) is returned. Data from the VirtualProvider is read in delta mode up to this read status and indexed in the SAP HANA database. The read status is taken from the delta characteristic.
If no delta characteristics are entered, no deltas can be loaded to the VirtualProvider's SAP HANA index.