Shipment Document VDA Version 3.2, July 2018

Transcription

1 Shipment Document VDA 4939 Version 3.2, July 2018 Copyright VDA 2017

2 VDA Version 3.2, July 2018 Shipment Document 2 Process description This VDA recommendation defines a uniform shipping document to act as a transport document and goodsaccompanying slip, which are herewith combined as a Transport and shipment document according to VDA 4939 (referred to as TSD below). This recommendation responds to the growing demands on the part of suppliers/loaders, forwarders/carriers and vehicle manufactures/recipients in terms of the accompanying documents used during transportation by truck. Documents that comply with this recommendation can also be used for other methods of transport. The legislation, regulations and requirements relating to goods transport must be adhered to in all cases and always take precedence over the recommendations set out below. In the case of cross-border transport, this also applies to the national regulations applicable in the relevant countries. If the SD is used as set out in the present recommendation, then previously used documents such as delivery notes, EDI shipping lists, shipping orders/consignment notes and possibly also company-specific pick-up and transport documents should become unnecessary for national transport. Any exceptions must be agreed on between the parties involved. Disclaimer The VDA Recommendations are recommendations that may be freely adopted by anyone. Users are responsible for correct implementation of the recommendations as required on a case-by-case basis. The recommendations take into account the prevailing technology at the time of publication. Use of the VDA Recommendations does not absolve anyone from responsibility for his/her own actions, and all users act at their own risk. Liability of VDA and those involved in drafting of VDA Recommendations is excluded. If you notice any errors, omissions or ambiguities in these recommendations, please contact VDA without delay so that these errors can be rectified. Publisher Copyright Verband der Automobilindustrie e.v. (VDA) Behrenstrasse 35, Berlin This recommemdation was developed by ICT Working Committee (AK KIT) Verband der Automobilindustrie e.v. (VDA) Reprint, also in extracts, is only permitted, if the source is stated. Status July 2018 Version Version 3.2

3 VDA Version 3.2, July 2018 Shipment Document 3 Table of contents 1 Short description of the document Objectives Fundamental principles and definitions Document and information flow in the delivery process Assignment of documents Document types Creation of the document and document format Document language Interaction of EDI and documents Shipment document Document/information flow Creating and scanning the 2D code Document design and structure Document concept and layout General requirements for the form Use of data blocks Shipment master Shipments of materials (delivery schedule and JIT processes) Shipments of materials (JIS processes) Empty packaging process Shipment line items (excluding JIS deliveries) Shipment document line item sheet JIS deliveries D code sheet List of loading units Content and structure of the data fields Creating 2D code Structure of the 2D code Symbol counter Message structure according to ISO User data for coding in Data Matrix Generating a data string as described in ISO/IEC for coding in Data Matrix References to standards... 44

4 VDA Version 3.2, July 2018 Shipment Document 4 List of changes Version Release Changes 3.0 July 2016 First release 3.1 November 2017 Shipment master for empty packages added 3.2 July 2018 JIS-line item sheet added

5 VDA Version 3.2, July 2018 Shipment Document 5 1 Short description of the document 1.1 Objectives Standard documents help optimize the conduct of transport operations. They should support all shipping concepts such as JIT, forecast delivery schedules, and JIS. Different forms are combined in a single set of documents. By taking account of the possible uses of individual document types, it is possible to achieve very low levels of data redundancy. The use and contents of the SD can (and must) be harmonized and organized between the various parties in the light of the requirements of the transport and delivery process. All the data relating to a shipment (as in the EDI delivery note and transport data) can be entered using a twodimensional code (2D code) on the shipment master sheet where it can be made available for automatic processing. This recommendation on the SD has been harmonized and optimized for use in parallel with despatch advices as described in VDA As well as fulfilling its role as a goods-accompanying document, the TSD can also assist in the emergency measures taken in the event of problems during the electronic communication of despatch advices. 1.2 Fundamental principles and definitions The regulations regarding the issue of consignment notes in accordance with German road haulage legislation (Güterkraftverkehrsgesetz) and CMR 1 were taken into account. Any changes to regulations must be adhered to and always take precedence over the recommendations below. Loaders (shippers) of dangerous goods must adhere to the requirements for transport documents according to section of the German regulations pertaining to the transportation of dangerous goods by road and rail (GGVSE/ADR). The current version of these regulations has been taken into account in the present recommendation. An additional accompanying form for dangerous goods is not usually required. Data fields are also available for specifications relating to dangerous goods. The data must be entered in compliance with the above-mentioned regulations. Retention requirements and periods must be adhered to as set out in the applicable (national) commercial and fiscal legislation. Printed or stamped documents are permitted in the place of handwritten documents. VDA recommendation 4939 does not contain a separate glossary of terms. The meanings of the terms used in the present recommendation are explained in VDA recommendations 4999 (Glossary of logistics terms in the automotive industry) and These definitions were drawn up by VDA AK-KIT and DSLV. 1 Convention on the Contract for the International Carriage of Goods by Road

6 VDA Version 3.2, July 2018 Shipment Document 6 2 Document and information flow in the delivery process 2.1 Assignment of documents Figure 1: Goods-accompanying documents in the delivery process For details regarding the labels attached to the loading unit we refer to VDA recommendation Global Transport Label Document types The shipment document consists of Master sheet and Line item sheet 2D code sheet List of loading units The master and line item sheets may extend over several pages. The shipment master sheet can also fulfill the function of the consignment note in the case of national transport operations. The shipment document contains the data corresponding to a shipment.

7 VDA Version 3.2, July 2018 Shipment Document Creation of the document and document format The documents are printed on blank paper (white). Pre-printed forms must not be used. Any additionally required copies of the document must be printed separately. The number of copies must be defined by the parties involved in the light of the requirements of the process. The format is A4 as set out in ISO 216. Letter format is also permitted. If letter format is used then the width of the Delivery note column in the line item sheet must be reduced accordingly. Longer delivery note numbers may then be broken over two lines as a result of this. The pages must be printed on one side only and must be sequentially numbered Document language The document language is German. In the case of cross-border deliveries, the blocks (field names and header lines) must be designated in English. In the case of national deliveries or upon mutual agreement by the parties, the language of the receiver's country may be used. The contents of the fields on the shipment documents intended for the receiver (shipment master sheet and shipment line item sheet) must be entered in the receiver's national language. Alternative agreements are permitted. In the case of cross-border deliveries, it may be necessary or mandatory to enter texts and data in the shipment master sheet and/or the shipment line item sheet in the language of the country of dispatch or in another language. It may also be necessary to print the documents (or individual document types) in several different languages. Alternative or additional languages may be used if this is required by legal regulations. In the case of international transport operations, for example, these may be specified as customs or transport notes on the shipment master sheet. 2.2 Interaction of EDI and documents The SD is generated on the basis of the same data that is used to create the despatch advice as per VDA Shipment document The shipment document accompanies the shipment until it arrives at the receiver's premises. When the shipment document is used for national transport operations within the European Union then it is no longer necessary for the shipper to complete a shipping order, EDI shipping list or delivery note. Despite this, in the case of international transport operations, it may still be necessary to issue separate CMR consignment notes.

8 VDA Version 3.2, July 2018 Shipment Document 8 Binding delivery Shipper Supplier Receiver Customer Transport order Despatch advice Transport Pick-up list Delivery data (combined shipment) Loading Forwarder CC Pick-up Grouped load Complete load Shipment document VDA 4939 with master, line item, 2D code sheets and list of loading units. Combined shipment Figure 2: Interaction of EDI messages and documents 2.3 Document/information flow In the delivery process used within the automotive industry, it is normal for freight forwarding contracts to be issued within the framework of long-term supply agreements. According to VDA 5002, the content and execution of a freight forwarding contract is documented by means of a shipping order which clearly refers to a shipment. In the past, this shipping order (=transport order to the forwarder) was issued using the VDA 4922 shipping order form. In principle, the shipment master sheet can perform this function. In the pick-up process according to VDA 5004, the operational transport order is issued by the receiver. It can be issued as an EDI transport order or in an agreed paper form. The receiver's transport order acts as a shipping order which, in turn, represents a practical implementation of the long-term supply agreement. The shipment documents are drawn up by the shipper/supplier and given to the driver. In the case of shipments that are not transported by truck, the documents have to be enclosed with the goods. During transportation or on pick-up, the forwarder/carrier can manually add data that was not available to the supplier at the time of pick-up. The shipper may request a proof of delivery from the carrier and obtain a copy of the document set or of individual document types (e.g. the shipment master sheet) from the driver of the vehicle. When a shipment is delivered, the shipment document is presented to the recipient on the arrival of the truck or taken from the packing in the case of other shipping methods. The carrier may request a copy of the shipment document confirmed by the receiver and arrange for this to be handed over to its vehicle driver as proof of delivery.

9 VDA Version 3.2, July 2018 Shipment Document Creating and scanning the 2D code Data Matrix ECC200 should be used as the two-dimensional code. The requirements set out in the ISO/IEC standard must be observed. The data must possess the structural characteristics described in ISO and as are also required, for example, by the automotive industry's Global Transport Label. In the shipment 2D code sheet, selected delivery note and transport data that is generated in parallel must be stored in a 2D code (see section 4.2.1). The 2D code makes it possible to automatically scan (read and capture) the document data. If none of the parties involved in the delivery process wishes to make use of the option of automatically capturing this data then the parties may agree to dispense with the shipment 2D code sheet. For detailed information on creating the 2D code, see section 4 3 Document design and structure 3.1 Document concept and layout General requirements for the form The distance between the printed area and the edge of the sheet must not be less than 6 mm on any side. If portrait format is used then a value of 15 mm is recommended for the left-hand margin and if landscape format is used then this same value is recommended for the top margin. The data blocks must be visually separated from one another by means of a frame constructed from single lines. The various aspects of the layout are specified in greater detail in the following sections Use of fonts The dimensions given in this recommendation for tables, columns, fields and field lengths are based on the use of the proportional fonts ARIAL or, alternatively, HELVETICA. For the suggested font sizes, see sections 3.6 Character sets other than those described in may only be used if both parties in the process agree to this. They must then define the font sizes themselves accordingly Use of character sets The character set used in the shipment document may correspond to that used in the EDI message DESADV according to VDA 4987 (UNOA, UNOB or UNOC, see ISO 9735). In the examples and figures presented here, it is assumed that the UNOC character set is used Numerical formats The specification of numerical values is subject to the same rules as in the EDIFACT message: leading zeros must be deleted and decimal places are specified only in the length relevant for the value that is to be communicated. This is generally dependent on the unit of quantity Use of data blocks The field sizes correspond to practical requirements. The requirements expressed by members of the VDA, Verband der Automobilindustrie e.v., as well as by members of the DSLV, Deutscher Spediteur- und Logistikverband e.v., have been taken into account as far as possible. There are no regulations governing the size (height) of the data blocks, with the exception of the header line. The size depends on the amount of data present. By refusing to state any such formal requirements, it is possible to make optimum use of the pages in the document. The following data blocks are as described in Appendix A1.1. If

10 VDA Version 3.2, July 2018 Shipment Document 10 the shipment does not contain any dangerous goods then the Dangerous goods information block can be omitted from the shipment document. Page breaks within a data block should be avoided. Block D of the master sheet and the blocks in the shipment line item data can be spread across page breaks. If a block is split over two pages then the table header must be repeated on the next page. 3.2 Shipment master Shipments of materials (delivery schedule and JIT processes) The shipment master sheet is printed on A4 paper (alternatively: Letter) in portrait format. The layout is detailed in figure 3. Explanations on the data blocks Block A Header data This block is printed on the shipment master and the line item sheets and contains information about the supplier, shipment number and shipment date, as well as a page count indicator. Block B Address and reference data of the partners involved Address data and ID of the shipper, receiver and forwarder of the goods, the loading and unloading points, the DUNS number of the shipper. Block C Further information on the shipment Block D List of loading units in the shipment Package ID: Unique ID of the shipping unit (Unique Shipping ID) - if block D is longer than the space available on the page then the table is split and continued on the next page. Block E Comments If necessary, further information can be printed (or even written by hand) here. Such information might refer, for example, to stacking-related issues or bearing loads, in particular if standard packing is not used. If transport registration numbers are assigned by the authorities (e.g. the EKAER number in Hungary) then these can be printed here. Block F Dangerous goods information Must be completed if the shipment contains dangerous goods. Otherwise this block can be omitted completely. Block G Fixed sentence on load securing. This must be printed on all shipment documents and acknowledged by the loader or driver. Block H Acknowledgment info Used to record the take-over and reception dates and is also signed by the participants. Page layout A filing margin of 15 mm must be left on the left-hand side and the top, bottom and right margins should be 5 mm. Other dimensions can be taken from the following figures.

11 VDA Version 3.2, July 2018 Shipment Document 11 Figure 3: Shipment master form with measurements

12 VDA Version 3.2, July 2018 Shipment Document 12 Figure 4: Shipment master with sample data

13 VDA Version 3.2, July 2018 Shipment Document Shipments of materials (JIS processes) Figure 5: Example of a shipment master sheet for JIS deliveries

14 VDA Version 3.2, July 2018 Shipment Document 14 For generation of the JIS-shipment master the following rules apply: 1. TPU is a JIS package with compartments: only one line for each TPU with gross, net and tare weight. 2. TPU is a JIS package as simplified handling unit: only one line with gross, net and tare weight. 3. TPU is a pallet or similar with SLCs: one line for the TPU with gross and tare weight, and for each group of SLC a line with gross, net and tare weight. 4. Intermediate packages are treated the same way as for other material deliveries. 5. Supplier or customer has to define unique packaging type codes in format an..7 and to store them in the relevant master data tables. 6. One or more TPU pet delivery note. It is forbidden to split a TPU into several delivery notes.

15 VDA Version 3.2, July 2018 Shipment Document Empty packaging process For empty packaging an additional data block D2 is defined: Figure 6: Master sheet for empty packaging shipments

16 VDA Version 3.2, July 2018 Shipment Document 16 Explanations on the data blocks Block A D1: as for material shipments, A3 can be used to print the DMC Block D2: summarised list of all packaging types in the shipment (type, quantity, name or description) Block E H: as for material shipments

17 VDA Version 3.2, July 2018 Shipment Document 17 Figure 7: Example shipment master sheet for empty packaging deliveries

18 VDA Version 3.2, July 2018 Shipment Document Shipment line items (materials, excluding JIS deliveries) Landscape format should be used for the shipment items. The table size has been chosen in such a way that the Letter paper format can also be used while still maintaining the required minimum page margins. If the A4 format is used then the form can be printed centred accordingly with large margins.

19 VDA VERSION 3.2, JULY 2018 SHIPMENT DOCUMENT 19 Figure 8: Table layout for the shipment line item sheet Copyright VDA 2017

20 VDA Version 3.2, July 2018 Shipment Document 20 Figure 9: Example of a completed shipment line item sheet with one article reference, packaged on a pallet in five SLCs. 3 empty SLCs are used to fill the layer and the bundle is covered by a lid.

21 VDA Version 3.2, July 2018 SHIPMENT DOCUMENT 21 Explanations on the data blocks Block A Header data This block is printed on each shipment line item sheet and contains information about the supplier, shipment number and shipment date, as well as a page count indicator. Each of the columns is 9 cm in width and the height of the block is 3 cm. Block B Line item data Headings the lines containing the headings are printed once on each line item sheet. The font is Arial, 8 Pt., Bold. Line A Article data The article and delivery note data is entered in this line in 10-point font size. Quantity = Total delivery quantity for the line items in the delivery note - it is recommended that the line is grayed by % for highlighting. Line B Other references Optional line in which any other references relating to the line items in the delivery note can be specified. Field label: 8 pt; Data content 10 pt. Line C Package information The package information is communicated in this line (columns 1 to 3 and 5). The filled quantity of each package is indicated in column 5. For those packages containing the parts (inner packages or simplified handling units) and bearing a single label the part number shall be printed again in column number 3. Lines A, B and C form logically associated blocks and are transferred as a separate table for each delivery note line item. Line C must be used for each package type. If the quantities per package are different, then line C has to be repeated for each quantity per package. In lines A through C, the text should be printed at a distance of 2 points from the top and bottom cell border. Note: A loading unit or a group of several identical loading units shall be listed completely including all inner packaging items and auxiliary packaging (a.k.a. as packaging aid). Only after completion of one group of identical loading units or of an individual loading unit the next group of or individual loading unit shall follow. Lines A, B and C should be grouped as follows depending on the packing and/or pakage assembly structure: Simplified handling unit with single type of package - Part number information and quantities (line A) - Possible also reference specifications (line B) - Loading unit (type, number, etc.) (line C) - Auxiliary package for the loading unit (if present) (line C) - === End of simplified handling unit Loading unit with single type of package - Part number information and quantities (line A) - Possible also reference specifications (line B) - Loading unit (type, number, etc.) (line C) - Auxiliary package for the loading unit (if present) (line C) - Intermediate package (if present) (line C) - Auxiliary package for intermediate packages (if present) (line C) - === End of loading unit level - Internal packages (type, number, filling quantity) packages of the same type and same filling quantity should be combined. (Line C) - Auxiliary package for internal package (if present) (line C) Loading unit with mixed packages - Loading unit (type, number, etc.) (line C) Copyright VDA 2017

22 VDA Version 3.2, July 2018 Shipment Document 22 - Loading unit (unique shipping ID) (line C) - Auxiliary package for the loading unit (if present) (line C) - Intermediate package (if present) (line C) - Auxiliary package for intermediate packages (if present) (line C) - === End of loading unit level - Part number information and quantities (line A) - Possible also reference specifications (line B) - Internal packages (type, number, filling quantity) packages of the same type and same filling quantity should be combined. (Line C) - Auxiliary package for internal package (if present) (line C) Detailed examples of these groupings can be found in Appendix Shipment document line item sheet JIS deliveries For JIS deliveries Block B is defined as follows:

23 VDA VERSION 3.2, JULY 2018 SHIPMENT DOCUMENT 23 Figure 10 Line A: Label number and packaging type code, font: Arial bold, size 12 pt.; a distance of 2 mm should appear before each line A Line B: Manufacturing reference number, call-off group, assembly line / place of consumption, sequence number, compartment number, inner JIS-label number, JIS-info font: Arial, header 8 pt., data 10 pt. Copyright VDA 2017

24 VDA Version 3.2, July 2018 Shipment Document 24 Figure 11: Sample data for a JIS line item sheet

25 VDA Version 3.2, July 2018 Shipment Document 25 Explanation: 3JUN ABC : 1 JIS-package with 4 compartments, each containing one JIS-module 3JUN ABD : 1 JIS-package with a re-ordered module 1JUN ACD : 1 JIS-package with 1 JIS-module 3JUN AEC : 1 JIS-package with 4 compartments for 2 manufacturing reference numbers 4JUN ABCXX000001: 1 JIS-package with 4 SLC, each containing one JIS.module 4JUN ABC : 1 JIS-package with intermediate packages (3J), each containing 2 SLC. The SLC do not bear an own label, because they are never delivered to the assembly line separately.

26 VDA Version 3.2, July 2018 SHIPMENT DOCUMENT D code sheet The 2D code sheet is created in A4 or Letter format in portrait orientation. It possesses the same form header as the shipment master sheet, block A. Figure 12: Header of the 2D code sheet with example data. The code sheet contains selected user data coded in Data Matrix format (see section User data in Data Matrix format ). Multiple Data Matrix symbols can be printed next to one another and below one another. The total size of the symbols depends on the number of modules in the matrix and the resolution (see section Creating 2D codes ). Figure 9 shows a 2-column arrangement with 4 symbols of 120 x 120 modules of 0.3 mm each, resulting in a size of 36 x 36 mm (see section 4 Creating 2D codes ). If the maximum number of characters is used for each 2D symbol and the module size is 0.5 mm then the width of each symbol is approximately 7.2 cm. A 2-column arrangement with two symbols per column is possible and recommended. Figure 13 2D code sheet with symbols of size 120 x 120 modules x 0.3 mm, 1573 characters per symbol on 36x36 mm (capacity of the 4 symbols: 6292 characters). Copyright VDA 2017

27 VDA Version 3.2, July 2018 Shipment Document List of loading units This layout of the shipment documents is intended to carry the complete list of all package IDs (license plates respectively JIS-label-numbers) belonging to shipments loading units. In the list, the ID without data identifier (DI) is printed. The IDs are printed on the labels of the loading units as well (Master / Mixed /Single). The completeness of the shipment can be checked manually using this list, if necessary. Sections Block A - Header data This block is printed on the shipment master and the line item sheets and contains information about the supplier, shipment number and shipment date, as well as a page count indicator. Block B - List of loading units Package IDs of all loading units Block H Acknowledgment info Used to record the take-over and reception dates and is also signed by the participants.

28 VDA Version 3.2, July 2018 Shipment Document 28 Figure 14: List of transport loading units (TPU)

29 VDA Version 3.2, July 2018 Shipment Document Content and structure of the data fields Content EDI source Format EDI Format Form Font Size Pt. Block/ Line Comment Shipment - Master Document date DTM+11 DE 2380 n8 an..10 Arial 12 Block A CCYY-MM-DD or DD.MM.CCYY Shipment number SG1 RFF+CRN an..35 an..19 Arial 18 Block A Ship-from (SF) Name SG2 NAD+SF DE 3036 an..35 an..23 Arial 12 Block B SF Name 2 SG2 NAD+SF DE 3036 an..35 an..23 Arial 12 Block B SF Steet SG2 NAD+SF DE 3042 an..35 an..23 Arial 10 Block B SF Country SG2 NAD+SF DE 3207 a2 a2 Arial 10 Block B SF Pst code SG2 NAD+SF DE 3251 an..17 an..9 Arial 10 Block B SF Location SG2 NAD+SF DE 3164 an..35 an..25 Arial 10 Block B SF Supplier number SG2 NAD+SF DE 3039 an..20 an..20 Arial 10 Block B SF DUNS number Point of loading ID Point of loading text SF VAT ID SG2 NAD+SF/RFF+ANK DE 1154 SG2 NAD+SF/LOC+9 DE 3225 SG2 NAD+SF/LOC+9 DE 3224 SG2 NAD+SF/RFF+VA DE 1154 n9 n9 Arial 10 Block B an..17 an..17 Arial 10 Block B an..256 an..23 Arial 10 Block B an..17 an..23 Arial 10 Block B Ship-to (ST) Name SG2 NAD+ST DE 3036 an..35 an..23 Arial 12 Block B ST Name 2 SG2 NAD+ST DE 3036 an..35 an..23 Arial 10 Block B Copyright VDA 2017

30 VDA Version 3.2, July 2018 Shipment Document 30 Content EDI source Format EDI Format Form Font Size Pt. Block/ Line ST Steet SG2 NAD+ST DE 3042 an..35 an..23 Arial 10 Block B ST Country SG2 NAD+ST DE 3207 a2 a2 Arial 10 Block B ST Post code SG2 NAD+ST DE 3251 an..17 an..9 Arial 10 Block B ST Location SG2 NAD+ST DE 3164 an..35 an..25 Arial 10 Block B ST ID SG2 NAD+ST DE 3039 an..20 an..20 Arial 10 Block B ST DUNS Unloading point ID Unloading point Text SG2 NAD+ST/RFF+ANK DE 1154 SG2 NAD+ST/LOC+11 DE 3225 Alternatively SG10/SG17/SG20 LOC+11 DE 3225 SG2 NAD+ST/LOC+11 DE 3224 Alternatively SG10/SG17/SG20 LOC+11 DE 3224 n9 n9 Arial 10 Block B an..17 an..23 Arial 10 Block B an..17 an..23 an..256 an..23 Arial 10 Block B an..256 an..23 Block B Forwarder (FW) Name SG2 NAD+FW DE 3036 an..35 an..23 Arial 12 Block B FW Name 2 SG2 NAD+FW DE 3036 an..35 an..23 Arial 10 Block B FW Street SG2 NAD+FW DE 3042 an..35 an..23 Arial 10 Block B FW Country SG2 NAD+FW DE 3207 a2 a2 Arial 10 Block B FW Post code SG2 NAD+FW DE 3251 an..17 an..9 Arial 10 Block B FW Location SG2 NAD+FW DE 3164 an..35 an..25 Arial 10 Block B FW ID SG2 NAD+FW DE 3039 an..20 an..20 Arial 10 Block B Comment

31 VDA Version 3.2, July 2018 Shipment Document 31 Content EDI source Format EDI FW DUNS SG2 NAD+FW/RFF+ANK DE 1154 Format Form Font Size Pt. Block/ Line n9 n9 Arial 10 Block B Comment Shipment date / time DTM+11 DE 2380 n..12 an..20 Arial 11 Block C CCYY-MM-DD, HH:MM time is optional Transport mode (name) SG6/TDT DE Name an3 an..30 Arial 11 Block C Process identification BGM DE 1000 an..35 an..20 Arial 11 Block C Milkrun-/Call-off number Transport number Required delivery date & time SG1/RFF+AAN/AVU DE 1154 SG6 TDT DE 8028 oder SG1 RFF+AAO DE 1154 DTM+2 DE 2380 (JIT Prozesse) an..35 an..20 Arial 11 Block C an..17 an..20 Arial 11 Block C n..12 an..20 Arial 11 Block C Alternative DTM+132 DE 2380 (LAB) n..12 an..20 Arial 11 Block C Transport means-id SG6/TDT DE 8213 an..35 an..20 Arial 11 Block C INCOTERM Customer s packaging type code resp. bundle type (if used) for empty packaging SG5/TOD DE LOC+1 DE 3225 an3 + an..35 an..20 Arial 11 Block C SG11/PAC DE 7065 an..17 an..13 Arial 11 Block D/D1 Not the code but the name of the codes Source DTM+2 or DTM+132 DTM+132 to be calculated= Shipment date + transport time (from master data for that relation) TPU indicator SG10 CPS+++3 n1 an1 Arial 11 Block D/D1 Loading units are marked with X Number of packages / TPUs SG11/PAC DE 7224 n..6 n..5 Arial 11 Block D/D1

32 VDA Version 3.2, July 2018 Shipment Document 32 Content EDI source Format EDI Gross weight in kg loading unit (bundle) Gross weight in kg simplified loading unit Tare weight in kg loading unit (bundle) Tare weight in kg simplified loading unit Tare weigtht in kg Auxilliary packaging (PAC with code 37) Stackability of TPUs for transport SG16/MEA+AAZ+AAB DE 6314 SG11/MEA+AAY+G DE 6314 SG16/MEA+AAZ+T DE 6314 SG11/MEA+AAY+T DE 6314 SG11/MEA+AAY+T DE 6314 SG11/MEA+ABU DE 6314 Format Form Font Size Pt. Block/ Line n..12 n..7 Arial 11 Block D/D1 n..12 n..7 Arial 11 Block D/D1 n..12 n..7 Arial 11 Block D/D1 n..12 n..7 Arial 11 Block D/D1 n..12 n..7 Arial 11 Block D/D1 n..3 n..2 Arial 11 Block D/D1 Delivery note number SG17/RFF+AAU DE 1154 an..35 an..11 Arial 11 Block D/D1 Total number of loading units MEA+AAE DE 6314 n..6 n..5 Arial 11 Block D/D1 Total gross weight in kg Total tare weight in kgt Total net weight in kg MEA+AAX+AAD DE 6314 n..12 n..5 Arial 11 Block D/D1 MEA+AAX+T DE 6314 n..12 n..5 Arial 11 Block D/D1 MEA+AAX+AAL DE 6314 n..12 n..5 Arial 11 Block D/D1 Package type code (empties) SG17/LIN DE 7140 an..17 an..13 Arial 11 Block D2 Sum of all packages of this type SG17/QTY DE 6060 n..6 n..5 Arial 11 Block D2 Dangerous goods information SG19/DGS DE an..256 an..256 Arial 11 Block F Comment Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions Optional with decimal point and decimal fractions

33 VDA Version 3.2, July 2018 Shipment Document 33 FTX+AAD Content EDI source Format EDI Format Form Font Size Pt. Block/ Line Comment Shipment line item sheet Delivery note number SG17/RFF+AAU DE 1154 an..35 an..14 Arial bold 10 Line A delivery note line number SG17/RFF+AAU DE 1156 an..6 an..6 Arial bold 10 Line A Customer's part number SG17/LIN DE 7140 an..35 an..30 Arial bold 10 Line A Short description SG17/IMD DE 7008 an..256 an..30 Arial bold 10 Line A Total delivery quantity SG17/QTY+12 DE 6060 n..10 n..10 Arial bold 10 Line A Unit of measure SG17/QTY+12 DE 6411 an..3 an..3 Arial bold 10 Line A See table of measure units Engineering change index SG17 PIA DE 7140 an..35 an..10 Arial 10 Line A Usage (name) SG17/IMD DE 7009 an..2 an..11 Arial 10 Line A 11 = series, 12 = spare part Order number SG17/RFF+ON DE 1154 an..35 an..12 Arial 10 Line A Internal destination SG2/NAD+ST LOC+7 DE 3225 an..35 an..25 Arial 10 Line A Alternatively SG17 LOC+7 DE 3225 an..35 an..25 Arial 10 Line A Place of consumption SG17/LOC+159 DE 3225 an..35 an..25 Arial 10 Line A Other references To be printed with qualifying text Batch number SG14/GIR+1 an..35 an..35 Arial 8 Line B Batch No.:: + value from GIR+1 Best before date SG14/DTM+361 an..8 an..10 Arial 8 Line B Best before: + value SG14(2) DTM+361 Manufacturing date SG14/DTM+94 an..8 an..10 Arial 8 Line B Production date: +value SG14(2) DTM+94,

34 VDA Version 3.2, July 2018 Shipment Document 34 Content EDI source Format EDI Format Form Font Size Pt. Block/ Line Comment Expiry date SG14/DTM+36 an..8 an..10 Arial 8 Line B Expiry date: + value SG14(2) DTM+36 Order No. wholesaler SG18/RFF+UC an..35 an..35 Arial 8 Line B Individual order No. SG18/RFF+COF an..35 an..35 Arial 8 Line B Order No. depot SG18/RFF+AAA an..35 an..35 Arial 8 Line B Invoice No. SG18/RFF+IV an..35 an..35 Arial 8 Line B Number of packages SG11/PAC DE 7224 n..4 n..4 Arial 10 Line C Label type (name) SG13/PCI DE 7511 an..2 an..10 Arial 10 Line C Following terms to be used: 1J = SINGLE 5J = MIXED 6J = MASTER Inner packages belonging to a mixed bundle have to be marked with an (X) after the label type: SINGLE(X) Package type code SG11/PAC/DE 7065 an..17 an..10 Arial 10 Line C Part number SG17/LIN DE 7140 an..35 an..30 Arial 8 Line C For inner packages belonging to a mixed bundle the part number has to be repeated. Quantity per pack SG10/CPS+++1 or 4 /SG11 QTY+52 DE 6060 n..35 n..10 Arial 10 Line C

35 VDA Version 3.2, July 2018 Shipment Document 35 Content EDI Source Format EDI JIS Line item sheet Format Form Data Identifier SG13.PCI+17.DE7511 an..2 an..2 Arial bold 12 Line A License Plate SG15.GIN+ML.DE7402#2 an..22 an..22 Arial bold Package type code SG11.PAC.DE7065 an..17 an..17 Arial bold 12 Line A Manufacturing reference No. SG14.GIR+4 AN an..35 an..24 Line B Call-off group SG14.GIR+4 XA an..35 an..15 Line B Assembly line SG14.GIR+4 XN an..35 an..15 Line B Place of consumption SG17.LOC+159 an..35 an..15 Line B Compartment number SG15.GIN+AO an..35 an..15 Line B Font Size Pt. Line Comment inner JIS-Label number SG15.GIN+ML.DE7402#2 An..22 an..22 Line B With DI Sequence number SG14.GIR+4 XO an..35 an..15 Line B JIS-Info SG14.GIR+4...XQ an..35 an..17 Arial 10 Line B 12 Line A Customer may require a certain system of generating this number List of loading units Unique package ID SG15/GIN+ML / GIN+BU an..35 an..35 Arial 10 License Plate (without data identifier)

36 VDA Version 3.2, July 2018 Shipment Document 36 The following abbreviations shall be used for measure units in the shipment document: Table 1: Measure unit codes UN/EDIFACT Form DE Form EN Name PCE / C62 ST PC Piece SET SET SET Set MTR M M Metre CMT CM CM Centimetre MMT MM MM Millimetre MTK M2 M2 Square metre MTQ M3 M3 Cubic metre LTR L L Litre LEF BL LF Leaf PR PA PA Pair RO RO RO Roll KGM KG KG Kilogram GRM G G Gramm KMT KM KM Kilometre TNE T T Ton (metric) 4 Creating 2D code The Data Matrix code is used so that selected data on the shipment document can be scanned automatically. The data contents are indicated in Figure 12. The aim of this procedure is to support the goods-in and other registration processes involved in transport operations. The Data Matrix ECC200 code printed on the shipment documents must comply with the standards ISO/IEC The associated test and quality standard is ISO/IEC The minimum height/width of the modules (x) is 0.25 mm and these should not exceed 0.5 mm (see Figure 11). The recommended module size is 0.3mm (12 mil). The minimum width for a module is 3 points, recommended 4. Figure 15: Module size of Data Matrix symbols (x) A value of ten modules is recommended for the quiet zone (white area) around the Data Matrix. This applies to each of the symbols printed next to, below or above one another, with the result that the quiet zone is doubled in this case. Copyright VDA 2017

37 VDA Version 3.2, July 2018 Shipment Document 37 The print quality is regulated by ISO/IEC The quality is specified as a grade, which is determined by a 2D verifier on the basis of the sum of individual measurements. The minimum quality grade is 1.5/0.25/660: 1.5: Minimum quality grade at the point of creation = Grade 1.5 (equivalent to alpha grade C ); 0.25: Verifier measurement aperture = 0.25 mm; 660: Measurement wavelength = 660 nanometers +/- 10 nanometers Data Matrix provides 24 quadratic symbol sizes from 10 x 10 through 144 x 144 modules. The maximum size of a single 2D symbol is 144 x 144 modules. In the case of alphanumeric data, the maximum recording capacity of one 2D symbol is 2335 characters. However, the recommendation is not to exceed the size of 120 x 120 modules (capacity 1,573 characters) because not all scanners have sufficient memory for the maximum size. The total size of a quadratic Data Matrix symbol is obtained by multiplying the module size by the number of modules per side. To this, it is necessary to add the quiet zone which separates the code from the edge of the symbol. At a recommended symbol size of 120x120 modules and a module size of 0.3 mm/12 mil, the Data Matrix code requires space of 36x36 mm plus a quiet zone of 10 points. This leads to a space requirement of 39x39 mm. Symbol sizes of 120x120 modules plus quiet zone in different resolutions: Module 0.25 mm/10 mil: 30x30 mm Module 0.3 mm/12 mil: 36x36 mm Module 0.4 mm/16 mil: 48x48 mm Module 0.5 mm/20 mil: 60x60 mm Character sets 1. Values in accordance with ISO/IEC 646. The G0 set and C0 set are used. In the C0 set, characters 28 to 31 are modified and map FS, GS, RS and US. Characters 32 to 127 correspond to EDIFACT UNOB. 2. Values 128 to 255 in accordance with ISO (also known as extended ASCII). This character set corresponds to EDIFACT UNOC. 4.1 Structure of the 2D code The data that is to be transported can be coded in one or more 2D symbols depending on data volume. Each Data Matrix symbol contains a submessage which is itself fully coded in ISO/IEC syntax. In all cases, if the data stream for coding has to be split and taken over into the next symbol then this occurs after the end of a complete data element. Every symbol contains a counter which specifies symbol number x out of total number of symbols y when the defined sequence for the DI 4F is used (see section Symbol counter ). Any required number of symbols can be used in order to map a contiguous data record or data stream. After being scanned, and irrespective of the sequence in which this occurs, the data contents of the symbols are arranged in their original sequence by the downstream data capture system. In every Data Matrix, the data stream starts with the control character Macro 06 (character 237) which indicates that data identifiers are used in accordance with ISO/IEC 15418, part ANS Data Identifiers. The control character Macro 06 replaces the ISO/IEC control sequence with preamble [)>RS06GS before the data and postamble RSEOT. at the end of the data string for each symbol The separator character between the individual data elements introduced by the ASC data identifiers (DI s) is the Group Separator G S (see section 4.2 Message structure according to ISO/IEC ).

38 VDA Version 3.2, July 2018 Shipment Document Symbol counter In messages that consist of more than one symbol, the symbol counter is specified in each symbol as the first data element after the header sequence. The data identifier is 4F. The description of the data element as a symbol counter is as follows, where the term page is used to describe the contents of a symbol. Logical assignment of a page (a symbol content) within a group of pages, which are distributed across multiple data media (as many as required), structured as a sequence of 1 to 3 subelements that are separated by forward slashes (/): Page number (required), followed by the number of pages (optional but required for the last page), followed by an alphanumeric group identifier (optional; if used, then for all pages, and in accordance with ISO/IEC , structured as a sequence of 3 data elements: IAC, CIN, reference number., unique within the domain of the labeler). Suffixed slashes are optional. For the current application for transport and shipment documents, it is more appropriate to use the shipment number than the group identifier according to ISO/IEC Example: DI: 4F Symbol (page) numbers: 1, 2, 3,... Number of symbols: 4 The group reference for the symbols is the shipment number Separator / Example of the symbol counter data element for 4 symbols: Symbol 1: 4F1/4/ Symbol 2: 4F2/4/ Symbol 3: 4F3/4/ Symbol 4: 4F4/4/ If the number of symbols is not determined until the last symbol, then the number of pages can be omitted on all the other pages. Nevertheless, the separating slash character is still printed. However, the total number of pages must be recognizable on the last page in order to be able to check for completeness. Example of the symbol counter data element for 4 symbols, the number of symbols is not known until the last symbol: Symbol 1: 4F1// Symbol 2: 4F2// Symbol 3: 4F3// Symbol 4: 4F4/4/ Message structure according to ISO15434 When the data contents of the Data Matrix symbols are coded as a message as described in ISO15434 then the message envelope is required with the header at the start and trailer at the end of the user data. The message is structured as follows: Message Header: [)>RS (string, hex 5B 29 3E 1E / dec ) Format Header: 06 (for structure with DIs) Group Separator: GS (hex 1D / dec 29) DI with user data Group Separator DI with user data Group Separator DI with user data

39 VDA Version 3.2, July 2018 Shipment Document 39 Group Separator... etc. Message Trailer: RS (hex 1E / dec 30) Record Separator: EOT (hex 04 / dec 04) Example of a message, where , , , etc. stand for the user data: User data for coding in Data Matrix The following user data is to be transferred in Data Matrix code for material deliveries: Table 2 Data to be coded in Data Matrix Code (materials) User data Shipment document for materials Source in DESADV DI State Comments Example data none 9K M ID for materials (9K)03 Shipment number RFF+CRN 2K M (2K) Goods shipper / supplier no., assigned by the customer DUNS (or Odette) number of goods shipper NAD+SF DE 3039 V M (V) NAD+SF/RFF+ANK DE V D Transfer the ID that was used to generate the license plate (13V) Goods receiver ID, assigned by the customer Goods receiver DUNS Unloading point ID Shipment date and time Milkrun/call-off number NAD+ST DE V M (8V) NAD+ST/RFF+ANK DE 1154 NAD+ST/LOC+11 DE V O (20V)UN ST 2L M (2L)49876 DTM+11 DE D 011 M YYYYMMDDHHMM Not converted into UTC SG1/RFF+AAN/AVU 5K D Only in the milkrun/call-off process (8D) (5K) D1

40 VDA Version 3.2, July 2018 Shipment Document 40 Transport reference number Required delivery date for shipment incl. time Number of loading units 1..n Unique shipping ID of the loading units TDT 8028 or RFF+AAO DE K (only RFF+AAO) D If available (5K) B2 DTM+2 DE D..002 O YYYYMMDDHHMM MEA+AAX+AAD DE 6314 SG13/PCI (Data Identifier) + SG15/GIN+ML resp. GIN+BU (JIS) Not converted into UTC Q M (Q)22 1J/5J/6J JIS: 3J/4J (8D) M License plate 2 (1J)UN (1J)UN (1J)UN Table 3: Data to be coded in Data Matrix Code (empty packages) User data Shipment document for empty packages Source in DESADV DI State Comments Example data none 9K M ID for empties (9K)T201 Shipment number RFF+CRN 2K M (2K) Goods shipper / supplier no., assigned by the customer DUNS number of goods shipper NAD+SF DE 3039 V M (V) NAD+SF/RFF+ANK DE V D Transfer the ID that was used to generate the license plate (13V) Goods receiver ID, assigned by the supplier (manager of empties) NAD+ST DE V M (9V) Goods receiver DUNS Shipment date and time Required delivery date for shipment incl. time NAD+ST/RFF+ANK DE V O (20V)UN ST DTM+11 DE D 011 M YYYYMMDDHHMM Not converted into UTC DTM+132 DE D..002 O YYYYMMDDHHMM Not converted into UTC Number of loading MEA+AAE DE 6314 Q M (Q)22 (8D) (8D) Structure of the license plate according to ISO/IEC : <DI><IAC><CIN><SN>, example with DI 1J and IAC UN, DUNS No.: 1JUN

41 VDA Version 3.2, July 2018 Shipment Document 41 units 1..n Unique shipping ID of the loading units SG13/PCI (Data Identifier) + SG15/GIN+ML J O License plate 3 (J)UN (J)UN (J)UN State values: M = Mandatory field that must always be present, D = Depending, dependent on the process, e.g. call-off O = Option, optional field Note: If the document is used for empty packaging and the unique package IDs of the loading units are not encoded into the DMC, the field A3 can be used for the DMC containing the remaining data Generating a data string as described in ISO/IEC for coding in Data Matrix The generation of the data string from the user data will be explained in seven software-assisted steps. 1) Preparation of the data: Each user data field is assigned a DI. 2) Creation of the data string by sequencing the user data fields using the group separator as separator, but initially without header and trailer. 3) Definition of the data volume: The data volume is counted together with separators 4) Determination of the number of symbols required: Define the maximum desired code size, e.g. 120x120 with capacity for 1573 characters, minus approx. 18 characters for counter and envelope, equals a total of 1555 characters. Because a data element introduced by a DI cannot be split, the maximum license plate length of 35 characters must be included as a reserve, with the result that the capacity available for user data is 1520 (alphanumeric) characters. The final value is now determined by dividing the user data volume by the available capacity and rounding the result up to a whole number. If necessary, if the final symbol is exceeded by a small amount of data, then a smaller size of 36x36 (107 characters 1n) to 104x104 (1222 characters an) modules can be used for this symbol. 5) Subdivision of the data string into segments of maximum 1555 characters each. Note that self-contained data elements must not be split. 6) Generation of the symbol counter: The symbol counter is placed before the first user data field and is introduced by DI 4F. 7) Completion of the data string so that the symbols can be printed: Addition of the Message Header Sequence at the start and the Message Trailer Sequence at the end of the message Example of the generation of the Data Matrix symbols 1) Preparation of the data: This example uses the data from Figure 12 Table of user data in Data Matrix 2) Creation of the data string from the user data: 9K03 GS 2K GS V GS 13V GS 8V GS 2L49876 GS 8D GS 5K D15011 GS 8D GS Q22 GS 1JUN GS 1JUN GS 1JUN ) Definition of the user data volume: A count of the data assuming 123 characters of header data (see Fig. 12, fields 9K to Q22) plus 4000 characters for 200 packages with license plates of 20 characters each (incl. GS ) results in 4123 alphanumeric (an) characters 3 Structure of the license plate according to ISO/IEC : <DI><IAC><CIN><SN>, example with DI 1J and IAC UN, DUNS No.: 1JUN

42 VDA Version 3.2, July 2018 Shipment Document 42 4) Determination of the number of symbols required: The calculation performed assuming a target size of 120x120 modules per symbol, or capacity for 1573 characters minus 18 characters for the control sequences for syntax and symbol counter characters (an) and reserve characters, results in a net capacity of 1520 characters (an). This number, divided by the identified user data volume of 4123 characters, gives the number of symbols required. In this case: 4123:1520=2.71 symbols. When rounded up, this means that 3 Data Matrix symbols of size 120x120 modules are needed to code the user data. 5) Subdivision of the data string into 3 segments for 3 symbols, the final data element in the data section remains self-contained: Data section for symbol 1 (header data plus 69 unique shipping IDs=1503 characters): 9K03 GS 2K GS V (13V) GS 8V GS 2L49876 GS 8D GS 5K D15011 GS 8D GS Q22 GS 1JUN GS 1JUN GS 1JUN GS... to GS 1JUN Data section for symbol 2 (76 unique shipping IDs=1520 characters): GS 1JUN GS 1JUN GS 1JUN Data section for symbol 3: (remaining 55 unique shipping IDs=1100 characters) GS 1JUN GS 1JUN GS 1JUN ) Generation of the symbol counter: 3 symbols are determined: There are 3 counters in accordance with the section Symbol counter : Symbol 1: 4F01/03/ Symbol 2: 4F02/03/ Symbol 3: 4F03/03/ ) 7) Completion of the data string: A header, symbol counter and trailer sequence are added to each of the separated data segments: Data segment for symbol 1 of 3: [)> RS 06 GS 4F01/03/ GS 9K03 GS 2K GS V V GS 8V GS 2L GS 8D GS 5K D15011 GS 8D GS Q22 GS 1JUN GS 1JUN GS 1JUN GS... to GS 1JUN RS EOT Data segment for symbol 2 of 3: [)> RS 06 GS 4F02/03/ GS 1JUN GS 1JUN to. GS 1JUN RS EOT Data segment for symbol 3 of 3: [)> RS 06 GS 4F03/03/ GS 1JUN GS 1JUN to. GS 1JUN RS EOT Consequently, each segment has now been prepared for transfer to the printing system. Figure 16 Figure 17 Figure 18 Figures 16 through 18 illustrate the example symbols 1 to 3 in the format 120x120 modules, all printed with a module size of 0.3 mm/12 mil, 36 mm x 36 mm.

43 VDA Version 3.2, July 2018 Shipment Document 43 Fig. 19 presents an extract from the data information present in symbol 1 after scanning. Symbols 2 and 3 would follow the same example.... continued at transport unit

44 VDA Version 3.2, July 2018 Shipment Document 44 Figure 19: Display of the data read from symbol 1 of 3 with unique shipping numbers 1 to 69, example illustration using diagnostic software 5 References to standards ANS MH Data Identifiers and Application Identifiers according to ISO/IEC ISO/IEC Bar code symbol print quality test specifications - Two-dimensional symbols ISO/IEC Syntax for high-capacity ADC media ISO/IEC Data Matrix