Skip to Content

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.

Drawing6.jpg

UI Mock-ups for the Sflight App:

/wp-content/uploads/2016/02/1_885553.jpg

Master-Detail view with Airlines information on left navigation panel and various flights operating for a specific airlines on the details section.

/wp-content/uploads/2016/02/2_885662.jpg

Check Availability sceanrio

/wp-content/uploads/2016/02/3_885663.jpg

Information on seats availability

/wp-content/uploads/2016/02/4_885674.jpg

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)

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply