Trading partner agreements
Keeping track of who business documents are exchanged with and what is set up with each partner: a profile per partner with its contact person, identifiers, communication protocol and B2B standards, an agreement per partner, and one generic flow parameterised from them in place of a flow per partner. What a message looks like and how it maps is B2B message mappingB2B message mappingDefining the structure of business messages exchanged between partners using different standards, and mapping one structure onto another. This includes interface specifications, schemas and transformations; executing them in middleware belongs to integration flows.SAP only, and executing the exchange is integration flowsIntegration flowsMoving and transforming messages between systems in middleware instead of in application code: an integration flow with its adapters and mappings, and the runtime it executes on. Reaching a remote system from application code is destinations, and brokering events between systems is Event Mesh.SAP only.
Overview
Trading Partner ManagementTrading Partner ManagementPartner profiles, agreement templates and agreements for B2B exchange, pushed into the Partner Directory of Cloud Integration so one flow serves every partner, inside SAP Integration Suite.sap official, btp in 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 keeps company and trading partner profiles, agreement templates and agreements, and on activation pushes an agreement's 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, where one parameterised integration flow reads them by partner ID.
Not covered: At configuration. The exchange itself runs in a 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 flow, and the message guidelines and mappings an agreement refers to come from 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.
No community artifact is documented here.
Artifacts
Content
Details
Coverage
For your agent
- Ref
capability:trading-partner-agreements- JSON
- /capabilities/trading-partner-agreements.json
- MCP
- Connecting an agent