Analytical List Page: Virtual Elements Vs Table Functions

[former_member517243]

Requesting suggestion on a design perspective for an analytical list page . Since there is no BOPF involved in it, I cannot manipulate data, I need to display 70 columns in an analytical list page using Fiori elements. Out of 70 Columns only 5 columns are static values and rest 65 are calculated values. What should be the best design approach in this case for VDM designing ?

I could think of three ways here,

1. Consumption view using Virtual elements, but if I use Virtual elements do I need to have separate Class for all different columns or I can differentiate in my method of Virtual Element.
2. Table functions
3. Writing a program and update custom DB of 70 columns and then use a CDS view on it, Data would not be real time in it and would be a inferior view of presenting data.

Regards

Mohinder

[maheshpalavalli]

1. You can have a single class to handle this, check this api documentation, there you can find that you have something called entity name and in filters, you even have element name. -> this will only work with odata service query, if you access the view data via select query, it wil not work. And also note, if you are having any analytical table or aggregations, this will not work . (not sure somthing has been changed in the latest versions), you can check by adding any analytical annotation to the view.

https://help.sap.com/viewer/cc0c305d2fab47bd808adcad3ca7ee9d/7.51.6/en-US/4b5e56ec6f28453f81ac370bd9...

2. Table functions are good, you can use them, but make sure they are optimized(performance) properly else, the view read will take more time. -> This will work even while directly accessing the view data in select query and in odata service.

3. This is really not a good idea, If possible, update the table column(which is part of the cds view) when the data is created, running a background job to update is not a good idea and like you said the data will not be real time.

You can use the above points while deciding the aproach.

[former_member517243]

thanks Mahesh,

1st Option: I am going to have the analytical list page where aggregation would be done on few columns to present the KPIs.

How different it would be if I create a SEGW project use CDS view, do the manipulation in DPC's versus publishing it directly through @Odata in CDS view and using Virtual Elements?

Regards

Mohinder

[maheshpalavalli]

abap_instance The recommended approach is to create via segw project using the referenced data source as the CDS view(As per my knowledge), so that you can have both DPC and MPC classes, which you can use to futher extend your functionality when and wher eit is required.