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:

http://mxxxx.ak:8080/sap/opu/odata/SAP/HCM_TEAM_CALENDAR_SRV/EmployeeCollection?$filter=StartDate%20eq%20datetime%272016-9-29T00:00:00%27%20and%20%20EndDate%20eq%20datetime%272016-10-12T00:00:00%27%20and%20EmployeeID%20eq%20%2700053533%27%20and%20AppMode%20eq%20%27R%27&sap-client=200

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’

sap-client:200

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

T-code: /n/iwfnd/maint_service

Find the Odata service

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

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

http://help.sap.com/saphelp_gateway20sp12/helpdata/en/56/d0cc05b564411e841141f68294e29f/content.htm?frameset=/en/3c/17df546e39c50ae10000000a441470/frameset.htm&current_toc=/en/57/a41787789c4eca867d9a09696fc42c/plain.htm&node_id=252&show_children=false

The response data looks like: