EDI Insights & Facts: July 2025

Saturday, 26 July 2025

Widely used EDI middleware applications in the market

Some widely used EDI middleware applications in the market along with the companies name:

1. Cleo Integration Cloud (CIC)

Company: Cleo
Key Features: EDI integration, API support, file transfer, dashboards, hybrid integration.
Popular For: Logistics, manufacturing, and retail integrations.

2. OpenText Trading Grid

Company: OpenText
Key Features: Cloud-based EDI, secure B2B communication, trading partner onboarding.
Popular For: Enterprise-level EDI solutions and compliance.

3. IBM Sterling B2B Integrator

Company: IBM
Key Features: Advanced EDI integration, supply chain visibility, partner onboarding.
Popular For: Large enterprises with complex B2B networks.

4. Seeburger BIS (Business Integration Suite)

Company: Seeburger
Key Features: B2B/EDI, MFT, API integration, cloud & on-premise support.
Popular For: Manufacturing, automotive, and logistics sectors.

5. SPS Commerce Fulfillment

Company: SPS Commerce
Key Features: Pre-built retailer connections, EDI document automation, analytics.
Popular For: Retail EDI, especially for suppliers.

6. TrueCommerce

Company: TrueCommerce
Key Features: Cloud EDI, order processing, inventory visibility, eCommerce integrations.
Popular For: Mid-size businesses and eCommerce integrations.

7. Boomi (Dell Boomi)

Company: Boomi (a Dell Technologies business)
Key Features: API and EDI integration, drag-and-drop workflows, cloud-native.
Popular For: Fast-growing businesses and hybrid environments.

8. MuleSoft Anypoint Platform

Company: Salesforce (MuleSoft)
Key Features: API-led connectivity, B2B integration, secure data exchange.
Popular For: Enterprises needing API + EDI strategies.

9. Axway B2B Integration

Company: Axway
Key Features: Secure file transfer, API + EDI integration, community management.
Popular For: Regulated industries like finance and healthcare.

10. DiCentral (Now part of TrueCommerce)

Company: DiCentral (acquired by TrueCommerce)
Key Features: Cloud EDI, ERP connectors, supply chain visibility.
Popular For: EDI with global reach.

Friday, 18 July 2025

Understanding about AS4 (Applicability Statement 4)

What is AS4 in EDI?

AS4 (Applicability Statement 4) is a modern secure web services-based communication protocol used for B2B data exchange, especially in EDI (Electronic Data Interchange). It is a successor to AS2, offering enhanced security, reliability, and flexibility using SOAP and web services standards.

Key Components of AS4 Architecture

Component	Description
SOAP Envelope	AS4 uses SOAP 1.2 for message structure.
ebMS Header	Metadata such as sender, receiver, message ID, and action.
Payload	Can be any type (XML, EDIFACT, X12, etc.).
WS-Security	Ensures message encryption, signature, and integrity.
Reliability	Built-in retry, duplicate detection, and delivery tracking.
P-Mode	Configuration setting that governs how messages are exchanged between partners (like service agreements).

Understanding about SAP Port Configuration

In SAP EDI/IDoc processing, a port defines how IDocs are sent or received between systems,

Integration Scenarios

SAP to SAP
SAP to middleware (like Sterling, Boomi, Cleo, SAP PI/PO)
SAP to a file directory

Types of Ports in SAP:

Port Type	Description
tRFC (Transaction RFC)	Used for real-time IDoc transmission to another SAP system
File Port	Writes IDocs to a file (e.g., for middleware like Cleo, Seeburger, etc.)
ABAP-PI	Internal communication through ABAP proxy (used in SOA/web services)
XML HTTP	Sends IDocs as XML over HTTP(S)
Directory (EDI)	Sends IDoc to file system (common for outbound interfaces)

Where to Configure:

Use transaction WE21 to configure ports.

Why Port Is Important:

When SAP triggers an IDoc, it uses:

Partner profile (WE20)
Output type (e.g., BA00)
Port (defined in WE21)

If the port is misconfigured or missing, you'll get errors like:

Error while writing IDoc to file (EA084)
Port does not exist
No authorization to write file

EDI Insights & Facts