Contact (+45) 4324 5424    I   E-mail: sales@bording.dk    I     Support and download Center     I     AGETOR Wiki      I     About Bording Data

EDI and VANS suppliers

EDI stands for Electronic Data Interchange and is employed all over the world for e-commerce between companies. Despite the new XML-based formats, and national initiatives like the Danish OIOUBL, many companies still prefer EDI.

Covers the needs for electronic integration
 The most widespread EDI standard is EDIFACT, but common to all EDI standards is that they define a very large number of standard documents. Companies that do business together find most of their electronic integration needs manageable with EDI.

VANS suppliers transport EDI documents
When two companies exchange EDI documents the exchange is facilitated through a connecting link named VANS (Value Added Network Supplier). VANS reads the individual companies’ EAN numbers and uses this information to transport documents to the right places. 

For public authorities and private companies
OIOUBL (Former OIOXML) has replaced all electronic communication between private companies and public authorities in Denmark, and it has become widespread among private companies. Nevertheless, EDI is still a strong player, especially within the industrial sector and with companies that do business across national borders. Therefore, hardly any large companies can manage doing business without using EDI. 

Why use AGETOR for business integration with EDI?
AGETOR converts between EDI and the format your ERP system supports. Typically your business partners communicate in various EDI formats, and instead of creating integrations between the ERP system and every single EDI format, it is usually a good idea as a customer to define an intermediate format – an in-house XML format. AGETOR converts all inbound EDI formats to this intermediate format and then to the format supported by your ERP system. Thus, it is only necessary to create the integration to the ERP system once.

Make it simple
If your ERP system already supports a flexible XML format, it is not necessary to define an intermediate format. Instead, AGETOR will base the conversion on the flexible XML format, to which you can attach customer-specific integrations in whatever format needed, via such means as scripting or the effective XML tools included in AGETOR.

Common Shape

AGETOR for EDI integration offers you:

  • EDI integrations examples. You receive several examples on how to create EDI documents. For example, with regard to  EDIFACT93A invoices, orders and order confirmations. When creating your EDI integration project, you can start out with these examples.

  • Easy conversation of EDI. An “EDI2XML filter” is included, which makes it easy to convert to XML from EDI. You will receive several examples on how to use the filter to receive EDI documents as well. 

  • To archive archive inbound and outbound EDI documents. Use AGETOR archives to store all inbound and outbound EDI documents. During an auditing process you will find all documents in the archives, and if something goes wrong, and for example if you need to reload an order, you can do this from the AGETOR archives. 

  • Support for effective scripting tool. Our experience has taught us that it is too complex and too expensive to process XML using XSLT, Java or C#.NET. Scripting tools such as Groovy and Javascript, provide a far more effective annotation and can be compressed for much easier data manipulation. Amongst others, AGETOR supports Groovy with code completion and integration with AGETOR SDK (Software Development Kit). You can also add scripts as a part of the AGETOR transformations.