B2B message mapping

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, and accepting XML on a service of your own is XML payloads.

Overview

SAP SHIPS

Integration Advisor in SAP 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.

Not covered: At design time. The generated runtime artifacts are injected into a Cloud Integration tenant or exported, and an integration flow executes them.

THE COMMUNITY ADDS

No community artifact is documented here.

Artifacts1

1 of 1 artifacts
ArtifactSignals
Services1
Integration AdvisorB2B interface and mapping specification in Integration Suite
Signals
none

Content2

Group by
Piece, what it offers
Completing the B2B migration into SAP Integration Suite vision
SAP Community, DG, Blog
Onboard a trading partner from agreement to live monitoring
SAP TechEd — session catalogue, TalkThe reasoning

Details