Integration Architecture Guide For Cloud and Hybrid Landscapes PDF

Integration Architecture Guide for Cloud and
Hybrid Landscapes
Based on SAP® Integration Solution Advisory
Methodology
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
1 / 82
Table of Contents
3 Intelligent Enterprises Are

Integrated Enterprises
4 Introduction
11 SAP’s Strategy for Aligned
Domain Models and APIs
17 SAP Integration Solution

Advisory Methodology
22 Process Integration
53 Data Integration
64 Analytics Integration
70 UX Integration – Deployment
Options
75 End-to-End Integration
Monitoring
78 Automated Integration
Configuration
80 Integration of SAP S/4HANA

81 Outlook and Finding Out More
82 List of Abbreviations
2 / 82

Intelligent Enterprises Are Integrated Enterprises
SUMMARY This guide provides technology guidance along
Integration has become the key enabler the three pillars of SAP’s overall integration
and competitive differentiator for intelligent strategy: integration principles, integration suite,
enterprises. In the paper “Intelligent Enterprises and integration methodology.
Are Integrated Enterprises,” SAP has outlined
its strategy and road map toward an integrated As a foundation, SAP’s strategy for APIs and
intelligent suite along end-to-end business aligned domain models is described, including
processes with a focus on SAP-to-SAP line- SAP API Business Hub and SAP Graph. This is
of-business (LoB) integration scenarios. followed by detailed guidance for the major
integration flavors:
Based on SAP® Business Technology Platform, • Process integration leveraging the various
this document1 explains the strategy and services of SAP Cloud Platform Integration
provides enterprise and integration architects Suite and SAP Process Orchestration
with detailed guidance on how to evolve their • Data integration with SAP Data Intelligence
existing integration architecture based on the and related solutions for enterprise information
SAP technology offerings available today. It and data management from SAP
focuses specifically on integration services used • Analytics integration, including the
to cover all integration needs in heterogeneous SAP Analytics Cloud, SAP Data Warehouse Cloud,
landscapes. In addition, we provide the paper and SAP BW/4HANA® solutions
“CIO Guide: SAP’s Hybrid Integration Platform • UX integration with a focus on the OData
for the Intelligent Enterprise,” a management provisioning options for SAP Fiori® user
abstract to accompany this detailed integration experience (UX)
architecture guide.
Additional topics include:
Thus, there are three corresponding publications: • End-to-end integration monitoring, which
• “Intelligent Enterprises Are Integrated provides an overview of integration monitoring
Enterprises” focuses on end-to-end business options for cloud and hybrid landscapes
processes in the intelligent enterprise that • Automated setup of integration scenarios
span SAP’s intelligent suite and partner and • Guidance for the transition from
third-party solutions. SAP Business Suite to SAP S/4HANA® and
• “CIO Guide: SAP’s Hybrid Integration SAP S/4HANA Cloud from an integration
Platform for the Intelligent Enterprise” perspective
is a short executive overview of SAP’s hybrid
integration platform. It summarizes the detailed Since the previous version of this document was
guide that you are currently reading. issued, all sections have been updated and the
• “Integration Architecture Guide for Cloud and following topics have been added: SAP One
Hybrid Landscapes” is the detailed guide to Domain Model, SAP Graph, SAP Cloud Platform
integration technologies from SAP, which you Master Data Integration service, SAP Cloud
are now reading. Platform Extension Suite, and analytics integra-
tion, including SAP Analytics Cloud, SAP Data
Warehouse Cloud, and SAP BW/4HANA.
1. F
ormerly, this detailed integration architecture guide was issued with the title “CIO Guide.” We have changed its title to reflect
its target group. “Integration Architecture Guide for Cloud and Hybrid Landscapes” will be accessed under a new URL. It will no
longer have “CIO” in the title. The name “CIO Guide” now refers to the management abstract and can be accessed through the
URL used for the previous version of the detailed guide.
3 / 82

Introduction
Integration has become the key enabler for SAP’s integration strategy is based on three
intelligent enterprises. The holistic integration pillars described in the following sections:
of business processes, data, business partners, • Integration principles: Out-of-the-box
people, and physical assets such as sensors integration, open integration, holistic
or machines builds the foundation for next- integration, and AI-driven integration
generation intelligent enterprises. In the paper • Integration suite: SAP Cloud Platform
“Intelligent Enterprises Are Integrated Integration Suite as a versatile and enterprise-
Enterprises,” SAP has outlined its strategy grade hybrid integration platform
toward an integrated intelligent suite along • Integration methodology: SAP Integration
end-to-end business processes with a focus on Solution Advisory Methodology to guide
SAP-to-SAP integration and its related road maps. customers with integration patterns, allowing
them to determine their enterprise integration
Integration is becoming more and more strategic strategy
for enterprises coping with increasingly hetero-
geneous and hybrid IT landscapes. Based on INTEGRATION PRINCIPLES
SAP Business Technology Platform, this As shown in Figure 1, SAP’s comprehensive
document complements that strategy by providing integration strategy facilitates integration of end-
enterprise and integration architects with guidance to-end business processes spanning integrated
on how to evolve their existing integration archi- intelligent suite solutions as well as partner
tectures with the SAP technology offerings and third-party solutions. The four end-to-end
available today. It has a strong focus on integration business processes – lead to cash, design to
services used to cover all integration needs in operate, source to pay, and recruit to retire –
heterogeneous landscapes, including partner were explicitly chosen because they represent a
and third-party solutions. The hybrid integration large portion of the activities that our customers
platform is the central nervous system of an deal with. They also cover a number of interactions
intelligent enterprise and allows digital ecosys- between SAP solutions.
tems to be built on top.
Integration has become the key enabler for

intelligent enterprises. The holistic integration
of business processes, data, business partners,
people, and physical assets builds the foundation
for next-generation intelligent enterprises.
4 / 82

Figure 1: Key Integration Principles for the Intelligent Enterprise
BUSINESS NETWORK
Customer Manufacturing Finance and Human

and Supply Chain Procurement Resources
Out-of-the-box
Lead to Cash 1 integration
Design to Operate
BUSINESS
PROCESSES Source to Pay
Recruit to Retire
And multiple sub processes
2 Open integration
APPLICATIONS INTELLIGENT SUITE PARTNER SOLUTIONS THIRD-PARTY SOLUTIONS
SUITE QUALITIES OPENNESS

3 Holistic integration
SEAMLESS CONSISTENT ALIGNED EMBEDDED AND ONE COORDINATED E2E

User Experience Security and Domain CROSS-PRODUCT Workflow Lifecycle Process
Identity Models Analytics Inbox Management Blueprints
Management
AI-driven
4
SAP One Domain Model
SAP BUSINESS TECHNOLOGY PLATFORM integration

TECHNOLOGY
SAP CLOUD PLATFORM INTEGRATION SUITE
The integration strategy is based on four key Open Connectors capability of SAP Cloud
principles: Platform Integration Suite, SAP provides
• Out-of-the-box integration: Within the document feature-rich, prebuilt connectors for more than
“Intelligent Enterprises Are Integrated 160 third-party applications.
Enterprises,” SAP outlines its strategy and road • Holistic integration: SAP provides a holistic
map for the integration of end-to-end processes integration technology portfolio that covers all
of its intelligent suite (SAP-to-SAP) based on flavors of integration. Based on SAP Cloud
well-defined suite qualities. As an example, the Platform Integration Suite, SAP supports all
alignment of domain models ensures that types of integration use cases, ranging from
master data can be exchanged in an efficient process, data, user, and IoT to analytics-centric
and convenient way between SAP applications. integration.
SAP provides open APIs and events across LoB • AI-driven integration: In addition to bringing
applications and platforms in SAP API Business intelligence to core business processes, SAP is
Hub. Besides aligned APIs, prebuilt integration using AI techniques to simplify the development
content (so-called integration packs) builds an of integration scenarios. One example is the
important foundation for integrating applications Integration Advisor capability of SAP Cloud
of the intelligent enterprise. Platform Integration Suite. Its crowd-based
• Open integration: Besides SAP-to-SAP and machine learning approach enables users to
SAP-to-partner integrations, SAP is open for define, maintain, share, and deploy integration
any third-party integration as well as custom content much faster than building it from
extensions leveraging public APIs. With the scratch.
5 / 82

INTEGRATION SUITE
SAP Cloud Platform Integration Suite is SAP’s recommended toolkit for simplifying and accelerating
integration for SAP, partner, and third-party integration scenarios (see Figure 2).
Figure 2: SAP Cloud Platform Integration Suite – SAP’s Hybrid Integration Platform
SAP Partner
SAP CLOUD PLATFORM INTEGRATION SUITE
SAP S/4HANA®
SAP API BUSINESS HUB
SAP S/4HANA Cloud 1,500+ prepackaged integration flows | API first | Workflow Third parties
Open connectors to 160+ third-party cloud apps | Governance
SAP® Customer
Experience
CLOUD API MANAGEMENT SAP GRAPH INTEGRATION ADVISOR
SAP Ariba® solutions INTEGRATION Exposed data as APIs and Harmonized APIs AI-based integration and
End-to-end process end-to-end lifecycle management for SAP metadata management
SAP SuccessFactors® integration
solutions
DATA INTELLIGENCE ENTERPRISE MESSAGING OPEN CONNECTORS SERVERLESS RUNTIME
SAP Fieldglass® Data integration, Sensing and response to Accelerated connectivity Functions to
solutions orchestration, and AI business events to third-party applications respond to events
SAP Concur®
SAP ONE DOMAIN MODEL AND METADATA | MASTER DATA INTEGRATION
solutions
More Fully managed

Microsoft Azure AWS Alibaba Cloud SAP
multi-cloud
SAP Process Orchestration Cloud Connector Data integration tools (EIM)
INTEGRATION SUITE on-premise process and data integration platforms,

The integration suite offers holistic integration2 such as SAP Process Orchestration, and the
– application-to-application (A2A), master data, solutions for enterprise information and data
business-to-business (B2B), electronic data management from SAP that our customers rely
interchange (EDI), business-to-government (B2G), on. The integration suite is a toolkit that consists
and e-government integrations. It supports data of multiple services to support holistic
integration and data pipelining and event-driven integration scenarios. Table 1 summarizes the
and API-based integrations. SAP Cloud Platform services and high-level use cases, which will be
Integration Suite acts as the foundation for process described in more detail later in this document.
excellence across the value chain. It complements
2. SAP Cloud Platform Integration Suite comprises the following core capabilities by default: 1. Cloud Integration 2. API Management
3. Integration Advisor 4. Open Connectors. Other integration services can be added and are provisioned on SAP Cloud Platform.
6 / 82

Table 1: SAP Cloud Platform Integration Suite – Services and Use Cases
Services Use cases
Cloud Integration End-to-end process integrations (A2A), AI-accelerated business-to-business

(B2B) and electronic data interchange (EDI) integrations, and business-to-
government integrations with over 1,400 prebuilt integrations delivered as
integration packs
Master data Out-of-the-box master data integrations across SAP® applications in the
integration intelligent suite
SAP Data Intelligence Data integration, data pipelining scenarios, and extract, transform, load (ETL)
scenarios for data lakes and data warehouses that apply machine learning
algorithms for data clustering, regression, and insights
API Management Full lifecycle management of enterprise APIs (design – develop – manage and
developer engagement) with support for customers launching their own API
domains and running enterprise API programs
SAP API Business Hub SAP’s directory of process blueprints, domain models, over 1,200 APIs, events,
and integration packs
Integration Advisor AI-based mapping proposals to accelerate onboarding of trading partners

through accelerated mappings, with support for EDI metadata management
and out-of-the-box B2B library support
Open Connectors Over 160 open connectors to simplify third-party connectivity through
one-to-many integrations with various integration hubs such as CRM, ERP,
cloud storage, and social media
SAP Cloud Platform Event-based integrations with out-of-the-box events from SAP applications
Enterprise Messaging such as SAP S/4HANA® and SAP Customer Experience and SAP
SuccessFactors® solutions
SAP Cloud Platform A service for building, running, and managing serverless applications that
Serverless Runtime extend your digital core with vendor-managed infrastructure and can scale
automatically
SAP Graph (“beta”) A unified API to access SAP-managed data that can be used to build new
extensions and applications using SAP data
7 / 82

Notes on Terms Used in This Document known as individual services. To avoid any
The core capabilities of SAP Cloud Platform confusion, the following list shows the current
Integration Suite are discussed throughout this name of each core capability and the service
document. Those capabilities were previously name it was known under before.
Core Capabilities of SAP® Cloud Former Name

Platform Integration Suite
Cloud Integration capability SAP Cloud Platform Integration service
API Management capability SAP Cloud Platform API Management service
Integration Advisor capability SAP Cloud Platform Integration Advisor service
Open Connectors capability SAP Cloud Platform Open Connectors service
INTEGRATION METHODOLOGY integration challenges and provides guidance

SAP Integration Solution Advisory Methodology on choosing the right integration approach
helps enterprise architects to shape the and services. This document is based on this
enterprise integration strategy for their approach and provides recommendations for
organizations. The methodology also offers process-, data-, analytics-, and user-centric
architecture blueprints to address enterprise integration patterns.
SAP Integration Solution Advisory

Methodology helps enterprise architects
to shape the enterprise integration
strategy for their organizations.
8 / 82

ABOUT THIS DOCUMENT
Figure 3 shows the key building blocks for integration as covered in this guide.
Figure 3: Content Overview – Key Integration Building Blocks
Out-of-the-box Open Holistic AI-driven

integration integration integration integration
SAP® Integration Solution Advisory Methodology
Foundation
Aligned domain models APIs and integration packages End-to-end process blueprints
Integration styles and technologies
Analytics
Process integration Data integration User integration
integration
API-managed integration | Event-based integration
Setup and operations
Integration monitoring Integration automation
Integration deployment models
Multi-cloud Private cloud On premise Embedded
This document is made up of the following • “SAP Integration Solution Advisory

sections: Methodology” outlines how the methodology
• “SAP’s Strategy for Aligned Domain Models supports enterprise architects on their digital
and APIs” provides a foundational overview of transformation journey with a proven approach
SAP’s strategy for aligned domain models. It for tackling the growing integration challenge.
also outlines the key role of APIs and gives an
overview of SAP API Business Hub, including
end-to-end process blueprints content and
SAP Graph software.
9 / 82

• “Process Integration” provides guidance for • “Analytics Integration” provides details
the “process integration” style and related use on how SAP Data Warehouse Cloud,
cases. It describes how the integration suite SAP Analytics Cloud, and SAP BW/4HANA
supports various use cases, such as A2A, B2B, are integrated. It explains how both provide
B2G, and master data integration. It provides connectivity to SAP and third-party systems
guidance on how SAP Cloud Platform – cloud and on premise – to access data with or
Integration Suite, SAP Process Orchestration, without replication. In addition, it details how
and the SAP Application Interface Framework the embedded edition of SAP Analytics Cloud
tool can be used to implement various process allows other applications – SAP and third-party
integration scenarios. It outlines the use of the – to integrate analytics capabilities in their
SAP Cloud Platform Master Data Integration operational systems.
service to exchange and synchronize master • “UX Integration – Deployment Options”
data across SAP applications based on aligned provides guidance on OData provisioning
domain models. The section discusses the options for the SAP Fiori® UX, with focus on
additional integration capabilities of the user-centric integration.
integration suite: API Management, Open • “End-to-End Integration Monitoring” provides
Connectors, and Integration Advisor capabilities. an overview of monitoring options for hybrid
It also discusses the SAP Cloud Platform landscapes, including the use of SAP Solution
Enterprise Messaging service and the cloud Manager and the SAP Focused Run and
connector that comes with the SAP Cloud SAP Cloud ALM solutions.
Platform Connectivity service. Finally, it outlines • “Automated Integration Configuration”
the use cases for SAP Cloud Platform Extension provides insights into how the Cloud Integration
Suite and its relationship to the integration suite. Automation service helps simplify and
• “Data Integration” provides guidance for automate the configuration of integration
the “data integration” style and related use scenarios of intelligent enterprise scenarios
cases. It introduces SAP Data Intelligence, a within a customer landscape.
comprehensive data management solution • “Integration of SAP S/4HANA” gives insight
for governance, integration, processing, and into what the transition from SAP Business
orchestration of data in on-premise, cloud, and Suite to SAP S/4HANA and SAP S/4HANA
hybrid landscapes. In addition, this section Cloud means from an integration perspective.
provides guidance for using solutions for
enterprise information and data management
from SAP.
10 / 82

SAP’s Strategy for Aligned Domain Models
and APIs
A combination of more than one and often several synchronize master data, to integrate and extend
SAP applications supports comprehensive, end- building blocks, and to consume data through
to-end processes in the intelligent suite. APIs that APIs. Various lines of business at SAP have been
are provided by these applications and which can aligning the data models of master data objects,
be used for integration, consumption, and extension including value types and code lists, thereby
are documented in SAP API Business Hub. simplifying data sharing across SAP applications.
We call this domain model alignment. Its result
Enterprise applications often come with their is the newly created and further developing
own individual and disjunct master data SAP One Domain Model, which simplifies
schemes. This heterogeneity – which also results several integration, consumption, and extension
from bringing together applications that have scenarios. The relation between these aspects,
been developed individually or acquired over shown in Figure 4 is explained in more detail
time – makes it difficult to exchange and below.
Figure 4: SAP One Domain Model and Its Role for Master Data Handling and Consumption
Customer Partner
Third-party integration Apps, extensions Master data management
SAP Cloud Platform

SAP® Cloud Platform SAP Master Data
Extension Suite, SAP Graph,
Integration Suite Governance
SAP API Management
SAP’s integrated intelligent suite SAP One

Domain Model
SAP SuccessFactors® SAP Ariba® SAP Concur® SAP Fieldglass® ...
SAP S/4HANA®
solutions solutions solutions solutions
SAP Cloud Platform Master Data Integration
11 / 82

SAP One Domain Model is essential for data enables you to use and extend business
exchange and synchronization between various functionality, for example, an integrated business
SAP applications of the intelligent suite. It is used process or an extension of SAP software by
by the newly developed SAP Cloud Platform means of an API. Navigation and drill-down
Master Data Integration service. This service is functionality lets you explore any package to
described in more detail in “Process Integration.” discover digital content and related documentation.
The service supports not only cloud applications
but SAP S/4HANA systems that run on premise Partners can list content and engage with
as well. Developers working with customers and customers over SAP API Business Hub when
partners can use the service through SAP Cloud they participate in the “partner engagement for
Platform Integration Suite. The definitions of digital content” program. The blog “Welcoming
objects in SAP One Domain Model are becoming Partners to the SAP API Business Hub” provides
available externally as well. These definitions you with more information about that offer and
form the basis for consumption and extension its benefits.
mechanisms enabled by SAP Cloud Platform
Extension Suite, SAP Graph, and SAP API As part of an intelligent enterprise, descriptions
Management. SAP One Domain Model is also used of an intelligent enterprise’s end-to-end processes
with the SAP Master Data Governance application along with their components, interactions, and
to support master data management by customers APIs are made available. This includes value flow,
and partners. data flow, and software product collaboration
diagrams based on SAP Enterprise Architecture
SAP API BUSINESS HUB Methodology3 (available in a new “Business
SAP API Business Hub is the place to get started Processes” section of SAP API Business Hub),
with building applications, integrations, and as shown in Figure 5. The blueprints relate to the
extensions. It supports the discovery and suite quality of end-to-end process blueprints
consumption of digital content such as APIs, as described in “Intelligent Enterprises Are
prepackaged integration content, business Integrated Enterprises.” Enterprise architects
events, end-to-end business process blueprints, can inspect which components and interactions
and sample applications. You will find content belong to specific processes, the APIs and inter-
from both SAP and our partners. All digital actions that exist, and how they can be extended.
content is organized into packages, which
3. To find out more about process blueprints, see the blog “Process Blueprints and the SAP Enterprise Architecture
Methodology.”
12 / 82

Figure 5: Sample Software Product Collaboration Diagram for Hire-to-Retire Process
SAP ONE DOMAIN MODEL are highly desirable. “Intelligent Enterprises Are
The need to exchange and synchronize master Integrated Enterprises” names aligned domain
data (which may or may not be aligned) between models as an important suite quality. Instead of
individual applications has been coped with trying to come up with a global canonical data
historically by implementing point-to-point model for the whole enterprise, the domain-driven
integrations. However, the number and variance approach taken by SAP restricts alignment efforts
of the resulting individual interactions are to those parts that must be aligned, that is, where
difficult to handle, error prone, may lose a producer and consumer agree on an exchange
information when mappings are performed, format. It does not let current application and
and come with significant cost. Thus, the system boundaries define model boundaries.
identification and definition of aligned models Instead, domains define the top level of the
and the implementation of a more efficient models and should remain stable for future
exchange and synchronization mechanism with product release versions. (See the blog “SAP One
a “hub and spoke” model based on these models Domain Model and Domain-Driven Design.”)
13 / 82

Figure 6 illustrates the approach. Various example, odm.sales or odm.product. Attributes
solutions, such as SAP S/4HANA, SAP Commerce shown in Figure 6 in blue areas are relevant for
Cloud, and SAP Sales Cloud, share an overlap of interactions between at least two interacting
attributes that typically have individual attribute applications. If objects are relevant for several
names or field lengths that differ between the domains, “aspects” are used. For example,
solutions. However, there is a semantic overlap ProductSalesAspect comprises sales-related
among them. information needed by commerce applications.
Aspects can evolve independently from the core
Figure 6: Identification of a Common Set of part and must be aligned only between a smaller
Attributes Shared by Various Applications group of involved and affected stakeholders.
SAP S/4HANA® You can inspect the currently available models

following SAP One Domain Model in SAP API
Business Hub.
The CDS format is also used in SAP HANA®,

SAP S/4HANA Cloud, the ABAP® RESTful appli-
SAP Sales Cloud
cation programming model, and SAP Cloud
Application Programming Model (sometimes
SAP® Commerce Cloud referred to as “CAP”). Developers are familiar
with the format, and respective tooling can
efficiently be used and reused.
The fully overlapping part of the object model
covers objects that all the solutions pictured deal Attributes with their types and specifics as well
with, for example, “Customer” or “Product,” and as relations can be visualized and navigated
about which each of them has some data. These graphically (see Figure 7). To use SAP One
objects are modeled in the core data services Domain Model in your application, you can use
(CDS) format in a dedicated namespace, for the compiler and runtime for core data services
(https://cap.cloud.sap/docs).
Various solutions, such as SAP S/4HANA,

SAP Commerce Cloud, and SAP Sales Cloud,
share an overlap of attributes that typically
have individual attribute names or field lengths
that differ between the applications.
14 / 82

Figure 7: Visualization of Objects, Attributes, and Relations
The identification of suitable common attributes Platform Master Data Integration service support
is a continuous process. “Intelligent Enterprises model versioning. They also support the definition
Are Integrated Enterprises” names the first of nonmandatory and customer-specific fields,
six objects – Cost Center, Workforce Person, which can be exchanged over the master data
Product, Supplier, Customer, and Asset – and integration service.
provides a clear road map for when they will
be used in the respective end-to-end business SAP One Domain Model is focused on harmonizing
processes. SAP One Domain Model has been the business semantics of objects and their
released through SAP API Business Hub. There respective APIs. The approach to the technical
you will find a visual representation of all foundation for harmonized REST APIs is described
business entities and their relationships to each in the paper “Best Practices for Enterprise
other. Both SAP One Domain Model and the APIs”. It enables API implementation teams at
distribution mechanisms of the SAP Cloud customers and partners to apply SAP’s guidelines
for harmonized REST APIs in their own projects.
15 / 82

SAP GRAPH4 Figure 8: SAP Graph Software
Existing SAP applications, naturally grown or
acquired by SAP, come with a multitude of APIs,
data representations, and domain models. The
challenge of forging these elements into a single
Client apps
unified domain model and API is considerable
when you bear in mind the thousands of
applications that already use them. In addition SAP® Graph
to listing existing APIs in SAP API Business Hub,
SAP is committed to delivering a new, modern, Product
side-by-side API that exposes a unified domain

model, SAP One Domain Model. We refer to this Customer
Workforce
additional API by the name of SAP Graph.
SAP Graph is one of the main APIs in SAP API
Business Hub. Travel
Sales
SAP Graph is an API for accessing SAP-managed

data. As shown in Figure 8, it exposes a unified
SAP
graph-like domain model of business objects
SAP SAP Customer SAP Ariba®
S/4HANA® Experience SuccessFactors® solutions ...
solutions
(domain entities, such as Products and Sales SAP business systems

Orders) and relationships (links) to client
applications, hence its name. Application
developers use SAP Graph as a RESTful service SAP Graph uses open standards such as OData v.4
to navigate and access the data, regardless of as a single access protocol and OAuth for unified
where (in which business system) that data authentication. By unifying the data access to a
resides, on premise or in the cloud. single interface, the entry barrier for extending
intelligent enterprises is lowered significantly.
Overall, SAP Graph leads to higher productivity
and a better development experience.
4. SAP Graph is currently in the “private beta” phase. For details, see https://beta.graph.sap.
16 / 82

SAP Integration Solution Advisory
Methodology
To support the digitalization of business processes, SAP Integration Solution Advisory Methodology
the scope of integration practices within customer supports enterprise architects on this journey
organizations is constantly increasing. To tackle with a proven approach for tackling the growing
the broad scope of integration, customers need integration challenge, complemented with
to evolve their enterprise integration architecture defined best practices and accelerators for
while leveraging existing investments and skill integration. Customers and partners can adapt
sets. Large organizations typically build on the and enrich the content of this methodology,
principle of a hybrid integration platform, which is delivered by SAP, according to individual
combining integration technologies and services requirements.
that may come from different vendors. This implies
the need to give integration developers guidance METHODOLOGY IN A NUTSHELL
as to which integration technology or service to The goal of SAP Integration Solution Advisory
choose for an integration scenario. In addition to Methodology is to help raise the integration
technical aspects, customers need to consider maturity level of an organization by moving from
the organizational dimension of integration. arbitrary integration to a systematic approach
When specifying and introducing common based on well-defined integration standards. For
integration roles and processes, customers this purpose, the methodology can be applied
can better scale integration knowledge across stepwise for the following use cases (see Figure 9).
and beyond their organization.
Figure 9: Overview – SAP Integration Solution Advisory Methodology
Assess your
integration strategy
egy and g
strat ove
io n r
at na
gr ration domai
teg ns
nc
te
In
In
SAP® Integration
Enable a practice of Solution Advisory Design your hybrid
empowerment integration platform
styles
Use ca
Methodology
ion
se
te
pa
eg
ra
rn
Int
ies
t
s
en
Op
no
lo
: SA h
P and tec
third-party
Define integration
best practices
17 / 82

Let us now examine each use case, its objective and approach, and the provided accelerators.
Assess Your Integration Strategy

Enterprise architects can use the methodology to assess their integration architecture and identify
areas for future improvement. This assessment is performed in a staged approach starting with
identifying the relevant integration domains. Integration domains are typical integration areas within
a hybrid system landscape, such as on-premise-to-cloud or cloud-to-cloud integration (see Figure 10).
Figure 10: Integration Domains
User-centric SAP Third party Real-world

applications SAP S/4HANA® Cloud SAP Ariba®
objects
solutions
SAP® Customer
User to cloud Cloud to cloud Thing to cloud
Experience SAP Concur®
solutions
SAP SuccessFactors®
solutions ...
SAP Fieldglass® Cloud apps
solutions
Business Government
Private cloud
partner agency
Cloud
On premise to cloud
On premise
SAP Third party
On-premise to
User to on premise SAP Business SAP S/4HANA Applications Thing to on premise
on-premise
Suite
Integration domain
Enterprise architects can use the methodology

to assess their integration architecture and
identify areas for future improvement.
18 / 82

The next level of detail is to perform a scoping on For example, the “data integration” style includes
the level of integration styles. Integration styles use case patterns such as data replication and
describe the different categories of integration: data virtualization. Use cases that cannot be
process, data, user, IoT, and analytics. Each assigned to a single integration style are
integration style has specific characteristics and classified as cross use cases. The methodology
can be refined by use case patterns (see Figure 11). includes an initial set of use case patterns that
can be extended by customers. Like integration
domains, integration styles and use case
patterns are technology agnostic.
Figure 11: Catalog of Integration Styles and Use Case Patterns
Integration styles
Process Data Analytics User Thing

integration integration integration integration integration
A2A Data Embedded Thing to

UI integration
integration replication (ETL) analytics analytics
Master data Data Cross-application Mobile Thing to

integration virtualization analytics integration process
Use case patterns
B2B Data quality Chatbot Thing to

integration management integration data lake
B2G Data Customer-specific

Thing to thing
integration orchestration use case
...
... ... ...
API-managed Event-based Stream Workflow Robotic process Digital

...
integration integration analytics management automation integration hub
Cross use cases
19 / 82

Design Your Hybrid Integration Platform hybrid integration platform, the set of relevant
SAP Integration Solution Advisory Methodology integration domains and use case patterns of the
can be used to blueprint an integration reference previous use case (see “Assess Your Integration
architecture for an organization based on Strategy”) are mapped to the respective
integration technologies from SAP as well as integration technology and service categories
third parties. For shaping an organization’s (see Figure 12).
Figure 12: Technology Mapping
Integration Process Data Analytics User Thing Cross use
Technology-agnostic
styles integration integration integration integration integration cases
concepts
Use case
P1 P2 ... D1 D2 ... A1 A2 ... U1 U2 ... T1 T2 ... C1 C2 ...
patterns
Capabilities
SAP or third-party
Enterprise Data API
components
IPaaS IoT platform ...
Integration service bus integration management
technologies
T1, T2, … T3, T4, … T5, T6, … T7, T8, … T9, T10, … ...
Customer context
This mapping is highly influenced by the best practices. This can be best accomplished by
customer context, such as existing investments, creating architecture blueprints for the relevant
commercial aspects, and more. Enterprise integration use case patterns (including
architects may need to combine several integration domains) of the hybrid integration
technologies, such as integration platform platform. The methodology includes a catalog of
as a service and an IoT platform to design an sample architecture blueprints using integration
organization’s hybrid integration platform. technology and services from SAP, which also
deliver information about how to implement the
Define Integration Best Practices blueprint (see Figure 13). These blueprints can
Enterprise architects can derive integration be applied along with other existing best
standards for their organizations. This makes practices, such as the SAP Best Practices
it possible to channel the integration demand package for SAP S/4HANA or enterprise
through well-defined processes and systematically integration patterns for SAP Cloud Platform
implement integration solutions based on company Integration Suite.
20 / 82

Figure 13: Sample of an Architecture Blueprint (Digital Integration Hub)
Public cloud
Apps I Data I Users | Things SAP Cloud application
Fiori® (SAP, third party)
Desktop Mobile
Public cloud
SAP® Cloud Platform
integration API Pub/Sub
components management
Read Write Enterprise
messaging
Your
application Pub/Sub
SAP HANA®
Cloud integration
database
TCP Secure tunnel
On-premise Firewall
integration Cloud
components connector DMZ
Firewall
Smart data Data
provisioning
integration agent
Firewall
On-premise
Apps I Data I Users | Things Database On-premise application
(SAP, third party) (SAP, third party)
Enable a Practice of Empowerment introducing an integration competency center.

Once integration best practices have been This helps establish integration as a recognized
defined, they can be rolled out to the organization, discipline within an organization.
empowering project teams to develop interfaces
in an agile way based on the defined integration The next sections provide SAP technology
strategy. This also provides a feedback channel recommendations for the most important
for incorporating lessons learned into the integra- use case patterns from the areas of process,
tion strategy. As part of this use case, organizational data, analytics, and user integration.
aspects and processes are covered, such as
21 / 82

Process Integration
This section provides technology guidance for • B2B integration: Chain business process steps
the “process integration” style and related use between business partners by exchanging
cases. The first part discusses the various use transactional data, leveraging standard B2B
cases that the Cloud Integration capability of protocols. Example: Exchange purchase
SAP Cloud Platform Integration Suite and orders using B2B standards such as ANSI ASC
SAP Process Orchestration support in the X.12 or UN/EDIFACT in a design-to-operate
context of a typical hybrid landscape. It outlines process that integrates a manufacturer with
how the SAP Application Interface Framework suppliers.
tool complements these two technologies to • B2G integration: Transform transactional data
enable integration architects to implement end- into predefined exchange formats and transfer
to-end integration scenarios across integration it electronically to external legal or tax authority
and application layers. The section then provides systems. Example: File goods and services tax
an overview of various services available on returns from SAP S/4HANA to the Goods and
SAP Cloud Platform – such as SAP Cloud Platform Services Tax Network (GSTN) organization of
Master Data Integration and SAP Cloud Platform India in a prescribed format and protected
Enterprise Messaging – as well as the API fashion.
Management, Open Connectors, and Integration
Advisor capabilities of the integration suite. This section also addresses the following
Finally, guidance on when to use SAP Cloud cross use cases:
Platform Extension Suite is given. • API-managed integration: Provision
omnichannel and secure access to business
USE CASES applications by managed APIs. Example:
The following main use case scenarios of the Expose APIs to business partners. Managed
“process integration” style can be distinguished: APIs leverage API traffic management policies,
• A2A integration: Chain business process steps API security policies, and API analytics.
between business applications by exchanging • Event-based integration: Decouple applications,
transactional data. Example: Exchange sales extensions, or IoT data by messaging principles
orders in a lead-to-cash process across (pub/sub). Example: With event-driven extensions
SAP Customer Experience solutions and for SAP S/4HANA, application extensions can
SAP S/4HANA. react to events from SAP S/4HANA out of
• Master data integration: Exchange master the box.
data across business applications. Example:
Provide cost center and people data from
SAP S/4HANA Cloud to the SAP SuccessFactors®
Employee Central solution.
22 / 82

THE CLOUD INTEGRATION CAPABILITY AND each other in a typical hybrid system landscape.
SAP PROCESS ORCHESTRATION The section then focuses on how integration
The Cloud Integration capability of SAP Cloud content developed for the Cloud Integration
Platform Integration Suite and SAP Process capability of the suite can be deployed on
Orchestration build the foundation of SAP’s SAP Process Orchestration (starting with release
integration strategy for supporting A2A, B2B, 7.5). It concludes with a discussion of how, based
and B2G integration. They also support use cases on typical integration patterns, SAP Application
for master data integration. The technologies are Interface Framework can be combined with
complementary. The Cloud Integration capability the Cloud Integration capability of the suite and
of the suite is SAP’s strategic integration tech- SAP Process Orchestration. The SAPinsider
nology for hybrid and cloud integration for both article “Future-Proof Your Integration Strategy
SAP-to-SAP integration as well as partner and with SAP Cloud Platform Integration Suite”
third-party integration. further describes how both solutions can be
used to support a hybrid integration landscape.
SAP Process Orchestration is on-premise
integration software that bundles process Figure 14 shows a typical hybrid system land-
integration, business process management, scape from an integration point of view. It
and business rules management capabilities. includes on-premise SAP applications, cloud
Described below is how you can use the solutions from SAP, and applications from
Cloud Integration capability of the suite and SAP partners, third parties, business partners,
SAP Process Orchestration to complement and public authorities.
Figure 14: Hybrid Integration Landscape – Integration Domains
3 SAP® Cloud Platform Integration Suite, Cloud Integration capability
Cloud solutions from SAP Third party B2B, B2G

SAP Customer SAP SuccessFactors® SAP Concur®
SAP S/4HANA® Partner solutions Business partner
Experience solutions solutions
SAP Application Extension apps on
SAP Fieldglass®
Interface Framework SAP Ariba® solutions Third-party solutions Government
solutions SAP Cloud Platform
SAP Cloud Platform Integration Suite,

2c Cloud Integration capability
Cloud
2b 2a
On premise
Cloud connector
1 SAP Process Orchestration
SAP applications Third party
SAP Application SAP Application

Interface Framework Interface Framework Third-party solutions Partner solutions
SAP Business Suite SAP S/4HANA
23 / 82

• On-premise-to-on-premise integration: a customer with a major on-premise footprint
When starting with a typical as-is customer and existing investments in SAP Process
landscape, SAP Process Orchestration 7.5 is Orchestration wants to integrate a single
the recommended approach for integrating cloud solution from SAP (for example, a
on-premise software such as SAP S/4HANA, SAP SuccessFactors solution), SAP Process
SAP Business Suite software, third-party appli- Orchestration can be used (see Figure 14,
cations, and legacy applications (see Figure 14, path 2a). It is also possible to deploy cloud
path 1). In addition, SAP Process Orchestration integration content on SAP Process Orchestration
offers B2B functionality with exhaustive 7.5. Following SAP’s integration strategy as
capabilities to integrate business partners, introduced above, the Cloud Integration capability
leveraging industry standards such as EDIFACT of the suite supports mediated integration for
and ASC X.12 (see “B2B Integration” and SAP application scenarios that is not based on
“B2G Integration with SAP Document aligned APIs (see Figure 14, path 2b). Aligned
Compliance”). SAP Process Orchestration is APIs between two SAP applications may provide
also available in SAP HANA Enterprise Cloud route-through content for the Cloud Integration
and can be used to connect on-premise capability of the suite. In that case, the customer
applications in the customer landscape with can choose to deploy the route-through inte-
applications hosted in a private cloud environ- gration flow on the cloud integration runtime
ment. Since mainstream maintenance for of SAP Cloud Platform Integration Suite, for
older releases of SAP Process Orchestration example, to comply with company standards or
(7.1x, 7.3x, and 7.4) will end after 2020, SAP if point-to-point integration should be used. The
recommends upgrading to the SAP NetWeaver® point-to-point (direct) option may be considered
technology platform 7.5. Furthermore, SAP for simple landscapes (see Figure 14, path 2c).
recommends evaluating existing integration Customers with a policy to route all communi-
scenarios and – wherever possible – moving cation to and from the cloud through their
them to SAP Cloud Platform Integration Suite. local SAP Process Orchestration software can
The way forward for SAP Process Orchestration is integrate SAP Process Orchestration with the
described in detail in the blog in SAP Community Cloud Integration capability of the suite. However,
titled “Process Integration (PI) Way Forward this leads to the necessity of maintaining routing
and Recommended Actions.” rules in both technologies. In addition to
• Hybrid integration: SAP Cloud Platform SAP-to-SAP integration scenarios, the
Integration Suite with its Cloud Integration Cloud Integration capability of the suite can
capability is the recommended integration be used to integrate cloud-based software
platform. It provides a rich and continuously from third parties, business partners,
growing set of integration packs. However, if business networks, and public authorities.
24 / 82

Examples are the integration of SAP applications risk. In the customer-managed case, integration
with SAP Information Collaboration Hub for Life packs are provided by SAP and configured by the
Sciences to track pharmaceutical products at customer while SAP operates SAP Cloud Platform
every stage in the supply chain. Another example Integration Suite. This provides the customer
is the integration of SAP applications with the with the highest flexibility and the ability to
systems of tax authorities (e-documents). implement custom extensions. The Cloud
• Cloud-to-cloud integration: The Cloud Integration capability of the suite can also
Integration capability of the suite is used for be used to integrate cloud applications from
integrating between cloud applications (see third parties, business partners (B2B), and
Figure 14, path 3). Where aligned APIs exist, public authorities (B2G). The Cloud Integration
direct connections between applications can be capability of the suite and SAP Process
established. SAP-to-SAP scenarios can be man- Orchestration are complementary. Table 2
aged by SAP or by the customer. For scenarios summarizes key criteria for integration
managed by SAP, configuration and operation architects to consider when deciding which
are conducted by SAP, which gives the customer integration technology to use.
maximum speed to value and lowest project
Table 2: The Cloud Integration Capability Versus SAP Process Orchestration
Cloud Integration Capability of

SAP Process Orchestration
SAP® Cloud Platform Integration Suite
Deployment • Data centers owned and run by SAP • Customer landscape

• Fully vendor-managed multi-cloud in major • Private cloud (for example, SAP HANA®
hyperscale environments Enterprise Cloud)
• Customer-managed in hyperscale
environments
Operations including SAP Customer

maintenance, updates,
and upgrades
License model Monthly subscription fee, pay per use Product license
Architecture • Multitenancy with data isolation • Single-tenant solution

• Virtualization with automated failover • Failover to be configured by customer
• Rolling software updates • Near-zero downtime maintenance for updates
through support packages or enhancement
packages
Prepackaged Availability for a wide variety of cloud • Availability for a wide variety of on-premise
integration content solutions from SAP, third-party applications, SAP® software and third-party software
and business-to-business and business-to- • Runtime of the Cloud Integration capability
government scenarios of SAP Cloud Platform Integration Suite
(starting from SAP Process Orchestration
software, release 7.5) for reuse of cloud
integration content
Continued
25 / 82

Table 2: The Cloud Integration Capability Versus SAP Process Orchestration (continued)

SAP® Cloud Platform Integration Suite
Preferred • Cloud to cloud • On premise to on premise

integration • On premise to cloud (for customers with a • On premise to cloud (for customers
domains cloud focus) with an on-premise focus), however SAP
recommends moving hybrid integration
scenarios to SAP Cloud Platform Integration
Suite
Decision criteria • Center of gravity – deployment of most or • Center of gravity – deployment of most
leading applications – in the cloud or leading applications – on premise
• No need to invest in on-premise middleware • Interest in leveraging an existing invest-
(installation, operation, upgrades) ment in SAP Process Orchestration
• Fast innovation cycle • Customer interest in having full control
• Flexible license model over integration (installation, operation,
• Scenarios with a need for compliance, such upgrades)
as e-invoicing or payroll, to integrate with
legal authorities
Multi-Cloud Support Integration capability of SAP Cloud Platform

As a fully managed, multi-cloud-ready integration Integration Suite. B2B and B2G integrations refer
platform, SAP Cloud Platform Integration Suite is to processes that interlink business partners in
available in many regions around the globe. You the private and public sector. Business networks
can choose between data centers hosted by SAP managed by SAP, such as the SAP Ariba® Cloud
and those run by our partner infrastructure-as-a- Integration Gateway solution (see “SAP Ariba
service (IaaS) providers. Currently, the supported Cloud Integration Gateway”), leverage this
IaaS providers for the integration suite are capability to simplify the integration between
Microsoft Azure, Amazon Web Services, and enterprises and networks of business or
Alibaba Cloud (specifically, in China). You can get regulatory systems.
an overview of the availability of the SAP Cloud
Platform Integration Suite services by region, In addition to the requirements of A2A integration
infrastructure provider, and release status in within an organization, this use case must support
SAP Trust Center. a variety of industry standards in electronic
business document exchange. These include
B2B Integration UN/EDIFACT, ASC X12, and at a communication
The SAP offering for B2B integration is based level, AS2. With B2B functionality for SAP Process
on the B2B functionality for SAP Process Orchestration and the Cloud Integration capability
Orchestration and the B2B features of the Cloud of the suite, SAP offers two options to build and
run B2B integration scenarios.
26 / 82

SAP plans to provide all required B2B B2G Integration with SAP Document Compliance
capabilities with both deployment variants – Many enterprises must send data to government
the Cloud Integration capability of the suite agencies to conform to local compliance require-
and SAP Process Orchestration. This will allow ments. For example, this can be e-information
customers to choose between the cloud and such as e-invoicing, payroll, or tax across different
on-premise solutions with no limitations imposed, LoBs in different countries. Information and
while offering support for a wide variety of B2B security requirements vary across regions due to
and B2G scenarios. different legal requirements. Initially introduced
in 2014 as the “eDocument” solution, the
The key decision criteria for using the B2B func- SAP Document Compliance solution serves
tionality of the Cloud Integration capability are: as SAP’s global platform for meeting country-
• Minimize effort and cost for maintenance and specific digital compliance requirements.
operations SAP Document Compliance uses the Cloud
• Benefit from the innovation speed of the cloud Integration capability of SAP Cloud Platform
• Connect easily to several cloud-based business Integration Suite to help customers comply with
applications these regulations in multiple countries in a stan-
• Position the B2B business network in a neutral dardized way. It includes GST for India, STP for
environment “in the middle” – between the Australia, PEPPOL for Europe, and e-invoicing for
business partners – potentially allowing easier VAT for Spain, Hungary, Chile, and Italy – to name
integration a few (see Figure 15).
Figure 15: SAP® Document Compliance: E-Government Integration Cloud
Tax Integration SAP® SuccessFactors® eVAT for KATRE Wage ELSTER for Germany
by Vertex for Employee Central Payroll – Netherlands Reporting for
the U.S. Integration with Norway Finland
Electronic Invoice
payroll
ePayment and and Transport
eInvoice for Mexico Registration
for Hungary
Electronic Invoicing
for Columbia SAP Document
Compliance –
Electronic Tax
Electronic Invoicing Register Books
for Peru for Greece
• Electronic Invoicing Electronic Invoicing

for Chile for South Korea
• Statutory Reporting
SAP Document
• Payroll e-Filing for UK Compliance, invoicing
• Statutory Reporting option for China
Electronic Invoice and Goods and Services

Transport Registration Tax (GST) Integration
for Portugal for India
• VAT Register Book Electronic Invoicing eInvoice and Delivery Single Touch Payroll New Zealand Inland
for Spain for Italy Note for Turkey (STP) Reporting Revenue Reporting
• Electronic Invoicing for Australia for Payroll
(Facturae)
27 / 82

SAP Document Compliance is available in two integration runtime and creates and manages
deployment models: the integration logic on behalf of the customers.
• Primarily managed on premise: This model These business networks are described in the
requires two components: an on-premise following sections.
component (SAP Document Compliance,
on-premise edition) and a customer-managed SAP Ariba Cloud Integration Gateway
cloud platform service (Cloud Integration The SAP Ariba Cloud Integration Gateway
capability of the integration suite). In this solution, enabled by SAP Cloud Platform
model, the SAP customer deploys and manages Integration Suite, is an offering that integrates
the integration content in the cloud and sets SAP Ariba solutions into an existing customer
up the connections between the back-end infrastructure. While the integration suite is a
system and SAP Cloud Platform and between generic integration platform for all kinds of A2A,
SAP Cloud Platform and the tax authorities. B2B, and B2G scenarios, SAP Ariba Cloud
• Primarily managed in the cloud: This model Integration Gateway specializes in supply chain
requires a single component: a cloud service and procurement processes with a defined set of
managed by SAP. The customer sets up only message types and mappings. SAP Ariba Cloud
the connectivity between the back-end system Integration Gateway accelerates the integration
and the cloud service, while the service takes process by making it simple to connect trading
care of the connection to the different receivers, partners, SAP Ariba solutions, Ariba Network,
simplifying the setup and operation of the and customer back-end systems, such as
solution. In this model, the Cloud Integration SAP S/4HANA or SAP Business Suite. More
capability of the integration suite is the central specifically, SAP Ariba Cloud Integration Gateway
component of the service. is an integration offering managed by SAP and
based on SAP Cloud Platform Integration Suite.
Business Networks It provides an efficient way to integrate buyer
The Cloud Integration capability of the and supplier systems through one gateway to
integration suite enables and powers business Ariba Network and SAP Ariba solutions in the
networks (or integration clouds) that interlink cloud. SAP Ariba Cloud Integration Gateway
business partners in the private and public offers self-service tools built on the integration
sector. The capability performs all the mediation suite that include integration wizards, a self-
of the message exchange. It offers various testing framework, and reporting and monitoring
connectivity options, high security, reliable capabilities – all tailored for the integration use
messaging with the necessary quality-of-service, case by SAP Ariba solutions. Figure 16 gives an
bidirectional flow with multiple communication overview of the integration options for buyers
patterns, and numerous integration capabilities and suppliers with SAP Ariba Cloud Integration
such as routing, mapping, and security protocol Gateway.
mediation. SAP provisions and maintains the
28 / 82

Figure 16: SAP Ariba Cloud Integration Gateway – SAP Cloud Platform Integration Suite
Buyers Suppliers
Add-ons for EDIFACT

SAP Ariba Cloud
Integration X12
Gateway
One-click Test
deployment central
OAGIS
SAP® Ariba® Cloud
SAP SAP Integration Gateway GUSI
S/4HANA® ERP
Developer
Secure
EANCOM
tools
SAP Fieldglass®
solutions PIDX
SAP IBP Byers Suppliers
cXML
SAP Concur® Connection
protocols Ne k Multitenant
tw or
solutions
Buyer Supplier
Microsoft
SAP S/4HANA Dynamics
Cloud, essentials
edition Quickbooks
SSO Enabled by
Portal
Third-party SAP Cloud Platform Peachtree
ERP (future) Integration Suite
Add-on
Oracle Standards for SAP
mapping Integration
wizard
SAP Ariba Cloud
repository
Infor ERP Integration
Gateway
PeopleSoft
SAP
JD Edwards
S/4HANA
Lawson Cloud, essentials
edition
Buyers can integrate SAP S/4HANA or SAP Further Business Networks

Business Suite by using their existing integration Additional business networks are supported
technologies. They might use SAP Process by the following products:
Orchestration or the Cloud Integration capability • SAP Information Collaboration Hub
of the integration suite (managed by the customer) for Life Sciences (a pharma network):
or integrate directly through the cloud connector SAP Information Collaboration Hub for Life
of SAP Cloud Platform Connectivity. As a Sciences is an on-demand solution that
foundation, SAP provides an add-on for connects pharmaceutical organizations
SAP S/4HANA and SAP Business Suite that and supply chain partners through a secure
covers all application-related artifacts, such as cloud service owned and managed by SAP.
application configuration and interface data. This It offers traceability message exchange
allows suppliers to connect once to Ariba Network and transformation as well as reporting to
to integrate with many customers without having government agencies and the European Hub.
to deal with buyer-specific mappings or customized It complements existing SAP solutions, such
configurations. As shown in Figure 16, SAP Ariba as the SAP Advanced Track and Trace for
Cloud Integration Gateway supports multiple Pharmaceuticals application, to support SAP
B2B standards and can integrate with the customers in their endeavor to stay compliant
existing supplier infrastructure through, for with the various national regulations.
example, SAP Process Orchestration or the
Cloud Integration capability of the integration suite.
29 / 82

• Peppol access services of SAP Document in SAP S/4HANA and serves as an add-on to
Compliance, cloud edition: The Peppol access SAP Business Suite. It complements the Cloud
services of SAP Document Compliance, cloud Integration capability of SAP Cloud Platform
edition, provide Peppol access point services to Integration Suite and SAP Process Orchestration
senders and receivers of electronic documents with a deep integration capability in the application
using Peppol eDelivery Network. They enable layer (see Figure 17). SAP Application Interface
them to exchange invoices and related Framework provides an efficient way to implement,
documents in electronic form with authorities monitor, and analyze inbound and outbound
and business partners. application interfaces from a central location
• SAP Multi-Bank Connectivity: The within the application. It provides full access to
SAP Multi-Bank Connectivity solution is an the relevant data and functions of the underlying
on-demand solution that connects financial SAP applications. This makes it possible to
institutions and other financial service providers implement, for example, data validation checks
with their corporate customers on a secure as well as value mappings that rely on application
network that is owned and managed by SAP. data and business logic.
The solution simplifies connectivity, automates
financial transactions, helps to reduce payment SAP Application Interface Framework enables
rejection rates, eases reconciliation, and provides business users to monitor interfaces, trigger
enhanced visibility to corporate treasury. alerts, and manage errors without IT support,
• SAP Cloud for Utilities: The SAP Cloud for which drastically reduces the time needed for
Utilities solution is an industry business error handling. Integration messages that run
solution that supports end-to-end industry into application-level errors can be efficiently
processes across all business functions, at corrected by business users in a way that
scale, in the cloud, and in real time. It uses complies with the General Data Protection
leading technology innovations that help utility Regulation (GDPR). It eliminates the need to
companies compete in a digital world. return the message to the sending application
and ask for a resend. SAP Application Interface
SAP APPLICATION INTERFACE FRAMEWORK Framework improves governance through role-
SAP Application Interface Framework is an based access to interface data and through its
interface management tool that is embedded capability to hide sensitive fields from monitoring
and error handling.
SAP Application Interface Framework enables

business users to monitor interfaces, trigger
alerts, and manage errors without IT support,
which drastically reduces the time needed for
error handling.
30 / 82

Figure 17: SAP Application Interface Framework
SAP S/4HANA® or SAP® Business Suite
Standard applications Alert management
Application log
Security, authorizations
SAP functions Custom functions Data
SAP Application Interface Framework

Interface customizing Monitoring and error handling
(for example, data validation, value mapping) (forward error correction)
Integration Business
developer user
API layer
Application layer
Integration layer
SAP Cloud Platform SAP Process
...
Integration Suite Orchestration
Cloud On-premise Cloud On-premise

applications B2B, B2G applications B2B, B2G
applications applications
The combination of SAP Application Interface tasks of process integration can be distributed
Framework with either the Cloud Integration ideally in the integration layer or close to the
capability of the integration suite or SAP Process application.
Orchestration (with both being part of the
integration layer) has great potential. Available Table 3 gives an overview of typical integration
with either SAP S/4HANA or SAP Business Suite, patterns best implemented in either the
it provides integration architects with a powerful integration layer or the application layer. It
combination for integrating external applications, provides guidance for integration architects on
business partners, and public authorities. The best practices for each integration pattern.
The combination of SAP Application Interface

Framework with either the Cloud Integration
capability of the integration suite or SAP Process
Orchestration has great potential.
31 / 82

Table 3: Sample Integration Patterns – Integration and Application Layer
Sample integration pattern Integration layer Application layer
Cloud Integration capability of SAP Application

Integration technology SAP® Cloud Platform Integration Interface Framework
Suite or SAP Process Orchestration
Structure mapping
Routing
Splitter
Aggregator
Protocol adaptation
Value mapping – static code list
Value mapping – dynamic code list
Data validation
Forward error correction
(business user)
Recommended Partially possible Not recommended
It is recommended that the following integration within the sending application. The determination
patterns be implemented in the integration layer of logical receiver destinations within an
either in the Cloud Integration capability of the application is usually tightly coupled with the
integration suite or SAP Process Orchestration, application data and process model and, hence,
as reflected in Table 3: is part of the application layer. An example is
• The structure mapping pattern maps the configuration of the distribution model in
message fields between two interfaces. the ABAP programming language.
Structure mappings can mediate between • The splitter pattern creates multiple messages
different structures of the same format (for out of a received message by fragmenting the
example, two different XML structures) or even payload by a splitter rule. By then applying the
change the format (for example, from JSON to routing pattern, split message parts might be
XML). routed to different receivers.
• The routing pattern is used to determine for • The aggregator pattern collects multiple
a given message a set of receivers based on inbound messages until a modeled threshold is
static settings (technical routing) or message reached. A single payload is then constructed
payload data (content-based routing). Logical out of all aggregated payloads by applying an
receiver destinations define a message receiver aggregation rule. Finally, this single message
is forwarded to one or more receivers.
32 / 82

• The protocol adaptation pattern handles the detect application errors, such as incomplete
mediation between two different protocols used value mappings, due to unforeseen values
by the sending and receiving applications (for coming up. They then must extend these
example, Java Message Service, REST, or mappings in an agile way close to the
SOAP5). application. As opposed to dynamic value
mappings, static code-list-value mappings (for
For further integration patterns related to the example, country code mappings) can be best
integration layer, refer to the book Enterprise implemented in the integration layer, as they
Integration Patterns by Gregor Hohpe and can be reused across multiple integration
Bobby Woolf published in 2003 by scenarios between various applications.
Addison-Wesley. • The data validation pattern checks a received
message with respect to schema correctness
The following patterns can be implemented or data correctness. This pattern can be applied
either in the integration layer or the application in the integration layer as well as in the
layer: application layer. SAP Application Interface
• The value mapping pattern transforms field Framework particularly supports this pattern,
values that are exchanged between two as it provides full access to application data and
applications. Since this pattern is tightly functions.
coupled with business application data, • The forward error correction pattern handles
business users must be able to maintain value an application error during message processing
mappings in a dynamic way. The value mapping by forwarding it to the receiver. One key capability
pattern is typically covered by SAP Application of SAP Application Interface Framework (in the
Interface Framework, as business users may application layer) is this exact type of error
correction and resolution by business users.
The data validation pattern checks a received

message with respect to schema correctness or
data correctness. This pattern can be applied in the
integration layer as well as in the application layer.
5. “List of Abbreviations” can be found at the end of the document.
33 / 82

SAP CLOUD PLATFORM MASTER DATA Enterprises Are Integrated Enterprises” names
INTEGRATION “aligned domain models” as an important suite
Master data objects – for example, Workforce quality and thus explicitly considers this challenge.
Person, Cost Center, Business Partner, or Product Historically, for both integration and management
– are used in the various applications of end-to- (including quality enhancement), either a set
end business processes of an intelligent enterprise, of individual point-to-point integrations, a
for example, recruit to retire, lead to cash, source centralized SAP Master Data Governance
to pay, and design to operate. Establishing application, or both were deployed in enterprise
their reliable and performant exchange and landscapes.
synchronization is a demanding task. “Intelligent
Figure 18: SAP’s Evolved Approach to Master Data Exchange and Synchronization
Procurement Procurement Procurement

Commerce
Commerce Service Commerce Service Service
SAP® Master
Master Data Marketing data
Governance integration
Marketing Billing Marketing Billing Billing
SAP
S/4HANA
SAP SAP SAP
S/4HANA® S/4HANA Master Data
Governance
As shown in Figure 18, the new SAP Cloud language (CDL) of the core data services
Platform Master Data Integration service technology platform form the common and
replaces a similar set of individual point-to-point aligned basis of all data that is exchanged.
interactions between involved applications using Applications that are connected to SAP Cloud
a hub and spoke mechanism in the cloud. Platform Master Data Integration are free to use
or keep using their individual object representation
Domain model alignment, resulting in SAP One but can rely on a unified representation during
Domain Model, is currently being established to data exchange and synchronization. This is
cope with master data diversity and to provide a nondisruptive and ensures a viable transition
stable foundation for smooth data exchange. path where existing SAP applications are not
(See “SAP One Domain Model.”) Object requested to change. They just have to
representations described in the core definition implement their individual mapping.
34 / 82

The SAP Cloud Platform Master Data Integration itself ensures eventual consistency and also
service provides scalable and robust technical supports and eases key mapping. As shown in
means for publishing master data creation or Figure 19, the change and log APIs encapsulate
modification events from individual, connected the scalable distributed log mechanism. They
applications. It allows other thus loosely coupled are the way for (out-of-the-box integrated)
participants to monitor these business events SAP applications to interact with the service.
and to react and, for example, persist the Customers and third parties can access the
changes in their own application. The service service through the Cloud Integration capability
of the integration suite.6
Figure 19: Interaction with the SAP Cloud Platform Master Data Integration Service
Customer and third-party applications
Exposure through SAP® Cloud Platform Integration Suite
SAP Cloud Platform Master Data Integration service

Change API Distributed and scalable Log API
(inbound) master data event log (outbound)
Change requests Change event

(using SAP One notifications (using
Domain Model object
(Out-of-the-box integrated) SAP applications SAP One Domain
representation) Model object
representation)
Guidance for Master Data Integration and same purpose, need not be migrated to use the
Management master data integration service. As shown in
The SAP Cloud Platform Master Data Integration Table 4, when it comes to master data
service is embedded in SAP Business Technology management, SAP Master Data Governance is
Platform. It is used implicitly by other services, still the preferred solution. (Also refer to the blog
such as the Cloud Integration capability of the “FAQ About SAP Master Data Governance.”) As
integration suite, and other SAP applications to shown in Figure 18, SAP Master Data Governance
exchange and synchronize master data objects. can interact through the SAP Cloud Platform
The existing implementations, where the Cloud Master Data Integration service.
Integration capability of the suite is used for the
6. Direct access to the SAP Cloud Platform Master Data Integration service for customers and partners is not supported.
A more convenient integration of the Cloud Integration capability of SAP Cloud Platform Integration Suite with the
master data integration service is planned.
35 / 82

Table 4: Technology Recommendations for Master Data Integration and Management
SAP® Cloud Platform Cloud Integration SAP Master Data

Master Data Integration capability of SAP Cloud Governance
Master data integration 1 2

(SAP-to-SAP)
Master data integration 3 4
(SAP-to-non-SAP)
Master data management
1. Built-in integration for SAP-to-SAP is especially for new implementations based on aligned domain models.
2. Existing scenarios on SAP® Cloud Platform Integration Suite services can exist with no need to be migrated.
3. Usage is over SAP Cloud Platform Integration Suite services.
4. This implicitly uses SAP Cloud Platform Master Data Integration for access in case of aligned domain models.
The road map for aligned domain models APIs are the digital building blocks for achieving
supported by SAP Cloud Platform Master Data agility, composability, and connected multiexpe-
Integration is described in “Intelligent Enterprises riences and for innovating on new business
Are Integrated Enterprises,” with focus on cloud models. SAP customers want a 360-degree
scenarios in the context of an intelligent enterprise. API platform that supports (a) API businesses,
Further information on this topic can be expected (b) API engagement through marketplaces,
in future updates of that document as well as in and (c) agile and accelerated API development
SAP Road Map Explorer. and delivery.
SAP CLOUD PLATFORM INTEGRATION SUITE, With its large installed base, SAP is making the
API MANAGEMENT API conversation mainstream in enterprises
SAP customers across industries and geographies three ways. First, it positions open APIs (see
are in the process of digital transformation. Our SAP API Business Hub) as digital building blocks
customers’ top priorities are: for intelligent enterprises. Second, it helps improve
• Deliver superior connected, intelligent API maturity enterprise-wide. And third, it offers
experiences across multiple channels for a full-lifecycle API platform as part of a business
their customers. In the experience economy, technology platform for all customer innovation
enterprises win by constantly measuring projects.
brand, product, and employee experiences
and delivering these superior experiences Over the past couple of years and in several
with agile business operations. digital transformation projects of our customers,
• Improve process excellence by adding more SAP has rapidly evolved its understanding of the
agility and composability in their enterprises importance of APIs and their management – and
across value streams such as lead to cash, delivers on that. The API Management capability
recruit to retire, source to pay, and design to of the integration suite addresses three areas –
operate. (a) API marketplaces, (b) API management and
• Innovate with digital ecosystems and new engagement, and (c) API development and
business models by collaborating across delivery (see Figure 20).
business networks and driving growth through
new subscription-based business models.
36 / 82

• API marketplace: SAP’s own API marketplace innovations on top of APIs. API engagement is
is SAP API Business Hub. Customers can offer about democratizing access to digital assets for
their own API marketplace with the developer LoB users, citizen developers, and citizen
portal capabilities. Customers running a full API integrators.
business can leverage the SAP Subscription • API development and delivery: The API
Billing solution for subscription management, Management capability of the integration suite
rating, billing, and invoicing. supports agile development and delivery
• API management and engagement: API practices and supports multiple modes of API
management facilitates full lifecycle development. Two of these modes are low-code
management of APIs – smart discovery of API development and no-code, wizard-based
APIs, creating and managing API products API development with the Open Connectors
for API product managers, and having a great capability of the integration suite. Two
engagement with developers. API management additional modes are serverless functions for
has a measurable positive business impact on event-based APIs and microservices-based
an API program. API engagement is a critical API development with a domain-driven
component in helping developers easily discover, approach to APIs in Cloud Foundry and
consume, and build apps, integrations, and Kubernetes environments.
Figure 20: 360-Degree API Platform for the Intelligent Enterprise
Digital innovations Digital

innovations
Multiexperience Digital ecosystems and Real-time Apps, digital
(apps, bots) industry business networks analytics ecosystems, and
Consumers
multiexperience
API marketplace API marketplace

SAP® API Business Subscription and For running a
Developer Portal
Hub, SAP App Center, Billing full-fledged API
Total developer
and SAP Graph Subscription management,
App engagement business
SAP’s marketplace for APIs rating, billing, and invoicing
developers
API management and engagement API management

and engagement
API Portal API monetization API Analytics API Gateway
API design, smart With the app
API products, rate plans, Business insights Policy
API product discovery, policy subscription billing and operational enforcement developers and
manager management
alerts point makers
API development and delivery API development

and delivery
Low code/no-code Domain-driven Microservices-based Serverless Digital Platform for
API and API development API development API development functions integration accelerated API
integration with IPaaS with cloud application Cloud Foundry, and event-driven APIs hub
developers delivery and AI
programming Kubernetes, and ABAP®
DevSecOps
37 / 82

The API platform from SAP helps customers Developers can use SAP’s domain-driven
manage their enterprise API programs and API design by starting with the domain models
projects across all the phases of the lifecycle. defined in the CDS format – a domain-specific
language – and SAP Cloud Application
Plan and blueprint: The most important part of Programming Model. The model allows data
an API program is business alignment. During experts to model data into business-focused APIs.
this phase, the API product manager engages
with business stakeholders to take stock of the Develop: The API Management capability of the
existing holistic enterprise architecture using integration suite is a powerful API development
SAP Integration Solution Advisory Methodology. and delivery platform. The advantage of combining
This process helps define well-aligned goals for API management with API development is
the API program. Business scenarios, business significant. SAP supports the following ways to
models, and KPIs as well as API road maps are develop APIs:
defined for iterative execution. “Design thinking” • Low-code/no-code API development using
is applied in the planning phase to facilitate the integration suite (and its Cloud Integration
cross-organization discovery. SAP offers process capability), which enables a flow designer to
models and blueprints, recommended business build APIs with graphical support. A no-code,
KPIs, and advisory services to help customers wizard-like connector builder (using the Open
set up API programs. Connectors capability of the integration suite)
allows you to build APIs and provides preconfig-
Design: After the plan and blueprint phase, the ured content to connect to over 160 third-party,
next step is the scenario-driven API design cloud-based solutions (apps, services, and
phase. The scenario-driven API design approach platforms).
is an outside-in design approach where APIs are • Microservices and service-mesh-based approach
designed in quick iterations with business users using programming languages of choice in
and owners of consuming applications. The API Cloud Foundry or Kubernetes
designer UI is used to design the actual APIs and • Serverless runtime for event-based APIs and
supports the API developer in designing APIs function as a service (Kubernetes; SAP Cloud
based on the OpenAPI specification. The designer Platform, Kyma runtime)
also allows importing existing API specifications • SAP Cloud Application Programming Model
in RAML or OData (v2, v4) and transforming them for domain-driven API development to quickly
into OpenAPI specifications. API developers can expose data-centric APIs
use schemas delivered by SAP to define semantics • Digital integration hub with SAP HANA for API
for APIs. They can also generate code in Java data mediation
(JAX-RS, Spring) or NodeJS to start developing
the APIs. SAP offers back-end-as-a-service Manage, meter, and monetize: The API
functionality as part of its serverless runtime Management capability of the integration suite
component for quick creation of API mock supports smart API discovery and provides over
services. 40 out-of-the-box policies (traffic management,
38 / 82

security, caching, mediation) to manage APIs. SAP Subscription Billing is a powerful solution
API product managers can define API that helps customers run subscription businesses
products, add rate plans, and monetize their to monetize API consumption.
APIs successfully. Once APIs are launched,
powerful analytics based on SAP HANA help Build digital innovations with APIs: The most
API product managers measure the business important value of APIs is how easy they make
KPIs and value of the API programs. it to build apps, integrations, and innovations.
SAP API Management technology, powered
Engage: The API Management capability of the by SAP HANA, offers deep integration to
integration suite supports engagement with both SAP Business Application Studio to build apps
developers and consumers (LoB users, citizen and to mobile services to build native apps for
integrators, and developers). The out-of-the-box, IOS and Android. SAP Conversational AI services
role-based developer portal supports theming can be accessed to build bots easily. APIs can
and customization and helps developers easily also be consumed by business users in the
discover, subscribe, and consume APIs. SAP Analytics Cloud solution to build real-time
dashboards.
Table 5: Sample API Policies and Integration Patterns
API policies and integration patterns API management layer Integration layer
API Management capability of SAP® Cloud Integration capability of

Integration technology SAP Cloud Platform Integration
Cloud Platform Integration Suite
Suite or SAP Process Orchestration
API traffic management policies
API security policies
API analytics and monetization
Structure mapping
Protocol adaptation
Routing
Splitter
Aggregator
Value mapping
Recommended Partially possible Not recommended
39 / 82

Table 5 gives an overview of some typical API Management solution and SAP Subscription
policies and integration patterns that are best Billing. The API Management capability of the
implemented in either the API management layer integration suite includes a built-in rating and
or the integration layer. It provides guidance for monetization feature for simple API
integration architects on how to combine the monetization use cases.
capabilities of both offerings optimally.
The API Management capability of the integration
Policies define a set of rules that are applied to an suite supports basic structure mappings. Over
API to customize its behavior. It is recommended 40 built-in policies help manage and secure API
that the following policies and patterns be end points. SAP ships support for best-practice
implemented in the API management layer, policies in SAP API Business Hub to be copied to
represented by the API Management capability and reused in the customers’ tenants of the API
of the integration suite: Management capability of the integration suite.
• API traffic management policies – This group
of policies helps control traffic quotas and Engaging with developer ecosystems is another
spikes and can set concurrent rate limits for important part of the API Management capability
an API. For example, the quota policy helps API of the integration suite. The capability allows API
providers restrict the number of calls made to developers and product managers to create API
an API in a specific time frame. It also supports products by packaging several APIs, defining rate
the definition of cache policies for an API. plans, and publishing these API products to the
• API security policies – This group of policies developer portal included in the API Management
lets you control security-related aspects of capability of the integration suite. Customers can
an API. The API Management capability of the create their own branded developer portals using
integration suite automatically generates API the SAP Cloud Platform Portal service.
keys on behalf of applications. The policies
enable API providers to view, approve, and As mentioned in “SAP Application Interface
revoke API keys. In addition, the API Management Framework,” it is recommended that the following
capability helps IT administrators control the patterns be implemented in the integration layer –
authentication mechanism that developers either in the Cloud Integration capability of the
require to access an API in a finely granular integration suite or in SAP Process Orchestration.
manner. Those patterns are structure mapping, routing,
• API analytics and monetization – The API splitter, aggregator, protocol adaptation, and value
Management capability of the integration mapping. The API policies and integration patterns
suite provides analytics for understanding API mentioned are only a sample of the policies and
usage as well as errors. Custom reports can be patterns typically used. For additional integration
created on the platform. Metering APIs help to patterns related to the integration layer, refer to the
obtain metering information for integrations book Enterprise Integration Patterns by Gregor
with billing software systems, such as the Hohpe and Bobby Woolf.
SAP Billing and Revenue Innovation
40 / 82

SAP CLOUD PLATFORM INTEGRATION SUITE, CRM, human capital, payments, ERP, accounting,
OPEN CONNECTORS database, messaging, collaboration, e-commerce,
Customer system landscapes are becoming and more.
more heterogeneous and have data maintained
in various distributed systems. The Open The “common resources” functionality enables
Connectors capability of SAP Cloud Platform customers of the Open Connectors capability of
Integration Suite simplifies connectivity to the integration suite to define their own custom
third-party applications and accelerates data model and map it to third-party connectors.
integration by providing prebuilt, feature-rich This enables them to extend features of the
connectors to more than 160 third-party prebuilt connectors and turn their custom data
applications. Customers benefit from simplified model into a callable REST resource within the
connectivity through REST APIs with normalized prebuilt connector. The custom data model of the
authentication, error handling, search, pagination, common resources functionality can be mapped
and bulk support – regardless of the underlying to more than one prebuilt connector to provide a
architecture of the third-party applications. simplified one-to-many integration across
Standardized events support polling and Web multiple third-party applications.
hooks irrespective of the eventing support of the
connected application. This simplifies handling The “formulas” functionality enables customers
of change notifications through the prebuilt to build simple API compositions across multiple
connectors. The ready-to-use connectors come connectors by efficiently chaining requests from
with interactive API documentation based on the multiple connectors together. This enables
OpenAPI Specification 2.0, an open standard customers to address common use cases easily,
for RESTful APIs. It provides integrated test and such as synchronizing contacts across multiple
tryout functionality for third-party applications all third-party applications.
in one place. The connectors are kept up-to-date
by changes at the end point, so the integrations Customers can use the Open Connectors capability
built on them are not affected. of the integration suite with the suite’s Cloud
Integration capability to simplify integration
The connectors are grouped or categorized as with several third-party apps. It also enables
hubs to provide a unified set of Uniform Resource them to drive innovation through open and
Identifiers (URIs) across various connectors that easy integration between SAP and third-party
are part of the same hub (see Figure 21). Hubs ecosystems, as shown in Figure 21. The Cloud
provide consistent resource URIs regardless of Integration capability of the integration suite
the technology used by the target third-party transforms, mediates, and routes requests to
application. Hub topics include marketing, social, third-party applications through the suite’s Open
finance, field service, help desk, cloud storage, Connectors capability, which then establishes the
actual connections to the third-party systems.
41 / 82

Figure 21: Simplified Integration to Numerous Third-Party Apps
SAP SuccessFactors® solutions SAP Concur® solutions Cloud services

SAP® Business SAP S/4HANA® Cloud SAP Customer Experience
Suite And more
SAP Fieldglass® solutions SAP Ariba® solutions
SAP Cloud Platform Integration Open Connectors capability of

Suite services SAP Cloud Platform Integration Suite
Adapters Protocol Message Adapter Formulas Common Connectors

(EDI, HTTP, converters mapping (HTTP) resources
SOAP, IDoc)
Orchestration, mediation, transformation, and routing Third-party connectivity
Harmonized APIs to reduce the

cost of third-party integration
Third-party CRM hub E-commerce hub Storage hub Help desk Social
Act!, Bullhorn, Magento, Shopify, Google Drive, Zendesk, Twitter, Instagram,
apps Zoho, and others Dropbox, OneDrive, Freshdesk, Flickr, and others
Salesforce.com, Amazon S3, Box, ServiceNow, JIRA,
Microsoft and others Salesforce.com
Dynamics, and Service Cloud, and
others others
SAP CLOUD PLATFORM ENTERPRISE SAP solutions such as SAP S/4HANA without
MESSAGING disrupting central business processes. Use this
The SAP Cloud Platform Enterprise Messaging service to create responsive applications that
service is a fully managed cloud service that work independently and participate in event-
allows applications, services, and systems to driven processes inside your company and
communicate through asynchronous messages across your business ecosystem for greater
and events. This allows you to extend core agility and scalability (see Figure 22).
42 / 82

Figure 22: Event-Driven Integration with SAP Cloud Platform Enterprise Messaging
SAP Cloud Platform

SAP S/4HANA®
Integration Suite
SAP® Ariba® solutions

SAP Cloud Platform
Extension Suite
SAP Customer Experience
Messages Messages
and and
INTEGRATE events
SAP Cloud Platform
events
INTEGRATE
AND EXTEND Enterprise Messaging
AND EXTEND
SAP SuccessFactors® solutions

Internet of Things
SAP Concur® solutions
Cloud appliances
SAP Fieldglass® solutions
and microservices
SAP Cloud Platform Enterprise Messaging is Messaging and Event Capabilities

a key component for enabling an intelligent SAP Cloud Platform Enterprise Messaging
enterprise. To facilitate your company’s transition decouples applications and services in your
to becoming an intelligent enterprise, SAP Cloud system landscapes by introducing a dedicated
Platform Enterprise Messaging supports you in messaging service to take full responsibility for
connecting systems, building cloud-native apps, sending and receiving messages and events.
and extending on-premise apps with equal ease. By decoupling communication, messages and
events can be sent asynchronously. This results
Messaging as a Service in higher throughput since the sender does not
SAP Cloud Platform Enterprise Messaging is a need to know of the receiving applications or
fully managed messaging-as-a-service offering. services. This frees up its resources because
SAP as cloud provider is responsible for managing, the sender does not have to wait for a response.
running, and operating this service as part Asynchronous communication ensures greater
of the serverless computing offering on scalability (high throughput, low latency)
SAP Cloud Platform. This serverless ecosystem, because sending applications can simply “fire
in which all servers are implemented and and forget.”
managed by SAP, allows you to spend less time
on operations, scaling, and solving infrastructure
dependencies.
43 / 82

You can use a number of open standards and SAP Cloud Platform Enterprise Messaging
protocols, such as REST, AMQP7 , and MQTT8 supports the CloudEvents specification to
with SAP Cloud Platform Enterprise Messaging. ensure that all event data is shared in a standard
The service supports point-to-point messaging, way that is easily consumable. You can send
publish-subscribe messaging patterns, and events from SAP software sources, such as
publish-and-consume messages from queues SAP S/4HANA and third-party sources, and
and topics through REST APIs. Libraries for Java consume these events in side-by-side extension
and Node.js are also available. apps built on SAP Cloud Platform. The available
events are listed as part of SAP API Business
SAP manages all your data messages across Hub. Extension apps implement additional logic
secure data centers around the globe. Messages or logic different to the underlying business
and events can be placed in queues from which process and use event subscriptions to be
they are sent securely and reliably to the relevant informed of changes in the original system. For
receivers. In case of network issues, messages security, extension app consumers use a read
and events are stored in the queue until they can service to obtain additional information and data
be delivered. about the event. In this way, you can share and
replicate data across hybrid landscapes and
Event-Enablement Capabilities enable event-driven applications in which events
SAP Cloud Platform Enterprise Messaging can trigger the execution of atomic pieces of
provides the messaging capabilities through business logic (functions).
which events (for example, notifications with
business object identifiers) can be transported
between applications and services in hybrid
landscapes (see Figure 23).
SAP Cloud Platform Enterprise Messaging

provides the messaging capabilities through
which events can be transported between
applications and services in hybrid landscapes.
7. Advanced Message Queuing Protocol

8. Message Queuing Telemetry Transport
9. See https://cloudevents.io.
44 / 82

Figure 23: Events and Messages in Hybrid Landscapes

Environment
Events management Messaging

and eventing
Messaging management application
SAP Cloud
Platform Operations and monitoring
Messaging
Enterprise
client APIs
Messaging Configuration
Event sources and destinations on demand Event sources and destinations on premise
On-premise
SAP S/4HANA Other
Other Event Event

event enablement enablement enablement
SAP S/4HANA®
Event enablement
Implementing Event-Driven, Serverless processes. For each specific business need, a

Architectures B2B standard must be chosen out of the many
To implement a fully event-driven, serverless that exist and its interface must be customized.
architecture for becoming an intelligent enterprise, Both require agreement between partners. A
use SAP Cloud Platform Enterprise Messaging detailed analysis must be made, and the required
with other services available on SAP Cloud customization of the B2B standard interfaces
Platform. SAP Cloud Platform Enterprise involved must be specified. Most of these
Messaging, together with SAP Cloud Platform interfaces allow millions of different expressions
Integration Suite, is designed to help you of information on the semantic level, whereas
implement end-to-end integration and just a few are usually required. Those few must
extension scenarios. be mapped to the other individually customized
B2B interfaces at the business partner sites.
SAP CLOUD PLATFORM INTEGRATION SUITE, The comparison and negotiation involved require
INTEGRATION ADVISOR deep business domain knowledge. This complexity
Defining and implementing standards for cannot be reduced by integration packs, which
business document exchange involves complex
45 / 82

cannot anticipate all possibilities, or by experts, Advisor capability unifies the required tasks for
whose expertise is usually in only one of the creating B2B integration content based on intelli-
involved domains. gent proposals derived from a comprehensive
knowledge base through a machine learning
The Integration Advisor capability of the integration approach. With this technology, it is possible to
suite is a cloud-based service that addresses these accelerate the process of building integration
challenges. As shown in Figure 24, the Integration content significantly.
Figure 24: The Integration Advisor Capability of SAP Cloud Platform Integration Suite
Integration Advisor
Editor
Interface specification
Propose Knowledge
graph
Mapping specification
Source interface
+ Simulation Target interface
Contribute
Runtime artifact
Run
Cloud SAP® Process SAP SAP API

integration Orchestration Application Business Hub
Interface
Framework
46 / 82

For creating customized B2B interfaces, the The Integration Advisor capability of the
Integration Advisor capability provides a integration suite supports business domain
comprehensive library of the documentation and experts who need to specify and document the
code lists of all frequently used B2B standards interfaces and mappings. These customized
and de facto standards (for example, ASC X12 interfaces and mappings are used to generate
and UN/EDIFACT). The Integration Advisor automatically the required runtime artifacts
capability has a unified design-time view. The for validation, conversion, transformation,
machine learning algorithms provide high-quality preprocessing, and postprocessing as well as the
proposals on how interfaces should be customized documentation. Technically, these artifacts can
and mappings based on practices learned be used immediately in the integration flows of
from “the crowd.” The crowd refers to the the Cloud Integration capability of the integration
central knowledge graph, where all interface suite (see Figure 25) or in message mappings of
customizations, mappings, and changes made SAP Process Orchestration.
by experts are anonymously registered. These
are used to calculate proposals.
Figure 25: Integration Flows of SAP Cloud Platform Integration Suite
Customized source Mapping Customized target

interface guideline guideline interface guideline
Integration Advisor
capability of
Integration Suite
Generate
Sender
IDoc
SFTP Start IDoc pre- Qualifier pre- Source RD + ORDERS05- Target RD + Qualifier post- Envelope XML to X12 End MAIL
processing processing validation to-X12 850 validation processing handling converter
mapping
Receiver
47 / 82

The content generated by the Integration Advisor It can be combined with the Cloud Integration
capability of the integration suite guarantees capability of the integration suite when process
precise validation of incoming messages as well integration is needed (see “The Cloud Integration
as the generation of error messages. These Capability and SAP Process Orchestration”).
can be used for internal error handling or for
submission to business partners through The cloud connector acts as a reverse invoke
functional acknowledgments,10 which is proxy component that is installed and runs on
supported by the Cloud Integration capability an on-premise network. It establishes a tunnel
of the suite. using the Transport Layer Security protocol –
which replaces Secure Sockets Layer – from
SAP Cloud Platform Integration Suite thus makes the on-premise network to its counterpart in
it possible to create individually customized the cloud, the SAP Cloud Platform Connectivity
integration flows in a semiautomatic manner, service. This service is integrated in SAP Cloud
which serve as the technical adapters for Platform and SAP S/4HANA Cloud. Once a
external communication.11 The Integration tunnel from the cloud connector to SAP Cloud
Advisor capability also supports the tracking and Platform Connectivity has been established,
handling of failed messages and should be used cloud applications that are authorized can access
for all B2B communication scenarios to take full on-premise systems through the tunnel. From an
advantage of this combination. Using application- application perspective, the connectivity service
specific implementations or third-party solutions and its tunnel act like an HTTP-SOCKS5 proxy,
may diminish this benefit. that is, they can be used in a programming-
language-agnostic way. The cloud connector
With the Integration Advisor capability, the administrator has full control over which on-
integration suite lets customers expose their premise systems are exposed to the cloud. The
digital assets, either within or outside their administrator can restrict access to on-premise
organizations. For example, they could submit systems to explicitly configured resources when
their B2B interface requirements to business using HTTP or a remote function call (RFC). The
partners. administrator can also switch the tunnel on or off
at any given time. A single cloud connector instance
THE CLOUD CONNECTOR OF SAP CLOUD can be connected to multiple subaccounts of
PLATFORM CONNECTIVITY SAP Cloud Platform and vice versa. For scenarios
The cloud connector comes as a standard part of in which principal propagation is needed – for
the SAP Cloud Platform Connectivity service. It example, when forwarding the identity of the
establishes secure technical connectivity between cloud user to an on-premise system – trust must
cloud solutions from SAP and protected on-premise be configured between the cloud connector and
networks that cannot be accessed directly from the trust management of the used subaccount.
the Internet. The cloud connector is used in Apart from this, on-premise systems do not need
hybrid scenarios in which cloud applications to be touched or modified to expose them to
must access or extend on-premise software. cloud applications over the cloud connector.
10. UN/EDIFACT: CONTRL and ASC X12: 997.

11. For example, through AS2, SFTP, HTTP/S, or SOAP.
48 / 82

SAP CLOUD PLATFORM EXTENSION SUITE integration logic. The extension suite is a
SAP Cloud Platform Extension Suite12 is the recommended solution when business cases
go-to cloud-native extensibility framework for require adding business logic as extensions,
intelligent enterprises. It offers a standard way providing a UX for new user groups (B2B, B2C),
for extending SAP solutions such as SAP S/4HANA, or implementing innovative business models.
SAP Success Factors solutions, and SAP Customer It supports asynchronous extensions using
Experience solutions, and for developing event- event-driven architecture as well as synchronous
driven extensions and applications. SAP Cloud extensions with APIs and microservices. For
Platform Extension Suite provides the following more information on when to use these two
key benefits: products, see the blog “Simplify Extensions and
• A way of extending standard SAP solutions Integrations Using SAP Cloud Platform, Kyma
without disrupting their performance or core Runtime, and SAP Cloud Platform Integration
processes Suite.” To learn more about the new SAP Cloud
• Frameworks that offer simplified, standardized, Platform Extension Suite, access this
unified extensibility and configuration for introduction.
SAP solutions
• A central repository for solutions’ APIs, events, ROAD MAP FOR INTEGRATION CONTENT
credentials, and other data, ensuring easy As outlined in “Intelligent Enterprises Are
access to services while creating your extensions Integrated Enterprises,” SAP applications can
synchronize business objects with common
Based on this harmonized extension framework, attributes and use common semantics, which
a set of optimized runtimes is available to cover reduces SAP-to-SAP integration efforts for
the various needs of an extension: customers. As mentioned in “SAP Cloud
• SAP Cloud Platform, ABAP environment Platform Master Data Integration,” new
• SAP Cloud Platform Application Runtime implementations can take advantage of
service SAP Cloud Platform Master Data Integration
• SAP Cloud Platform Serverless Runtime service for scenarios for which SAP has delivered
• SAP Cloud Platform, Kyma runtime aligned domain models. SAP Cloud Platform
Integration Suite supports both types of
SAP Cloud Platform Extension Suite and the integration scenarios – those for unaligned
integration suite complement each other by as well as aligned APIs (see Figure 26).
separating the business logic from the
or more information about the naming of SAP Cloud Platform Extension Suite, see “The Evolution of SAP Cloud
12. F
Platform Extension Factory into SAP Cloud Platform Extension Suite.”
49 / 82

Figure 26: Evolution of Integration Content from SAP
Mediated integration Direct integration

SAP® Cloud Platform Integration Suite services SAP Cloud Platform Integration Suite (route-through)
SAP APIs Unaligned APIs Aligned APIs (domain models)
Design time IFlow leveraging integration patterns IFlow without any message transformation
Option 1: Option 2:
Runtime Cloud integration runtime mandatory Cloud integration runtime Direct
Governance extension Simple landscapes
Example
Simplification of integration scenarios
• Mediated integration flows in SAP Cloud complying with company standards, establishing
Platform Integration Suite address SAP-to-SAP central monitoring capabilities, or enabling
integration scenarios that are not based on extensions such as routing to multiple back-end
aligned APIs (for example, integration flows applications. Optionally, the consumer and
of existing integration packs). Integration provider of an integration flow could be directly
mediated by the integration suite covers all integrated during runtime for simple
integration scenarios that include third-party landscapes that do not require runtime
applications, business partners (B2B), or public governance. A route-through integration flow
authorities (B2G). Mediated integration flows with the integration suite also provides the
typically make use of integration patterns, such foundation to plug in customer extensions.
as structure mappings, splitters, aggregators, Examples could be the enrichment of the
and protocol adaptation (for example, from standard flow with information from third-party
REST/OData to SOAP). They are executed in the applications or the integration of an archiving
integration suite. system. A customer extension changes the
• Route-through integration flows in the route-through integration flow into one that is
integration suite are based on aligned APIs, mediated by the integration suite. SAP provides
have exactly one consumer and one provider, tool support (for example, an iFlow wizard in
and do not change the message payload or SAP API Business Hub13) to generate route-
the header. The customer has the choice to through integration flows for the integration
deploy a route-through integration flow on suite based on aligned APIs from SAP or third
the integration suite. Reasons could include parties in SAP API Business Hub.
ee the blog “Route-Through Integration Flow Generation Based on APIs from SAP API Business Hub in
13. S
SAP Cloud Platform Integration Suite.”
50 / 82

Reuse of Integration Packs benefiting from the capability to run prepackaged
Integration packs are built and released by SAP cloud integration content on SAP Process
following a cloud-first strategy: new content is Orchestration (see Figure 27).
built on SAP Cloud Platform Integration Suite,
leveraging fast innovation cycles in the cloud, Customers and partners can use the Web tooling
and shipped through SAP API Business Hub. of SAP Cloud Platform Integration Suite to create
With release 7.5, SAP Process Orchestration has and configure cloud integration content. In the
been extended to support a variant of the cloud discover area of their tenant of SAP Cloud
integration runtime of the integration suite. Platform Integration Suite, they can browse
As per the release schedule of SAP Process integration packs provided by SAP and partners
Orchestration, dedicated versions of the cloud and copy them to their workspace. In the design
integration runtime of the integration suite area of the integration suite, they can modify
are planned to be released for SAP Process and configure the content. Within the cloud
Orchestration. This is intended to enable integration content management cockpit of
compatibility of the corresponding content SAP Process Orchestration, customers can
versions of the integration suite and SAP Process connect to their tenant of SAP Cloud Platform
Orchestration. This content compatibility Integration Suite, select the relevant integration
allows customers to continue to leverage their flow, and deploy, run, and monitor it on the local
investments in SAP Process Orchestration while cloud integration runtime of the integration suite.
Figure 27: Content Reuse from SAP Cloud Platform Integration Suite
Cloud solutions from SAP Third-party cloud applications B2B, B2G
Cloud Integration capability of SAP® Cloud Platform Integration Suite
Common design time
Discover Design Run Monitor
Cloud
Content reuse
On premise
Model Design Run Monitor
Runtime of the Cloud Integration capability

of SAP Cloud Platform Integration Suite
Run Monitor
SAP applications Third-party applications B2B, B2G
51 / 82

SAP introduced product profiles to make sure cloud
integration content modeled in the workspace of the
integration suite is compatible with a specific release
of SAP Process Orchestration. A specific product
profile restricts the configuration of an integration
flow to the set of adapter types and integration flow
steps supported by a particular release and support
package stack of SAP Process Orchestration. Based
on the common cloud-based design time, including
the integration flow concept, SAP follows a common
modeling paradigm. This gives customers the
flexibility to decide where to deploy their integration
flows – in the cloud or on premise. This can, for
example, be useful in cases when the customer wants
to run some integration flows on premise during
migration phases and later deploy them in the cloud.
SAP Road Map Explorer

With SAP Road Map Explorer, customers can get
detailed insights into integration-related road map
items, which also cover the end-to-end processes of
intelligent enterprises: recruit to retire, lead to cash,
source to pay, and design to operate.
52 / 82

Data Integration
Modern landscapes are dominated by distributed • Data quality management (DQM) involves the
data assets, integration challenges, and data integration of data from multiple sources for
sprawl. This makes data integration a challenging cleansing, matching, or consolidation (central
task requiring some crucial capabilities. This business terms). Examples: Cleansing address
section addresses key data integration use cases data; embedding DQM services in apps to
and provides an overview of available products validate address data or enrich with geocodes.
and related guidance. The SAP product portfolio • Data orchestration involves pipeline-driven
offers a unique set of capabilities, suitable as data integration for disparate kinds of data,
well for diverse data processing and metadata which also supports distributed processing.
management. Example: Enabling data science and machine
learning across all enterprise data assets by
USE CASES integrating data across diverse landscapes.
• Data replication involves the table-based
integration of data, covering data replication, SOLUTIONS FOR ENTERPRISE INFORMATION
migration, and analytical use cases based on AND DATA MANAGEMENT
ETL/ELT. Example: Replication of data from Solutions for enterprise information and data
legacy applications or databases into SAP HANA management from SAP ease integration and
for migration, analytics, or Big Data. enable customers to derive value from their
• Data virtualization involves the provisioning data landscape by keeping overall efforts low.
of a virtual data layer by federation of queries The solutions are clustered into capabilities for
to remote data sources without physical data data integration, data management, and data
movement. Example: Lookup of shared master processing (see Figure 28), which are crucial for
data from various data sources for virtual data any sophisticated solution working with data.
access in SAP HANA to remote data sources.
Figure 28: Overview of Capabilities of SAP® Solutions
Data integration Data management Data processing
ETL Connectivity Application Data Data Data Pipelining Orchestration Big Data and
integration cataloging quality preparation machine learning
53 / 82

Data Integration today’s variety of different sources and data
Correctly accessing and moving data is essential formats, the data quality functions are necessary
for delivering high-quality data to a target system, to understand the overall quality of the data
API, storage, or end user. In the past, ETL tech- and to get insights about which data must be
nologies were used to establish point-to-point improved before it can be trusted for business
data movements, including transformation use. The next logical step is to use data
during the process. The ETL approach remains preparation capabilities to improve data quality
one key pillar for the data integration area to or to tailor data for a specific customer need.
safeguard existing customer investments and The “customer” here can be data-driven
to keep a solution for traditional data movement applications or analytical systems.
activities in place. Enhancing the scope of
accessing and moving data is key for adoption Data Processing
and requires a broad range of connectivity to With the amount of data that customers
diverse on-premise, cloud, and hybrid systems. have in their landscapes, pure point-to-point
The connectivity capabilities provided by SAP replication or ETL cannot always be the answer
software comprise a wide range of adapters, when it comes to distributing data to the right
connectors, and connections. They give customers places at the right time. Building data-driven
the opportunity to integrate deeply with the port- applications using a pipelining approach is key
folio of business software and services from SAP to getting massive data volumes processed.
and are based on the unique experience of our SAP software capabilities allow customers to
engineering teams. scale their data processing depending on the
workload and ensure that only relevant
Data Management information is exchanged between different
Companies produce tons of data in different applications. Data-driven applications also
formats every day. Understanding this data is require the remote orchestration of connected
a crucial aspect for building and operating data- systems, for example, to push down the
driven applications, enhancing existing customer processing to where the data is stored, or to
data movement scenarios, and getting a centralized remotely start a process as part of a data-driven
overview of the data assets. Our metadata application. To complement its data processing
management capabilities, which include data capabilities, SAP simplified the access to
cataloging, allow relevant information about any disparate sources and integrated core machine
data set to be stored in one central area. With learning (ML) functionality, which can be readily
used on top of the processing engine.
54 / 82

Products and Solutions
Solutions for enterprise information and data management from SAP include products that were
either organically built or added through acquisitions over the years. These products and solutions
are shown in Figure 29.
Figure 29: Portfolio Categories and Related Products
Data integration Data management Data processing
SAP® Landscape Transformation

SAP Information Steward SAP Data Services
Replication Server
SAP HANA® smart data SAP Data Quality Management, Data services of the Cloud
integration version for SAP solutions Integration capability of SAP Cloud
SAP Data Intelligence
• SAP HANA smart data integration, • SAP Landscape Transformation Replication

SAP HANA smart data access, and Server
SAP HANA smart data quality The SAP Landscape Transformation Replication
The smart data integration offering is a log-based, Server is a trigger-based real-time data replication
real-time data replication tool with transformation product with basic transformation capabilities.
capabilities. Its focus is to move data from Its focus is to move high volumes of data from
non-ABAP sources into SAP HANA. The smart ABAP and non-ABAP systems into SAP HANA
data access offering enables remote data to or any ABAP-based system.
be accessed as if it were stored in local tables • SAP Data Quality Management, version for
in SAP HANA, without copying the data into SAP solutions
SAP HANA. The smart data quality offering This software allows developers to embed
is a set of functionalities provided by several data cleansing and enrichment services into
components, which you can use to cleanse any business process or application using
and enrich data before it is persisted in the cloud-based microservices.
SAP HANA database. All offerings are part
of the SAP HANA platform.
55 / 82

• SAP Information Steward tools for batch data integration between on-
SAP Information Steward software provides data premise applications and cloud applications.
stewards and IT users with a single environment • SAP Data Intelligence
to discover, assess, define, monitor, and improve The SAP Data Intelligence solution is a
the quality of their enterprise data and metadata. comprehensive data management solution
• SAP Data Services that governs, integrates, processes, and orches-
SAP Data Services software is a product trates any volume, velocity, and variety of data
that empowers users to integrate, transform, in on-premise, cloud, multi-cloud, and hybrid
improve, and load accurate and complete data distributed system landscapes.
to support operational and analytical data-driven
initiatives. The product comes with a large These products are highly optimized for dedicated
number of different connectors that focus use cases and offer robust services in their
on third-party connectivity. respective area. Figure 30 illustrates the area
• Data services of the Cloud Integration of specialization of the different technologies.
capability of SAP Cloud Platform Integration
Suite (also known as CPI-DS)
The data services of the Cloud Integration
capability provide cloud-based data integration
Figure 30: Capabilities of Solutions for Enterprise Information and Data Management
ETL Connectivity Application Data Data Data Pipelining Orchestration Big Data and
integration cataloging quality preparation machine learning
SAP® Landscape Transformation

Replication Server
SAP Data Services
SAP HANA® smart data integration
Data services of the Cloud Integration

capability of SAP Cloud Platform
Integration Suite (CPI-DS)
SAP Information Steward
SAP Data Quality Management,

version for SAP solutions
56 / 82

SAP understands that the current situation SAP Data Intelligence is designed to streamline
leads to the following questions: the capabilities for data integration, data
• Which data integration tool should I choose governance, and data processing within one
for a certain scenario? product and address all deployment and
• How will this impact my landscape design landscape design challenges.
(cloud versus on-premise)?
• How will this influence the total cost of Table 6 summarizes the recommended technolo-
ownership? gies for the use case patterns introduced: data
replication (ETL), data virtualization, data quality
management, and data orchestration.
Table 6: Overview of Data Integration and Data Quality Products
Use case patterns
Data integration and Data replication Data Data quality Data

data quality products (ETL)6 virtualization management orchestration
SAP HANA® smart data integration,1

SAP HANA smart data access,1
SAP HANA smart data quality1
SAP® Data Services2
Data services of the Cloud Integration

capability of SAP Cloud Platform
Integration Suite (CPI-DS)3
SAP Landscape Transformation

Replication Server4
SAP Information Steward
SAP Data Intelligence5
1. Used to move data from non-ABAP® programming language sources into SAP HANA®
2. Used for moving data in the on-premise landscape with high transformation needs
3. Mainly used in cloud integration scenarios with an application context
4. Used to move high volumes of data from ABAP and non-ABAP systems into SAP HANA or any ABAP-based system
5. Recommended for any on-premise-to-cloud and cloud-to-cloud data integration need with options to reuse existing data integration products to orchestrate in a pipeline
6. This use case pattern also includes the integration style “bulk/batch (ETL).”
57 / 82

SAP DATA INTELLIGENCE renaming the product to SAP Data Intelligence.
In 2017, SAP released a new product called the SAP Data Intelligence is available as a fully man-
SAP Data Hub solution as a single solution for aged cloud service offering or as an on-premise
data integration, orchestration, and management, deployment.
leveraging open source and embedding machine
learning capabilities. Its focus was to deal with SAP Data Intelligence is designed to cover
Big Data and complex data orchestration across three key capabilities: data integration, data
distributed landscapes and processing engines, management, and data processing. It enables the
enhancing developer productivity and extracting end-to-end process of accessing data of different
value from distributed data in on-premise and types and varying quality from SAP S/4HANA,
cloud environments. SAP HANA services in the cloud, and cloud
solutions from SAP. SAP Data Intelligence enables
Based on customer feedback and the industry’s accessing data from storages from hyperscalers
general direction, SAP decided to extend the as well as legacy data sources, Web services,
scope of SAP Data Hub in two directions: first, SAP Cloud Platform Enterprise Messaging, and
to offer a fully managed cloud deployment of third-party messaging queues such as Kafka or
SAP Data Hub on SAP Cloud Platform, and second, MQTT. The holistic capabilities allow users to
to strengthen intelligent processing with capabilities prepare the data and process it in a scalable
to operationalize machine learning. This would environment. SAP Data Intelligence can transform
allow CIOs to scale and apply artificial intelligence disparate data into valuable data, at the right
company-wide with a manageable and predictable time, in the needed quality, and where it can fulfill
TCO. With the launch of these enhancements, SAP its purpose. Figure 31 shows a high-level overview
decided to highlight these evolutionary steps by of SAP Data Intelligence.
Figure 31: Overview of SAP Data Intelligence
SAP S/4HANA® Cloud Data management

SAP S/4HANA
SAP Fieldglass® solutions SAP® Data Warehouse Cloud
SAP Ariba® solutions SAP S/4HANA Cloud
SAP SuccessFactors® solutions SAP S/4HANA
SAP Concur® solutions Data Data Data SAP Analytics Cloud
cataloging quality preparation SAP Digital Boardroom
Access Prepare Process Deliver
Google Cloud Platform MQTT

Data integration Data processing
Apache Hadoop Apache Kafka
AWS APA and Web services
Apache Spark Legacy databases
Alibaba Cloud
Microsoft Azure
ETL Connectivity Application Pipelining Orchestration Big Data and
integration machine learning
58 / 82

SAP Data Intelligence supports the following use SAP Data Intelligence includes data movement
cases. capabilities based on proven SAP technologies
and open-source approaches.
Integrate and use business data: In many cases,
moving data is required and cannot be replaced
by remote orchestration and execution.
Figure 32: Use Case – Integrate and Use Business Data
SAP® Business Suite

SAP S/4HANA® AWS Alibaba Cloud
Microsoft Azure Apache Kafka
Access Deliver
SAP Data Intelligence Google Cloud Platform MQTT
Apache Hadoop
SAP S/4HANA Cloud
As illustrated in Figure 32, one of the primary use Integrate and process intelligent data:
cases of SAP Data Intelligence is to move data SAP Data Intelligence has embedded integration
from SAP Business Suite, SAP S/4HANA, and and processing capabilities. In addition to a wealth
SAP S/4HANA Cloud to data lakes or messaging of preconfigured content, the environment is
systems. open for customer-created development
artifacts, such as existing code snippets, to save
Manage and integrate complex data: Managing customer investments. For example, an already
and integrating all kinds of data sources and developed sentiment analysis algorithm, based
systems is a crucial task in any landscape on Python code from a customer legacy
strategy. SAP Data Intelligence was built to serve environment, can be packaged and executed
as one data management and integration tool within a process of SAP Data Intelligence.
for your environment to manage all your data
sources and systems. As illustrated in Figure 33, embedding proven
code and integration components in any
As illustrated in Figure 31 and Figure 32, language and combining it with new technologies
SAP Data Intelligence can be used as the central based on an open framework is a key value-add
platform to serve all data management and that SAP Data Intelligence can offer. This allows
integration needs, especially for products of the high flexibility for any data integration needs and
SAP HANA services in the cloud: business-related helps ensure the inclusion of future market
transactional systems such as SAP S/4HANA, trends and developments with minimal effort.
SAP S/4HANA Cloud, and customer systems;
and environments that are not from SAP.
59 / 82

Figure 33: Use Case – Intelligent Data Integration introduced by the cloud, the answer to how
and Processing and where to deploy data management and
Legacy integration tools becomes rather a question of
development the individual landscape design of an enterprise.
Java
The architectural design of SAP Data intelligence,
Java based on the Kubernetes container service,
R allows deployment within a hyperscaler’s own
data center infrastructure, or as a fully managed
R
SAP Data cloud service from SAP. Given this deployment
Intelligence
flexibility, customers can fit SAP Data Intelligence
into their landscape design as an overall data
Access Process
integration technology without losing core
JavaScript functionality due to landscape restrictions.
JavaScript Figure 34 highlights the main functionalities
of SAP Data Intelligence.
Traditional integration tools were installed in

close physical proximity of the on-premise
environments. With the changes and advantages
Figure 34: Overview of SAP Data Intelligence Capabilities
SAP® Data Intelligence
Access Prepare Process Deliver
Data governance
Data discovery | Data profiling | Metadata cataloging
Intelligent processing
Notebook | Content | ML deployment
Data orchestration and monitoring

Connection management | Workflows | Scheduling
Data pipelining
Data ingestion | Data processing | Data enrichment
60 / 82

Data Governance intelligent enterprises. They make data available
Data governance enables enterprise-wide to business and developers, helping achieve
metadata discovery and visibility. It provides metadata excellence and data-driven application
information about the individual systems and development. These features of SAP Data
the data within those systems, and thus makes Intelligence enable you to:
it possible to understand the entire landscape. • Extract value from distributed data and embrace
With SAP Data Intelligence, you can: the best of SAP and open technologies and tools
• Easily govern and manage metadata assets • Use ready-to-run ingestion and streaming
across enterprise systems capabilities to speed up your digital business
• Discover, understand, and consume transformation projects
information about data • Connect and reuse existing ETL products such
• Answer related information requests without as SAP Landscape Transformation Replication
browsing through multiple systems and Server, SAP Data Services, or SAP HANA smart
repositories or touching various data models data integration to save your investments and
• Define and run business rules to understand accelerate data adoption
the quality of your data • Effectively use your data with end-to-end data
• Leverage end-to-end self-service data landscape management
preparation capabilities
Data Pipelining
Intelligent Processing As a powerful modeling environment, SAP Data
The intelligent processing capabilities Intelligence enables you to build data-driven
of SAP Data Intelligence allow users to applications and integrate them as your move
operationalize and manage machine forward on your journey to becoming an intelligent
learning models and requirements. They can: enterprise. You can create complex, multistep,
• Use intelligent tooling for machine learning reusable data pipelines to leverage your digital
and data science in the context of transformation projects and orchestrate data
application scenarios integration processes. With the solution, you can:
• Process and operationalize existing ML models • Build data-driven pipelines and streams with a
• Automatically test and continuously retrain standardized modeling environment
models • Perform data transformations, data quality, and
• Provide insights into the performance of ML data preparation processes using a graphical
models with advanced reporting capabilities user interface
• Embed and productize scripts, programs, and
Data Orchestration and Monitoring algorithms of data scientists
Orchestration and extraction of value from data • Execute end-to-end data processes, starting
and processes from diverse sources support with the ingestion of data into the landscape
61 / 82

EXISTING CUSTOMER INVESTMENTS AND SAP CLOUD PLATFORM INTEGRATION SUITE
STRATEGY AND SAP DATA INTELLIGENCE
SAP understands that customers have made The Cloud Integration capability of
significant investments in solutions for enterprise SAP Cloud Platform Integration Suite and
information and data management from SAP and SAP Data Intelligence are complementary
strives to help them protect those investments. offerings that address two different integration
Existing solutions will be integrated with SAP Data styles. Based on typical usage scenarios and
Intelligence in the best way whenever it makes characteristics of both integration technologies,
sense from a business and technology standpoint, this section gives enterprise and integration
for example, to establish additional connectivity architects guidance on when to use which
to new target systems. integration technology. It also discusses how
to combine the technologies in an end-to-end
Tight integration between SAP Data Intelligence integration scenario.
and solutions for enterprise information and data
management from SAP allows the delivery of The Cloud Integration capability of the integration
new functions and enhances the feature scope suite addresses process integration and facilitates
in a unified way on a single platform. With this linking business processes that are distributed
approach, SAP can deliver innovations of across multiple applications within a hybrid
SAP Data Intelligence faster and customers can system landscape. As outlined in “Process
use them with their existing products. This hybrid Integration,” the Cloud Integration capability
approach, combining mainly existing on-premise supports A2A, B2B, and B2G integration use
enterprise information and data management cases. It uses a message-based processing
products and SAP Data Intelligence in the cloud, paradigm that allows the queuing, transforming,
establishes new opportunities for scalability, routing, and monitoring (including error handling)
connectivity, and flexibility. of exchanged business data on a message level.
A key requirement of this process integration
Prime cases for data replication and ETL are style is to guarantee the transactional integrity of
established within SAP Data Intelligence based an integration scenario by, for example, ensuring
on proven technologies. Functionality and reliable messaging capabilities. Furthermore, SAP
connectivity will be enhanced continuously until offers a broad range of prepackaged integration
SAP Data Intelligence is the only platform needed scenarios for the Cloud Integration capability.
for all data integration, data management, and
data processing activities within a customer’s In contrast, SAP Data Intelligence focuses on
landscape. This will include on-premise-to-cloud data integration, making it possible to share,
and cloud-to-cloud activities. In addition, SAP pipeline, govern, and orchestrate (mass) data in
will offer an embedded data intelligence concept, complex landscapes. It supports the expansion
which will be included in products such as the of traditional data warehousing by incorporating
SAP Data Warehouse Cloud solution, with a Big Data stores and the ingestion and processing
lightweight data integration framework for of IoT data. SAP Data Intelligence enables
inbound data movements. intelligent processing of data with capabilities to
62 / 82

operationalize machine learning, by modernizing As shown in Table 7, the integration technologies
data flows and leveraging new functionality and are complementary and can be used in combined
algorithms, including machine learning and scenarios. For example, transactional data can
image processing. Typically, data from enterprise be passed from the Cloud Integration capability
applications is accessed on the database level of the integration suite to SAP Data Intelligence.
(table, view)14 outside a transactional business This can, for example, be stored in data lakes and
context. The following table summarizes the key can be used to train ML algorithms. Conversely,
characteristics of both integration technologies. SAP Data Intelligence can integrate with the
Cloud Integration capability when a deep trans-
actional integration with enterprise applications
is required.
Table 7: Cloud Integration Capability and SAP Data Intelligence

SAP Cloud Platform Integration Suite
Objective Chaining distributed business processes in Pipelining and orchestrating diverse data
hybrid landscapes and business data in hybrid landscapes
Use cases • Application to application • Data integration (ETL and streaming,

• Business to business, business to among others) for scenarios such as
government building an intelligent data warehouse
• Master data integration • Data processing of complex data assets
• Data governance of hybrid landscapes
• Operationalization of data scenarios
(for example, machine learning)
Coupling to API focused (synchronous, asynchronous, Data focused (table, table views, storage,
application business events) technical events)
Integration Available for a broad range of integration Available as predefined templates for
content scenarios for SAP® applications (hybrid, operations and pipelines
cloud, partner, third party)
Specific capabilities • Message-based processing (monitoring, • Distributed data processing

alerting, error handling) • High-frequency event processing
• Transactional integrity (reliable messaging) • Advanced data transformations and
• Process-centric integration flows processing (for example, machine
learning, predictive, code)
• Data-centric integration flows
14. API-level access is also possible with SAP Data Intelligence, but it is not the key focus.
63 / 82

Analytics Integration
Tapping into the data generated by operational reporting, planning, and prediction. Example:
processes, data warehousing solutions The cross-product analytics front-runner –
such as SAP Data Warehouse Cloud and financial analytics dashboard for SAP Analytics
SAP BW/4HANA® as well as SAP Analytics Cloud Cloud – combines data from SAP S/4HANA,
provide a holistic platform to support an intelligent, SAP SuccessFactors solutions, the “lead-to-
data-driven enterprise. They offer business users cash” dashboard (sales operations), and
the capabilities to combine data from various SAP Digital Boardroom.
sources for standard reporting, real-time
business intelligence, planning, prediction, SAP ANALYTICS CLOUD
and application building. SAP Analytics Cloud combines augmented
business intelligence (BI), planning, and predic-
The two data warehousing solutions complement tion into one comprehensive analytics platform
each other in the so-called hybrid scenario, a (see Figure 35). Its key capabilities include:
native integration between SAP BW/4HANA • Augmented BI:
and SAP Data Warehouse Cloud. Furthermore, – Use standard reports based on templates,
SAP Data Warehouse Cloud and SAP Analytics flexible storytelling with drill-down and
Cloud are automatically integrated with each ad hoc capabilities, and geospatial analyses
other. All three solutions provide connectivity – Use cross-application analytics augmented
to SAP and third-party systems, both in the cloud by “smart features” such as natural-language
and on premise, to access data with or without processing (“search to insight”) or forecasting
replication. They are all open to be extended. In time series
addition, SAP Analytics Cloud offers an embedded • Sharing:
edition: a comprehensive set of APIs that allow – Combine prebuilt stories in SAP Digital
other applications, both SAP and third-party, to Boardroom
integrate analytical capabilities in their opera- – Intuitively find the most suitable report using
tional systems. the SAP Analytics Hub solution
• Responsive design: Build your visualizations
This section discusses the cloud solutions. It once and consume them on any device – from
then addresses how the continued on-premise mobile phones to video walls
solutions for analytics and data warehousing • Planning:
from SAP tie in with these cloud solutions. – Benefit from freely definable input schedules
and planning functions
USE CASES – Use simulation capabilities such as value
Two use cases are addressed: driver trees and private versions to support
• The embedded analytics use case provides planners by visualizing the impact of their
prebuilt application-specific analytics to assumptions
support real-time decision-making within a – Use collaboration and sharing as well as
business application. Example: A treasury calendar functionality to ensure alignment
executive dashboard is based on embedding among planners and transparency of the
SAP Analytics Cloud into SAP S/4HANA Cloud. entire planning process for managers
• The cross-application analytics use case • Prediction: Enable embedded machine learning
incorporates data from multiple business and predictive algorithms to support business
applications to facilitate cross-application users and data scientists
64 / 82

Figure 35: Architecture of SAP Analytics Cloud
Applications SAP® Digital Boardroom SAP Analytics Hub Mobile experience SAP App Center
BI Planning Predictive Application design Embedding

Analytic Discovery Events and workflows Smart assist Scripting Analytics into
applications
capabilities Charts and tables Allocation Creation and deployment Composites
Geospatial Value driver tree simulation of predictive models UI theme and style sheet
Core Data Administration

Wrangling Modeling Visualizations Collaboration Mobile APIs
capabilities connectivity auditing
Platform as
SAP Cloud Platform
a service
Cloud data sources On-premise data sources

and applications and applications
The close integration with SAP Data Warehouse R server: Data may thus be processed by
Cloud allows SAP Analytics Cloud to consume R scripts and R visualizations and may in turn
the information provided in the warehouse. In be integrated into UIs in SAP Analytics Cloud.
addition, SAP Analytics Cloud can tap into SAP
and third-party data sources, cloud or on-premise, Even more complex logic or custom widgets
live or replicated, depending on the use case. can be built on the same platform with
Data models may be loaded from more than SAP Analytics Cloud, analytics designer capability.
one source, for example, to combine data from With JavaScript-like code, application designers
regional systems in one model, and models may create stateful applications to extend the
may be linked in browser-based blending. Thus, functional reach of SAP Analytics Cloud. To
cross-application analytics are already supported speed up implementations, SAP Analytics Cloud
by a stand-alone SAP Analytics Cloud. More offers more than 100 predefined content packages
complex scenarios that include data harmonization, from SAP and SAP partners. These content
cleansing, and semantic alignment can be packages come at no extra charge. They consist
supported by adding SAP Data Warehouse of easy-to-adapt templates covering LoB and
Cloud. All these capabilities can be modeled in industry best practices. They are based on SAP
SAP Analytics Cloud intuitively with WYSIWYG and third-party data sources, covering major
design tools. Therefore, business users can create SAP products and featuring SAP Analytics Cloud
or enhance models and UIs in SAP Analytics capabilities. SAP Analytics Cloud content may
Cloud. For developers and data scientists, be based on SAP Data Warehouse Cloud.
SAP Analytics Cloud offers access to an However, most packages do not require
SAP Data Warehouse Cloud.
65 / 82

SAP DATA WAREHOUSE CLOUD maintaining the security, trust, and semantic
SAP Data Warehouse Cloud is an open, end-to- richness of your information. It enables IT to
end data management solution in the cloud govern data and the environment in real time so
(data warehouse as a service), designed for you can rely on trusted insight without delay.
both enterprise IT and LoB users (see Figure 36). Plus, it empowers business users to understand
SAP Data Warehouse Cloud is a business-ready and connect data independently, transform it
cloud data warehouse managed by SAP that into insights, and share information instantly –
unites relevant data sources in one solution, without manual processes or data duplication.
Figure 36: Overview of SAP Data Warehouse Cloud
SAP® Analytics Cloud
Consumption API third-party

Analytics Predictive Applications
consumption
Governance Data modeling Business modeling Repository Security

SAP Data
Business content
services services services services services
Warehouse
Cloud
SAP HANA® Cloud
In-memory Storage Disk
Data Third-party API third-party

ingestion data lake Virtual access Connectivity Replication data load
Data Sources from cloud

External cloud sources On-premise sources
sources solutions from SAP
A comprehensive approach to data warehousing for instant data to value
Although it is a cloud-native solution, broader insights, lowering your total cost of

SAP Data Warehouse Cloud works with your ownership and connecting all your relevant
existing on-premise systems, both SAP and data in one interface.
third party, and provides you with a simple and
cost-efficient way to embrace cloud computing. SAP Data Warehouse Cloud provides dedicated
You can use it to extend your existing warehouse virtual work environments known as “spaces” for
investments to the cloud. Its flexibility allows shared data, models, and objects. This supports
you to extend on-premise SAP, third-party, and better separation of LoB content per subject,
open-source technologies to the cloud in a hybrid department, or level of authorization; enhanced
environment. This lets you enhance models for governance and user administration; and
66 / 82

point-and-click access to corporate and external and ease of use of SAP Data Warehouse Cloud
data. Spaces make it possible for IT to provide make it an ideal solution for many enterprise
users in various groups with access to isolated scenarios, including hybrid data warehouse
virtual work environments while upholding the use cases, data marts, and cross-application
integrity of the central repository and models. warehousing. The hybrid scenario allows
Users in each group get the flexibility they need customers to leverage existing investments
while IT maintains centralized governance, data in SAP software for on-premise data warehousing
quality, and security. Data may be extracted or without the need to rebuild existing scenarios.
be used in a federated way without replication to Business users can enhance and extend the on-
spaces in SAP Data Warehouse Cloud. Cleansing premise models with new data sets (for example,
and mapping of data from various sources by external data-like benchmarks). They can
provides a consistent view of data. Copying of create and modify data models and share them
data is minimized with advanced virtualization, across the organization. In a secure and governed
centrally governed data access, and secure environment, decisions are based on a single
collaboration through role-based security. source of truth without involving IT at every turn.
Information from SAP Data Warehouse Cloud can
Built-in connectors include SAP solutions, files be consumed either by leveraging the integrated
in a data lake, and SQL databases. In addition, analytical capabilities of SAP Analytics Cloud or
third-party tools for data loading may be in third-party services and applications through
integrated through APIs. The rich functionality APIs.
Figure 37: Embedded Analytics and Enterprise Analytics
SAP® or third-party
SAP application SAP or third-party
applications
Cross-application
Planning or predictive
SAP Analytics Cloud SAP Analytics Cloud
Embedded analytics Enterprise analytics
ANALYTICS CLOUD DEPLOYMENT SCENARIOS: management and the creation of connections

ENTERPRISE AND EMBEDDED would be typical tasks, as well as model building
SAP Analytics Cloud supports two deployment and story design.
scenarios: enterprise and embedded (see
Figure 37). Besides an “enterprise” scenario, there is
SAP Analytics Cloud, embedded edition. The
In the “enterprise,” or stand-alone, scenario, embedded edition allows application developers
customers have full access to the UIs and to embed analytical capabilities into their appli-
functionalities of SAP Analytics Cloud as cations. Based on a suite of APIs, SAP Analytics
described above. In this scenario, user Cloud can be automatically provisioned,
67 / 82

configured for the needs of the embedding SAP Analytics Cloud, embedded edition,
application, and fully managed by the embedding will be automatically deployed as a functional
application during runtime (see SAP Analytics enhancement to the embedding applications
Cloud APIs). and consequently comes without additional
administration efforts or license fees for
As a result, applications such as SAP S/4HANA customers. The “enterprise” scenario, which
Cloud, SAP SuccessFactors solutions, and other requires an additional license, is ideally suited
cloud solutions from SAP can offer the rich for customers who wish to build cross-application
BI capabilities of SAP Analytics Cloud for analytics, planning, and prediction. These
their application-specific data. (See the blog deployment scenarios can coexist. Embedding
“Integrated Analytics: SAP Analytics Cloud SAP Analytics Cloud can also be offered by
Now Embedded in SAP S/4HANA Cloud.”) third-party applications. Partners may wish to
SAP Analytics Cloud, embedded edition, provides complement the solutions they develop and sell
access to the data of the embedding application by adding embedded analytics. Customers may
exclusively based on an automatically provided also embed SAP Analytics Cloud in their solutions.
live connection.15 Thus, the required real-time
response to data changes as well as reuse of the ON-PREMISE ANALYTICS WITH SAP BW/4HANA
application’s authorization concepts for secure SAP offers different data warehousing applica-
data access and personalization are built in. tions to support customer needs from different
perspectives, such as infrastructure-related
SAP Analytics Cloud is embedded in so-called questions (cloud or on-premise), matureness
iFrames. A reserved space of the application’s of offered services, and integration with SAP
UI will be filled with stories from SAP Analytics and third-party sources and consumers.
Cloud, thus preserving all features and functions
of SAP Analytics Cloud (for example, navigation With SAP BW/4HANA and the SAP Business
or slice and dice). Dedicated APIs allow the Warehouse (SAP BW) application, SAP has a
embedding application and the embedded long history in data warehousing and offers
edition of SAP Analytics Cloud to communicate stable and mature solutions at enterprise data
so that filter values may be passed and warehouse scale for on-premise installations.
navigation from analytical to operational tasks With SAP Data Warehouse Cloud, SAP now
can be enabled (“intent-based navigation”). offers a software-as-a-service managed data
warehouse solution running in the public cloud.
15. N
ot all use cases are supported by the live connection. For example, planning and prediction are not included. For more
information about the difference between live connection and importing data, see “Choosing a Live Connection or
Importing Data” in the SAP Help Portal.
68 / 82

With these offerings, our customers can decide The native hybrid integration between
based on their history with SAP solutions and SAP BW/4HANA and SAP Data Warehouse Cloud
their strategy concerning their cloud journey. allows for exposing BW models such as BW
They can choose SAP BW/4HANA as their analytic queries from SAP BW/4HANA to SAP Data
on-premise solution or SAP Data Warehouse Warehouse Cloud. It also supports a remote
Cloud to implement a cloud-based data data scenario where business users in SAP Data
warehouse strategy. Warehouse Cloud can reuse existing BW analytic
query metadata models with no need to rebuild
Even running both solutions in parallel is an any semantics already defined in SAP BW/4HANA.
architecture SAP proposes due to the fact that At the same time, users of SAP Data Warehouse
each solution lacks certain aspects the other Cloud can extend those exposed models with
solution offers. A prominent example is the their own data and semantics without changing
self-service aspect that targets the business user the original model in SAP BW/4HANA.
concerning data integration, data modeling, and
data visualization, which SAP Data Warehouse This allows IT to make sure that no data leaves the
Cloud does not yet deliver. SAP BW/4HANA company to be extracted into external applications.
might be installed as the strategic on-premise, IT can help ensure that all data handling – such
enterprise-grade, central data warehouse as data transformations, enhancing data models
solution in a company. However, applying with local department data, and combining data
SAP Data Warehouse adds required self-service from SAP and third-party sources – is performed
functionalities. These allow business users in a secure, governed environment in
to work with data models served from SAP Data Warehouse Cloud.
SAP BW/4HANA and exposed securely
to the business departments space in
SAP Data Warehouse Cloud.
The native hybrid integration between SAP BW/4HANA

and SAP Data Warehouse Cloud allows for exposing BW
models such as BW analytic queries from SAP BW/4HANA
to SAP Data Warehouse Cloud.
69 / 82

UX Integration – Deployment Options
The SAP Fiori UX is the leading UX design system accessing SAP Fiori apps. One important aspect
for SAP applications. It provides a harmonized of a harmonized UX is a central point of access
UX and navigation across on-premise and for users to SAP and third-party business
cloud solutions. It includes intuitive access to applications. SAP Fiori launchpad offers such
applications, tasks, and notifications using single a central entry point16 (see Figure 38).
sign-on. In addition, SAP offers development
tools and technologies for implementing and
Figure 38: Launchpad as Central Access Point
SAP® SuccessFactors® solution

Other SAP
and third-party
products
SAP S/4HANA® Cloud SAP Cloud Platform
SAP S/4HANA SAP Business Suite
USE CASES DEPLOYMENT OPTIONS FOR SAP FIORI UX

Below you will find a general overview of and While the SAP Fiori design system becomes broadly
options for implementing SAP Fiori UX – in adopted across the SAP solution portfolio, there
particular SAP Fiori launchpad. Focus is on are still product-specific implementations that
one main use case pattern of “UX Integration,” use different UI technologies and deployment
limited to its deployment options. It examines options. They help ensure efficient and secure
the different deployment options for SAP Fiori UX data provisioning to business apps and their UI
and the launchpad. The use case also discusses elements. All options integrate the UI layer with
the underlying architecture that provides data the business logic and platform services.
to the user interfaces built with SAPUI5 and
SAP Fiori UX.
heck either of the following links for a detailed description of SAP Fiori launchpad: https://experience.sap.com/fiori or
16. C
www.sap.com/products/fiori.html.
70 / 82

The standard SAP Fiori apps and related UI Data Provisioning Options
components are typically deployed “embedded” To retrieve the necessary data for SAP Fiori apps
within the respective SAP system, for example, from the back end, you have different options:
SAP S/4HANA or SAP S/4HANA Cloud. For • SAP Gateway technology (on premise)
SAP Business Suite landscapes, you can set up deployed embedded or as a hub17
a dedicated SAP Fiori front-end server (hub) to • SAP Cloud Platform OData Provisioning
keep the UI components in a central place and service (Neo environment or Cloud Foundry
separate from the back-end release cycle. environment)18
SAP Cloud Platform offers tools and services When SAP Fiori apps are deployed on premise,
for you to integrate and extend SAP solutions the UI components are installed on the SAP Fiori
and to develop your own custom applications front-end server as a hub or as an embedded
with SAPUI5 and SAP Fiori UX. These applications deployment within the system. SAP Gateway
can be deployed and run either in the cloud or on technology on the front-end server handles
your on-premise SAP system. OData service calls to access business data on
the back end.
Each SAP product comes with its own local home
page or launchpad, providing users access to On SAP Cloud Platform, customers can run,
system-specific applications and services. On extend, and develop SAP Fiori apps in the cloud
top of this, you may establish a common point while connecting to on-premise systems through
of access across systems (cloud and on-premise), the cloud connector. In this case, OData requests
leveraging the launchpad running on SAP Cloud can then be handled either by SAP Gateway (in
Platform, Cloud Foundry environment, and related the same way as for the on-premise setup) or
services for a single sign-on and tasks in-box. For by the SAP Cloud Platform OData Provisioning
detailed information about the different options, service (see Figure 39).
refer to SAP Fiori Deployment Options and
System Landscape Recommendations.
SAP Cloud Platform offers tools and services for

you to integrate and extend SAP solutions and to
develop your own custom applications with
SAPUI5 and SAP Fiori UX.
or deployment options of SAP Gateway technology, see the blog “SAP Gateway Deployment Options in a Nutshell.”
17. F
18. h
ttps://blogs.sap.com/2019/02/24/sap-cloud-platform-environment-cloud-foundry-vs-neo.
71 / 82

Figure 39: Data Provisioning Options for Hybrid Scenarios
SAP Fiori® launchpad

OData
Custom apps and extensions service
API management
SAP Cloud Platform Cloud Integration capability of

Data source
OData Provisioning SAP Cloud Platform Integration Suite
Cloud
Cloud connector
On premise
SAP Gateway SAP Gateway
Enablement for Enablement for Enablement for

SAP Gateway SAP Gateway SAP Gateway
SAP system Third party
Back end: Back end:
SAP S/4HANA® or SAP Business Suite or SAP Business Suite
SAP Business Suite SAP S/4HANA
Gateway Gateway SAP Cloud Cloud Integration capability of

embedded hub Platform OData SAP Cloud Platform Integration Suite
Provisioning
General recommendations include the following. • When the customer needs to develop and run
SAP Fiori apps in the cloud reusing existing
Embed SAP Gateway: back-end investments
• When the deployments are completely
on premise Use the SAP Cloud Platform OData Provisioning
• When the customer does not need to provision service (SAP Cloud Platform, Neo environment):
data from multiple back-end systems • When the deployments need to have SAP Fiori
apps in the cloud
Use SAP Gateway as a hub: • When the customer needs to develop and run
• When the deployments are either on premise SAP Fiori apps in the cloud to reduce total
or have SAP Fiori apps in the cloud cost of ownership (TCO) when compared to
• When the customer needs to provision data SAP Gateway (by eliminating the need for a
from one or more back-end systems hub system on premise)
• When the customer needs to provision data
from one or more back-end systems
72 / 82

Use the SAP Cloud Platform OData Provisioning service to connect any kind of data sources
service (SAP Cloud Platform, Cloud Foundry from an on-premise system (whether SAP
environment): or third party) or from the cloud. For further
• When the deployments need to have SAP Fiori information, refer to the SAP Help Portal site
apps in the cloud for SAP Gateway technology and SAP Cloud
• When the customer needs to develop and run Platform OData Provisioning.
SAP Fiori apps in the cloud to reduce TCO when
compared to SAP Gateway (by eliminating the The considerations, recommendations, and
need for a hub system on premise) restrictions concerning embedded or hub
• When the customer needs to provision data deployment are pretty much the same for the
from multiple back-end systems SAP Fiori front-end server in pure on-premise
• When the data must be provisioned from scenarios and the SAP Gateway technology
SAP Business Suite or SAP S/4HANA systems in hybrid scenarios. For that reason, they are
(available for OData – v2 and v4 – and planned summarized in Table 8. You can find detailed
for plain REST calls) information in SAP Fiori Deployment Options
and System Landscape Recommendations.
If not all data sources are based on OData, the
Cloud Integration capability of SAP Cloud
Platform Integration Suite is the recommended
If not all data sources are based on OData, the

Cloud Integration capability of SAP Cloud Platform
Integration Suite is the recommended service
to connect any kind of data sources from an
on-premise system or from the cloud.
73 / 82

Table 8: Differences Between Deployment Options
Hub Embedded
Central configuration, but complex for lifecycle Multiple configurations, administration

Administration
and upgrade operations
High-availability concept required In line with high-availability concept of

Availability
embedding systems
Central Support for central functionalities, such as Need for an additional approach, as central
functionalities in-box and search functionalities are not directly supported in an
embedded deployment
Content Support for composition scenarios, potentially Limited content scope per system
complex
Requirement that hub version be in sync with Possibility to deploy appropriate version per
Interoperability
back ends back end
Separate systems required, performance Reuse of existing landscape, local access to

Landscape
impact in globally distributed environments content of the SAP Fiori® user experience and
apps to improve performance
Ownership of hub and content possibly Ownership of system probably in one hand
Ownership
distributed
Roles and Decoupled from back end In one place

authorization
Scalability Dedicated resources for UI requests Possible necessity to resize entire back end
Decoupled from back ends Potential risk in Internet scenarios when

Security
coupling with back ends
For restrictions compared to a full on-premise server for SAP Gateway, refer to
SAP Note 1830712 (S-user required).
74 / 82

End-to-End Integration Monitoring
Reliable integration plays a central role, especially To maintain reliable operations at the application
in hybrid landscapes that contain software-as-a- level, the different integration fragments of
service (SaaS) cloud services, managed cloud the components involved must be monitored.
components, and on-premise components. For performance, throughput, and backlog
As a solution provider, SAP aims to deliver fully considerations, the appropriate statistical
integrated solutions instead of single services metrics must be calculated. To detect critical
that must be integrated by customers, who may integration situations, exceptions need to be
incur implementation and maintenance costs as considered for every single component involved.
a result. One central application should monitor data,
exchanged through orchestrated and
SAP makes sure data exchange processes nonorchestrated interfaces, for all customer
operate reliably between the different solution landscape types as well as for all customer sizes.
components involved. This is relevant for cloud, For that reason, SAP offers customers a flexible
on-premise, and especially hybrid scenarios. delivery model of the central operations platform
The purely technical connectivity between the to support deployments as a private cloud or
different components is a prerequisite but is through SaaS. This approach lets customers
by far not sufficient to ensure a reliable data realize their preferred deployment environment
exchange. (see Figure 40).
Figure 40: Different Deployment Models for Integration Monitoring
SAP Solution Manager SAP Focused Run SAP Cloud ALM

available for hybrid available for hybrid available for hybrid
customer solutions customer solutions customer solutions
7.2 2.0
Focused
Build
+
SAP Solution SAP Focused SAP Cloud
Manager Run ALM
Focused
Insights
• Fully integrated ALM suite for • Operations platform for service • Fully integrated application
on-premise-centric midsize and providers and high-end hybrid lifecycle management (ALM) suite
larger customers customers for cloud-centric small, midsize,
• Customers who are satisfied with • Customers with advanced needs and larger customers
the currently provided functional that go beyond SAP Solution • Customers who are requesting a
scope Manager and SAP Cloud ALM standardized cloud-based
operation platform
75 / 82

SAP SOLUTION MANAGER AND of communications in hybrid landscapes is
SAP FOCUSED RUN supported. Exceptions can be collected from
In SAP Solution Manager 7.2, SAP provides different most of the cloud solutions from SAP, including
integration monitoring capabilities. They include SAP Cloud Platform, SAP Ariba solutions,
monitoring of SAP Process Orchestration (with SAP SuccessFactors solutions, and the
special focus on the SAP Process Integration SAP Sales Cloud solution. Target groups for
offering), message flow monitoring for orches- integration monitoring as part of SAP Solution
trated integration, and interface and connection Manager 7.2 are customers with large on-premise
monitoring for direct communication. and hybrid deployments as well as customers
of the “classic” SAP Solution Manager software.
The goal of centrally monitoring SAP Process
Orchestration is to provide central monitoring The SAP Focused Run solution19 is a spin-off of
for multiple integration domains. The scope SAP Solution Manager 7.2 and concentrates on
of the functionality covers component-specific the specific need for high-volume monitoring,
self-checks and availability checks, process alerts, root cause analysis, and analytics use
integration channel status checks, and cases for IT operations. Part of SAP Focused Run
component-specific monitoring based on is advanced integration monitoring, which helps
aggregated message data. Message search customers manage complex and integrated
capabilities as well as message alerting landscapes with millions of interface calls and
complement this functionality. message flows (see Figure 41). It covers the
monitoring and alerting of single message flows,
Through message flow monitoring for processed by SAP Process Orchestration or
SAP Process Orchestration, message fragments SAP Cloud Platform Integration Suite. It also
collected from different components of SAP supports peer-to-peer interface technologies,
Process Orchestration can be assembled in such as IDocs, Web service, and RFC on a single
so-called message flow instances. To do this, execution level.
specific integration model information based on
the integration visibility component is utilized. An advanced integration monitoring cockpit can
Direct communications can be monitored with be started from the launchpad for SAP Focused
interface and connection monitoring. This Run. Its entry and overview screens are similar to
supports monitoring exceptions, response times, those in SAP Solution Manager. In SAP Focused
and utilization at statistical levels. Alerts can be Run, however, a deeper drill-down functionality all
generated when certain thresholds are reached. the way to the level of single process messages is
Besides monitoring direct communication possible.
between on-premise components, monitoring
ore information on SAP Focused Run can be found at https://support.sap.com/en/solution-manager/focused-solutions

19. M
/focused-run.html.
76 / 82

Figure 41: Integration and Cloud Monitoring – Part of Advanced Integration Monitoring
The entry point to advanced integration monitor- SAP CLOUD ALM

ing can be single managed objects, for example, So far, SAP had provided SAP Focused Run for
systems or cloud services, or, alternatively, customers as an on-premise product. As a result
integration scenarios. Based on the fact that of the increasing importance for customers of
integration fragments are collected on the most the SAP Cloud portfolio, the solution is now also
detailed level, the different integration artifacts provided as an SaaS offering running with
can be correlated to end-to-end message flows SAP Cloud Platform.
and messages can be tracked throughout the
landscape. Target groups for the SAP Cloud ALM solution20
are small and midsize customers, cloud-only
In addition, you can handle integration exceptions customers, and cloud-first customers. (Cloud-
related to cloud solutions from SAP, such as first customers have a hybrid landscape and
SAP Cloud Platform, SAP Ariba solutions, prefer to run their application operations
SAP SuccessFactors solutions, and SAP Fieldglass® platform in the cloud.) It is delivered as part of
solutions. The service provides instant visibility SAP Enterprise Support services and the cloud
of the capabilities of the integration suite. solution subscription. SAP Cloud ALM addresses
the specific needs of cloud-centric SAP customers
Target groups for advanced integration monitoring who run most of their IT infrastructure in the cloud.
as part of SAP Focused Run are service providers, Visit SAP Cloud ALM for more details.
very large customers, and any customers who
need to monitor, create alerts, and track on a
single interface or message level.
ee https://news.sap.com/2018/09/sap-cloud-alm-tailored-application-lifecycle-management.
20. S
77 / 82

Automated Integration Configuration
Setting up the technical configuration for context in a standardized way. These scenarios
integrating cloud solutions with other cloud or are executed from a single execution engine,
on-premise solutions is often a complex process. which is available as a cloud service that plugs
This section describes the Cloud Integration into all the components involved. The approach
Automation service. It simplifies the integration provides a consistent user experience and
of different solutions by automating the steps a central entry point for the configuration
involved in setting up the technical configuration of integration scenarios delivered by SAP.
in the customer landscape. The integration scenario content as well as
the execution are aligned with other central
CHALLENGE integration planning services. In the Cloud
Usually, the integration of two or more solutions Integration Automation service, a structured,
means far more than setting up a directional or tailored, customized description of the customer-
bidirectional connection between two applications. specific configuration steps is intended to
Multiple tenants must be configured and set up, facilitate and standardize the integration
and integration scope heavily depends on the configuration processes. It is also intended that,
customer’s requirements and business processes. for integration scenarios enabled for the service,21
large parts of the setup will run automatically.
Without the Cloud Integration Automation service,
the process of setting up such an integration In this context, “customized” means that every
is often a manual, nonstandardized process description will point to the actual end points
involving scattered documentation and several within the customer’s on-premise and cloud
experts for the different solutions. These experts software landscape. Hyperlinks and other
must align closely to execute the appropriate configuration values derived from the customer
configuration steps in the corresponding landscape can be used throughout the
components. Otherwise, permissions may integration process.
be missing, configuration settings may be
incompatible, and performance of similar steps The Cloud Integration Automation service runs
may result in redundant effort. Without the on SAP Cloud Platform and is populated by the
Cloud Integration Automation service, the integration configurations of the various cloud
overall process is time-consuming, with very little solutions from SAP. Enhancements are planned
automation of such configuration tasks available. to facilitate future extensibility and options for
third-party contributions. Figure 42 shows the
SIMPLIFYING THE PROCESS WITH two services that make up the Cloud Integration
INTEGRATION AUTOMATION Automation service on the customer side.
SAP offers a central service that is used by
SAP solutions to define and automate integration
scenarios, for example, in the intelligent enterprise
21. F
or integration scenarios that are technically possible but not fully enabled for the service, only documentation will be offered.
78 / 82

Figure 42: Two Central Services to Automate Technical Configurations
Execution
Maintenance planner service provider
A planning solution that enables customers An execution engine that

to select the required components for an consumes the plan and guides you
integration scenario based on their existing through a mostly automated setup
landscape information
Plan the integration scenario Execute the integration setup

of choice within your landscape. in a highly automated manner.
From the customer point of view: personalized workflow is created. This workflow
• The maintenance planner service is available consists of all steps that were defined as part of
to all customers with an SAP support contract. the integration scenario by SAP. Individual users
The maintenance planner (or alternative tools are assigned to certain integration roles (for
that call the service) allows users to select an example “integration administrator”), which
integration scenario for the automation process. group tasks by responsibility. The workflow
The process will have access to the configuration service provides an overview of the overall
content and to information about the customer’s progress and guides users through the workflow
system landscape as well as to cloud tenants. step by step. For steps that can be executed
In this way, the generic information for an automatically, the user will have a button to
integration scenario will be combined with trigger the automatic execution of the step.
the available customer-specific configuration The technical configuration of the integration
data, such as system IDs. scenario is complete when all steps of the
• The execution service provider offers a workflow have been processed. Plug-and-play
customer-specific integration workflow that functionality may not be possible due to some
helps set up the configuration for their integration constraints, notably security standards.
scenarios. It guides customers through the Nevertheless, the personalized workflow,
workflow that was created based on the results including automated configuration steps, helps
of the maintenance planner and enables an to accelerate the process of setting up the
automatic integration setup. technical configuration of integration scenarios.
The maintenance planner guides you through Further information on the Cloud Integration
the planning phase with wizard-like dialogs. Once Automation service, including supported
the scenario and systems have been defined, a scenarios, can be found on SAP Help Portal.
79 / 82

Integration of SAP S/4HANA
As our next-generation Intelligent ERP, for synchronous communication, such as direct
SAP S/4HANA is an integrated ERP system business object manipulation (CRUD operations:
running on SAP HANA, available in the cloud and create, read, update, delete). SOAP APIs for
on premise. SAP is committed to providing inte- asynchronous message-based communication
gration content as well as integration artifacts are the cloud-based alternative to IDocs (for
to facilitate third-party integration. To enable example, for A2A and B2B scenarios). Business
customers and partners innovating with SAP events are used to notify interested parties about
products, SAP offers integration packages, significant status changes of underlying business
including digital contents for SAP S/4HANA objects. Traditional technologies, such as IDocs
on SAP API Business Hub. and BAPIs (from the BAPI® programming interface),
can be used in select cases through the cloud
connector of the SAP Cloud Platform Connectivity
Figure 43: Integration of SAP S/4HANA
service. They can also be used directly over the
new WebSocket–based RFC protocol to integrate
SAP S/4HANA Cloud with on-premise SAP
SAP S/4HANA® solutions. The preferred integration solution
Cloud solutions
Cloud
Third-party is SAP Cloud Platform Integration Suite.
from SAP cloud
The on-premise version of SAP S/4HANA supports

mostly integration that was originally released
with SAP ERP Central Component (SAP ECC).
This simplifies the integration of SAP S/4HANA
with existing landscapes, such as SAP ECC. APIs
for the on-premise version of SAP S/4HANA are
SAP S/4HANA
largely compatible with those for SAP ECC. Only
On-premise software Third-party
from SAP on premise APIs that are the target of simplification or
those which have become incompatible due to
SAP S/4HANA publishes APIs and business events simplification will be disabled for external use.
that enable customers to build integrations with Areas subject to simplification in SAP S/4HANA
third-party solutions and to build apps and are listed in the simplification item catalog.
extensions on SAP Cloud Platform.22 It is planned The preferred integration solution is either SAP
that additional APIs and business events will be Cloud Platform Integration Suite or SAP Process
published for SAP S/4HANA and SAP S/4HANA Orchestration. The criteria for choosing the
Cloud. Further information is available on right one is laid out in “The Cloud Integration
SAP API Business Hub. Capability and SAP Process Orchestration.”
API integration artifacts for SAP S/4HANA Cloud For detailed information on the transition to
are generally OData- or SOAP-based APIs and SAP S/4HANA, feel free to check out the paper
business events. OData APIs are recommended “Mapping Your Journey to SAP S/4HANA.”
22. A
first set of APIs and business events for SAP S/4HANA is now available on SAP API Business Hub. For more information,
see “ANNOUNCEMENT: Publication of SAP S/4HANA APIs on API Business Hub.”
80 / 82

Outlook and Finding Out More
This document provides a deep dive into the most important integration patterns, including
SAP technology recommendations. Updates of this guide about concrete technologies,
methodologies, and approaches are planned. Additional documents marking the next steps
in SAP’s integration strategy may also be provided. In the meantime, the following resources
provide more detailed information about the topics covered.
FIND OUT MORE • SAP Analytics Cloud

• SAP Integration Solution Advisory • SAP API Business Hub
Methodology • SAP S/4HANA Cloud
• SAP Cloud Platform Integration Suite • Custom Extensions in SAP S/4HANA
• SAP Cloud Platform (documentation) Implementations – A Practical Guide for
• SAP Cloud Platform Integration Suite, Cloud Senior IT Leadership
Integration capability (documentation) • Mapping Your Journey to SAP S/4HANA –
• SAP Process Orchestration A Practical Guide for Senior IT Leadership
• SAP Cloud Platform Integration Suite, • SAP Cloud Platform Integration Suite,
API Management capability (documentation) Integration Advisor capability
• SAP Application Interface Framework (documentation)
• SAP Cloud Platform Master Data Integration • SAP Cloud Platform Integration:
• SAP Cloud Platform Enterprise Messaging The Comprehensive Guide; J. Mutumba Bilay,
(documentation) P. Gutsche, M. Krimmel, and V. Stiehl;
• SAP Cloud Platform Integration Suite, Open SAP Press, 2018.
Connectors capability (documentation) • Modeling guide for SAP HANA smart data
• The Cloud Connector of SAP Cloud Platform integration and SAP HANA smart data quality
Connectivity • Maintenance planner
• SAP Cloud Platform Extension Suite • Extending SAP S/4HANA; Herzig, Heitkötter,
• SAP Ariba Cloud Integration Gateway Wozniak, Agarwal, and Wust; SAP Press, 2018.
• SAP Data Intelligence • SAP Road Map Explorer
• SAP Data Warehouse Cloud • Best Practices for Enterprise APIs
81 / 82

List of Abbreviations
A2A . . . . . . . . . . . Application to application
API. . . . . . . . . . . . Application programming interface
AS2. . . . . . . . . . . . Applicability Statement 2
ASC X12 . . . . . . . ANSI ASC X12 (American National
Standards Institute Accredited
Standards Committee)
B2B . . . . . . . . . . . Business to business
B2G . . . . . . . . . . . Business to government
CIO. . . . . . . . . . . . Chief information officer
cXML. . . . . . . . . . Commerce eXtensible Markup
Language
EANCOM. . . . . . . European Article Number
Communication
EDI. . . . . . . . . . . . Electronic data interchange
GUSI. . . . . . . . . . . Global upstream supply initiative
HTTP. . . . . . . . . . Hypertext transfer protocol
IDoc. . . . . . . . . . . Intermediate document
IPaaS. . . . . . . . . . Integration platform as a service
IoT . . . . . . . . . . . . Internet of Things
OAGIS . . . . . . . . . Open Application Group Integration
Specification
OData . . . . . . . . . Open Data Protocol
PIDX. . . . . . . . . . . Petroleum Industry Data Exchange
REST . . . . . . . . . . Representational state transfer
RFC. . . . . . . . . . . . Remote function call
SAP ECC. . . . . . . SAP ERP Central Component or
SAP Business Suite
SOAP. . . . . . . . . . Simple Object Access Protocol
SOCKS5 . . . . . . . Socket Secure (protocol)
UX. . . . . . . . . . . . . User experience
UN/EDIFACT. . . United Nations/Electronic Data
Interchange for Administration,
Commerce, and Transport
xCBL . . . . . . . . . . XML Common Business Library
82 / 82

Follow us
www.sap.com/contactsap
Studio SAP | 72377enUS (20/12)
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.
In particular, SAP SE or its affiliated companies have no obligation to

pursue any course of business outlined in this document or any related
presentation, or to develop or release any functionality mentioned therein.
This document, or any related presentation, and SAP SE’s or its affiliated
companies’ strategy and possible future developments, products, and/or
platforms, directions, and functionality are all subject to change and
may be changed by SAP SE or its affiliated companies at any time for
any reason without notice. The information in this document is not a
commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks
and uncertainties that could cause actual results to differ materially from
expectations. Readers are cautioned not to place undue reliance on these
forward-looking statements, and they should not be relied upon in making
purchasing decisions.
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.
See www.sap.com/copyright for additional trademark information

and notices.

Integration Architecture Guide For Cloud and Hybrid Landscapes PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integration Architecture Guide For Cloud and Hybrid Landscapes PDF

Uploaded by

Copyright:

Available Formats

Integration Architecture Guide for Cloud and

3 Intelligent Enterprises Are

17 SAP Integration Solution

80 Integration of SAP S/4HANA

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

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

Integration has become the key enabler for

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

Customer Manufacturing Finance and Human

And multiple sub processes

APPLICATIONS INTELLIGENT SUITE PARTNER SOLUTIONS THIRD-PARTY SOLUTIONS

SUITE QUALITIES OPENNESS

SEAMLESS CONSISTENT ALIGNED EMBEDDED AND ONE COORDINATED E2E

SAP BUSINESS TECHNOLOGY PLATFORM integration

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

More Fully managed

SAP Process Orchestration Cloud Connector Data integration tools (EIM)

INTEGRATION SUITE on-premise process and data integration platforms,

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

Services Use cases

Cloud Integration End-to-end process integrations (A2A), AI-accelerated business-to-business

Integration Advisor AI-based mapping proposals to accelerate onboarding of trading partners

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

Core Capabilities of SAP® Cloud Former Name

Cloud Integration capability SAP Cloud Platform Integration service

API Management capability SAP Cloud Platform API Management service

Integration Advisor capability SAP Cloud Platform Integration Advisor service

Open Connectors capability SAP Cloud Platform Open Connectors service

INTEGRATION METHODOLOGY integration challenges and provides guidance

SAP Integration Solution Advisory

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

Figure 3: Content Overview – Key Integration Building Blocks

Out-of-the-box Open Holistic AI-driven

SAP® Integration Solution Advisory Methodology

Integration styles and technologies

API-managed integration | Event-based integration

Setup and operations

Integration monitoring Integration automation

Integration deployment models

Multi-cloud Private cloud On premise Embedded

This document is made up of the following • “SAP Integration Solution Advisory

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

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

Third-party integration Apps, extensions Master data management

SAP Cloud Platform

SAP’s integrated intelligent suite SAP One

SAP Cloud Platform Master Data Integration

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

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

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

SAP S/4HANA® You can inspect the currently available models

The CDS format is also used in SAP HANA®,

Various solutions, such as SAP S/4HANA,

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

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

side-by-side API that exposes a unified domain

SAP Graph is an API for accessing SAP-managed

(domain entities, such as Products and Sales SAP business systems

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

Figure 9: Overview – SAP Integration Solution Advisory Methodology

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

Assess Your Integration Strategy

Figure 10: Integration Domains

3 Intelligent Enterprises Are

17 SAP Integration Solution

80 Integration of SAP S/4HANA

• Electronic Invoicing Electronic Invoicing

5. “List of Abbreviations” can be found at the end of the document.