SAP HANA Star Join vs BW Composite Provider Nav. Attr

[former_member730008]

Dear Experts,

In our case BW is semantic/ reporting layer but we have used SAP HANA calculation views for complex calculation and also, to combine multiple data sets (huge data).

We can access the additional attributes by 2 approaches below. It would be great if you can suggest which approach is best in terms of performance?

Approach 1 --> To join master data with Transaction data

Approach 2 --> Navigation attributes from IO (IO association)

Thanks in Advance.

Regards,

Praveen Jelli

[former_member182343]

Hi Praveen ,

I suggest you to go with Approach 1.

You can have all complex logics/joins/calculations at calculation view and use it in Composite provider. Testing at calculation view end is easy.

Similarly, you can directly use calculation view for reporting purpose.

Regards,

Vijay

[TuncayKaraca]

Hello Praveen,

It's a good question! The best way would be testing performance on both approaches for a small scenario. You can also review HANA Calculation View with IO association for the Composite Provider if HANA view created for it. That way you can see and evaluate what's happening from HANA Calculation development perspective with IO navigation attribute enabled.

Here atriquell has a great blog post about the similar concepts and performance, check Optimizing models in BW/4HANA mixed scenarios

Regards,
Tuncay