Purpose of Mixed Scenarios in BW on HANA

[vivekbhoj]

Hi,

I have been thinking what could be the purpose of Mixed Scenarios in BW on HANA.

Why should we import BW Models to HANA or HANA Models to BW?

When we try to use them we have to take care of so many things like: BW Analysis Authorizations, Analytic Privileges, CKF, RKF

then there are many limitations and cautions that we have to take care of before importing any model.

Why should we go through all these when we can directly use our HANA Models or BW Models separately for reporting.

I tried to get an answer an think of a scenario but couldn't find one?

So in which scenarios can we use these models?

[MJUDI · Accepted solution]

Hi Vivek,

There many reasons why you would combine data from SAP BW data warehouse with data in SAP HANA that is most likely replicated in real-time. A scenario where you need to combine historical information such as trending with real-time status information that exist in HANA for example. Integrating SAP data in BW with non-SAP data that you might have in HANA is also another reason to combine BW and native HANA data.

Importing BW data models into HANA scenario was primarily developed to address the Explorer use case. Explorer can't access BW providers directly and therefore you need to import these model into HANA and expose its data in Explorer on top of SAP HANA.

Hope this helped a bit

Thanks,

MJ

[vivekbhoj · Accepted solution]

Hi Mohamed,

As you said:

Importing BW data models into HANA scenario was primarily developed to address the Explorer use case. Explorer can't access BW providers directly and therefore you need to import these model into HANA and expose its data in Explorer on top of SAP HANA.

-> It is good for re-usability of existing BW Models

There many reasons why you would combine data from SAP BW data warehouse with data in SAP HANA that is most likely replicated in real-time. A scenario where you need to combine historical information such as trending with real-time status information that exist in HANA for example. Integrating SAP data in BW with non-SAP data that you might have in HANA is also another reason to combine BW and native HANA data.

-> What you mentioned is true.

But lets say i am using HANA server for only BW - standalone BW on HANA server.

Lets say I have another HANA server for ECC, so can i import my HANA models created in ECC HANA Server to BW?

[MJUDI · Accepted solution]

Hi Vivek,

As of SAP BW 7.30 SP08 powered by SAP HANA, the following mixed scenarios are available, however the consumption of SAP HANA data models was available in BW before SP8 and this can be done in two ways:

• TransientProvider based on HANA Model (no InfoObjects required)
• VirtualProvider based on HANA Model (BW managed metadata)

New scenarios in SP08 are:

1. Direct loading of HANA data into BW based on new source system type: Operational Data Provider (ODP) with the context "HANA".
2. Easy consumption of HANA master data in BW queries using BW Virtual Master Data.
3. Flexible BW Data Provisioning for SAP HANA applications using Open Hub Destination with new target SAP HANA DB.
4. Easy BW InfoProvider Consumption by generating Analytic View for BW InfoProvider via HANA Modeler.

In addition to the above, you can also implement a mixed scenario at the semantic layer in BI, or directly connecting Data Sources in tools such as Design Studio or Analysis to BW and HANA models.

In your described scenario where you have a HANA model (I'm assuming this a HANA Live VDM) in the ECC's HANA and you have a BW on HANA system, as far as I'm aware there is no way to generate a BW data model from a HANA model except using Transient or Virtual Providers to access HANA data in real-time. I believe this can be easily done across two HANA instances as well. You can also have a BW data model loaded from a HANA view using the new scenario described in first point above if staging or persist the data in BW is necessary.

Thanks,

MJ

[vivekbhoj · Accepted solution]

Hi Mohamed,

I know about these providers and am getting what you are trying to say.

[former_member222993 · Accepted solution]

Hi Vivek,

Sorry for this delay in responding.. this seems like a pretty old thread however, got a bit excited with the good information provided here by you and Mohamed.

Following scenarios make Mixed mode usage very valuable..

1. Existing BW with loads of models and data: With minimal effort, Reporting can be accelerated if one decides to access this data from the SAP HANA side. As you know, this can be done without data movement.

2. Existing SAP R/3 data in BW e.g. Orders/Shipments etc: Yes, we can use XS engine and simulate DSO in SAP HANA etc.. however, all the jobs, support personal, existing usage can be left untouched while allow Information composer access to end-users (power users) who could load their own data (most likely master data or some augmenting transaction data) and create really interesting/powerful reports from the SAP HANA side (again by simply importing and creating some basic Calculation views).

3. As you know SAP HANA has Predictive Analytics. The orders/shipments and other data imported on to SAP HANA side can be conveniently used for some very interesting business use cases and presented nicely using Lumira.

I can think of many more and specific uses that will deliver huge value to biz.

Best wishes,

Venu

[former_member213376 · Accepted solution]

Hi Vivek.

       Need a small help.

       I have created a composite provider(HCPR) - which is based on a HANA calculation view(thats an extension of HANA live view -Billing Document). Its working fine and i can use for my analysis or APD processes.

       When i try to transport this to QA system through TR(transport request) charm process i am getting the below mentioned dump.

             

Please shed some light dude

Regards,

Prasana

[Former Member]

Hi.Please be aware

Note 1666670 - BW on SAP HANA - landscape deployment planning

(

SAP does support the deployment of BW residing on the same production SAP HANA system together with other applications listed in the "exceptions" section of SAP note 1661202, but please note the following key considerations:

- Mixed license types are not allowed on one SAP HANA appliance. The entire SAP HANA appliance (including the part utilized by BW) must be licensed for full use, e.g. platform license, enterprise license, etc.

[Former Member]

License policy changed, it's various,

Mixed license types are allowed on one SAP

HANA system. This means it is supported to run BW on one production SAP HANA

system with other applications/scenarios listed in note 1661202, with distinct

license types for the BW portion and for the other use cases, respectively.