When a BW system uses an SAP HANA database, it is possible to use what are called „Mixed Scenarios“. In these scenarios you can use SAP HANA tools to combine data modeled in both the BW system and in SAP HANA.
Integrating BW objects into HANA views
In BW SAP HANA views you can generieren HANA views from InfoCubes, DataStore objects, InfoObjects, Queries as InfoProvide and CompositeProviders. You only need to set the appropriate check mark in HANA Studio.
After successful activation, a HANA view is created. Newly created HANA views end up in the HANA Content folder by default (the name of the content package will be: system-local.bw.bw2hana).
You can, however, also define another storage location in the transaction RS2HANA_VIEW.
Here, you can also define general settings for the generation of HANA views as well as for the creation/ replication of relevant authorizations.
You can check which HANA views have been generated from a BW system and what status they are subject to in the transaction RS2HANA_ADMIN.
You can also repair existing HANA views here if, for example, changes have been made to the underlying object.
Integrating HANA views into BW objects
CompositeProvider enables access to SAP HANA views. An intermediate Calculation view is always created because HANA views generated automatically by the system should not be changed. In theory, a simple Calculation view is sufficient.
Of course, any type of complex data modeling may be created here using all the functionalities of HANA native tools.
HANA views can then be added in the usual way to a CompositeProvider in BW, which completes the mixed-scenarios circle.
When transporting, be sure to collect all relevant HANA objects in BW.
Transporting HANA views (TC: SCTS_HTA)
You can use SAP HANA Transport for ABAP (HTA) to transport objects from ABAP for SAP HANA applications. These are ABAP applications based on SAP HANA and with which ABAP and SAP HANA objects are transported via the Change and Transport System in ABAP.
You must first transfer the objects and packages from the SAP HANA repository to the SAP HANA Transport for ABAP repository (HTA Repository) in the ABAP system and then add a transport request. This process is known as "synchronization".
Once it has been approved, the Transport Management System can import the transport request into the target system. The packages and objects are created and activated in the SAP HANA repository during importation. This operation is known as "deployment".
It allows you to transport even minor changes to SAP HANA objects and packages.
It assumes the same settings used to carry out synchronization. Before release, make sure that all the "traffic lights" are on green. Amber indicates that the object has been changed since the last release.
You can find out more about HANA Transport for ABAP here.