0

SAP HANA Modeler Design is Cumbersome

pravir khandelwal 8 years ago updated by michael appleby 8 years ago 1

I do not understand why SAP had to make the SAP HANA Modeler so difficult to use. SAP in general likes to use lots of words that are superficial and not self-explanatory. Attribute View, Analytical View, Calculation View for Dimension, Cube without star join, Cube with Star Join and so on so forth. Why could SAP not simply make it Aggregates, Dimensions, and Facts, and Stars - just use standard industry terminology instead of creating new confusing ones?


And the Modeler tool is so not intuitive. If you want to create a dimension view with 3 or more tables, you keep creating joins after joins, projections, etc. etc. Why can it not be an ETL tool like GUI where you select any number of tables you like, define joins, and specify output columns and properties. And in the same interface, allow to toggle between SQL view and Graphical view.


Just by creating a graphical tool, SAP is assuming it is intuitive and user-friendly but it is not; nor is it robust to handle all types user needs without building serious complex views. It does create job security for the employees and consultants but costs extra money for the companies that have to hire army of people to do the work.

Hi Pravir,

You are in UserEcho which is for feedback on the new SCN Profile. If you wish to discuss a techical topic, like SAP HANA Modeler Design, please ask a question in answers.sap.com, but I am not sure which of the dozens of SAP HANA tags you should use, but would recommend one that is under the SAP HANA (L2) tag. I suspect you will know better than I which would be appropriatae.

Cheers, Mike (Moderator)
SAP Technology RIG