(2011) HANA views
If you are using the HANA system, it is possible to create HANA views for selected types of DataProviders using SAP HANA Smart Data Integration or SAP HANA Smart Data Access.
Prerequisites for HANA SDI
The provisioning of offloaded data to the HANA view is using the following components.
SAP HANA Smart Data Integration and SAP HANA Smart Data Quality
Version 1.0 SP03 Patch 11 (1.3.11) for SAP HANA 1.0 SPS 12 and higher
HANA DP Agent 2.0
Datavard DataTiering SDA+ HANA native add-on transport
Setup for HANA SDI
As soon as you met the prerequisites, you need to do the following:
Register Adapters with SAP HANA
Deploy and register ABAPAdapter
Add Remote source in HANA studio
Add SAP system where SDA+ is installed
Setup for HANA SDA
Add Remote source in HANA studio
Useful links
Install and Configure the Data Provisioning Agent
SAP HANA Academy - SDI: ABAP Adapter [SPS 11]
Not supported types of DataProvider
HANA views can be created for all types of DataProvider except the following types:
Tables
HANA native
DDIC
InfoProviders
Write Optimized DSO
Creation of view
In order to be able to access offloaded data of DataProvider, you need to create a HANA view. You can do it by creating this report:
Go to main SDA+ transaction /DVD/OFF
Select menu Others
Chose Create HANA view
Report execution parameters
Parameter name |
|
---|---|
HANA DB connection | Connection name to HANA database (leave empty if you want to use primary HANA database) |
Schema | Name of the database schema |
Remote source | Remote source defined on HANA database that points to the current SAP system |
DataProvider Name | Name of DataProvider for which we want to create a view |
Object names are generated with the following names:
Object kind | HANA object name pattern |
---|---|
Virtual table name | <Remote source>_<DataProvider Name>_VT |
Aggregation with pruning condition | <Remote source>_<DataProvider Name>_CS.AGGR_FILTER |
Calculation scenario (for reading data) | <Remote source>_<DataProvider Name>_CS |
If you want to get the list of DataProviders for which the HANA view was already created, use the search help in a view deletion report or read table /DVD/OFF_ANA_H_S using transaction SE16.
The functionality will create the following calculation scenario:
Pruning condition
Pruning condition is vital for good performance of existing queries that will be also using offloaded data. This condition will restrict reading data from an underlying virtual table if the user reads data with a certain filter. This filler will be intersected with the pruning condition if the result in not empty set data will be read otherwise the virtual table is not accessed. Currently, it is possible to generate two kinds of pruning conditions.
Update of pruning condition
The condition will be automatically updated after the following DataProvider events:
Offload
Reload
Including selective reload by Writer 3.0
Manual update of pruning conditions shouldn’t be necessary. If you need to update it manually as a workaround, repeat the creation of a view with the same parameters.
Default
By default pruning condition is set the same as uniting of all offloading request conditions of DataProvider.
Less equal from MAX values
Maximal values of specified fields of DataProvider are combined into conditions with the less equal operators.
Let's have fields from FIELD_1 to FIELD_N and function <MAX(FIELD_X)> - the maximal value of field FIELD_X in offloaded data, the condition will be generated as follows:
FIELD_1 <= <MAX(FIELD_1)> AND FIELD_2 <= <MAX(FIELD_2)> AND … AND FIELD_N <= <MAX(FIELD_N)>
Fields selection
Fields that will be used for the generation of pruning conditions can be set as DataProvider specific setting HANA_OBJ_PRUNNING_FIELD in CSV format.
Example: FIELD_1;FIELD_2;FIELD_3
Deletion of view
If you don’t want to use the created HANA view anymore, you can delete it with a deletion report. You can find it attached to the main SDA+ transaction.
Go to main SDA+ transaction /DVD/OFF
Select menu Others
Chose Delete HANA view
The program contains only one execution parameter for DataProvider name, for which the HANA view should be deleted.
Please be sure that the HANA view that you want to delete is not used in HANA anymore. If you delete a view that is further used, dependent objects become inconsistent.