Skip to Content

OData – Everything that you need to know (Part 8)

In Part 7 of this blog series, we saw the structure of an OData service in the system and discussed the OData URI convention model.

In this blog, we will create the OData model for the flight example.

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)

OData – Everything that you need to know (Part 6)

OData – Everything that you need to know (Part 7)



In the next blog, I will explain the OData Channel and implement the service.

Next Blog: OData – Everything that you need to know (Part 9)

5 Comments
You must be Logged on to comment or reply to a post.
  • Thanks Anubhav for this fantastic series of blogs. They are quite informative.

    Just want to understand what all basically you have created in SE80 for this flight model. I mean do we need to create the function/program for the action that I want to perform in the final FIORI app? For example in the mock-up you have mentioned that you would be searching the flight for an airline, so do I have to keep a program ready which I will have to link in SEGW to perform the activity?

    • thanks Dhiraj!!

      to answer ur query…you need to have the backend ready to be consumed by OData and finally in Fiori app.

      YOu need to create wrapper apis based on the functionality.

  • Hi Anubhav ,

      You created the Entity Set based on the RFC Module. So can you please share what code we have to write in order to enable the creation through RFC . Will be a great help

  • Hi Anubhav Pandey,

    please do you have a Blog where you explain how you implement the different RFC for the OData Service. For instance : ZAP_Get_Flight_connection

     

    Thx

    Eric

     

    • Sorry Eric. I dont have the blog or codebase with me that I an share. However, these APIs are no special than function modules that are RFC enabled.