Skip to Content

In the previous parts (Part 1, Part 2, Part 3, Part 4, Part 5) we focused mainly on customers either without a complete DWH or with a custom DWH solution ( Part 5). In Part 6 we looked at customers that are using SAP NetWeaver BW without SAP HANA and in this part we will look at customer that are using SAP NetWeaver BW on SAP HANA.

/wp-content/uploads/2013/11/7_01_332259.jpg

Figure 1

In our scenario we are looking at a customer that has a heterogeneous landscape, with parts being based on SAP systems such as SAP ERP or SAP CRM, parts being based on non-SAP, and parts being based on standard relational databases.

In our scenario the customer made the choice to implement SAP NetWeaver BW on SAP HANA as EDW.

/wp-content/uploads/2013/11/7_02_332260.jpg

Figure 2

In Figure 2 you can see a scenario where the customer would use SAP NetWeaver BW on SAP HANA as EDW, but without fully leveraging all the capabilities SAP BW on SAP HANA is offering. In this option the customer is just replacing the database from SAP BW with SAP HANA and does not leverage any of the new options – such as a mixed scenario.

/wp-content/uploads/2013/11/7_03_332312.jpg

Figure 3

Figure 3 shows the first option how customers could leverage some of the new capabilities with SAP NetWeaver BW on SAP HANA. In this scenario the customer not only loads the data from the source systems into SAP NetWeaver BW but instead also replicates the data from the SAP ERP system into a SAP HANA managed schema.

In the situation where the customer is using SAP NetWeaver BW on SAP HANA, there are tables in SAP HANA managed by SAP BW and you can also have tables managed by SAP HANA (using SAP HANA Studio) – as shown in Figure 3. In our example the customer replicates the data from SAP ERP in real-time to the SAP HANA system. In addition the customer is also loading unstructured information – such as Twitter feeds – into SAP HANA directly.

With the data now in SAP HANA the customer can generate a Transient Provider in SAP BW on top of the SAP HANA Analytical models and then leverage the Composite Provider capabilities and combine for example data from SAP NetWeaver BW with the information in SAP HANA without having to load the data from SAP HANA into SAP NetWeaver BW.

/wp-content/uploads/2013/11/7_04_332313.jpg

Figure 4

Figure 4 shows another example how customers can leverage the new options with SAP NetWeaver BW on SAP HANA. In our next example (Figure 4) the customer is using SAP NetWeaver BW on SAP HANA like before and also replicates the information from SAP ERP into a separate schema in SAP HANA.

In this example all the unstructured information is already stored in HADOOP and the customer is not planning on moving the data from HADOOP into SAP HANA – and he does not have to do so. With Smart Data Access from SAP HANA the customer can then point to the information in HADOOP and – as pointed out in Figure 3 – then leverage the information and combine the data with data in SAP BW.

/wp-content/uploads/2013/11/7_05_332314.jpg

Figure 5

In Figure 3 and 4 we have seen options to create a Transient Provider based on the model in SAP HANA and then to combine the data from SAP NetWeaver BW with the information in SAP HANA – a so called “mixed scenario”. Figure 5 now shows another option where our customer is generating a SAP HANA model based on information that was modeled in SAP BW. With SAP NetWeaver BW on SAP HANA customers can also leverage existing assets – such as a BEx Query or a InfoProvider – and generate an SAP HANA analytical model, which then can be accessed directly by connecting to SAP HANA.

A good example for this scenario is the usage of SAP Lumira, SAP BusinessObjects Explorer, or SAP Predictive Analysis in combination with data from SAP NetWeaver BW. In such a use case – knowing that these three BI clients can not connect to a BEx query directly – customers could use the integration of SAP NetWeaver BW on SAP HANA and generate the model in SAP HANA and connect the BI clients to the generated model.

/wp-content/uploads/2013/11/7_06_332315.jpg

Figure 6

So how about SAP NetWeaver BW on SAP HANA and SAP HANA Live ?

Figure 6 shows such a scenario. In our last example the customer is running SAP BusinessSuite on RDBMS (not on SAP HANA) in combination with SAP NetWeaver BW on SAP HANA. As mentioned previously we have two sets of schema in the SAP HANA system – one set of tables managed by SAP NetWeaver BW and one set managed by SAP HANA.

Our customer is also using SAP HANA Live as pre-configured content for operational reporting and those models are part of the SAP HANA manged content.

Our customer is loading the information from the SAP BusinessSuite into SAP NetWeaver BW – like in the prior scenarios – but is also using real-time replication to load the data from the OLTP environment into SAP HANA and uses then the pre-configured models from SAP HANA Live for operational reporting.

I hope people find this information useful and that this content helps to clarify some of the possible scenarios that are available with SAP HANA, SAP HANA Live, and SAP NetWeaver BW on SAP HANA.

In the next post we are looking at customer landscape #8, where a customer uses OLTP environments based on SAP technology and a custom DWH based on SAP products.

To report this post you need to login first.

2 Comments

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

  1. Mohanrao Kethineedi

    Hi Ingo,


    I learned a lot from you in ASUG workshops/conferences and your expert blogs. Thank you for all your contributions.

    If we have both Suite on HANA and BW on HANA what is the best configuration to take full advantage of both BW and HANA live? I am referring to above scenarios figure 4 or figure 6 with suite on HANA (not RDBMS).


    I see 3 possible scenarios for this with Suite on HANA, BW on HANA, and HANA Live

    1.      Suite on HANA, BW on HANA, and HANA Live on same instance:

    Pros:

    • No need to replicate data to use Live or new HANA optimized BI content which also uses Live models.
    • Be able to use new HANA optimized BI content which also uses HANA Live models

    Cons:

    • OLTP system may be effected by BW system operational issues like upgrades and failures
    • OLTP (Suite on HANA) and OLAP (BW on HANA) systems forced to upgrade same time

    2.      Suite on HANA on one instance and BW on HANA and Live different instance:

    Pros:

    • OLTP system not effected by OLAP system
    • Be able to use new HANA optimized BI content which also uses HANA Live models

    Cons:

    • Data needs to be replicated between Suite on HANA and BW instance

    3.      Suite on HANA and HANA Live on one instance and BW on HANA different instance:

    Pros:

    • OLTP system not effected by OLAP system except for Live access
    • No need to replicate data for HANA Live use

    Cons:

    • BW can’t use all new HANA optimized BI content without replicating data
    • Can’t use mixed mode scenarios between BW and Live as SAP promoting in many presentations without replicating data.

    I would appreciate your thoughts on this.

    (0) 

Leave a Reply