EDI vs API: is EDI still used, and what replaces it?
Retailers still send their suppliers EDI compliance guides. APIs have arrived beside EDI, not in place of it. What each one is, when a supplier meets which, and what has to be right either way.
Insights, tutorials, and news from the world of quantum computing
Retailers still send their suppliers EDI compliance guides. APIs have arrived beside EDI, not in place of it. What each one is, when a supplier meets which, and what has to be right either way.
Practitioners on SAP, JD Edwards, SYSPRO, Infor and Acumatica describe the same EDI failures in different vocabularies. Nearly all of them are a unit code, a location number, a part number or a pack level in the wrong place, owned by no one.
Many of the ERPs Australian suppliers run have no translator of their own. EDI arrives through a partner adaptor, and the adaptor's choice of door decides how upgrades, licences and failures behave.
I read what the people who run SAP, NetSuite, Dynamics, Epicor, Acumatica, Odoo, IFS, Infor, JD Edwards and SYSPRO say about EDI in their own forums. The ERP opens a door, something else does the EDI, and the ASN is where it hurts.
Most EDI rejections are not EDI problems. They are product, pack and location data problems that the mapping transmitted faithfully. Here is how the dependencies work and what to validate.
What the EDI implementation process involves when a retailer wants purchase orders, ASNs and invoices by a date: the sequence, who does what, and what must be ready in your ERP before the first test.