| Status | Edited following Approval |
| Owner | |
| Stakeholders |
Issue
The previous KDD066 established the principle of simplifying and standardizing EDI platforms by defining that each business process must have:
One Primary EDI system
One (optional) Secondary EDI system, allowed only by exception
However, at the time of KDD066 approval The Primary and Secondary EDIs listed in the table were indicative and are based on the conceptual Design understanding. As part of Detailed Design (SyWay), there is now a need to revisit each process from the KDD066 table and evaluate the options and Finalise the Primary and Secondary EDI. Along with that there is a need to establish a governance process in case any new EDI is required.
Recommendation
Background & Context
KDD066 established a strategic direction to simplify and standardise EDI platforms by:
Defining a Primary EDI per process
Allowing Secondary EDI only by exception
Reducing fragmentation and long-term operational complexity
KDD066 - EDI platforms in the f…
Since then, SyWay Detailed Design has delivered:
A clear To-Be integration architecture centred on SAP Integration Suite, APIs, events, and controlled legacy EDI coexistence for 3PLs
3PL SyWay TO BE Final
A clarified supplier collaboration strategy, including Ariba Network, Supplier Portal, and phased onboarding models
Ariba Network
Confirmed bank connectivity decisions (e.g. continued SWIFT Bureau usage)
SyWay - Workshop_ MBC recommend…
As a result, the indicative EDI assignments in KDD066 no longer reflect the executable To-Be design and must now be formally confirmed or adjusted.
| Area | Transaction | Primary EDI | Secondary EDI |
| Sales | Quotation | None | |
| Sales Contract | None | ||
| Sales Order | Elemica | Esker | |
| Billing | Customer Portal | Elemica , Tungsten, E-Invoicing, ARKHINEO | |
| Complaints | None | ||
| Procurement | RFx | None | |
| Catalogs | Ariba Catalogs | ||
| Contracts | None | ||
| Purchase Orders | Ariba Network | Elemica | |
| Order Confirmation | Ariba Network | Elemica | |
| ASN | Ariba Network | Elemica | |
| Service Entry Sheet | Ariba Network | Elemica | |
| Invoice | Ariba Network | Fedex , ProMaster , Synchro , Xerox , Ariba Network , E-Invoicing , Citibank , OpenText | |
| TM | Freight Orders | None | BluJay , Transwide, CASS |
| Invoices | None | CASS , TMS/CHEMLOGIX | |
| Truck Weight Update | None | Weighbridge Systems: Selfy Weighbridge, LAS, Weightbridge - Tecsidel, APAC Weighbridge Systems, Qbit Portaria | |
| Transport Event Update (via SAP BNL) | None | Selfy, Simba, Project 44, FDTMS | |
| Logistics | Inventory Management (Inc. Goods Receipt, Stock Transfer, Goods Issue, Stock on Hand etc.) | 3PL Template Interfaces | Arcese, Katoen Natie, Sunland Infor, Kenco, Mitsui Soko, PML CN, DHL CN |
| Inbound | None | Elemica | |
| Outbound | None | Elemica | |
| Goods Reciept | None | Elemica | |
| Finance | Payment | Swift | Swift , Bank Portals |
| GTS | Customs | None | Seeburger , COMEX , Jet etc.. |
Assumptions
Constraints
Impacts
Financial Impact
Business Rules
Options considered
Sales
Option A:
Option B:
Option C:
Option D:
Evaluation
Option A | Option B | Option C | Option D | |
|---|---|---|---|---|
| Criterion 1 |
|
|
|
|
| Criterion 2 |
|  Con |
|
|
| Criterion 3 |  Pro | Con | Con | Pro |