PUBLIC

2023-12-04

Feature Scope Description for SAP Integration

Suite
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1 Cloud Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2 API Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4 Open Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.5 Integration Advisor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.6 Trading Partner Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
3.7 Integration Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.8 Migration Assessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
3.9 Edge Integration Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Compliance and Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5 Service Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 Browser Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

7 Service Level Agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Feature Scope Description for SAP Integration Suite

2 PUBLIC Content
1 About this Document

This document describes the features that are available in SAP Integration Suite. The availability of some of the
features may depend on your license agreement with SAP.

To illustrate integration with other SAP offerings, the product documentation on SAP Help Portal might
include references to features that are not included with SAP Integration Suite. Features that are not included
in this feature scope description might require a separate license.

This document does not include any information about:

Packages and pricing available for SAP Integration Suite. For more information, see SAP Discovery Center .

Feature Scope Description for SAP Integration Suite

About this Document PUBLIC 3
2 Introduction

SAP Integration Suite is a versatile, dynamic, and enterprise-grade platform that can simplify integration for
people with diverse skill sets through a variety of integration approaches. Pre-packaged integration scenarios
provide ready-to-go integrations and can rapidly reduce development times. API and digital teams can build
semantic APIs to accelerate digital applications.

Certain constraints might apply with regard to the usage of some of these features (as described in the product
documentation).

 Note

Certain limitations apply with regard to the purchased edition of the product.

Feature Scope Description for SAP Integration Suite

4 PUBLIC Introduction
3 Features

Get a high-level overview about the features of SAP Integration Suite.

SAP Integration Suite comes with the following capabilities. For more information on the features available for
each capability, check out the respective section:

• Cloud Integration [page 5]

• API Management [page 28]
• Graph [page 31]
• Open Connectors [page 32]
• Integration Advisor [page 32]
• Trading Partner Management [page 33]
• Integration Assessment [page 34]
• Migration Assessment [page 34]

3.1 Cloud Integration

Cloud Integration supports end-to-end process integration across cloud-based and on-premise applications
based on the exchange of messages.

It provides capabilities to process messages in integration scenarios spanning different companies,

organizations, or departments within an organization.

Integration Content

Integration developers can use predefined integration content out of the box, enhance it, or develop their own
integration content from scratch.

Integration content refers to all design artifacts that define how a message is to be processed in the course of
an integration scenario.

The following features related to integration content are available.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 5
Integration Content

Feature Description

Predefined content provided by SAP SAP provides reusable integration content which is com-
posed of various predefined integration flows and other el-
ements (for example, value mappings) that cover the inte-
gration requirements for a number of standard integration
scenarios (for example, setting up integration with the Ariba
network or integrating SAP SuccessFactors and SAP ERP).

Develop and edit integration content SAP Cloud Integration provides an integration content de-
signer to develop your own integration content.

You use an integration flow model to specify the senders and

receivers of messages for a scenario, and how messages are
to be processed at runtime. An integration flow is deployed
on a tenant, where it can be executed. It is composed of
adapters (defining how a tenant is connected to remote
systems) and integration flow steps (defining the individual
processing steps).

The supported adapters and integration flow steps are de-

scribed in sections Connectivity and Message Processing of
this document.

You can simulate an integration flow without the need to

deploy it on the tenant (activating of tracing supported).

Deploy integration content on different integration platforms You can deploy and run integration content on different inte-
gration platforms.

Accordingly, different product profiles are available to adapt

the user interface of the integration content designer to the
specifications and capabilities of the target integration plat-
form.

Supported target integration platforms:

• SAP Cloud Integration runtime environment ( runs on

an SAP BTP tenant)
• SAP Process Orchestration (on-premise) runtime envi-
ronment (release SAP Process Orchestration 7.5 SP 0
and higher)

Transport integration content You can transport integration content across tenants using
different options:

• Change and Transport System CTS+

• SAP Cloud Transport Management
• Manual export/import

Feature Scope Description for SAP Integration Suite

6 PUBLIC Features
Connectivity

SAP provides a set of adapters that allow you to specify a certain connection type and to define, for example,
which technical protocols should be used to connect a sender or a receiver system to the tenant and how this
connection is protected.

Note related to terminology:

A receiver adapter connects the tenant to an external system. A sender adapter receives incoming messages
(sent from an external system) or connects the tenant to an external system and polls for messages.

The following adapters are available out of the box.

Adapter

Feature Description

AmazonWebServic Connects SAP Integration Suite to Amazon Web Services.

es
The adapter supports the following protocols:
Sender adapter
• S3: Simple Cloud Storage
• SQS: Simple Queue Service

AmazonWebServic Connects SAP Integration Suite to Amazon Web Services.

es
The adapter supports the following protocols:
Receiver adapter
• S3: Simple Cloud Storage
• SQS: Simple Queue Service
• SNS: Simple Notification Service
• SWF: Simple Workflow Service

AMQP Enables SAP Integration Suite to consume messages from queues or topic subscriptions in an exter-
nal messaging system.
Sender adapter
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0

Supported transport protocols: TCP, WebSocket

AMQP Enables SAP Integration Suite to send messages to queues or topics in an external messaging system.

Receiver adapter Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0

Supported transport protocols: TCP, WebSocket

AMQP for SAP Enables SAP Integration Suite to consume messages from SAP Event Mesh.
Event Mesh
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Sender adapter
Supported transport protocol: WebSocket

AMQP for SAP Enables SAP Integration Suite to send messages to SAP Event Mesh.
Event Mesh
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Receiver adapter
Supported transport protocol: WebSocket

Feature Scope Description for SAP Integration Suite

Features PUBLIC 7
Feature Description

AMQP for Microsoft Enables SAP Integration Suite to consume messages from Microsoft Azure Service Bus.
Azure Service Bus
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Sender adapter
Supported transport protocol: TCP

AMQP for Microsoft Enables SAP Integration Suite to send messages to Microsoft Azure Service Bus.
Azure Service Bus
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Receiver adapter
Supported transport protocol: TCP

AMQP for Solace Enables SAP Integration Suite to consume messages from Solace PubSub+.
PubSub+
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Sender adapter
Supported transport protocol: TCP

AMQP for Solace Enables SAP Integration Suite to send messages to Solace PubSub+.
PubSub+
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Receiver adapter
Supported transport protocol: TCP

AMQP for Apache Enables SAP Integration Suite to consume messages from Apache Qpid Broker-J.
Qpid Broker-J
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Sender adapter
Supported transport protocol: TCP, WebSocket

AMQP for Apache Enables SAP Integration Suite to send messages to Apache Qpid Broker-J.
Qpid Broker-J
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Receiver adapter
Supported transport protocol: TCP, WebSocket

AMQP for Apache Enables SAP Integration Suite to consume messages from Apache ActiveMQ 5 / Apache ActiveMQ
ActiveMQ 5 / Artemis.
Apache ActiveMQ
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Artemis
Supported transport protocol: TCP
Sender adapter

AMQP for Apache Enables SAP Integration Suite to send messages to Apache ActiveMQ 5 / Apache ActiveMQ Artemis.
ActiveMQ 5 /
Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0
Apache ActiveMQ
Artemis Supported transport protocol: TCP

Receiver adapter

AMQP for IBM MQ Enables SAP Integration Suite to consume messages from IBM MQ.

Sender adapter Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0

Supported transport protocol: TCP

Feature Scope Description for SAP Integration Suite

8 PUBLIC Features
 Feature Description

AMQP for IBM MQ Enables SAP Integration Suite to send messages to IBM MQ.

Receiver adapter Supported message protocol: AMQP (Advanced Message Queuing Protocol) 1.0

Supported transport protocol: TCP

Ariba Connects SAP Integration Suite to the Ariba Network. Using this adapter, SAP and non-SAP cloud
applications can receive business-specific documents in commerce eXtensible Markup Language
Sender adapter
(cXML) format from the Ariba network.

The sender adapter allows you to define a schedule for polling data from Ariba.

Ariba Connects SAP Integration Suite to the Ariba network. Using this adapter, SAP and non-SAP cloud ap-
plications can send business-specific documents in commerce eXtensible Markup Language (cXML)
Receiver adapter
format to the Ariba network.Receiver adapter

AS2 Enables SAP Integration Suite to exchange business-specific documents with a partner through the
Applicability Statement 2 (AS2) protocol.
Sender adapter
Sender adapter: Can return an electronic receipt to the sender of the AS2 message (in the form of a
Message Disposition Notification (MDN))

AS2 Enables SAP Integration Suite to exchange business-specific documents with a partner through the
Applicability Statement 2 (AS2) protocol.
Receiver adapter

AS4 Enables SAP Integration Suite to securely process incoming AS4 messages using Web Services.
The AS4 sender adapter is based on the ebMS 3.0 specification that supports the ebMS handler
Sender adapter
conformance profile.

• Supports one-way/ebMS3 push message exchange pattern (MEP).

• Support on-way/ebMS3 pull that allows the message party to pick the corresponding message
from the partner.
• Supports signature verification and decryption of the message.
• Generates receipts after processing the incoming AS4 message.
• Allows you to set a size limit for the body and attachment of an incoming message.

AS4 Enables SAP Integration Suite to establish a connection between any two message service handlers
(MSHs) for exchanging business documents. The AS4 receiver adapter uses the Light Client conform-
Receiver adapter
ance policy and supports only message pushing for the sending MSH and selective message pulling
for the receiving MSH.

Receiver adapter:

• Supports one-way/push message exchange pattern (MEP) that involves the transfer of business
documents from a sending MSH to a receiving MSH.
• Supports one-way/selective-pull message exchange pattern (MEP) that involves the receiving
MSH initiating a selective pull request to the sending MSH. The sending MSH responds by
sending the specific user message.
• Supports storing and verification of receipts.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 9
Feature Description

AzureStorage Enables SAP Integration Suite to receive files from Azure Storage.

Sender adapter

AzureStorage Enables SAP Integration Suite to connect to Azure Storage, to manage files, containers, folders, and
messages, and to perform create, read, update and delete (CRUD) operations on objects stored there.
Receiver adapter

Data Store Enables SAP Integration Suite to consume messages from a data store.

Sender adapter

Dropbox Enables SAP Integration Suite to receive files from the Dropbox storage.

Sender adapter

Dropbox Enables SAP Integration Suite to write files and folders to the Dropbox storage.

Receiver adapter

ELSTER Enables SAP Integration Suite to send a tax document to the ELSTER server.

Receiver adapter ELSTER (acronym for the German term Elektronische Steuererklärung) is used in German fiscal
management to process tax declarations exchanged over the Internet.

The adapter supports the following operations: Getting the version of the ERiC (ELSTER Rich Client)
library, validating a tax document, and sending a tax document.

Facebook Enables SAP Integration Suite to access and extract information from Facebook based on certain
criteria such as keywords or user data.
Receiver adapter
Using OAuth, the SAP BTP tenant can access resources on Facebook on behalf of a Facebook user.

FTP Enables SAP Integration Suite to connect to a remote system using TCP (Transmission Control
Protocol) to receive files from the system.
Sender adapter
FTP stands for File Transfer Protocol.

The sender adapter allows you to define a schedule for polling data from the connected system.

FTP Enables SAP Integration Suite to connect to a remote system using TCP (Transmission Control
Protocol) to write files to the system.
Receiver adapter
FTP stands for File Transfer Protocol.

HTTPS Establishes an HTTPS connection between SAP Integration Suite and a sender system.

Sender adapter

Feature Scope Description for SAP Integration Suite

10 PUBLIC Features
 Feature Description

HTTP Establishes an HTTP connection between SAP Integration Suite and a receiver system.

Receiver adapter Receiver adapter:

• Supports HTTP 1.1 only (target system must support chunked transfer encoding and may not rely
on the existence of the HTTP Content-Length header)
• Supports the following methods: DELETE, GET, HEAD, POST, PUT, TRACE
Method can also be determined dynamically by reading a value from a message header or
property during runtime.

IDoc Allows SAP Integration Suite to exchange Intermediate Document (IDoc) messages with a sender
system that supports communication via SOAP Web services.
Sender adapter
A size limit for the inbound message can be configured for the sender adapter.

IDoc Allows SAP Integration Suite to exchange Intermediate Document (IDoc) messages with a receiver
system that supports communication via SOAP Web services.
Receiver adapter

JDBC Allows SAP Integration Suite to connect to a JDBC (Java Database Connectivity) database and to
execute SQL commands on the database.
Receiver adapter

JDBC for DB2 (On- Allows SAP Integration Suite to connect to DB2 (On-Premise) using JDBC (Java Database Connectiv-
Premise) ity) and to execute SQL commands on the database.

Receiver adapter

JDBC for Microsoft Allows SAP Integration Suite to connect to Microsoft SQL Server (Cloud) using JDBC (Java Database
SQL Server (Cloud) Connectivity) and to execute SQL commands on the database.

Receiver adapter

JDBC for Microsoft Allows SAP Integration Suite to connect to Microsoft SQL Server (On-Premise) using JDBC (Java
SQL Server (On- Database Connectivity) and to execute SQL commands on the database.
Premise)

Receiver adapter

JDBC for Oracle Allows SAP Integration Suite to connect to Oracle (Cloud) using JDBC (Java Database Connectivity)
(Cloud) and to execute SQL commands on the database.

Receiver adapter

JDBC for Oracle Allows SAP Integration Suite to connect to Oracle (On-Premise) using JDBC (Java Database Connec-
(On-Premise) tivity) and to execute SQL commands on the database.

Receiver adapter

JDBC for Allows SAP Integration Suite to connect to PostgreSQL (Cloud) using JDBC (Java Database Connec-
PostgreSQL tivity) and to execute SQL commands on the database.
(Cloud)

Receiver adapter

Feature Scope Description for SAP Integration Suite

Features PUBLIC 11
Feature Description

JDBC for SAP Allows SAP Integration Suite to connect to SAP HANA Cloud using JDBC (Java Database Connectiv-
HANA Cloud ity) and to execute SQL commands on the database.

Receiver adapter

JDBC for SAP Allows SAP Integration Suite to connect to SAP HANA Platform (On-Premise) using JDBC (Java
HANA Platform Database Connectivity) and to execute SQL commands on the database.
(On-Premise)

Receiver adapter

JMS Enables asynchronous messaging by using message queues.

Sender adapter The sender adapter consumes messages from a queue. The messages are processed concurrently.

To prevent situations where the JMS adapter tries again and again to process a failed (large) message,
you can store messages (where the processing stopped unexpectedly) in a dead-letter queue after
two retries.

Certain constraints apply with regard to the number and capacity of involved queues, as well as for the
headers and exchange properties defined in the integration flow before the message is saved to the
queue (as described in the product documentation).

JMS Enables asynchronous messaging by using message queues.

Receiver adapter The receiver adapter stores messages and schedules them for processing in a queue. The messages
are processed concurrently.

Kafka Allows SAP Integration Suite to connect to an external Kafka broker via Kafka protocol and to fetch
Sender adapter Kafka records (messages).

Kafka Allows SAP Integration Suite to connect to an external Kafka broker via Kafka protocol and to send
Receiver adapter Kafka records (messages).

Mail Sender for Enables SAP Integration Suite to read e-mails from an e-mail server using the Internet Message
IMAP Access Protocol (IMAP) protocol.

Sender adapter To authenticate against the e-mail server, you can send the user name and password in plain text or
encrypted (the latter only if the e-mail server supports this option).

You can protect inbound e-mails at the transport layer with IMAPS and STARTTLS.

The sender adapter allows you to define a schedule for polling data from the connected system.

For more information on possible threats when processing e-mail content with the Mail adapter, see
the product documentation.

Feature Scope Description for SAP Integration Suite

12 PUBLIC Features
 Feature Description

Mail Sender for Enables SAP Integration Suite to read e-mails from an e-mail server using the Post Office Protocol
POP3 (POP3) protocol.

Sender adapter To authenticate against the e-mail server, you can send the user name and password in plain text or
encrypted (the latter only if the e-mail server supports this option).

You can protect inbound e-mails at the transport layer with POP3S and STARTTLS.

The sender adapter allows you to define a schedule for polling data from the connected system.

For more information on possible threats when processing e-mail content with the Mail adapter, see
the product documentation.

Mail Enables SAP Integration Suite to send e-mails to an e-mail server.

Receiver adapter To authenticate against the e-mail server, you can send the user name and password in plain text or
encrypted (the latter only if the e-mail server supports this option).

• You can protect outbound e-mails at the transport layer with STARTTLS or SMTPS.
• You can encrypt outbound e-mails using S/MIME (supported content encryption algorithms:
AES/CBC/PKCS5Padding, DESede/CBC/PKCS5Padding).

MDI The MDI (SAP Master Data Integration) adapter synchronizes your master data from SAP applications
like SAP ECC and other third party applications with SAP MDI service.
Receiver adapter

Microsoft Connects SAP Integration Suite to Microsoft Dynamics Customer Relationship Management (CRM).
Dynamics CRM

Receiver adapter

Microsoft Connects SAP Integration Suite to a remote system using the HTTP/HTTPS protocol to read files from
SharePoint the system.

Sender adapter

Microsoft Connects SAP Integration Suite to a remote system using the HTTP protocol to write files to the
SharePoint system.

Receiver adapter

OData Connects SAP Integration Suite to systems using the Open Data (OData) protocol in either ATOM or
JSON format (only synchronous communication is supported).
Sender adapter
Supported versions: OData version 2.0

• The adapter receives incoming requests in either ATOM or JSON format.

• Supported operations: Create (POST), Delete (DELETE), Query (GET), Read (GET), Update (PUT)
Using the GET or POST method, the sender adapter can also invoke operations that are not
covered by the standard CRUD (Create, Retrieve, Update, and Delete) methods (function import).

Feature Scope Description for SAP Integration Suite

Features PUBLIC 13
Feature Description

OData Connects SAP Integration Suite to systems using the Open Data (OData) protocol.

Receiver adapter Supported versions:

• OData version 2.0

Supported operations: Create (POST), Delete (DELETE), Merge (MERGE), Query (GET), Read
(GET), Update (PUT), Patch (PATCH)
• OData version 4.0
Supported operations: Create (POST), Query (GET), Update (PUT)
• The outgoing request payload must be in XML format.

ODC Connects SAP Integration Suite to SAP Gateway OData Channel (through transport protocol HTTPS).

Receiver adapter Supported operations: Create (POST), Delete (DELETE), Merge (MERGE), Query (GET), Read (GET),
Update (PUT)

OpenConnectors Connects SAP Integration Suite to more than 150 non-SAP Cloud applications that are supported by
SAP Open Connectors.
Receiver adapter
• Uses APIs to fetch data from specific third-party applications.
• Is designed to handle large volumes of incoming data.
• Supports messages in both JSON and XML format, for request and response calls.
• Allows you to define specific values for variables.

ProcessDirect Connects an integration flow with another integration flow deployed on the same tenant.

Sender adapter An integration flow with a ProcessDirect sender adapter (as consumer) consumes data from another
integration flow.

N:1 cardinality of producer and consumer integration flows is supported.

ProcessDirect Connects an integration flow with another integration flow deployed on the same tenant.

Receiver adapter An integration flow with a ProcessDirect receiver adapter (as producer) sends data to another integra-
tion flow.

N:1 cardinality of producer and consumer integration flows is supported.

RabbitMQ Allows SAP Integration Suite to consume messages from the RabbitMQ server. In addition, you use
the adapter to send acknowledgements to the RabbitMQ server.
Sender adapter

RabbitMQ Allows SAP Integration Suite to send messages to the RabbitMQ server.

Receiver adapter

RFC Connects SAP Integration Suite to a remote receiver system using Remote Function Call (RFC).

Receiver adapter RFC is the standard interface used for integrating on-premise ABAP systems to the systems hosted
on the cloud using SAP Cloud Connector.

The adapter supports SAP NetWeaver, version 7.31 or higher.

Feature Scope Description for SAP Integration Suite

14 PUBLIC Features
 Feature Description

Salesforce Connects SAP Integration Suite to Salesforce.

Sender adapter

Salesforce Connects SAP Integration Suite to Salesforce.

Receiver adapter

ServiceNow Connects SAP Integration Suite to ServiceNow. Supports basic authentication and OAuth.

Receiver adapter

SFTP Connects SAP Integration Suite to a remote system using the SSH File Transfer protocol to read files
from the system. SSH File Transfer protocol is also referred to as Secure File Transfer protocol (or
Sender adapter
SFTP).

Supported versions:

SSH version 2 (as specified at The Secure Shell (SSH) Protocol Architecture ), SSH File Transfer
Protocol (SFTP) version 3 or higher

The sender adapter allows you to define a schedule for polling data from the connected system.

SFTP Connects SAP Integration Suite to a remote system using the SSH File Transfer protocol to write files
to the system. SSH File Transfer protocol is also referred to as Secure File Transfer protocol (or SFTP).
Receiver adapter
Supported versions:

SSH version 2 (as specified at The Secure Shell (SSH) Protocol Architecture ), SSH File Transfer
Protocol (SFTP) version 3 or higher

Slack Enables SAP Integration Suite to receive search-related information from the Slack storage.

Sender adapter

Slack Enables SAP Integration Suite to get data from the Slack storage or to create, modify, or delete data
on the Slack storage.
Receiver adapter

SOAP SOAP 1.x Exchanges messages with a sender system that supports Simple Object Access Protocol (SOAP) 1.1
or SOAP 1.2.
Sender adapter
The message exchange patterns supported by the sender adapter are one-way messaging or request-
reply.

The adapter supports Web services Security (WS-Security).

A size limit for the inbound message can be configured for the sender adapter.

SOAP SOAP 1.x Exchanges messages with a receiver system that supports Simple Object Access Protocol (SOAP) 1.1
or SOAP 1.2.
Receiver adapter
The adapter supports Web services Security (WS-Security).

Feature Scope Description for SAP Integration Suite

Features PUBLIC 15
Feature Description

SOAP SAP RM Exchanges messages with a sender system based on the SOAP communication protocol and SAP Re-
liable Messaging (SAP RM) as the message protocol. SAP RM is a simplified communication protocol
Sender adapter
for asynchronous Web service communication that does not require the use of Web Service Reliable
Messaging standards.

A size limit for the inbound message can be configured for the sender adapter.

SOAP SAP RM Exchanges messages with a receiver system based on the SOAP communication protocol and SAP
Reliable Messaging (SAP RM) as the message protocol. SAP RM is a simplified communication pro-
Receiver adapter
tocol for asynchronous Web service communication that does not require the use of Web Service
Reliable Messaging standards.

Splunk Enables SAP Integration Suite to receive search-related information from the Splunk storage.

Sender adapter

Splunk Enables SAP Integration Suite to get data from the Splunk storage or to create, modify, or delete data
on the Splunk storage.
Receiver adapter

SuccessFactors Connects SAP Integration Suite to a SuccessFactors sender system using the REST message proto-
REST col.

Sender adapter The adapter supports the following operations: GET

SuccessFactors Connects SAP Integration Suite to a SuccessFactors receiver system using the REST message proto-
REST col.

Receiver adapter The adapter supports the following operations: GET, POST

SuccessFactors Connects SAP Integration Suite to SOAP-based Web services of a SuccessFactors sender system
SOAP (synchronous or asynchronous communication).

Sender adapter The adapter supports the following operations: Query

SuccessFactors Connects SAP Integration Suite to SOAP-based Web services of a SuccessFactors receiver system
SOAP (synchronous or asynchronous communication).

Receiver adapter The adapter supports the following operations: Insert, Query, Update, Upsert

Feature Scope Description for SAP Integration Suite

16 PUBLIC Features
 Feature Description

SuccessFactors Connects SAP Integration Suite to a SuccessFactors system using OData V2.
OData V2
Features of OData version 2.0 supported by the adapter:
Receiver adapter
• Operations: GET (get single entity as an entry document), PUT (update existing entry with an
entry document), POST (create new entry from an entry document), DELETE (Delete an entry
from an entry document), UPSERT (combination of Update OR Insert)
• Query options: $expand, $skip,and $top
• Server-side pagination
• Client-side pagination
• Pagination enhancement: Data retrieved in chunks and sent to Cloud Integration
• Deep insert: Creates a structure of related entities in one request
• Authentication options: Basic authentication
• Reference links: Link two entities using the <link> tag

SuccessFactors Connects SAP Integration Suite to a SuccessFactors system using OData V4.
OData V4
Features of OData version 4.0 supported by the adapter:
Receiver adapter
• Operations: GET, POST, PUT, DELETE
• Navigation
• Primitive types supported according to OData V4 specification
• Structural types supported for create/update operations:
Edm.ComplexType, Edm:EnumType, Collection(Edm.PrimitiveType) and Collection(Edm.Com-
plexType)

SugarCRM Connects SAP Integration Suite to SugarCRM.

Receiver adapter

Twitter Enables SAP Integration Suite to access Twitter and read or post tweets.

Receiver adapter Using OAuth, SAP Integration Suite can access resources on Twitter on behalf of a Twitter user.

Workday Connects SAP Integration Suite to Workday. Supports Workday SOAP API with basic authentication.

Receiver adapter

XI Connects SAP Integration Suite to a remote sender system that can process the XI message protocol.

Sender adapter

XI Connects SAP Integration Suite to a remote receiver system that can process the XI message proto-
col.
Receiver adapter

Message Processing

The Cloud Integration system can process messages in different ways.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 17
The following message processing features are available.

Message Transformation

Feature Description

Mapping Transforms the data structure and format used by the sender into a structure and format that
the receiver can process.

Supports the following kinds of mappings:

• Message mappings designed with a graphical editor as part of the Cloud Integration
toolset (supports XSD and EDMX structures)
• Custom-mapping functions defined in scripts
• XSLT mappings (defined in an XSLT resource)

ID Mapping Maps the source message ID to a target message ID. You can use this feature to implement
scenarios with exactly once processing of messages.

Content Modifier Modifies the content of an inbound message by changing the header or body of the message.

A message is composed of a message body and message headers. Furthermore, when being
processed on a Cloud Integration tenant, additional data associated with the message can
be passed along in an additional container (referred to as message exchange) to make it
available at a later point in time during message processing. The Content Modifier can read
data from and write data to the message body, the message header, and the properties area
of the message exchange. That way, the content of a message can flexibly be modified and
prepared for a receiver or subsequent processing steps.

Certain constraints apply with regard to the supported data formats (as described in the
product documentation).

XML Modifier Modifies the content of an inbound message by removing external DTDs and/or removing
XML declarations.

Converter Transforms an input message into another format.

The following converters are available:

• XML to JSON: Transforms messages in XML format to JSON format.

You can specify streaming (with either the whole XML document or only specified XML
elements presented by JSON arrays).
• JSON to XML: Transforms messages in JSON format to XML format.
• XML to CSV: Transforms messages in XML format to CSV format.
• CSV to XML: Transforms messages in CSV format to XML format.
• XML to EDI: Transforms a message in XML format to Electronic Data Interchange (EDI)
format.
• EDI to XML: Transforms a message in EDI format (EDIFACT or ASC-X12 format) to XML
format.

Certain constraints apply with regard to the supported data formats (as described in the
product documentation).

Feature Scope Description for SAP Integration Suite

18 PUBLIC Features
 Feature Description

Decoder Decodes the incoming message to retrieve the original data (for example, if a base64-en-
coded message has been received).

• Base64 Decode: Decodes base64-encoded message content.

• GZIP Decompress: Decompresses the message content using GNU zip (GZIP).
• ZIP Decompress: Decompresses the message content using zip (only zip archives with a
single entry supported).
• MIME Multipart Decode: Transforms a MIME multipart message into a message with
attachments.

Encoder Encodes the message using an encoding scheme to secure any sensitive message content
during transfer over the network.

• Base64 Encode
Encodes the message content using base64.
• GZIP Compress: Compresses the message content using GNU zip (GZIP).
• ZIP Compress: Compresses the message content using zip (only zip archives with a
single entry supported).
• MIME Multipart Encode: Transforms the message content into a MIME multipart mes-
sage.
If you want to send a message with attachments, but the protocol (for example, HTTP
or SFTP) does not support attachments, you can send the message as a MIME multipart
instead.

 Note
Note that SAP Cloud Integration does not support the processing of MIME multipart
messages that contain multiple attachments with the same file name.

Filter Filters information by extracting a specific node from the incoming message by using an
XPath expression.

Message Digest Calculates a digest of the payload or parts of it and stores the result in a message header.

Script Executes custom Java script or Groovy script for message processing.

Calling External Systems or Subprocesses

Feature Description

Request-Reply Calls an external receiver system in a synchronous step and gets back a response.

Send Calls an external receiver system for use cases where no reply is expected.

Content Enricher Calls an external system, accesses resources of this system, and merges the returned con-
tent with the original message.

Poll Enrich Step Polls content from an external component, and enriches the original message with it.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 19
Feature Description

Process Call Calls a local integration process.

A local integration process defines a container for a separate subprocess to be called

from the main process. Using local integration processes, a complex message processing
sequence can be fragmented and decomposed into smaller parts.

Looping Process Call Calls a local integration process in a loop.

Idempotent Process Call Detects if a message ID has already been successfully processed and stores the status of
the successful process in the idempotent repository. If there's duplicate execution with the
same message ID (for example if there’s a retry by the sender system), the called subprocess
can either be skipped or the message is marked as a duplicate. You can then decide how to
handle the duplicate in the subprocess.

Routing

Feature Description

Router Routes a message to one or more receivers.

SAP Cloud Integration also supports routing that depends on the content of the message
(content-based routing). For example, the tenant detects that a message has a particular
field value, and forwards it to the specific receiver participant that handles requests from the
sender participant.

Multicast Sends the same message to more than one receiver.

• Parallel multicast: Initiates message transfer to all the receiver nodes in parallel
• Sequential multicast: defines the sequence in which the message transfer to the receiv-
ers is initiated.

Feature Scope Description for SAP Integration Suite

20 PUBLIC Features
 Feature Description

Splitter Decomposes a composite message into a series of individual messages and sends them to a
receiver.

Supported splitters:

• General splitter: Breaks down a composite message containing ‘n’ messages into ‘n’
individual messages. Each individual message is enveloped by the same elements that
enveloped the composite message.
• Iterating splitter: Splits a composite message into a series of smaller messages without
copying the enveloping elements of the composite message
• PKCS#7/CMS splitter: Splits a PKCS7 Signed Data message that contains a signature
and content (and breaks down the signature and content into separate files)
• IDoc splitter: Splits a composite IDoc messages into a series of individual IDoc mes-
sages with the enveloping elements of the composite IDoc message
• EDI splitter: Splits a bulk EDI message into a series of individual messages and validates
and acknowledges the inbound message.
A bulk EDI message can contain one or more EDI formats, such as EDIFACT, EANCOM,
or ASC-X12. The EDI splitter can process different EDI formats depending on the busi-
ness requirements of the trading partners.
• Zip splitter: Splits an inbound archive file (.zip) into individual files.
• Tar splitter: Splits an archive (.tar) file into individual files.

Certain constraints apply with regard to the supported data formats (as described in the
product documentation).

Join Merges messages from different routes and combines them into a single message.

This feature is used in combination with the Gather feature. Join simply brings together the
messages from different routes; it doesn't affect the content of the messages.

Certain constraints apply with regard to the usage of this feature (as described in the
product documentation).

Gather Merges messages from different routes (into a single message) with the option to define
certain strategies how to combine the initial messages.

Storing Data During Processing

Feature Description

Persist Message Stores a message payload so that you can access the stored message and analyze it at a
later point in time.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 21
Feature Description

Data Store Operations Stores messages temporarily for later processing.

The following operations are supported:

• SELECT
• GET
• WRITE
• DELETE

Write Variables Specifies values for variables required during message processing.

Protecting Messages

Feature Description

Encryptor Encrypts the content of a message.

Supported standards:

• PGP
• PKCS#7/CMS Enveloped Data and Signed Data

Decryptor Decrypts the content of a message.

Supported standards:

• PGP
• PKCS#7/CMS Enveloped Data and Signed Data

Signer Signs a message.

Supported standards:

• PKCS#7/CMS Enveloped Data and Signed Data

• XML Digital Signature

Verifier Verifies a message.

Supported standards:

• PKCS#7/CMS Enveloped Data and Signed Data

• XML Digital Signature

Feature Scope Description for SAP Integration Suite

22 PUBLIC Features
Additional Features

Feature Description

Transactional processing Ensures data consistency by processing the message within one transaction (supported
when Java Message Service (JMS) and Java Database Connectivity (JDBC) resources are
used in an integration flow.

This feature is supported for the following resources:

• JDBC resources: Data Store Operations (Write, Get, Select, Delete), Write Variables,
Aggregator
• JMS resources: JMS sender and receiver adapter, AS2 sender adapter

Either a JMS transaction or a JDBC transaction can be handled (no support for distributed
transactions between JMS and JDBC resources).

Externalization Supports parameterization of certain integration flow attributes (as listed in the product
documentation). This means that you can provide the attribute values in a later configura-
tion step without having to edit the integration flow.

Dynamic attributes You can define placeholders for certain integration flow attributes (as listed in the product
documentation). The values of these attributes are then set dynamically based on the
content of the processed message.

API-Based Integration Development

SAP Cloud Integration supports API-based integration development (as an alternative to coding).

The SAP Cloud Integration Design application provides graphical editors to design the following kinds of APIs:

• OData API (an OData API-based integration scenario with OData V2 sender adapter)
• REST API (a REST API-based integration scenario with HTTPS sender adapter
• SOAP API (a SOAP API-based integration scenario with SOAP 1.x sender adapter)

The SAP Cloud Integration Monitor application allows you to deploy and manage SOAP, REST, and OData APIs
and to monitor message processed through these APIs.

Certain constraints might apply with regard to the usage of some of these features (as described in the product
documentation).

OData API

The following features are available for OData API development.

Integration developers can develop OData APIs that expose existing data sources, such as SOAP, as OData
endpoints. These OData APIs can be consumed by SAP Fiori apps, SAP Mobile Services, or any other custom
app, to address user-centric scenarios.

You can develop OData APIs that expose existing data sources, such as SOAP, as OData endpoints. These
OData APIs can be consumed by SAP Fiori apps, SAP BTP Mobile Services, or any other custom app, to
implement user-centric scenarios.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 23
OData API Development Features

Feature Description

Import from SOAP Create an OData model or add to an existing one by importing the model definition from
SOAP Web services.

Import from OData Create an OData model or add to an existing one by importing the model definition from an
existing OData API.

Import from ODC Create an OData model or add to an existing one by importing the model definition from
an OData API that is created in the IW_BEP component of an on-premise Gateway system
(ODC).

Edit an OData model Create an OData model from scratch or edit an existing model using the OData Model
Editor.

View an OData model View the overall layout of an OData model in the Graphical Model Viewer.

Bind to SOAP Bind function imports and operations of entity sets in your OData model to the correspond-
ing SOAP Web service operations.

Bind to OData Bind function imports and operations of entity sets in your OData model to the correspond-
ing OData APIs.

Bind to REST Bind function imports and operations of entity sets in your OData model to the correspond-
ing REST services.

Bind to ODC Bind function imports and operations of entity sets in your OData model to the correspond-
ing OData APIs that are created in the IW_BEP component of an on-premise Gateway
system (ODC).

Edit predefined integration Edit and update predefined integration flows that have an OData sender adapter to suit
flows your business scenario. The SAP Cloud Integration Web application sets up predefined
integration flows when OData objects are bound to a data source.

Deploy OData API Deploy an OData API once it's ready. SAP Cloud Integration also helps you monitor the
service after deployment.

Monitoring and Operations

Enable integration developers to monitor the processing of messages and the components of the platform at
runtime, to manage artifacts required to set up a secure connection of the tenant and remote systems, and to
manage tenant-specific data stores.

Feature Scope Description for SAP Integration Suite

24 PUBLIC Features
 Feature Description

Monitor message processing Provides an overview of the messages processed on a tenant and displays the detailed
sequence of processing steps for individual messages (message processing log).

Different log levels are available (no logging information, all messages logged and dis-
played, only error messages logged and displayed).

Manage integration content Provides an overview of integration content artifacts, such as integration flows or security
artifacts, that have been deployed on the tenant.

Allows you to deploy or undeploy artifacts.

Manage security artifacts and Allows you to deploy security-relevant artifacts (for example: user credentials, PGP public
deploy them on the tenant keyring, PGP secret keyring, SSH known hosts artifact, secure parameter artifact, and
OAuth2 credentials).

Manage keystore entries Allows you to manage the tenant keystore and its entries (X.509 certificates and key
pairs).

Supported functions:

• Creating a key pair

• Creating an SSH key
• Showing details of a keystore entry
• Uploading a keystore entry
You can upload or add individual entries to an existing keystore. In the latter case,
you can overwrite existing entries or keep them (SAP-owned keystore entries can't
be changed or deleted).
• Downloading the public content of a keystore or a single keystore entry
• Deleting a keystore entry (not supported for SAP-owned keystore entries)
• Backing up keystore entries owned by the tenant administrator
• Restoring backed-up keystore entries

Certain constraints apply with regard to the size of the keystore (as described in the
product documentation).

Manage the lifecycle of keys Eases the tenant administrator's task of renewing keys provided by SAP on the tenant.

Supported functions:

• Activating a new key pair provided by SAP to replace an old key pair that expires
soon
• Restoring an old key pair

Manage access policies Allows you to guard access to message processing log attachments and trace data on the
level of individual integration flows.

Manage JDBC data sources Allows you to manage access to database systems a tenant can connect to (using the
JDBC receiver adapter).

Test connectivity Allows you to test outbound TLS, SSH, FTP, SMTP, IMAP, POP3, AMQP, and Kafka connec-
tions. You can also check whether a certain Cloud Connector instance can be reached.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 25
Feature Description

Manage user roles Allows you to manage user roles to grant permissions to execute an integration flow.

Manage stores Provides an overview of the stores on the tenant that are temporarily used to persist
different types of data during message processing.

Supported kinds of stores:

• Data stores
• Variables
• Message queues (only available if a message broker has been provisioned)
Queues that are active for a tenant (including retry of selected messages in the
queue, deleting messages, or downloading messages as file archive).
• Number ranges

Manage locks Allows you to display and manage lock entries, which are created to avoid the same
message being processed several times in parallel (for example, by different runtime
nodes).

Archive data You can connect Cloud Integration to a remote content management system and use this
system to archive data.

You can archive the following kind of data:

• Messages received from a sender and responses returned to a sender

• Messages sent to a receiver and responses returned from a receiver
• Messages stored by the Persist integration flow step
• Message processing log attachments

Note that the content management system isn't part of the Cloud Integration feature
scope.

Inspection of Resource Consumption

Inspect the usage of integration resources.

Feature Description

Inspect resource consumption Inspect the usage of integration resources (for example, database connections or trans-
actions) by integration scenarios.

Perform steps to resolve critical situations.

Business-to-Business Integration

The following features support you in setting up business-to-business (B2B) integration scenarios.

Feature Scope Description for SAP Integration Suite

26 PUBLIC Features
 Feature Description

SAP Integration Advisor Allows you to specify integration content for B2B scenarios.

Partner Directory Allows you to store information about communication part-

ners and to parameterize integration flows using this infor-
mation (accomplished by using script steps in the integra-
tion flow).

The Partner Directory helps you to set up a communication

network between many communication partners efficiently.

AS2 adapter Allows a tenant to exchange business-specific documents

with a partner through the Applicability Statement 2 (AS2)
protocol.

For more information, see the section Connectivity.

Support of the EDI standard The following integration flow steps allow you to config-
ure scenarios where Electronic Data Interchange (EDI) mes-
sages are involved: EDI Splitter, XML to EDI converter, and
EDI to XML converter.

For more information, see the section Message Processing.

Application Programming Interfaces

Cloud Integration provides various application programming interfaces (APIs) that you can use to access data.

The following types of API access are supported.

Feature Description

Java API Allows you to execute a Java script to define message processing and to build custom
adapters.

The Java standard libraries of Java 8 can be used.

Cloud Integration supports the XML Document Object Model (DOM) to process XML
documents.

OData API Allows you to access data (for example, monitoring data).

The API is implemented as a REST API and the technical protocol is Open Data Protocol
(OData). OData specification version 2.0 is supported.

The API is protected by basic authentication and OAuth.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 27
Data Storage

Certain components store data on the tenant.

Feature Description

Store data in the Cloud Integration system The following components store data in the Cloud
Integration system:

• Integration flow steps: Data Store operations, Write

variables, Message Store
• Partner Directory
• Message processing log (including attachments)

Store data using Java Messaging Service (JMS) queues The following components can store data in JMS queues:

• JMS receiver adapter

• AS2 sender adapter
• AS4 sender adapter
• XI sender and receiver adapter

3.2 API Management

API Management lets you publish, promote, and oversee APIs in a secure and scalable environment.

Feature Description

Building APIs API portal is an application that provides a common platform for API designers to
define and publish APIs. Every API Management customer is provided with their
own API portal application on cloud. The API portal offers capabilities to configure
systems, build and publish APIs, analyze and test APIs.

Publishing APIs A Product is a bundle of APIs. It contains metadata specific to your business for
monitoring or analytics. For example, all APIs related to CRM can be bundled as one
CRM Product. Instead of publishing APIs individually, it is easier to bundle related
APIs together as a Product and publish it. After including the required APIs to a
Product, the Product is published to the Catalog, where the Product is available for
Application developers to browse through.

Analyzing APIs API Management provides comprehensive analytics capabilities to understand the
various patterns of API consumption. The API Analytics server uses the runtime data
of the APIs to analyze the information. The runtime data is gathered, analyzed, and
displayed as charts, headers, and key performance indicators (KPIs).

Feature Scope Description for SAP Integration Suite

28 PUBLIC Features
 Feature Description

Consuming APIs API business hub enterprise is an application that provides a common platform
for Application developers to consume APIs. Every API Management customer is
provided with their own API business hub enterprise application on cloud. The
API business hub enterprise offers capabilities to onboard application developers,
explore and test APIs, create and subscribe to Applications.

Monetizing APIs SAP API Management provides monetization feature to all API providers to generate
revenue for using the APIs. As an API Admin, you can create a rate plan and attach a
rate plan to a Product in the API Portal and publish the product in the API business
hub enterprise. You can also view bill details of each developer in the API Portal.
As an application developer, in the API business hub enterprise, you can create an
application and add products to the application. Based on the product usage, you
can view the corresponding bill details.

Discover API Packages In API Management, you can discover API Management platform supported API
packages available in SAP Business Accelerator Hub on the API Portal.

Security Data Protection and Privacy for API Management- Various types of customer data
are processed by and stored on API Management at different times. This data gets
the highest level of protection, and SAP takes dedicated measures to guarantee this
security level.

Auditing and Logging Information for API Management- An audit log, also called an
audit trail, is essentially a record of events and changes. SAP software creates logs
based on events. Audit logs are records of these event logs, typically representing
security-relevant chronological records that provide documentary evidence for an
event or activity.

API Designer Model APIs using the API designer. The API designer is based on the OpenAPI Spec-
ification (OAS) standard, which is an open source collaborative project. The API
designer allows you to seamlessly create and edit APIs, and view its corresponding
documentation in a single window frame. It has rich inbuilt capabilities, which may
not be limited to conversion of APIs from one format to another (for example, from
RAML to YAML, JSON to YAML and vice versa), generate server and client stubs,
download API specification files etc. These API specification files created from the
API designer can be published as APIs on theSAP Business Accelerator Hub.

Transport APIs and Its Related Arti- API artifacts and their respective application-specific content, can be reused across
facts multiple tenants using the transport mechanism.

You can use the SAP Cloud Transport Management service (TMS) for exporting,
importing, and shipping the APIs and its related artifacts from the development or
test environment to production environment. For example, you can design and test
API portal content on the test tenant and then use the Cloud Transport Management
service to move the content to the target tenant.

Consuming API Management Serv- Kyma environment provides a fully managed Kubernetes runtime based on the open-
ice Instance from Kyma source project "Kyma". You can use the Kyma environment to search and discover
API Management, API Portal and API business hub enterprise applications.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 29
Feature Description

Migration of API Management Sub- You can choose to migrate an API Management subscription from Neo to Cloud
scription Foundry environment or from one Cloud Foundry environment to another Cloud
Foundry environment.

Migration Assistant for asset migration includes the tools and utilities that enable
migration of design time assets nondisruptively.

API business hub enterprise [New If you have added API business hub enterprise as a capability with Integration suite,
Design] or if you’ve subscribed to API business hub enterprise as part of standalone API
Management subscription, we now have a new design of the user interface for you to
experience.

Secure options to consume APIs There are secure options to consume APIs using the API Access Plan for API portal,
API business hub enterprise and on-premise connectivity. You can create service
keys with credential types "binding- secret", "instance- secret" and "x509".

Graph Graph is a capability of API Management within SAP Integration Suite. With Graph,
developers access your business data as a single semantically connected data graph,
spanning the suite of SAP products and beyond. Targeting SAP's ecosystem of part-
ner and customer developers, Graph's powerful API reduces the cost and complexity
of creating and deploying reusable extensions and other client applications.

Graph is a solution to unify your business APIs in the form of a semantically con-
nected data graph, accessed via a single powerful API. Out of the box, it provides
developers a single connected and unified view of your SAP-managed business
data. Graph consolidates thousands of data entities from SAP systems like SAP
S/4HANA, SAP Sales Cloud, and SAP SuccessFactors, into one curated, semantically
connected, data model. We call this connected graph a Business Data Graph.

API Revisions API revisions is a feature of API Management within SAP Integration Suite and
API Management standalone service. With API revisions, you can make incremental
changes to an API proxy without causing any disruption to the deployed API. Access
the past changes made to the API proxy, and even restore the API to any of its
previous states.

Revisions typically include small incremental and compatible changes. For example,
adding a property or adding a new resource or a policy to an API proxy. You create
revisions when there are changes that don't break the existing consumption flows.
API revisions are agnostic of the actual URL that is used for consuming the API. Since
the deployed revision is being consumed, you don't have to access it separately.
The API proxy URL doesn't change across revisions of an API proxy. It is a design
time entity, you can view the different revisions in the design time, and compare the
contents of different revisions.

Graph

Graph is a capability of API Management .

Feature Scope Description for SAP Integration Suite

30 PUBLIC Features
 Feature Description

Access business data as a single semantically connected Access your business data as a single semantically con-
data graph nected data graph, spanning the suite of SAP products and
beyond. Targeting SAP's ecosystem of partner and customer
developers, Graph's API reduces the cost and complexity of
creating and deploying reusable extensions and other client
applications.

Unify business APIs in the form of a semantically connected Unify your business APIs in the form of a semantically con-
data graph nected data graph, accessed via a single powerful API. Out of
the box, Graph provides you with a single connected and uni-
fied view of your SAP-managed business data. Graph con-
solidates from SAP systems like SAP S/4HANA, SAP Sales
Cloud, and SAP SuccessFactors, into one curated, semanti-
cally connected, data model (referred to as a Business Data
Graph).

3.3 Graph

Graph is a capability of API Management within SAP Integration Suite.

Feature Description

Access business data as a single semantically connected Access your business data as a single semantically con-
data graph nected data graph, spanning the suite of SAP products and
beyond. Targeting SAP's ecosystem of partner and customer
developers, Graph's API reduces the cost and complexity of
creating and deploying reusable extensions and other client
applications.

Unify business APIs in the form of a semantically connected Unify your business APIs in the form of a semantically con-
data graph nected data graph, accessed via a single powerful API. Out of
the box, Graph provides you with a single connected and uni-
fied view of your SAP-managed business data. Graph consol-
idates data entities from SAP systems like SAP S/4HANA,
SAP Sales Cloud, and SAP SuccessFactors, into one curated,
semantically connected, data model (referred to as a Busi-
ness Data Graph).

Feature Scope Description for SAP Integration Suite

Features PUBLIC 31
3.4 Open Connectors

Open Connectors simplifies and allows you to build seamless integrations with over 150 non-SAP applications
using pre-built connectors.

Feature Description

Accelerate the application connec- Use pre-built connectors to simplify, standardize, and accelerate the connectivity with
tivity. third-party cloud applications. These pre-built connectors are kept up-to-date with
changes in their underlying APIs.

Use common resources. Map data in common resources to transform fields provided by one or more third-
party applications into a normalized resource at SAP.

Create formula templates and in- Use formula templates and instances to build workflows that are independent of
stances. specific third-party cloud applications. Use different step types and triggers, such as
events or schedules.

Upload and download data in bulk. Upload and download data in bulk in a normalized way, regardless of the underlying
service architecture.

For a detailed list of available connectors, refer to the product documentation.

3.5 Integration Advisor

Integration Advisor allows you to specify integration content for B2B scenarios.

Integration Advisor is an intelligent integration content management system that helps you accelerate the
development of business-oriented interfaces and mappings. It uses a machine learning-based proposal
approach that helps you to accelerate your efforts. You can then generate runtime artifacts quickly,
significantly reducing the efforts. The application also supports community collaboration for creating and
maintaining tailored content.

SAP Integration Advisor

Feature Description

Simplify the design of message implementation guidelines Facilitates the design of message implementation guidelines
(interfaces) based on industry standards and the definition
of mapping guidelines to specify mappings between these
interfaces.

Feature Scope Description for SAP Integration Suite

32 PUBLIC Features
 Feature Description

Support of type systems Includes a library of type systems, that is: a collection of
message templates that are provided by agencies that main-
tain the B2B standards.

Available type systems:

• External B2B Standards: ASC X12, UN/EDIFACT

• SAP S/4HANA: SOA, IDoc, OData
• SAP Ariba: cXML

Integration with SAP Cloud Integration integration design Based on the designed message implementation guidelines
environment and mapping guidelines, automatically generates the re-
quired runtime artifacts (for validation, conversion, transfor-
mation, pre- and post-processing) that can be used in inte-
gration flows.

3.6 Trading Partner Management

Trading Partner Management supports the definition and configuration of business-to-business (B2B)
scenarios. It helps you manage B2B relationships with multiple trading partners.

Trading Partner Management tightly interoperates with the following capabilities:

• Cloud Integration
• Integration Advisor

Trading Partner Management provides the following features:

Feature Description

Maintain trading partner profiles. Specify trading partner information relevant in the context of
B2B scenarios.

Create agreements between partners. Specify information that defines how 2 trading partners can
exchange business data with each other in the context of a
B2B scenario.

Push B2B scenario configuration to Cloud Integration. On activation, trading partner agreements are stored in the
Cloud Integration Partner Directory. Cloud Integration can
consume this information at runtime and use it to parame-
terize integration flows.

Monitor B2B interchanges. Monitor the status of B2B interchanges.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 33
3.7 Integration Assessment

Integration Assessment supports the definition of the integration landscape, based on the SAP Integration
Solution Advisory Methodology (ISA-M).

It helps you to define integration patterns and to ensure a consistent usage of the integration technology.

Integration Assessment provides the following features:

Feature Description

Maintain ISA-M master data. Use predefined ISA-M master data and customizing options.

Create business solution requests. A business solution request represents the leading object for
an integration requirement from a business perspective.

Create integration requests. An interface request represents the leading object for an
integration requirement from a technical perspective.

Select appropriate technology. Automatically selects suitable technology, based on ISA-M

master data, integration policies, and questionnaires.

3.8 Migration Assessment

Migration Assessment helps you estimate the technical effort involved in migrating configuration objects from
a SAP Process Orchestration system 7.5 to SAP Integration Suite.

Migration Assessment helps you to evaluate if your integration scenarios can be migrated.

It provides the following features:

Feature Description

Extract data. Extract data from your existing SAP Process Orchestration
7.5 system.

Estimate migration effort. Evaluate the extracted data

Estimate the potential effort of migrating your integrated

configuration objects from your SAP Process Orchestration
7.5 system to SAP Integration Suite.

Feature Scope Description for SAP Integration Suite

34 PUBLIC Features
3.9 Edge Integration Cell

Edge Integration Cell is an optional hybrid integration runtime that enables you to manage APIs and run
integration scenarios within your private landscape.

Feature Scope Description for SAP Integration Suite

Features PUBLIC 35
4 Compliance and Security

SAP Integration Suite ensures cloud security at multiple levels.

Security Features

Feature Description

Tenant isolation Strictly separates data from different customers that is processed and stored in the
system.

Although different customers share resources of the same physical infrastructure,

these resources are strictly separated for each customer into separate tenants.

Data flow security (transport level) Supports secure communication protocols for communication with remote systems
using Cloud Integration.

Supported protocols:

• Hyper Text Transfer Protocol (HTTP) over Transport Layer Security (TLS), which
is referred to as HTTPS
• SSH File Transfer Protocol (SFTP)
• Simple Mail Transfer Protocol (SMTP), Post Office Protocol (POP)3, and Internet
Message Access Protocol (IMAP)

For more details, check out the product documentation.

Data flow security (message level) Makes sure that messages exchanged with remote components through Cloud
Integration can be protected by digital encryption and digital signatures.

For the supported standards and algorithms, check out the product documentation.

Data storage security Makes sure that customer data stored in the Cloud Integration system during a mes-
sage processing sequence (when using Cloud Integration) is protected.

Message content can be stored encrypted (using AES and a key length of 256 bits). If
this security measure is configured, the encryption key that is generated automatically
is unique for each tenant and is renewed periodically. Furthermore, it is not stored in
the same database as the encrypted data.

During message processing using Cloud Integration, the involved Cloud Integration
runtime component writes monitoring data to the database. Only administrators with
dedicated permissions can access this data.

Data such as message processing logs or audit logs is stored for a defined period
(retention time) in the system. See the product documentation to find out the different
retention times for the different types of data stored in the system.

Feature Scope Description for SAP Integration Suite

36 PUBLIC Compliance and Security
 Feature Description

Physical data storage Customer data is stored in various regions worldwide. Here, the highest security
standards are met. For example, redundant power supplies are used and physical
access is restricted by means such as biometric access control mechanisms. All of
these measures are regularly checked and audited.

User management and authoriza- Makes sure that access to dedicated functions of Cloud Integration is controlled and
tion protected by authorization checks. To manage the authorizations of dialog users,
an authorization concept is in place that allows administrators to assign dedicated
permissions (roles) to users.

Predefined role collections (which contain a set of dedicated roles) are designed to fit
the persona and tasks that come into play during the lifecycle of an integration project.

Access management Makes sure that inbound requests in scenarios using Cloud Integration are authenti-
cated by a load balancer (if client certificate authentication is configured). In this case,
the load balancer checks the client certificate of the calling component against a list of
trusted certification authorities.

This certificate is mapped to a service key.

Dialog users accessing the platform are authenticated against an identity provider. By
default, SAP Identity Service (ID Service) is used. SAP ID Service is the central service
for the process of managing identities and their lifecycles.

Malware scanning Scans documents that are uploaded to the Cloud Integration tenant, such as integra-
tion flows and its resources, to avoid malware attacks. For the supported document
types, refer to the product documentation.

Certificates and Reports

Cloud Integration regularly undergoes audits and reviews of its policies and controls.

 Note

Note that these assets were created before our branding changes related to SAP technology were
announced on January 2021.

• For the complete list of compliance and security standards that the <service-short-name> is compliant
with, see SAP Cloud Platform ISO Certificates .
• For the complete list of Service Organizational Control (SOC) audit reports available for the <service-short-
name> is, see SAP Cloud Platform SOC Reports .

Feature Scope Description for SAP Integration Suite

Compliance and Security PUBLIC 37
Data Protection

Cloud Integration follows SAP's global data protection and privacy guidelines. For more information on the
guidelines, see Data Privacy .

To access the Personal Data Processing policy for your region, see Personal Data Processing for SAP Cloud
Services .

Feature Scope Description for SAP Integration Suite

38 PUBLIC Compliance and Security
5 Service Availability

Availability Aspect Description

Regions See SAP Discovery Center .

Infrastructures SAP Integration Suite runs on several underlying Infrastructure-as-a-Service technologies and
regions owned by our partner infrastructure providers, including Amazon Web Services, Microsoft
Azure, and Alibaba Cloud.

Environments SAP Integration Suite runs in the SAP BTP, Cloud Foundry environment.

Languages The web-based administration user interface of SAP Integration Suite is available in English.

The SAP Integration Suite documentation on SAP Help Portal is available in English.

Accessibility SAP Integration Suite provides accessibility support in its tools and the customer documentation.
This includes:

• High-contrast black theme for the UI

• Texts and information
• UI elements via attributes and element IDs
• Orientation and navigation throughout the UI
• User interaction

Free trial use SAP Integration Suite is included in the free trial for the platform.

Restrictions

• If your contract allows EU-Access, you are not allowed to use the Cloud Foundry environment. Operations
support for applications running in EU regions can also only be performed by operators located in the EU.
• Service-specific restrictions are described in the respective capability section in this document or in the
linked feature scope descriptions for the separately licensed services.

 Note

Further restrictions may apply when using the product on an infrastructure hosted by a third-party
provider.

Feature Scope Description for SAP Integration Suite

Service Availability PUBLIC 39
6 Browser Support

Overview of the browser support

For the UIs of the service, the following browsers are supported on Microsoft Windows PCs and, where
mentioned below, on macOS. Note that, however, certain limitations might apply for specific browsers:

Cloud Integration has been tested using the following browsers:

• Google Chrome (latest version)

• Microsoft Edge (latest version)
• Mozilla Firefox (latest version)
• Windows Internet Explorer (as of version 10)

 Note

The application can also be used with Safari browser and Internet Explorer 9. However, some features
might not work as expected.

Feature Scope Description for SAP Integration Suite

40 PUBLIC Browser Support
7 Service Level Agreement

The Service Level Agreement (SLA) is a contract between SAP and its customers that forms the basis of your
contractual relationship with SAP when referenced in specific order forms.

 Note

This Service Level Agreement covers cloud service offerings that are operated by SAP. For more
information about the service level agreement for cloud service offerings operated by an SAP partner,
contact your operator.

• The order form is the ordering document to subscribe to cloud services from SAP. It defines the
commercial terms and lays out the agreement structure. The order form also incorporates several other
documents that relate to the SLA.
• The Service Level Agreement for SAP Cloud Services applies to any cloud service on the SAP price list,
defining downtime, credits, update windows, and others.
For more information, see Service Level Agreement for SAP Cloud Services .
• The SAP Business Technology Platform Supplement overrides the Service Level Agreement for SAP
Cloud Services in case of deviations and specifies the SLA for SAP Business Technology Platform in
general.
For more information, see SAP Business Technology Platform Supplement .

Additionally, the General Terms and Conditions for SAP Cloud Services warrants the SLA and provides the
available remedy if SAP fails to meet its SLA.

For more information, see SAP Trust Center Agreements Cloud Services Agreements .

Maintenance Windows and Major Upgrade Windows

The maintenance and major upgrade windows are defined in the Service Level Agreement for Cloud Services.
SAP may update these windows from time to time in accordance with the Agreement.

The following windows apply for the <service-short-name> service:

Maintenance Windows Major Upgrade Windows

MENA APJ Europe Americas Frequency MENA APJ Europe Americas

Zero down- Zero down- Zero down- Zero down- Up to 4 FRI SAT SAT SUN
time time time time times per
5 pm 1 pm 8 pm 6 am
year
(4hrs) (4 hrs) (4 hrs) (4 hrs)

For the latest information, see Maintenance Windows and Major Upgrade Windows for SAP Cloud Services
and search for your service.

Feature Scope Description for SAP Integration Suite

Service Level Agreement PUBLIC 41
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using
such links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Feature Scope Description for SAP Integration Suite

42 PUBLIC Important Disclaimers and Legal Information
Feature Scope Description for SAP Integration Suite
Important Disclaimers and Legal Information PUBLIC 43
www.sap.com/contactsap

© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN