Chat with us, powered by LiveChat
9 minute read

Electronic Data Interchange (EDI) with the Help of VDA Standards

Verband der deutschen Auto­mobil­industrie (VDA)

The Association of the Automotive Industry was founded in 1901 and is an interest group of the German automotive industry and its suppliers. The headquarters are located in Berlin.


VDA Headquarters in Berlin (Source: Wikimedia Commons
VDA Headquarters in Berlin (Source: Wikimedia Commons

The VDA is publicly known through the Internationale Automobilausstellung (IAA, International Automotive Exhibition), since they operate as their organiser. In addition to the representation of interests, VDA also undertakes standardisation tasks, with recommendations for logistical processes in the automotive sector to be adopted. Those recommendations established themselves throughout the years as the de facto standard of the German automotive industry.

The Development of the VDA Standards

Already in 1977, before even UN/CEFACT started to develop the EDIFACT standards, the Verband der deutschen Automobilindustrie began, defining EDI message standards, which were dedicated to the automotive industry and its suppliers. In contrast to EDIFACT or ANSI ASC X12, no segments or separators are used, but instead elements with constant length, called the fixed length format are used. Every data element has a defined length, within which the information can be transmitted. If the information is shorter than the defined length, the rest is filled out with blank spaces.

Numbering of the VDA Messages

Each VDA message type has a unique number, almost like a description. Message type 4905 describes for example a delivery forecast. At the end of this article you will find a list of the different VDA standards.

Current Development

The current fixed length VDA standards are gradually being replaced by EDIFACT document types. Therefore, the VDA association releases recommendations, on how EDIFACT messages can represent VDA document types. Nevertheless, the current VDA message types are still very frequently used in the automotive industry and one can expect this to still be the case in the coming years.

How are VDA Standards Being Used?

Depending on the car manufacturer, different VDA standards can be used. The following scenario, depicted with a delivery forecast and despatch advice, as well as the paper documents which go with it, come up very frequently. This example is of a pump manufacturer, who sends goods to a car manufacturer.


An Example of the Use of VDA Standards
An Example of the Use of VDA Standards

The car manufacturer forecasts the deliveries to the pump manufacturer with the help of a 4905 message. The pump manufacturer prepares the goods accordingly and confirms the delivery with a 4913 message. Next step is to ship the pumps, together with two paper documents: a barcode label 4902 together with the goods, which can be scanned with a barcode scanner and a paper-based goods slip 4912.

Are You Looking to Use VDA Standards?

The use of VDA standards is now required by more and more car manufacturers and their pre-suppliers. However, the implementation of the corresponding electronic document types and the paper documents which go with it, including the correct barcodes, is not so simple. We are more than happy to help you with any questions you might have about VDA.

List of VDA Standards

The list below gives you a (non-exhaustive) overview of the important standards, which the VDA association adopted (as of February 2015).

If you need to check a particular standard in detail, use the search function on the publication site of the VDA association. The links change from time to time, hence we are not able to include them here directly.

Nr. Description First Publi­cation
4900 Trans­mission of ODETTE mess­ages; EDIFACT pay­load Jan 91
4901 Enqu­iries/offer Oct 77
4902 Trans­port label (barcode enab­led) Sep 94
4903 Microfilm Apr 82
4904 Deli­very fore­cast May 83
4905 Trans­mission of call off Apr 96
4905/2 Trans­mission of call off based on ODETTE­-DELINS Ver­sion 3 Jan 91
4907 Trans­mission of remi­ttance advice Aug 93
4911 Trans­mission of price data Jan 89
4912 DFÜ goods slip Jan 91
4913 Trans­mission of deli­very notes and tran­sport data Mar 96
4914 File Tran­sfer Proto­col (FTP) – contains 4914/1 and 4914/2 Mar 88
4915 Trans­mission of detai­led call off (JIT) Apr 96
4916 Trans­mission of call off just­-in-­seque­nce May 91
4918 Trans­mission of vehicle identi­ficat­ion and trans­port data Apr 87
4919 Trans­mission of vehicle arrival and depar­ture notifi­cation; process descri­ption Apr 87
4920 Trans­mission of forward­ing instructi­ons (sender­/supplier to shi­pper) Apr 89
4921 Trans­mission of deli­very data (shipper to client/­goods receiver) Apr 89
4922 Form for the ship­ment of goods betw­een the suppl­ier, shipper and client – shipp­ing req­uest Jun 10
4923 Trans­mission of enqui­ries Jan 92
4924 Trans­mission of offer­/quotat­ion Jan 92
4926 Trans­mission of acknowl­edgment of order Sep 93
4927 Trans­mission of equip­ment state­ment and equip­ment move­ment Feb 97
4928 Check­list for produc­tion partners (system ­suppliers) with just in time deli­very in the inform­ation process­ing area; first publi­cation Aug 96
4929 AVIEXP: EDI for deli­very notes and trans­port data; VDA guide­line of the ODETTE subset AVIEXP V5R1 for UN/­EDIFACT message DESADV D96A Feb 98
4930 Trans­mission of inven­tory and stock move­ment informa­tion with exter­nal ware­housing Apr 93
4931 Packag­ing data sheet Apr 93
4932 INVOIC: EDI for invoices and credit notes data; VDA recom­menda­tion to ODETTE subset V5R1 for UN/­EDIFACT message INVOIC D97A May 99
4933 Standard­ised trans­port note/ shipping read­iness advice (inclu­ding labels) Jul 14
4936 Web EDI (part I) for the deploy­ment of call off data, the logg­ing and ship­ment of deli­very notes (ship­ment, trans­port and deliv­ery slip data), print­ing of the goods slip, and deploy­ment of the credit note data. Nov 01
4937 Auto­mated responses for deli­very notes part 0: process descript­ion and general infor­mati­on Mar 09
4937 P1 Auto­mated respo­nses for deli­very notes part 1: syntax and serv­ice report (EDIFACT CONTRL) Mar 09
4937 P2 Auto­mated responses for deli­very notes part 2: appli­cation error and confir­mation message (EDIFACT APERAK) Mar 09
4937 P3 Auto­mated respon­ses for deli­very notes part 3: receiv­ing advice notice (EDIFACT RECADV) Mar 09
4938 P1 Process frame­work for the exchange of elect­ronic invoi­ces with the use of EDIFACT without digi­tal sign­ature Apr 12
4938 P2 Global INVOIC appli­cation manual – data struc­ture (incl. labels) Jun 14
4938 P3 Elec­tronic invo­icing process with small and medium sized busi­nesses in the auto­motive industry (incl. labels) Dec 13
4938 P4 Freight invoice – data struc­ture for the exch­ange of invo­ice data for trans­port services. Dec 13
4939 Trans­port and shipping slips Dec 07
4940 Check­list for the deploy­ment of ODETTE mess­ages Aug 93
4941-1 Part 1: Packag­ing acc­ount over­view Feb 06
4941-2 Part 2: Packag­ing inven­tory report Feb 06
4941-3 Part 3: Packaging inventory discrepancy Feb 06
4942-4 Part 4: Packag­ing inven­tory correct­ion Feb 06
4942-5 Part 5: Packag­ing inven­tory delimitation Feb 06
4943 Packag­ing batch report Feb 06
4944 Packag­ing trans­port request Feb 06
4945 Packag­ing trans­port status Feb 06
4946 Packag­ing request acknow­ledg­ment Feb 06
4947 P1 Part 1: Packag­ing move­ment notice Feb 06
4947 P2 Part 2: Packag­ing recei­ving confir­mation Feb 06
4948 P0 Bypass/drop ship part 0: Pro­cess descri­ption and general infor­mation Oct 06
4948 P1 Bypass/drop ship part 1: order Oct 06
4948 P2 Bypass/drop ship part 2: order resp­onse Oct 06
4948 P3 Bypass/drop ship part 3: deli­very notice Oct 06
4949 Propo­sition about the standard­isation of the communi­cation for the except­ion handling of the supply chain in after­market May 07
4970 Trans­port preview for finished vehi­cles Jun 99
4971 Pick up order for fin­ished vehi­cles Mar 00
4972 Dispatch notice from plant­/base for fini­shed vehi­cles Mar 00
4973 Vehi­cle entry for fini­shed vehic­les Mar 00
4974 Vehi­cle exit for fini­shed vehic­les Mar 00
4975 Change/­informa­tion notice for fin­ished vehicles Feb 00
4976 Change/­informa­tion confirma­tion for fini­shed vehicles Mar 00
4977 Damage report for finished vehicles Mar 00
4978 Repair start/end notice for finished vehicles Mar 00
4979 Shipping readiness notice for finished vehicles Mar 00
4980 Loading instructions for finished vehicles Mar 00
4981 Usage of portal agents in the portal applications of the automotive industry Oct 11
4982 Data exchange between the companies of the automotive industry and the logistic service providers to fulfil the requirements of the import control system ICS of the European Union. Dec 11
4983 Transmission of attachments and signatures with EDIFACT messages (including labels) Mar 12
4984 Transmission of delivery forecasts (incl. labels) Jun 14
4985 Transmission of JIT call offs (incl. labels) Jan 13
4986 Transmission of production synchronous (JIS) call offs Jun 14
4987 Transmission of delivery notes (incl. labels) Jul 14
4988 Transmission of remittance advice with EDI (incl. labels) Dec 13
4989 Transmission of arrival confirmation Dec 13
4990 Inventory and stock movement report Feb 15
4991 Transmission of shipping notes (incl. labels) Apr 14
4993 Activity fields for portal managers Feb 15
4999 Glossary Mar 15

Questions?

Electronic Data Interchange (EDI) with the Help of VDA Standards? Feel free to contact us, we would love to help you!

subjects

most read

Keep on reading

Cookie Settings

All marketing cookies
LinkedIn (cn_LinkedINActive)
LinkedIn uses cookies so as to provide you with a personalised user experience and show you relevant content.
Google Analytics (cn_AnalyticsActive)
Used to send data to Google Analytics about the visitor's device and behaviour. Tracks the visitor across devices and marketing channels.
Facebook (cn_FacebookActive)
Used by Facebook to display a range of promotional products, such as third-party real-time bidding.
Google Adwords (cn_AddWordsActive)
Used to identify users visiting the website via Google Ads.
Pardot (cn_PardotActive)
Pardot uses cookies to make your interactions with our website more meaningful. They help us better understand what you’re looking for, so we can tailor content for you