Skip to Content

OData service version changed when deployed on SAP PO (7.5)

Jul 18, 2017 at 03:57 PM


avatar image
Former Member


We are have developed OData service in the backend (Netweaver 7.4 SP14) when deployed on SAP PO (Netweaver 7.5 Java stack) the service version gets changed from 2.0 to 1.0.

When the same service we deployed on the backend the version is 2.0. Further checking both metadata are different. For 2.0 I can see annotations however the same information is missing in 1.0

Is there anything wrong I am doing while deploying on PO?

Any help would be much appreciated?


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Jun Wu Jul 19, 2017 at 01:42 AM

why you deploy it to PO?

Show 4 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Because our PO is on latest Netweaver and hence latest version of a UI5 library. We are thinking of using smart controls while building SAPUI5 screens but since OData version got changed to 1.0 so not able to use annotations.

Is it a standard behavior when we deploy on PO (Java stack)?


first I don't think PO is the proper server to develop your UI app.

second, sap's java(platform) is always secondary compared with abap. (that's why you don't see the version 2, I guess.)

you don't have to deploy(integrate) the odata to po, you can use web dispatcher to do the job.

Former Member

We are interacting with non SAP system from UI so I think PO is the right box where UI5 apps should be deployed.

Exposing Back-End Data as OData Services

13 Reasons to Migrate from SAP PI to SAP PO


why connecting to non sap system can justify the use of PO for ui app? Your abap server cannot do it? all are using ajax call, po java server won't give u any advantage.