The EDI module provides users with a maximum amount of flexibility when dealing with trading partners. These tools can map any Navision data element to an ANSI X12 standard. Once the mapping is in place, the Transition Management tools allow users to easily manage the day-to-day process of conducting electronic commerce.

EDI is based on a set of ANSI standards.  Why is it so difficult to integrate into most business systems?

 Business systems are as diverse and varied as their names and oigins indicate. The EDI ANSI X12 standard provides a common intermediate format to conduct electronic commerce between trading partners. The interpretation and use of the data elements within these standards is determined by the EDI standards committee in each industry and further modified by the individual trading partners.

For example: The electronics industry has a different set of requirements than the retail distribution industry. Historically, software providers have produced a hard coded custom application to EDI which is rigid, expensive to maintain and modify. A better approach is to use an EDI logical mapping tool and pass along data between the traditional interfaces. But this is also problematic; the logical maping can only pass along data provided by the same rigidity.

Solution: A single mapping tool is provided that maps any Dynamics NAV data element to any EDI data element without additional programming. This tool is further augmented by the addition of specific trading partner packages that include already mapped transactions for major trading partners. These maps are templates that can easily be modified and maintained as the trading partners requirements change.

If it is that simple why doesn't every software provider take this approach?

Dynamics NAV's unique development and operational environment makes this logical mapping approach possible. For example, when a new field is required by one of your trading partners you have two options:
  1. Add the field to NAV and change the logical EDI map to recognize it.
  2. Change the EDI map to recognize an EDI virtual field, which is held in the EDI transaction database. This field can be viewed and updated from within Navision and mapped to an outgoing transaction where needed. Obviously this approach keeps your database modification minimal.