Graph in SAP Integration Suite FAQ

The following answers aim to address initial questions you may have about the Graph functionality of API Management in SAP Integration Suite.

1. General Questions

1.1. Getting Started

Q1.1.1: What is Graph?

Graph is the new unified and consolidated API for SAP-managed data. Developers use Graph to build applications that access a business data graph of SAP-managed data, regardless of where this data resides.

Q1.1.2: How can I get updates about Graph or get in touch with the product team?

Sign up to the SAP Integration Suite Community Newsletter or register for the monthly webinar to get regular updates.

1.2. Availability

Q1.2.1: Can I use Graph now?

Yes, the Graph functionality is generally available as part of API Management in SAP Integration Suite
You can also learn how to use the Graph API with the Graph Navigator on SAP Business Accelerator Hub.

1.3. Big Picture

Q1.3.1: How is Graph different from SAP Business Accelerator Hub?

SAP Business Accelerator Hub is the central catalog of APIs from SAP and selected partners for application developers to search, discover, test and consume these APIs to build extensions or integrations using SAP BTP.

Graph is a new and innovative capability of API Management within SAP Integration Suite. Extending traditional API Management, Graph enables you to expose all your business data in the form of a semantically connected data graph, accessed via a single unified and powerful API.

Q1.3.2: Are Graph and SAP HANA Graph related?

The two products fulfill different purposes. SAP HANA Graph is an integral part of SAP HANA core functionality. It expands the SAP HANA platform with native support for graph processing and allows you to execute typical graph operations on the data stored in an SAP HANA system.

Graph is a new capability within SAP Integration Suite used for accessing data from the SAP Intelligent Enterprise systems through an easy-to-use API. The “Graph” name refers to the connections between data objects that allow easy access to associated data.

2. Technical Questions

2.1. How Things Work

Q2.1.1: How is performance affected?

There is some latency when using Graph, but is often offset by the fact that fewer queries are required to achieve the same goal, due to efficient navigation. From initial testing, latency is insignificant (percentage-wise), given that the majority of elapsed time is spent in the data source itself. Graph is not intended to be used for system-to-system integration but rather for extension-app usage (where a ‘user’ is typically a human being).

Q2.1.2: Does Graph save a copy of the data from the source systems somewhere?

Graph does not persist anything. Graph does not copy or store data; all calls are forwarded to the underlying data source systems.

2.2. Data

Q2.2.1: Does Graph support full CRUD-operations?

Graph allows you to create, read, update and delete data, considering any existing access rights and data source boundaries.

Q2.2.2: What about custom entities (extensibility)? Can customers add the APIs and entities for their own custom applications to Graph and maintain them across updates?

Extensions to the data source APIs are automatically taken over into Graph. Customers can additionally define custom model extensions to the out-of-the-box business data graph.

2.3. Data Source Systems

Q2.3.1: Which data source systems are supported?

Currently, and OData data sources, including SAP S/4HANA, SAP Sales Cloud, and SAP SuccessFactors are supported.

Q2.3.2: Will non-SAP data sources be supported?

Currently, non-SAP sources that are OData compliant are supported, but stay tuned for additional planned functionality in this area.

Q2.3.3: Does Graph support ECC?

Graph supports SAP ERP Central Component (ECC) content which has been prepared and exposed as an OData service. To create the service interface, you can use Gateway Builder starting from SAP Gateway version GW_FND 7.52 and the latest SP (refer to SAP Note 2217489 - Maintenance and Update Strategy for SAP Fiori Front-End Server Information published on SAP site) or OData Provisioning.

2.4. SAP Business Technology Platform (BTP)

Q2.4.1: What is necessary from BTP perspective to use Graph?

  • A BTP subaccount, used for configuring the landscape used by Graph.
  • The SAP Integration Suite service where the Graph functionality is available as part of API Management.

  • Most customers would use the security services as well (IDP).

Q2.4.2: Does Graph require a BTP license?

Yes. the owner of the landscape uses an SAP Integration Suite on SAP BTP to configure the business data graph.

2.5. Security

Q2.5.1: How is security managed?

Security is actually enhanced by using Graph. The extension application can only access the Graph API with the key to the landscape (secret), which can be revoked at any time. Business user authorization is in the responsibility of the source system.

Q2.5.2: What is the authorization model for accessing or modifying the data?

Authorization is managed in the data source system itself. Graph does not override the existing authorization configuration on the sources.