Skip to Content

After watching lectures DMM268 and DMM300 at SAP Teched 2016, I was really excited about the possibilities of SAP BW and SAP HANA mixed architectures options.

Before we begin with the examples, let’s have a quick overview of this concept.

What is a Data Warehouse Mixed Architecture?

It’s an SAP best practice for modern data warehousing. Simply put, it’s a data model that is implemented at the same time in SAP BW and native SAP HANA.

What are the benefits of this Mixed Architecture?

It combines processes, data and metadata of BW and native HANA, bringing the best capabilities of both worlds in order to gain flexibility and insight.

SAP HANA and SAP BW deliver integrated tools to manage mixed scenarios end-to-end, including modeling, transport mechanisms and consumptions interfaces.

SAP HANA database is the central runtime for reporting and data warehouse process, offering best in class performance and scalability.

Mixed Scenarios examples:

1 – Mixed Reporting Case

Mixed SAP BW and SAP HANA reporting:

  • OLAP processing done in BW analytic Engine;
  • Bex queries can be exposed as HANA views;
  • Consume directly on HANA using BI tools (e.g. Lumira);
  • HANA analytic privileges based on BW analysis authorization.

2 – Reporting on SAP HANA Views

Reporting on generated SAP HANA views for BW infoproviders

  • Data extracted, loaded and transformed in BW and stored in BW infoproviders;
  • Infoproviders can be automatically exposed as HANA views;
  • These generated SAP HANA views can be enriched in HANA Studio.

3 – Native HANA features for agile scenario

Using HANA-native features for agile scenarios:

  • Data can be loaded to a separate DB schema in HANA via SLT, ETL tool or file upload in HANA Studio;
  • HANA Modeler is used to build reporting views
  • SAP HANA views integrated into SAP BW using a Composite Provider.

4 – SAP BW for managing specific data

SAP BW for specific data consolidation:

  • Specific data managed by BW, e.g. master data, heterogeneous data from many sources, data from SAP ERP extractors);
  • These BW managed data objects are exposed to SAP HANA for further modelling;
  • BI clients can consume data via native HANA.

5 – Use of SAP BW Analytical Engine

  • Data not managed by SAP BW, completely modelled in SAP HANA;
  • SAP BW OLAP functionality “added” on top of SAP HANA models by integration it with a BW Composite Provider;
  • E.g. SAP HANA Live views integrated into BW.

These are just few examples of what can be achieved used SAP HANA and SAP BW mixed architecture.

Is your company using any of the above approaches?

Or have you ventured in another mixed architecture solution?

Feel free to share with us.

To report this post you need to login first.

12 Comments

You must be Logged on to comment or reply to a post.

  1. Mauricio Cubillos

    Tiago,

    Great blog and great approach: use cases. It helps put the conversation into specific topics.

    I would like to  add an architecture and data management approach. When thinking the DW as a part of a mayor Data Management landscape, with multiple components and applictions, having new functionalities (mostly industry standards) that easy the integration you got a better solution. Hybrid scenarios tells: “you can work with BW and/or HANA, but also you can integrate with BW and/or HANA”.

    (0) 
  2. Fabian Geist

    Hi Tiago,

    nice overview!

    Here comes another possibility which works for 3) and 5).


    As the Composite Provider that is based on a HANA Calculation View has a bad Performance, because the view holds a lot of calculations, etc., it is possible to load the data of the HANA View into an ADSO.
    By this the data is persistent in this ADSO (in BW).
    On top of this ADSO you can build your Composite Provider + BW Query.
    Thereby the Query is reading from the persistent data in the ADSO and not from the slow HANA View.


    Regards,
    Fabian

    (0) 
    1. Marcel Scherbinek

      ” As the Composite Provider that is based on a HANA Calculation View has a bad Performance, because the view holds a lot of calculations, etc.,”

      You named already the reason for a bad performance but generally I wouldn’t say that they have a bad performance. On the other side I can recommend modeling Composite Provider on HANA Calculation Views when you pay attention on workload and architecture.

      (0) 
    2. Vijay Matlani

      Hi Fabian,

      Just to add to my knowledge can you please highlight steps in short on how to load the data of the HANA View into an ADSO.

      Regards,
      Vijay

      (0) 
    3. Fabian Geist

       

      Hi Vijay,

      sorry for my late response. Here are the steps:

      1. Create a HANA View you want to load into ADSO
      2. Create a DataSource (should be based on Source System>DB Connect>Connection to HANA DB)
      3. Configure the DataSource: Extraction>Adapter>Table/View = Your HANA View
      4. Create an ADSO. Choose your DataSource as Template.
      5. Configure ADSO and create Transformation / DTP
      6. Load data

      Best regards,
      Fabian

      (0) 
  3. David Velasquez

    Hi Tiago,

    Thank you for sharing the information. We have to have open eyes with these mixed architectures because according to roadmap of SAP Data Warehouse technology, this integration will continue.

    Regards,
    David 

    (0) 
  4. Eddie Ng

    Very valuable blog! we have been using these mixed architecture consuming the hana views via composite provider and using BW queries to expose to Design Studio. At the same time, we are exposing the hana views directly to AAOE for more analytical reporting…

    The BW queries are also integrated to workbook solutions and published as a transactions in Business Client.

    we could use BW authorisation analysis easily and integrate into existing SAP authorisation roles

    (0) 
  5. Jameel Ahmed Shaik

     

    Hi, We have done one scenario.

     

    • Data not managed by SAP BW, completely modelled in SAP HANA;
    • SAP BW OLAP functionality “added”  directly created Bex Query on HANA Views

    Jameel

    (0) 

Leave a Reply