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.
In the United States, organizations traditionally follow ASI standards (ANSI ASC X12_) for EDI document formats. Outside the United States, the international standard is referred to as Electronic Data Interchange For Administration, Commerce and Transport (EDIFACT). DEACOM ERP provides a configurable setup to allow companies to tailor their EDI setup to support the two major standards.
Although there are global standards, the setup in DEACOM still needs to be configured for individual companies based on their business processing rules. Often times, trading partners or their Value Added Networks (VANs) only partially conform to the standards, use custom formats, or conform to the standards but have special pieces of information that must be communicated. The flexibility of the configurable setup in DEACOM facilitates every file format the company has seen to date.
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 some of the configurations are listed below along with their common identifier and if they are pulling data into (inbound) or out (outbound) of the ERP system:
|Transaction||Common ID||Inbound / Outbound|
|Purchase Order Acknowledgement||855||Outbound|
|Advanced Shipment Notice||856||Outbound|
|Warehouse Shipping Advice||945||Inbound|
|Functional Acknowledgment||997||Inbound / Outbound|
Inbound transactions are mapped via the flexible EDI designer 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.
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 works with any VAN. However, we do have a relationship in place with SPS Commerce. The Deacom team has configured many instances 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 but does require a working knowledge of the configuration tool. The process is typically done in two steps:
Training on the mapping process is available in the following forms with DEACOM: