axway.com
7
Interoperable EDI and API Gateways
Some B2B processes involve complex, multi-party
interactions where multiple types of messages, exchange
protocols, and exchange channels are commonplace.
This is especially true for wide order-to-cash processes
involving custom declarations, invoice payment, and
tracking of shipment. These B2B transactions can be API-
based or EDI-based.
Examples of EDI-based transactions include the classical
document exchanges such as purchase orders, shipment
notices, and invoices. Examples of API REST/web services
B2B transactions include traceability of shipment, exception
handling on damaged items or interrupted process. B2B
transactions that may use either EDI, web services or REST
APIs, include customs declarations (manifest declarations)
as a consumed service and customs response as an
exposed service.
EDI standards have come a long way in helping small
businesses use an integrated, interoperable EDI and API
data exchange system, going so far as to define API access
to EDI exchanges and thereby allowing enterprises to
integrate 100% of their B2B partners.
API-based transactions can include complementary
services that aren't built into EDI standards — services
that provide visibility into transport tracking, statistics on
volumes, SLAs and error rates. They also include interactive
exception management such as transport cancellation and
exception notification.
Partners Enterprise
Supply Chain
Providers
Logistics 3rd Party
T&L
Warehouse
API GATEWAY
Warehouse
Finance
Japanese
Customs
German
Customs
3rd Party
Assistance
Suppliers
Support
manifest
declaration
EDI, API
Small Partners
EDI GATEWAY
Order, Invoice
Exception
management
APIs
Declaration
Acceptance
APIs
EDI GATEWAY
API GATEWAY
In an interoperable EDI and API gateway, a multiple
combination of API- and EDI-based transactions work in
concert to serve the same order-to-cash process.
Statistics APIs
Delivery Tracking
APIs
