Hybrid modeling (sometimes called mixed modeling) is when we combine the models from SAP BW/4HANA with SAP HANA to optimize performance and extend the capabilities. Both are individually powerful modeling environments, but when you put them together you have an even bigger tool set to work with.
Mixed scenarios are mostly based around the combining of data owned and modeled in SAP BW/4HANA (data physically stored in the SAP BW-managed schema of SAP HANA) with data owned and modeled in SAP HANA (data physically stored in external non-BW schemas).
You might be wondering where the data in external, non-BW schemas originates if it is not loaded by SAP BW/4HANA. SAP HANA includes tools to extract data from any data source and load the data to tables in SAP HANA's database. The tables are created in separate schemas that sit alongside the schema that is owned by SAP BW/4HANA.
For example, tables in a separate schema are populated once a day with the sales figures from a non-SAP application. In another separate schema we have a live feed of delivery data from another application. The schemas can even be in separate SAP HANA databases. For example, the SAP HANA database that powers SAP S/4HANA where we have access to live ERP data.
Data available from any SAP HANA database schema can be accessed by SAP BW/4HANA.
Consuming SAP HANA Calculation Views in SAP BW/4HANA
Just like the XS classic data models, HDI HANA Calculation Views can be consumed as source objects in SAP BW/4HANA via CompositeProviders or InfoObject Characteristics. This provides an opportunity to enhance SAP BW/4HANA models with the unique SAP HANA modeling capabilities. It also means consumption of SQL functions / procedures by SAP BW/4HANA models is very easy. You simply wrap up the SQL in a calculation view and then consume the calculation view in SAP BW/4HANA.
SAP HANA calculation views (regardless of which type) can also be consumed in SAP BW/4HANA Open ODS views. However, in this case a so-called SAP HANA Column View serves as source. This is an SAP HANA database run-time object which is always generated when the calculation view is built. However, consider that not all modeling services are available for this scenario (e.g. input parameters, hierarchies etc.).
Use cases for consuming SAP HANA models in SAP BW/4HANA:
Consume HANA data with SAP reporting clients via BW Analytic Manager
Consume HANA data in real time without traditional data loading processes, thus avoiding development costs, data redundancy, and latency
Consume HANA data with full usage of BW/4HANA services like Caching, Statistics, Authorizations, Data Tiering Optimization, etc
Consume HANA data within the existing BW/4HANA metadata framework. This means re-usage of existing InfoObject texts, hierarchies, master data with navigational attributes, as well as analysis authorizations
Leverage BW/4HANA OLAP capabilities like handling of non-cumulative key figures, hierarchy processing, compounding, or exception aggregation
Consume HANA data in BW/4HANA planning applications
You are able to define which type of calculation views can be consumed by your SAP BW/4HANA application. This setting needs to be defined once in the general SAP BW/4HANA customizing (Tr.
Launch the next demo to explore a CompositeProvider consuming a SAP HANA calculation view and a DataStore Object (advanced):