By this time,we are aware of creating an Analytic Views and knowing the use of it in HANA Modeling. For more details on HANA we have very good self explanatory documents in the link http://help.sap.com/hana_appliance/
But what some of us don’t know is “what would happen when a modeler is working on change request and at the same time the reporting user is also executing a particular information space built on the same Analytic View. This would create an inconsistency issue. So, through this document i am explaining the option available in order to avoid such circumstances.
Go to the Properties tab of your Anayltics View. Here, I have created the view CEA1_00 on COPA tables.
As shown below we could see the option Visibility as ” Reporting Enabled”. It’s the default option when the Analytics View is created. Now, this model is visible for any kind of reporting tools like like Business Object Explorer.
But once we start working on a change request like to modify a column or adding a new filter or removing a column from the View, then we have to make sure the Model(View) is not visible at the business user end for reporting purpose, else it would create an inconsistency issue.
In order to address this, HANA studio offers an option ” Internal” as shown below .
I had come across this situation, and hence thought of sharing with the community.