I hear, “how can this matter?” Letting the borders of EDI fade overwhelms operational support as well as weakens EDI products and services.
Keeping clear what is and is not EDI is critical.
In the later portion of my career I spent a great deal of time at companies with EDI problems. Which is, of course, why I was hired. They needed someone with years of experience and knowledge. I love these opportunities. Many of these roles have been in EDI support. We used to lament about how much of what we did was not EDI. My purpose for this blog is helping companies keep EDI pure, simple and successful. Discerning what is EDI and what is not EDI without basic EDI knowledge and understanding is very confusing. The differences seem insignificant.
EDI is the methodology of translating between application data and EDI Standards so trading partners can integrate their systems. EDI and ERP applications should be lightly coupled. Meaning they sit next to each other communicating only through import and export files.
When a company allows their EDI system to take on ERP application functions soon everything becomes EDI. Much of the data that comes into any large company arrives via EDI. Because data came in through EDI does make EDI responsible for that data throughout the corporation. If we can keep EDI components unpolluted and lightly coupled; EDI is simple. Otherwise support becomes unmanageable.