1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

(http://ww Community
w.sap.co (https://community.sap.com)
m/) (https://sharedui.services.sap.com/v2/protected.html?
ref=https://archive.sap.com/)

Ask a Question (https://answers.sap.com/questions/ask.html) Write a Blog Post (https://blogs.sap.com/wp-admin/post-new.php) Login (https:/

SAP Gateway (https://community.sap.com/tag.html?id=01200615320800003185)

Capabilities Matrix: Which SAP product to use to

expose your business data as OData service for UI
consumption
Tags: sap_fiori | sap_mobile | sapui5 | fiori | sap_gateway | sap_ui5 | odata | mobility | sap_mobility | gateway

If you are a UI developer, you probably have heard about OData by now. (If not, you can find a great overview on the subject here.
(http://scn.sap.com/community/mobile/blog/2013/10/03/lets-talk-odata-shall-we)) It is an abstraction layer between the complicated business data and the
user interface. Also, it is the data format that powers many of the new and simplified UIs that SAP is rolling out in different products: SAP Fiori apps,
S/4HANA, and the ability to build your own apps using the SAPUI5 framework demonstrate very clearly SAP’s commitment to this technology.

So now you probably want to know how you can free up your existing data from your SAP and non-SAP systems and convert them to the OData format,
so that they can be easily consumed by these innovative new UIs? There are different SAP Products that help you to achieve this. My colleague Martin
Bachmann has given a great overview on the subject here: SAP Gateway, SAP Process Orchestration, OData, SAP Mobile Platform – how does all this fit
together? (http://scn.sap.com/docs/DOC-59578)

In most cases, you would use SAP Gateway to create OData services in your SAP backend systems. SAP Gateway consists of two main technical
components:

Gateway Backend Enablement

Gateway Hub (http://help.sap.de/saphelp_nw74/helpdata/en/7d/9b2451f8c0266ee10000000a445394/content.htm)

https://archive.sap.com/documents/docs/DOC-63973 1/7
1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

In short terms, the Gateway Backend Enablement is responsible for "gathering" the data for the OData service; the Gateway Hub is responsible for
actually converting the service from the SAP proprietary format into the OData format and to expose the data for consumption by the user interface. For
details on this topic, you might want to look into the various Gateway deployment options described in this blog
(http://scn.sap.com/community/gateway/blog/2013/05/27/sap-netweaver-gateway-deployment-options-in-a-nutshell).

However, since the release of SAP Process Orchestration 7.31 SP13 or SAP Process Orchestration 7.40 SP08 (http://scn.sap.com/community/process-
orchestration/blog/2014/11/26/exposing-gateway-services-from-process-orchestration) and the SAP Mobile Platform 3.0
(http://scn.sap.com/community/gateway/blog/2014/03/20/there-is-a-gateway-for-that), there are further deployment options for exposing SAP Gateway services from your SAP
backend systems as OData services.

In order to find the right setup for your environment, there are different aspects you should consider:

https://archive.sap.com/documents/docs/DOC-63973 2/7
1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

If you already run an SAP Process Orchestration or an SAP Mobile Platform 3.0 server, you might save the operating cost for an additional
Gateway hub server and thereby lowering your overall TCO.
If you need to integrate 3rd party data sources like REST based web services, JDBC databases, JPA models or SOAP web services, and expose
these as a unified OData service, then SAP Mobile Platfrom 3.0 might be the right choice for you.
Some companies have policies in place that all services have to be routed via SAP Process Orchestration. In this case, you can now also expose
your SAP Gateway services.

Also, there are some usage constraints you need to be aware of in order to make the right choice.

To help you out, we have come up with a detailed capabilities matrix showing the key differences between the Gateway Hub, SAP Process Orchestration
and the SAP Mobile Platform 3.0:

OData Provisioning Capabilities Matrix

Feature SAP OData Integration Description
Support Gateway Provisioning Gateway
Hub in SAP in SAP
Process Mobile
Orchestration Platform
3.0

SAP Supported Supported (1) Supported Ability to expose SAP Gateway services created in SAP backend systems.
Gateway (1)

OData
Service
(IW_BEP)
exposure

Custom Supported Not Supported Not An OData service can be implemented on the hub. For example, data can be retrieved from diffe
OData Supported handy if the source system is too old for SAP Gateway to be installed.
service on
the Hub

https://archive.sap.com/documents/docs/DOC-63973 3/7
1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

Multi-Origin Supported Supported Supported The same service can be sourced from multiple SAP backends by appending the parameter ;mo
SAP
Gateway
services

Rule based Supported Not Supported Not Routing a user request to a specific backend, depending on their assigned SAP roles or other crit
routing for Supported
SAP
Gateway
services

SAP Fiori Supported Not Supported Not Deployment of SAP Fiori applications.
App Supported
deployment

Task Supported Planned (2) Supported Consumption of the Task Gateway (http://help.sap.com/saphelp_gateway20sp10/helpdata/en/e4/
Gateway frameset=/en/e4/3143530d9e0050e10000000a44176d/frameset.htm&current_toc=/en/57/a41787
service (TASKPROCESSING) service from different task providers.
consumption

3rd party Not Planned (4) Supported Ability to create OData services based on different data sources like REST services, SOAP servic
data source Supported (5)

integration (3)

and
conversion
to OData

Function Supported Supported Supported Support for the function import feature of the OData format.
Import for (6)

SAP
Gateway
services

https://archive.sap.com/documents/docs/DOC-63973 4/7
1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

(1) Some restrictions apply: no soft-state, no eTags, no subscriptions, no push notifications, no advanced search on catalog service,… For a complete and always
1931374 - Integration Gateway for SAP Mobile Platform 3.0 - Known Constraints (http://service.sap.com/sap/support/notes/1931374)

2169792 - OData Provisioning in SAP Process Orchestration - Known Constraints (http://service.sap.com/sap/support/notes/2169792)

(2) Support planned* starting with SAP Process Orchestration 7.50. Fore more details, please consult the SAP Process Orchestration Roadmap (https://se
Technology / Product Roadmaps / SAP Process Orchestration)
(3) In theory you may write custom ABAP coding to connect to 3rd party data sources in your SAP Gateway OData service implementation, but this can only be se
(4) Support for multiple 3rd party data sources is planned* for SAP Process Orchestration 7.50.
(5) Supported 3rd party data sources: JDBC, REST, SOAP, JPA. Some further restrictions (http://service.sap.com/sap/support/notes/1931374)apply for these data
(6) Function import will only work for SAP Gateway services that are not integrated with 3rd party data sources.

*This is the current state of planning and may be changed by SAP at any time.

(https://people.sap.com/bjoernw)

Bjoern Woppmann (https://people.sap.com/bjoernw)

June 12, 2015 at 10:13 AM
12 Likes

3 replies

William van Strien (https://people.sap.com/william.vanstrien)replied May 28, 2015 at 22:42 PM

(https://people.sap.com/william.vanstrien)

HI Bjoern,

nice article, convenient to have this matrix for decision guide support.

I wrote a conceptual article over the SAP Mobile playing field, subject that overlaps with
your post
https://archive.sap.com/documents/docs/DOC-63973 5/7
1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

Thoughts on SAP Gateway development: The SAP Mobile Integration playing field
(http://wvstrien.blogspot.nl/2014/10/the-sap-mobile-integration-playing-field.html)

glad to hear your feedback, as well as updates now 8 months later.

REgards, William.

Former Member replied May 29, 2015 at 04:11 AM

Hello Bjoern, Nice summary and very helpful matrix. Thanks for sharing.

Regards,

Suresh

Syam Babu (https://people.sap.com/syambabu.allu)replied June 15, 2015 at 14:49 PM

(https://people.sap.com/syambabu.allu)

Bejoern,

Well versed explanation of all possibility in SAP with oData.

Thanks,

Syam

https://archive.sap.com/documents/docs/DOC-63973 6/7
1/28/2020 Capabilities Matrix: Which SAP product to use to expose your business data as OData service for UI consumption

Find us on

(https://www.facebook.com/sapcommunity) (https://twitter.com/SAPCommunity) (https://www.youtube.com/c/SAPCommunities)

(https://www.linkedin.com/company/sap) (https://instagram.com/sap/) (http://www.slideshare.net/SAP) (mailto:?subject='SAP Community')

Privacy (http://sap.com/about/legal/privacy.html) Terms of Use (http://sap.com/corporate/en/legal/terms-of-use.html)

Legal Disclosure (http://sap.com/about/legal/impressum.html) Copyright (http://sap.com/about/legal/copyright.html)

Trademark (http://sap.com/about/legal/trademark.html) Cookie Preferences

Newsletter (https://www.sap.com/cmp/nl/sap-community-voice/index.html) Support (mailto:sapnetwork@sap.com)

https://archive.sap.com/documents/docs/DOC-63973 7/7