EDI-Integration in NAV
Electronic Data Interchange (EDI) is a standard for the electronic exchange of certain company documents, such as orders, bills, and particular reports or confirmations. It is a part of electronic commerce, especially in the transporting of goods. As the documents in question must comply with specific standard templates, it is used mainly for recurring transactions.
There are a number of EDI standards, such as EDIFACT (developed by the United Nations), ANSI X12, TRADACOMS (British supermarkets) and ODETTE (Automotive industry). EDI is also used in the free energy market. In the Netherlands, a special standard has been made for the energy market, and is called EDINE. Today, these standards are being increasingly taken over by open standards such as XML.
Most software vendors provide a "hard-coded" EDI solution. Nevertheless, this tool is difficult to maintain and very expensive. A more modern approach is, however, to remain using this rather inflexible means, but to entrust the mapping to a third party who does the mapping for you. The disadvantage of this is that some of the data mapped is provided by the less flexible interface.
Our approach with regard to EDI is to actually develop one single mapping tool that enables you to map any Navision Data Element without having to resort to customized work.
We have been successful in integrating a similar EDI tool into Navisolutions.
There are a number of EDI standards, such as EDIFACT (developed by the United Nations), ANSI X12, TRADACOMS (British supermarkets) and ODETTE (Automotive industry). EDI is also used in the free energy market. In the Netherlands, a special standard has been made for the energy market, and is called EDINE. Today, these standards are being increasingly taken over by open standards such as XML.
Most software vendors provide a "hard-coded" EDI solution. Nevertheless, this tool is difficult to maintain and very expensive. A more modern approach is, however, to remain using this rather inflexible means, but to entrust the mapping to a third party who does the mapping for you. The disadvantage of this is that some of the data mapped is provided by the less flexible interface.
Our approach with regard to EDI is to actually develop one single mapping tool that enables you to map any Navision Data Element without having to resort to customized work.
We have been successful in integrating a similar EDI tool into Navisolutions.