on 2018 Oct 17 10:03 AM
Till now in our project we were using SAP HANA Native for creating views, which were then consumed by Analysis For Office (AFO) directly.
Now we may plan to expose all these view through BW4HANA system. And now I'm wondering what is the best way of doing that. My initial plan was following:
<em>HANA View</em> -> <em>Composite Provider</em> -> <em>Query </em>-> <em>AFO</em>
This seem to be working fine, however I noticed that there is also possibility to consume HANA Views using Open ODS Views.
The differences (which I see) for consuming calculation views between Composite Provider and Open ODS view which I discover for this kind of implementation are:
Request clarification before answering.
Hi Konrad,
Recently I have been investigating this very same scenario. Other community members may also have suggestions but here are my conclusions so far:
1. Using Open ODS Views seems to be a cleaner approach if the requirement is purely to consume a HANA-based virtual data model in BW (also considering that your Calculation Views do not have any input parameters). In this case you have a one-to-one relationship between a reporting HANA View and an Open ODS View which is subsequently consumed by a BW Query;
2. As you have pointed out, a Composite Provider allows you to combine multiple data sources. However, if your data sources are only HANA Views then I think it would be better to apply a consistent modelling approach and just create new HANA Views as needed to feed Open ODS Views. On the other hand, if you have a requirement to combine your HANA Views with other data sources such as data persisted in BW ADSOs then the Composite Provider would be more appropriate.
Also, I would be interested to know what has lead to the decision to consume your native HANA virtual data model in BW/4HANA? Some reasons I can think of are to take advantage of BW features such as:
- master data hierarchies and attributes
- BW authorisation concept
- BW Query features such as Structures, Cumulative Key Figures, Totals, BW Variables (standard and custom), Cell Selections and Formulas etc
Regards,
Mustafa.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mustafa,
Thanks a lot for your response.
The main reason of that decision is that we already have another team working on BW and we wanted to have a single point of reference both for HANA reports and BW report (now users need to login separetely to BW and HANA system depending on the reporting need).
Additional advantages of exposing those views in BW are similair as the one which you mentioned:For master data we are not sure to what extend we will use them, since we have many custom fields and it would be very big effort to create and maintain master data for all of them.
Let's see if other community members suggest anything else for this topic.
Thanks,
Konrad
Hi Konrad,
Thanks for your feedback. This is building quite a good use case and validation for combining native HANA models with BW. Yes, let's see what other suggestions are offered. It could make for an interesting discussion 🙂
Regards,
Mustafa.
User | Count |
---|---|
50 | |
9 | |
8 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.