Skip to Content

oData versus sap.m.PlanningCalendar

Hello Experts!

I'm going to use sap.m.PlanningCalendar to display data from SAP through oData service. There are a huge amount of data and my question is how you handle such issues? In SAP tables data are in completely another form than PlanningCalendar requires.

My first idea is to create in sapui5 application oData model. When a user changes date in PlanningCalendar then I use method "read" with the filter - the date between the chosen by user and 14 days further. The next step is to convert fetched data to form required from PlanningCalendar and display them.

I suspect that there is a better solution :) Perhaps a better idea is to prepare oData service in form required from PlanningCalendar by transforming SAP data in Gateway service? Maybe then PlanningCalendar has built-in tools to not load all data but only those which are currently displayed - something like paging. But transforming huge amount of data into Gateway service won't improve performance...

How do you do it?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

0 Answers