Week 4: Application, Business, & e-Government Integration

Unit 1: Design Enterprise-Grade Integration Scenarios

Design enterprise-grade integration scenarios
Importance of enterprise-grade integration flows

▪ A poorly designed integration flow can lead to errors

▪ Integration flows share tenant resources that can
indirectly affect one another
▪ Avoid the risk of introducing non-functional flaws into
your integration flow
▪ Building enterprise-grade integration flows helps to
maintain overall business process availability
▪ Ensures robust integration flows for safeguarding
mission-critical processes

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

Design enterprise-grade integration scenarios
Qualities of enterprise-grade integration flows

▪ High availability
▪ Resilience
▪ Resource management
▪ Loose coupling
▪ Handling failures gracefully
▪ Readability
▪ Reusability

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

Design enterprise-grade integration scenarios
Design guidelines

Guidelines to design enterprise-grade integration flows

▪ Covering different areas such as applying the highest security
standards, handling errors, scripting, etc.
▪ Application-specific guidelines (SAP SuccessFactors, API
Management)
▪ Reference integration flows @Business Accelerator Hub or
directly in Cloud Integration to be deployed with minimum effort
▪ See guidelines in the documentation

Guidelines to implement specific integration patterns

▪ Most common enterprise integration patterns such as content-
based routing, aggregator, splitter, etc.
▪ Exactly-once scenarios
▪ See blog series

Enterprise integration pattern community

▪ 60+ enterprise integration patterns implemented with Cloud
Integration
▪ Overview blog
Huge and active community
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Design enterprise-grade integration scenarios
Design integration flows for quality of service exactly once

Cloud Integration supports message ID mapping

and message duplicate checks as flow steps in
modeling
▪ Message ID mapping is necessary whenever the
sender and receiver require different formats or
unique IDs have to be generated for each message
in a split or multicast scenario
▪ The idempotent process call supports scenarios
where the receiver isn’t idempotent or where
redundant processing may lead to side effects

Blog Post

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

Design enterprise-grade integration scenarios
Asynchronous decoupling

▪ To ensure reliability we can now decouple the sender

and flows using the message queues (JMS) or data
store
▪ Use the storage i.e. JMS or data store to persist the
message at the beginning of the processing
sequence
▪ The subsequent processing steps are executed
asynchronously
▪ This ensures that the dependencies are loosened
and a retry mechanism is also implemented
▪ The new data store sender adapter achieves
asynchronous decoupling through data store
▪ Message queues (JMS) is recommended over data
store for asynchronous decoupling with retry pattern

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

Design enterprise-grade integration scenarios
Reusability with script collection artifact

▪ A script collection is a bundle of scripts

▪ It can contain supported script
resources like Groovy Script,
JavaScript and Jars (archives) files
▪ Referenced by different integration
flows within the same or different
packages
▪ Avoid incompatible changes to an
existing function of the referenced script
resources
▪ See General Scripting Guidelines, for
general guidelines
▪ As of now, there is no auto-deployment
of referenced script collections
Blog Post

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

Design enterprise-grade integration scenarios
Reusability with message mapping artifact

▪ Now, you can create message mapping

as a dedicated artifact
▪ Referenced by different integration flows
within the same or different packages
▪ Dynamically assign message mapping
artifacts using a header or property, or
via a partner directory
▪ Avoid incompatible changes to the
referenced message mapping artifact
▪ As of now, there is no auto-deployment
of referenced message mappings

Blog Post

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

Design enterprise-grade integration scenarios
Adapters with retry

Why a retry?
▪ Connections to external endpoints and even whole integration scenarios can fail due to temporary issues.
▪ Some senders cannot retry the message.
▪ A direct retry on the Cloud Integration side could solve the problem.

Re-delivery to external targets, no re-processing of the integration flow

▪ XI receiver adapter (configurable for delivery assurance Exactly Once (EO))
▪ Kafka receiver adapter (configurable)
▪ SFSF receiver adapter (5 retries with 3 min. pause between each retry)

Re-processing of the integration flow

▪ XI sender adapter (configurable for delivery assurance EO / At Least Once (ALO))
▪ AS2 / AS2 MDN sender adapter (configurable for delivery assurance EO)
▪ AS4 sender adapter (configurable for delivery assurance EO / ALO)
▪ All polling sender adapters (SFTP / FTP / Mail / Ariba / SuccessFactors)
▪ All sender adapters connected to a broker (JMS, AMQP, Kafka) and data store (Data Store sender adapter)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Design enterprise-grade integration scenarios
Demo

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

Design enterprise-grade integration scenarios
Summary

▪ Ensure enterprise-grade robust integration flows

for safeguarding mission-critical processes
▪ Cloud Integration supports message ID mapping
and message duplicate checks
▪ You can asynchronously decouple your integration
scenario using the message queues (JMS) or data
store
▪ Use script collection and message mapping
artifacts for better reusability and ease of
maintenance
▪ Many adapters provide retry, which helps you with
temporary connectivity issues
▪ Regularly refer to the design guidelines

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

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
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/trademark for additional trademark information and notices.
Week 4: Application, Business, & e-Government Integration
Unit 2: Simplify Non-SAP Connectivity
Simplify non-SAP connectivity
Accelerate business outcomes with simplified integration

The Cloud Integration capability of SAP Integration Suite is an

enterprise-grade integration platform that simplifies and
accelerates integration of data, processes, applications, and On-Premise
business networks to help companies achieve faster business Cloud Apps Apps
A2A
outcomes as they journey to becoming an intelligent enterprise.
Holistic
Benefits Integration
▪ Versatile integration platform covering all integration styles and patterns
▪ Fully SAP-managed, multi-cloud integration platform Open
▪ Strong focus on security and infrastructure availability Integration

B2G
B2B
▪ Large ecosystem with partner-developed integration content & adapters
▪ Compatible with SAP Process Orchestration Out-of-the-Box Public
Business Integration Authorities
Key capabilities Partners
AI-Driven
▪ Prebuilt integration content Integration
▪ Rich set of connectivity adapters for SAP to SAP and SAP to third-party
applications integration, both in the cloud or on-premise
▪ Extend out-of-the-box integrations to address custom requirements MDI

▪ Simplify integration process modeling with the power of AI Focus of Social Business
▪ Access platform OData APIs for easy extensions this unit Networks Networks

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

Simplify non-SAP connectivity
Comprehensive set of connectivity options

250+ adapters to accelerate integration development Adapters built by partners

Technical adapters Additional non-SAP applications Example list
▪ HTTP, HTTPS (incl. REST), SOAP connectors ▪ iShare
▪ FTP(S), SFTP
▪ Cloud storage ▪ Kafka
▪ Mail (SMTP, IMAP, POP3)
▪ Collaboration ▪ MQTT
▪ OData V2 & V4
▪ CRM ▪ Office 365
▪ IDoc, RFC, XI
▪ eCommerce ▪ SharePoint
▪ AMQP, JMS, AS2, AS4
▪ ERP
▪ Kafka, RabbitMQ Full list of adapters by partners in
▪ JDBC, Data Store, LDAP ▪ eSignature SAP Business Accelerator Hub
▪ HCM
Application adapters ▪ Field services
▪ Ariba, MDI, SuccessFactors ▪ Finance Adapter development kit
▪ AWS (S3, SQS, SNS, SWF) ▪ Help desk
▪ Salesforce, MS Dynamics, MS Azure ▪ Framework to create new adapters
▪ Messaging ▪ Use any IDE of your choice
Storage (Blob, File, Queue, Table), MS
SharePoint ▪ Payments
▪ Dropbox, ServiceNow, Workday, ▪ Social
Slack, Splunk ▪ …
▪ Twitter, Facebook, SugarCRM Full list of adapters by SAP in
▪ Elster SAP product documentation

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

Simplify non-SAP connectivity
Consume integration adapters from SAP Business Accelerator Hub

Simplified consumption in
SAP Integration Suite
▪ Explore adapters from the Discover
view of Cloud Integration
▪ Select the adapter in Flow Designer for
import and deployment

SAP Business Accelerator Hub

▪ Adapters published by OEM partners
in SAP Business Accelerator Hub after
following an SAP internal governance
process
▪ Dedicated category for adapters
▪ Prebuilt integration content available
for many adapters

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

Simplify non-SAP connectivity
Demo

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

Simplify non-SAP connectivity
Summary

SAP Integration Suite offers seamless integration

of SAP and non-SAP applications, both in the
cloud or on-premise through ...
▪ A rich set of connectivity adapters
▪ Prebuilt integration content

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

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
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/trademark for additional trademark information and notices.
Week 4: Application, Business, & e-Government Integration
Unit 3: Monitor and Operate Integration Scenarios
Monitor and operate integration scenarios
Monitoring tools for Cloud Integration
Centralized Monitoring and Alerting
using SAP Cloud ALM

Archiving Data External Logging

Monitoring Tools
for Cloud Integration
Standard Monitoring
Dashboard OData APIs

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

Monitor and operate integration scenarios
Standard monitoring dashboard

Monitors for integration content and message monitoring

Access to different available monitors
▪ Monitor Message Processing
▪ Manage Integration Content
▪ Manage Security
▪ Manage Stores
▪ Access Logs
▪ Manage Locks

Help Portal

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

Monitor and operate integration scenarios
Standard monitoring dashboard – Enhanced filtering options

Standard filter options:

▪ Time, Status, Artifact
▪ IDs, incl. business-related Application
Message ID set via a Content Modifier step

Additional filter criteria

▪ Fields to be set via a Content Modifier step:
− Sender, Receiver, Custom Status, etc.
− Value help available
▪ Field to be set via Script step:
− Custom header properties
(name-value pair)
− Store business or payload-related
information in the message processing log

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

Monitor and operate integration scenarios
Archiving data

▪ Archiving data enables customers to persist data from Cloud

Integration to an external content management system (CMS)
▪ To address legal obligations of retaining data for extended
durations
▪ The external archiving system must support the CMIS API
standard version 1.1
▪ Monitor data archiving progress using the Monitoring OData API
▪ You can archive data for persist step content, adapter
payloads, and attachments
▪ The system job also records specific key performance
indicators (KPIs) of the archiving runs

Help Portal

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

Monitor and operate integration scenarios
Centralized monitoring and alerting using SAP Cloud ALM

▪ End-to-end monitoring of integration scenarios

bringing the technical message flow closer to the
business context
− Correlation of messages to an end-to-end message path
− Reporting of failed messages and deployment
exceptions
− Tracking messages based on business attributes
▪ Technical health tracking of Cloud Integration tenants
− Exhaustion of JMS resources
− Validity of certificates and key pairs
▪ Alerting with a possibility to collaborate in a team
during troubleshooting
▪ Personal email notifications
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Blog Post | Expert Portal 6
Monitor and operate integration scenarios
External logging

▪ External logging allows customers to send

message processing logs to an external system,
regardless of database storage availability
▪ It enables pushing Cloud Integration logs to
external customer-owned persistence solutions.
▪ Internal and external log levels can be set
independently
▪ To activate external logging on your tenant
− Set up Splunk as your external logging
destination
− You need to be Tenant Admin with the
role ExternalLogging.Activate
− Use the activateExternalLogging function
of the official OData API

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC Help Portal 7
Monitor and operate integration scenarios
OData APIs on SAP Business Accelerator Hub

SAP Business Accelerator Hub contains an

OData API package for Cloud Integration.
It enables you to trigger the following
actions:
▪ Manage and query integration artifacts
▪ Access HTTP and trace log files*
▪ Get the details of the messages processed
▪ Access message store entries and JMS
resources
▪ Manage the partner directory content
▪ Access and manage security artifacts

* Only available on Neo Environment

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
Monitor and operate integration scenarios
Applying DevOps with SAP Integration Suite

▪ Automation of integration operations is possible

using the OData APIs for Cloud Integration and
API Management available on SAP Business
Accelerator Hub
▪ Ready-to-use pipelines for Jenkins-Git
infrastructure (SAP Business Accelerator Hub
integration recipes GitHub community)
▪ Project “Piper” contains multiple library steps for
integration operations which can be used in
CI/CD pipelines
▪ SAP Continuous Integration and Delivery, a Low-
Code/No-Code service on SAP BTP, provides a
predefined pipeline for SAP Integration Suite

Blog Post

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

Monitor and operate integration scenarios
Applying DevOps with SAP Integration Suite – “Piper”

▪ SAP provides tooling for CI/CD via “Piper” for easier automation of your processes
▪ Cloud Integration and API Management capabilities of SAP Integration Suite offer many “Piper” steps,
leveraging the underlying OData APIs

Blog Post

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

Monitor and operate integration scenarios
Delayed software update in Cloud Integration capability of SAP Integration Suite

▪ Production tenant updates and increments can be

delayed by a week through a self-service option
▪ Effectively mitigates regression risk for custom
integration flows
▪ Delay the software update in the production tenant
and consume the regular update in the test tenant
▪ Applicable for Cloud Integration runtime only
▪ The delay is applicable only for the monthly
increments
▪ The About dialog in the tenant displays the cloud
integration runtime version, facilitating easy
comparison of versions across test and production
tenants Navigate to the Profile Button (top-right corner) > Click About to see
the Cloud Integration Runtime version

Help Portal | Blog Post *Available with SAP Integration Suite, standard and premium editions, additional instances, and SAP CPEA
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11
Monitor and operate integration scenarios
Demo

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

Monitor and operate integration scenarios
Summary

▪ SAP offers multiple possibilities for monitoring Cloud

Integration artifacts

▪ External logging enables pushing Cloud Integration logs

to external customer-owned persistence solutions
▪ Using our pipeline scripts you can start your DevOps
journey for SAP Integration Suite today
▪ Also, try out project “Piper” for easier automation of your
processes
▪ Production tenant updates and increments can be
delayed by a week through a self-service option

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

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
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/trademark for additional trademark information and notices.
Week 4: Application, Business, & e-Government Integration
Unit 4: Generate Business Partner Interfaces
Generate business partner interfaces
Challenges of B2B integrations

▪ Complexity
▪ Standardization
▪ Security
▪ Partner Management
▪ Scalability
▪ Cost

Casanova
Biotech UN/EDIFACT ISO X12 GS1
GmbH

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

Generate business partner interfaces
Standards and customization

Influencing factors
Industries
Example Customization means
answering a lot of further
An IDoc purchase order has questions, such as:
▪ 720 data elements
Which elements are
▪ 60 code lists with 4,000–5,000 required?
code values Products and services

▪ <5% of these data elements, code What is the exact

lists, and code values are required meaning?
per implementation
What are the constraints
▪ But which one? and conditions of this
element? Countries and laws

Are the occurrences

correct? Is this element
mandatory?

Typical view of an IDoc interface

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
 Generate business partner interfaces
Project phases and costs

+
Business domain experts Integration experts

Message
Business Mapping Technical Testing and
Implementation Deployment
requirements Guidelines implementation correction
Guidelines
Tools

Cloud Cloud
Integration Integration
Effort

4 days 1 day 2 days 1 day

Media breaks

All durations are examples and can differ from company to company
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Generate business partner interfaces
Integration Advisor main components

Library of Type Message Implementation Mapping Artifacts

Systems Guidelines (MIGs) Guidelines (MAGs)
Deployable
Library of Functional specification Specification of a scripts and
predefined/ describing the (source or mapping between a schemas and
standardized target) structure of the source and target documentation
reusable data customized interface MIG
types

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

Generate business partner interfaces
Message Implementation Guidelines

Message Implementation
Guideline (MIGs)
▪ Interface structure
▪ Documentation editor
▪ Generated through
proposal
▪ Refined by customer

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

Generate business partner interfaces
Mapping Guidelines

Mapping Guidelines
(MAGs)
▪ Mapping between 2 MIGs
▪ Confidence indication
▪ Generated through
proposal
▪ Refined by customer

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

Generate business partner interfaces
Integration Advisor architecture

Editor

Capabilities for business partner MIG

interfaces and mappings Propose

▪ Machine learning MAG

Source Target
▪ Crowdsource-based learnings MIG MIG
Knowledge
Graph
▪ Automatic generation
Runtime Artifacts +
Contribute
Documentation

Documentation

Cloud SAP Process

Integration Orchestration

This functionality is unique in the market and protected by various patents held by SAP
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
 Generate business partner interfaces
Project phases with SAP Integration Suite

+
Business domain experts Integration experts

Message
Business Mapping Technical Testing and
Implementation Deployment
requirements Guidelines implementation correction
Guidelines
Tools

Integration Cloud Integration Cloud

Advisor Integration Advisor Integration
Effort

1 day 1/2 day 1 day 1/2 day

Media breaks

All durations are examples and can differ from company to company
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Generate business partner interfaces
Demo

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

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
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/trademark for additional trademark information and notices.
Week 4: Application, Business, & e-Government Integration
Unit 5: Manage Trading Partner Configurations
Manage trading partner configurations
Challenges in the standard approach

▪ Development effort
▪ Maintenance effort
▪ Complex issue solving

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

Manage trading partner configurations
SAP Integration Suite capabilities for B2B
Integration Advisor
Editor
Interface Specification
Propose
Integration Advisor (IA) Mapping Specification
Source Target Knowledge
▪ Standardized access to B2B and SAP libraries Interface Interface Graph
▪ Definition and documentation of interfaces and
Runtime Artefacts
mappings Contribute

▪ Intelligent and crowd-sourced proposal service

Editor Trading Partner Management
Trading Partner Management (TPM)
▪ Creation and maintenance of B2B trading partners
▪ Creation and maintenance of B2B scenarios Trading partner
profiles and
▪ Push B2B scenario configuration to partner directory agreements
B2B Scenario
Cloud Integration
Trading Partner Agreement
▪ Stores configuration in partner directory
▪ Processes B2B transactions with an SAP delivered flow
Monitoring
B2B Monitoring Partner
B2B transaction XM
YM
Directory
▪ Monitors the B2B transactions at runtime in conjunction Generic Integration Flow B2B transaction XM
YM
XM
with trading partner agreement data B2B transaction YM
Cloud Integration B2B Monitoring
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Manage trading partner configurations
Entities of Trading Partner Management

Company Profile

Trading Partner Profiles

Agreement Templates
TPA Template
Predefined B2B Scenario
Agreements
TPA
Agreed B2B Scenario

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

Manage trading partner configurations
Trading Partner profiles

Company overview and related details for B2B scenarios

▪ Company partner profile for tenant owner company Company Profile
▪ Trading partner profile for all companies with whom the owner company
does B2B
Company overview information
▪ Address
▪ Contact person(s)
▪ Business context
B2B scenario-related details
Trading Partner Profiles
▪ Identifiers used in B2B interchanges for identifying sender and receiver
▪ Business system access information
▪ Communication parameters
▪ Certificates
▪ Supported document standards (type systems) and versions
▪ Interchange and envelope handling configuration
▪ Number range configuration
▪ Used Message Implementation Guidelines (MIGs)
▪ General reusable parameters
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Manage trading partner configurations
Trading partner agreement template

Tenant owner company view of trading partner agreement

▪ Defines the required choreography of interchanges
▪ Required order of which interchange will be sent or should be
received
▪ Based on one and two-way business transactions
▪ Considers owner company’s system and communication
configuration derived from company partner profile TPA Template
Predefined B2B Scenario
▪ Refers to relevant own MIGs

Template for creation of trading partner agreements with

trading partners

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

Manage trading partner configurations
Trading partner agreements

Company Partner Profile Trading Partner Profiles

▪ Based on TPA template
▪ Agreed choreography (B2B scenario) Mediate/
– Initiating and responding business system Agree

– List of business transactions

– Involved IA artifacts
TPA Template
– Interchange handling Predefined B2B Scenario

– Quality of services
▪ Used to generate the relevant runtime and
monitoring artifacts which will be pushed to the
partner directory

TPA
Agreed B2B Scenario

Trading Partner
Agreement
(TPA)
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Manage trading partner configurations
Demo

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

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
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/trademark for additional trademark information and notices.
Week 4: Application, Business, & e-Government Integration
Unit 6: Monitor Business Partner Integrations
Monitor business partner integrations
Challenges in monitoring B2B scenarios

▪ Data Volume
▪ Multiple Systems
▪ Network Connectivity
▪ Data Integrity
▪ Timeliness

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

Monitor business partner integrations
Filtering in B2B monitor

Extensive filtering enables fast drilldown to searched interchanges

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

Monitor business partner integrations
Multi-level interchange drilldown

First level: B2B details

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

Monitor business partner integrations
Multi-level interchange drilldown

Second level:
technical details

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

Monitor business partner integrations
Validation in the monitor

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

Monitor business partner integrations
Acknowledgment status in the monitor

▪ Can be enabled per trading partner agreement

▪ Visualized in the monitor

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

Monitor business partner integrations
Demo

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

Thank you.
Contact information:

open@sap.com
Follow all of SAP

www.sap.com/contactsap

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
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/trademark for additional trademark information and notices.