Skip to Content
Author's profile photo Former Member

Fiori Application Technical Overview 3

In this session, we will debug the Fiori application’s Odata service (ABAP code) to find out how the data is retrieved from the back-end system.

We will also know the “component stack” in the server side.


As we can see, the data is returned in the “Response” of the requst:


HCM_TEAM_CALENDAR_SRV is the Odata service name.

EmployeeCollection is the entity name in the Odata service.

HTTP parameters:

$filter:StartDate eq datetime’2016-9-29T00:00:00′ and  EndDate eq datetime’2016-10-12T00:00:00′ and EmployeeID eq ‘00053533’ and AppMode eq ‘R’


SAPGUI to front-end (also called gateway hub) system

T-code: /n/iwfnd/maint_service

Image [1].png

Find the Odata service

Image [2].png

Image [3].png

Image [4].png

Image [5].png

Image [6].png

Image [7].png

Image [8].png

Now let’s replay the XHR (xml http request) to trigger the ABAP break point.

Image [9].png

Image [10].png

Image [11].png

So what’s usage of Gateway component?

Server need gateway to be installed so that it can:

Understand the Odata protocol format request and invoke the concrete Fiori application’s Odata service to get data.

Assemble the data into the format of Odata protocol so that the client side can understand the response data.

And other things. Please refer to SAP Gateway Developer Guide

The response data looks like:

Image [12].png

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.