Odata service - how it gets data from SRM backend and mapping

[Former Member]

hello

I'm exploring Odata as functional resource for our Fiori Shopping Cart App
and wanna have some more in-depth understanding for analysis and debugging purposes.

We have central hub Fiori App deployment where Odata service is defined in gateway and called from gateway client to our SRM backend via RFC.

My question is where can I start looking at to see how standard way it retrieves specific backend information in SRM, like class/method/FM, for a specific service, say country_sh_service or cross_catalog_search and how it does mapping in UI side fields..
I read helpful blogs but I may be missing something to find the answer myself.

Thanks for the help.

[saurabh_chikate]

Hi Dex,

For this, you will need at least read access to all the involved system. (Backend and gateway).

You can backtrack the calls this way.

1. get the service name

2. Login to Gateway system. open transaction SEGW.

A list will be displayed, in the project list find the name of service except for the last '_srv' extension.

expand that service and you will get the folder named runtime artifacts. expanding it will give 4 classes. Open one with the extension _DPC_EXT.

Opening those classes will have an implementation of the operations in form of methods.

Opening those methods will give you an idea about the technical process carried out behind the execution.

But if that method is using RFC then you will have to view that in the backend system.

3. Inside the same project, you will find a folder named Data Model.

The data model is like an interface between your method and OData Service.

It will have some fields that are going to appear in your Odata.

4.Mapping with UI fields can be found out in Application source code of Fiori App.

Mostly it will have names relevant to the Data Model from DATA Model.

It is just a crude way to backtrack so please don't judge this as technical answer.

Regards,

Saurabh