cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Odata EXPANDED Entity Set Multilevels

hemantbaviska
Explorer
0 Likes
1,369

Dear Experts,

I have an Odata with below multilevel navigation. So currently we are reading all the data using the BATCH operation. But the performance is not that good. So i was thinking of using the GET_EXPANDED_ENTITYSET to read all the data of "Opportunity" in a single frameowrk call.

Opportunity : HEADER

Navigation ITEM 1: Attachments.

2. Contact Person

3. DocFlow

4. Notes

5. Relationships

6. Tasks.

7. PartnerFunctions.

So my question is will this increase the performance and is it feasible to read 8-10 ITEMS in a single framework call.

Regards

Hemant

Accepted Solutions (0)

Answers (2)

Answers (2)

hemantbaviska
Explorer
0 Likes

Hello maheshkumar.palavalli

Thanks for the reply. I was bit busy with other issue so could not replied back.

We are already using the parallel batch calls but its still taking like 20-30 mins for the initial offline sync. So I was thinking of merging all the code in expanded entitysets. Yes we are using the FM/Bapi to read all the data. So I need to see if this will improve the perforamnce or not.

maheshpalavalli
Active Contributor
0 Likes

I would suggest you to use direct db reads via CDs views/tables, this is will increase the loading speed by many times. and like I mentioned, it will be faster with parallel batches for sure, not in a single batch. But again, remove those FM/BAPIs and write logic using queries on tables or CDS views

maheshpalavalli
Active Contributor
0 Likes

Getting all in single expand entity is good, but I belive the best option is to send calls in parellel(not single batch, multiple calls) from the front end, in that way, all hit different tables and fetch the data in parellel, this is how fiori element object page fetches data.

This is only good if you have a good logic to fetch those data, for instance fetching from a cds view, else if you are using a bapi or a function module or some complex abap logic, it's better to go for expand entity.