PathFinder for traditional EDI


Electronic Data Interchange (EDI) has been used as a means of exchanging business documents in electronic form between trading partners for some twenty years now.

During this period, a number of national and international bodies have created 'standard' message structures to handle specific business documents. For many businesses, this is an integral part of their infrastructure and these internationally-agreed formats are still the best way of exchanging their data. These standards tend to be referred to as 'traditional' EDI standards, to distinguish them from the more recent XML-based and deregulated methods of document exchange.

Such formats include:

PathFinder is used by many customers exactly because, as well as its other abilities with data exchange and application interfacing, its open Syntax design means that it completely supports the traditional EDI standards. Any traditional EDI message can be received and transformed into either a file that can be imported into an application (XML Interface file, SAP IDoc, etc), a report that can be sent by email or viewed in a browser, or a CSV file that can be viewed as a spreadsheet. Similarly, any Interface file or spreadsheet CSV file can be transformed back into an EDIFACT or Tradacoms (or any other traditional format) and sent off to a trading partner.

PathFinder communications are independent of the actual file format transmitted, and so traditional EDI data can either be exchanged directly with a trading partner using such protocols as AS/2 or FTP, or sent via a mailbox on a Value Added Network (VAN) according to business requirements.

Please see the sidebar for PathFinder's other abilities in the areas of data exchange and as a middleware application.