Skip to Content
-1

Can I create graphical calculation views via script?

In the process of migrating a system based on another backend to HANA, I would need to create a huge number of calculation views, and I would assume I can save a lot of effort by converting the existing definitions to calculation views automatically, maybe with only 90% correctness, and then manually correcting the final 10%.

Is there any way to generate calculation views via some kind of SQL or other script? How would these scripts look like?

In case the script is officially unsupported, as log as it works, I would not mind too much, as - taking into account the purpose - I would not need the same script to be supported in a future version of HANA maybe five years from now, if the whole migration project just runs a few months.

Background why calculation views would be used:

The system to be migrated is a large data analysis system. In addition to purely relational tables/views, it consists of many OLAP cubes which would need to be converted to calculation views. For the existing ETL processes, I was also suggested to convert them to calculation views, but I am not sure if this would be the best approach, or if maybe converting these to a few thousand stored procedures would be a better approach. But that would be a separate question.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Aug 14, 2018 at 12:34 PM
    -1

    As far as I understand your need, may be you can try to script an XML builder to build your calculation views. Definitely not sure this will reduce time instead of making it graphically.

    Add comment
    10|10000 characters needed characters exceeded

  • Aug 14, 2018 at 03:53 AM

    hi Frank

    You may use custom SQL in Table function(TF) and use this TF in calculation views.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Ibrahim, I am not sure if that would be the optimum way to replace OLAP cubes of the existing system. (Sorry I did not describe that requirement in the first version of my query).