While discussing with a Pre sales guy on a Customer use case and some internal projects we thought we can actually use the SAP Lumira Publish to SAP HANA feature as an Agile Data Modeling tool for Business users. Want to share those experiences and ideas which we thought make sense for Enterprise Customers using HANA as their Analytics platform including Lumira Server.
It is more a “Value Add” to position SAP Lumira in “Enterprise Use-Cases” and to show how fast we can bring Data together in the Backend with SAP Lumira and start directly to report on it in an “Agile Modelling Approach”.
In general SAP Lumira Desktop can be used as an ETL and Data Modeling tool to upload Adhoc data from different data sources into HANA easily. Even can modify/enhance the data using different functionalities available in Prepare section if needed and then publish to SAP HANA as a View for consumption into different other Analytical (Ex. Design Studio) or UI (Ex.Web IDE after wrapping the View in an Odata service) applications. Of course it is available for Lumira Server too.
As described here, this is an example where Business user publishes Adhoc BW data to HANA and can create Stories in Lumira server directly or depending on the use case a power user can do further enhancements in HANA and then make this View available to the Business users.
Using above example and the explanation of the feature after this section we can see that there are many advantages and even some of the current SAP Lumira limitations can be handled:
There may be other scenarios where this feature may be useful and these are just based on our current Customer use cases which we are working on. Also for some of the scenarios (mentioned above) there may be different other ways to achieve it depending on the kind of user working on it (Business or Power/IT). So need to choose the right approach based on the user and the use case.
Only drawback is for now this feature may be used only for Adhoc scenarios as implementing delta upload or Scheduling the upload will be a bit difficult. Because during publishing to SAP HANA, SAP Lumira automatically creates the underlying Column table with Cryptic names (some system generated name) and when we try to update the same HANA View with new data using Lumira Desktop, the underlying Column table is replaced with a new one and the view is updated accordingly. So a power user is required for such cases and it will be like a “disconnected” Refresh Approach.
Publish to SAP HANA Feature Step by Step Example:
This example is for a scenario where we already captured the required content from a Website via “Data from Clipboard” data source, enhanced it to make it ready for reporting and then publishing it to HANA.
Dataset with merged data:
Finally as a closing remark, this feature is not placed against the standard publishing functionality Publish to Lumira Server option which is suited for most of the Reporting scenarios (even with “Online mode or Refresh possibilities) but more as a “Value Add” to position SAP Lumira in different “Enterprise Use-Cases”.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
12 | |
10 | |
9 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 | |
4 |