I want to share with you people about the strange thing which I encountered recently when working with Counters in HANA and creating OData service for the calculation view.
I have created a calculation view with multiple attributes and few measures. Suppose I have created a calculated column (CAL_COLUMN). The requirement is to count the distinct CAL_COLUMN. So obviously I will go for COUNTER and apply on CAL_COLUMN.
Imagine the Column is Date field; ERDAT= 1 Jan, 2016
Calculated column for Year is applied; CAL_COLUMN = component (“ERDAT”, 1) = 2016
Suppose we have 5 entries for 2016 and you want to capture the count. And the counter is applied for CAL_COLUMN.
The calculation view (CV_TEST1) is activated without error.
Data Preview is perfect and in the ANALYSIS tab of Data Preview you are able to see the count value = 5 for the X-Axis attribute.
Everything is perfect till the HANA view and Data Preview.
Let us see the OData creation and view consumption part.
The OData service throws the error: Service exception column store error
The calculation view is splitted at calculated column level and CV_TEST1 is created.
This means CV_TEST1 will have attributes and 1 calculated column (CAL_COLUMNS).
On top of which another Calculation view CV_TEST2 is created with CV_TEST1 as data foundation at the Aggregation node. The COUNTER is created on the ATTRIBUTE CAL_COLUMNS.
The Odata service is working with no ERROR.
Conclusion: If you want to create the OData service on your calculation view having counters on calculated columns, then kindly split the view creation in two levels (one till calculated column level and another till the COUNTER level)
Thanks for reading!
Thanks for your time!!
Thanks for your support!!!