| 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 and Evaluation
Sales
Commerce Portal – Primary EDI
Description
Customer- and distributor-facing digital channel supporting end-to-end Lead-to-Cash interactions.
Enables product discovery, pricing, cart & checkout, order tracking, document access, and support through a single portal.
Integrated in real time with SAP and CRM, designed as the strategic digital front door for customers.
Why Primary
Aligns with SyWay and ERP Rebuild To-Be architecture and digital ambitions.
Provides a single, standard onboarding channel for new customers and distributors.
Supports real-time, transactional processing rather than document exchange only.
Reduces manual handling and dependency on legacy EDI platforms.
Enables future capabilities (self-service, AI support, analytics, digital revenue growth).
Ensures consistent customer experience across GBUs (“One Syensqo”).
Elemica – Secondary EDI
Description
VAN-based B2B integration platform used for structured exchange of orders, shipping, inventory, and settlement documents.
Currently supports a set of key and strategic customers with established, high-volume integrations.
Provides stable, proven connectivity for customers with long-standing Elemica dependencies.
Why Secondary (and not Primary)
Several key and strategic customers are already deeply integrated with Elemica and have explicitly indicated no appetite to migrate to a new EDI or portal channel.
Forcing migration would introduce commercial risk and potential disruption to critical revenue streams.
Elemica ensures business continuity for these customers without impacting ongoing operations.
However, Elemica is not aligned with the long-term SyWay / ERP Rebuild strategy, which favors SAP-native, API-driven, and portal-based interactions.
Retaining Elemica as Primary would:
Prolong dependence on a VAN-based model
Increase long-term cost and complexity
Slow down adoption of standardized digital channels
Positioning Elemica as Secondary allows:
Protection of strategic customer relationships
Controlled, exception-based usage
Prevention of further expansion of the Elemica footprint
| Comparison Factor | Commerce Portal (Primary EDI) | Elemica (Secondary EDI) |
|---|---|---|
| Strategic role | Standard, default customer interaction channel | Exception-based EDI for selected customers |
| Customer eligibility | Can be used by any customer or distributor | Limited to specific, strategic customers |
| Onboarding approach | Standardized, scalable onboarding | Project-based onboarding (per customer) |
| Customer willingness | High for new and standard customers | Low for some strategic customers |
| Integration model | SAP-integrated, API-driven, real-time | VAN-based, message-oriented |
| Process coverage | End-to-end Lead-to-Cash | Transactional document exchange |
| Scalability & future readiness | High – supports digital growth | Low – footprint must be controlled |
| Governance need | Light (standard rules) | Strict exception governance required |
Recommendation:
Commerce Portal is the Primary EDI, as it is scalable, reusable, and applicable to all customers.
Elemica remains Secondary, as each onboarding requires a dedicated project and some strategic customers are unwilling to migrate.