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

Data model design, Do I need a complex entity?

$
0
0

Hello Gurus,

Our project is trying to build a UI5 application for  transaction processing(ex-Service order) and have decided to use OData protocol for interacting with SAP ECC. I'm trying to create a datamodel for my gateway project and wondering which of the two below options I should choose.

 

Option 1

Create a separate entity for

Header,

Item,

Text,

Attachment,

Partners Involved.


Batch up update/create requests when information relevant for more than one of the above entities need to be updated with single click for save button on the UI.

 

Option 2

Complex entity that would hold all the above information.

 

I'm leaning towards option#2 for the following reason: In the scenario, when there is a need to update header info and item data for an existing order and if I have the corresponding put requests in single batch - I may run into a situation where the second put request may fail if the first request is still processing the transaction and still holds a lock.

 

Please confirm my understanding and shed some light on the pros and cons of the above options.

 

Regards,

Seetharam


Viewing all articles
Browse latest Browse all 2823

Trending Articles



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