openSAP_btp4_Week_11_2025_All_Slides.pdf

Week 1: Overview of B2B in SAP Integration Suite
Unit 1: Introducing the Basic Concepts

2
PUBLIC
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ
Introducing the basic concepts
Learning objectives of this course
In this course, you will learn about the B2B capabilities of
SAP Trading Partner Management and Integration Advisor
▪ Week 1: Overview of B2B in SAP Integration Suite
▪ Week 2: Set Up and Configure an End-to-End Scenario
▪ Week 3: How to Operate and Maintain the B2B Integrations
This week:
▪ Introducing the basic concepts
▪ Trading Partner Management overview
▪ Integration Advisor overview
▪ Using Cloud Integration and Monitoring for B2B
integrations
▪ Course scenario for the coming weeks
▪ SAP Integration Suite roadmap for B2B

3
PUBLIC
Why do you need a B2B middleware?
SAP
Ariba
SAP
S/4HANA
Cloud
SAP
Concur
UN/
EDIFACT
SAP
ERP
ASC
X12
OAGIS
Third-Party
Application
Proprietary
WSDL
CSV
SAP
S/4HANA
Cloud
Variety of communications and B2B content

4
PUBLIC
What are the key issues to be solved by a B2B middleware?
Digital transformation means that a company wants to electronically exchange business documents with all
their trading partners. But:
A company has many trading partners
Many different kinds of business documents to
be exchanged
▪ e.g. purchase order, invoice, dispatch advice, etc.
10 or more per trading partner is usual
Different B2B standard required by each trading partner
▪ e.g. ASC X12, UN/EDIFACT, GS1XML, Tradacomms, UBL,
OAGI, Rosettanet, defactostandard (IDoc, SOAP),
▪ custom …
Every trading partner has its own
configuration and requirements per
business document
Different communication protocols used by each trading
partner
▪ e.g. AS2, AS4, STFP, OFTP, etc.
Every trading partner has its own
communication addresses, parameters,
and certificates
Complexity
1,000 trading partners or more is usual

5
PUBLIC
Integration Advisor and Trading Partner Management at a glance
Editor
Trading Partner Agreement
Trading Partner Management
B2B Scenario
Trading partner
profiles and
agreements
Integration Advisor
Knowledge
Graph
Editor
Propose
Contribute
Interface Specification
Mapping Specification
Runtime Artifacts
Source
Interface
Target
Interface
B2B Monitoring
Partner
Directory Generic Integration Flow
Monitoring
B2B transaction YM
XM
B2B transaction YM
XM
B2B transaction YM
XM
SAP Cloud Integration
Integration Advisor (IA)
▪ Functional specifications of interfaces and mappings
▪ Central documentation of B2B and SAP libraries
▪ Intelligent and crowd-sourced proposal service
Trading Partner Management (TPM)
▪ Creation and maintenance of B2B scenarios
▪ Consideration of individual aspects and requirements
per trading partner
▪ Push B2B scenario configuration to partner directory
▪ Stores configuration in partner directory
▪ Processes B2B transactions with one integration flow
B2B Monitoring
▪ Monitors the B2B transactions at runtime in alignment
with the trading partner agreement data

6
PUBLIC
Demo of B2B capabilities at a glance in SAP Integration Suite

7
PUBLIC
Key takeaways
▪ The B2B capabilities of SAP Integration Suite support
the efficient connection of all trading partners as well
as the efficient implementation of transformation rules
and mappings for quick and easy exchange of the
individually agreed requirements of the business
documents.
▪ Focus on a business-user-driven, low-code approach
(from specification/guideline to runtime artifacts),
making it easier for business analysts and non-
technical users to actively participate in the integration
process.
▪ Optimized operational effort through dynamic
integration
Further reading
▪ B2B in SAP Integration Suite

Thank you.
Contact information:
open@sap.com

© 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.
www.sap.com/contactsap
Follow all of SAP

Unit 2: Trading Partner Management Overview

2
PUBLIC
One-stop shop
▪ Simplified B2B integration scenario
management with multiple trading partners
▪ Crowd-sourced content
▪ Lift and shift scenarios in transformation
projects to the cloud
Trading Partner Management overview
What is the role and aim of Trading Partner Management
Onboarding of trading partners –
leveraging SAP Integration Suite
capabilities
▪ Accelerated onboarding of trading
partners
▪ Trading partner-specific interface and
mappings design from Integration Advisor
▪ Optimized operational effort through
dynamic integration
▪ Monitoring of integrations with business
partners
▪ Archiving

3
PUBLIC
▪ All parameters of own
company for the B2B
scenario
− Identifier
− Connected systems
− Kind of communication
Building blocks of Trading Partner Management
Company Profiles
Trading Partner
Profiles (TPPs)
Trading Partner
Agreement
Templates
Trading Partner
Agreements (TPA)
▪ All parameters of the
trading partner for the B2B
scenario
− Identifier
− Connected systems
− Kind of communication
▪ B2B scenario for
company
▪ Basis for the trading
partner agreement
▪ Complete the B2B scenario
▪ Include interchange +
mapping guidelines

4
PUBLIC
B2B scenario – Key concepts
Trading Partner
System
Interchange B2B
Format
Interchange B2B
Format System
Purchase
Order
Processing
Purchase
Order
Processing
ASC X12
850
SOAP Receiver SAP S/4HANA SOAP
Order Confirmation Confirmation
ASC X12
855
AS2 Sender
Invoice
Processing
Invoice
Processing
SOAP Receiver
SAP S/4HANA SOAP
Invoice 810 → Invoice
ASC X12
810
AS2 Sender
Outbound
Delivery
Processing
Outbound
Delivery
Processing
SOAP Receiver
SAP S/4HANA SOAP
Advanced Shipping
Notification
856 → Advance
Ship Notice
ASC X12
856
AS2 Sender
SAP S/4HANA SOAP
Order
Communication Mapping Communication
Company
Outbound
interchange
Inbound
interchange
[ Purchase Order Request ]
[ Purchase Order Response ]
[ Invoice Exchange ]
[ Deliverey Notification ]
SOAP Sender AS2 Receiver

5
PUBLIC
Same B2B scenarios with
multiple trading partners.
1) SFTP is in the roadmap for TPM
Use of B2B scenario with trading partners
Company Trading Partners
SAP S/4HANA
SOAP API ASC X12
UN/
EDIFACT
Purchase
Order
PO Create
(via SOAP sender)
850
(via AS2)
ORDERS
(via SFTP1))
ORDERS.
ORDERS05
(via IDOC)
Order Confirmation
(via SOAP receiver)
ORDRSP
(via SFTP1))
ORDRSP.
ORDERS05
(via IDOC)
Invoice
(via SOAP receiver)
DESADV.
DESADV01
(via IDOC)
Outbound
delivery
Advanced Shipping
Notification
(via SOAP receiver)
DESADV
(via SFTP1))
INVOIC.
INVOIC02
(via IDOC)
SAP
Integration
Suite
(Cloud
Integration)
Trading
Partner
Systems
B2B System
SAP S/4HANA
On Prem
Procurement
SAP IDoc
or
855
(via AS2)
810
(via AS2)
856
(via AS2)
Value Added
Network
INVOIC
(via SFTP1))
or
Invoice

6
PUBLIC
Company/trading partner profile
Trading Partners
Identifiers:
▪ 1000404 (SAP S/4HANA
SOAP API)
▪ X12-404 (X12)
System:
B2B System
System: Value Added
Network
System: SAP S/4HANA
On Prem Procurement
System
SAP S/4HANA Cloud
Company
Identifiers:
▪ 1710 (SAP S/4HANA
SOAP API)
▪ X12_1710 (X12)
Identifiers:
▪ 1000705 (SAP S/4HANA
SOAP API)
▪ XYZ32322 (UN/EDIFACT)
Identifiers:
▪ 1000123 (SAP S/4HANA
SOAP API)
▪ AB-233432 (IDoc)
Company BestRun US
Trading Partner
BlackBelt Inc.
Trading Partner
Euro Distributor SE
Trading Partner
Wholesales UK Inc.
Interchange B2B format:
SAP S/4HANA SOAP API,
Version: 1809
ASC X12,
Version: 4010
UN/EDIFACT,
Version: D01.B
IDoc,
Version: 2009
Integration
Suite
(Cloud
Integration)

7
PUBLIC
Agreement template
▪ Company’s stable side of a B2B
scenario
▪ Basis for trading partner
agreements
▪ Configuration from company
profile
− Identifiers,
− System,
− Communication, and
− Interchange B2B format
▪ Refers to company’s MIGs (IA)
System
B2B System
SAP S/4HANA SOAP API,
Version: 1809
Communication: SOAP
Company
Identifiers:
▪ 1710 (SAP S/4HANA
SOAP API)
▪ X12_1710 (X12)
Trading Partner
BestRun US
Purchase
Order
Outbound
delivery
Invoice
PO Create
(via SOAP sender)
Order Confirmation
(via SOAP receiver)
Invoice
(via SOAP receiver)
Advanced Shipping
Notification
(via SOAP receiver)
SAP S/4HANA
SOAP API
Company MIGs
Integration Advisor
BestRun PO Create
BestRun Order
Confirmation
BestRun Invoice
BestRun Advance
Ship Notice

8
PUBLIC
Trading partner agreement
Purchase
Order
PO Create
(via SOAP sender)
Order Confirmation
(via SOAP receiver)
SAP S/4HANA
SOAP API
Trading Partner MIGs
Integration Advisor
TulliusGrocery ORDERS
TulliusGrocery ORDRSP
Trading Partners
UN/EDIFACT
ORDERS
(via AS2 receiver)
ORDRSP
(via AS2 sender)
B2B System
Agreement Template
Mapping: PO Create → ORDERS
Mapping: Order Confirmation → ORDRSP
MAGs
BestRun PO Create →
TulliusGrocery ORDERS
TulliusGrocery → BestRun
Order Confirmation
Mapping
System: B2B System
Identifiers:
▪ 1000705 (SAP S/4HANA
SOAP API)
▪ XYZ32322 (UN/EDIFACT)
Trading Partner
Tullius Grocery
Communication: AS2
UN/EDIFACT,
Version: D01.B
Trading
Partner
Systems

9
PUBLIC
Key takeaways
▪ Business user-oriented design-time tool
▪ Accelerated onboarding of trading partners via
reusable configurations
▪ Simplified B2B scenario creation via
pattern/template-based approach
▪ Referenced crowd-source content from Integration
Advisor
▪ Enriched data monitoring for operations and support

Unit 3: Integration Advisor Overview

2
PUBLIC
Runtime Artifacts
Integration
Knowledge
Graph
Propose
Contribute
Integration Advisor overview
The role and aim of Integration Advisor
▪ No coding just functional specifications (guidelines)
▪ Machine learning
− Proposals to start your integration projects
− Central integration knowledge base (crowd-source-based)
▪ Automatic generation of documentation and runtime
artifacts
▪ Community collaboration
Integration Advisor
Editor
Source
Interface
Target
Interface

3
PUBLIC
The main components
▪ Library of
− B2B standards
− A2A interfaces
(de facto standards)
Type System
Custom
Messages
Message
Implementation
Guidelines (MIGs)
Mapping
Guidelines
(MAGs)
Runtime Artifacts
▪ Library of
proprietary schemas
and interfaces
▪ Customized
interfaces of
− Customer’s
requirements, or
− Trading partner’s
requirements
▪ Reusable in trading
partner agreements
(TPAs)
▪ Basis for mapping
guidelines (MAGs)
▪ Mapping between
customer and
trading partner
MIGs
▪ Part of partner
agreement
− Agreement (TPA)
- Direction
− Individual
customizations
▪ Basis for runtime
artifacts
▪ Generated schemes
(XSD) and
transformation scripts
(XSLTs) for
− Syntax conversion
− Payload validation
− Pre/post-processing
− Mapping
▪ Pushed to partner
directory

4
PUBLIC
Message Implementation Guideline
Proposal
Properties
Codelists
Qualifier
Allowed code values
Editor – Key Features I
▪ Proposal of frequently used nodes
▪ Customization (tailoring) via selection
of nodes/codes
▪ Semantic qualification and qualified
duplicates
▪ Provisioning and link to codelists and details
▪ Picture string (patterns) for date, dateTime,
etc.

5
PUBLIC
Simulation
Business Rule
Review status
Editor – Key Features I
▪ Focus on documentation
▪ Semantic qualification and qualified
duplicates
▪ Business rules and integrity
conditions (assertions)
▪ Review status
▪ Provisioning of all required properties
of nodes
▪ Embedded simulation

6
PUBLIC
Editor – Key Features II
▪ Overview
▪ Compare several MIGs
▪ Migrate to other type system versions
Migrate
Compare
Overview
Migrate

7
PUBLIC
Editor – Key Features II
▪ Export of
− MIGs en masse
− Documentation
(PDF, Word, Excel)
− Example files
− Schemas
▪ Import of
− MIGs en masse or single
− Codelists
PDF Export
Example payload
Russian Doll XSD Export
(for precise validation)

8
PUBLIC
Mapping Guideline editor – Key features I
Functions
Simulate
Condition
Date transformation
Qualified duplicates
Proposed mapping elements
▪ Proposal of mapping elements,
mapping functions, code value
mappings
▪ Consideration of qualified nodes
and duplicates
▪ Embedded
− Mapping semantic rules
− Code value mapping
− String processing
▪ Mapping functions(Xpath 2.0)
▪ Embedded simulation

9
PUBLIC
Mapping Guideline editor – Key features II
Overview
Shared code
Global code value mapping
Documentation
▪ Overview
▪ Substitution of source and target MIGs
▪ History
▪ Mass update of MIGs in MAGs
▪ Export of
− Documentation (PDF, Word, Excel)
− Runtime artifacts (XSDs, XSLTs)
− Sample files
▪ Import of
− MAGs en masse or single

10
PUBLIC
Key takeaways
▪ Significantly reduce the time for creating/maintaining
integration content in all phases, from functional
specification to deployment
▪ Higher consistency of integration content with the in-
built content management features
▪ Reusable artifacts for consumers like TPM/Cloud
Integration
▪ Get rid of silo working with the help of crowd-sourced
content

Unit 4: Using Cloud Integration and Monitoring for
B2B Integrations

2
PUBLIC
Cloud Integration
▪ Processes B2B transactions with one integration
flow
B2B Monitoring
▪ Monitors the B2B transactions at runtime in
alignment with trading partner agreement data
B2B Monitoring
Partner
Monitoring
B2B transaction YM
XM
B2B transaction YM
XM
B2B transaction YM
XM
Cloud Integration
Using Cloud Integration and Monitoring for B2B integrations
Generic integration flow

3
PUBLIC
B2B Scenario
Generates
automatically
Per interchange
(message exchange)
The generic integration flow using Cloud Integration
Pushes all content
per B2B scenario
Generic integration flow is based on three parts:
▪ Step 1 – Sender communication flow
▪ Step 2 – Interchange processing flow
▪ Step 3 – Receiver communication flow
Integration Advisor
Runtime Artifacts
Source
Interface
Target
Interface
3

4
PUBLIC
Partner Directory Integration Flow
Partner directory
Partner directory for dynamic parameterization
Basis for the trading partner management system
Partner Directory
TP_1 STANDARD X12
TP_1 COMM_TYPE AS2
TP_2 STANDARD EDIFACT
TP_2 COMM_TYPE SOAP
Trading Partner
Management
In general for e.g.
Partner ID Parameter ID Value
For B2B scenarios:
Get PD
Data Script
Use PD
Data Step
POSTMAN

5
PUBLIC
Trading partner agreement activation
Complete trading partner agreement
will be pushed into partner directory
Partner directory entry per
▪ Interchange extraction
in step 1 “Sender Communication”
▪ Business transaction activity
covering step 2 & 3
PID
(SAP_TPM_<Hash>)
… …
Business Transaction (Purchase Order Request/Response)
Partner Directory Entry String Parameters
(SAP_TPM_<Hash>)
Parameters Receiver
Communication Parameters
Interchange Assembly
PID
(SAP_TPM_<Hash>)
--- Interchange Extraction
Leads to 5 partner directory entries
▪ 3 per business transaction activity
▪ 2 per interchange envelope extraction at
communication sender (SOAP, AS2)
PID Receiver Interchange IA Runtime Artefacts
Binary Parameters
Partner Directory

6
PUBLIC
Partner Directory
<n0:OrderRequest xmlns:n0="http://sap.com/xi/EDI"
xmlns:prx="urn:sap.com:proxy:OH9:/1SAI/TAE813A0CAF5E48F72CEACA:786"
xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<MessageHeader>
<ID>FA163E1805F81EECAEB23CFC49735773</ID>
<CreationDateTime>2022-04-11T12:21:25Z</CreationDateTime>
<SenderBusinessSystemID>0M2DJNB</SenderBusinessSystemID>
<SenderParty>
<InternalID>1710</InternalID>
</SenderParty>
<RecipientParty>
<InternalID>1000404</InternalID>
</RecipientParty>
</MessageHeader>
<Order>
Sender interchange from company BestRun US
Extracted as
parameters
Partner ID:
SAP_TPM_969a378a5ee
9df2ec8fcff906603a351
Identification of the appropriate processing instructions
Step 1 – interchange header parameters Step 2 – Partner ID based on step 1 Step 3 – parameters from partner directory

7
PUBLIC
B2B monitoring
▪ Processes B2B transactions with one integration
flow
B2B Monitoring
▪ Monitors the B2B transactions at runtime in
alignment with trading partner agreement data
B2B Monitoring
Partner
Monitoring
B2B transaction YM
XM
B2B transaction YM
XM
B2B transaction YM
XM
Cloud Integration

8
PUBLIC
Generic Integration Flow
Monitoring scenarios
Processing results of the generic integration
flow
▪ TPM parameters - company + trading
partner
▪ Result per interchange exchange
Allows search based on filters
Step 1: Sender
Communication
Step 2: Interchange
Processing
Step 3: Receiver
Communication
Receiver
System
Sender
System

9
PUBLIC
Monitoring details
Details per interchange exchange
▪ Sender and receiver interchange details:
– B2B standard format
– Message type
– Interchange control number
▪ Collection of the processing events
▪ Exportable list (xls)
▪ Payload visibility and export

10
PUBLIC
Key takeaways
▪ Benefits of one generic integration flow
▪ Detailed overview of deployed artifacts via the
exposed partner directory user interface
▪ Optimized and consolidated view of messages
processed within the B2B scenarios
▪ Detailed view for operations and root-cause analysis
in B2B monitoring

Unit 5: Course Scenario for the Coming Weeks

2
PUBLIC
Course scenario for the coming weeks
B2B scenario definition
B2B Scenario
Defines business transaction for fulfilling a collaborative business process between company and trading partner
System
Interchange B2B
Format
Interchange B2B
Format System
Purchase
Order
Processing
Purchase
Order
Processing
UN/EDIFACT
ORDERS
SOAP Receiver
SAP S/4HANA
On Premise IDoc
ORDRSP.ORDERS05 ORDERSP
UN/EDIFACT
ORDERSP AS2 Sender
Invoice
Processing
Invoice
Processing
SOAP Receiver Invoice AS2
Outbound
Delivery
Processing
Outbound
Delivery
Processing
SOAP Sender Shipment Notice AS2 Receiver
SAP S/4HANA
On Premise IDoc
ORDERS.ORDERS05
Communication Mapping Communication
Company
Receiver
Sender
Sender
Receiver
Outbound
interchange
Inbound
interchange
UN/EDIFACT
INVOIC
UN/EDIFACT
DESADV
SAP S/4HANA
On Premise IDoc
DELVRY03
SAP S/4HANA
On Premise IDoc
INVOIC02.INVOC
Two-way business
transaction:
 request
and
→ response
One-way business
transaction:
→ exchange
or
→ notification
Business Transaction
[ Purchase Order Request ]
[ Purchase Order Response ]
[ Invoice Exchange ]
[ Delivery Notification ]
Trading Partner

3
PUBLIC
B2B scenario – Purchase order request response
Same B2B scenario with
multiple trading partners
▪ Company’s side relatively
stable/the same
▪ Trading partner’s side as of
each trading partner
Company
Trading
Partners
SAP IDoc UN/EDIFACT
Purchase
Order
ORDERS.ORDER05
(via SOAP receiver)
ORDERS
(via AS2))
ORDRSP.ORDERS05
(via IDoc sender)
ORDRSP
(via AS2)
INVOIC.INVOIC02
(via IDoc sender)
Outbound
delivery
DESADV.DESADV01
(via IDoc sender)
DESADV
(via AS2)
Integration
Suite
(Cloud
Integration)
Trading
Partner
Systems
B2B System
SAP S/4HANA
On-Prem
Procurement
Value Added
Network
INVOIC
(via AS2)
Invoice
SAP On-
Premise / Cloud

4
PUBLIC
Trading partner agreement – Purchase order request response
TPA
Agreed B2B Scenario

5
PUBLIC
SAP S/4HANA On Premise IDoc
Company sender/receiver
identifier in company’s IDoc
interchanges
Company sender/receiver
identifier in trading partner
EDIFACT interchanges
Trading partner sender
/receiver identifier in trading
partner's EDIFACT
interchanges
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>400</MANDT>
<DOCREL>1709_FPS02</DOCREL>
<DIRECT>2</DIRECT>
<IDOCTYP>ORDERS05</IDOCTYP>
<MESTYP>ORDERS</MESTYP>
<SNDPOR>SAPDE0</SNDPOR>
<SNDPRT>KU</SNDPRT>
<SNDPRN>HE4CLNT400</SNDPRN>
<RCVPOR>SAPDE0</RCVPOR>
<RCVPRT>KU</RCVPRT>
<RCVPRN>OSAPDEMO01</RCVPRN>
</EDI_DC40>
UNA:+.? '
UNB+UNOA:3+UNEDI-TP-E0001
:14+1234567890123:14+230612:1235+20230612123501++ORDERS'
UNH+1+ORDERS:D:96A:UN' Receiver Partner ID
Use of company and trading partner identifiers
UN/EDIFACT
Company
BestRun US
Trading Partner
Tullius Grocery
Receiver Partner ID
Sender Partner ID
Sender Partner ID
Trading partner sender/receiver
identifier in company’s IDoc
interchanges

6
PUBLIC
Trading partner agreement
Purchase
Order
Outbound
Delivery
Invoice
ORDERS. ORDERS05
(via IDoc receiver)
ORDRSP. ORDERS05
(via IDoc sender)
INVOIC. INVOIC02
(via IDoc sender)
DESADV. DESADV01
(via IDoc sender)
IDoc
Trading Partner MIGs
Integration Advisor
Tullius Grocery ORDERS
Tullius Grocery ORDRSP
Tullius Grocery INVOIC
Tullius Grocery DESADV
Trading Partners
System:
B2B System
UN/EDIFACT,
Version: D96:A
Identifiers:
▪ 1000404 (SAP S/4HANA
SOAP API)
▪ X12-404 (X12)
Trading Partner
Tullius Grocery
UN/EDIFACT
ORDERS
(via AS2)
ORDRSP
(via AS2)
INVOIC
(via AS2)
DESADV
(via AS2)
Trading
Partner
Systems
B2B System
Agreement Template
ORDERS → ORDERS.ORDERS05
ORDRS.ORDERS05 → ORDSP
INVOIC.INVOIC02 → INVOIC
DESADV. DESADV01 → DESADV
MAGs
Tullius Grocery PO Create →
BestRunORDERS
BestRun ORDRS.ORDERS05
→ Tullius Grocery ORDRSP
BestRun INVOIC.INVOIC02 →
Tullius Grocery INVOIC
BestRun DESADV.DESADV01
→Tullius Grocery DESADV
Mapping
SAP
On-Premise

7
PUBLIC
Preview B2B scenario

8
PUBLIC
Key takeaways
▪ B2B scenario design is based on predefined
patterns (two-way, one-way)
▪ Agreement template as baseline for agreements
which could be reused for several trading partners
with similar scenarios
▪ Configuration of identifiers and processing
instructions from master inherited in B2B scenarios
for accelerated onboarding
▪ Detailed overview and optimized update process for
change management

Unit 6: SAP Integration Suite Roadmap for B2B

2
PUBLIC
SAP Integration Suite roadmap for B2B
An outlook of B2B features planned

3
PUBLIC
*) SAP Help for
TPM:Getting Started with B2B Scenarios in SAP Integration Suite | SAP Help Portal
IA: Integration Content Development | SAP Help Portal
**) Roadmap: SAP Road Map Explorer
Status of TPM, IA, and B2B monitoring
Status
▪ Current release of TPM capability extends our B2B
offering within SAP Integration Suite to cover specific
B2B scenarios
▪ The supported components released within TPM will
be continuously extended with the overall
investments of B2B in SAP Integration Suite
▪ Further details
− current status on SAP Help*) and
− planned status in the roadmap explorer**)

4
PUBLIC
▪ Global custom codelists
▪ Code value mapping from multiple source to one
target node
▪ WSDL support for Custom Messages & Extended
S4HANA SOAP Messages
▪ Duplicate Target Nodes
▪ New type system – TRADACOMS
▪ Envelope support for MIGs and MAGs
Integration Advisor features

5
PUBLIC
▪ Support of TRADACOMS
▪ Multiple trading partners to be assigned to one
trading partner agreement
▪ Support of the process direct on the sender and
receiver side
▪ Trading partner-specific code value mapping at
agreement level
▪ Optimized search and filtering option for root cause
analysis
▪ Advanced envelope configuration options
Trading partner management features

6
PUBLIC
SAP SAP
Integration feature
request
▪ Customer Influence portal:
New customer request
SAP review of feature requests
and planning process
▪ SAP will accept or decline the feature request
▪ If accepted, the feature request will be taken into the
development cycle
End-to-end request to roadmap process
Acceptance as
feature request?
Yes/No
Foreseen for
planning and
delivery
Roadmap
▪ Planned feature
published on
roadmap
E-mail for request
SAP’s Customer Influence program for SAP Integration Suite
1 2
Customer
Influence portal
Request
assessment
Planning and
delivery
SAP
roadmap
Customer
and partner
requests

7
PUBLIC
SAP Road Map Explorer for B2B integration

openSAP_btp4_Week_11_2025_All_Slides.pdf

More Related Content

Similar to openSAP_btp4_Week_11_2025_All_Slides.pdf

More from Thomas

Recently uploaded

openSAP_btp4_Week_11_2025_All_Slides.pdf