Trading Partner Management
Partner profiles, agreement templates and agreements for B2B exchange, pushed into the Partner Directory of Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp so one flow serves every partner, inside SAP Integration SuiteSAP Integration SuiteSAP's integration service on BTP: Cloud Integration for orchestration, API Management in front of it, and an MCP gateway that serves a managed API to agents.sap official, btp.
Trading Partner Management holds the configuration of B2B relationships: a profile of the own company and of each trading partner with contact person, identifiers, communication protocol and B2B standards, a communication partner profile for AS2 settings, agreement templates, and the agreements created from them. Activating an agreement pushes its details into the Partner Directory of Cloud IntegrationCloud IntegrationBuilds and runs integration flows that process, route and map messages between cloud and on-premise systems, SAP and non-SAP, through prebuilt adapters; available only under an SAP Integration Suite plan.sap official, btp, and a generic integration flow reads them at runtime by partner ID, so a new partner is an agreement and not another flow. A B2B monitor lists interchanges, assigned to a partner or unassigned, and keeps them for 90 days. The flows it deploys run in Cloud Integration, and the Partner Directory entries carry runtime artefacts generated by Integration AdvisorIntegration AdvisorSpecifies B2B message interfaces and the mappings between them from a library of standards, and generates the schemas and scripts an integration flow runs, inside SAP Integration Suite.sap official, btp: SAP names both as the capabilities it builds on.
Where it sits
Who is behind it
In the atlas: maintains 137, wrote 14@SAPmaintainer
What it declares
Every artifact
- Type
- Service
- Origin
- By SAP
Connections
Tracking trading partners and what is set up with each
Java MCP server for Integration Suite Trading Partner Management
Builds and runs integration flows between cloud and on premise
B2B interface and mapping specification in Integration Suite
Integration service on BTP with Cloud Integration and API Management
Download
Learn more
- Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenario Part - 3Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenario Part - 3Builds the inbound side of a custom EDIFACT-to-IDoc scenario on Trading Partner Management: an iFlow picks a file from SFTP and sets headers for adapter type, document standard, namespace, version and sender and receiver IDs, and a second iFlow assembles them into the agreement's plain partner ID and matches it in the Partner Directory. A Groovy script then calls PartnerDirectoryService.getParameter to read a partner's custom activity parameters and general value-mapping data stored under the agreement, so dynamic field mapping comes from the agreement rather than a flow per partner. Third of a series on setting up trading partner agreements in SAP Integration Suite, after the TPM foundation and the agreement itself in parts 1 and 2.amysh95, published 2026-03-10amysh95, SAP Community
- More than 100 trading partners, one platform: Scalable B2B at Algoma SteelMore than 100 trading partners, one platform: Scalable B2B at Algoma SteelB2B integration at Algoma Steel on SAP Integration Suite: more than 100 trading partners served through Trading Partner Management and one generic integration flow architecture, ML-assisted mapping for the documents, and EDI at that scale after a move from SAP Process Integration and SAP Process Orchestration. The abstract names the three pieces, which is the trading partner agreements model, and not the partner standards or the mapping tooling behind them. A TechEd 2026 session (Wednesday 28 October, Berlin), presented by Jagesh Lakdawala and Marco Ertel, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
- Onboard a trading partner from agreement to live monitoringOnboard a trading partner from agreement to live monitoringOne trading partner onboarded from scratch in Trading Partner Management: a trading partner agreement configured, a business document mapped with ML-assisted mapping proposals, which is B2B message mapping, and a transaction run and monitored live, all inside SAP Integration Suite with no EDI tooling outside it. The abstract names the steps and not the document standard or the partner's protocol. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Claudia Carabineiro, Marco Ertel, Marton Luptak and Tobias Griebe, written here from SAP's abstract; the recording is not yet published.SAP TechEd — session catalogue
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
History in the atlas
- First seen.
For your agent
- Ref
artifact:btp-trading-partner-management- JSON
- /artifacts/btp-trading-partner-management.json
- MCP
- Connecting an agent