User Guide en Ttssb Generator 3 4 0

TSB-Generator VOLKSWAGEN AG

User Guide

TSB-Generator

VDA4939

GTL

@VOLKSWAGEN AG Page 1 of 52 Version 1.33 May 2014


Contents

USER GUIDE ............................................................................................................. 1

CONTENTS ................................................................................................................ 2

1. INTRODUCTION .................................................................................................... 6 1.1 Objective ..................................................................................................................... 6 1.2 History ......................................................................................................................... 6

1.2.1 Version 1.0 ............................................................................................................. 6 1.2.2 Version 1.1 ............................................................................................................. 6 1.2.3 Version 1.2 ............................................................................................................. 7 1.2.4 Version 1.3 ............................................................................................................. 7 1.2.5 Version 1.3.1 .......................................................................................................... 7 1.2.6 Version 1.3.2 .......................................................................................................... 7 1.2.7 Version 1.3.3 .......................................................................................................... 7 1.2.8 Version 1.3.4 .......................................................................................................... 7 1.2.9 Version 1.4 ............................................................................................................. 8 1.2.10 Version 2.0 ........................................................................................................... 8 1.2.11 Version 2.2.0 ........................................................................................................ 8 1.2.12 Version 2.2.4 ........................................................................................................ 9 1.2.13 Version 2.2.5 ........................................................................................................ 9 1.2.14 Version 2.3.0 ........................................................................................................ 9 1.2.15 Version 2.3.1 .......................................................................................................10 1.2.16 Version 3.0.0 .......................................................................................................10 1.2.17 Version 3.1.0 .......................................................................................................10 1.2.18 Version 3.2.0 .......................................................................................................10 1.2.19 Version 3.3.0 .......................................................................................................10

2. INFORMATION ABOUT THE TSB-GENERATOR (FOR ADMINISTRATORS) .. 12 2.1 System requirements ................................................................................................12 2.2 Operation ...................................................................................................................14

2.2.1 Operating the TSB-Generator ...............................................................................14 2.2.2 Input ......................................................................................................................14 2.2.3 Processing ............................................................................................................15 2.2.4 Output ...................................................................................................................15 2.2.5 Data maintenance .................................................................................................15 2.2.6 Brand logos ...........................................................................................................15

2.3 Network capability .....................................................................................................16 2.4 Client Capability ........................................................................................................16 2.5 Directories .................................................................................................................16 2.6 Multilingualism ..........................................................................................................16

3. INSTALLATION ................................................................................................... 18 3.1 Download the installation program ..........................................................................18



3.2 Execute the setup program ......................................................................................18 3.3 Master data ................................................................................................................20 3.4 Uninstalling the TSB-Generator ...............................................................................20 3.5 Operating the TSB-Generator ...................................................................................20

3.5.1 Data exchange ......................................................................................................20 3.5.2 Manual mode ........................................................................................................20 3.5.3 Automatic mode ....................................................................................................21

3.6 Transport number .....................................................................................................21

4. OPERATING THE TSB-GENERATOR ................................................................ 23 4.1 Startup parameters ...................................................................................................23 4.2 Main window ..............................................................................................................23 4.3 Master data ................................................................................................................26 4.4 Supplier master data window ...................................................................................26 4.5 Window master data receiver (plant, clients) ..........................................................30 4.6 Window carrier master data......................................................................................31 4.7 Manual processing ....................................................................................................33

4.7.1 VDA4939...............................................................................................................33 4.7.2 GTL .......................................................................................................................36

4.8 Configuration .............................................................................................................37 4.8.1 Language ..............................................................................................................37 4.8.2 Directories .............................................................................................................38 4.8.3 Update ..................................................................................................................41

.....................43 4.8.4 Document generation ............................................................................................44

5. OTHER SETTINGS .............................................................................................. 48 5.1 Settings for the 2DCode label ...................................................................................48 5.2 Print script .................................................................................................................48



5.3 Waiting period after printing.....................................................................................48

6. ERROR MESSAGES ........................................................................................... 49

7. OTHER TSB-GENERATOR VDA4939 DOCUMENTS ........................................ 51

8. GLOSSARY ......................................................................................................... 52



List of Figures Figure 4-1 Main window ...................................................................................................24

Figure 4-2: Screen architecture (The word Update was replaced by the word Apply).......26

Figure 4-3 Supplier master data .......................................................................................27

Figure 4-4 Plants .............................................................................................................30

Figure 4-5 Carrier ............................................................................................................32

Figure 4-6: Manual processing .........................................................................................34

Figure 4-7: Manual edting GTL ........................................................................................36

Figure 4-8: Language configuration .................................................................................37

Figure 4-9: Folder configuration .......................................................................................39

Figure 4-10: Update .........................................................................................................42

Figure 4-11 Update information .......................................................................................43

Figure 4-12: Configuration of VDA4939 generation ..........................................................45

Figure 4-13: Configuration of GTL generation ..................................................................46

NOTES:

1. This document refers to Java products in many parts.

The Java platform is a product of SUN Microsystems. The terms of license and product of SUN Microsystems Ltd apply.

For questions about the Java products, please contact your local SUN Microsystems office.

2. This document refers to Adobe products in many parts.

Adobe products are part of Adobe Systems Incorporated. Terms of license and product of Adobe Systems Incorporated apply.

For questions about Adobe products, please contact your local Adobe Systems Incorporated office.

3. Here are some conventions that will help you easily navigate through the documentation. The drive x: in the document references your CD-ROM drive and the drive c: your installation drive. Paths are in bold, buttons labeling and fields are in italics. File content and program messages are written in Courier New. Text which is a placeholder for possible values is placed between . Filename and Path must not longer than 255 Characters.



1. Introduction

The transport and shipment document (TSB - VDA4939) was developed and released in 2002 on behalf of the VDA Committee for E-commerce and logistics. The TSB-Generator VDA4939 is used by Volkswagen AG.

Volkswagen AG provides its automotive suppliers free of charge with an application known as TSB-Generator which generates pick-up sheets according to the VDA5004 policy.

The TSB-Generator meets the requirements of the VDA4939.

The TSB-Generator can generate accompanying papers, including barcodes in accordance to VDA 4939.

Users are EDI suppliers for VDA 4913 / DESADV who are unable to generate TSBs with their own software.

1.1 Objective

The optimization potential of the delivery process in the automotive industry is not yet tapped. Suppliers and logistic service providers can use defined standard documents to optimize transport processes and reduce their own administration effort.

Various forms are merged in document records of the VDA4939. Redundancy free data can be created when taking into account the beneficial uses of individual document types.

The use of previous documents, such as EDI goods receipt/issue slip VDA4912, forwarding order/bill of lading and possibly company-specific pick-up and transport documents should be replaced by the usage of TSB. Exceptions may be agreed between the parties involved.

The current road haulage rules, the dangerous goods regulations and international rules on cross-border traffic are taken into consideration. The VDA4939 can also be used internationally, e.g. within the European freight transport. Current laws, regulations and rules always take precedence if the TSB based on the VDA4939 does no longer satisfy the requirements.

Basis for the TSB-Generator is the VDA4939 Version 02, issue December 2007.

1.2 History

1.2.1 Version 1.0

Initial version

1.2.2 Version 1.1

Various improvements and corrections



1.2.3 Version 1.2

Various improvements and corrections

1.2.4 Version 1.3

Corrections in the generation of PDF417 (missing trailers, incorrect characters at the end of sentence)

Printing on UNIX systems might possibly not have worked. Parameters were enclosed in quotation marks which did not work when using Java on UNIX.

When printing using Ghostscript in automatic mode, the paper format parameters are sent to the script and set using-sPAPERSIZE =% 2.

All unloading locations will be entered in C1 if many are available. Previously only one place of unloading has been entered.

The same shipping number could be printed in field C1 ASN in this shipment if there were multiple 713er sets with the same LS number.

Processed files in automatic modus can be automatically moved to a different directory.

There is a new entry BARCODE_MAX_CHARACTERS in configuration.properties which the number of characters to be coded in a barcode can be determined with. The more characters, the smaller are the black and white rectangles.

1.2.5 Version 1.3.1

Internal changes in the management of the receiver list.

1.2.6 Version 1.3.2

All files from the IN directory are read and processed if the checkbox move the Input files after processing in the configuration settings is enabled. In this case, the value in the file LastInputDirScan.properties has no effect anymore.

1.2.7 Version 1.3.3

If multiple input files are processed simultaneously, individual files might be skipped or not printed when printing using Ghostscript.

To avoid this problem, the files will only be processed one after the other after a waiting period. The waiting period is set to three seconds by default. This can be changed in the program configuration. This functionality is applicable from the version 1.33 (see SLEEP_AFTER_PRINT setting in Section X5.3 X).

If multiple input files are processed simultaneously, individual PDF files might be skipped or not printed when printing using Ghostscript.

1.2.8 Version 1.3.4

For a better overview, containers with the same ASN number will be printed in the same table in the shipment item sheet.

The generated documents are labeled with TSB-Generator 1:34 VOLKSWAGEN AG in the footer.

The suppliers logo is adapted in the document header.

The supplier's name is set to a maximum of 35 characters.



1.2.9 Version 1.4

The key previously required to install the program does not apply anymore.

The TSB-Generator can only be downloaded from the supplier portal VOLKSWAGEN www.vwgroupsupply.com.

The JRE integrated version is not available anymore. Therefore, the Java runtime environment must be installed separately on the user's computer before installing the TSB-Generator.

The version 1.4 is compatible with Windows Vista and Windows 7 .

1.2.10 Version 2.0

By using the TSB-Generator pick-up sheets can be created which can then be used for the NLK process (New Logistics Concept). The user of the DESADV message with additional segments from the dispatch call-off is required.

Transport ID

Dispatch call-off no. (VAB Nr.)

Target arrival time

Collection date (Shipment date)

The DESADV files with the additional information are referred to as DESADV NLK in the documentation.

The following fields were modified and deviate from the VDA4939 recommendation:

The transport ID will be added to the transport master header if it is a DESADV NLK.

Field B2 Delivery Date was replaced by dispatch call-off.

Field B3 bordereau/freight list no. was replaced with Transport ID

A 1D barcode was added to the footer of the transport master sheet.

Users of the TSB-Generator version 2.0 can hide the PDF417 (2D barcode).

The TSB-Generator is still able to interpret conventional DESADV messages without the additional segments and to process VDA4913 messages.

1.2.11 Version 2.2.0

The TSB-Generator was expanded to interpret new DESADV-Segments for OT special processes (drop shipment, demand driven order process, FIB)

OT-Consignee

Vehicle ID Number

SAP Customer Order Number

SAP-Order Number

SAP-Order Line Number

Purchase-Order Number

These Segments are referenced in the document as Customer reference fields for OT special processes (drop shipment, demand driven order process, FIB).



The new Segments are optional.

The TSB-Generator Version 2.2.0 allows users to update Receiver information within the program.

For all suppliers of original parts who delivers in special processes (drop shipment, demand driven order process, FIB) is prerequisite:

An update of the consignees must not be updated over the program. For an update of the address master data of the consignees please contact your material planner.

1.2.12 Version 2.2.4

The feature Update Receiver Data has been corrected. The URL i https://sso.volkswagen.de/webedi/adressexp/anliefer_adressen.csv

now points to the correct file.

1.2.13 Version 2.2.5

TSB Generater versions 2.2.4 and older do not compute the tare weight. Beginning with version 2.2.5, TSB Generator does compute the tare weight and it is included in the PDF output.

When reading a file in the DESADV format, the indication of hazardous material was sometimes omitted in the printout. This was caused by an error in the processing of the segment structure. The error is fixed with version 2.2.5.

1.2.14 Version 2.3.0

The new file Empfaener_OT.dat was introduced for the supplies of original parts. This file was located on Master data directory (Stammdaten-Verzeichnis) and will be always read and represented together with the file Empfaenger.dat

During the updating of the receivers (Menu "Program" - "Update") the new file has been read also of the WebEDI-Page. The URL is:

https://sso.volkswagen.de/webedi/adressexp/anliefer_adressen_OT.csv

TSB-Generater must be restarted after a downlaod.

In the dialog "suppliers" choose printer the printer display was speed up to the available Printer and "A4 printers" have not been inspected anymore.

https://sso.volkswagen.de/webedi/adressexp/anliefer_adressen.csvhttps://sso.volkswagen.de/webedi/adressexp/anliefer_adressen_OT.csv


1.2.15 Version 2.3.1

1. Changes regarding VDA 4913: Previously: The barcode on the transport master sheet of the transport and shipment document (TSB) encodes, among other things, the supplier ID of the issuing supplier. The source of the supplier ID is SA 712_04, plant supplier.

Updated: TSB-Generator checks SA 713_16 (supplier ID when ASN is issued by shipper). If this field is not blank its value is used as supplier ID in the barcode on the transport master sheet. If the field is blank the supplier ID is taken from SA 711_04, data sender number.

2. Extended Footer The source file (VDA 4913 or DESADV) was added to the footer.

1.2.16 Version 3.0.0

The functionality to create Global Transport Labels was added.

1.2.17 Version 3.1.0

The system default program will be used for viewing PDFs

Zur Anzeige von PDFs wird das im Betriebssystem eingestellte Standardprogramm verwendet. The configuration of Acrobat during setup has been removed.

When reading VDA4913 files the qantity per package will be calculated from the sum oft he contained pieces. This replaces the value in field 07 of record 715. When reading DESADV the calculated value will be used for mixed load if no QTY+1 segment was found.

The printer configuration in the shipping location is now per output format (TSB or GTL)

A page break is inserted after a KLT label if a main label follows.

The parameter -dPDFFITPage was removed from the GhostScript print script, to prevent changing the page margins.

The input field country was removed from the address configurations. Only the country code is required. The country name will be automatically determined.

1.2.18 Version 3.2.0

Autimatic update of receiver master data

Online check for program updates

User defined receivers can be put in the file Empfaenger_Additional.dat

1.2.19 Version 3.3.0

Adaptions and corrections for OT (Original parts).



1.2.20 Version 3.4.0

The original data will only be updated when the update is successful. The data is not deleted anymore when the update is not successful.



2. Information about the TSB-Generator (for administrators)

The TSB-Generator is a standalone application

The TSB-Generator is network-compatible (printing on network printers, a unique allocation of suppliers shipping locations to printers)

The TSB-Generator supports the multi-client capability (storage of multiple supplier master data)

The requirements of the VOLKSWAGEN EDI-Guidelines are implemented in a software package:

o Implementation Guidelines transport and shipment documents (TSB Version 01) from PDF EDI

o Implementation Guidelines Pick-up sheet (PUS)

o EDI Implementation Guidelines ASN VDA4913 / 4 Issue 03/1996

o EDI Implementation Guidelines ASN and transport data EDIFACT DESADV 14 February 2005

o EDI Implementation Guidelines Volkswagen / Audi version 09/2008

The TSB-Generator does NOT check ASN files. The test is automatically performed by the EDI converter at Volkswagen. If you have any questions about ASN data, you can contact the service team of Volkswagen AG, tel: +49 5361-9-20636.

The application has been developed for Windows and UNIX / Linux operating systems (implementation in Java).

Reading of text files in ASCII and EBCDIC format is possible

A manual generation of a VDA4939 (TSB) is not possible and not planned (the data basis is VDA4913/DESADV)

The TSB-Generator does not generate files for the EDI message communication.

The generated VDA4939.PDF files can be deleted via the program configuration.

2.1 System requirements

Before installing the TSB-Generator on your computer, make sure that the following minimum requirements are met to run the software properly:

TSB-Generator is fully developed in JAVA; therefore a Java Runtime Environment Version 1.4 is required.

A program is required for displaying the VDA A4939.PDF. The Adobe Reader or Ghostscript is required for the operation. We recommend Adobe.



A program is required for printing the VDA4939.PDF. Therefore, the Adobe Reader or Ghostscript is required for the operation. We recommend Ghostscript.

For compatibility with operating systems, the information given by Adobe, and Sun shall prevail.

Before installing the TSB-Generator, make sure that the Java Runtime Environment and the Adobe Reader software is running properly on your operating system.

System requirements:

1. The Java Runtime Environment Version 1.6.0 (6.0) is used as the runtime environment. The TSB-Generator supports the JRE 1.4.2 version. Please ensure that the JRE (Java Runtime Environment) is installed on the target computer (computer which the TSB-Generator is run on) before proceeding with the TSB-Generator installation.

The JRE can be downloaded and installed for free from http://java.sun.com/j2se/1.6.0/download.jsp (12.47 MB - 15.06 MB, depending on the OS - version).

If you would like to install the JRE yourself, please read the instructions and documentation provided by SUN Microsystems, or ask your system administrator.

The terms of license and product of the SUN Microsystems Ltd apply.

The runtime environment 1.6 supports the following system configurations:

2. The screen must have a minimum resolution of 800 x 600 pixels. 3. Laser or inkjet printer must have a minimum resolution of 300 x 300 dpi. The printer can be a network printer. Please refer to your operating system documentation or ask your system administrator on how to control and change the printer settings from your PC / network.

4. The printer must be capable of printing without margins. Otherwise it can happen that the print result is incomplete at the page margins.

5. If the input files are created on another system, you will need a PC connection to this system. Please refer to your operating system documentation or ask your system administrator in charge on how you can configure network connections.

6. The input folder that contains the input files must have the appropriate access rights for the TSB-Generator features. Please refer to your operating system documentation or ask your system administrator on how to set these permissions.

7. The input data from your system must be saved in the ASCII and/or EBCDIC format. 8. The Adobe Reader is required to view and print. The Adobe Reader must be installed before the TSB-Generator is installed. The Adobe Reader can be downloaded for free from http://get.adobe.com/com/reader/.

Please refer to the instructions and documentation you can get from Adobe or ask your system administrator on how to install the Adobe Reader.

The TSB-Generator was tested with Acrobat Reader versions 6.0 and 7.0.

The terms of license and product of Adobe Incorporate system apply.

9. The automatic mode requires a program to send PDF files to the printer without any user interaction. Since Acrobat Reader is not suitable for such background processing, the TSB-Generator program requires Ghostscript.

If you plan to use the TSB-Generator in the automatic mode, please make sure you have installed Ghostscript before installing TSB-Generator.

http://java.sun.com/j2se/1.6.0/download.jsphttp://get.adobe.com/com/reader/


The current version of Ghostscript for your OS is license free and can be downloaded from http://www.cs.wisc.edu/~ghost/.

The TSB-Generator was tested with the 8.51 to 8.71 versions.

If you are sure that you will not use automatic mode, you do not need to install Ghostscript. In this case, the Acrobat Reader will be used as a PDF Reader in the manual mode.

If you decide later to use the TSB-Generator in the automatic mode, you will need to uninstall the TSB-Generator, install Ghostscript and then reinstall the TSB-Generator.

Please refer to the instructions and documentation you can get from Ghostscript or ask your system administrator on how to install Ghostscript.

The terms of license and product of Ghostscript apply.

10. The hardware requirements are derived from the conditions laid down by the JRE and Adobe to operate under the respective operating systems. For example, for a MS Windows OS system, a PII 400 MHz processor, 128MB of RAM and minimum 100 MB free hard disk space, are required.

NOTE:

Due to the different system requirements and compatibility information provided by the manufacturer for Java and Adobe products, it may lead to incompatibility of the TSB-Generator with your operating system in very rare cases. You should read the information concerning the system requirements before installing the needed components and the TSB-Generator.

If these conditions are met, you can use the TSB-Generator.

2.2 Operation

2.2.1 Operating the TSB-Generator

The program is operated through a graphical user interface (see section User interfaces), which offers the following areas:

Main Window

Master data for carrier, clients (receiving plants and destinations), suppliers (shipping locations)

Configuration

Edit

2.2.2 Input

You cannot manipulate the input data with the application.

The input data formats are:

Text (ASCII or EBCDIC) file with the VDA-49131 format, in accordance with:

o VOLKSWAGEN EDI Guidelines in version 4

1 The laws, regulations and provisions applying to the carriage of goods shall be considered under any circumstances and shall prevail. @VOLKSWAGEN AG Page 14 of 52 Version 1.33 May 2014
http://www.cs.wisc.edu/%7Eghost/


Text (ASCII or EBCDIC) files in the format DESADV, in accordance with:

o VOLKSWAGEN EDI EDIFACT Guidelines DESADV

2.2.3 Processing

Processing goes through following steps:

Conversion of EBCDIC to ASCII, if necessary.

Parsing the input file: the defective parts will be skipped if there are problems caused by syntactic errors in the input file, the file will be read as far as possible. In case of problems, an entry in the error log is generated and the file will be copied into the ERROR folder.

The contained information will be transferred to a Java data structure with information and information from the master data will be added.

2.2.4 Output

The TSB-Generator does not generate *. VDA files, which can be used in the EDI message communication.

The TSB-Generator reads the input files from a specified directory/path. There is no conversion /move/ deletion of the original files. Only in case of errors, the file is copied in the ERROR directory.

2.2.4.1 Output Documents

The output document is a VDA 4939 2nd Edition version of December 2007 as *.PDF.

2.2.5 Data maintenance

The TSB-Generator has several sources for master data:

Suppliers (shippers/subcontractors) with shipping locations

Freight forwarders with drivers

Receiver (receiving plant) with reception points

The suppliers and carriers must be created and maintained in the TSB-Generator.

2.2.6 Brand logos

The header of the VDA4939 documents can be filled with the supplier logo. The logo can be stored in the master data. The TSB-Generator supports following formats:

JPEG

GIF

PNG



All logos will be displayed in accordance with the assigned VDA4939 field sizes. If no logo is specified in the master data, the company name will be displayed.

2.3 Network capability

The network capability is ensured by:

Access to network drives via:

o drive mappings (in Windows environments)

o UNC paths (Universal / Uniform Naming Convention)

Access to network printer

2.4 Client Capability

The application allows you to manage several supplier master data (shipper/subcontractor). This is achieved by an extensible list of suppliers. After reading the input file, the selection of the supplier is made in accordance with the registered IDs in the VDA4913 or DESADV (see Implementation Guidelines transport and shipment documents (TSB Version 01)).

If it is required to run the application with variable settings (e.g. different IN directories, different supplier addresses for the same supplier ID), the application can be installed several times on the same computer or on the same network. Each of the instances can get an individually customized set of master data files and settings.

2.5 Directories

The directories are listed in the following table:

2.6 Multilingualism

The application is multilingual. The installation program guides the user in English or German through the installation process.

The user interface within the application, including the entry forms for manual data entry, is multilingual. The user can configure it via the language menu.

Directories

In Here are the input data to be processed

Out Here the generated Adobe PDF Files are stored

error Here are copies of input files which failed to be processed.

update Here templates for manually entered data can be saved.

stammdaten Master data directory for data files: Lieferanten.dat, Empfaenger.dat, Spediteure.dat



The generated documents are completely in German. Other languages can be selected manually.

The TSB-Generator is provided in German (default) and English (installation).



3. Installation

To carry out the basic installation, you should be confident in dealing with your operating system. Operating system components (e.g. Explorer, Start Menu, etc.) and their management are presumed to be known. If this is not the case, please refer to your operating system documentation or ask your system administrator.

For simplicity's sake, the installation on Windows operating systems is described here.

Please read your system requirements (see chapter 2.1) before installing!

3.1 Download the installation program

The TSB-Generator downloads are available for the following platforms:

Linux

Solaris / UNIX

Windows

3.2 Execute the setup program

The setup program guides you easily through the installation process. Some queries are made during this process.

1a) Windows only:

Start the program TSB-Setup.exe.

1b) UNIX Only:

Enter in the shell type: sh. / TSB-Setup.bin

2) All Platforms:

Choose the language in which you want to be guided through the installation process, and then click OK.

2) All Platforms:

Click yes if you want to continue the installation.

2) All Platforms:

You will see a welcome note. Click Next.

2) All Platforms:

You will see a reference text regarding the installation of JAVA. If JAVA already exists on your system, then click Next, if not please Cancel the installation and install JAVA.

4) All platforms:



This dialog allows you to select the folder in which the TSB-Generator will be installed. Default is the folder C:\Program Files\TSB-Generator\. To change the installation folder, click the Browse button.

Once you've selected the new local folder, or have entered a network folder in the top field, click Ok. If you have entered a not yet existent folder, you will not be asked if it should be created.

Click Next to start the installation process.

5a) Windows only:

In this dialog enter the path of the installed Adobe Reader for displaying the PDF data. There must be a complete path to the executable file, e.g. C:\Program Files\Adobe\Acrobat 8.0\Reader\acroRd32.exe. You can later change the path.

Then click Next.

6a) Windows only:

In this dialog you will be asked to enter the path for the Ghostscript installation. For example: C:\Program Files\gs\gs8.53\bin\gswin32c.exe. It is necessary to choose the gswin32c.exe file.

You have to enter the path in the GhostScript-Exe file. This is in the following folder in version 8.53:

C:\Programme\gs\gs8.53\bin

There are two files:

gswin32.exe

gswin32c.exe

Please select the file gswin32c.exe. The entire path is

C:\Programme\gs\gs8.53\bin\gswin32c.exe

If your Ghostscript installation is in another folder, enter the appropriate path.

If you are sure that you wont need the automatic mode, you can keep the text box empty. If you later decide to use the automatic mode, then you will have to install Ghostscript and reinstall the TSB-Generator.

7) All platforms:

You can see a summary of the selected settings. Check everything. If all settings are correct, click Install. Otherwise, click Back and correct your information.

7) All platforms:

The setup program installs the TSB-Generator according to your preferences. Finally, in the last dialog it informs you about the successful installation of the TSB-Generator.



The TSB-Generator is now installed on your computer.

Note for UNIX users:

Under UNIX acroread and gswin32c are searched using the PATH variable.

3.3 Master data

After successfully installing the TSB-Generator, the receiver master data file must be copied into the master data directory (in the TSB installation directory).

Then, enter at least one supplier (with places of dispatch, if applicable) and a shipper (with driver, if applicable). If the input data reference to further suppliers and transporters, these must also be created. (See sections Window master data suppliers/subcontractors and Window master data freight forwarder/driver)

3.4 Uninstalling the TSB-Generator

The TSB-Generator is easy to remove from your computer. All you need to do is to run the Uninstall.exe located in the selected installation directory. Uninstall.exe can also be found in the Start menu under Programs TSB-Generator folder.

To uninstall the available JRE read the Java documentation available or ask your system administrator in charge.

To uninstall the Adobe Reader read the Adobe documentation available or ask your system administrator in charge.

To uninstall Ghostscript read the Ghostscript documentation available or ask your system administrator in charge.

3.5 Operating the TSB-Generator

3.5.1 Data exchange

There are no interfaces to other applications. Data are imported and exported via files in the file system.

3.5.2 Manual mode

Input files (VDA4913 or DESADV) are opened manually in the manual mode, similar to other programs. If the input file is in EBCDIC format, it will be converted to ASCII. See also the section on program configuration. The original file remains unchanged. The TSB-Generator tries to produce a VDA4939. During this process, input data will be associated with master data. A file will not yet be created in the Out directory. This happens only when displaying it in Adobe Reader. Before displaying the PDF File, information regarding dangerous goods and additional references can be added or changed.



When displaying, a PDF file will be created in the Out directory whose name looks like this: XXX_VDA4939.pdf. XXX is here the name of the input file without suffix. If the input file is, for example, 112233.vda, then the output file will be 112233_VDA4939.pdf.

Note:

Output files will not be automatically deleted after printing in the manual mode. The reason is that the Adobe Reader is first only open for displaying it. A message will not be sent to the TSB-Generator stating that the print has been completed. Therefore, the TSB-Generator cannot delete the file.

3.5.3 Automatic mode

In the automatic mode the recently added files will be automatically imported from the input directory (referred to as IN directory in the following) in regular intervals.

The TSB-Generator will only import files that correspond to the naming scheme which has been set in the configuration (Program -> Configuration -> Document production). The interval in which the directory is checked for new files may also be specified.

A manual modification of files is not possible in this mode. Successfully imported files are automatically sent to the printer. This requires Adobe Reader, Ghostscript or another PDF print program.

A copy of the input file will be copied into the error directory if a problem occurs that prevents creating the PDF file. The same applies if a problem occurs while printing, as long as the error will be sent back to the TSB-Generator.

Since the print program (e.g. via Adobe Reader) is operated outside of the TSB-Generator, the TSB-Generator has only very limited possibilities to check if the printing process was successful.

Note:

As the Adobe Reader version 6.0 immediately starts to print in the automatic mode, the TSB-Generator can delete the output file after printing if this has been set in the program configuration.

3.6 Transport number

The transport number is assigned separately for each TSB-Generator installation and whenever you open a file, it will be increased and assigned to the file. If the same file is repeatedly opened, its transport number will go up by one. The counting starts from scratch each day. The initial value can be configured as described below.

For experienced users and administrators:

The file config/TransportNumberCounter.properties contains a FIRST_TRANSPORT_NUMBER entry which specifies at which point the counting begins. The value LAST_TRANSPORT_NUMBER determines the last assigned number. The counting starts



from scratch at the value assigned with the FIRST_TRANSPORT_NUMBER. This makes the transport number unique per each calendar day.

If a supplier has several installations of the TSB, the transport number can be definitely assigned by assigning different for FIRST_TRANSPORT_NUMBER, for example FIRST_TRANSPORT_NUMBER = 1 for the first installation and FIRST_TRANSPORT_NUMBER = 1000 for the second installation. It only needs to be ensured that the second value is chosen large enough. It will then assign the transport numbers

1, 2, 3, 4...

and

1001, 1002, 1003, 1004...



4. Operating the TSB-Generator

The controls of the TSB-Generator are explained below. Basically, the TSB-Generator can be used intuitively. Since VDA4939 is a VDA recommendation for the transport documents, a manual entry in the TSB-Generator is not possible. The basic data generated from your systems are VDA4913/DESADV files in ASCII or EBCDIC. These are read by the TSB-Generator and converted into the VDA4939. This keeps the original format of the imported file. The TSB-Generator works with a copy of this file, which is stored in the OUT directory after a successful conversion as XXX_VDA4939.PDF.

Note: Changes can still be made in the interfaces shown to support a better workflow, for example.

4.1 Startup parameters

When starting the TSB-Generator, you can give the parameter automatic. As a result, the TSB-Generator starts immediately in the automatic mode.

This is the case under Windows / systems e.g. under "target" in the program shortcut in the form

TSB-Generator.exe automatic

On UNIX systems, this option is also as a start-parameter available.

4.2 Main window

The main window will be displayed after starting the TSB-Generator and is the central point of the application.



Figure 4-1 Main window

The window contains the following elements: Start Automatic Modus Starts the automatic mode.

The automatic mode allows interference-free operation for the production of VDA4939.

The intervals to read the input registers can be set under Program.

Stop Automatic Modus

Stops the automatic mode.

The automatic mode will be stopped.

Load File

Loads a VDA4913 or DESADV file for the manual amendment and conversion.

The input file can be selected from the corresponding directory. This feature can only be used in manual mode.

Edit

Opens the screen for entering dangerous goods information and additional information.

Here the comments can be entered in the fields D1 dangerous goods and E2 additional information of the respective document records of the VDA4939. This feature can only be



used in manual mode. The function cannot be used if no data exists (or errors), or if no VDA4913 / DESADV has been imported.

Create Output

Opens the created VDA4939 in Adobe Reader.

The input file has been converted into a VDA4939.PDF. The result is shown here. This feature can only be used in manual mode. Note that at this point the TSB-Generator has NOT yet made changes to the input data. If there are errors with regard to content in the document, check the input file and the master data. The function cannot be used if no data exists, or no VDA4913 / DESADV have been imported.

Suppliers

Opens a window to display and edit the master data of the supplier. The user enters and manages the supplier master data, according to the field data. The supplier master data will be used for the address details in the VDA4939. Make sure that the format of your supplier data (supplier number, DUNS number) in the input data corresponds to the format in the data.

Receiver

Opens the window to display and edit the receiver master data (plants).

The receiver master data are provided by VOLKSWAGEN and managed by the user. An update is needed if VOLKSWAGEN master data are provided.

The TSB-Generator 2.2.0 Version allows users to update receiver information see section 4.8.3.

Haulier

Opens the window to display and edit the carrier master data. The carrier master data are entered and managed by the user according to the field data. The carrier master data are used for the address details in the VDA4939. Make sure that your data in the input data correspond to the information in these data (driver).

Output formats

Choose if VDA4939, GTL or both should be created.

Document Settings Opens the configuration window for the document settings.

Program Opens the configuration window. Central component of the TSB-Generator for setting up the system parameters. A proper operation is not possible without a complete configuration.

Close Closes the window and leads back to the main screen

? Opens the help. Opens the help window.



4.3 Master data

The TSB-Generator has different master data. Besides the non-editable receiver data, the following master data can be changed in the input screens:

Suppliers/subcontractors with shipping locations

Freight forwarders

They are basically similar in structure and work in the same way. On the left is a list (e.g. suppliers). Clicking the button "New" or "Remove" can create new entries and delete existing entries. When selecting a supplier entry from the list, the details will be shown on the right. These can be edited. The button "Apply" saves changes of the details. For each supplier record is filled again with a list of data, such as shipping locations per supplier. This list and their details can also be edited.

Figure 4-2: Screen architecture (The word Update was replaced by the word Apply)

The master data:

Receiver/plants with reception points

exist already in the TSB-Generator and can be displayed by the button Receiver, but not edited.

NOTE:

If it is necessary to change the reception master data, experienced users and system administrators can load these data into a text editor and edit them. Therefore, open the file Empfaenger.dat in the directory \\TSB-Generator\Stammdaten with an editor program. Please create a backup before processing any changes.

User defined receivers can be put in the file Empfaenger_additional.dat. The data must have the same structure as in Empfaenger.dat.

4.4 Supplier master data window For all data inputs, the requirements according to EDI Guidelines of the Volkswagen / Audi are decisive.

List Details of the selected item in

the list

List with subordinated data

Details of the selected item in the subordinate

list

Apply New Delete Apply New Delete



Figure 4-3 Supplier master data

The window contains the following elements: Supplier list

List of suppliers

The supplier's name is the company name of the sender. This information will be used for in the sender block of the VDA4939.

For all suppliers of original parts who delivers in special processes (drop shipment, demand driven order process, FIB) is prerequisite:

An update of the consignees must not be updated over the program. For an update of the address master data of the consignees please contact your material planner.

Button New

Opens the next line to enter another supplier in the list.

This feature ensures that the user can create several suppliers / supplier sites in the master data. All fields are initially empty.

There must be at least the Suppliers ID. The new entry will be added to the list only after clicking the "Update" button.

Button Delete Deletes the selected suppliers master data. The selected suppliers master data will be completely removed

Supplier Details

Area for displaying and entering the details of the selected supplier. @VOLKSWAGEN AG Page 27 of 52 Version 1.33 May 2014


The following fields are available: Name (maximum 35 characters) Street 1 Street 2 ZIP / City

District Country code Supplier ID VAT-ID (Ust-ID) Logo

Notes: At least the supplier ID must be assigned. NO index should be entered in the field supplier ID. Note: The supplier ID must correspond to the field data sender number/supplier number in the EDI data. VDA 4913 SA 711, pos 4 / DESADV SG 2 NAD "CZ" C082 3039

Logo

Opens the selection of a company logo. Here you can save a logo in the format PNG, JGP, GIF per supplier master record. The logo appears in the VDA4939 in the heading. The size will be adjusted according to the requirements of the VDA4939.

Button Apply

Updates the selected supplier master record

The new or changed data in the TSB-Generator will be saved when clicking this button. If this window is closed without pressing the apply button, the previous entries will not be saved.

Copy into shipping location

Copies the following fields from the supplier to the shipping location: Name Street 1 Street 2 ZIP / City District Country code

List of shipping locations

Opens the list of shipping locations for the selected supplier master record. This information is necessary, and will be used in the sender block for the VDA4939.

Button New Opens the next record to specify another shipping location. This feature ensures that the user can create multiple shipping locations per supplier in the master data. All fields are empty at first. At least a shipping location ID must be assigned. The new record is added to the list only after clicking "Update".

Button Delete Deletes the selected shipping location master record. The selected shipping location master record will be completely removed

Shipping location details Area for displaying and entering the details of the selected shipping destination.



The following fields are available: Name Street 1 Street 2 ZIP / City District Country code Shipping location ID DUNS Number Contact Printer

Notes: If the loading place information does not correspond to the supplier information, the entry must be made according to the supplier record.

At least the shipping location ID must be assigned. The field shipping location ID should be filled with the index (e.g. '0 ') of the supplier number without its separators (e.g.' / 'or'-'). Note: The shipping location ID must correspond to the driver in the EDI data. VDA 4913 SA 712, pos 4 / DESADV SG 2 NAD-LOC "CZ" C517 3225

Default Printer

Indicates the printer settings for the loading place record/supplier data record. An individual printer can be saved for each supplier record with a different ID (index of supplier number) in the source data and master data. This is used for printing transport documents in the automatic mode. For the correct printer name, see the printer configuration on your computer or ask your system administrator.

Driver and port are optional, and not available on Unix systems. If no loading place has been created for a supplier or no printer has been entered in the loading place data record the system will use the default printer of your computer. A trouble-free operation is not possible without proper configuration of the printer. Please refer to your system documentation or ask your system administrator to know which printers need to be activated.

Select box "TSB/GTL

Assigns the printer to an output format.

Button "Choose Printer... Opens a dialog with the list of available printers.

Button Apply Updates the selected Shipping location. New and changed data will be saved when clicking this button. If this window is closed without pressing the update button, the previous entries wont be saved.

Close Closes the windows and leads back to the main window

? Opens the help window. The country codes and designations are created according to ISO / DIN.



4.5 Window master data receiver (plant, clients)

The requirements according to EDI guidelines of the Volkswagen / Audi are decisive for all data inputs.

Figure 4-4 Plants

The window contains the following elements: Receiver-List The file is provided by Volkswagen and it cannot be edited by the user. This information will be used for VDA4939 in the receiver block.

Receiver details Area for viewing the details of the selected receiver. The following information is displayed:

Name (the receivers name is the company name of the receiver) Street 1 Street 2 Zip / City

District Country

Mandant

Receiver ID (plant number) VAT-ID (Ust-ID)

Contact data

List of reception points



List of reception points (locations of delivery) for the selected receiver.

Reception point details Area for viewing the details of the selected reception point. The following information is displayed:

Name Street 1 Street 2 Zip / City District Country Reception point ID DUNS Number

Contact data

Close

Closes the windows and leads back to the main window

?

Opens the help window.

A master file with the above data is provided by the client and delivered/installed as part of the application. If there are any changes/updates by Volkswagen, you will receive actual master data files.

The country codes and designations are created according to ISO / DIN.

4.6 Window carrier master data

The requirements according to EDI guidelines of the Volkswagen / Audi are decisive for all master data inputs.



Figure 4-5 Carrier

The window contains the following elements: List of carriers List of carriers.

The carrier name is the company name of the area carrier in charge of the supplier. This information will be used in the carrier block of the VDA4939

Carrier details Name (Name is the company name of the carrier Street 1 Street 2 Zip / City District Country code Carrier ID DUNS number Note: The carrier ID must correspond to the field transport partner number in the EDI data. VDA 4913 SA 712, Pos 13 / DESADV SG 2 NAD C082 3039

Driver list List of the drivers for the selected carrier master record. The drivers information is optional. This information will be used in the carrier block of the VDA4939.

Driver details Area for viewing the details of the selected driver



The following information is displayed: Name Driver ID DUNS Number Contact

Note: The driver ID must correspond to the field driver in the EDI data. VDA 4913 SA 712, pos 5 / DESADV SG 6 TDT "FW" C082 DE3127

Close

Closes the windows and leads back to the main window

?


The country codes and designations are created according to ISO / DIN.

4.7 Manual processing

In the Edit dialog additional input can be made for the printouts. The dialog has a tab for VDA3949 and one for GTL.

4.7.1 VDA4939

Since the generated PDF417 label include the input file (VDA4913 or DESADV) and these must be consistent with the generated VDA4939 output, only data which were not in the input data but not in the VDA4939 can be edited.

A screen is provided for editing the following fields:

D1 Dangerous goods notes (filled from the input file as much as possible). It is the responsibility of the user to maintain the consistency of the PDF417 labels, possibly by using the information (dangerous numbers) from the input file.

Note: With dangerous goods advices, we expect the UN dangerous goods number in EDI data. The number is taken from the EDI data and transferred to the TSB and will be initialized in this window.

E1 Additional details

The screen reflects exactly the structure of VDA4939 documents as they are produced from the input file. After selecting a document from the list, dangerous goods notes and additional notes for this document can be entered (dangerous goods not when using shipment position sheets).

The data can be saved in the update directory (default setting, other directories are available) and can be loaded from there. The file name is initialized with the transport number (can be changed). These files are only for internal use within the TSB-Generator.



Figure 4-6: Manual processing

The window contains the following elements: Document list

List of generated VDA4939 documents.

Select the document to be processed from this list.

Dangerous goods D1: Goods risk:

Field for dangerous goods information.

The dangerous goods information for the selected document can be entered in this field. Entered changes will not affect the original file.



Information already contained in the import file VDA4913/DESADV, is displayed here and can be edited. The data are sent via delivery note to the appropriate delivery note number. The list includes also delivery notes without dangerous goods information. These can be completed if required. Under D1 in the VDA4939 only delivery notes will be displayed which have been entered with dangerous goods information.

A double-click in the field of the table starts the editing function.

The TSB-Generator does not check dangerous goods information and does not release from the legal requirements, such as the enclosure of the dangerous goods sheets, for example.

Button Load: Loads a previously saved file with the dangerous goods information into the block D1.

The shipment master sheet and the delivery note for which the data should be loaded have to be selected first.

Button Save: Saves the dangerous goods information in a file.

The shipment master sheet and the delivery note for which the data should be loaded have to be selected. The file can be reused for other documents. We recommend using the UN code of dangerous goods as the name of the file.

Button Reset:

Resets the entries.

The entries made on the information in the import file are reset. Only the selected Risk good text will be reset.

Additional notes E1: Additional Note: Field for the entry of an additional note.

In this field additional information about the selected document can be entered.

Button Load:

Loads a previously saved file containing additional notes into the block E1.

The text is loaded into the field E1 of the document sheet currently selected in the list.

Button Save: Saves the additional note E1 of the document sheet, which is currently selected in the list, in a file.

Button Reset:

Deletes the additional note of the document sheet currently selected in the list.

Close

Closes the window and leads back to the main screen.

? Opens the help window.



4.7.2 GTL

Figure 4-7: Manual edting GTL

The window contains the following elements: Supplier area GTL Here you enter text to appear in the supplier area oft he GTL (field E1 on a GTL A5 and AIAG B10 or D2 for a Small KLT)

Button Load:

Loads a previously saved file with content for the supplier field.

Button Save:

Savest the content oft he supplier field into a file.

Button Reset:



Resets the content.

Close Closes the window and leads back to the main screen.

?


4.8 Configuration

The following settings can be made in this window:

Language settings

Program Folders

Update

4.8.1 Language

Figure 4-8: Language configuration



The window contains the following elements: Tab Language: Opens the screen for language settings

Pull down Program language:

Field to select the program language of the TSB-Generator.

Here you can set the language for the menu and the other components of the TSB-Generator. German and English can be selected in the version ready to be shipped.

Pull down Document language:

Field to select the language of the document VDA4939.

Here you can set the language for the output of the TSB-Generator. German and English can be selected in the version ready to be shipped.

Close

Closes the window and leads back to the main screen

?



4.8.2 Directories

The installation directory is the default location for the parent directory.



Figure 4-9: Folder configuration

The window contains the following elements: Tab Folders: Opens the screen for folder settings.

Import interval (s): Field to set the import interval.

Here you can enter the import interval for the TSB-Generator in seconds. After the intervals have expired, the set IN directory will be searched for new VDA4913/DESADV. The new files are imported and processed. The files are not changed. This setting is required for automatic mode.

Name sample:

Field to specify the name of the input files.

In this field you can save the file names of the DESADV/VDA4913 as a pattern. This approach ensures that files which are in the IN directory, but should not/cannot be converted, are not imported by the TSB-Generator.

The pattern can include the * as a placeholder once or more often and is case sensitive, e.g. the following files will be recognized with the pattern VDA*.txt:



VDA4913_test1.txt

VDA_test.txt

VDA_test.vda

Those files wont be recognized:

vda_test.txt (as it is spelt with lowercase letters)

test_VDA.txt (as it does not start with VDA)

In order to recognize both VDA_test.txt and test_VDA.txt, the pattern must be *VDA*.txt, for example.

Field In:

Specification of the input directory.

Here you can enter the directory from which the TSB-Generator imports the input files VDA4913/DESADV. In automatic mode the program searches this directory for new files after the specified time interval.

Field Out TSB: Specification of the output directory.

Here you can set the output directory for the generated VDA4939. These files will be saved in this directory after printing. The contents of this directory can be automatically deleted.

Field Out GTL: Specification of the output directory.

Here you can set the output directory for the generated GTLs. These files will be saved in this directory after printing. The contents of this directory can be automatically deleted.

Field Error: Specification of the error directory.

Here you can set the output directory for incorrect input data. The data record will not be checked. Only files which can clearly not be recognized as VDA4913/DESADV or cause errors during the processing will be saved here.

Field Update:

Specification of a directory for template files.

Here the list of manually entered data (dangerous goods information and additional information) for VDA4939 or GTL can be specified.

Field Processed Files:

Specify the directory for processed files.

Here you can specify the directory where the input files are moved to after processing in automatic mode. This requires enabling the function Moving files.

Field Master data:

Specification of a directory for the master data.

Here you can specify the directory for the master data of the TSB-Generator. The default is stammdaten in the installation directory of the TSB-Generator. The following master data files must be listed in this directory:

country_codes_en.txt @VOLKSWAGEN AG Page 40 of 52 Version 1.33 May 2014


Lieferanten.dat (Supplier)

Empfaenger.dat (Receiver)

Spediteure.dat (Carrier)

as well as supplier logo image files

Ghost Script program:

Field to specify the path of the PDF printer program (Ghost Script).

You should specify the full path of the Ghost Script executable program file. This setting is already made during installation, but can be changed here. It is recommended to use Ghostscript.

Close

Closes the window and leads back to the main screen.



4.8.3 Update

With version 2.2.0 you have the possibility to update the receiver master data from within the program. After entering your connection data (proxy, port, VW B2B login and password) in the program configuration you can download the latest receiver master data into the master data folder. The file is available for download from the VOLKSWAGEN supplier portal at www.vwgroupsupply.com. The master data for receivers are used fort he adress fields on the VDA4939 and GTL. Please take care that the information in your input files match the master data (receiving factory). You must restart the TSB Generator after the download.

http://www.vwgroupsupply.com/


Figure 4-10: Update

The window contains the following elements: Tab Update Opens the tab for updating the receiver master data.

Login VW B2B Login

Password VW B2B Passwort

The user's password is mandatory.

The password m,ust be provided at each program start, unless the option for permanently storing the password is chosen.

Proxy

Optional proxy server for internet access.

Port

Optional proxy port for internet access.



Save password permanently

Specify wether the password should be saved permanently. The password will be saved unencrypted and therefore should only be selected if this does not create a security risk. If the password ist not saved, it has to be entered after each program start for the update functions to work properly.

Save Saves the settings.

Update program Search for available program updates. Available updates will be shown in a dialog and a download link will be provided.

Update receiver

Update the receiver master data file "Empfaenger.dat". The file "Empfaenger_Additional.dat" with customized receiver data will not be modified.



This dialog informs about availability of a new program version. The download using the default web browser can be started by following the provided link.

Figure 4-11 Update information



4.8.4 Document generation

This window is for the detailed configuration of the document generation. In the upper area are parameters that apply to both, VDA4939 and GTL. Below are tabs with settings specific to VDA3949 or GTL exclusively.

General Settings for Documents Checkbox Move input files after processing: Checkbox for selecting/deselecting of moving processed files to the old directory.

If the checkbox is selected, the input files will be moved to the directory for processed files after processing. They will also be moved if an error occurred during processing.

In addition, if the checkbox is selected, all files from the IN directory will always be processed. The value in the file LastInputDirScan.properties does not have an effect in this mode.

This mode should be chosen if the input files in the IN directory are only processed by the TSB-Generator. If there are other programs using this directory, we recommend not selecting this checkbox.

Checkbox IN files are EBCDIC encoded:

Checkbox for selecting/deselecting if the input file in EBCDIC is encoded.

If your input data VDA4913/DESADV EBCDIC are encoded, you have to make an entry accordingly.

Checkbox Delete PDF-Files after printing: Checkbox for selecting/deselecting deleting the VDA4939 output files after printing them.

The output file can be automatically deleted here after printing the VDA4939 if the files are not required for other purposes.


?




Figure 4-12: Configuration of VDA4939 generation

Tab PUS VDA4939: Opens the tab for configuration of VDA4939 generation.

Checkbox No PDF417 output: Checkbox for selecting/deselecting of displaying 2Dcode labels on the transport document.

If this field has not been selected, the PDF427 barcodes will not be printed on the output documents. Checkbox F1 area to print receipt information: You can specify here whether the F1 Receipt Information will be printed on the VDA4939.

Checkbox E1 area to print additional information: You can specify here whether the E1 Additional Information will be printed on the VDA4939.

Radio button page format:

You can specify the page format for the VDA 4939 here: DIN A4 or U.S. Legal. Number of copies

This allows you to specify how many copies are needed for each document type when creating and/or the PDF.



Checkbox Notes:

Checkbox for selecting/deselecting whether the shipment containts AMES-T, DDP or no notes.

The setting for AMES-T relevant material has to be made here. When sending AMES-T relevant and non-relevant material, separate data records have to be handed over to the TSB-Generator. If you are not sure whether you are delivering AMES-T relevant material to Volkswagen or not, please contact the AMES-T team. In this case, the checkbox must be selected/deselected before importing the data.

Figure 4-13: Configuration of GTL generation

Tab GTL: Opens the tab for configuration of GTL generation.

Checkbox Print area supplier field on GTL: Checkbox for selecting/deselecting of printing the information in the supplier field.

See respective configuration of supplier field text.

Selection of 2D code (in this version disabled and set to Data Matrix):

Configuration of 2D bar code to be either Data Matrix or PDF417.



Radio button label size:

Allows setting the page format for the GTLs. Available options are DIN A5 and AIAG B10. Small KLT

Package types that trigger the generation of small KLT labels. Some types are pre-defined. Additional types can be entered in the input field below.



5. Other Settings Note:

This chapter contains configuration instructions for experienced users and system administrators.

5.1 Settings for the 2DCode label

Due to different hardware configurations in scanners, the scanning procedure can vary in terms of distances between the 2DCodes.

You can therefore set the label size to >mm< in the properties of the TSB-Generator. Please note that the program requires minimum distances. Therefore, the label dimensions slightly differ from the set values depending on the specification.

The following records are available in the file configuration.properties in the directory \\TSB-Generator\config: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>quote>>quote


6. Error Messages Below you can find the possible error messages of the TSB-Generator are listed and explained. XXX stands for the individual part of the error, e.g. for file names.

ERROR_PARSE_VDA4913 Error when importing the VDA4913 file: XXXX

ERROR_CREATING_VDA4939 Error when creating the VDA4939 file: XXX

ERROR_UNKNOWN_FORMAT The format of the input file cannot be recognized: XXX

ERROR_START_ACROBAT It was not possible to start Acrobat

FILE_NOT_FOUND The file XXX cannot be found

ERROR_MOVING_FILE Error when moving the file: XXX

# Suppliers

ERROR_IN_LIEFERANTEN_DATAFILE The shipping point is not assigned to a supplier

ERROR_LIEFERANT_ID The supplier must have a unique ID

ERROR_VERSANDORT_ID The shipping location must have a unique ID

DUPLICATE_LIEFERANT_ID A supplier with this ID already exists

DUPLICATE_VERSANDORT_ID A shipping location with this ID already exists

LIEFERANT_NOT_FOUND A supplier with the following ID XXX was not found

VERSANDORT_NOT_FOUND A shipping location with the following ID XXX was not found

VERSANDORT_WERK_NOT_FILLED No supplier plant for determining the shipping location has been specified

WARN_USING_FIRST_VERSANDORT Use the first shipping location, as only one exists

# Carriers

ERROR_IN_SPEDITEURE_DATAFILE The driver is not assigned to any carrier

ERROR_SPEDITEUR_ID The carrier must have a unique ID

ERROR_FRACHTFUEHRER_ID The driver must have a unique ID

DUPLICATE_SPEDITEUR_ID A carrier with this ID already exists

DUPLICATE_FRACHTFUEHRER_ID A driver with this ID already exists

SPEDITEUR_NOT_FOUND A carrier with the ID TOKEN1 was not found

FRACHTFUEHRER_NOT_FOUND The driver with the ID TOKEN1 was not found



EMPTY_SPEDITEUR_ID The carrier ID is empty

# Receiver

ERROR_IN_EMPFAENGER_DATAFILE The driver is not assigned to any Carrier

EMPFAENGER_NOT_FOUND The receiver with this ID XXX was not found

EMPFANGSORT_NOT_FOUND The reception point with this ID XXX was not found

#

WARN_UNKNOWN_COUNTY_CODE The country code XXX is not known

# Errors while creating VDA4939

ERROR_LOGOFILE_NOT_FOUND The Logo file was not found

# Errors in VDA4913 file

ERROR_MISSING_RECORD The file contains no records XXX

# Errors in DESADV file

ERROR_MISSING_SEGMENT The file does contains no segments XXX

ERROR_PARSING_DESADV_MESSAGE The DESADV-Data contains a structural error: expecting BGM Segment, Segment XXX found.



7. Other TSB-Generator VDA4939 documents This user guide describes the use of the TSB-Generator. Basis for this guide are following documents:

1. Implementation Guidelines transport and shipment documents (TSB Version01) from pdf-EDI

2. Implementation Guidelines Pick-up sheet (PUS)

3. EDI Implementation Guidelines delivery note data VDA4913 / 4 Issue 03/1996

4. EDI Implementation Guidelines delivery note and transport data EDIFACT DESADV

5. EDI Implementation Guidelines Volkswagen / Audi version 09/2009

These documents describe the VDA4939, the input data and the VDA4913 DESADV and the specific requirements of VOLKSWAGEN AG. The TSB-Generator was developed and tested in accordance with these requirements. We reserve the right to make technical changes also to the documents above.



8. Glossary VDA: Verband der Automobilindustrie e.V. (first EDI message standard since 1975)

VDA4939.PDF: Is a synonym for the output file of the TSB-Generator. The file name is as follows: .PDF

ODETTE: Organization for Data Exchange by Tele Transmission in Europe (since 1984)

EDIFACT: Electronic Data Interchange for Administration, Commerce and Transport (Worldwide EDI-Messages standards, since 1986)

AMES-T: Advanced Mobility Engineering and Services for Transportation. AMES-T is a process at Volkswagen to support the logistic procurements. See also: http://www.ames-t.de

TSB: Transport- und Sendlung-Beleg (Transport and shipment document)

GTL: Global Transport Label

WA: Warenanhnger (Goods trailers)

WBS: Shipping Document

TM: Transport-Master (=Transport Document) (Transport master sheet (= transport document)

SM: Shipping-Master (= Shipment Document) (Shipment master sheets master sheet (= shipment document))

SP: Sendungs-Positionsbltter Positionsblatt (= Sendungsbeleg) (Shipment position sheets position sheet (= shipment document))

CC: Consolidation Center: Distribution centers of the VW Spedition

OS: Operating System (e.g. Linux, Windows)

OT: Originalteile (Original parts)

Blocks: Field names and titles within a TSB document

2D-Codes: (two dimensional Barcode) is part of the TM and includes all delivery notes and transport data of transport

JRE = Java Runtime Environment is the runtime environment for JAVA applications

NLK = Neues Logistikkonzept (new logistics concept)

PUS = Pick-up sheet

http://www.ames-t.de/User GuideContents1. Introduction1.1 Objective1.2 History1.2.1 Version 1.01.2.2 Version 1.11.2.3 Version 1.21.2.4 Version 1.31.2.5 Version 1.3.11.2.6 Version 1.3.21.2.7 Version 1.3.31.2.8 Version 1.3.41.2.9 Version 1.41.2.10 Version 2.01.2.11 Version 2.2.01.2.12 Version 2.2.41.2.13 Version 2.2.51.2.14 Version 2.3.01.2.15 Version 2.3.11.2.16 Version 3.0.01.2.17 Version 3.1.01.2.18 Version 3.2.01.2.19 Version 3.3.01.2.20 Version 3.4.02. Information about the TSB-Generator (for administrators)2.1 System requirements2.2 Operation2.2.1 Operating the TSB-Generator2.2.2 Input2.2.3 Processing2.2.4 Output2.2.4.1 Output Documents2.2.5 Data maintenance2.2.6 Brand logos2.3 Network capability2.4 Client Capability2.5 Directories2.6 Multilingualism3. Installation3.1 Download the installation program3.2 Execute the setup program3.3 Master data3.4 Uninstalling the TSB-Generator3.5 Operating the TSB-Generator3.5.1 Data exchange3.5.2 Manual mode3.5.3 Automatic mode3.6 Transport number4. Operating the TSB-Generator4.1 Startup parameters4.2 Main window4.3 Master data4.4 Supplier master data window4.5 Window master data receiver (plant, clients)4.6 Window carrier master data4.7 Manual processing4.7.1 VDA49394.7.2 GTL4.8 Configuration4.8.1 Language4.8.2 Directories4.8.3 Update4.8.4 Document generation5. Other Settings5.1 Settings for the 2DCode label5.2 Print script5.3 Waiting period after printing6. Error Messages7. Other TSB-Generator VDA4939 documents8. Glossary