Quantcast
Channel: SCN : All Content - SAP Gateway
Viewing all articles
Browse latest Browse all 2823

OData Query optimization

$
0
0

Hi guys,

 

I am developing a Gateway OData service, and have one question I would like to clarify with you.

I have a requirement to send to the mobile device 10 different text tables (i.e. TVK1T, TVK2T, TVK3T, etc) using an OData web service.

I see two possible approaches for doing these:

 

1) Create 10 different entities, one for each table, where each of one will have two properties:

-Code

-Text

 

This way, I have to define a query operation for each entity and an RFC for each text table in the SAP Backend.

Then, the data can be retrieved from the mobile app using one $bacth request with 10 operations inside.

 

2) Create one entity that will have the fields:

- Table ID

- Code

- Text

 

This way, I can retrieve the data for the 10 tables using just one RFC I develop in the SAP Backend.

The mobile app just have to send one request containing one operation.

 

* In my opiinon, the second one is the best approach because the effort is much less than the first one, and it will be much more performant.

 

* In your opinion, What is the best approach to follow?

 

Best Regards,

Emanuel


Viewing all articles
Browse latest Browse all 2823

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>