Skip to Content
0
Former Member
Jul 08, 2014 at 10:41 AM

What is the best practice to replicate the change of an object name in HANA AT/AN view where there are dependent views in it?

26 Views

Dear All HANA Studio Experts,

I'm using SAP HANA Studio Version: 1.0.68 in our current landscape and looking for a expert and intelligent solution for a problem that we have encountered recently.

We have created multiple AT views, AN views and created CA views on top of these AN views to cater different LOB related to our organization. We have also designed BO universe on top of the CA views from HANA and finally created webi reports out of these universes.

In a particular scenario, we have one AT view which is been used by 10 different AN views.

Now we had 3 Requirements like below:

1. To add a new field in this AT view,

2. To update an existing field in this AT view and

3. To remove a field from this AT view which is not required anymore.

Problems Encountered:

Req 1. When we added a new field (e.g. XX_ADD) in the AT view and activate it, its throwing warning that there are dependent objects on this AT view. However no error thrown and it leads to re-work to check if this new field is available in all those dependent views and re-deployed those all.

Question: How to ensure if this addition of object will not impact the rest of the dependent views?

Req 2. When we updated an existing field (e.g. XX_UPDATE_NEW) in the AT view and activate it, its throwing warning that there are dependent objects on this AT view. However the BO reports built on top of these different dependent AN views became inoperative.

Question: How to ensure if we need to update the name of an existing object it will not impact the rest of the dependent AN views?

Req 3. Finally we have removed one object from the existing fields as it is not required. Again we faced warnings that there are dependent AN views on this AT view.

Question: How to ensure if we need to delete an existing object, it will automatically reflect in all dependent AN views?

Please suggest, if it is a good practice to create separate AT,AN and CA views for each of the LOB's and avoiding any dependent views (hence gradually the total no. of logical objects will be increase) or to reuse the AT/AN views whenever possible and in case of any updation/deletion we need to do a huge rework to check and redeploy the dependent objects again and again?

Thanks for reading this detailed explanation and please let me know in case you need any other inputs....don't hesitate to share your expert thoughts on this.