BlogBlogtypeA post on somebody's own site or a community platform. Nobody edits it after publication, so it dates from the day it was written.See every one →SAP Community

Implementing B2B Advisory in SAP Integration Suite for Custom XML EDIFACT Scenario Part - 3

Builds 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.

Where it sits

Explains
Trading partner agreementsBTPTrading partner agreementscapabilityKeeping 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 mapping](capability:b2b-message-mapping), and executing the exchange is [integration flows](capability:integration-flows).Trading Partner ManagementBTPTrading Partner ManagementservicePartner profiles, agreement templates and agreements for B2B exchange, pushed into the Partner Directory of [Cloud Integration](artifact:btp-cloud-integration) so one flow serves every partner, inside [SAP Integration Suite](artifact:btp-integration-suite).
Source
reachable

Who is behind it

amysh95author

Properties

About this work

declared and crawled
Published
declared
Published on
declared
Views
crawled
1,136

More on this3

Group by
Piece, what it offersStill applies
Completing the B2B migration into SAP Integration Suite vision
SAP Community, DG
nothing recorded
More than 100 trading partners, one platform: Scalable B2B at Algoma Steel
SAP TechEd — session catalogueThe reasoning
nothing recorded
Onboard a trading partner from agreement to live monitoring
SAP TechEd — session catalogueThe reasoning
nothing recorded

Details

Graph6 edges
POINTS OUT →
explainsTrading partner agreementscapability, core only
published onSAP Communitypublishing source
discovered viaSAP Communitybtp-tag
discovered viaSAP Communitycloud-integration-tag
discovered viaSAP Communityintegration-suite-tag
Source
History1
  • Entered the atlasDiscovered via SAP Community · btp-tag, SAP Community · cloud-integration-tag, SAP Community · integration-suite-tag.
For your agent
Ref
content:implementing-b2b-advisory-in-sap-integration-suite-for-custom-xml-edifact-scenar
JSON
/content/implementing-b2b-advisory-in-sap-integration-suite-for-custom-xml-edifact-scenar.json
MCP
Connecting an agent