Mixed scenarios in general are supported in BW on HANA and BW/4 HANA with Native HANA models(XS classic), there has been a lot of documentation on this topic available in SAP community, for example, Blog
With the introduction of XS advanced in HANA, regarding the mixed scenarios, there has been no support in BW on HANA and very little support in BW/4 HANA 1.0. In the newer releases of BW, it is getting improved. In this blog, I am going to describe how the integration scenarios work in BW/4 HANA 2.0 SP 02 or 03 with Native HANA XSA.
1. BW Models in Native HANA :
In the integration scenarios, BW objects can be generated as external calculation views and then consumed in Native HANA models to utilize HANA platform capability for further modeling. In XS classic, using HANA studio/Eclipse BW objects like ADSO, Composite providers will be generated as external Calculation views, they are available in HANA repository automatically for further use in CV modeling. However, it is not same in XS Advanced HDI containers. the below picture explains the process,
In XS advanced, HDI containers are created for DB modeling, with all the objects tables, views, procedures, functions and Calculation views are created inside the HDI container. These HDI containers are isolated from Classic database schemas. So with that, HDI container can’t have direct access to the generated CVs from BW objects.
For that, a custom user provider service(cups) will be created from HDI container to classic Database, which gives the access to _SYS_BIC schema, then a synonym will be created in HDI container for the generated CV and then synonym will be used as local objects in HDI container for further modeling of CVs. Finally HDI container CVs will be consumed by BI tools.
Note: Data base user which is used to set up cups must have authorization on _SYS_BIC schema in order to grant the access to HDI container user. This process of access scenario is explained in this blog, Classic DB access
2. Native HANA HDI models in BW/4 HANA:
In integration scenarios of XS classic, native HANA CVs can be embedded in BW/4 objects like Composite provider and open ODS views and then further modeling and query creation can happen in BW/4 HANA, then finally BI tools will consume the queries. However with XS advanced, CVs in HDI containers are not directly consumable in BW/4 HANA. So the process to achieve that is explained in below picture
In XS advanced, CVs will be created in HDI container, it is isolated to other containers and also toclassic database as explained above. In order to provide the access on HDI container, .hdbrole will be created inside the container, that will be granted to DB schema user who wants to access container objects in this case BW managed schema in HANA. The container hdbrole can be granted in Web IDE DB Explorer admin console by running the standard Stored procedures, you can follow the blog, hdi container roles to classic user
Even after granting the role, container CVs are not visible to consume in Composite provider, for that customization setting required to be done in BW/4 HANA system. Please note that, this is only possible in BW/4 HANA 2.0, can’t be possible in BW/4 HANA 1.0.
SPRO -> SAP Reference IMG -> SAP BW/4HANA Customizing Implementation Guide -> SAP BW/4HANA -> Data Modeling -> Settings for Consumption of SAP HANA Views
With this above setting, HDI containers will be made available to consume in composite providers. for more information refer to SAP note 2810348.
In the future coming releases of BW/4 HANA, more integration is planned for XS advanced HDI containers.