Hello,
My question is about best practices when you create a oData service in order to build a fiori app based on this service.
I know that the normal way would be to create a oData independently to the app that use the service, but when I look at standard fiori app, I can see that they build one oData service for one Fiori app. The oData service is not build to be reuse by another application.
For example, for the sales order, the header look like this :
order number
customer number
customer name
customer address
Ship to number
ship to name
Ship to address
total amount
currency
As you can see, custom and ship to name and address are in the entity header, although there should be only the customer and ship to number and an association to an entity customer with the name and address :
Header
order number
customer number
Ship to number
total amount
currency
Customer
customer number
customer name
customer address
the second model looks better and is more like a database model, but the SAPUI5 application is easier to develop with the first model. Also, with the second model, we would have to implement more methods (basic relation) in order to improve performance.
I started my development with the first option (the oData look like what I want to display in the screen instead of a database model), but I would like to know if it is a good practice.
thank you