Best Practice for HANA Information Views in IDT?

building semantic layer
1

I’m trying to get a better understanding of how to use HANA views in the context of the IDT.

Are there any guidelines for how many Information Views should/can be included in a Business Layer? If an Analytical view is like a star schema, does it even make sense to have more than one in a BL? Can you join views in the IDT?

charlie :us: (BOB member since 2002-08-20)

2

My understanding is that if you’re using HANA information views, you shouldn’t join them in IDT - the joins should be done in the model. Apparently there can be performance issues if you’re trying to join them in the universe. We have done it both ways and our “best practice” now is to do all the joins in HANA.

Selma (BOB member since 2004-10-12)

3

Thanks for the reply. I just found a reference which agrees with your findings in one of the training videos: “The best practice is to use a single view in a data foundation, with no joins to any other objects, which enables all of the processing to take place in SAP HANA”.

charlie :us: (BOB member since 2002-08-20)