EDI refers to a process that involves using electronic communications to complete transactions between two organizations, called "Trading Partners". For many manufacturers and distributors EDI is no longer a choice – it has become a requirement for doing business with their customers. By moving to this method of conducting business, many benefits can be realized including lower operational costs, higher efficiency, better supply chain visibility, and improved accuracy.
There are several EDI standards. ANSI X12 is generally used in North America, while EDIFACT is used most commonly outside of North America. DEACOM ERP provides a configurable setup to allow companies to tailor their EDI needs to support these two major standards and other data formats.
A Value Added Network (VAN) is the intermediary between trading partners that facilitates the communication of the data. VANs help trading partners streamline the development of their EDI files by providing addition translations from trading partners into formats that can be read by their internal systems. Some trading partners do allow files to be sent directly to them, but most require a VAN to facilitate the transaction for security and configuration purposes.
DEACOM provides a highly flexible and configurable set of tools allowing companies to maximize the value of implementing EDI transactions. A list of common configurations are listed here along with their X12/EDIFACT identifier and their direction (inbound or outbound).
Inbound transactions are created via a flexible EDI mapping tool within the software. Outbound transactions are configured via triggers in DEACOM. The nature of the trigger functionality allows for any outbound EDI functionality to be supported.
|Sales Order Transactions||X12/EDIFACT||Inbound / Outbound|
|Purchase Order (Sales Order)||850/875/ORDERS||Inbound|
|Purchase Order Acknowledgement||855/ORDRSP||Outbound|
|Advanced Shipment Notice||856/DESADV||Outbound|
|Purchase Order Transactions|
|Purchase Order Acknowledgement||855/ORDRSP||Inbound|
|Advanced Shipment Notice||856/DESADV||Inbound|
Data files can be formatted in a variety of ways based on the industry, trading partner and VAN. DEACOM supports a number of different formatting structures including:
EDI transactions can be completed via a number of different communication protocols or methods. DEACOM supports the following protocols for communication via a VAN or directly to the trading partner:
DEACOM ERP software has successfully worked with many VANs such as SPS Commerce, Digital Movers, Covalent Works, Sterling Commerce, and GXS to name a few. However, we do have a relationship in place with SPS Commerce. The Deacom team has standardized many maps with SPS Commerce and companies can take advantage of this close integration to streamline their mapping processes.
Implementing EDI in DEACOM does not require a developer to complete the mappings. However, it does require a working knowledge of EDI standards and format requirements along with the ability to use the built-in EDI configuration tool and trigger functionality. The process is typically done in three steps:
Implementing the EDI process is available in the following forms with Deacom: