Introduction
B2B integration supports EDIFACT, ANSI.X12, and TRADCOMS standards, depending on your partner and context. SAP Integration Suite offers several EDI integration flow steps for implementing such B2B scenarios.
Prerequisite:
Follow the steps mentioned below to set up the following B2B scenario: Partners exchange multiple ORDERS EDI payloads using TRADACOMS standards between partners and the SAP Integration Suite tenant. The partners would like to generate the outcome in XML format.
B2B Scenarios and Their Configuration:
The following screenshot shows the configuration of the EDI Splitter step. This step splits the inbound multiple ORDERS message into individual ORDER:
The partner uses the TRADACOMS XSD from the Partner Directory. Therefore, you need to add the following Partner Directory path in the Content Modifier step:
Note: The partner already placed the TRADACOMS_ORDHDR_FILE_9.xsd in its own Partner Directory
The configuration of the EDI to XML Converter step is shown in the following screenshot. This step processes individual EDI messages and converts them into a corresponding XML format:
Note: The same xsdName is be used in EDI to XML Converter step.
Deployment and Execution of the Scenario:
After you’ve finished the integration flow design as shown above, save and deploy the integration flow.
After successful deployment of the integration flow, copy the endpoint URL. Set up a request using an HTTP client (for example, Postman) and use the copied endpoint URL as address. In the request body pass the TRADACOMS ORDERS message type of version 9 which has multiple ORDERS.
This blog summarizes the steps required to create and run a B2B scenario based on TRADACOMS standard using SAP Integration Suite.
I hope you enjoyed reading the blog. Expect another interesting blog soon.
Related SAP Help Portal documentation:
B2B integration supports EDIFACT, ANSI.X12, and TRADCOMS standards, depending on your partner and context. SAP Integration Suite offers several EDI integration flow steps for implementing such B2B scenarios.
Prerequisite:
- You have obtained an SAP Integration Suite tenant with SAP Integration Suite standard edition and above licenses.
- TRADACOMS Schema (XSD) must be from Integration Advisor : With Integration Advisor, create message implementation guidelines (MIGs) and mapping guidelines (MAGs) for TRADACOMS. The runtime artifacts exported from the MIG and MAG will be used as schemas (xsd) for the EDI Splitter, EDI to XML Converter, and XML to EDI Converter steps.
Example of TRADACOMS schema (XSD): TRADACOMS_ORDHRD_FILE_8.xsd
Follow the steps mentioned below to set up the following B2B scenario: Partners exchange multiple ORDERS EDI payloads using TRADACOMS standards between partners and the SAP Integration Suite tenant. The partners would like to generate the outcome in XML format.
B2B Scenarios and Their Configuration:
Create an https-based integration flow using EDI Splitter (2.0 version) and EDI to XML Converter (2.0 version) components as below
The following screenshot shows the configuration of the EDI Splitter step. This step splits the inbound multiple ORDERS message into individual ORDER:
The partner uses the TRADACOMS XSD from the Partner Directory. Therefore, you need to add the following Partner Directory path in the Content Modifier step:
xsdName= pd:cPartner:TRADACOMS_ORDHDR_FILE_9:Binary
Note: The partner already placed the TRADACOMS_ORDHDR_FILE_9.xsd in its own Partner Directory
The configuration of the EDI to XML Converter step is shown in the following screenshot. This step processes individual EDI messages and converts them into a corresponding XML format:
Note: The same xsdName is be used in EDI to XML Converter step.
Deployment and Execution of the Scenario:
After you’ve finished the integration flow design as shown above, save and deploy the integration flow.
After successful deployment of the integration flow, copy the endpoint URL. Set up a request using an HTTP client (for example, Postman) and use the copied endpoint URL as address. In the request body pass the TRADACOMS ORDERS message type of version 9 which has multiple ORDERS.
This blog summarizes the steps required to create and run a B2B scenario based on TRADACOMS standard using SAP Integration Suite.
I hope you enjoyed reading the blog. Expect another interesting blog soon.
Related SAP Help Portal documentation:
| Related Integration Flow Step | Documentation |
| EDI splitter | Define EDI Splitter | SAP Help Portal |
| EDI to XML Converter | Define EDI to XML Converter | SAP Help Portal |
| XML to EDI Converter | Define XML to EDI Converter | SAP Help Portal |
| EDI Extractor | Define EDI Extractor | SAP Help Portal |
- SAP Managed Tags:
