OData – Everything that you need to know (Part 6)
In my previous blogs, we discussed the basics of HTTP, REST and finally Odata with context of SAP Netweaver Gateway. We also saw what are the possible deployment options available. In short we have laid the foundation for what is coming in the following blogs, i.e. end-to-end guide of creating, publishing and consuming Odata services.
Previous Blogs in the series:
OData – Everything that you need to know (Part 1)
OData – Everything that you need to know (Part 2)
OData – Everything that you need to know (Part 3)
OData – Everything that you need to know (Part 4)
OData – Everything that you need to know (Part 5)
In this blog, we will define the problem statement and give you a glimpse of what we are trying to build as a small application to showcase the power of OData. We will also build a simple Fiori-like app as a frontend consumer. Knowledge of Fiori is not at all a must here. As I mentioned earlier, during the course of the end-to-end exercise we will also explain various artifacts of OData.
In the next few blogs we will be creating a simple Master-Detail Fiori-like app based on SAP Flight Model example. . We will leverage the existing backend developments to expose the data as OData service that will be consumed by frontend. Future blogs will follow the Embedded deployment environment but, most of the steps we do here is applicable to the other two deployments. It is just a matter of where you do the modeling.
Here, is a link to the Overview of Fiori in case you wish to know more.
The app we are going to develop is a very simple app based on SFLIGHT example to check seat availability and add new flight tours.
Master-detail app will have the left navigation panel will feature the list of Airlines along with codes. The detail section of the app will contain the tabular list of different flights corresponding Airline. User will be allowed to select a flight and check for availability for a given date and class. App will also allow user to add new flights for a specific Airline and dates on which the flights are scheduled. We will showcase the CRUDQ operations along with navigations from master to object view and function imports during the course of this app.
Data Model for SFLIGHT that we will use.
UI Mock-ups for the Sflight App:
Master-Detail view with Airlines information on left navigation panel and various flights operating for a specific airlines on the details section.
Check Availability sceanrio
Information on seats availability
Adding a new Flight tour for future dates.
In my next blog, I will cover the Service Document, Service Document Metadata and Entity Data Model concepts and then we are ready to get into the system.
Next Blog: OData – Everything that you need to know (Part 7)
really good series...waiting for the next 🙂
The wait is over. added a few more!
Hi All,
I have added few more blogs to this series to demonstrate building an OData service.
Thank you.
Interesting, but where is the Fiori apps source (zip file)
Where is the OData Service ABAP Code ?
Could you provide both in order to deploy it on our systems ?
Dear Taryck,
Unfortunately, I dont have the source code with me anymore.
Let me know if you have any specific questions.
Cheers
Anubhav
I was able to recreate entities and relations. But I would like to sample Function_Import. I've seen the Seek avaliable is a good candidate for that. But how is it implemented ?
Because I'm trying to build a Fiori extension to Airline BC_Model in order to demonstrate both Fiori UI capabilities and OData service consumption in the idea/concept of extended enterprise where my provider and customer interact with my services (OData)....
Any help will be appreciated. You could suggest that to the SAP Persons in charge of the Airline BC_Model.