Week 3: How to Operate and Maintain the B2B Integrations

Unit 1: Using ProcessDirect Integration Flows

Using ProcessDirect integration flows
Learning objectives of this course week

In this course week, you will learn

▪ How to create and use customized ProcessDirect-
related processing flows
▪ How and for what to use the custom parameters
▪ How to validate an end-to-end scenario of an
activated business transaction activity
▪ How to handle error messages
▪ How to create and maintain B2B integration content
▪ How to transport the B2B integration content in a
multi-tier landscape
▪ How to do a migration from another B2B system

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

Using ProcessDirect integration flows
What kind of customized ProcessDirect-related processing flows are possible?

Generic standard integration flows

Custom sender
JMS JMS
communication
Step 1b – Extract Headers Step 2 – Interchange Processing Flow Step 3 – Receiver
Custom pre-processing from Interchange Flow Communication Flow

before mapping Extraction

PD lookup step
Custom IA related Custom Interchange
steps pre-processing mapping steps post-processing assembly steps
Others

Custom main mapping

Custom ProcessDirect
main mapping

Custom post-processing
after mapping
Custom Communication Custom Pre-Processing Custom Mapping Custom Post- Custom Receiver
Sender Flow Integration Flow Integration Flow Processing Inte- Communication
Custom receiver gration Flow

communication Communi-
cation and set
parameters
Pre-processing
flow steps
Mapping flow
steps
Post-processing
flow steps
Communi-
cation and set
parameters
steps steps

Customized integration flows

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3
Using ProcessDirect integration flows Custom Integration Package
General suggestions

▪ Create a separate integration package

▪ Create an integration flow template
▪ ProcessDirect address should be externalized
▪ Use same naming convention for integration flow
name and ProcessDirect address, for example:
– Integration flow name: Custom Integration Flow Template
[Pre-Processing|Post-Processing|Mapping] . <TP-
Name> . <BTA-Name> . <Type-System>
– ProcessDirect address:
/tpm/[pre-processing|post-processing|mapping]/
[default|<tp-name>/<bta-name>/<type-system>
▪ Use exactly the same terms in integration flow
names and ProcessDirect address

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

Using ProcessDirect integration flows
Custom sender communication
At Company or Trading Partner Profile:

▪ For what purpose?

– Incorporate non-supported communication protocols
– Connect to other integration flows
▪ How to set up in TPM
– Company or Trading Partner Profile: At Trading Partner Agreement:
▫ System → Communications → Direction: Sender; Adapter:
Process_Direct
▫ One communication channel for all custom sender communications
– Trading Partner Agreement → Business Transaction Activity
▫ Sender communication channel: Select “ProcessDirect”-related
communication channel
Sender Integration Flow:

▪ How to create an integration flow

– Should cover required communication or processing
behavior at sender communication side
– Set header parameters such as for setting
content type, and type system
– ProcessDirect adapter at receiver side
Address: /tpm/b2b/sap_tpm_internal_processdirect
– Connection address: Same as ProcessDirect address in Step 1b
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Using ProcessDirect integration flows
Custom receiver communication At Company or Trading Partner Profile:

▪ For what purpose?

– Incorporate non-supported communication protocols
– Connect to other integration flows
▪ How to set up in TPM
– Company or Trading Partner Profile:
▫ System → Communications → Direction: Receiver; Adapter: At Trading Partner Agreement:
Process_Direct
▫ One communication channel per custom receiver communication
– Trading Partner Agreement → Business Transaction Activity
▫ Receiver communication channel: Select “ProcessDirect”-related
communication channel Receiver Integration Flow:
▪ How to create an integration flow
– Should cover required communication or processing
behavior at receiver communication side
– Set custom parameters such as communication address,
credentials, etc., if required
– ProcessDirect adapter at sender side

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

Using ProcessDirect integration flows
Demo: custom sender and receiver communication

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

Using ProcessDirect integration flows
Custom pre-processing before mapping

▪ For what purpose? At Trading Partner Agreement:

– Getting external data such as from lookup tables
– Adjustments of source structures such as pre-sorting
▪ How to set up in TPM
– Trading Partner Agreement → Business Transaction
Activity Pre-Processing Integration Flow:
▫ Sender interchange: Enable “Customized Pre-Processing”
and enter ProcessDirect address
▪ How to create an integration flow
– Create processing flow steps for getting external data
or adjusting source payload, for example, via XSLT
– ProcessDirect address: Same as ProcessDirect
address in related custom pre-processing integration
flow
– ProcessDirect adapter at sender side and no adapter
at receiver side
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
Using ProcessDirect integration flows
Custom main mapping (I)
At Trading Partner Agreement:
Sender Interchange

▪ For what purpose?

– Mapping via Integration Advisor’s MAG is not
possible or not sufficient
– Legacy mapping artifacts are already available
▪ How to set up in TPM
– Trading Partner Agreement → Business
Mapping
Transaction Activity
▫ Mapping: Enable “Customized Mapping Processing”
and enter ProcessDirect address
▫ Requires selection of (dummy) source and target MIGs
Receiver Interchange
in selected type systems, message types, and message
type version
▫ MAG selection will be disabled

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

Using ProcessDirect integration flows
Custom main mapping (II)

▪ How to create a mapping integration flow Mapping Integration Flow:

– Create processing flow steps with mapping, if
necessary
– Mapping can be created via message mapping,
XSLT, or Groovy
– ProcessDirect adapter at sender side and no
adapter at receiver side
– ProcessDirect address: Same as ProcessDirect Example Message Mapping:
address in related custom mapping integration flow

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

Using ProcessDirect integration flows
Custom post-processing after mapping

▪ For what purpose? At Trading Partner Agreement:

– Getting external data such as from lookup tables
– Adjustments of source structures such as post-sorting
▪ How to set up in TPM
– Trading Partner Agreement → Business Transaction
Post-Processing Integration Flow:
Activity
▫ Sender interchange: Enable “Customized Pre-Processing”
and enter ProcessDirect address
▪ How to create an integration flow
– Create processing flow steps for getting external data
or adjusting source payload, for example, via XSLT
– ProcessDirect adapter at sender side and no adapter
at receiver side
– ProcessDirect address: Same as ProcessDirect
address in related custom post-processing integration
flow
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11
Using ProcessDirect integration flows
Demo: custom pre-processing and custom post-processing

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

Using ProcessDirect integration flows
Key takeaways

▪ Not all
− Required communication is supported
− Manipulation or mapping of payloads is possible
− Data will be available at the point of time of processing
▪ Customized integration flows connected via ProcessDirect
help fulfill the additional requirements at
− Communication sender and/or receiver side
− Mapping, enriching, or manipulation via custom mapping,
pre-processing, and/or post-processing
▪ Naming conventions support consistent creation,
categorization, and search for related custom integration
flows
▪ Bear in mind: Next releases may provide standard features
for existing customizations
Suggestion: Think about the migration strategy
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13
Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Unit 2: Using Dynamic Parameters
Using dynamic parameters
Overview Custom parameters SAP TPM standard parameters
TPM Standard Parameter UN-EDIFACT SAP-IDoc

SAP_EDI_REC_Message_Number UNH/[01]0062 EDI_DC40/[03]DOCNU

UNT/[02]0062 M (Receiver)

SAP_EDI_REC_Interchange_Control_ UNB/[05]0020 EDI_DC40/[03]DOCNU

What are dynamic parameters? Number M (Receiver)

▪ Custom parameters → Maintainable in TPM SAP_EDI_REC_Message_Version UNH/[02]S009/[02] EDI_DC40/[04]DOCREL

0052

▪ SAP TPM standard parameters

SAP_EDI_REC_Processing_Priority_ UNB/[08]0029 EDI_DC40/[08]EXPRSS
– Key parameters for all processing Code

– For all envelope or message header elements SAP_EDI_REC_Usage_Indicator UNB/[11]0035 EDI_DC40/[09]TEST

SAP_EDI_REC_Message_Type UNH/[02]S009/[01] EDI_DC40/[12]MESTYP

0065
Where you can set custom parameters? SAP_EDI_REC_Sender_System_ID UNG/[02]S006/[01] EDI_DC40/[18]SNDPO
0040 R
▪ Company Profile → Customer-related custom parameters
▪ Trading Partner Profile → Trading partner-related custom SAP_EDI_REC_Sender_ID UNB/[02]S002/[01] EDI_DC40/[21]SNDPR
0004 N

parameters
SAP_EDI_REC_Sender_Routing_Add UNB/[02]S002/[03] EDI_DC40/[22]SNDSAD

▪ Trading Partner Agreement Template → Template of ress 0008

business transaction activity-related custom parameters SAP_EDI_REC_Receiver_System_ID UNG/[03]S007/[01] EDI_DC40/[24]RCVPO

0044 R
– Per business transaction activity
– Can inherit customer-related custom parameters SAP_EDI_REC_Receiver_ID UNB/[03]S003/[01] EDI_DC40/[28]RCVPR
0010 N

▪ Trading Partner Agreement (TPA) → Template of business SAP_EDI_REC_Receiver_Routing_A UNB/[03]S003/[03] EDI_DC40/[29]RCVSAD

ddress 0014
transaction activity-related custom parameters SAP_EDI_REC_Interchange_Date UNB/[03]S004/[01] EDI_DC40/[31]CREDAT
0017

SAP_EDI_REC_Interchange_Time UNB/[04]S004/[02] EDI_DC40/[32]CRETIM

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 0019 2
SAP_EDI_REC_Document_Standard UN-EDIFACT SAP_IDoc
Using dynamic parameters
For what can you use custom parameters?

Sender Interchange: Inbound Direction

▪ Routing, or calling parameters for custom pre-processing flows

Mapping:
▪ Central configuration and provisioning of values for mappings

Receiver Interchange: Custom Custom

Custom
parameters parameters Custom
▪ Envelope or message header-specific parameters parameters
for receiver for envelope, parameters
– Envelope/message header elements that are not yet supported for pre-
communi- and post- for mapping
processing
– Overruling already set TPM envelope/message header values cation processing
▪ Routing, or calling parameters for custom post-processing flows

Receiver Communication:
▪ Configuration parameters for receiver communication
▪ Additional ProcessDirect-based receiver communication channels
Outbound Direction
▪ Overruling already set TPM communication parameters

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

Using dynamic parameters
Company and trading partner-related custom parameters
Creation of Company or Trading Partner-Related Custom Parameters

How to create
▪ Simply via import of CSV files

For what are customer or trading partner-related

custom parameters useful?
▪ Mappings: e.g. time zone, country, currency, lookup-tables
▪ Receiver Interchange
– Envelope/Message Header: e.g. partner type, partner
function, partner system ID
▪ Receiver Communication: e.g. email (SMTP) address,
SFTP address
Inbound Direction → Company Custom Parameters

Outbound Direction → Trading Partner Custom Parameters

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

Using dynamic parameters
TPA template and TPA-related custom parameters
Inherit Company-Related Custom Parameters

Trading Partner Agreement Templates → Business Transaction Activity

▪ Inherit from company profile
▪ Create / delete individual activity parameters
Inherit Trading Partner-Related Custom Parameters
Trading Partner Agreement → Business Transaction Activity
▪ Copy from trading partner agreement template
▪ Inherit from trading partner profile
▪ Create / delete individual activity parameters

For what are individual activity parameters useful? Create Activity-Related Custom Parameters
▪ Sender Interchange:
– Pre-Processing: e.g. sender message function, sender extension
parameters
▪ Mapping: e.g. controlling agency, message function,
▪ Receiver Interchange Inbound Direction → Activity Parameters Defined in TPA Template
– Envelope/Message Header: e.g. message function, extension types
– Post-Processing: e.g. receiver message function, receiver extension
functions
▪ Receiver Communication: e.g. email/AS2 (SMTP) subject, email AS2 Outbound Direction → Activity Parameters Defined in TPA
content type, SFTP directory

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

Using dynamic parameters
Use of custom parameters for custom pre- or post-processing flows

a) Additional flow step for getting custom parameters or

SAP TPM standard parameters from partner directory
– Required: Get SAP_TPM_ACTIVITYPARTNER_ID from
header for fetching content from appropriate PD entry
– Obtain SAP TPM standard parameters via getParameter: Custom Pre-
SAP_TPM_ACTIVITYPARTNER_ID and set it as Processing of Post-
exchange property Processing Flow
– Get custom parameters via getParameter:
SAP_TPM_CustomActivityParams and resolve array via a) Script for Calling
each loop Partner Directory

b) For example, in XSLT-based processing flow step: Calling

required parameters via global declaration with <xsl:param>
Note: You can also use these parameters in other flow
steps, such as content modifier

b) XSLT Script for

Processing

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

Using dynamic parameters
Demo: definition and usage of custom parameters in custom flows and envelope headers

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

Using dynamic parameters
Custom parameters for mappings (MAGs)

Mapping Guideline → Global Setting of Custom Parameters in Business Transaction Declaration of Custom
Activity Parameters in MAG
Parameters
▪ Custom parameters must be set as global
parameters

Mapping Guideline → Mapping

▪ Custom parameters can be called via
– Functions at target side
– Mapping element functions

Call via Function

at Target Side

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

Using dynamic parameters
Use in mapping element functions
Setting of Custom Parameters in Declaration of Custom
Business Transaction Activity Parameters in MAG

Mapping element functions using

custom parameters with

a) Single values:
▪ e.g. create date time stamp with
adjusting time zone using the custom
parameter $Trading_Partner_Timezone a) Mapping
Element Function
b) With lists (lookup tables): Using Single
Values
▪ e.g. provide a target value based on a
match of compound of source values
with the entries in CVM table
$CVM_TaxCode for getting the resulting
tax code b) Mapping
Element Function
Using Lookup
Tables with a
Compound of
Source Values
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9
Using dynamic parameters
Demo: definition and usage of custom parameters in mappings

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

Using dynamic parameters
Custom parameters for custom receiver communication channel
Trading Partner → System Setting of Custom Parameters in
→ Communications Business Transaction Activity

Setting of required custom parameters for

custom receiver communication channel
▪ Such as custom receiver communication “Mail.Receiver”

In related business transaction activity

a) Select the receiver communication “Mail.Receiver”
b) Set custom parameter “Mail_Receiver_From” in
Company Profile and add it into activity parameters
c) Set custom parameter “Mail_Receiver_To” in Custom Integration Flow
Trading Partner Profile and add it into activity parameters for Communication
d) Create the custom parameter “Mail_Receiver_Message_Subject” Receiver:
in activity parameter with custom expression

Created and deployed integration flow “Mail.Receiver” Custom Parameters in

e) ProcessAddress must be the same as in Trading Partner Profile Receiver Mail Adapter:
f) Flow step for obtaining custom parameters
g) Flow step for resolving expression as defined in “Mail_Receiver_Message_Subject”
h) Refer to required custom parameters via ${property.xxx} expression

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

Using dynamic parameters Setting of Custom Parameters in
How to create custom expression Business Transaction Activity

A custom script can be created for resolving custom

expressions using a limited set of “Simple Expression
Language”
▪ Expression example:
expression[${header.SAP_TPA_BTA_Direction.substring(0,1)} -
${header.SAP_SAP_EDI_REC_Message_Type} - Groovy Script in
${header.SAP_TPA_SND_Trading_Partner_Name.replaceAll('\\s','- Flow Step
')} - ${header.SAP_EDI_Interchange_Control_Number} -
${date:now:yyyyMMdd}_${date:now:HHmmssSSS}]
“Resolve Custom
Expression”:
▪ Example for message subject:
O – INVOIC – TulliusGroceryBros – 00001 – 20231001_12300000

Groovy script for resolving expression

a) Obtain the custom parameters and check if one of the custom
parameters has prefix “expression[“ and suffix “]”
b) Resolve the dynamic expressions starting with ${header.xxx}
or ${property.xxx} for obtaining the values
c) Some of the expression functions must be explicitly declared
and logic must be implemented such as date and time stamps
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12
Using dynamic parameters
Demo: definition and usage of custom parameters in custom receiver communication

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

Using dynamic parameters
Key takeaways

▪ Custom parameters are very useful for setting

individual and additional values that are not supported
by TPM profiles
▪ Custom parameters can be effectively maintained and
categorized for higher reuse via company profile,
trading partner profile, trading partner agreement
template, and trading partner agreement
▪ Custom parameters in combination with
ProcessDirect-related flows give greater flexibility for
fulfilling additional B2B-related requirements
▪ Custom parameters can be used to overrule SAP
standard parameters
▪ Custom parameters provide trading partner-related
values for mappings via Mapping Guidelines.

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

Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Unit 3: Validating the End-to-End Scenario
Validating the end-to-end scenario
Introduction

You can effectively set up and validate an end-to-

end scenario representing a business transaction
activity by:
▪ Checking that none of the reference Mapping Guidelines
are broken
▪ Analyzing the PD entries of a “Business Transaction
Activity” stored in the partner directory
▪ Setting up a test end-to-end scenario for a “Business
Transaction Activity” using API test client
▪ Analyzing and correcting PID string for calculating the
PID
▪ Analyzing the payload validation results
▪ Analyzing the results of major flow steps of “Step 2 –
Interchange Processing Flow”

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

Validating the end-to-end scenario
Activate TPA → Check if MAG is processable via MAG simulation
Trading Partner Agreement

TPM does not obtain broken run artifacts from

Integration Advisor
▪ This leads to an error in the activation process
▪ Recommendation: Check via MAG simulation if data
will be processed
Mapping
To do this Guideline

a) Open the MAG

b) Select “Simulate” and upload the source payload
c) You should see the results of the simulation data at
the target side
d) If none of the MAGs in the TPA are broken, click
“Activate”

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

Validating the end-to-end scenario
How to analyze the entries stored in the partner directory

Activated Trading
Once the TPA is successfully activated, you can Partner
check what kind of data is pushed into the partner Agreement
directory for each business transaction activity
a) Check that the TPA is activated
b) Open the “View Data” in the Business Transaction →
Partner Directory Data → Inbound or Outbound

A separate window will show a list of all stored:

▪ String parameters with their values
▪ Binary parameters with their content types Partner Directory
of Selected
Business
Transaction
Activity

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

Validating the end-to-end scenario
How to simulate an end-to-end scenario – Preparation for the TPA

Display in API-
An end-to-end flow can be effectively simulated Based Test Client
using an API-based test client, where you can
see the sender and receiver interchange payload
in one view Enablement of
Sender/Receiver
To do this: Communication
Channels
▪ You should prepare two custom communication flows
(available as package):
– Step 1a – B2B Simulation. Sender that receives the Custom Integration Flows
calls from API test client hands over to Step 1b and
returns the processing results back to the API test
client
– Step 3b – B2B Simulation Receiver. It inserts
linefeeds (in UN/EDIFACT or ASC X12) and stores
them in datastore for the response via Step 1a
▪ In TPM: Both custom communication flows should be
enabled as ProcessDirect sender and receiver
communication channels
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Validating the end-to-end scenario
How to set up a test end-to-end scenario – Preparation in the API test client
HTTP Header Parameters

In the API test client of your choice, you should

a) Create an HTTP request
b) Insert the address in the B2B simulation and your connection API-Based Test Client
credentials, such as user name and password
c) Copy the test source interchange payload into the body
d) Add the HTTP headers:
– communication_protocol, one of the values:
AS2, IDOC, SOAP
– message_content_type, one of the values:
application/XML, application/EDIFACT, application/EDI-X12
– type_system, one of the values:
ASC-X12, UNEDIFACT, SAP_IDoc,
SAP_S4HANA_Cloud_SOA
– Insert_carriage_retune: true or false

It should usually be possible to send the sender

interchange payload
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
Validating the end-to-end scenario
How to get a correct PID string for calculating the PID

API-Based Test Client: Result After First Sent

You can check which values must be provided for getting a

“matching” PID string with the following steps:
a) Send the interchange sender payload from API-based test client
b) You should usually see an internal server error coming from Cloud
Integration Failure Entry in B2B Monitoring

In most cases, the appropriate PID entry cannot be found in the

partner directory. Check this via
c) Details in the B2B Monitoring entry
d) It will show the generated PID and PID string if nothing is found
You should now compare:
– Generated PID String:
Process_Direct-SAP_IDoc--755-BSQA1001--LS---
TGB10213244--KU---INVOIC.INVOIC02
– Expected PID String from Partner Directory:
Process_Direct-SAP_IDoc--1809_FPS02-DS1CLNT-----
SAP-TGB-E-01-----INVOIC.INVOIC02

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

Validating the end-to-end scenario
Correct the parameters in TPM or sender interchange payload

Changes in Trading
Partner Agreement
Due to the identified mismatch, you need to
change the following in the TPM:
▪ Trading Partner Agreement/Profile Parameters
a) Type System Version
b) Company Identifier (Sender in Outbound
Direction)
c) Trading Partner Identifier (Receiver in
Outbound Direction)
▪ Sender Interchange Payload, deletion of
d) SNDPRT – Sender Partner Type
Changes in New PID and
e) RCVPRT – Receiver Partner Type Sender PID String After
because both are not yet supported Interchange Update in
Payload Partner
The updated PD entry should have the same Directory

PID string:
Process_Direct-SAP_IDoc--755-BSQA1001-
----TGB10213244-----INVOIC.INVOIC02

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

Validating the end-to-end scenario
How to get a correct PID string for calculating the PID – Resubmission

Correctly processed sender interchange payload in API test client:

The generated PID string of the submitted sender

interchange payload should now be the same:

Process_Direct-SAP_IDoc--755-BSQA1001-----
TGB10213244-----INVOIC.INVOIC02

If this is the case, you should see:

▪ In API test client: A 200 OK with the resulting receiver
interchange payload
▪ An entry in B2B Monitoring with status completed … and in B2B Monitoring:

You can now start with more detailed end-to-end

tests and corrections via the API test client

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

Validating the end-to-end scenario
Demo: setting up an end-to-end flow using API test client

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

Validating the end-to-end scenario
How to get and analyze the payload validation results

Enable/disable payload validation in Business

Transaction Activity:
Integration Advisor generates precise payload
validation rules, which can be enabled at each
“business transaction activity”

If payload validation is enabled

a) B2B Monitoring displays “Completed” for the completed
process, but an “Error” in the details because of non- Display of validation error in B2B Monitoring:
mandatory validation failures
b) Details will be provided in the related MPL log entry via
“XML Validator Error Document”

Get to the details in related MPL log entry:

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

Validating the end-to-end scenario
How to get and analyze the payload validation results

Example: Based on the definition of the MIG, the following errors will be shown:
a) Value of KUNDEINR is too long
b) Code of FKTYP is not defined in the MIG
c) According to the assertion rule, the value of CURCY is not the same as EU

The sender interchange Validation error results Definition in MIG

payload

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

Validating the end-to-end scenario
How to analyze the content of major interim steps
Step 2 – Interchange Processing Flow → Process to Receiver Interchange

Sometimes, it is necessary to enable the

trace for further analysis of the content,
especially the
▪ Step 2 – Interchange Processing Flow

The following flow steps produce major

transformations:
a) After custom pre-processing,
if enabled
b) After Integration Advisor-related pre- → Assemble Receiver
processing Interchange
c) After mapping
d) After Integration Advisor-related post-
processing
e) After custom post-processing, if enabled
f) After assemble interchange and extracting
custom header parameters
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 13
Validating the end-to-end scenario
Demo: validating and correcting using test approach via API test client

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

Validating the end-to-end scenario
Key takeaways

▪ Once a TPA is activated, all B2B integration content per

business transaction activity will be pushed into the partner
directory
▪ To analyze, validate, and correct the pushed content you can
use the following features and tools:
▪ Partner Directory Data for showing the pushed content
▪ Postman for triggering and simulating an end-to-end flow of a
business transaction activity
▪ Business Transaction Activity → Enable Payload Validation for
getting payload validation results, which you can get via B2B
Monitoring
▪ Use API-based test client, B2B Monitoring, enabled payload
validation, and enabled trace for effective set-up, testing, and
correction.

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

Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Unit 4: Handling Error Messages
Handling error messages
Introduction

This unit explains the most frequent errors when

setting up a TPA.

The focus is on errors on the interchange

payload level and not on the communication
level.

There are two types of errors:

▪ Errors when activating a TPA
▪ Errors when processing

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

Handling error messages
TPA activation: failed to publish Mapping Guideline in partner directory

Error message while activating/updating the TPA:

▪ Failed to publish Mapping Guideline with
id 4974cc53971048219021e45d949b1244 to Partner
Directory. Error was: …

Reason:
▪ There is a fatal mapping error in the Mapping Guideline
so the XSLT cannot be generated.
The consequence: The TPA cannot be activated or
updated
▪ At least one mapping element has a syntactically
incorrect function

Root Cause:
▪ Do a simulation in MAG before TPA activation or updating

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

Handling error messages
TPA activation: subsequent change of identifiers

Issue
▪ Subsequent change of identifier leads to processing error
after updating the business transactions

Reason:
▪ All subsequent changes in the TPA overview will not be
updated in the partner directory while just clicking on
“Update” (a)

Root Cause:
▪ Do “Deactivate” (b) and “Activate” instead of “Update” (a)
BSQA1001

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

Handling error messages
Processing: where to find errors?

If you see in the response an “internal server

error occurred …”

Go immediately to the B2B Monitoring and go

to
▪ Unassigned Interchange, if the error occurred in
step 1 and cannot be assigned to a partner
directory entry
▪ Interchanges, if there is a content processing
error

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

Handling error messages
Processing: sender interchange payload could not be parsed

Error message in B2B Monitoring → Unassigned

Interchange:
▪ Incoming message could not be parsed

Errors could be:

▪ Sender interchange payload has invalid syntax (a)
▪ Wrong or non-supported content type (b)
▪ Wrong or non-supported type system (c)

Root cause analysis:

▪ Analyze sender interchange payload in detail
▪ Click on link to get details of MPL – Message Process Log
(d)
▪ Enable trace of step 1a and step 1b integration flows, if
required → Check on which flow step the error will be
raised

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

Handling error messages
Processing: cannot find appropriate processing content in partner directory

Error message in B2B Monitoring → Interchange:

▪ Agreement Configuration Access Failed

Reason:
▪ At least one of the key values in the sender interchange payload header
is incorrect:
– Communication protocol type value (a)
– B2B standard type (type system) (b)
– Message type (c)
– Message type or B2B standard version (d)
– Sender or partner ID, qualifier, or type (e)
– Receiver or partner ID, qualifier, or type (e)

Root cause analysis:

▪ Check TPA to see which of them could match (e)
▪ Compare the PID string with the one stored in the partner directory (f)
▪ Compare values in header (d – f) with corresponding values in TPA
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Handling error messages
Processing: validation syntax error in sender interchange payload

Error message in B2B Monitoring → Interchange:

▪ Document validation error….

Reason:
▪ The sender interchange payload based on UN/EDIFACT or
ASC.X12 might be incorrect in its syntax representation or
might have incorrect values in the headers or trailers

Root cause analysis

▪ Open the “Splitter Validation Error Document” in
the linked Message Processing Log entry
▪ Analyze the sender interchange payload
accordingly

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

Handling error messages
Processing: validation schema is invalid

Error message in Interchange:

▪ The schema is invalid, Line: -1, Column: -1

Reason:
▪ The IA generated (source/target) Russian Doll is invalid,
because at least one node has inconsistencies in its
properties, such as fixed value and the selected code value
do not match.

Root cause analysis:

▪ Export the “SAP Cloud Integration Runtime Artifacts” of the
failed MIG
▪ Extract it and open the …RD.xsd in a XML schema validation
tool
– You will see the validation errors in detail
▪ Correct the properties in the MIG accordingly, e.g., delete the
fixed value if just one code value is selected.

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

Handling error messages
Processing: validation errors in receiver interchange payload

Error message in interchange:

▪ Receiver Validating Warning: Mandatory field(s) is/are missing, …

Reason:
▪ The output does not match the defined validation rules in the target MIG:
– Mandatory elements are missing
– Value is too long or does not match the primitive type
– Code value does not match the defined list
– Violation of integrity condition (assertions)

Root cause analysis

▪ Open the “XML Validator Error Document” or receiver payload in
the linked Message Processing Log entry
▪ Compare the receiver interchange payload
with the target MIG and make the required changes
▪ Recommendation: High precision in MIGs increases the efficiency
of the error find and doesn’t require exception handling in MAGs.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10
Handling error messages
Processing: syntax conversion error at receiver interchange payload

Error message in interchange:

▪ Invalid Payload: XML TO EDI CONVERSION cannot
process the payload, …

Reason:
▪ The output does not fit to the expected syntax rules
(esp. ASC X12, UN/EDIFACT or TRADACOMS)

Root cause analysis

▪ Enable trace of integration flow: “Step 2 – Interchange
Processing Flow V2”
▪ Resend and analyze trace → flow step: XML to EDI
Converter With/Without Custom Separators → Message
Content
▪ There may be incorrect values in the headers/trailers, which
could be obtained from the TPA profile or from the custom
parameters

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

Handling error messages
Processing: other frequent errors

Processing failed:
... No consumers available on endpoint
▪ The ProcessDirect addresses of the custom processes do not match

Processing failed:
... SaxonApiException: Errors were reported during stylesheet compilation
▪ Issues with the mapping, such as incorrect functions

Processing failed:
... Failed to resolve endpoint:
xslt://pd:SAP_TPM_47705c5ebb9b1b001f8d64c0ec9d614c:MAPPING_XSLT:Binary
▪ The MAG is not available in the partner directory

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

Handling error messages
Demo: different error cases

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

Handling error messages
Key takeaways

Sometimes it is quite hard to find errors

It helps to follow certain principles in order to make

the root cause analysis more efficient:
▪ Always start with B2B Monitoring, because many errors
are well explained in the B2B Monitoring entries and
you’ll find all the necessary links to the details in these
entries
▪ Create the source and target MIGs as precisely as
possible → This makes the error finding easier and you
do not need to implement exception handling in the
Mapping Guideline

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

Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Unit 5: Export and Import in a Multi-Tier System
Export and import in a multi-tier system
Introduction

The next unit explains how B2B integration content should be

created, maintained, and used in a recommended 3-tier landscape

The transport of the B2B integration content between the tenants

is currently possible using mass export and import

In this unit you’ll learn how you to do mass export/import in the

following order
▪ Source Tenant
1. Export all Mapping Guidelines of the trading partner
agreements to be exported
2. Export all the required trading partner agreements
▪ Target Tenant
1. Import the exported Mapping Guidelines
2. Import the exported trading partner agreements

Custom integration flows can be transport by the enabled Content

Transport System
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2
Export and import in a multi-tier system
Source tenant: export Mapping Guidelines

In the overview list of Mapping Guidelines, click Overview list of Mapping Guidelines → Export
“Export”

In “Select Mapping Guidelines for Export”:

▪ Select all MAGs which should be exported for
the TPA and click “Export”
▪ Consider: You must select these MAGs (and
involved MIGs) which are referred to in the Window for
TPA and corresponding TPA template selecting MAGs
for export
All selected MAGs including involved MIGs and
custom messages will be exported to the
“Downloads” folder as a zip file, starting with
“SAP_IA_MAGs_Export”
Exported file on
download folder

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

Export and import in a multi-tier system
Source tenant: export trading partner agreements (I)

In Trading Partner Management → Cross Actions,

click “Export and Import”
▪ In “Choose Action” select “Export Agreement”,
give an “Action Name”, and click “Create”

In the “Export” window Do final export configuration

1. Select all the TPAs to be exported using the

filter features and click “Next”
2. Configure Export Options:
Choose whether identifiers, communication
channels, custom parameters, and security
should be exported. Recommendation:
– First time: Export all
– Further updates: Placeholder or Skip
3. In the review step, click “Finish”

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

Export and import in a multi-tier system
Source tenant: export trading partner agreements (II)

In Trading Partner Management → Cross Actions Display result of export action at “Cross Actions”
overview, you’ll see the status of the actions

Once the status is “Completed”, you can go to the

details of this entry and click “Download”

In the “Downloads” folder you will find a second

zip file, which starts with “EXPORT_”
Details of export
This zip files includes the selected TPA and its action
corresponding company as well as trading partner
profile

Exported file in
download folder

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

Export and import in a multi-tier system
Target tenant: import Mapping Guidelines

In the overview list of Mapping Guidelines, click Overview list of Mapping Guidelines → Import
“Import”.

In “Select Mapping Guidelines for Import”:

a) Browse for the zip file which starts with
“SAP_IA_MAG_Export”
b) Click “Check”
It will then show which of the MAGs can be
imported Selection of Mapping Guidelines to be imported
c) Select all the MAGs to be imported and
d) Click “Import”
All selected MAGs, including involved MIGs and
custom messages, will be imported.
The successfully imported MAGs will be listed in the
overview list of “Mapping Guidelines”.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6
Export and import in a multi-tier system
Target tenant: import trading partner agreements (I)

In Trading Partner Management → Cross Actions,

click “Export and Import”
▪ In “Choose Action”, select “Import Agreement”, give an
“Action Name”, and click “Create”
In the “Import” window
Do final export configuration
a) Browse for the export zip file which starts with “Export”
b) Set how identifiers, communication channels, parameters,
and security should be imported
Recommendation:
− Initial import: “Create”
− Further updates: “Skip”, or “Create and Overwrite”
if values are changed
c) Choose whether MIG and MAG references should be
imported
Consider: The referenced MIGs and their versions
must be the same as in the already imported MAGs.
d) Click “Import”
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Export and import in a multi-tier system
Target tenant: import trading partner agreements (II)

After processing, the import action entity has the status Final status
▪ Completed, if the content is imported successfully of import
action
▪ Failed, if the content cannot be imported.
In most cases, the referenced MAGs or MIGs do not exist in
the target tenant
After a successful import you should see the imported entries: Imported trading partner agreement
▪ Trading partner profile and company profile with identifiers,
communication channels, custom parameters, and security, if
selected
▪ Trading partner agreement template and trading partner
agreement with custom parameters, and references to MAGs
as well as MIGs, if selected
Procedure
▪ First time: Content should be complete
▪ Properties may be changed accordingly, for example, the
communication channels
▪ Updates: Content will be updated. Make sure that changed
properties will not be overwritten
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8
Export and import in a multi-tier system
Demo: how to export and import Mapping Guidelines and trading partner agreements

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

Export and import in a multi-tier system
Key takeaways

You can (mass) import and export many MAGs

and TPAs at once

You can decide what content should be

overwritten or not overwritten so that changed
parameters in the target tenant can be kept

This approach is required to distribute B2B

integration content consistently in a multi-tier
landscape

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

Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Unit 6: Lifecycle Management
Lifecycle management
Introduction

This unit explains how you can create, use, and

manage B2B integration content in a
recommended 3-tier landscape
It also explains how you can efficiently update
several trading partner agreements and
dependent content in this 3-tier landscape. This
includes:
▪ Get new versions of MIGs and MAGs and get history
▪ Mass update of MAGs related to new MIG version
▪ Mass update of new MIG and MAG versions in
trading partner agreements
▪ Mass deactivation and activation of trading partner
agreements

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

Lifecycle management
Recommended 3-tier landscape
Transport for
testing

Set-up of recommended 3-tier landscape

▪ DEV Tenant:
– Only tenant for creation and maintenance
– Provides master B2B integration content Copy test data
– Test data should be copied from QA tenant
▪ QA Tenant:
SAP
– Tenant for B2B integration content with QA S/4HANA
business applications and trading partners’ B2B Test Data Quality
Directory System
systems
– Gets ready to test B2B integration content from DEV QA PROD
DEV tenant Tenant Tenant Tenant
– Provides basic communication configuration data
▪ PROD Tenant:
– Tenant for productive use between productive
business applications and trading partners’ B2B
systems Transport for
productive use

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

Lifecycle management
DEV tenant: set versions and prepare for transport

If tests per trading partner agreement are

successful
MIGs and MAGs
▪ Activate related (a) source MIG, (b) target MIG, and
then (c) MAG to get a new version and history
▪ Export MAGs
Custom integration flows
▪ Save as a new version via (d) View metadata
▪ Export whole integration package
Trading partner agreement
▪ Set version manually – Currently no versioning and
history available
▪ Business transaction activities: Set final
communication channels
▪ Export relevant trading partner agreement
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4
Lifecycle management
Versioning and history of MIGs

MIGs should be activated before they are

transported to QA or PROD tenant
Clicking “Edit” on activated MIG leads to a new
draft version
Overview list of MIGs
▪ Displays the actual active/draft version
▪ Has link to history list
▪ Has action button to compare different versions of
MIGs

Comparison
▪ Displays the differences in the structures and
details
▪ Can be also used for comparing MIGs based on
same message types

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

Lifecycle management
Versioning and history of MAGs

MAGs should be activated before they are

transported to QA or PROD tenant
▪ Prerequisite: Source and target MIGs must be
activated

Clicking “Edit” on activated MAG leads to a new

draft version
Overview list of MAGs
a) Displays the actual active/draft version
b) Has link to history list
c) Mass update of MAGs

MAG → Overview
d) Possibility to change the versions of assigned
source/target MIGs

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

Lifecycle management
Demo: versioning and history of MIGs and MAGs

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

Lifecycle management
Mass update of MIGs in MAGs

Quite often, company MIGs can be used in

several MAGs

An imported new version of a company MIG

means that this version must be updated in all the
MAGs

“Update MAGs” ensures that the update of a new

version of a company MIG is performed once in all
Mapping Guidelines

The combability check displays the

inconsistencies, such erroneous mapping
elements after update

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

Lifecycle management
Mass update of MIG/MAG in trading partner agreements

If the versions of the MIGs have been

updated in the MAGs, they (MIGs, Select the source and target versions
MAGs) can also be updated all at
once in the relevant trading partner
agreements via
Trading Partner Management →
Cross Action
▪ Update MIG
▪ Update MAG

In update MIG/MAG you can

▪ Define in the current MIG/MAG version Filter and select TPAs for
which target MIG/MAG version will updating the versions
replace it
▪ Filter for the relevant TPAs and select the
ones in which the update is to take place

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

Lifecycle management
Mass deactivation/activation of trading partner agreements

If all the versions are updated in all the trading

partner agreements, it is necessary to write these
updates to the partner directory.
A mass update of all the relevant trading partner
agreements is possible via:
Trading Partner Management → Cross Action
▪ Deactivate Agreements
▪ Activate Agreements

In order to update, you need to perform the steps in

the following order
1. Deactivate all the relevant trading partner agreements
2. Wait until all the relevant trading partner agreements
have been deactivated
3. Activate all the trading partner agreements

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

Lifecycle management
Demo: mass updates of Mapping Guidelines and trading partner agreements

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

Lifecycle management
Key takeaways

A 3-tier landscape is a very useful landscape for creating and

maintaining B2B integration content
▪ Content should be only created, updated, and tested on the DEV
tenant
▪ This content should be tested together with trading partners in the
QA tenant
▪ Tested and confirmed B2B integration content should used on the
PROD tenant for productive use

Transport is currently only possible via export and import.

MIGs and MAGs can be versioned and have a history.

Especially company MIGs are used in several MAGs. Mass

update features ensure that the new versions can be updated
to related MAGs and trading partner agreements all at once.
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12
Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Unit 7: Migration from Legacy
Migration from legacy
Introduction

This unit explains how you can migrate B2B

integration content from a legacy B2B system
into the B2B capability of SAP Integration Suite

The migration is carried out using the test-driven

approach
▪ The required MIGs and MAGs will be built via given
sender and receiver interchange payloads
▪ The generated output will be compared with the
given (expected) receiver interchange payload

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

Migration from legacy
Import of custom IDoc type into Integration Advisor (I)

If custom IDoc (Z-IDoc)-based message types are to

be used to create a MIG
▪ SAP S/4HANA: Open message type documentation via
transaction: WE60
▪ (a) Search for the custom IDoc and (b) generate an XML
schema
▪ Transform this XML schema into the IA-compliant schema
using “Transform SAP S/4HANA IDoc XSD to IA IDoc
XSD”

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

Migration from legacy
Import of custom IDoc type into Integration Advisor (II)

This generated IA-compliant XSD can be imported

into IA as a message type that refers to a standard
message type that is provided by the IA.

The advantages are:

▪ Get full documentation from the standard message type
▪ Benefit from the proposal service

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

Migration from legacy
Create IDoc (source) MIG via interchange payload

If the source MIG is based on the IDoc standard

or custom message type
▪ Create MIG skeleton via uploading payload
(IDOC_INVOIC_01.xml)
▪ Check: Use file content as example values

Once MIG skeleton is created

▪ Click Get Proposals (a)
▪ Click the value help to get proposed qualifiers (b)
▪ Select the qualifiers that are used in the payload
▪ Further refine the MIG accordingly

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

Migration from legacy
Demo: creating an IDoc-based MIG

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

Migration from legacy
Create UN/EDIFACT (target) MIG via interchange payload (I)

Before an EDIFACT MIG can be created via

interchange payload, this payload must be converted
into XML syntax

For this purpose:

▪ In IA: Create a dummy MIG based on the same message
type and version
▪ Select all nodes in this dummy MIG (a)
▪ Export the MIG as SAP Cloud Integration Runtime
Artifacts (b)
▪ Pick exported VB XSD file (such as UN-
EDIFACT_INVOIC_D93A_EAN007.xsd)
▪ Upload it into integration flow “Convert EDI to XML or vice
versa” → flow step: “EDIFACT or X12 to XML conversion”

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

Migration from legacy
Create UN/EDIFACT (target) MIG via interchange payload (II)

Convert the UN/EDIFACT interchange payload into

the XML syntax via “EDI to XML Syntax Conversion”

Save the XML-based output data and delete

▪ Envelope header: S_UNB
▪ Envelope trailer: S_UNZ

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

Migration from legacy
Create UN/EDIFACT (target) MIG via interchange payload (III)

If the target MIG is based on UN/EDIFACT

▪ Create MIG skeleton via uploading payload
(e.g. EDIFACT_INVOIC_01.edi)
▪ Check: Use file content as example values

Once MIG skeleton is created

▪ (a) Click Get Proposals
▪ (b) Click the value help to get proposed qualifiers
▪ Select the qualifiers that are used in the payload
▪ Further refine the MIG accordingly

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

Migration from legacy
Demo: creating an UN/EDIFACT-based MIG

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

Migration from legacy
Create Mapping Guideline using proposal service

Create empty Mapping Guideline and

▪ Assign source IDoc MIG and target
UN/EDIFACT MIG
▪ Run the proposal service via “Get Proposal” (a)
▪ Select best proposal results (b)
▪ Adjust the MAG so the simulation (c) will show
some results at the target side

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

Migration from legacy
Assign the MIGs and MAG to the business transaction activity

Refer the prepared MIGs and MAG in

the relevant business transaction activity
(e.g. 02.) Invoice – Outbound)

Activate the TPA or update the business

transaction

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

Migration from legacy
Perform a test run

Once the TPA is activated and the business

transaction is updated
▪ Perform a test run via an API-based test tool
▪ Download the result as a file in a folder

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

Migration from legacy
Compare generated with expected receiver interchange payload

Compare the generated result with the expected

target interchange payload and

Make the changes in the TPM, MAG, or MIGs

accordingly so that the generated result will match
the expected target interchange payload.
▪ Check guidelines or ask experts in case of doubts and
ambiguities

Remark: Some values should be ignored, such as:

▪ Interchange reference number
▪ Interchange creation date and time stamp

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

Migration from legacy
Demo: testing and finalizing the business transaction activity

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

Migration from legacy
Key takeaways

You can migrate B2B integration content via existing

source and receiver payloads from the B2B legacy system.

This is possible via testing and comparing the processed

results with the expected receiver payloads using the
suggested end-to-end test scenario and an API-based test
client.

Initially
▪ The MIGs will be created from the payloads
▪ The draft MAG is made by the proposal service
– The quality of the proposal depends on the contributions by
the crowd
– Therefore: Please activate the MIGs and MAGs before
transport

This approach is agnostic of any legacy B2B system.

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

Thank you.
Contact information:

[email protected]
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 3: How to Operate and Maintain the B2B Integrations
Appendix
Appendix for Unit 2: Using Dynamic Parameters
Example List of SAP’s predefined parameters

Name Standard Sender Header Parameters Standard Receiver Header Parameters TPM UN-EDIFACT ASC-X12 SAP-IDoc SAP-SOAP

Acknowledgement Request SAP_EDI_Acknowledgement_Request SAP_EDI_REC_Acknowledgement_Request UNB/[09]0031 ISA/[14]I13 NA NA

Common Access Reference SAP_EDI_Common_Access_Reference SAP_EDI_REC_Common_Access_Reference UNH/[03]0068 ST/[03]1705 NA NA

Document Standard SAP_EDI_Document_Standard SAP_EDI_REC_Document_Standard TRUE UN-EDIFACT ASC-X12 SAP_IDoc SAP_S4HANA_Cloud_SOA

Functional Group Creation Date SAP_EDI_Functional_Group_Date SAP_EDI_REC_Functional_Group_Date UNG/[04]S004/[01]0017 GS/[04]373 NA NA

Functional Group Creation Time SAP_EDI_Functional_Group_Time SAP_EDI_REC_Functional_Group_Time UNG/[04]S004/[01]0019 GS/[05]337 NA NA

Functional Group Control Number SAP_EDI_GS_Control_Number SAP_EDI_REC_Group_Control_Number UNG/[05]0048 GS/[06]28 NA NA

UNE/[02]0048 GE/[02]28

Receiver System Identifier SAP_EDI_GS_Receiver_ID SAP_EDI_REC_Receiver_System_ID TRUE UNG/[03]S007/[01]0044 GS/[03]124 EDI_DC40/[24]RCVPOR MessageHeader/[09]RecipientBusinessSystemI
D

Sender System Identifier SAP_EDI_GS_Sender_ID SAP_EDI_REC_Sender_System_ID UNG/[02]S006/[01]0040 GS/[02]142 EDI_DC40/[18]SNDPOR MessageHeader/[08]SenderBusinessSystemID

Interchange Control Count SAP_EDI_Interchange_Control_Count SAP_EDI_REC_Interchange_Control_Count UNZ/[01]0036 IEA/[01]I16 NA NA

Interchange Reference Number SAP_EDI_Interchange_Control_Number SAP_EDI_REC_Interchange_Control_Number TRUE UNB/[05]0020 ISA/[13]I12 EDI_DC40/[03]DOCNUM MessageHeader/[01]ID/[04]CONTENT
IEA/[02]I12 (Receiver)

Interchange Creation Date SAP_EDI_Interchange_Date SAP_EDI_REC_Interchange_Date UNB/[03]S004/[01]0017 ISA/[09]I08 EDI_DC40/[31]CREDAT NA

Interchange Creation Time SAP_EDI_Interchange_Time SAP_EDI_REC_Interchange_Time UNB/[04]S004/[02]0019 ISA/[10]I09 EDI_DC40/[32]CRETIM NA

Message Controlling Agency SAP_EDI_Message_Controlling_Agency SAP_EDI_REC_Message_Controlling_Agency TRUE UNH/[02]S009/[04]0051 ISA/[02]I02 NA NA

Message Number SAP_EDI_Message_Number SAP_EDI_REC_Message_Number TRUE UNH/[01]0062 ST/[02]329 EDI_DC40/[03]DOCNUM MessageHeader/[01]ID/[04]CONTENT

UNT/[02]0062 SE/[02]329 (Receiver)

Message Type SAP_EDI_Message_Type SAP_EDI_REC_Message_Type TRUE UNH/[02]S009/[01]0065 ST/[01]143 EDI_DC40/[12]MESTYP local-name(/node()[1])

Message Version SAP_EDI_Message_Version SAP_EDI_REC_Message_Version TRUE UNH/[02]S009/[02]0052 GS/[08]480 EDI_DC40/[04]DOCREL NA

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

Appendix for Unit 6: Lifecycle Management
Lifecycle management Start
DEV tenant: creation of company-related content

Create Company
Create company profile Profile

▪ Identifiers used in test content from QA business application

▪ Sender/receiver communication for B2B Simulation + final communication
with dummy values Get test content
Test data
from QA business Copy
directory
▪ Custom parameters belonging to company such as applications

partner role, partner function of e-mail address (for e-mail communication) yes

Create company MIGs per identified business transaction activity

Create company
▪ Based on message types and schema structure according QA business MIGs using test data

application
▪ Copy test data from QA business application into test data directory
▪ Create MIG via provided test data Another
business
transaction
▪ MIG should be in draft while complete cycle created activity?

Create trading partner agreement template per agreed B2B scenario no

▪ Superset of business transaction Trading Partner

Agreement
▪ Assignment to company MIGs and B2B simulation communication Template

▪ Custom parameters related to company’s used message types such as

message function or message category
To create Trading
Partner related
content
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5
Lifecycle management From company
related content
DEV tenant: creation of trading partner-related content

Create Trading
Create trading partner profile per trading partner Profile

▪ Identifiers used in test content from trading partners QA B2B

system
▪ Sender/receiver communication for B2B simulation Get test data and
MIG (pdf) from
Adjust test data
with given test data
trading partner from company
▪ Custom parameters belonging to trading partner such as
copy
partner role, partner function, or e-mail address (for e-mail yes
yes
communication) Test data
directory

Create trading partner MIGs per agreed business

transaction activity Create trading
partner MIGs using
▪ Based on message types and provided MIGs (PDF) from test data

trading partners
▪ Get test data from trading partner Another
business
transaction
– Adjust it according to the given company-related test data activity?

– Copy into test data directory no

▪ Create MIG via provided test data Another trading

partner?
– Enrich and finalize MIG with details from provided MIG (PDF)
no
– MIG should be in draft while complete cycle created To create Trading
Parner Agreement

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

Lifecycle management
From create Trading
DEV tenant: creation of trading partner agreement Partner related
content

Create MAGs per created trading partner MIG Create Trading

Test end-2-end flow
Test data
and compare with
Partner Agreement directory
▪ Reference to company MIG and corresponding trading partner MIG reference test data

▪ Create skeleton of MAG using proposal service

▪ MAG should be in draft while complete cycle created
Create initial MAG
Adjust MAG or
using proposal
profiles accordingly
Create TPA per created trading partner profile service

▪ Based on trading partner agreement template

▪ Select subset of business transactions agreed with trading partner Assign trading
partner MIG and Update Business
▪ Per business transaction activity MAG in business Transaction Activity
transaction activity
– Assignment to trading partner MIGs and B2B simulation
communication
– Custom parameters related to trading partners used Another
Test required? yes
interchange/message types such as message function or message yes business
transaction
category activity?

▪ Activate TPA no
no
– Run tests with provided test data based on agreed test cases
Another
– Compare test results with expected test data Activate Trading Activate MIGs and business yes
Partner Agreemnt MAG transaction
– Update B2B integration content accordingly activity?

no

Transport to QA
Tenant
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7
Lifecycle management Test Trading Partner Agreement
QA tenant: test trading partner agreement with trading partner QA Tenant DEV Tenant

Start

If test runs on DEV tenant are successful

Import B2B
integration content
Import tested B2B integration content from DEV tenant of TPA

1. Custom Integration Flow Package Set QA related Incorporate change

communication requests and fix
2. MAGs parameters issues

3. Trading Partner Agreement Set MIGs and MAGs

Activate TPA
to active

Preparation of imported content

▪ Company and trading partner profiles: Set QA-related Test wtih business
application and
yes Exported updated
B2B integration

communication parameters trading partner

yes
content

Test Collect change

requests and issues

▪ End-to-end test of TPA between QA business application

(such as SAP S/4HANA) and trading partners QA B2B system Another test
case

▪ Run all agreed test cases and collect all change requests from no

involved functional expert and trading partner contact If change

requests and

▪ DEV tenant: Incorporate change requests and fix issues issues

▪ Re-iterate procedure until final confirmation Confirmation

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

Lifecycle management Productive Trading Partner Agreement

PROD tenant: set trading partner agreement productive PROD Tenant DEV Tenant QA Tenant

Start

Import B2B
integration content

If test runs with trading partner on QA tenant are successful of TPA

Set PROD related Incorporate change Test wtih business

Import confirmed B2B integration content from DEV tenant communication
parameters
requests and fix
issues
application and
trading partner
yes

Preparation of imported content Activate TPA

Set MIGs and MAGs Collect change
to active requests and issues

▪ Company and trading partner profiles: Set PROD-related yes

communication parameters Final end-2-end Export updated B2B

check integration content

Test
If QA tests are
▪ Activate trading partner agreement
Production
required?

▪ Final end-to-end check no Collect bugs and

If change
requests and
change requests issues

Productive mode no

Changes/fixes
▪ Collect bugs and change requests requied on
priority
Ask for
confirmation

▪ DEV tenant: Update B2B integration content with the

corresponding prioritization If sunset?

▪ Do tests on QA tenant if significant change requests must be yes

Confirm for
tested with trading partner Stop
productive use

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

Thank you.
Contact information:

[email protected]
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.