{"ref":"capability:b2b-message-mapping","page":"/capabilities/b2b-message-mapping","json":"/capabilities/b2b-message-mapping.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"b2b-message-mapping","name":"B2B message mapping","domain":"integration-and-messaging","ecosystems":["btp"],"universal":false,"description":"Defining 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](capability:integration-flows).","short":"Defining and mapping business messages between B2B standards","core_coverage":{"state":"core-only","assessed_at":"2026-09-20","what_core_does":"[Integration Advisor](artifact:btp-integration-advisor) in [SAP Integration Suite](artifact:btp-integration-suite) starts from a library of type systems kept by the agencies that own each standard, and from one of its messages builds a message implementation guideline, a mapping guideline between two of them, and the XSD schemas and XSLT scripts generated from the mapping.","where_it_stops":"At design time. The generated runtime artifacts are injected into a [Cloud Integration](artifact:btp-cloud-integration) tenant or exported, and an integration flow executes them.","sources":[{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integration_Advisor/library-of-type-systems-740136b.md","title":"Library of Type Systems — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"The library of type systems is a collection of message templates that are provided by agencies that maintain the B2B/A2A/B2G standards."},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integration_Advisor/runtime-artifacts-d016138.md","title":"Runtime Artifacts — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"They comprise a set of automatically generated, processable schemes \\(XSD\\) and transformation scripts \\(XSLT\\) that facilitate:"},{"url":"https://raw.githubusercontent.com/SAP-docs/btp-integration-suite/33f339544cd06d3c4e272fe8ef57c7248f68c6a2/docs/ISuite_Integration_Advisor/inject-mapping-artifacts-to-sap-cloud-integration-47ad97e.md","title":"Inject Mapping Artifacts to SAP Cloud Integration — SAP Integration Suite documentation, SAP-docs/btp-integration-suite","checked":"2026-09-20","quote":"You can inject mapping artifacts from Integration Advisor to your SAP Cloud Integration tenant."}]},"drafted_with_ai":true,"framing_by_ecosystem":{"btp":{"description":"Settling what a business message looks like between partners who use different standards, such as UN/EDIFACT, ASC X12 and SAP IDoc, and mapping one onto the other: the interface specification, the mapping, and the schemas and transformations generated from them. Executing those in middleware is [integration flows](capability:integration-flows), and accepting XML on a service of your own is [XML payloads](capability:xml-payloads)."}},"history":[{"date":"2026-10-17","field":"description","from":"Settling what a business message looks like between partners who use different standards, such as UN/EDIFACT, ASC X12 and SAP IDoc, and mapping one onto the other: the interface specification, the mapping, and the schemas and transformations generated from them. Executing those in middleware is [integration flows](capability:integration-flows), and accepting XML on a service of your own is [XML payloads](capability:xml-payloads).","to":"Defining 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](capability:integration-flows).","reason":"Keep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit."}]},"sap_delivery":{"door":"btp","all":{"built_in":[],"documented_pattern":[],"announced":[],"packages":[{"ref":"artifact:btp-integration-advisor","name":"Integration Advisor","json":"/artifacts/btp-integration-advisor.json"}]},"by_flavor":{}},"edges":{"use_cases":[],"shared_tasks":[],"related_tasks":[],"options":[{"ref":"artifact:btp-integration-advisor","name":"Integration Advisor","json":"/artifacts/btp-integration-advisor.json","ecosystem":"btp","origin_ring":"sap-official"}],"samples":[],"explained_by":[{"ref":"content:completing-the-b2b-migration-into-sap-integration-suite-vision","name":"Completing the B2B migration into SAP Integration Suite vision","json":"/content/completing-the-b2b-migration-into-sap-integration-suite-vision.json"},{"ref":"content:teched-2026-in161","name":"Onboard a trading partner from agreement to live monitoring","json":"/content/teched-2026-in161.json"}],"normative_context":[]}}