SAP Gateway with SAP HANA Integration provides a basic integration framework for read-only scenarios based on the approach of OData Channel to expose SAP HANA information models as OData services. SAP HANA Information models are used to create multiple views of transactional data and are the combination of attributes and measures. OData representations of SAP HANA information models can be used for analytical purposes.
A general knowledge of ABAP OO concepts and tools is required.
For information on the required software components and the underlying SAP NetWeaver release, see Installation Prerequisites.
For information on the underlying SAP NetWeaver release and other components, see Additional Software Components in SAP Gateway Configuration Guide.
For the SAP Gateway with SAP HANA integration the role template /IWHDB/RT_USER is available. It contains authorizations object /IWHDB/HAI. For more information on roles, see User, Developer and Administrator Authorizations.
For the implementation and usage of SAP Gateway with SAP HANA integration framework you need to maintain the database connection in table DBCON.
Furthermore, to declare the maintained SAP HANA connection to the framework you need to implement the enhancement spot /IWBEP/ES_DESTIN_FINDER.
At present the following integration constraints apply:
SAP HANA analytic privileges are not supported on the ABAP side. Therefore SAP Gateway with HANA can only be used with a service user.
Since the ADBC (ABAP Database Connectivity) interface uses only one defined database user to connect to the SAP HANA database it is not possible to apply an SAP HANA analytical privileges concept within the SAP Gateway integration. As a workaround solution a new authorizations object /IWHDB/HAI is available. With the help of this authorization object you can restrict access to the SAP HANA artefacts during runtime. In addition, the model provider class and data provider class contain protected hook methods for authority checks. The default implementation of these authority check methods contain the authority check for the authorization object /IWHDB/HAI. Customers have the possibility to enhance these methods by redefinition in the inherited classes.
Thus SAP Gateway with HANA offers limited productive usability until the corresponding trust relationship between SAP Gateway and HANA can be supported in SAP NetWeaver Application Server ABAP.
Filtering for measures is currently not supported.
Input parameters for calculation and analytical views are not supported.
Reference definitions for measure and unit/currency are not supported.
SAP Gateway with SAP HANA integration is based on the OData Channel approach for business content enablement. Following this implementation method there are two main components as essential parts of the SAP HANA integration:
The abstract HDB model provider extracts metadata out the SAP HANA DB repository and adapts it to the OData Channel representation. Metadata retrieval implementation follows a kind of hybrid approach. There is a generic part as well as a specific implementation part.
In order to name specific SAP HANA information models developers needs to re-implement the definition method of the abstract model provider class.
The generic HDB data provider delegates requests to the SAP HANA DB. Only read scenarios are supported. Runtime data retrieval works generically without a special implementation of sub-classes or configuration. Container structure and metadata data information about which data has to be retrieved will be received with the technical request context information.
With the help of the integration framework the following information models could be exposed as an OData service from the SAP HANA DB:
Attribute views are the reusable dimensions or subject areas used for business analysis.
Analytic views are the multi-dimensional views or OLAP cubes. Using analytic views you analyze values from a single fact table that is based on the related attributes from the data foundation and attribute views.
Calculation views are used to create your own data foundation using database tables, attribute views, analytic views, and calculation views to address a complex business requirement.