Skip to Content
0
Nov 30, 2022 at 07:45 AM

BW/4HANA development best practice : go max HANA or use BW objects

173 Views

Hello,

This is a bit of a read and a bit philosophical, so my apologies.

With BW4HANA we have our BW toolbox with ADSO's, master data, composite's, etc as well as the ability to use HANA DB capabilities like table functions, calculation views etc.

I now have a different approach than a senior developer in my team. I will use the HANA capabilities more conservatively. In the end I will have a more traditional composite provider with characteristics, master data attributes and some keyfigures leaving some work for the queries in the way of selected and calculated keyfigures, for example.

My colleague on the other hand goes full on HANA. Extracting the data to ADSO's and then using table functions, calculation views, etc on the underlying tables to deliver a final view that has everything, from joined master data to calculated and restricted keyfigures, so that there is little work required in bex queries.

My composite would have maybe a few keyfigures and further selections would be made in the query, where his composite could have more than hundred.

His way of working has some advantages, it could be faster, because selections are pushed to hana and it is more easily used in other reporting environments by business users because the view has everything precalculated.

But I think there are some disadvantages too. It is more difficult for another developer to understand, harder to maintain and does not leverage the capabilities of BW. Subjectively, I also find it not very elegant to have an explosion of keyfigures in the view and composite provider.

How do you work? Is there a consensus on best practice? Are there guidelines for SAP on this matter? I haven't been able to find anything.

I'm very interested to hear other thoughts.