1

Guide to Electronic Data Interchange between Porsche and its suppliers

Version 4.2 September 2014

Publisher: Dr. Ing. h. c. F. Porsche AG

2

Contents

INTRODUCTION ....................................................................................................................... 5 

1 ELECTRONIC COMMUNICATION (EDI) ................................................................ 6

1.1 Transferring different types of data ............................................................................. 6 1.1.1 Administrative data .................................................................................................... 6 1.1.2 Use of standards ....................................................................................................... 6 1.2 Use of EDI ................................................................................................................. 6

2 DATA PROCESSING – TECHNICAL SOLUTION ..................................................... 7

2.1 Data transfer processing ............................................................................................ 7 2.2 EDI interfaces with suppliers ....................................................................................... 7 2.3 Establishing connections between Porsche and technical partners ................................. 7 2.4 Contingency plan ....................................................................................................... 8

3 EDI CONNECTION ................................................................................................ 9

3.1 EDI connection cycle .................................................................................................. 9 3.2 Supplier communication ........................................................................................... 10 3.3 Technical problems/failure ....................................................................................... 10

4 CONTACTS ....................................................................................................... 11

4.1 EDI coordination Zuffenhausen .................................................................................. 11 4.2 EDI coordination Ludwigsburg (delivery instructions only) ............................................ 11 4.3 EDI coordination Sachsenheim/Ludwigsburg (EDI delivery notes only) .......................... 11 4.4 EDI coordination Leipzig ........................................................................................... 11 4.5 EDI coordination Weissach ........................................................................................ 11 4.6 EDI coordination, finance data (all plants) ................................................................... 11

PORSCHE SUPPLIER COMMUNICATION ............................................................................... 12

5 VIRTUAL FILENAMES AND TECHNICAL PARTNERS ........................................................ 13

5.1 Outgoing messages ................................................................................................. 13 5.2 Incoming messages ................................................................................................. 15 5.3 Naming conventions ................................................................................................. 16

6 SUPPLIER COMMUNICATION ZUFFENHAUSEN ............................................................. 18

6.1 EDI of delivery instruction data .................................................................................. 18 6.1.1 VDA 4905 delivery instruction ................................................................................... 18 6.1.2 ODETTE DELINS delivery instruction .......................................................................... 19 6.2 EDI of DCOs ............................................................................................................ 19 6.2.1 VDA 4915 DCO........................................................................................................ 19 6.2.2 ODETTE DELINS DCO ............................................................................................... 21 6.2.3 Processing under the new logistics concept ............................................................... 21 6.2.4 DCO forecasts and call-offs ...................................................................................... 22 6.3 EDI of JIT/JIS call-offs ............................................................................................... 22 6.3.1 VDA 4916 JIT/JIS call-offs for assembly scopes in scheduled sequence ....................... 22 6.3.2 VDA 4916 JIT/JIS call-offs for assembly scopes in actual sequence ............................. 25 6.4 EDI of delivery note data ........................................................................................... 27 6.4.1 VDA 4913 delivery note ............................................................................................ 27 6.4.2 ODETTE DESADV delivery note ................................................................................. 29

3

6.5 VDA 4907 Remittance advice .................................................................................... 29 6.6 VDA 4938 and 4906 invoice ..................................................................................... 30 6.7 Freight invoice ......................................................................................................... 33

7 SUPPLIER COMMUNICATION, LUDWIGSBURG/SACHSENHEIM ......................................... 34

7.1 VDA 4905 delivery instruction ................................................................................... 34 7.2 EDI of delivery note data ........................................................................................... 35 7.2.1 VDA 4913 delivery note ............................................................................................ 35 7.2.2 ODETTE DESADV delivery note ................................................................................. 36 7.3 VDA 4938 and 4906 invoice ..................................................................................... 37 7.4 EDI of waybill data ................................................................................................... 37 7.4.1 EDIFACT IFTMIN waybill ............................................................................................ 37 7.4.2 EDIFACT IFCSUM waybill ........................................................................................... 37

8 SUPPLIER COMMUNICATION, LEIPZIG ...................................................................... 38

8.1 VDA 4905 delivery instructions ................................................................................. 39 8.2 VDA 4915 DCO........................................................................................................ 40 8.3 Processing under the new logistics concept ............................................................... 41 8.4 VDA 4916 JIT/JIS call-offs ........................................................................................ 41 8.5 VDA 4913 delivery note and transport data ................................................................ 44 8.5.1 Delivery advice for standard purchased parts ............................................................. 46 8.5.2 Special case consignment note ................................................................................. 47 8.5.3 Cumulative daily delivery note (CDDN) ........................................................................ 48 8.5.4 Shipment papers ..................................................................................................... 50 8.6 VDA 4938 and 4906 invoice data .............................................................................. 54 8.7 Credit advice procedure ........................................................................................... 54 8.8 VDA 4921 waybill data ............................................................................................. 55 8.9 VDA 4927 empties processing .................................................................................. 56

9 SUPPLIER COMMUNICATION, WEISSACH .................................................................. 57

9.1 VDA 4905 delivery instruction ................................................................................... 57 9.2 EDI of invoicing data in accordance with VDA 4938 and 4906 ..................................... 58

10 APPENDIX ........................................................................................................ 59

10.1 VDA 4905 delivery instruction Zuffenhausen/Ludwigsburg/Weissach ............................ 59 10.2 VDA 4915 DCO, Zuffenhausen .................................................................................. 64 10.3 VDA 4916 JIT/JIS call-offs/assembly call-offs, Zuffenhausen ........................................ 68 10.4 VDA 4913 delivery note Zuffenhausen ....................................................................... 70 10.5 VDA 4907 remittance advice .................................................................................... 78 10.6 VDA 4938 and 4906 cross-plant invoice (virtual filename (VFN) always xxxxx.ZU.V49xx) 80 10.7 VDA 4921 waybill, Zuffenhausen ............................................................................... 86 10.8 Freight invoice, Zuffenhausen .................................................................................... 89 10.9 Delivery note Sachsenheim/Ludwigsburg VDA 4913 ................................................... 92 10.10 EDIFACT IFTMIN waybill, Ludwigsburg ........................................................................ 96 10.11 EDIFACT IFCSUM waybill, Ludwigsburg ...................................................................... 99 10.12 VDA 4905 delivery instruction, Leipzig ..................................................................... 101 10.13 VDA 4915 DCO, Leipzig ......................................................................................... 105 10.14 VDA 4916 JIT/JIS call-off, Leipzig ............................................................................ 109 10.15 VDA 4913 VG 40 delivery advice/consignment note Leipzig ...................................... 112 10.16 VDA 4913 VG 40 cumulative daily delivery note, Leipzig ........................................... 117 10.17 VDA 4913 consignment note Leipzig, VG 30, 32, 33, 36 .......................................... 122

4

10.18 VDA 4913 consignment note Leipzig, VG 35 ............................................................ 127 10.19 PLG VDA 4921 waybill ............................................................................................ 133 10.20 PLG VDA 4921 waybill to logistics service provider .................................................. 135 10.21 VDA 4927 empties processing ................................................................................ 138

ABBREVIATIONS ..................................................................................................... 140

5

INTRODUCTION Improved goods flow in the supply chain between Porsche and its suppliers requires fast, automated information flows within this complex system in the development and supply phase. The tool that enables all the partners concerned to carry out business transactions with each other is Electronic Data Interchange – EDI1. Using electronic communication between Porsche and its suppliers should lead to information being transferred and used more effectively both internally and between business partners. The information flow preceding, accompanying or following the physical goods must be ensured and thus support smooth running of the logistics and supply chain. This ensures that the supply chain process is designed to enable suppliers to deliver their modules to Porsche in the right quantity, at the right time, in the right place of installation, in the agreed versions and delivery form. Every Porsche partner should be able to access full information updates and react quickly with a targeted response to any problems. The purpose of this guide is to provide our suppliers with useful basic information on EDI along with a current overview of the formats in use at Porsche .

1 EDI: Electronic Data Interchange

6

1 Electronic Communication (EDI)

1.1 Transferring different types of data

1.1.1 Administrative data

All partners are to use standardised electronic message records for transferring business data (delivery instructions, invoices, etc.) All EDI master data is stored centrally for this purpose. To create the master data, the relevant Porsche EDI administrators send out datasheets for suppliers to complete and return. Storing the master data centrally ensures that all important master data is up to date and is accessible to all involved.

1.1.2 Use of standards

Our communications connections are designed in accordance with the public recommendations of the Verband der Automobilindustrie e.V. (VDA) on the electronic exchange of structured data in supply networks.

1.2 Use of EDI

Our suppliers must use electronic communication and therefore should plan for the fact that we will require them to use EDI standards for communicating business data.

7

2 DATA PROCESSING – TECHNICAL SOLUTION

2.1 Data transfer processing

Data transfers with Porsche are processed via the centralised Dr. Ing. h.c. F. Porsche AG (Porsche AG) datacentre. Every area of supplier communication where EDI is employed transfers data using SAP Exchange Infrastructure (SAP XI). In-house editing of EDI data is performed in SAP Exchange Infrastructure, as is the conversion of the data in accordance with national (VDA) and international (ODETTE) standards.

2.2 EDI interfaces with suppliers

EDI communication with Porsche requires a software product which uses a VDA-recommended transfer protocol. The standard transmission process for the European automotive industry and therefore, Porsche, is the modern, industry-wide ODETTE FILE TRANSFER PROTOCOL (OFTP) which is based on ISDN connections. EDI at Porsche is carried out exclusively via point-to-point connections between Porsche and its partners. Our suppliers must take all necessary measures so that an error-free processing of the EDI data is always given. This requires an automatic and continuous processing of the EDI data.

2.3 Establishing connections between Porsche and technical partners

The Porsche AG datacentre provides a 24 hour EDI service for the supplier industry (permanent transmission and reception operability). Connection is established by Porsche via automatic calls to the supplier's communication processor (dial-out procedure). The type of lines available for EDI processing are ISDN multiplex connectors. How Porsche transmits data (e.g. delivery instructions and detailed call-offs (DCOs)) Transfer of data to suppliers is triggered by an automatic call to the supplier (dial-out procedure). Using this process, Porsche ensures that data transfer is performed as soon as the data is created.

8

How Porsche receives data (e.g. delivery notes, invoices) The transfer of data from suppliers is generally triggered by an automatic call from the supplier to the Porsche AG datacentre (DIAL-IN PROCEDURE). The incoming data is routed to its destination system (e.g. goods receipt system) immeduiately following receipt.

2.4 Contingency plan

In order to assure Porsche production and fault-free supply of its plants, both Porsche and its suppliers must have contingency plans in place for all process steps. They come into effect if the system, and thus fault-free delivery, is temporarily unavailable.

9

3 EDI Connection

3.1 EDI connection cycle

The flowchart below shows the activities required by Porsche and the supplier in order to implement an EDI connection. Every Porsche supplier must be EDI-enabled by the time of the pilot production run at the latest. EDI connections are usually discussed in initial meetings between the supplier and Porsche Purchasing. If the supplier has the requisite systems in place for using EDI he transfers his master data to Porsche on a datasheet provide in advance. The transferred data is binding and is effective immediately following entry. So for example, if a supplier provides the wrong ISDN telephone number, no connection can be established. It is also important to inform Porsche immediately of any changes to master data, especially a change of contact person. There is a test phase during which the technical department at Porsche coordinates formats and content with the supplier. During this time, information will be transferred by EDI as well as temporarily by fax. Porsche's technical department analyses the data and coordinates form and content with the supplier's contact person until it is correct. If test operation is stable, EDI will go fully live after mutual agreement. Fax will no longer be used and EDI data will be mandatory.

SUPPLIER

Central facility of partner & transmis-sion of data sheet

PORSCHE

Administration of EDI master data

Data transfer and connection test

Connection of individual formats cooperation

Test

live

10

3.2 Supplier communication

The supplier is responsible for checking that incoming call-offs are complete and factually correct. If anomalies occur, e.g. transfer numbers which are out of ascending series, the contact person in the relevant Porsche department must be informed immediately. The relevant contacts can be found in section 4 and on the EDI datasheet.

3.3 Technical problems/failure

The responsible Porsche contact person must be informed immediately, by telephone and in writing (e-mail, fax), of any supplier problem that may have consequences for Porsche production or activities in progress. In addition, Porsche names emergency contacts for any technical problems or IT system failures and stores these centrally. This guarantees that contact can be made quickly in the case of problems.

11

4 Contacts

4.1 EDI coordination Zuffenhausen

Ms Helene Fleiter/ E-mail: Edi-Werk-Zuffenhausen@porsche.de Ms Melanie Winter/ Tel.: 0711-911-26304/-27665/-24547 Mr Selim Limerer Fax: 0711-911-26242

4.2 EDI coordination Ludwigsburg (delivery instructions only)

Ms Heike Messerschmidt E-mail: Edi-Werk-Ludwigsburg@porsche.de Tel.: 0711-911-23298 Fax: 0711-911-23311

4.3 EDI coordination Sachsenheim/Ludwigsburg (EDI delivery notes only)

Mr Pieter De Fré E-mail: pieter.de_fre@porsche.de Tel.: 0711-911-76024 Fax: 0711-911-76918

4.4 EDI coordination Leipzig

Ms Katja Lauer/ E-mail: Edi-Werk-Leipzig@porsche.de Mr Mario Luft Tel.: 0341-999-13834/ 14097 Fax: 0711-911-13928

4.5 EDI coordination Weissach

Mr Norbert Hausding Email: norbert.hausding@porsche.de Tel.: 0711-911-88805 Fax: 0711-911-84822

4.6 EDI coordination, finance data (all plants)

Mr Joaquim Antunes E-mail: Edi-Rechnungswesen@porsche.de Tel.: 0711-911-27454

12

Porsche supplier communication

Here you can find an overview of the formats used in individual plants. Zuffenhausen Ludwigsburg Leipzig Weissach VDA 4905 delivery instruction x x x x ODETTE DELINS delivery instruction x x x x VDA 4905 incoming delivery instruction x VDA 4915 DCO x x ODETTE DELINS DCO x x Incoming VDA 4915 DCO x VDA 4916 JIT/JIS call-off x x VDA 4916 near-time call-off x VDA 4916 ‘material on site’ acknowledgement

x

VDA 4916 installation time information (ITI)

x

VDA 4916 JIT/JIS call-off incoming

x

VDA 4913 delivery advice x x x VDA 4913 outgoing delivery advice x VDA 4913 consignment note Incoming supplier to supplier

x

VDA 4913 consignment note Goods receipt acknowledgment, outgoing

x

VDA 4913 consignment note Outgoing extraction from consignment store

x

VDA 4913 consignment note Incoming cumulative daily delivery note (CDDN)

x

VDA 4913 consignment note Outgoing stock report

x

VDA 4913 consignment note discrepancy in outgoing delivery

x

credit advice for logistics costs x VDA 4907 remittance advice x x x VDA 4906 or VDA4938 invoice x x x x VDA 4921 incoming waybill x x freight invoice x x VDA 4927 container/empties information outgoing to logistics service provider (LSP)

x

13

Technical part-ner

5 Virtual filenames and technical partners

Porsche can manage a number of technical partners per supplier, meaning that it can transfer messages from suppliers to multiple destination addresses, and receive and process messages from multiple addresses of the supplier.

5.1 Outgoing messages

Outgoing messages from different Porsche plants are separated by plant, i.e. collected in a file for each plant. Porsche plant File name OFTP address Supplier -

Messages are sorted by Porsche plant and sent to one of the supplier's technical partners. The virtual filename of the EDI messages consists of the plant abbreviation, supplier number and interchange format. In principle its composition is as follows: SENDER.RECIPIENT.FORMAT

Zuffenhausen

Ludwigsburg

Leipzig

Plant n

ZU.12345.V4905 O0013….1

LU.12345.V4905 O0013….1

LE.12345.V4905 O0013….1

… …

14

Technical part-ner 1

Technical part-ner 2

A further example shows how sending plant-specific messages allows them to be sent to multiple technical partners, i.e. to send copies to as many of the supplier's partners as necessary. Porsche plant File name OFTP address Supplier -

If the cluster is made up of different supplier numbers belonging to one supplier whose call-offs should be sent to a technical partner using a single SSID but multiple SFIDs, the filename can contain either the individual supplier numbers, or a single, meaningful abbreviation of the supplier name that covers all the supplier plants. This cannot be used for breaking down supplier plants according to the 6-digit supplier number. The following is an example using a consistent virtual filename:

Zuffenhausen

Ludwigsburg

Leipzig

Plant n

ZU.12345.V4905

LU.12345.V4905

LE.12345.V4905

…

O0013….1

O0013….1

O0013….1

…

ZU.RECIPIENT.V4905 O0013….2 (copy)

Technical partner SSID

SFID 1

SFID 2

SFID 3

SFID n

Zuffenhausen

Ludwigsburg

Leipzig

Plant n

ZU.Supplier.V4905

ZU.Supplier.V4905

ZU.Supplier.V4905

ZU.Supplier.V4905

15

5.2 Incoming messages

In incoming messages from suppliers to Porsche, the filename specifies which Porsche plant and destination system the message is intended. Here is a specific example: Supplier File name Porsche system

As with the outgoing message, the virtual filename is configured on the following principle: SENDER.RECIPIENT.FORMAT If the interchange with the supplier involves a cumulative daily delivery note (CDDN), this version cannot be used because a separate mapping is activated for a CDDN.

Technical part-ner

12345.LU.V4913 Porsche System 1

Porsche System 2

Porsche System 3

12345.LE.V4913

12345.ZU.V4913

16

Incoming messages can also use a single virtual filename for a supplier cluster with multiple supplier plants, as long as the technical partner sends them with a single SSID and multiple SFIDs. Furthermore, a suitable abbreviation of the supplier name can be used in the filename instead of individual supplier numbers. Here is an example:

5.3 Naming conventions

Outgoing messages The filename format for outgoing messages from Porsche to suppliers is as follows XX.YYYYY.ZZZZZZZ XX = plant code ZU Zuffenhausen LE Leipzig LU Ludwigsburg WE Weissach YYYYY = supplier number (first 5 digits) ZZZZZZZ = transfer format V4905 VDA 4905 delivery instruction V4907 VDA 4907 remittance advice V4908 VDA 4908 credit advice V4913 VDA 4913 delivery note information (including process types) V4913T VDA 4913 cumulative daily delivery note (CDDN)

Technical partner SSID

SFID 1

SFID 2

SFID 3

SFID n

Porsche system

Porsche system 1

Porsche system 2

Porsche system 3

Porsche system n

Supplier.ZU.V4913

Supplier.ZU.V4913

Supplier.LE.V4913

Supplier.LE.V4913

Supplier.ZU.V4913

17

V4915 VDA 4915 DCO V4916 VDA 4916 production synchronised (JIT/JIS) DCO V4921 VDA 4921 waybill V4927 VDA 4927 empties data ODELINS ODETTE DELINS delivery instruction ODELJIT ODETTE DELJIT DCO Incoming messages The filename format for messages that Porsche receives from suppliers is as follows YYYYY.XX.ZZZZZZZ with the exception of invoices which are always formatted as YYYYY.ZU.V4906 or YYYYY.ZU.V4938 XX = plant code ZU Zuffenhausen LE Leipzig LU Ludwigsburg WE Weissach YYYYY = supplier number ZZZZZZZ = transfer format V4905 VDA 4905 delivery instruction V4906 VDA 4906 invoices V4938 VDA 4938 invoices (Global Invoic) V4913 VDA 4913 delivery note information, standard delivery V4913T VDA 4913 delivery note information for cumulative daily delivery note V4915 VDA 4915 DCO V4916 VDA 4916 JIT/JIS DCO V4921 VDA 4921 waybill OAVIEXP ODETTE AVIEXP delivery note, standard delivery SFRG special format freight invoice SATLAS special format Atlas invoice

18

6 Supplier communication Zuffenhausen Due to the introduction of an integrated logistics system in 2015 in plant Stuttgart-Zuffenhausen, we reserve the right to make changes regarding the specifications of content and message formats described in this chapter and appendix.

6.1 EDI of delivery instruction data

6.1.1 VDA 4905 delivery instruction

Creation of EDI files In principle, Porsche transfers delivery forecast and instruction data in accordance with VDA recommendation 4905. Porsche creates an EDI file of relevant delivery instruction data for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations are not coded. The supplier needs to break down the data by supplier plant. EDI data is prepared straight after material planning at Porsche. Processing at the supplier Please note that a new delivery instruction can only replace an existing instruction if it has the same Porsche part number and Porsche blanket order number. If this is not the case, the delivery instruction cannot be replaced. EDI partners should also check the transmission number to see whether call-offs have been transmitted in series. If a dataset is missing, please inform Porsche immediately so that we can resend the file. Usage Delivery instructions for various requirements can be handled via EDI (production, spare, sample and development parts). Delivery instructions must be based on a valid blanket order from Porsche Purchasing. Dates set by the purchasing department for pilot and 0-production on blanket orders will also be transmitted in the first delivery instruction of the order. Tools and initial samples are generally called off with a Porsche individual order. Delivery instruction management uses a breakdown by production and spare parts materials as determined by production or spares material planning. Call-off date Porsche uses the following VDA-compliant date information for the target entry time of delivery instruction quotas. A delivery instruction for a specific day is in YYMMDD format as per the code directory, for example 070601 => 1 June 2007. Weekly delivery instructions are based on complete weeks regardless of whether the month changes. The date is formatted as per the code directory: YY00WW (requirement for week). It is also possible to send monthly forecasts, which are transmitted as YYMM00.

19

6.1.2 ODETTE DELINS delivery instruction

As an alternative to VDA-compliant delivery instructions, it is also possible to use ODETTE DELINS

6.2 EDI of DCOs

6.2.1 VDA 4915 DCO

Porsche follows VDA 4915 for EDI of DCOs for purchased parts, the requirement for which is determined by the manufacturing progress of defined customer vehicles or by an event in the stock system. A binding delivery date is quoted including date, time and quantity. Data compilation Call-offs are generated by the automatic Porsche DCO system after it carries out corresponding preparations. They are triggered by a specific event (reporting point) during the order or manufacturing cycle of a vehicle or in the stock system (order point, goods issue). Creation of EDI files At set times, Porsche creates an EDI file of relevant DCO data for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations cannot be coded. The supplier must break down the data according to supplier plant. A file of DCO items, and any requirements changes, is created for each supplier number. Note: Record type 559 (DCO trailer record) has the counter for record type 555 attached (see Appendix 10.2). Processing at the supplier EDI partners should check the transmission number to ensure that call-offs have been received in series. If a dataset is missing, please inform Porsche immediately so that we can resend the file. Usage Porsche uses two types of reorder quantity procedures: 1. Gross reorder quantity procedure The requirement from the order generator is transmitted to the supplier once only, without changes (except correction quantity specifications). The goods receipts are not credited.

20

2. Net reorder quantity procedure With this reorder quantity procedure the goods receipts are credited to the requirement. All open call-offs for the relevant part number are then transmitted. If there is a change in requirements, all open requirements for the relevant part number are transmitted. This is the reorder quantity procedure which is normally used for deliveries based on VDA 4915. In principle, the requirement status field indicates which type of reorder quantity procedure is being used. Porsche uses DCOs to transmit not only specific delivery dates but also DCO forecasts. A DCO forecast can be followed either by a specific delivery date or by a JIT/JIS call-off. The date code identifies the type of DCO. Transmission processs for DCOs DCOs can be transmitted in one of two ways: 1. All open requirements for all part numbers are transmitted to the supplier in a pending EDI. 2. Only newly created or modified requirements are transmitted to the supplier in a pending EDI. The latter is generally the transmission process used for deliveries based on VDA 4915 but it can be switched between the two. Note on cumulative received quantity (CRQ) Administration of the cumulative received quantity, which is used for coordinating with the supplier, occurrs simultaneously when the following processes are logged in the goods receipt system:

Logging a goods receipt increases the cumulative received quantity. The DCO is credited at the same time.

Sales returns charged to the supplier (e.g. for quality reasons) reduce the cumulative received quantity.

Quantitative goods receipt corrections (both reductions and increments) are booked on the cumulative received quantity.

This provides an annual net cumulative received quantity including all goods receipts booked by the system from 1 January to 31 December of the current DCO year. The relevant date is the system date of the goods receipt log and not the delivery note date. At Porsche, 'annual' means that the cumulative received quantity will automatically be set to value ‘0’ on 1 January. Circumstances may arise where the net cumulative received quantity is negative after the reset (e.g. due to a waste booking charged to the supplier). In this case Porsche transmits the value ‘0’ because VDA 4915 can only represent positive values. After the next delivery, provided that the delivered quantity is higher than the negative value, the correct cumulative received quantity will appear in the EDI DCO. Porsche transmits the date of zero positioning and the latest cumulative quantity in the designated fields. Rounding of case quantities

21

In certain cases, rounding the DCO to full cases is determined by mutual agreement. If several cases are combined into one packaging level, the call-off will be rounded to the full packaging level. Delivering as an external service provider When delivering component scopes from other Porsche system suppliers, the supplier plant operates as an external service provider (ESP). It receives the call-off copies for the whole component scope of the relevant Porsche contract partners. The ESP must therefore ensure that it filters the relevant material numbers from the call-off copies of the system supplier. In return, the components delivery must be accompanied by a correct EDI delivery note sent to Porsche on behalf of the system supplier. Delivery The volume of data for goods receipts of DCO scopes can be so enormous that creating it manually is no longer economical. Therefore, Porsche considers it essential that DCOs are only used in combination with VDA 4913 EDI delivery notes.

6.2.2 ODETTE DELINS DCO

As an alternative to VDA-compliant DCOs it is also possible to use ODETTE DELINS. The field descriptions for this format are listed in the Appendix.

6.2.3 Processing under the new logistics concept

The new logistics concept of Porsche AG requires extended information exchange. For suppliers, this means that there is additional information in DCOs. For high-turnover component scopes processed using NLC logic, Porsche calls off various time slices per delivery day. This means that a day is divided into multiple delivery times which are shown in the DCO and must be taken into consideration. To control the materials flow throughout the whole process chain from supplier to installation location, internal Porsche routing information is transmitted with the DCO. In addition to the Porsche plant and unloading point, this information includes information on storage location, replenishment route and point of consumption. This additional information is transmitted in fields 09 ‘Customer storage location’ and 16 ‘Point of consumption’ of record type 552. This information, together with ‘Customer plant’ (field 03) and ‘Unloading point’ (field 8) must be printed on the goods labels in accordance with VDA 4902 Version 4, in field 02. The goods receipt dates and times transmitted in record type 554 are to be printed in field 14 (Design change status) of the goods label. Suppliers must provide this additional NLC-specific DCO information back to Porsche, both on the EDI delivery note and on all shipping documents and labels. The above NLC information is also transmitted in standard DCOs. It must be automatically read, and printed on the goods label (VDA 4902). A case-by-case decision is made as to whether it also needs to be provided on the EDI delivery note (VDA 4913).

22

High-frequency deliveries can only be made using the VDA standard. The DCO delivery date is always a binding goods receipt date at Porsche and is transmitted with date and time.

6.2.4 DCO forecasts and call-offs

Call-offs are not only used to transmit specific delivery dates; they can also be used to transmit DCO forecasts. These scheduled forecasts are always followed by an updated, binding detailed call-off. Transmission of an enhanced, updated DCO enables near-term material planning. The scheduled DCO forecast is triggered at Porsche when the assembly sequence is set. The DCO is produced by a virtual reporting point which takes into consideration the latest plant status before starting the bodyshell or assembly. The date code in record type 552, field 13 identifies the type of DCO.

DCO type Date code identifier

Scheduled forecast ‘P’.

Call-off ‘ ’ (blank)

In certain cases, the use of different DCO types is specified per supplier, based on the scope of the delivery.

6.3 EDI of JIT/JIS call-offs

6.3.1 VDA 4916 JIT/JIS call-offs for assembly scopes in scheduled sequence

Porsche uses VDA 4916 for EDI of just-in-time call-offs for selected purchased parts, the requirement for which is determined by the manufacturing progress of defined customer vehicles or by an event in the stock system. A binding delivery date is quoted including time and quantity. JIT/JIS call-offs are used to transmit not only specific delivery dates but also JIT/JIS call-off forecasts. Multiple forecasts can be triggered by different events. The last JIT/JIS call-off for a production number contains the exact delivery date with the sequence number for synchronised delivery. The date and change codes identify the type of JIT/JIS call-off. In certain cases the specific number and scale of JIT/JIS call-off types is specified in writing per supplier, based on the scope of the delivery. Basic technical procedures

23

JIT/JIS DCOs are generated by the automatic Porsche JIT/JIS DCO system following appropriate preparation. They are triggered by a specific event (reporting point) during the order or manufacturing cycle of a vehicle. Creation of EDI files At set times, Porsche creates an EDI file of JIT/JIS call-off data for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations cannot be coded. The supplier must break down the data according to supplier plant. A file of JIT/JIS call-off items is compiled for each supplier number. When the JIT/JIS call-off EDI data is ready, the send requests (starting at specified times) are generated and the transmitted data is stored. JIT/JIS EDI files are archived for 19 days, during which time the data can be resent. Processing at the supplier EDI partners should check the transmission number to ensure that call-offs have been received in series. If a dataset is missing, please inform Porsche immediately so that we can resend the file. Usage In principle the gross reorder quantity procedure is used.

The requirement from the order generator is transmitted to the supplier once only, without changes.

The goods receipt will not be credited. Transmission processs for just-in-time call-offs. JIT/JIS call-offs can be transmitted in one of two ways: 1. All open requirements for all part numbers and production numbers are transmitted to the supplier in a pending EDI. 2. Only new requirements are transmitted to the supplier in a pending EDI. The latter is generally the transmission process used for deliveries based on VDA 4916 but it can be switched between the two. Changes to or cancellations of just-in-time call-offs. Changes to the delivery scope of a production number are not transmitted via the change code A. The combination of production/part numbers to be changed (date correction or cancellation) are deleted using change code ‘L’ = cancellation. Cancellations can be handled in one of two ways:

24

1. For cancellation of a requirement for a vehicle in the system, a record type 662 is generated with identifier L and without a part number in record type 664. All existing requirements for this vehicle must be cancelled. If there are open requirements for this vehicle, these are transmitted in the same VDA 4916 file in an additional record type 662 with the change code blank, i.e. without changes and with the corresponding part number in record type 664. 2. For cancellation of a requirement for a vehicle in the system, a record type 662 is generated with identifier L and with a corresponding part number in record type 664. This record type 664 contains the part numbers to be cancelled and the cancellation only applies to the part numbers entered. The new combination of production/part numbers (changed part number or part number with new delivery date) are transmitted with the change code blank = transmitted without changes. Only the new combinations are transmitted, not the whole scope of part numbers for a production number. Delivery The data volume for goods receipts for JIT/JIS call-off scopes can be so enormous (the production number information for each scope is required) that creating them manually is no longer economical. Therefore Porsche considers it essential that JIT/JIS call-offs are only used in combination with VDA 4913 EDI delivery notes. Content of text records (record type 663) Porsche offers customers the opportunity to personalise their new vehicle via ‘individual numbers’ (I-numbers). I-number scopes are clearly defined and can be broken down to part number level. There may be further personalisation via so-called Z-codes which represent additional modifications. These are personal requests that customers describe verbally and only apply to a small number of vehicles. The scope and its feasibility is agreed with our suppliers. The content of these additional modifications cannot be transmitted to our suppliers via standardised data fields. The possibility of a Z-code arising on parts scopes to be processed on a JIT/JIS call-off, and the procedure in this case, is defined in separate agreements. Daily forecast The JIT/JIS daily call-off forecast is triggered at Porsche when the assembly sequence is set. This occurs around 6.5 days before assembly starts. The daily forecast is transmitted without a time and is identified by the date code ‘T’. Call-off The JIT/JIS call-off is triggered by the updated plant status around 39 hours before assembly starts at Porsche. The information contains a date and time for the production/part number combination and is marked with the date code ‘ ’ (blank).

25

Date code identifier Note that the date code of JIT/JIS call-offs for assembly scopes in scheduled sequence uses different identifiers for the Zuffenhausen and Leipzig plants.

JIT/JIS call-off type Zuffenhausen identifier

Daily forecast ‘T’

Call-off ‘ ’

Order of sequence for upholstery and axles A component sequence separate to that for the vehicle assembly is called off for upholstery and axles. The sequence numbers (record type 662, field 05) differ as follows: Vehicle assembly: 20XXXXXXXXX Upholstery: 30XXXXXXXXX Axle: 51XXXXXXXXX The sequence number can also be sent empty in exceptional cases. For example, in case of reorder for a vehicle in the finishing, there will not be any sequence number created. Sequence call-off scopes for upholstery and axles are also differentiated by their respective production line identifiers in record type 662, field 09 Production area code, as follows: Vehicle assembly: ‘ ’ (blank) Upholstery: 9003 Axle: 9001 Sequencing as an external service provider When sequencing component scopes from other Porsche system suppliers, the sequencer operates as an external service provider (ESP). It receives the call-off copies for the whole component scope of the relevant Porsche contract partners. The ESP must therefore ensure that it filters the relevant material numbers from the call-off copies of the system supplier. In return, the components delivery must be accompanied by a correct EDI delivery note sent to Porsche on behalf of the system supplier.

6.3.2 VDA 4916 JIT/JIS call-offs for assembly scopes in actual sequence

Porsche also uses EDI of JIT/JIS call offs in accordance with VDA 4916 for assemblies in actual sequence. Here, there are three distinct stages in the message type. Daily forecast The JIT/JIS daily call-off forecast is triggered at Porsche when the scheduled assembly sequence is set. This occurs around 6.5 days before assembly starts. The daily forecast is transmitted without a time and is identified by the date code ‘T’. The scheduled

26

sequence of the vehicles in the assembly is transmitted. The gross reorder quantity procedure is used for processing and each piece of information is transmitted once only. e.g. scheduled sequence number: 20111216076 Scheduled forecast The scheduled JIT/JIS DCO forecast is released with the updated plant status about 39 hours before assembly starts at Porsche. The information contains a date and time for the production/part number combination and is marked with the date code ‘P’. The scheduled sequence of the vehicles in the assembly according to the daily forecast is transmitted. e.g. scheduled sequence number: 20111216076 Near-term call-off Using near-term call-off, JIS call-offs can be transmitted to the supplier in actual sequence. This assembly call-off is linked to the takt time when vehicle assembly starts, and the supplier uses it to control JIS processing. Near-term call-offs are marked with the date code ‘K’. The actual sequence of the vehicles in the assembly is transmitted. This information is different to the scheduled sequence of the forecast data. The actual production sequence for a vehicle runs in ascending series. e.g. actual production sequence number: 56.484 The production sequence number can have up to 12 digits, as per the VDA standard. Whether and to what extent VDA 4916 EDI messages are exchanged with a supplier is defined on an individual basis and in writing. Date code identifier Note that the date code of JIS call-offs for assembly scopes in actual sequence uses different identifiers for the Zuffenhausen and Leipzig plants.

JIT/JIS Call-off type Zuffenhausen identifier

Daily forecast ‘T‘

Scheduled forecast ‘P’.

Near-term call-off ‘K’

If the EDI system suffers a technical fault or failure on either side, the contingency plan is put into effect for near-term call-offs. The Zuffenhausen production control station sends an emergency fax after a telephone discussion with the supplier's contact person. The fax contains production numbers as well as their actual sequence. This information has to be

27

logged on the supplier's system manually to ensure that the actual sequence is delivered without any gaps. Sequencing as an external service provider When sequencing component scopes from other Porsche system suppliers, the sequencer operates as an external service provider (ESP). It receives the call-off copies for the whole component scope of the relevant Porsche contract partners. The ESP must therefore ensure that it filters the relevant material numbers from the call-off copies of the system supplier. In return, the components delivery must be accompanied by a correct EDI delivery note sent to Porsche on behalf of the system supplier.

6.4 EDI of delivery note data

6.4.1 VDA 4913 delivery note

The procedure description under VDA 4913 governs the electronic data interchange of delivery note and transport data between supplier and customer as well as additional material flow information between suppliers, external service providers and customers. Delivery note data can be exchanged via EDI with the following Porsche plants: Leipzig Zuffenhausen Ludwigsburg/Sachsenheim

Delivery advice x x x

Stock notification x x x

Goods receipt notification

x

Goods dispatch notification

x

Suppliers must use EDI to notify Porsche that goods have been dispatched. If the supplier does not have the technical capabilities for this, it must put in place a DP service provider as intermediary. The data on the VDA 4913 EDI delivery note data and transport data message, the VDA 4902 goods labels, the VDA 4912 goods dispatch note and the VDA 4922 shipping order must correspond. Data provision The EDI delivery note data of a shipment number provided by the supplier combines a specific unloading point and target goods receipt time. So if a delivery needs to be made to multiple unloading points, separate shipment numbers must be raised for each one. The shipment or load reference number (also transport number) must be on the VDA 4912 EDI goods dispatch note and on the waybill (VDA 4922 shipping order).

28

Time of data transmission Porsche can send and receive data 24 hours a day. On receipt the data is immediately forwarded to the goods receipt computer. The supplier may edit and transmit the data only once he has dispatched the transport or consignment. Timely and correct transmission of the delivery note data is essential for us to monitor materials via planning and goods receipt control. Problem management If the delivery note data cannot be transmitted on time, the relevant goods receipt point has to be informed and revised paperwork provided. Errors in content and form are immediately revised by fax, via the goods receipt clearing points and the supplier's contact person. In the event of a problem, please contact the following e-mail address: lieferantenkoordination@porsche.de Data format EDI delivery note data can be prepared in any version of VDA recommendation 4913. For details of the official VDA standard and the individual fields, please refer to Appendix 10.4. Shipment papers Use of a shipping order (VDA recommendation 4922) is obligatory for deliveries to Porsche. For legal reasons as well as for contingency plans, paper documents are required in parallel with EDI delivery notes. We require EDI goods dispatch notes to be compliant with VDA recommendation 4912. VDA 4902 goods label Porsche uses VDA 4902 (version 04) goods labels for the delivery of production, auxiliary, consumable and raw materials supplies and initial samples. Basic conditions In principle, one material tag has to be created for one case if it contains only one part number. Where mixed shipments in a single transport unit are concerned:

one case/multiple part numbers multiple cases/one part number multiple cases/multiple part numbers

refer to the notes on the VDA recommendation (section 5). The pre-printed form can be completed manually or automatically.

29

Goods labels for production-synchronised deliveries must carry the production number in the ‘Supplier part number’ unless the goods are hazardous and the hazardous goods number needs to be entered instead. In the context of an overall logistics concept, the goods label supplements EDI of the VDA 4913 delivery note data, acting as a receipt accompanying the materials. Important notes In this section we refer explicitly to order number/delivery note number issues. As the order number is transmitted in all Porsche call-offs, the EDI delivery note in record type 713 also has to contain this number. This rule applies to unmixed deliveries as well as scheduled and actual sequence deliveries. Under the VDA standard, if the order number on the delivery note changes, a new delivery note number is mandatory. This system is also relevant for ODETTE messages as all EDI delivery notes in-house at Zuffenhausen are mapped to the VDA format. Under the VDA standard, the delivery note number can be up to 8 digits. Porsche processes the last 6 digits and transmits them back to suppliers in its delivery forecast and DCO data. Please note that therefore the last 6 digits of the delivery note number cannot be repeated within a calendar year.

Also, when generating EDI delivery notes a part number may only appear once within a delivery note number. Repeating the part number in the same delivery note number leads to an error and cannot be booked. All fields of a delivery note have to be filled automatically from the delivery forecast and DCOs/ JIT/JIS DCOs.

6.5 VDA 4907 Remittance advice

EDI of remittance advice files at Porsche is based on VDA 4907. For each payment run, a transmission is created for each supplier and each currency. Explanatory note on record type 911 field 04 supplier number Because the supplier number in SAP has 10 digits it is right aligned with leading zeros. Explanatory note on record type 912 field 04 document type Remittance advices via EDI are processed in SAP Standard by basic type PEXR2001 and message type REMADV. For individual documents settled by a payment, the system

30

forwards only the invoice or credit advice information to the supplier. But VDA 4907 allows for detailed codes here (see appendix 5, VDA standard, issue August 1993). This list of codes was implemented by extending the standard program based on specific procedures (invoices, credit advices, debits, cancellations, etc.) in accordance with VDA specifications. If there is no entry in the ‘SAP – VDA document type’ assignment table then the following will be set ‘01 – invoice’ on credit line item default ‘03 – your credit advice’ on debit line item default Explanatory note on record type 912 fields 05 and 10 supplier invoice number Because fields 05 and 10 only have 8 characters each while the field reference in SAP can have up to 16, the reference or invoice number of the supplier is split. The invoice number is imported right to left. An invoice number of up to 8 digits right to left is imported left-aligned in field 05 and completed with blanks if necessary. Additional digits (i.e. 9-16) are also imported left-aligned in field 10 and completed with blanks if necessary. Explanatory note on record type 912 field 12 remittance advice In principle, the remittance advice number always has 10 digits. Because the field ‘payment reference number’ in the VDA record only has 6 characters, the remittance advice number is read from the right and only 6 characters are imported into the field. To complete the remittance advice, the number sequence 3900 is put in front of this. Explanatory note on record type 919 field 06 payment method The payment method is always ‘2’ (bank transfer).

6.6 VDA 4938 or VDA 4906 invoice

Porsche uses EDI of purchase invoice data as per VDA 4938 or VDA 4906 to transmit invoices for blanket orders (production and spares materials = scope of delivery instruction). In this context, the SBI (self Billing Invoice), (neither in VDA4908 Format, nor in VDA4938) is not supported. All invoices for deliveries of the series and spare parts are obligatorily to send via EDI. Invoices with small amounts must be avoided, several daily deliveries of goods for a material must be collected in only one invoice. VDA 4938: Porsche used the VDA standard guideline. Documents (in German and English) directly from www.vda.de (search term: VDA4938) download. Also exists a link to a validation portal VDA4938 (Web-Checker). To test files Global-Invoic.

31

Time of data transmission Porsche can send and receive data 24 hours a day. Transmission cycle VDA 4906: For the sake of clarity as well as for economic and partly technical reasons, it is advantageous to send all the invoices for a known period in one transmission. . . Transmitting invoices individually should be avoided. Invoices (with the exception of those from multiple VAT IDs and supplier plants) must be sent collectively – preferably once a day – in a single transmission. Transmission number cycles can be selected so as not to overlap. Porsche checks transmission numbers and automatically deletes duplicates. When combining invoices over longer periods (e.g. 7 days), you should take into account the agreed terms of payment. The date on which the invoice is received, and not the invoice date, is the base date for the payment terms. VDA4938: Per invoice is generated on transmission. Transmissions numbers are to start from the number 100000. Problem management You need to make sure that the transmission goes through successfully (i.e. that you receive an acknowledgment). At Porsche, the sequence of transmission numbers does not necessarily have to be ascending. Transmission numbers that are resent are interpreted as duplicates by the Porsche systems and automatically deleted. Therefore, it is useful to reserve a proportion of transmission numbers to use for potential reruns. To prevent errors, always check that the Porsche mandatory fields are correctly filled out. Make sure that the delivery note only appears once on the invoice receipt for each material and each delivery schedule (possibly combine). It must also be taken into account that the invoice itemisation has an impact on processing and fault handling. If one item is wrong, the invoice cannot be processed/booked. Basic technical conditions EDI of invoice data is not dependent on different unloading points e.g. Weissach, Leipzig, Osnabrück, Ludwigsburg, Sachsenheim or Zuffenhausen. The data can be (only for VDA4906 possible) combined and sent in one transmission. Currently the invoicing process only covers so-called ‘production invoices’. These ‘production invoices’ are for all deliveries to production and spares. For spare parts with packaging costs, those costs should be transmitted in record 813 as per VDA 4906. Only materials costs should be in record 814. The invoice total (812) is the sum of record 813 and 814. Also in VDA 4938, the packaging costs are to be transmitted separately in the corresponding segment! Also, note that regardless of which plant in Germany the goods were delivered to, the invoice must always state our VAT no. DE147799625.

32

Your master data (for example: Order- and Materialnumber) and prices must always be kept up to date to allow fast, automatic and problem-free processing. Data format EDI invoice data must be prepared in the format recommended under VDA 4906 or VDA 4938. Later is the implementation also for non-production deliveries, services and others planned in the format VDA4938. Statutory regulations/information The introduction of procedures that will guarantee data authenticity and integrity is planned. EDI for non-production invoices The introduction of EDI (VDA 4938) for the invoicing of individual orders, service provision etc. is planned for a later date. Implementation specifics If no EDI messages are being exchanged between Porsche and a supplier, communications connections have to operate as described earlier under point 3.1. Before EDI goes live there is a test phase, the timeframe of which is agreed with the relevant contact at Porsche. The relevant technical department at Porsche analyses the data and coordinates form and content with the supplier's contact person until it is correct. During the test run, paper invoices still have to be sent to the address on the order so that Porsche can ensure payments are made correctly. Test data loaded onto the system is used only for formal testing. Once the system is stable and error-free, the technical department at Porsche will agree a go-live date. Starting from this date, suppliers must ensure that the documents covered by EDI are no longer sent as hard copy. VDA 4921 waybill The VDA 4921 waybill controls how the electronic data interchange of delivery and transport tracking data is handled between carriers and Porsche. Data transmitted from supplier to carrier, or compiled by the carrier for the supplier, will be completed and prepared by the carrier and forwarded to Porsche AG in accordance with to VDA recommendation 4921. This can involve handling multiple input files from multiple suppliers. The following VDA standards are to be taken into consideration along with the process description: VDA 4913 delivery note and transport data VDA 4920 shipping order data from supplier to carrier VDA 4902 goods label VDA 4912 EDI goods dispatch note VDA 4922 shipping order

33

Important notes It is essential that the content of EDI messages and shipping documents as a VDA 4922 shipping order and additional potential messages or receipts correspond. Deliveries of partial quantities from a delivery note are not allowed. Explanatory notes to record type 751 The data sender's number has to correspond with the registered numbers held by the data recipient. Explanatory notes to record type 752 The bordereau number is a unique code for subsequent records and the same number must be used for the whole year. Explanatory notes to record type 754 The supplier number and the shipment load reference number have to correspond with the information from the supplier to the carrier. For each shipment load reference number only one record 754 may be transmitted within the scope of one bordereau (records 752 and 753). Explanatory notes to record type 755 Delivery note numbers have to be transmitted in ascending sequence and may only be transferred once for each record 754.

6.7 Freight invoice

The current ‘Handbuch Rechnungs-DFÜ Cargo’ (EDI cargo invoicing manual) can be requested separately from Dept. FFF4. Contact: Ms Darocha Tel. +49 711 911 24372, e-mail: sabrina.darocha@porsche.de

34

7 Supplier communication, Ludwigsburg/Sachsenheim

7.1 VDA 4905 delivery instruction

Delivery instructions are used for transmitting aftersales requirements. Delivery instructions are triggered by reclassified requirements, deferred deadlines, quantity or unloading point changes, and cancellations. In addition to classification by date and quantity, delivery instructions contain all the necessary shipping information. Delivery instructions are VDA 4905-compliant. Delivery dates and quantities are understood as binding for the agreed planning time fence under the framework contract. All other quantity information is non-binding forecast data. Delivery date always refers to the time that the supplier delivers to the Porsche unloading point. If unforeseen events put a delivery date at risk, the supplier informs the responsible planners immediately. Creation of EDI files Porsche creates an EDI file of relevant delivery instruction data for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations cannot be coded. The supplier must break down the data according to supplier plant. EDI data is prepared immediately following material planning at Porsche. Processing at the supplier Please note that a new delivery instruction can only replace an existing instruction if it has the same Porsche part number and blanket order number. If this is not the case, the delivery instruction cannot be replaced. EDI partners should also check the transmission number to see whether call-offs have been transmitted in series. If a dataset is missing, please inform Porsche immediately so that we can resend the file. Application Delivery instructions for production and spare parts can be processed by EDI. Delivery instructions must be based on a valid blanket order from Porsche Purchasing. Delivery instruction management uses a breakdown of production and spare parts materials as determined by production or spares material planning. Call-off date Porsche uses the following VDA-compliant date information for the target entry time of delivery instruction quotas. A delivery instruction for a specific day is in YYMMDD format as per the code directory, for example 070601 => 1 June 2007.

35

7.2 EDI of delivery note data

7.2.1 VDA 4913 delivery note

The procedure description under VDA 4913 governs the electronic data interchange of delivery note and transport data between supplier and customer as well as additional material flow information between suppliers, external service providers and customers. Suppliers must use EDI to notify Porsche that goods have been dispatched. If the supplier does not have the technical capabilities for this, it must put in place a DP service provider as intermediary. The data on the VDA 4913 EDI delivery note data and transport data message, the VDA 4902 goods labels, the VDA 4912 goods dispatch note and the VDA 4922 shipping order must correspond. Data provision The EDI delivery note data of a shipment number provided by the supplier combines a specific unloading point and target goods receipt time. So if a delivery needs to be made to multiple unloading points, separate shipment numbers must be raised for each one. The shipment or load reference number (also transport number) must be on the VDA 4912 EDI goods dispatch note and on the waybill (VDA 4922 shipping order). Time of data transmission Porsche can send and receive data 24 hours a day. On receipt the data is immediately forwarded to the goods receipt computer. The supplier may edit and transmit the data only once he has dispatched the transport or consignment. Timely and correct transmission of the delivery note data is essential for us to monitor materials via planning and goods receipt control. Problem management If the delivery note data cannot be transmitted on time, the relevant goods receipt point has to be informed and revised paperwork provided in all cases. Errors in content and form are immediately revised by fax, via the goods receipt clearing points and the supplier's contact person so as to avoid having to resend. Data format EDI delivery note data can be prepared in any version of VDA recommendation 4913. Shipment papers Use of the shipping order (VDA recommendation 4922) is obligatory for deliveries to Porsche. For legal reasons as well as for contingency plans, paper documents are

36

required in parallel with EDI delivery notes. We require EDI goods dispatch notes to be compliant with VDA recommendation 4912. VDA 4902 goods label Porsche uses VDA 4902 (version 04) goods labels for the delivery of production, auxiliary, consumable and raw materials supplies and initial samples. Basic conditions In principle, one material tag has to be created for one case if it contains only one part number. Where mixed shipments in a single transport unit are concerned:

one case/multiple part numbers multiple cases/one part number multiple cases/multiple part numbers

refer to the notes on the VDA recommendation (section 5). The pre-printed form can be filled manually or automatically. In the context of an overall logistics concept, the goods label supplements EDI of the VDA 4913 delivery note data, acting as a receipt accompanying the materials. Important note In this section we refer explicitly to order number/delivery note number issues. As the order number is transmitted in all Porsche call-offs, the EDI delivery note in record type 713 must also contain this number. This rule applies to unmixed deliveries. Under the VDA standard, if the order number on the delivery note changes, a new delivery note number is mandatory. This system is also relevant for ODETTE messages as all EDI delivery notes in-house at Sachsenheim/Ludwigsburg are mapped to the VDA format.

Under the VDA standard, the delivery note number can be up to 8 digits. Porsche Sachsenheim/Ludwigsburg processes the last 6 digits and transmits them back to suppliers in its delivery forecast and DCO data. Please note that the last 6 digits of the delivery note number cannot therefore be repeated within a calendar year.

7.2.2 ODETTE DESADV delivery note

As an alternative to VDA-compliant delivery note data, it is also possible to use ODETTE DESADV. The field descriptions for this format are listed in the Appendix.

37

7.3 VDA 4938 or VDA 4906 invoice

EDI of invoicing is not plant-specific. Please refer to section 6.6 for all the relevant information.

7.4 EDI of waybill data

7.4.1 EDIFACT IFTMIN waybill

Porsche uses EDIFACT IFTMIN waybills to send transport and shipping orders to carriers. They contain information such as the goods description, delivery conditions and packaging data for each individual package. Please refer to the appendix for field descriptions for the information that Porsche sends.

7.4.2 EDIFACT IFCSUM waybill

Porsche uses EDIFACT IFCSUM waybills to send messages to carriers summarising all its individual shipments (shipping orders). They differ from the EDIFACT IFTMIN waybill in that they do not contain information on individual packages but rather, summary transport and shipping data such as the transport document. Please refer to the appendix for field descriptions for the information that Porsche sends.

38

8 Supplier communication, Leipzig

Technical communication between Porsche Leipzig GmbH (PLG) and its suppliers is carried out by EDI. Suppliers must ensure that any failure in their IT system will not cause delivery problems and will not have any impact on production at PLG. Availability of contacts Participating partners name a central contact person for EDI in each relevant business area. These contacts are available to exchange information with everyone involved in the project. The list of named contacts needs to be updated immediately if there are any changes. Processing at the supplier The supplier is responsible for checking that incoming call-offs are complete, using the old/new transmission number in the data records of the transmission concerned. If anomalies occur, the contact person in the relevant Porsche department must be informed immediately. Availability As a rule, Porsche systems operate six days a week, 24 hours a day (18 shifts). 10 pm Saturday to 10 pm Sunday is a scheduled maintenance window. There is no production during this time. Suppliers' systems need to be available on the same schedule as those of Porsche inasmuch as they must be able to receive and process data. If there is any change to the periods when call-offs could be made, PLG keeps suppliers informed. IT system changes If a supplier is planning any IT system parameterisation or programming that will impact on PLG, he needs to let Leipzig know immediately and explain the reasons for the work. The supplier is obliged to update the parameter sheet sent to him and return it to PLG. How to proceed, and carry out possible tests, is then agreed with the relevant person at PLG. Contingency plan To ensure production and accurate supply at PLG, both PLG and its suppliers must have contingency plans in place for all process steps. These come into effect if system availability cannot be restored and problem-free supply is temporarily interrupted, causing assembly bottlenecks or significant reworking. If system errors occur on JIS call-offs, the actual sequence suppliers are sent a call-off list by fax and e-mail. It includes the following data:

- Production number - Sequence number

The production-synchronised forecast as per VDA 4916 has already given the supplier all the other information he requires (e.g. part numbers) so he can reconcile the two. To keep PLG and supplier information complete, the PLG call-off system restarts at the same point where it stopped. The supplier receives the call-off that he already received and

39

serviced using the list. Call-offs provided after the event do not have to be fulfilled with another delivery.

8.1 VDA 4905 delivery instructions

Delivery instructions provide requirements updates in terms of quantities and dates for specified time intervals and periods. They are the basis of all subsequent production-synchronised call-offs. Delivery instructions are compliant with VDA 4905 V4 April 1996. EDIFACT or ODETTE format may also be used. PLG creates an EDI summary file for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations are not coded. The supplier needs to break down the data by supplier plant. Delivery instructions contain part numbers for cumulative requirements on a fixed time horizon. This time horizon divides into various requirements release phases. These are distinguished as: 1. Delivery instructions for specific days Day-based delivery instructions have a time horizon of three weeks. The code format used for this is YYMMDD, as per the code directory. The corresponding quantity is given in the next field, with 9 characters. 2. Delivery instructions for specific weeks Weekly delivery instructions are based on complete weeks regardless of whether the month changes. The code format used for this, based on the code directory, is: 555555, to identify call-off quantities relating to the next listed call-off period. The date is formatted as per the code directory: YY00WW (requirement for week). Note on cumulative received quantity (CRQ) Administration of the cumulative received quantity, which is used for coordinating with the supplier, happens simultaneously when the following processes are logged in the goods receipt system:

Logging a goods receipt increases the CRQ. The DCO is credited at the same time.

Sales returns charged to the supplier (e.g. for quality reasons) reduce the CRQ. Quantitative goods receipt corrections (both reductions and increments) are

booked on the CRQ. The CRQ is annual, i.e. it includes goods receipts and returns booked between 1.1 and 31.12. PLG automatically sets the CRQ to value ‘0’ on 1 January every year. PLG transmits the date of zero positioning and the latest cumulative quantity in the designated fields.

40

8.2 VDA 4915 DCO

PLG uses EDI of VDA 4915 DCOs for purchased parts. Alongside other information, a binding delivery date is quoted including date, time and quantity. The PLG storage location is also transmitted. The VDA 4915 DCO supplements the VDA 4905 delivery instruction. PLG creates an EDI summary file for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations are not coded. The supplier must break down the data according to supplier plant. DCO classifications are always based on full cases. Exceptions are the inflow and outflow of part numbers, for which there is a detailed agreement between PLG planning and its suppliers. Notes on cumulative received quantity (CRQ) Administration of the cumulative received quantity, which is used for coordinating with the supplier, occurs simultaneously when the following processes are logged in the goods receipt system:

Logging a goods receipt increases the CRQ. The DCO is credited at the same time.

Sales returns charged to the supplier (e.g. for quality reasons) reduce the CRQ. Quantitative goods receipt corrections (both reductions and increments) are

booked on the CRQ. The CRQ is annual, i.e. it includes goods receipts and returns booked between 1.1 and 31.12. PLG automatically sets the CRQ to value ‘0’ on 1 January every year. PLG transmits the date of zero positioning and the latest cumulative quantity in the designated fields. Explanatory notes to field content SA 552/08 (unloading point) is a mandatory field and is filled out. This information has to be printed on the goods label (field 2.1). SA 552/09 (customer storage location) is a mandatory field and is filled out. This information has to be printed on the goods label (field 2.2). PLG uses the ‘customer storage location’ information internally to control the materials flow throughout the whole process chain from supplier to installation location. SA 552/16 (point of consumption) is a mandatory field and must be filled out. This field must always be mapped, even if the field is blank in PLG scopes. SA 554/03-04 (call-off date and time) are mandatory fields and are filled out. This provides the target goods receipt date and time. This information has to be printed on the goods label (field 14 – originally ‘Design change status‘). SA 557 is not used.

41

8.3 Processing under the new logistics concept

Porsche's logistics concept requires extended information exchange. For suppliers this means that there is additional information in delivery instructions and DCOs which has to be processed. Delivery instructions are classified by day, Monday to Sunday. DCOs include multiple target goods receipt times (up to 22) per day and part number. For each target goods receipt time, a separate transport record (i.e. a separate record type 712) has to be attached to the VDA 4913 delivery note advice. Additional information on the multiple target goods receipt times for a target goods receipt date are transmitted in record type 554 (items 3 and 4).

8.4 VDA 4916 JIT/JIS call-offs

JIT/JIS call-offs are identified by targeted, vehicle-specific, sequence-specific information linking part numbers to production numbers. JIT/JIS call-offs are carried out in accordance with VDA 4916, Version May 1991. PLG creates an EDI file for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations are not coded. The supplier needs to break down the data by supplier plant. VDA 4916 can be used for the following: 1. Forecast data 2. Call-off data for scheduled sequenced supplier 3. Call-off data for actual sequenced supplier 4. Installation time information 5. Material on site message 6. Subsequent orders 7. JIT/JIS call-off cancellation The different procedures are identified by virtual filenames and the content of the change and date codes: Overview of how the code directory is applied to processes/virtual filenames:

Process

no.

Change code

662/03

Date code

662/12

Date code

664/08

virt. file name

1 Forecast Z P LE.xxxxx.V4916P

2 Scheduled

sequence call-off

= BLANK K LE.xxxxx.V4916

42

3 Actual sequence call-off

= BLANK T ¹) T LE.xxxxx.V4916

4 Installation time

information

D K ¹) K LE.xxxxx.V4916V

5 Material on site R S LE.xxxxx.V4916M

6 Re-order N K LE.xxxxx.V4916

7 Cancellation L K LE.xxxxx.V4916

¹) only call-offs without record type 664, otherwise empty

Explanatory note on date code: Provided that the part numbers record is attached, the date code in record type 664 is filled out. If there is no record type 664 attached, the date code in record type 662 is filled out. Call-off date and time are also given in record type 662, fields 13 and 14. Explanatory notes on message types: Re 1. Sending JIT/JIS call-off forecast data helps to guide sequence suppliers and can

be sent with or without call-off time. Re 2. For scheduled sequence call-offs, the scheduled time for them to enter the

production line is transmitted in record type 664/09 and 10. To provide exact installation quantities for a day, VDA 4916 installation time information is left out (see point 4). The most important information is always the production sequence number in

record type 662/05. Re 3. actual sequence call-offs may or may not correspond with record type 664. Record type 664/09 and /10, the time transmitted is around 4 hours before the

vehicle enters the line. To provide exact installation quantities for a day, VDA 4916 installation time information is left out (see point 4). The most important information is always the production sequence number in

record type 662/05. Re 4. As installation time approaches, precise takt-driven installation timing information is

sent to sequence suppliers. This forms the basis of the cumulative daily delivery note.

Re 5. The ‘material on site’ message may be sent by scheduled sequence suppliers if

they wish. This message contains the PRODNR of the sequence dispatch note and does not trigger a goods receipt booking. The PRODNR on the sequence dispatch note is not checked against load carrier assignment.

43

Re 6. Rework scopes are called off by content like production scopes. The only distinction is in the change code = N. They are delivered via a separate unloading point.

Re 7. A message with the change code ‘L’ indicates that the sequence scope or entire

vehicle is cancelled. Explanatory notes to record type 662 The production sequence number has nine digits. In the VDA 4916 the numbers are separated such that field 05 of record type 662 consists of seven digits in ascending sequence. In field 09/662, two alphanumeric characters specify the sequence type and assembly section. Note that the sequence number in the VDA 4916 forecast or call-off does not necessarily have to correspond with the sequence number in the installation time information. Explanatory notes to record type 663 Porsche offers customers the opportunity to personalise their new vehicle via individual numbers (I-numbers). I-number scopes are clearly defined and can be broken down to part number level. There may be further personalisation via so-called Z-codes which represent additional modifications. These are personal requests that customers describe verbally, and only apply to a small number of vehicles. The transmission of the content of these additional modifications to our suppliers cannot be performed via standardised data fields. When suppliers receive a record type 663 they must ensure that the content is warranted. Record type 663 is only transmitted if the content is relevant to the supplier. Explanatory notes to record type 664 Call-off time In special cases, such as for special vehicles, trade fair press vehicles and where the date code is ‘P’ for forecast data, field 10 – call-off time – can be left empty. However, the call-off date is provided in field 09. The call-off date in forecasts includes call-off time and is sent in the next call-off as part of corresponding daily volumes submission. Special vehicles are called off separately with longer leadtimes and then integrated into the corresponding daily volumes. For scheduled sequence suppliers, the call-off time is the scheduled time that the vehicle enters the line. The VDA 4916 forecast data cannot replace the requirements given in the delivery instruction data or cumulative quantity. The VDA 4916 call-off details the VDA 4905 and confirms it for delivery.

44

Special case for material on site scheduled sequences The material on site process provides an acknowledgment of production numbers delivered for scheduled sequences. Acknowledgement is provided via the VDA 4916. Material on site messages for delivered scheduled sequence scopes are created exclusively by production number. The following call-off implies that the supplier is delivering a JIS scope in a rack. Generally, each sequence rack should be supplied with a sequence dispatch note (see ‘Shipment papers’ section) The material on site message feeds back the production numbers of the sequence dispatch note, regardless of whether the content of the sequence dispatch note and load carrier correspond. No cross check is carried out between the sequence dispatch note and the load carrier content. As the material on site message was based on production numbers, there is no inventory management. The information is transmitted via VDA 4916 with date code S (662/12) and change code R (662/03). PLG transmits the original sequence dispatch note number in record type 662 item 09 (production area code) – label item 2. Production numbers are clearly acknowledged by the separate sequence dispatch note numbers for each delivered call-off group. Installation time information (ITI) Sequence suppliers receive installation time information via the VDA 4916. ITI is based on production numbers. If the supplier is delivering more than one module, the part number records 664 is also attached. The information is transmitted with change code D and date code K. Call-off groups are confirmed in the point of consumption field. ITI is triggered by a fixed reporting point in the direct vicinity of the installation location. The real ITI incorporates the takt offset. The takt offset is the difference between the reporting point sequence takt time and the cycle time of the installation sequence, and is mutually agreed with the JIS supplier.

8.5 VDA 4913 delivery note and transport data

The procedure description under VDA 4913, issue 1, Version 04 (May 1996) governs the electronic data interchange of delivery note and transport data between supplier and customer as well as additional material flow information between suppliers, external service providers and customers. VDA 4913 obliges suppliers to provide notification of shipping via EDI, produce a cumulative daily delivery note and consignment note and to send these to the Porsche system. If the supplier does not have the technical capabilities for this, it must put in place a DP service provider as intermediary. Suppliers must ensure that where delivery note numbers have more than 8 digits, they are printed as unique references on all documents.

45

The following rules apply: EDI messages must be fully completed, otherwise processing is not possible here. Always ensure that the VDA 4913 is produced only once the goods have been physically shipped or loaded onto the HGV. The data on the VDA 4913 EDI delivery note data and transport data message, the VDA 4902 goods labels, the VDA 4912 goods dispatch note and the VDA 4922 shipping order must correspond. Data provision Data is prepared in VDA 4913 format and the VDA 4913 mandatory and optional fields apply. For details of the official VDA standard and the individual fields, please refer to the Appendix. The EDI delivery note data of a shipment number provided by the supplier combines a specific unloading point and target goods receipt time. So if a delivery needs to be made to multiple unloading points and/or target goods receipt times, separate shipping numbers (record type 712) must be raised for each one. The shipment or load reference number (which is also the transport number) must be on the VDA 4912 EDI goods dispatch note and on the VDA 4922 waybill (shipping order). Transmission time Porsche can send and receive data 24 hours a day. The supplier may edit and transmit the data only once he has dispatched the transport or consignment. Timely and correct transmission of the delivery note data is essential for us to monitor materials via planning and goods receipt control. Incoming VDA 4913 VGA 40 records are processed based on the following scenarios:

Delivery advice for standard purchased parts Delivery advice for consignment scopes Delivery advice for body Cumulative daily delivery note for production scopes (version 1) Cumulative daily delivery note for production scopes (version 2) Cumulative daily delivery note for a rework scope

Record types 711, 713 and 716/718 show the different incoming processes: Record type

711/ 11 Record type

713/ 13 Record type 716/

03 Record type 718/

04

Record type 716/ 04

Record type 718/ 14

Re 1 = Blank = Blank = Blank Re 2 <> Blank = Blank = Blank

46

Re 3 = numeric (one production number per record type 712 for a body)

Re. 4.1

= Blank = VDA4916 record type 662/04 (Record type 718/ 04)

= VDA4916 record type 662/04 (Record type 718/ 14)

Re. 4.2

= Blank

= VDA4916 record type 662/05 & SA662/09 (Record type 716/ 03)

= VDA4916 record type 662/05 & SA662/09 (Record type 716/ 04)

Re 5 = N = VDA4916 record type 662/04 (Record type 718/ 04)

Also, the filename must correspond with the delivery advice/cumulative daily delivery note: Delivery advice: XXXXX.LE.V4913 Cumulative daily delivery note: XXXXX.LE.V4913T XXXXX = supplier number (unless otherwise agreed)

8.5.1 Delivery advice for standard purchased parts

Delivery advices for standard parts are not generally accompanied by a record type 716. Special note: field 18 (call-off number) of record type 713 must be completed with a delivery advice. The call-off number of the latest call-off is always entered. If suppliers receive only a delivery instruction, they should use the delivery instruction transmission number; if they receive a DCO, they should use the DCO transmission number. Every target goods receipt time and unloading point transmitted in the VDA 4915 must have a separate shipping number (record type 712). Fields 18 and 19 of record type 712 (target arrival date and target arrival time) are mandatory. The ‘Goods receiver number’ (field 13) of record type 713 is generally not completed The delivery advice contains the supplier numbers from the DCO (record type 711/field 04). The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. The 6th digit, identifying the supplier plant, can only be processed if the first five digits correspond to the accounts payable master.

47

As the order number is transmitted in all Porsche call-offs, the delivery advice in record type 713 also has to contain this number. Under the VDA standard, if the order number on the delivery advice changes, a new delivery note number is mandatory. Always ensure that all the data from calls offs is automatically included in the delivery advices, especially target goods receipt date/time. Record type 715/ field 03 ‘Customer packaging number’ (customer part number) contains the information on the load carrier used. PLG only allows the use of agreed packaging designations. To optimise transport, multiple target goods receipts times or part numbers should be combined into one pallet. The following should be taken into consideration when completing record type 715 Pallet and cover information is provided in the first transport record type 715/13 with label identifier G or M. In the rest of the transport records, only the individual packages will be transmitted, with label identifier S.

8.5.2 Special case consignment note

VDA 4193 governs data exchange for notifying goods receipts, discrepancies, returns, stock, goods dispatch and delivery advice in consignment notes. PLG uses the following process types:

- VGA 30 Receipt notification - VGA 32 Damage in transit, loss, difference, - VGA 35 Stock notification - VGA 36 Goods dispatched notification - VGA 40 Delivery advice

VGA 30 Receipt notification: Goods receipt confirmation for the consignment note is sent if all material is delivered. The goods receipt confirmation is booked based on material, quantity and delivery note item (record type 714). The goods receipt notification is only created and confirmed if the delivery is complete. If the delivery is incomplete then after consultation, the goods receipt is closed and a VGA 30 returned detailing the actual material delivered. The acknowledgement is sent promptly. How often acknowledgements are sent is agreed mutually by LSP and the supplier. Provided the supplier gives an external package ID in the VDA 4913 VGA 40 delivery advice, this will be fed back in the receipt notification.

48

VGA 32 discrepancy: Discrepancy notifications are sent only after an inventory is taken. The notification includes all positive and negative stock changes. External package IDs are acknowledged provided these were previously sent via EDI. VGA 33 Return delivery: Supplier returns are only made at the request of the supplier. From an accounting perspective, return deliveries are only booked from the consignment store to the supplier. VGA 35 Stock notification: Stock notifications are sent once a day on the request of the supplier. They include the delivery note item and the quantity. VGA 36 Goods dispatched notification: Daily entries from the consignment note are collected and sent to suppliers once a day via the VGA 36. Acknowledgement is provided by case. Provided the supplier gives an external package ID in the VDA 4913 VGA 40, this will be fed back in the VGA 36. There is no feedback by batch. The goods dispatched notification presents the supplier's cumulative daily delivery note at the same time and is the basis for invoicing. Transfer of ownership takes place when the goods are taken from the consignment store. The delivery note send from Porsche system must be use as reference for the invoice.

Supplier Porsche

Material delivery

Porsche System

Avis (VDA4913-VA40) [2]

711/08 Supplier No.– Owner of the goods upon arrival of the EDI

Receipt notification (VDA4913-VA30) [3]

Transport damage (VDA4913-VA32)Loss / difference [3a]

Relocation (VDA4913-VA33) [3b]

Stock notification (VDA4913-VA35) [3c]

Collective goods dispatched notification (VDA4913-VA36) [5]

with reference to supplier delivery note no. and cumulative daily delivery note no. (issued by Porsche)

Invoice (VDA4906) [6]

LAB (VDA4905) [1]

Cumulative daily delivery note

(VDA4913-VA40) [4]

Consignment store

Removal, transfer of ownership

8.5.3 Cumulative daily delivery note (CDDN)

The cumulative daily delivery note is generated by suppliers. The supplier adds all the installed scopes from that day to the CDDN. Modules that have not yet been installed are still owned by the supplier and must not be included.

49

Actual sequence suppliers can calculate module installation times themselves (number of cycles x takt time). Scheduled sequence suppliers receive an installation notification from PLG. The CDDN provides the basis for invoicing via VDA 4906 – see item 6.6. Invoicing via VDA 4906 is handled direct by Porsche AG. With respect to JIT/JIS call-off provision there are two possible versions of the CDDN: 1. Use of record type 718 for providing the production number or 2. Use of record type 716 for providing the first and last sequence number The versions to use are chosen by mutual agreement. Cumulative daily delivery note for production scopes Each supplier uses one cumulative daily delivery note and one record type 712 per day. As the order number is transmitted in all Porsche call-offs, the CDDN in record type 713 must also contain this number. Under the VDA standard, if the order number on the CDDN changes, a new delivery note number is mandatory. Version 1: CDDN with record type 718 For each delivery note item record in record type 714 there must be a production number record type 718 with production numbers corresponding to the delivery note item quantities. On this basis, Porsche carries out a plausibility check and automatic goods receipt check. Record type 718 must be filled out absolutely correctly in order for booking to proceed successfully. Version 2: CDDN with record type 716 A text record type 716 must be sent for delivery note item record in record type 714. In record type 716, items 03 and 04 must correspond to the first and last sequence type and sequence number of the relevant delivery note item quantity. In principle, the actual sequence is the one to use for sequence type and number. On this basis, Porsche carries out a plausibility check and automatic goods receipt check. For a successful booking, the following rules must be strictly adhered to: - The sequence number interval need not be interrupted if there are gaps in the sequence call-off (installation quota not 100%). - The sequence number interval needs to be split in both the CDDN and record type 714 if there are gaps in the delivery (missing parts). Each continued sequence interval thus has its own record type 714.

50

Cumulative daily delivery note for a rework scope A record type 712 must be produced for each supplier and rework order. In general, when shipping rework scopes, suppliers need to generate a CDDN via EDI and send it to Porsche. The structure of this CDDN is the same as the one for production CDDNs. The goods receipt is booked by reconciling the rework CDDN with the physical delivery.

8.5.4 Shipment papers

We require EDI goods dispatch notes to be compliant with VDA 4912. Please refer to the Appendix for a template example.

Example of printed form, VDA 4912 goods dispatch note

Use of the shipping order (VDA recommendation 4922) is also obligatory for deliveries to Porsche. For legal reasons as well as for contingency plans, paper documentation is required in parallel with EDI delivery notes. For goods that are subject to customs duty which has not been paid, the supplier also creates a T1 paper for each transport record created (record type 712). Goods subject to customs duty must always be accompanied by an invoice. VDA 4902 goods label

51

Porsche uses VDA 4902 (version 04) goods labels for unmixed deliveries of production, auxiliary, consumable and raw materials supplies and initial samples. The VDA 4902 goods label contains the call-off information from the VDA 4915 DCO. Specific data to be provided here includes the target goods receipt date and time, storage location information (known internally at Porsche as the Route), and the point of consumption (if completed). Fields 2.1/ 2.2/ 2.3 and 14 of the goods label must be completed with the record types and items transmitted in the VDA 4915 DCO, as follows (see illustration):

Goods labelVDA 4902

Call-offVDA 4915

Content

Field 2.1 Record type 522 item 8 Customer unloading point.Field 2.2 Record type 522 item 9 Customer storage location.

Referred to by Porsche as 'route'.Field 2.3 Record type 522 item 16 Customer point of consumption.

Field 11.2 Record type 556 item 3 Packing number (B) as mandatory fieldField 14 Record type 553 items 3 and

4Required customer delivery date in "DD.MM.YYYY HH:MM" formatReferred to by Porsche as "target goods receipt date"."Change status engineering“ is not required by Porsche on the goods label.

A goods label must be produced for each case. Where a single transport unit is a container including:

multiple cases/one part number multiple cases/multiple part numbers

the individual load carriers as well as the overall load unit (container) must be identified with a goods label (individual label and master label).

Load units consisting of one part number only are identified with a master label marked ‘M’. Field 14 remains empty if there are various target goods receipt times.

Load units consisting of cases with mixed part numbers are identified with a master label marked ‘G’ and the text ‘Mixed container’ in field 8 (customer part number). Field 2.2 (storage location) remains empty if there are various storage locations.

Field 9 ‘Quantity’ remains empty. Field 14 remains empty if there are various target goods receipt times.

52

Example form, VDA 4902 goods label (small)

Example form, VDA 4902 goods label (large)

In the context of an overall logistics concept, the goods label supplements EDI of the VDA 4913 delivery note data, acting as a receipt accompanying the materials. Sequence dispatch note

(1) Recipient of goods, short address

(9) Capacity (Q)

(12) Supplier No. (V)

(15) Package No. (S)

(10) Name of delivery, service

(11) Packaging no. Customer(B)

(13) Date

(16) Batch nos. (H)

(2) Unloading point – Storage location – Usage code (3) Delivery note no. (N)

(6) Part No. Customer (P)

Dr. Ing. h.c. F. Porsche AGD-04158 Leipzig

123456

970.558.555.91

20 Test material

25.02.11(14) Design change status

28.02.11 15:30

P0071234546

S123456789 1234567

PT02 / V33

(1) Recipient of goods

(3) Delivery note no. (N)

(8) Customer part no. (P)

(9) Capacity (Q)

(12) Supplier no. (V)

(15) Package no. (S)

(17) Test GmbH, PO Box 678, 12345 Leipzig

(10) Name of delivery, service

(11) Packaging no. Customer(B)

(13) Date

(16) Batch nos. (H)

VDA 4902 goods label,Version 4

(2) Unloading point – Storage location – Usage code

(4) Supplier address (Short name, factory, postcode, town)

(5) Net weight (6) Gross weight (7) No. of packages

Dr. Ing. h.c. F. Porsche AGD-04158 Leipzig

123456

970.558.555.91

20

123456

S123456789 1234567

Test GmbH, 12345 Leipzig

500

Test material

25.02.11(14) Design change status

28.02.11 15:30

550 01

PT02 / V33

P007

53

PLG uses sequence dispatch notes for JIT/JIS deliveries. Every sequence load carrier must be identified with a sequence dispatch note. If a sequence load carrier is made up of several individual cases/technical areas, each of these must be identified with the production number and sequence number in plain text and data matrix code. The sequence dispatch note consists of - Heading - Sequence dispatch note header - n sequence dispatch note items - ISO/IEC 16022 2D barcode The heading is freely selectable and should name the module clearly. Sequence dispatch note header:

Sequence dispatch note items:

The first production number or sequence number combination and the reporting point time must be entered here.

Item Content Origin SDN format 2D barcode format1 Supplier number VDA4916/SA661/04 5-digit 9-digit, left-justified + #2 SDN number Begins with "1" for each call off group on

1/1 of the year and is seamlessly incremented by 1 with each load carrier to the end of the year (zeroed on 31/12 of the year)

7-digit 7-digit, left-justified, + #

3 SDN date First module date - VDA4916/SA664/09 YYMMDD 6-digit, YYMMDD + #4 Number of PRODNR per load carrie Input by Supplier Actual number 3-digit, left-justified + #5 APL/KPL/call off group VDA4916/SA664/07 APL-KPL-call off group 14-digit, left-justified + #6 Unloading point VDA4916/SA664/06 4-digit 5-digit, left-justified + #

Item Content Origin SDN format 2D barcode format1 PRODNR VDA4916/SA662/09 and 05 9-digit 12-digit, left-justified

complete with blanks + #2 Sequence number VDA4916/SA662/04 7-digit 10-digit, left-justified

complete with blanks + #3 Reporting point VDA4916/SA664/10 HH:MM 4-digit, HHMM + #

54

If a supplier is delivering several call-off groups in one rack, he needs to generate and attach 2 separate sequence dispatch notes. An acknowledgement will be sent if the supplier sends a VDA 4916 ‘material on site’ message.

8.6 VDA 4938 or VDA 4906 invoice data

Invoicing for the A price (parts price) via VDA 4906 is handled direct by Porsche AG. EDI of invoicing is not plant-specific. Please refer to section 6.6 for all the relevant information.

8.7 SBI (Self Billing Invoic)

SBI (self Billing Invoic), (neither in VDA4908 Format, nor in VDA4938) is not supported. See section 6.6. PLG handles the invoicing of logistics costs in the credit advice itself. All the necessary information is sent to suppliers by e-mail, fax and post.

55

8.8 VDA 4921 waybill data

VDA 4921 controls how the electronic data interchange of delivery and transport tracking data is handled between carriers and Porsche Leipzig GmbH. The description is hardware dependent. Note As suppliers create separate transport records for each target goods receipt time and unloading point, the result is a waybill or shipping order per target goods receipt time. Objectives:

Fast compilation of VDA 4291 delivery and transport tracking data as advance information (material in transit) for Porsche AG. resulting in fewer queries from carriers.

Improved transparency in the materials flow. Improved data security and quality, resulting in fewer discrepancies between

shipping data and invoicing data. Higher quality packaging inventory record keeping. resulting in reduced costs in

processing discrepancies. Data transmitted from supplier to carrier, or compiled by the carrier for the supplier, will be completed and prepared by the carrier in accordance with VDA 4921 and forwarded to PLG. This can involve handling multiple input files from multiple suppliers. Please refer to the following VDA standards along with the process description: EDI Designation VDA 4913 delivery note and transport data VDA 4920 shipping order data from supplier to carrier Receipts VDA 4902 goods label VDA 4912 EDI goods dispatch note VDA 4922 shipping order Important notes It is essential that the content of EDI messages and shipping documents as a VDA 4922 shipping order, and additional potential messages or receipts, corresponds. Deliveries of partial quantities from a delivery note are not allowed. The scope of VDA 4921 is both incoming and outgoing for Porsche. Please refer to the corresponding field assignments in the Appendix.

56

8.9 VDA 4927 empties processing

All the movement data for cases is created and booked via the logistics service provider. Container pool management is implemented via VDA 4927. The supplier must be able to prove that the VDA 4927 was received, sent and processed. Explanatory notes on VDA 4927 for the exchange of container data with the logistics service provider. Load carrier movement data falls within the scope of this. 1. Load carrier movement data: Process codes are used 10 Production and consignment goods receipt 55 Cancellation of goods receipt access 50/51 Load carrier corrections at the warehouse with/without repacking 70 Findlinge 71 Missing cases 23 Shipment from warehouse 25 Shipment from consignment store 54 Cancellation of shipping

57

9 Supplier communication, Weissach

9.1 VDA 4905 delivery instruction

Delivery instructions provide requirements updates in terms of quantities and dates for specified time intervals and periods. Instructions are VDA 4905-compliant. Where parts are managed exclusively via delivery instruction, the instruction contains all production and shipping information. Call-off dates are understood as delivery dates. Delivery instruction call-offs are often used in conjunction with detailed call-offs (DCO) or production-synchronised (JIT/JIS) call-offs. Porsche mainly processes DCOs via VDA 4915 DCO messages, and JIT/JIS call-offs via VDA 4916 messages. The delivery instruction provides suppliers with a basis for advance material provisioning and capacity planning. It contains only forecast dates. DCOs provide the production information, if it is sent, for possible prefabrication. JIT/JIS call-offs contain additional product information as well as product number and shipping information. Creation of EDI files Porsche creates an EDI file of relevant delivery instruction data for each supplier. The term supplier is defined by the supplier number (5 digits) which is specified in the Porsche blanket order. Supplier locations cannot be coded. The supplier needs to break down the data by supplier plant. EDI data is prepared straight after material planning at Porsche. Processing at the supplier Please note that a new delivery instruction can only replace an existing instruction if it has the same Porsche part number, Porsche blanket order number, unloading point and supplier delivery instruction number. If this is not the case, the delivery instruction cannot be replaced. EDI partners should also check the transmission number to see whether call-offs have been transmitted in series. If a dataset is missing, Porsche must always be informed so that the file can be resent. Usage Delivery instructions for research and development parts can be processed by EDI. A delivery instruction must be based on a valid contract from Porsche Purchasing. Tools and initial samples are generally called off via a Porsche individual order. Call-off date Porsche uses the following VDA-compliant date information for the target entry time of delivery instruction quotas. A delivery instruction for a specific day is in YYMMDD format as per the code directory, for example 070601 => 1 June 2007. Weekly delivery instructions are based on complete weeks regardless of whether the month changes. The

58

date is formatted as per the code directory: YY00WW (requirement for week).

9.2 EDI invoicing with VDA4938 and VDA 4906

EDI of invoicing is not plant-specific. Please refer to section 6.6 for all the relevant information. Paper invoices must be sent for initial samples or research parts, as no text or other pertinent information can be transmitted in a VDA 4906. Later is the implementation planned in format VDA 4938.

59

10 Appendix

10.1 VDA 4905 delivery instruction Zuffenhausen/Ludwigsburg/Weissach

Record type 511: Delivery instruction header record Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer number STRINGE 9 04 Supplier number STRINGE 9 05 Transmission number old NSTRINGE 5 "00000" 06 Transmission number new NSTRINGE 5 "00000" 07 Transmission date NSTRINGE 6 "000000" 08 Zero setting entry date NSTRINGE 6 "000000" 09 Empty STRINGE 83 Record type 512: One-time data of delivery instruction Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer plant STRINGE 3 04 Delivery instruction number

new STRINGE 9 "000000000"

05 Delivery instruction date new NSTRINGE 6 " ", "000000" 06 Delivery instruction number old STRINGE 9 "000000000" 07 Delivery instruction date old NSTRINGE 6 " ","000000" 08 Customer part number STRINGE 22 09 Supplier part number STRINGE 22 10 Final order no. STRINGE 12 11 Unloading point STRINGE 5 12 Customer tag STRINGE 4 13 Unit of quantity STRINGE 2 14 Delivery interval STRINGE 1 15 Production release STRINGE 1 16 Material release STRINGE 1 17 Usage code STRINGE 1 S = production, E = general spares, U =

production and spares 18 Allocation code STRINGE 7 19 Warehouse STRINGE 7 20 Empty STRINGE 5

60

Record type 513: Delimitation and call-off data of delivery instruction Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Creation date of last receipt NSTRINGE 6 " ",

"000000" 04 Delivery note number

Last receipt STRINGE 8

05 Delivery note date Last receipt

NSTRINGE 6 " ", "000000"

06 Last receipt quantity NSTRINGE 12 07 Cumulative received quantity NSTRINGE 10 08 Call-off date NSTRINGE 6 " ", "000000" 09 Call-off quantity NSTRINGE 9 " ", "000000" 10 Empty STRINGE 6 Record type 514: Additional call-off data on delivery instruction Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Call-off date NSTRINGE 6 " ", "000000" 04 Call-off quantity NSTRINGE 9 " " 05 Call-off date NSTRINGE 6 " ", "000000" 06 Call-off quantity NSTRINGE 9 " " 07 Call-off date NSTRINGE 6 " ", "000000" 08 Call-off quantity NSTRINGE 9 " " 09 Call-off date NSTRINGE 6 " ", "000000" 10 Call-off quantity NSTRINGE 9 " " 11 Call-off date NSTRINGE 6 " ", "000000" 12 Call-off quantity NSTRINGE 9 " " 13 Call-off date NSTRINGE 6 " ", "000000" 14 Call-off quantity NSTRINGE 9 " " 15 Call-off date NSTRINGE 6 " ", "000000" 16 Call-off quantity NSTRINGE 9 " " 17 Call-off date NSTRINGE 6 " ", "000000" 18 Call-off quantity NSTRINGE 9 " " 19 Empty STRINGE 3 Record type 515: Additional call-off information on delivery instruction Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Production release start date NSTRINGE 6 "000000" 04 Production release end date NSTRINGE 6 "000000" 05 Production release, cumulative

requirement NSTRINGE 10 "0000000000"

06 Material release start date NSTRINGE 6 "000000" 07 Material release end date NSTRINGE 6 "000000" 08 Material release cumulative

requirement NSTRINGE 10 "0000000000"

61

09 Part number addition STRINGE 22 10 Intermediate supplier STRINGE 9 11 Date of planning horizon NSTRINGE 6 "000000" 12 Point of consumption STRINGE 14 13 Vehicle zero position NSTRINGE 10 "0000000000" 14 Empty STRINGE 18

62

Record type 517: Packaging data of delivery instruction Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Part number customer

packaging STRINGE 22

04 Part number supplier packaging

STRINGE 22

05 Capacity NSTRINGE 7 "0000000" 06 Empty STRINGE 72 Record type 518: Tex data of delivery instruction Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Delivery instruction text STRINGE 40 04 Empty STRINGE 3 Record type 519: Delivery instruction trailer record Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Counter 511 NSTRINGE 7 04 Counter 512 NSTRINGE 7 05 Counter 513 NSTRINGE 7 06 Counter 514 NSTRINGE 7 07 Counter 517 NSTRINGE 7 08 Counter 518 NSTRINGE 7 09 Counter 519 NSTRINGE 7 10 Counter 515 NSTRINGE 7 11 Empty STRINGE 67

63

Example file: 51102PORSCHE 46308 0000000001071120061231 51201L013 0711202 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 51201L013 0711202 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 51201L014 0711203 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 51201L015 0711204 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 5190200000010000004000000400000000000000000000000000010000004 If you require an example file with special content, please get in touch with your Porsche EDI contact.

64

10.2 VDA 4915 DCO, Zuffenhausen

Record type 551: Record header of DCO data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer number STRINGE 9 04 Supplier number STRINGE 9 05 Transmission number old NSTRINGE 5 06 Transmission number new NSTRINGE 5 07 Transmission date NSTRINGE 6 "YYMMDD" 08 Date of zero position for

cumulative received quantity NSTRINGE 6 "000000", "YYMMDD"

09 Empty STRINGE Record type 552: One-time data elements of DCO Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer plant STRINGE 3 04 DCO number new STRINGE 9 05 DCO date NSTRINGE 6 "YYMMDD" 06 Customer part number STRINGE 22 07 Supplier part number STRINGE 22 08 Unloading point STRINGE 5 09 Customer storage location STRINGE 7 10 Critical stock code STRINGE 1 11 Usage code STRINGE 1 12 DCO horizon NSTRINGE 6 "YYMMDD", " ", "000000" 13 Date code STRINGE 1 14 Final order no. STRINGE 12 15 Cumulative quantity

discrepancy STRINGE 10 "0000000000"

16 Point of consumption STRINGE 14 17 Empty STRINGE 4

65

Record type 553: DCO delimitation data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Cumulative received quantity STRINGE 10 04 Date of arrival NSTRINGE 6 "YYMMDD", " ", "000000" 05 Delivery note number STRINGE 8 "00000000" for new scopes 06 Delivery note date NSTRINGE 6 "YYMMDD", " ", "000000" 07 Delivery quantity NSTRINGE 12 08 Delivery status STRINGE 1 09 Date of arrival NSTRINGE 6 "YYMMDD", " ", "000000" 10 Delivery note number STRINGE 8 00000000" for new scopes 11 Delivery note date NSTRINGE 6 "YYMMDD", " ", "000000" 12 Delivery quantity NSTRINGE 12 13 Delivery status STRINGE 1 14 Date of arrival NSTRINGE 6 "YYMMDD", " ", "000000" 15 Delivery note number STRINGE 8 00000000" for new scopes 16 Delivery note date NSTRINGE 6 "YYMMDD", " ", "000000" 17 Delivery quantity NSTRINGE 12 18 Delivery status STRINGE 1 19 Empty STRINGE 14 Record type 554: DCO data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Call-off date NSTRINGE 6 "YYMMDD", " ", "000000" 04 Call-off time NSTRINGE 4 "HHNN", " ", "0000" 05 Call-off quantity NSTRINGE 9 06 Call-off code STRINGE 1 07 Call-off date NSTRINGE 6 "YYMMDD", " ", "000000" 08 Call-off time NSTRINGE 4 "HHNN", " ", "0000" 09 Call-off quantity NSTRINGE 9 10 Call-off code STRINGE 1 11 Call-off date NSTRINGE 6 "YYMMDD", " ", "000000" 12 Call-off time NSTRINGE 4 "HHNN", " ", "0000" 13 Call-off quantity NSTRINGE 9 14 Call-off code STRINGE 1 15 Call-off date NSTRINGE 6 "YYMMDD", " ", "000000" 16 Call-off time NSTRINGE 4 "HHNN", " ", "0000" 17 Call-off quantity NSTRINGE 9 18 Call-off code STRINGE 1 19 Call-off date NSTRINGE 6 "YYMMDD", " ", "000000" 20 Call-off time NSTRINGE 4 "HHNN", " ", "0000" 21 Call-off quantity NSTRINGE 9 22 Call-off code STRINGE 1 23 Call-off date NSTRINGE 6 "YYMMDD", " ", "000000" 24 Call-off time NSTRINGE 4 "HHNN", " ", "0000" 25 Call-off quantity NSTRINGE 9 26 Call-off code STRINGE 1 27 Empty STRINGE 3

66

Record type 555: Additional data for DCO Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Intermediate supplier STRINGE 9 04 Supplementary part number STRINGE 22 05 At zero position of cumulative

quantity NSTRINGE 10 "0000000000"

06 Empty STRINGE 82 Record type 556: Packaging data for Kanban DCOs only Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Part number customer

packaging STRINGE 22

04 Part number supplier packaging

STRINGE 22

05 Capacity NSTRINGE 7 06 Empty STRINGE 72 Record type 557: DCO text data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Text 1 STRINGE 40 04 Text 2 STRINGE 40 05 Text 3 STRINGE 40 06 Empty STRINGE 3 Record type 559: DCO trailer record Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Counter record 551 NSTRINGE 7 04 Counter record 552 NSTRINGE 7 05 Counter record 553 NSTRINGE 7 06 Counter record 554 NSTRINGE 7 07 Counter record 556 NSTRINGE 7 08 Counter record 557 NSTRINGE 7 09 Counter record 559 NSTRINGE 7 10 Counter record 555 NSTRINGE 7 11 Empty STRINGE 67

67

Example file: 55102PORSCHE 47914 0000400005071210061231 55202L0100000000307111409D.300.037.M PT01 S071123 731893 0000000000 55301000000015207111211-12-00 000000018000I 000000000000 000000000000 554020711041200000000012 0711070000000000018 0711080000000000012 0711090000000000084 0711090000000000126 0711120000000000084 554020711130000000000078 0711140000000000084 0711150000000000084 0711160000000000042 0711160000000000036 0711190000000000084 554020711200000000000078 0711210000000000078 0711220000000000084 0711230000000000036 0711230000000000042 000000 000000000 55501 0000000002 5590200000010000001000000100000030000001000000100000010000001 If you require an example file with special content, please get in touch with your Porsche EDI contact.

68

10.3 VDA 4916 JIT/JIS call-offs/assembly call-offs, Zuffenhausen

Record type 661: Record header of JIT/JIS call-off data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGA 3 02 Version NSTRINGA 2 03 Customer number STRINGA 9 04 Supplier number STRINGA 9 05 Transmission number old NSTRINGA 5 06 Transmission number new NSTRINGA 5 07 Transmission date NSTRINGA 6 08 Empty STRINGA 89 Record type 662: VIN data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGA 3 02 Version NSTRINGA 2 03 Change code STRINGA 1 04 Production number STRINGA 10 05 production sequence number STRINGA 12 06 Customer plant STRINGA 3 07 Unloading point STRINGA 5 08 Point of consumption STRINGA 14 09 Production area code STRINGA 7 for axle scopes: „9001“

for upholstery scopes: „9003“ 10 Production area date NSTRINGA 6 11 Production area time NSTRINGA 4 12 Date code STRINGA 1 13 Call-off date NSTRINGA 6 14 Call-off time NSTRINGA 4 15 Special specification STRINGA 12 16 Type/design sample STRINGA 8 17 Chassis number STRINGA 19 18 No. of vehicles NSTRINGA 9 19 Empty STRINGA 2 Record type 663: Text record Item Data element Field

type Length Default/Remark

01 Record type NSTRINGA 3 02 Version NSTRINGA 2 03 Number plate STRINGA 1 04 Text 1 STRINGA 35 05 Text 2 STRINGA 35 06 Text 3 STRINGA 35 07 Empty STRINGA 17

69

Record type 664: Part number data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGA 3 02 Version NSTRINGA 2 03 Customer part number STRINGA 22 04 Unit of quantity STRINGA 2 05 Call-off quantity NSTRINGA 9 06 Unloading point STRINGA 5 07 Point of consumption STRINGA 14 08 Date code STRINGA 1 09 Call-off date NSTRINGA 6 10 Call-off time NSTRINGA 4 11 Design change status STRINGA 14 12 Empty STRINGA 46 Record type 669: Trailer record Item Data element Field

type Length Default/Remark

01 Record type NSTRINGA 3 02 Version NSTRINGA 2 03 Counter record 661 NSTRINGA 7 04 Counter record 662 NSTRINGA 7 05 Counter record 663 NSTRINGA 7 06 Counter record 664 NSTRINGA 7 07 Counter record 669 NSTRINGA 7 08 Empty STRINGA 88 Example file 66101PORSCHE 46308 0000200003080121 66201 3100101 1000101 L01 MP 0711010000 0000000000 F71CA 000000000 664014F0.907.275.B ST000000001ET01 XM4X72REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001ET01 XM4X72REIFEN K0801161200 664017L0.601.307.P ST000000001ET01 XM4X72REIFEN K0801161200 664014F0.907.275.B ST000000001ET01 XM4X74REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001ET01 XM4X74REIFEN K0801161200 664017L0.601.307.P ST000000001ET01 XM4X74REIFEN K0801161200 664014F0.907.275.B ST000000001 XM5X73REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001 XM5X73REIFEN K0801161200 664017L0.601.307.P ST000000001 XM5X73REIFEN K0801161200 664014F0.907.275.B ST000000001ET01 XM5X75REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001ET01 XM5X75REIFEN K0801161200 664017L0.601.307.P ST000000001ET01 XM5X75REIFEN K0801161200 66401L7L.000.100. ST000000001DT01 XX5X97E-REIFENK0801162100 6690100000010000001000000000000130000001 If you require an example file with special content, please get in touch with your Porsche EDI contact.

70

10.4 VDA 4913 delivery note Zuffenhausen

In principle, all the fields listed for record types 711, 712, 713, 714, 715 and 719 are mandatory at Porsche and must be completed. Record type 718 must only be used for JIT/JIS scopes. Record type 711: Header record of delivery note/transport data Item

Data element Field type

Mandatory/optional

Length

Default/Remark

01 Record type NSTRINGE M 3 02 Version NSTRINGE M 2 03 Customer number NSTRINGE M 9 04 Supplier number NSTRINGE M 9 The supplier number must be

transmitted as a 6-digit supplier plant number.

05 Transmission number old

NSTRINGE M 5

06 Transmission number new

NSTRINGE M 5

07 Transmission date NSTRINGE M 6 08 Sub-supplier number STRINGE K 9 09 Carrier number STRINGE K 9 10 Warehouse code STRINGE K 1 11 Delivery identifier STRINGE M 1 12 Empty STRINGE M 65

71

Record type 712: One-time data elements of transport record Item Data element Field

type Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Shipment load

reference number NSTRINGE M 8 Important:. Shipment reference

numbers may not be repeated within the same calendar year. All the delivery notes for an unloading point and target goods receipt date must be combined under one shipment reference number.

04 Supplier plant STRINGE K 3 05 Carrier STRINGE M 14 Attach name of carrier. 06 Carrier handover date NSTRINGE M 6 07 Carrier handover time NSTRINGE M 4 "HHMM" 08 Gross shipment

weight NSTRINGE M 7

09 Net shipment weight NSTRINGE M 7 10 Freight terms code STRINGE M 2 11 Forwarder's EDI code STRINGE K 1 12 No. of packages NSTRING M 4 The number of packages is the

sum of the tradable transport units. 13 Customer transport

partner number STRINGE M 14 The transport partner’s number

must be attached: 183230 = Rhenus Freight 209000 = UPS 309040 = IN-Time 999990 = special trip

14 Means of transport code

NSTRING M 2

15 Means of transport number

STRINGE M 25

16 Tariff zone code STRINGE K 1 17 Tariff zone STRINGE K 8 18 Target date of arrival NSTRINGE M 6 "YYMMDD", the date must be

automatically taken from the DCO or JIT/JIS call-off.

19 Target time of arrival NSTRINGE M 4 ‘HHMM’, arrival time must be automatically taken from the DCO or JIT/JIS call-off.

20 Loading metres NSTRINGE K 3 21 HGV type code NSTRINGE K 1 22 Empty STRINGE M 3

72

Record type 713: One-time data elements of delivery note Item Data element Field

type Mandatory/ optional

Length

Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Delivery note number NSTRINGE M 8 Important: The last 6 digits of the

delivery note no. are processed and then returned in the delivery instruction/DCO. These may not be repeated within the same calendar year.

04 Shipping date NSTRINGE M 6 05 Unloading point STRINGE M 5 06 Shipment type STRINGE M 2 07 Customer identifier

(delivery instruction) STRINGE K 4 The entry provides a code identifying

the relevant material planners and should be taken automatically from the delivery forecast/instruction.

08 Final order no. STRINGE M 12 09 Process code NSTRINGE M 2 10 Empty STRINGE M 4 11 Customer plant STRINGE M 3 12 Consignment NSTRINGE K 8 13 Goods recipient number STRINGE M 9 14 Empty STRINGE M 1 15 Customer storage

location STRINGE M 7 Transmission of this is only required

for processing under the new logistics concept.

16 Supplier number STRINGE M 9 17 Point of consumption STRINGE M 14 Transmission of this is only required

for processing under the new logistics concept and for sequence processing (if the point of consumption field in the relevant VDA 4916 is filled out).

18 Call-off number STRINGE K 4 19 Customer tag STRINGE K 6 20 Customer

documentation number STRINGE K 14

21 Empty STRINGE M 5

73

Record type 714: Delivery note item data Item Data element Field

type Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Customer part

number STRINGE M 22

04 Supplier part number STRINGE M 22 05 Country of origin STRINGE M 3 06 Delivery quantity NSTRINGE M 13 07 Unit of quantity STRINGE M 2 08 Delivery quantity NSTRINGE K 13 09 Unit of quantity STRINGE K 2 10 VAT rate NSTRINGE K 3 11 Empty STRINGE M 1 12 Delivery note item

number NSTRINGE M 3

13 Call-off code STRINGE M 1 ‘P’ for JIT/JIS call-offs. If marked with ‘P’ then the corresponding production number must be transmitted with record type 718.

14 Batch number STRINGE K 15 15 Usage code STRINGE M 1 16 Hazardous materials

code STRINGE K 8

17 Preferential status STRINGE M 1 18 Dutiable goods STRINGE M 1 19 Empty STRINGE M 1 20 Inventory status STRINGE M 1 21 Changed version code STRINGE M 2 22 Original delivery note

number STRINGE K 8

74

Record type 715: Packaging data (Porsche mandatory record) Packaging data must be transmitted with the information from supplier-specific packaging instructions. When entering the packaging information please keep to the following rules:

G = (Gemischt) mixed label or M = master label; use with pallets S = Single label; use with small load carriers = cover without label identifier

Item Data element Field type

Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Packaging number

Customer STRINGE M 22 The packaging code should be taken

from the packaging instructions. 04 Packaging number

Supplier STRINGE M 22

05 No. of packaging units NSTRINGE M 13 The number of packaging units with the packaging code entered under item 3.

06 Delivery note item number

NSTRINGE M 3

07 Capacity NSTRINGE M 13 08 Package number from STRINGE M 9 This field must be entered for

packaging labelled ‘M’ or ‘G’ (pallet) and ‘S’ (small load carrier) but not for those labelled " " blank (cover).

09 Package number to STRINGE M 9 This field may only be used for packaging labelled ‘S’ (small load carrier), not for those labelled ‘M’ or ‘G’ (pallet) or " " blank (cover).

10 Packaging dimensions NSTRINGE K 12 11 Stacking parameter STRINGE K 1 12 Stock call-off number STRINGE K 15 13 Label identifier STRINGE M 1 ‘M’ for pallets

‘G’ for mixed pallets ‘S’ for small load carriers ‘ ’ (blank) for covers

14 Packaging identifier STRINGE K 1 15 Ownership identifier STRINGE K 1 16 Empty STRINGE M 1

75

Record type 716: Text data for item Item Data element Field

type Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Text 1 STRINGE M 40 04 Text 2 STRINGE K 40 05 Text 3 STRINGE K 40 06 Empty STRINGE M 3

76

Record type 717: Individual package record for item Item Data element Field

type Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Individual package

number STRINGE M 15

04 Delivery quantity NSTRINGE M 13 05 Unit of quantity STRINGE M 2 06 Delivery quantity NSTRINGE K 13 07 Unit of quantity STRINGE K 2 08 Batch number STRINGE K 15 09 Empty STRINGE M 63 Record type 718: Production number data (Porsche mandatory record for sequence processing) This record can be repeated. After 11 production numbers a new record type 718 must be produced. Item Data element Field

type Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Delivery note number NSTRINGE M 8 04 Production number 1 STRINGE M 10 05 Production number 2 STRINGE K 10 06 Production number 3 STRINGE K 10 07 Production number 4 STRINGE K 10 08 Production number 5 STRINGE K 10 09 Production number 6 STRINGE K 10 10 Production number 7 STRINGE K 10 11 Production number 8 STRINGE K 10 12 Production number 9 STRINGE K 10 13 Production number 10 STRINGE K 10 14 Production number 11 STRINGE K 10 15 Empty STRINGE M 5 Record type 719: Trailer record of delivery note/transport data Item Data element Field

type Mandatory/ optional

Length Default/Remark

01 Record type STRINGE M 3 02 Version STRINGE M 2 03 Counter record 711 NSTRINGE M 7 04 Counter record 712 NSTRINGE M 7 05 Counter record 713 NSTRINGE M 7 06 Counter record 714 NSTRINGE M 7 07 Counter record 715 NSTRINGE M 7 08 Counter record 716 NSTRINGE M 7 09 Counter record 718 NSTRINGE M 7 10 Counter record 719 NSTRINGE M 7 11 Counter record 717 NSTRINGE M 7 12 Empty STRINGE M 60

77

Example file 71103RVS 400012 0000400005071120 000045216 7120310811061010Nybrok Oy 07082910360004529000452801 0045 01WCK-857 00000000000000 7130310069224070828KA 03 200000 60100000000 0006 71403987.552.101.13 A11 987.552.101.13 A11 0040000000001000ST0000000000000ST000 001 S G 71802100692240001480450 71403987.552.101.12 9C6 987.552.101.12 9C6 0040000000001000ST0000000000000ST000 002 S G 71802100692240001480455 71403987.552.101.12 9D7 987.552.101.12 9D7 0040000000001000ST0000000000000ST000 003 S G 71802100692240001480452 71403987.552.101.12 9L4 987.552.101.12 9L4 0040000000001000ST0000000000000ST000 004 S G 71802100692240001380748 71403987.552.102.12 9L4 987.552.102.12 9L4 0040000000001000ST0000000000000ST000 005 S G 71802100692240001480458 71403987.552.101.11 N12 987.552.101.11 N12 0040000000001000ST0000000000000ST000 006 S G 71802100692240001380731 […] 7130310069251070828KA 03 60100000000 0006 71403987.552.102.11 8G2 987.552.102.11 8G2 0040000000001000ST0000000000000ST000 001 S G 71802100692510001380768 71403987.552.101.12 9L4 987.552.101.12 9L4 0040000000001000ST0000000000000ST000 002 S G 71802100692510001480484 71403987.552.102.12 9D7 987.552.102.12 9D7 0040000000001000ST0000000000000ST000 003 S G 71802100692510001380766 71403987.552.101.11 3S9 987.552.101.11 3S9 0040000000001000ST0000000000000ST000 004 S G 71802100692510001480467 If you require an example file with special content, please get in touch with your Porsche EDI contact.

78

10.5 VDA 4907 remittance advice

Record type 911 Item Data element Field type Length Default/Remark 01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer number STRINGE 9 04 Supplier number STRINGE 9 05 Transmission number old NSTRINGE 5 06 Transmission number new NSTRINGE 5 07 Transmission date NSTRINGE 6 "YYMMDD" 08 Payment date NSTRINGE 6 "YYMMDD" 09 Payment number STRINGE 6 10 Empty STRINGE 77 Record type 912 Item Data element Field type Length Default/Remark 01 Record type STRINGE 3 02 Version STRINGE 2 03 Delivery note number STRINGE 8 04 Document type STRINGE 2 05 Invoice number STRINGE 8 06 Invoice date NSTRINGE 6 "YYMMDD" 07 Invoice final value NSTRINGE 13 08 Plus/minus sign STRINGE 1 09 Amount of discount NSTRINGE 13 10 Book number STRINGE 8 11 Currency STRINGE 3 12 Payment number STRINGE 6 13 Customer plant STRINGE 3 14 Empty STRINGE 52 Record type 919 Item Data element Field type Length Default/Remark 01 Record type STRINGE 3 02 Version STRINGE 2 03 Counter record 911 NSTRINGE 7 04 Counter record 912 NSTRINGE 7 05 Counter record 919 NSTRINGE 7 06 Payment method STRINGE 1 07 Payment final value NSTRINGE 13 08 Final value of discount NSTRINGE 13 09 Invoice total NSTRINGE 13 10 Empty STRINGE 62

79

Example file: 91101761031 0000110020000000001070827070817 91202 01123 060801000000238000010000000000000 978704302 919010000001000000100000012000000238000000000000000000000002380000 If you require an example file with special content, please get in touch with your Porsche EDI contact.

80

10.6 VDA 4938 or VDA 4906 cross-plant invoice

Mandatory (only) for series and spare part deliveries! VDA 4938: VFN always xxxxx.ZU.V4938 Porsche used the VDA standard guideline. Documents (in German and English) directly from www.vda.de (search term: VDA4938) download. Also exists a link to a validation portal VDA4938 (Web-Checker). To test files Global-Invoice. VDA 4906 (virtual filename (VFN) always xxxxx.ZU.V4906): Invoice type 811 (Header record, mandatory record), 1 x per transmission (EDI cycle) Item Field name

VDA K M

Byte lgth

from to

Content in acc. with VDA 4906 incl. Porsche-specific extension tag if applicable

01 Record type M 3 1-3 Constant "811" must be present. 02 Version number M 2 4-5 Entry = 02 03 Customer number M 9 6-14 ID number that the supplier assigns to Porsche. All data in

a record structure containing a customer number field are subject to data protection regulations. Left-justified entry.

04 Supplier number M 9 15-23 ID number that Porsche assigns to a supplier. All data in a record structure containing a supplier number field are subject to data protection regulations. Left-justified entry.

05 Transmission number old

M 5 24-28 Each EDI cycle is assigned a number in series. The old transmission number is the last cycle. On the first cycle this is a space.

06 Transmission number new

M 5 29-33 The transmission number may be used once only. Transmissions with a number that has already been used are automatically deleted by Porsche. An uninterrupted ascending sequence is not required. Right-justified entry with leading zeros. No decimal point.

07 Transmission date M 6 34-39 In the format: YYMMDD. 08 VAT no. of

recipient. M 20 40-59 Porsche VAT no. Regardless of which plant in Germany the

goods were delivered to, this is always: DE147799625 Left-justified entry.

09 VAT no. of sender. M 20 60-79 VAT no. for the sender. Mandatory field for goods deliveries within the EU. Federal Central Tax Office (BZSt) identification number if applicable. Left-justified entry.

10 Empty K 49 80-128

Spare digits filled with blanks.

M = mandatory (Muß) K = optional (German deisgnation = Kann) (at Porsche)

81

Record type 812 (Invoice data, mandatory field), 1 per invoice

Item Field name VDA

K M

Byte lgth

from to

Content in acc. with VDA 4906 incl. Porsche-specific extension tag if applicable

01 Record type M 3 1-3 Constant "812" must be present. 02 Version number M 2 4-5 Entry = 02 03 Invoice number M 8 6-13 ID no. that the supplier assigns to a commercial invoice

that he has created. Right-justified entry. 04 Invoice date M 6 14-19 In the format YYMMDD 05 Amount of VAT M 13 20-32 Sum of products – fee x VAT rate: 100 of all items (record

type 814) of the same invoice. Right-justified entry with 2 decimal points, and leading zeros.

06 Invoice final value M 13 33-45 Sum of total price of all invoice items (record type 814), shipping and packaging costs (record type 813) plus applicable VAT; enter with 2 decimal points, right-justified with leading zeros.

07 Currency M 3 46-48 For code format, see ISO 4217-1978; (see code directory appendix, e.g. 978 for EUR).

08 Reference number

K 10 49-58 Usually: constant blanks; exception: definitions must be established by EDI participants; left-justified entry.

09 VAT rate M 3 59-61 The VAT rate must be the same for all items on the invoice; enter with 1 decimal point, right-justified with leading zeros.

10 Porsche plant K 3 62-64 Porsche plant where the goods are to be delivered. 11 Fee M 13 65-77 Sum of total price of all invoice items (record type 814),

shipping and packaging costs (record type 813) net of VAT. 2 decimal points.

12 Empty K 51 78-128 Spare digits filled with blanks. M = mandatory K = optional (at Porsche)

82

Record type 813 (Delivery data, mandatory field), 1 per delivery note

Item Field name VDA

K M

Byte

lgth

from to

Content in acc. with VDA 4906 incl. Porsche-specific extension tag if applicable

01 Record type M 3 1-3 Constant "813" must be present. 02 Version number M 2 4-5 Entry = 01 03 Delivery note number M 8 6-13 ID number that the supplier assigns to a delivery

note. Right-justified entry. 04 Shipping date M 6 14-19 In the format YYMMDD 05 Unloading point K 5 20-24 ID no. for the location receiving the goods at the

Porsche plant concerned. Left-justified entry. 06 Shipment type K 2 25-26 2-digit code. (see code directory for composition) 07 Orderer's tag K 4 27-30 Allocated from delivery instruction or order header

data. 08 Final order no. M 12 31-42 ID number that Porsche assigns to an order or

blanket order. For contracts, the individual call-off order number is always used. Left-justified in printable format. Numeric only – no special characters.

09 Shipping costs M 13 43-55 For the delivery concerned. Entry: Right-justified with 2 decimal points, and leading zeros. Note: invoice total (record 812 = 813 + 814)

10 Packaging costs M 13 56-68 For the delivery concerned. Entry: Right-justified with 2 decimal points, and leading zeros. Note: invoice total (record 812 = 813 + 814)

11 Empty K 60 69-128

Spare digits filled with blanks.

M = mandatory K = optional (at Porsche)

83

Record type 814 (Invoice item data, mandatory field), 1 per invoice item (always one 813 per 814)

Item Field name VDA

K M

Byte

lgth

from to

Content in acc. with VDA 4906 incl. Porsche-specific extension tag if applicable

01 Record type M 3 1-3 Constant "814" must be present. 02 Version number M 2 4-5 Entry = 03 03 Porsche part number M 22 6-27 ID number that Porsche assigns to an item, package

or other service. Left-justified in printable format. 04 Supplier part number K 22 28-49 ID number that the supplier assigns to an item,

package or other service. Left-justified in printable format.

05 Delivery quantity M 13 50-62 Right-justified entry with 3 decimal points, and leading zeros.

06 Price unit M 2 63-64 2-digit numeric code (see code directory). 07 Unit price M 13 65-77 Price net of VAT; right-justified entry with 2 decimal

points, and leading zeros. 08 Total price M 13 78-90 Delivery quantity x net unit price; right-justified entry

with 2 decimal points, and leading zeros. 1) Porsche transaction

09 Empty M 3 91-93 Spare digits filled with blanks. 10 Country of origin M 3 94-96 3-digit numeric code (see code directory) 11 VAT preference. K 1 97 Import blanks 12 Advance payment % K 4 98-101 2 decimal points. Only entered if proportion is less

than 100%. Usually: Import zeros. Agree entry with Porsche

13 Trading preference K 1 102 (see code directory) 14 Empty K 25 103-

128 Spare digits filled with blanks.

1) Delivery quantity x unit price without packaging and shipping costs. The latter are to be provided per invoice in record type 813. Surcharges and discounts are price components and should be included in the unit price.

M = mandatory K = optional (at Porsche)

84

Record type 819 (Invoice data trailer record, mandatory record), 1 x per transmission (EDI cycle)

Item Field name VDA

K M

Byte lgth

from to Content in acc. with VDA 4906 incl. Porsche-specific extension tag if applicable

01 Record type M 3 1-3 Constant "819" must be present. 02 Version number M 2 4-5 Entry = 03 03 Counter record

811 M 7 6-12 Count of transmitted record 811, entry right-aligned

with leading zeros. 04 Counter record

812 M 7 13-19 Count of transmitted record 812, right-justified entry

and leading zeros. 05 Counter record

813 M 7 20-26 Count of transmitted record 813, right-justified entry

and leading zeros. 06 Counter record

814 M 7 27-33 Count of transmitted record 814, right-justified entry

and leading zeros. 07 Counter record

819 M 7 34-40 Count of transmitted record 819, right-justified entry

and leading zeros. 08 Invoice total final

value M 13 41-53 Sum of all invoice final values from transmitted

record type 812. Right-justified entry with leading zeros and 1 decimal point.

09 Sum of fees 1 M 13 54-66 Sum of all invoice fees from transmitted record type 812. Right-justified entry with leading zeros and 1 decimal point.

10 Sum of VAT – amount 1

M 13 67-79 Sum of all VAT amounts from the transmitted record type 812, calculated using the first VAT rate. Right-justified entry with 2 decimal points, and leading zeros.

11 VAT rate 1 M 3 80-82 First VAT rate. Right-justified entry with leading zeros and 1 decimal point.

12 Sum of fees 2 M 13 83-95 Sum of all invoice fees from the transmitted record type 812, calculated using the second VAT rate. Right-justified entry with 2 decimal points, and leading zeros.

13 Sum of VAT – amount 2

M 13 96-108 Sum of all VAT amounts from the transmitted record type 812, calculated using the second VAT rate. Right-justified entry with 2 decimal points, and leading zeros.

14 VAT rate 2 M 3 109-111 Second VAT rate. Right-justified entry with leading zeros and 1 decimal point.

15 Empty K 17 112-128 Spare digits filled with blanks. M = mandatory K = optional (at Porsche)

85

Example file: 81102PORSCHEL 31116 1064110642080122 DE147799625 DE115235681 812024679258908012200000038614630000024184951978 190 0000020323488000000000000000000000000000000 8130117237537080122DT01 03 751887 00000000000000000000000000 8140303H.100.011.CT 03H 100 011 CT S 5 27100000000960000200000211703000000020323488 004 0000 819030000001000000100000010000001000000100000241849510000020323488000000386146319000000000000000000000000000000 If you require an example file with special content, please get in touch with your Porsche EDI contact.

86

10.7 VDA 4921 waybill, Zuffenhausen

Record type 751: Record header of waybill data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Data recipient number STRINGE 9 04 Data sender number STRINGE 9 05 Transmission number old NSTRINGE 5 06 Transmission number new NSTRINGE 5 07 Transmission date NSTRINGE 6 "YYMMDD" 08 Empty STRINGE 89 Record type 752: Transport vehicle identification data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Means of transport code NSTRINGE 2 04 Means of transport number STRINGE 25 05 Bordereau number STRINGE 17 06 Bordereau date NSTRINGE 6 "YYMMDD" 07 Bordereau correction code NSTRINGE 1 08 Special trip number STRINGE 8 09 Shipping volume NSTRINGE 6 10 Loading metres NSTRINGE 12 11 Empty STRINGE 46 Record type 753: Transport information data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Means of transport stopover

date NSTRINGE 6

04 Means of transport stopover time

NSTRINGE 4

05 Means of transport stopover location

STRINGE 35

06 Scheduled arrival date NSTRINGE 6 07 Scheduled arrival time NSTRINGE 4 08 Information correction code NSTRINGE 1 09 Text STRINGE 67

87

Record type 754: Shipping record supplement Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Supplier number STRINGE 9 04 Shipment load reference

number NSTRINGE 8

05 Shipping order number STRINGE 17 06 Shipping log date NSTRINGE 6 07 Shipment scope code STRINGE 1 08 Gross shipment weight NSTRINGE 7 09 Net shipment weight NSTRINGE 7 10 No. of packages NSTRINGE 4 11 Unloading point STRINGE 5 12 Supplier plant STRINGE 3 13 Customer plant STRINGE 3 14 Empty STRINGE 53 Record type 755: Delivery note directory Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Delivery note number 1 STRINGE 8 04 Delivery note number 2 STRINGE 8 05 Delivery note number 3 STRINGE 8 06 Delivery note number 4 STRINGE 8 07 Delivery note number 5 STRINGE 8 08 Delivery note number 6 STRINGE 8 09 Delivery note number 7 STRINGE 8 10 Delivery note number 8 STRINGE 8 11 Delivery note number 9 STRINGE 8 12 Delivery note number 10 STRINGE 8 13 Delivery note number 11 STRINGE 8 14 Delivery note number 12 STRINGE 8 15 Delivery note number 13 STRINGE 8 16 Delivery note number 14 STRINGE 8 17 Delivery note number 15 STRINGE 8 18 Empty STRINGE 3 Record type 759: Trailer record Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Counter record 751 NSTRINGE 7 04 Counter record 752 NSTRINGE 7 05 Counter record 753 NSTRINGE 7 06 Counter record 754 NSTRINGE 7 07 Counter record 755 NSTRINGE 7 08 Counter record 759 NSTRINGE 7 09 Empty STRINGE 81

88

Example file: 75101200002 256280 1300313004080117 7520112H-VV1871 KS-S4536 B080117A 080116 000015000000000004 753010000000000 0801171300 7540122158 F080117A14982155 080116 000215500014390004BLECH W5 75501L080117A 7540114482 F080117A14982164 080116 000128400003980010BLECH W5 75501L080117A 7540117436 F080117A14982164 080116 000128400003980010BLECH W5 75501L080117A 75901000000100000010000001000000200000020000001 If you require an example file with special content, please get in touch with your Porsche EDI contact.

89

10.8 Freight invoice, Zuffenhausen

Item Data element M/O Length Comment 01 Transmission date M 8 Date of transmission; added to file by

sender. Format: DDMMYYYY

02 Transmission time M 6 Time of transmission; added to file by sender. Format: hhmmss

03 Freight forwarder Name M 30 Name of forwarder Number M 9 unique forwarder number 04 Invoice number M 8 Forwarder's invoice number 05 Invoice date M 8 DDMMYYYY 06 PO number K 8 Porsche PO number; for information only 07 Order no. K 6 Porsche order number; for information

only 08 Total/net M 13 Net invoice total 09 Total/VAT M 13 Value added tax 10 Total/gross M 13 Net total + VAT total 11 Account number K 6 Freight invoice general ledger account 12 Cost centre K 6 Freight invoice cost centre 13 Currency K 3 Currency of all invoiced amounts

Permitted values: Empty (= EUR) EUR: euros

14 Version K 2 Interface version: Empty = Version 2

15 VAT/deductible K 13 VAT exempt amount 16 Filler K 26 Reserves 17 Item number M 3 Invoice items 18 Record type M 1 Record type of the following item data in

the other fields. ‘D’ = direct invoicing (sender =

supplier, recipient = shipping recipient) ‘V’ = Advance (sender = supplier,

recipient = UP) ‘H’ = main cycle (sender = UP,

recipient = shipping recipient/UP) ‘N’ = run-on (sender = shipping

recipient/UP = shipping recipient/UP) ‘T’ = pallet exchange cost ‘F’ = follow-on record, i.e. there is a

main record in this transmission with the same forwarder no, freight invoice no and item no.

19 Invoice type M 1 Type of service in invoice: 'E' = goods in 'V' = goods out/full containers 'L' = goods out/empty containers

20 Sender's address Country K 3 Vehicle number plate country code; empty

= Germany

90

Postcode M 7 Postcode Location M 30 Location name Sub-location K 30 Loading plant K 2 Only for supplier = Porsche AG: Loading

plant at goods issue Loading point K 2 Only for supplier = Porsche AG: Loading

point at goods issue 21 Recipient's address Country K 3 Vehicle number plate country code; empty

= Germany Postcode M 7 Postcode Location M 30 Location name Delivery plant K 2 Delivery plant identifier (Porsche goods

receipt only) Unloading point K 2 Unloading point identifier (Porsche goods

receipt only) 22 Distance [km] M 4 Distance between sender and recipient

addresses 23 Date of shipment M 8 DDMMYYYY 24 Special trip K 1 Identifies whether it is a special trip ('S' =

special trip) or not 25 Weight of delivery in kg M 7 26 chargeable weight K 7 27 Loading metres [m] K 4 28 Volume [m³] K 6 29 Tariff K 10 e.g.‘5-ton rate’ 30 Hazardous goods class K 15 31 Net freight M 13 Net freight cost of invoice item; for pallet

exchange records (record type = T), the exchange cost is entered here

32 Margin in % K 5 margin% and margin either both empty or both full

33 Margin K 13 margin% and margin [EUR] either both empty or both full

34 In-house freight K 13 35 Freight terms M 2 VDA freight terms codes

01 = paid 02 = free to specified location 03 = free in-house 04 = free to German border 05 = free to recipient/forwarder 99 = Special freight terms (individ. agreement)

36 Comments 3 lines for comments on invoice item line 1 K 40 e.g. number of packages and text line 2 K 40 line 3 K 40 37 Filler K 50 38 Waybill numbers up to 10 waybill numbers (VDA field 8 =

shipment load reference number) together with supplier number and name; Supplier number + waybill number is reference on waybill

Supplier name 1 M 20 Supplier name on first waybill

91

Supplier no. 1 M 8 Supplier number on first waybill waybill no. 1 M 8 Number on first waybill Supplier name 2 K 20 Supplier no. 2 K 8 waybill no. 2 K 8 Supplier name 3 K 20 Supplier no. 3 K 8 waybill no. 3 K 8 Supplier name 4 K 20 Supplier no. 4 K 8 waybill no. 4 K 8 Supplier name 5 K 20 Supplier no. 5 K 8 waybill no. 5 K 8 Supplier name 6 K 20 Supplier no. 6 K 8 waybill no. 6 K 8 Supplier name 7 K 20 Supplier no. 7 K 8 waybill no. 7 K 8 Supplier name 8 K 20 Supplier no. 8 K 8 waybill no. 8 K 8 Supplier name 9 K 20 Supplier no. 9 K 8 waybill no. 9 K 8 Supplier name 10 K 20 Supplier no. 10 K 8 waybill no. 10 K 8 39 End of record M 1 always marked with '*' (ASCII 042) 40 CR/LF M 2 Carriage Return/ LineFeed

(ASCII 013/ 010) If you require an example file, please get in touch with your Porsche EDI contact.

92

10.9 Delivery note Sachsenheim/Ludwigsburg VDA 4913

Record type 711: Header record of delivery note/transport data Item Data element Field

type Length Default/Remark

01 Record type NSTRINGE 3 02 Version NSTRINGE 2 03 Customer number NSTRINGE 9 04 Supplier number NSTRINGE 9 The supplier number must include the

dispatching plant as an index (6-digits). 05 Transmission number old NSTRINGE 5 06 Transmission number new NSTRINGE 5 07 Transmission date NSTRINGE 6 08 Sub-supplier number STRINGE 9 09 Carrier number STRINGE 9 10 Warehouse code STRINGE 1 11 Delivery identifier STRINGE 1 12 Empty STRINGE 65 13 Manufacturer identifier STRINGE 4 Record type 712: One-time data elements of transport record Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Shipment load reference

number NSTRINGE 8 All the delivery notes for an unloading

point and target goods receipt date must be combined under one shipment reference number. Shipment reference numbers may not be repeated within the same calendar year.

04 Supplier plant STRINGE 3 05 Carrier STRINGE 14 06 Carrier handover date NSTRINGE 6 "YYMMDD" 07 Carrier handover time NSTRINGE 4 "HHMM" 08 Gross shipment weight NSTRINGE 7 09 Net shipment weight NSTRINGE 7 10 Freight terms code STRINGE 2 11 Forwarder's EDI code STRINGE 1 12 No. of packages NSTRING 4 13 Customer transport partner

number STRINGE 14

14 Means of transport code NSTRING 2 15 Means of transport number STRINGE 25 16 Tariff zone code STRINGE 1 17 Tariff zone STRINGE 8 18 Target date of arrival NSTRINGE 6 "YYMMDD", 19 Target time of arrival NSTRINGE 4 "HHMM", 20 Loading metres NSTRINGE 3 21 HGV type code NSTRINGE 1 22 Empty STRINGE 3

93

Record type 713: One-time data elements of delivery note Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Delivery note number NSTRINGE 8 The last 6 digits of the delivery note no.

are processed and then returned from Porsche in the delivery instruction. Delivery note numbers may not be repeated within the same calendar year.

04 Shipping date NSTRINGE 6 "YYMMDD", " " 05 Unloading point STRINGE 5 06 Shipment type STRINGE 2 07 Customer identifier (delivery

instruction) STRINGE 4

08 Final order no. STRINGE 12 09 Process code NSTRINGE 2 10 Empty STRINGE 4 11 Customer plant STRINGE 3 12 Consignment NSTRINGE 8 13 Goods recipient number STRINGE 9 14 Empty STRINGE 1 15 Customer storage location STRINGE 7 Transmission of this is only required for

processing under the new logistics concept and in sequence.

16 Supplier number STRINGE 9 17 Point of consumption STRINGE 14 Transmission of this is only required for

processing under the new logistics concept and in sequence.

18 Call-off number STRINGE 4 19 Customer tag STRINGE 6 20 Customer documentation

number STRINGE 14

21 Empty STRINGE 5 Record type 714: Delivery note item data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer part number STRINGE 22 04 Supplier part number STRINGE 22 05 Country of origin STRINGE 3 06 Delivery quantity NSTRINGE 13 07 Unit of quantity STRINGE 2 08 Delivery quantity NSTRINGE 13 09 Unit of quantity STRINGE 2 10 VAT rate NSTRINGE 3 11 Empty STRINGE 1 12 Delivery note item number NSTRINGE 3 13 Production number code STRINGE 1 14 Batch number STRINGE 15 15 Usage code STRINGE 1

94

16 Hazardous materials code STRINGE 8 17 Preferential status STRINGE 1 18 Dutiable goods STRINGE 1 19 Empty STRINGE 1 20 Inventory status STRINGE 1 21 Changed version code STRINGE 2 22 Original delivery note number STRINGE 8 Record type 715: Packaging data (Porsche mandatory record) Packaging data must be transmitted with the information from supplier-specific packaging instructions. Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer packaging number STRINGE 22 04 Supplier packaging number STRINGE 22 05 No. of packaging units NSTRINGE 13 06 Delivery note item number NSTRINGE 3 07 Capacity NSTRINGE 13 08 Package number from STRINGE 9 09 Package number to STRINGE 9 10 Packaging dimensions NSTRINGE 12 11 Stacking parameter STRINGE 1 12 Stock call-off number STRINGE 15 13 Label identifier STRINGE 1 14 Packaging identifier STRINGE 1 15 Ownership identifier STRINGE 1 16 Empty STRINGE 1 Record type 716: Packaging data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Text 1 STRINGE 40 04 Text 2 STRINGE 40 05 Text 3 STRINGE 40 06 Empty STRINGE 3 Record type 717: Individual package record for item Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Individual package number STRINGE 15 04 Delivery quantity NSTRINGE 13 05 Unit of quantity STRINGE 2 06 Delivery quantity NSTRINGE 13 07 Unit of quantity STRINGE 2 08 Batch number STRINGE 15 09 Empty STRINGE 63

95

Record type 718: Production number data (Porsche mandatory record for sequence processing) Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Delivery note number NSTRINGE 8 04 Production number 1 STRINGE 10 05 Production number 2 STRINGE 10 06 Production number 3 STRINGE 10 07 Production number 4 STRINGE 10 08 Production number 5 STRINGE 10 09 Production number 6 STRINGE 10 10 Production number 7 STRINGE 10 11 Production number 8 STRINGE 10 12 Production number 9 STRINGE 10 13 Production number 10 STRINGE 10 14 Production number 11 STRINGE 10 15 Empty STRINGE 5 Record type 719: Trailer record of delivery note/transport data Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Counter record 711 NSTRINGE 7 04 Counter record 712 NSTRINGE 7 05 Counter record 713 NSTRINGE 7 06 Counter record 714 NSTRINGE 7 07 Counter record 715 NSTRINGE 7 08 Counter record 716 NSTRINGE 7 09 Counter record 718 NSTRINGE 7 10 Counter record 719 NSTRINGE 7 11 Counter record 717 NSTRINGE 7 12 Empty STRINGE 60

96

10.10 EDIFACT IFTMIN waybill, Ludwigsburg

UNB Segment Data element M/O Length Comment 0017 Creation date 0019 Creation time BGM Segment Data element M/O Length Comment 1001 Constant = 730 1004 Transport ref. number RFF#1 Segment Data element M/O Length Comment 1153 Constant = ZZZ 1154 Idoc number TOD Segment Data element M/O Length Comment 4055 Constant = 6 4053 Constant = 2 1131 Shipping conditions 4052#1 Shipping conditions reference NAD#1 Segment Data element M/O Length Comment 3035 Constant = CA 3035 Constant = PW 3039 Transport planning point 1131 Constant = ZZZ DTM#6 Segment Data element M/O Length Comment 2005 Constant = 10 2380 Shipping date 2379 Constant = 102 TOD Segment Data element M/O Length Comment 1131 Incoterms 4052#2 Incoterms 4052#1 Inco_ref. CNT Segment Data element M/O Length Comment 6069 Constant = 11 6066 No. of packages

97

PIA Segment Data element M/O Length Comment 4347 Constant = 1 7140#1 Material number 7143#1 Constant = NB 1131#1 Batch 7143#2 Constant = CG 1131#2 TMD#1 Segment Data element M/O Length Comment 8334 Route schedule FTX#5 Segment Data element M/O Length Comment 4451 Constant = PRD 4440#1 Material ref. 4451 Constant = TRA 4440#1 4440#2 Carrier grp_ref. GID Segment Data element M/O Length Comment 7224#1 Delivery quantity MOA#7 Segment Data element M/O Length Comment 5025 Constant = 123 5004 Carriage value 6345 Value of carriage limit LOC#10 Segment Data element M/O Length Comment 3227 Constant = 27 3225 Country of origin 3224 Country of origin_ref. NAD#2 Segment Data element M/O Length Comment 3035 Constant = CN 3039 Recipient of goods 1131 Constant = 160 3124#1 3036#1 Name 3042#1 Street 3164 Urban 3251 Postcode 3207 Country 3035 Constant = CZ 3039 Sender 1131 Constant = 160

98

3124#1 3036#1 Name 3042#1 Street 3164 Urban 3251 Postcode 3207 Country MEA#1 Segment Data element M/O Length Comment 6311 Constant = WT 6411 Unit of weight 6314 Gross weight 6311 Constant = ABJ 6411 Unit of volume 6314 Volume PCI Segment Data element M/O Length Comment 4233 Constant = 24 7102#1 package no. 7102#2 Shipping materials 7102#3 Shipping materials_ref GOR#2 Segment Data element M/O Length Comment 8323 Constant = 1 LOC#12 Segment Data element M/O Length Comment 3227 Constant = 9 3225 Loading point RFF#8 Segment Data element M/O Length Comment 1153 Constant = CU 1154 DIM#1 Segment Data element M/O Length Comment 6145 Constant = 2 6168 Length 6140 Width 6008 Height 6411 Unit of dimension If you need an example file of an EDIFACT IFTMIN waybill, please get in touch with your Porsche EDI contact.

99

10.11 EDIFACT IFCSUM waybill, Ludwigsburg

UNB Segment Data element M/O Length Comment 0017 Creation date 0019 Creation time BGM Segment Data element M/O Length Comment 1001 Constant = 730 1004 Transport ref. number TDT#1 Segment Data element M/O Length Comment 8051 Constant = 111 NAD#1 Segment Data element M/O Length Comment 3035 Constant = CA 3039 Freight forwarder 1131 Constant = ZZZ DTM#4 Segment Data element M/O Length Comment 2005 Constant = 10 2380 Shipping date 2379 Constant = 102 CNI Segment Data element M/O Length Comment 1490 Transport ref. number RFF#2 Segment Data element M/O Length Comment 1153 Constant = CU 1154 Transport ref. number NAD#3 Segment Data element M/O Length Comment 3035 Constant = CN 3039 Recipient of goods 1131 Constant = 160 3124#1 Freight forwarder 3036#1 Name 3036#2 Name2 3042#1 Street 3164 Urban 3251 Postcode 3207 Country

100

GID Segment Data element M/O Length Comment 1496 Package no. 7224#1 Constant = 1 MEA#3 Segment Data element M/O Length Comment 6311 Constant = WT 6411 Constant = 166 6314 Weight PCI Segment Data element M/O Length Comment 4233 Constant = 24 7102#1 Package no. If you need an example file of an EDIFACT IFCSUM waybill, please get in touch with your Porsche EDI contact.

101

10.12 VDA 4905 delivery instruction, Leipzig

Record type 511: Delivery instruction header record Item Data element M/O Length Comment 01 Record type M 3 511 02 Version M 2 02 03 Customer number M 9 left-aligned with no leading zeros

If empty or "KEIN_EBVWERT", then "Porsche 04 Supplier number M 9 left-aligned with no leading zeros 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 08 CRQ zero date K 6 09 Empty M 83 10 CRLF M 2 Record type 512: One-time data of delivery instruction Item Data element M/O Length Comment 01 Record type M 3 512 02 Version M 2 01 03 Customer plant M 3 the first 3 digits 04 Delivery instruction number

new M 9

05 Delivery instruction date new M 6 06 Delivery instruction number old M 9 07 Delivery instruction date old M 6 08 Orderer's part number M 22 Example: 111.111.111.11 ABC 09 Supplier part number K 22 10 Order no. K 12 11 Unloading point M 5 12 Orderer's tag M 4 13 Unit of quantity M 2 ISO calculation in VDA unit of measurement 14 Delivery interval M 1 L 15 Production release K 1 1 digit 16 Material release K 1 1 digit 17 Reg. no. change code M 1 constant S

if P10.KWERK = '040','050' or '090', then 'E' 18 Account assignment K 7 19 Warehouse K 7 20 Empty M 5 21 CRLF M 2

102

Record type 513: Delimitation and call-off data of delivery instruction Item Data element M/O Length Comment 01 Record type M 3 513 02 Version M 2 01 03 Creation date of last receipt M 6 04 Delivery note number

Last receipt M 8 8 digits right-aligned

05 Delivery note date Last receipt

M 6 including the 3rd digit of 6 characters

06 Last receipt quantity M 12 07 Cumulative received quantity M 10 08 Call-off date M 6 09 Call-off quantity M 9 10 Empty M 6 11 CRLF M 2 Record type 514: Additional call-off data on delivery instruction Item Data element M/O Length Comment 01 Record type M 3 514 02 Version M 2 01 03 Call-off date M 6 04 Call-off quantity M 9 05 Empty M 3 06 CRLF M 2 Record type 515: Additional call-off information on delivery instruction Item Data element M/O Length Comment 01 Record type M 3 515 02 Version M 2 02 03 Production release start date K 6 04 Production release end date K 6 05 Production release

cumulative requirement K 10

06 Material release start date K 6 07 Material release end date K 6 08 Material release

cumulative requirement K 10

09 Part number – addition K 22 10 Intermediate supplier K 9 11 Date of planning horizon K 6 12 Point of consumption K 14 13 Vehicle zero position K 10 14 Empty M 18 15 CRLF M 2

103

Record type 517: Packaging data of delivery instruction Item Data element M/O Length Comment 01 Record type M 3 517, issue only if P14.PCKNR

not identical blank 02 Version M 2 01 03 Customer part number M 22 04 Supplier part number K 22 05 Capacity M 7 06 Empty M 72 07 CRLF M 2 Record type 518: Tex data of delivery instruction Item Data element M/O Length Comment 01 Record type M 3 518 02 Version M 2 01 03 Delivery instruction text 1 M 40 left-aligned 40 digits upper case 04 Delivery instruction text 2 K 40 left-aligned 40 digits upper case 05 Delivery instruction text 3 K 40 left-aligned 40 digits upper case 06 Empty M 3 07 CRLF M 2 Record type 519: Delivery instruction trailer record Item Data element M/O Length Comment 01 Record type M 3 519 02 Version M 2 02 03 Counter 511 7 M 04 Counter 512 7 M 05 Counter 513 7 M 06 Counter 514 7 M 07 Counter 517 7 M 08 Counter 518 7 M 09 Counter 519 7 M 10 Counter 515 7 M 11 Empty 67 M 12 CRLF 2 M

104

Example file: 51102PORSCHE 46308 0000000001071120061231 51201L013 0711202 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 51201L013 0711202 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 51201L014 0711203 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 51201L015 0711204 0711207L5.601.025.E 9A1 SL 1776 730337 PT01 STL11S 0001 51301 000000000000000000000000000000000000071201000000500555555 080005000000500000000 5150200000000000000000000000000000000000000000000 000000 0000041233 5190200000010000004000000400000000000000000000000000010000004 If you require an example file with special content, please get in touch with your Porsche EDI contact.

105

10.13 VDA 4915 DCO, Leipzig

Record type 551: Record header of DCO data Item Data element M/O Length Comment 01 Record type M 3 551 02 Version M 2 02 03 Customer number M 9 Customer number from EDI table 04 Supplier number M 9 5-digit supplier number 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 YYMMDD 08 CRQ zero position date M 6 YYMMDD 09 Empty M 83 Record type 552: One-time data elements of DCO Item Data element M/O Length Comment 01 Record type M 3 552 02 Version M 2 02 03 Customer plant M 3 Customer plant where the goods are to be

delivered. 04 DCO number new M 9 serial number of Porsche DCO, left-aligned 05 DCO date M 6 YYMMDD 06 Customer part number M 22 Example: 111.111.111.11 ABC 07 Supplier part number M 22 not used 08 Unloading point M 5 from delivery schedule 09 Customer storage location M 7 Route information 10 Critical stock code K 1 not used 11 Usage code M 1 attachment to item 2 12 DCO horizon K 6 13 Date code M 1 attachment to item 5 14 Final order no. K 12 Delivery schedule number 15 Cumulative quantity discrepancy K 10 not used 16 Point of consumption M 14 Point of consumption, blank if

applicable 17 Empty M 4

106

Record type 553: DCO delimitation data Item Data element M/O Length Comment 01 Record type M 3 553 02 Version M 2 01 03 Cumulative received quantity M 10 CRQ from 01.01 of current year 04 Date of arrival 1 M 6 YYMMDD 05 Delivery note number 1 M 8 ID no. that the supplier number assigns to

a delivery note, right-aligned with leading zeros.

06 Delivery note date 1 M 6 Shipping date YYMMDD 07 Delivery quantity 1 M 12 Quantity in delivery note, right-aligned

entry with leading zeros and 3 decimal points

08 Delivery status code 1 M 1 I = DCO process booked at goods receipt; P = not yet received for transit

09 Date of arrival 2 K 6 not used 10 Delivery note number 2 K 8 not used 11 Delivery note date 2 K 6 not used 12 Delivery quantity 2 K 12 not used 13 Delivery status code 2 K 1 not used 14 Date of arrival 3 K 6 not used 15 Delivery note number 3 K 8 not used 16 Delivery note date 3 K 6 not used 17 Delivery quantity 3 K 12 not used 18 Delivery status code 3 K 1 not used 19 Empty M 14

107

Record type 554: DCO data Item Data element M/O Length Comment 01 Record type M 3 554 02 Version M 2 02 03 Call-off date 1 M 6 Target goods receipt date YYMMDD 04 Call-off time 1 M 4 Target time of arrival HHMM 05 Call-off quantity 1 M 9 Requirements quantity, right-aligned entry

with leading zeros and no decimal points 06 Requirements status code 1 K 1 Blank or "B" 07 Call-off date 2 M 6 Target goods receipt date from detailed

DCO table 08 Call-off time 2 K 4 Target goods receipt time from detailed

DCO table 09 Call-off quantity 2 M 9 Target goods quantity from DCO table 10 Requirements status code 2 K 1 if order quantity procedure = "B" then "B",

otherwise space 11 Call-off date 3 M 6 Target goods receipt date from DCO table 12 Call-off time 3 K 4 Target goods receipt time from DCO table 13 Call-off quantity 3 M 9 Target goods quantity from DCO table 14 Requirements status code 3 K 1 if order quantity procedure = "B" then "B",

otherwise space 15 Call-off date 4 M 6 Target goods receipt date from DCO table 16 Call-off time 4 K 4 Target goods receipt time from DCO table 17 Call-off quantity 4 M 9 Target goods quantity from DCO table 18 Requirements status code 4 K 1 if order quantity procedure = "B" then "B",

otherwise space 19 Call-off date 5 M 6 Target goods receipt date from DCO table 20 Call-off time 5 K 4 Target goods receipt time from DCO table 21 Call-off quantity 5 M 9 Target goods quantity from DCO table 22 Requirements status code 5 K 1 if order quantity procedure = "B" then "B",

otherwise space 23 Call-off date 6 M 6 Target goods receipt date from DCO table 24 Call-off time 6 K 4 Target goods receipt time from DCO table 25 Call-off quantity 6 M 9 Target goods quantity from DCO table 26 Requirements status code 6 K 1 if order quantity procedure = "B" then "B",

otherwise space 27 Empty M Record type 555: Additional data for DCO Item Data element M/O Length Comment 01 Record type M 3 555 02 Version M 2 01 03 Intermediate supplier K 9 04 Supplementary part number K 22 not used 05 At zero position of cumulative

quantity K 10 not used

06 Empty M 82

108

Record type 556: Packaging data of DCO Item Data element M/O Length Comment 01 Record type M 3 556 02 Version M 2 01 03 Part number customer packaging M 22 Packaging identification number 04 Supplier part number M 22 not used 05 Target capacity M 7 Packaging capacity, right-aligned entry

with leading zeros and no decimal points 06 Empty M 72 Record type 557: Text data for DCO Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Text 1 not used 04 Text 2 not used 05 Text 3 not used 06 Empty not used Record type 559: Trailer record Item Data element M/O Length Comment 01 Record type M 3 559 02 Version M 2 02 03 Counter record 551 M 7 Count of record type 551 transmitted 04 Counter record 552 M 7 Count of record type 552 transmitted 05 Counter record 553 M 7 Count of record type 553 transmitted 06 Counter record 554 M 7 Count of record type 554 transmitted 07 Counter record 555 M 7 Count of record type 555 transmitted 08 Counter record 556 M 7 Count of record type 556 transmitted 09 Counter record 557 M 7 Count of record type 557 transmitted 10 Counter record 559 M 7 Count of record type 559 transmitted 11 Empty M 67 Example file 55102PORSCHE 47914 0000400005071210061231 55202L0100000000307111409D.300.037.M PT01 S071123 731893 0000000000 55301000000015207111211-12-00 000000018000I 000000000000 000000000000 554020711041200000000012 0711070000000000018 0711080000000000012 0711090000000000084 0711090000000000126 0711120000000000084 554020711130000000000078 0711140000000000084 0711150000000000084 0711160000000000042 0711160000000000036 0711190000000000084 554020711200000000000078 0711210000000000078 0711220000000000084 0711230000000000036 0711230000000000042 000000 000000000 55501 0000000002 55601C002 0000006 5590200000010000001000000100000030000001000000100000010000001 If you require an example file with special content, please get in touch with your Porsche EDI contact.

109

10.14 VDA 4916 JIT/JIS call-off, Leipzig

Record type 661: Record header of JIT/JIS call-off data Item Data element M/O Length Comment 01 Record type M 3 661 02 Version M 2 01 03 Customer number M 9 left-aligned with no leading zeros

If empty or "KEIN_EBVWERT", then "Porsche"

04 Supplier number M 9 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 08 Empty M 89 Record type 662: VIN data Item Data element M/O Length Comment 01 Record type M 3 662 02 Version M 2 01 03 Change code M 1 Z, R, L, N, D, T, blank 04 Production number M 10 05 production sequence number K 12 always filled out, including for forecasts,

Exceptions are NA and Cayenne 10 AT forecast

06 Customer plant M 3 07 Unloading point K 5 Not filled out 08 Point of consumption K 14 Not filled out 09 Production area code K 7 Original delivery note number, for ‘material

on site’ messages, (change code ‘R’ ) For all other change codes: Number range of production sequence number

10 Production area date K 6 YYMMDD, original schedule date that vehicle enters the line

11 Production area time K 4 Time of reporting point when vehicle enters the line

12 Date code K 1 this is filled out where there is installation time info, call-offs without 664 records and material on site messages

13 Call-off date K 6 Not filled out 14 Call-off time K 4 Not filled out 15 Special specification K 12 filled out with model year for VW 16 Type/design sample M 8 Product code 17 Chassis number K 19 18 No. of vehicles K 9 19 Empty M 2

110

record type 663: Text record Item Data element M/O Length Comment 01 Record type M 3 663 02 Version M 2 01 03 Number plate M 1 blank = text follows 04 Text 1 M 35 Z-orders 05 Text 2 K 35 Z-orders 06 Text 3 K 35 Z-orders 07 Empty M 17 Record type 664: Part number data Item Data element M/O Length Comment 01 Record type M 3 664 02 Version M 2 01 03 Customer part number M 22 Format:

XXX.XXX.XXX.XX XXX 04 Unit of quantity M 2 ISO calculation in VDA unit of measurement 05 Call-off quantity M 9 no decimal points,

delete leading blanks, quantity before decimal point, entry left-aligned with leading zeros.

06 Unloading point M 5 currently the delivery instruction has 2 unloading points: PT01, DT01 (PLG, Schnellecke)

07 Point of consumption M 14 APL/KPL/call-off group, left-aligned 08 Date code M 1 09 Call-off date M 6 Format: YYYYMMDD 10 Call-off time M 4 Format: HHMM 11 Design change status K 14 12 Empty M 46 Record type 669: Trailer record Item Data element M/O Length Comment 01 Record type M 3 669 02 Version M 2 01 03 Counter record 661 M 7 Number of records 04 Counter record 662 M 7 Number of records 05 Counter record 663 M 7 Number of records 06 Counter record 664 M 7 Number of records 07 Counter record 669 M 7 Number of records 08 Empty M 88

111

Example file: 66101PORSCHE 46308 0000200003080121 66201 3100101 1000101 L01 MP 0711010000 0000000000 F71CA 000000000 664014F0.907.275.B ST000000001ET01 XM4X72REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001ET01 XM4X72REIFEN K0801161200 664017L0.601.307.P ST000000001ET01 XM4X72REIFEN K0801161200 664014F0.907.275.B ST000000001ET01 XM4X74REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001ET01 XM4X74REIFEN K0801161200 664017L0.601.307.P ST000000001ET01 XM4X74REIFEN K0801161200 664014F0.907.275.B ST000000001 XM5X73REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001 XM5X73REIFEN K0801161200 664017L0.601.307.P ST000000001 XM5X73REIFEN K0801161200 664014F0.907.275.B ST000000001ET01 XM5X75REIFEN K0801161200 664017L5.601.025.B 9A1 ST000000001ET01 XM5X75REIFEN K0801161200 664017L0.601.307.P ST000000001ET01 XM5X75REIFEN K0801161200 66401L7L.000.100. ST000000001DT01 XX5X97E-REIFENK0801162100 6690100000010000001000000000000130000001 If you require an example file with special content, please get in touch with your Porsche EDI contact.

112

10.15 VDA 4913 VG 40 delivery advice/consignment note Leipzig

Record type 711: delivery note and transport data Item Data element M/O Length Comment 01 Record type M 3 711 02 Version M 2 03 03 Data recipient number M 9 Porsche ID (customer)

for consignment: Porsche ID (ESP) 04 Data sender number M 9 The supplier ID must be send with 6 digit

plant code. 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 08 Sub-supplier number K 9 not used 09 Carrier number K 9 not used 10 Warehouse code K 1 not used 11 Delivery identifier M 1 Blank=production and consignment,

N=rework 12 Empty M 69 Record type 712: Transport data Item Data element M/O Length Comment 01 Record type M 3 712 02 Version M 2 03 03 Shipment reference number M 8 Can be the delivery note number if the

delivery note is also the waybill; may not be repeated within the same 12 months

04 Supplier plant K 3 not used 05 Carrier M 14 06 Carrier handover date M 6 07 Carrier handover time M 4 08 Gross shipment weight M 7 09 Net shipment weight M 7 10 Freight terms code M 2 11 Forwarder's EDI code K 1 not used 12 No. of packages M 4 13 Transport partner number M 14 14 Means of transport code M 2 Allowed for PLG: 01, 02 (bordereau with

VDA 4921), 08, 09 15 Means of transport number M 25 not used 16 code (postcode=1, 2=HGV reg. no.)

at item 17 K 1 not used

17 Content as per item 16 K 8 not used 18 Target date of arrival M 6 is used; YYMMDD from DCO 19 Target time of arrival M 4 is used; HHMM from DCO 20 Loading metres K 3 not used 21 HGV type code K 1 not used 22 Empty M 3

113

Record type 713: Delivery note header data Item Data element M/O Length Comment 01 Record type M 3 713 02 Version M 2 03 03 Delivery note number M 8 Delivery note number of the supplier's

delivery to Porsche (customer); delivery note numbers may not be repeated within the same 12 months,

04 Shipping date M 6 Delivery note date 05 Unloading point M 5 Acc. to VDA4905 call-off, record type

512/11 or VDA 4916 record type 662/07 or 664/06

06 Shipment type M 2 07 Customer identifier (delivery

instruction) K 4 not used

08 Order no. M 12 Acc. to VDA4905 call-off, record type 512/10

09 Process code M 2 Only for consignment, in which case "40", otherwise blank

10 Empty M 4 11 Customer plant M 3 For PLG=L01 (first 3 digits of unloading

point) 12 Consignment K 8 not used 13 Goods recipient number M 9 Only for consignment, otherwise blank 14 Empty M 1 not used 15 Customer storage location M 7 Porsche route identifier 16 Supplier number M 9 Only if the VDA sender = ESP, in which

case enter the supplier number 17 Point of consumption M 14 Only for JIS: Acc. to VDA 4916 record

type 664/07 for consignment: blank

18 Call-off number M 4 Call-off number of latest call-off 19 Customer identifier (for individual

orders) K 6 not used

20 Document no. Customer K 14 Initial samples (drawing no. or test report number)

21 Empty M 5

114

Record type 714: Delivery note item Item Data element M/O Length Comment 01 Record type M 3 714 02 Version M 2 03 03 Customer part number M 22 =Supplier item number (without Porsche

editing for printing) e.g.: 111.111.111.AB DEF

04 Supplier part number M 22 not used 05 Country of origin M 3 06 Delivery quantity 1 M 13 07 Unit of quantity 1 M 2 08 Delivery quantity 2 K 13 not used 09 Unit of quantity 2 K 2 not used 10 VAT rate K 3 not used 11 Empty M 1 not used 12 Delivery note item number M 3 External item number 13 Call-off code M 1 14 Batch number K 15 MJJMMTTCxxxxxxx

1. M = MHD in format JJMMTT 2. C = Charge The chronology is 1. MHD, 2. Charge. Does a material not have any MHD the Charge must be set in front beginning with a C. i.e.Cxxxxxxxxxxxxxx Does a material only have a MHD and no Charge only send i.e. M140531

15 Usage code M 1 Blank, M, S 16 Hazardous materials code K 8 not used 17 Preferential status M 1 18 Dutiable goods M 1 not used 19 Empty M 1 not used 20 Inventory status M 1 not used 21 Changed version code M 2 not used 22 Original delivery note number K 8 not used Record type 715: Packaging data Item Data element M/O Length Comment 01 Record type M 3 715 02 Version M 2 03 03 Customer packaging number M 22 Only PLG.- specially agreed packaging.

You can pickup the packaging code out of the VDA 4915 message in record type 556/03

04 Supplier packaging number M 22 not used 05 No. of packaging units M 13 06 Delivery note item number M 3 07 Capacity M 13 for record type 715/13 = M -> zero

for record type 715/13 = G -> zero for record type 715/13 = S -> case capacity

08 Package number from M 9 May not be repeated within the same 12 months.

115

09 Package number to M 9 May not be repeated within the same 12 months.

10 Packaging dimensions K 12 not used 11 Stacking parameter K 1 not used 12 Stock call-off number K 15 not used 13 Label identifier M 1 M, S, G 14 Packaging identifier K 1 not used 15 Ownership identifier K 1 not used 16 Empty M 1 For entry 1: Cases of the most important

material For entry 2: Packaging materials For entry 3: Cases on containers

Record type 716: Text on delivery note item – not used Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Text 1 K 40 not used (if used then text, no figures) 04 Text 2 K 40 not used 05 Text 3 K 40 not used 06 Empty M 3 not used Record type 717: Package record for item Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Individual package number M 15 not used 04 Delivery quantity 1 K 13 not used 05 Unit of quantity 1 K 2 not used 06 Delivery quantity 2 K 13 not used 07 Unit of quantity 2 M 2 not used 08 Batch number K 15 not used 09 Empty M 63 not used Record type 718: Production numbers data Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Delivery note number M 8 not used 04 Production number 1 M 10 not used 05 Production number 2 K 10 not used 06 Production number 3 K 10 not used 07 Production number 4 K 10 not used 08 Production number 5 K 10 not used 09 Production number 6 K 10 not used 10 Production number 7 K 10 not used 11 Production number 8 K 10 not used 12 Production number 9 K 10 not used 13 Production number 10 K 10 not used 14 Production number 11 K 10 not used 15 Empty M 5 not used

116

Record type 719: Trailer record of delivery note/transport data Item Data element M/O Length Comment 01 Record type M 3 719 02 Version M 2 02 03 Counter record 711 M 7 04 Counter record 712 M 7 05 Counter record 713 M 7 06 Counter record 714 M 7 07 Counter record 715 M 7 08 Counter record 716 M 7 09 Counter record 717 M 7 10 Counter record 718 M 7 11 Counter record 719 M 7 12 Empty M 60

117

10.16 VDA 4913 VG 40 cumulative daily delivery note, Leipzig

Record type 711: delivery note and transport data Item Data element M/O Length Comment 01 Record type M 3 711 02 Version M 2 03 03 Data recipient number M 9 Porsche ID (customer) 04 Data sender number M 9 Supplier no./forwarder no. 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 08 Sub-supplier number K 9 09 Carrier number K 9 not used 10 Warehouse code K 1 not used 11 Delivery identifier M 1 Blank=production and consignment,

N=rework 12 Empty M 69 Record type 712: Transport data Item Data element M/O Length Comment 01 Record type M 3 712 02 Version M 2 03 03 Shipment reference number M 8 04 Supplier plant K 3 not used 05 Carrier M 14 06 Carrier handover date M 6 07 Carrier handover time M 4 08 Gross shipment weight M 7 09 Net shipment weight K 7 not used 10 Freight terms code K 2 not used 11 Forwarder's EDI code K 1 not used 12 No. of packages K 4 not used 13 Transport partner number K 14 not used 14 Means of transport code M 2 Allowed for PLG: 01, 08, 09 15 Means of transport number M 25 not used 16 code (postcode=1, 2=HGV reg. no.)

at item 17 K 1 not used

17 Content as per item 16 K 8 not used 18 Target date of arrival K 6 not used 19 Target time of arrival K 4 not used 20 Loading metres K 3 not used 21 HGV type code K 1 not used 22 Empty M 3

118

Record type 713: Delivery note header data Item Data element M/O Length Comment 01 Record type M 3 713 02 Version M 2 03 03 Delivery note number M 8 Delivery note no. of supplier delivery to

Porsche (customer) 04 Shipping date M 6 Delivery note date 05 Unloading point M 5 Acc. to VDA 4916 call-off, record type

662/07 or 664/06 06 Shipment type M 2 07 Customer identifier (delivery

instruction) K 4 not used

08 Order no. M 12 Acc. to VDA4905 call-off, record type 512/10

09 Process code M 2 Blank – not used 10 Empty M 4 11 Customer plant M 3 For PLG=L01 (first 3 digits of unloading

point) 12 Consignment K 8 not used 13 Goods recipient number K 9 not used 14 Empty M 1 not used 15 Customer storage location K 7 not used 16 Supplier number M 9 17 Point of consumption M 14 Acc. to VDA 4916 record type 664/07 18 Call-off number K 4 not used 19 Customer identifier (for individual

orders) K 6 not used

20 Document no. Customer K 14 not used 21 Empty M 5 Record type 714: Delivery note item Item Data element M/O Length Comment 01 Record type M 3 714 02 Version M 2 03 03 Customer part number M 22 Customer part no. = Supplier part no.

(without Porsche editing for printing) 04 Supplier part number M 22 not used 05 Country of origin M 3 06 Delivery quantity 1 M 13 07 Unit of quantity 1 M 2 08 Delivery quantity 2 K 13 not used 09 Unit of quantity 2 K 2 not used 10 VAT rate K 3 not used 11 Empty M 1 12 Delivery note item number M 3 13 Call-off code K 1 not used 14 Batch number K 15 not used 15 Usage code M 1 16 Hazardous materials code K 8 not used 17 Preferential status M 1 18 Dutiable goods M 1 19 Empty M 1 20 Inventory status M 1

119

21 Changed version code M 2 22 Original delivery note number K 8 not used

120

Record type 715: Packaging data Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Customer packaging number M 22 not used 04 Supplier packaging number M 22 not used 05 No. of packaging units M 13 not used 06 Delivery note item number M 3 not used 07 Capacity M 13 not used 08 Package number from M 9 not used 09 Package number to M 9 not used 10 Packaging dimensions K 12 not used 11 Stacking parameter K 1 not used 12 Stock call-off number K 15 not used 13 Label identifier M 1 not used 14 Packaging identifier K 1 not used 15 Ownership identifier K 1 not used 16 Empty M 1 not used Record type 716: Text on delivery note item Item Data element M/O Length Comment 01 Record type M 3 716 02 Version M 2 02 03 Text 1 K 40 first sequence type and number

For bodies, prod. number 04 Text 2 K 40 last sequence type and number

For bodies, prod. number 05 Text 3 K 40 not used 06 Empty M 3 Record type 717: Package record for item Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Individual package number M 15 not used 04 Delivery quantity 1 K 13 not used 05 Unit of quantity 1 K 2 not used 06 Delivery quantity 2 K 13 not used 07 Unit of quantity 2 M 2 not used 08 Batch number K 15 not used 09 Empty M 63 not used

121

Record type 718: Production numbers data Item Data element M/O Length Comment 01 Record type M 3 718 02 Version M 2 02 03 Delivery note number M 8 04 Production number 1 M 10 05 Production number 2 K 10 06 Production number 3 K 10 07 Production number 4 K 10 08 Production number 5 K 10 09 Production number 6 K 10 10 Production number 7 K 10 11 Production number 8 K 10 12 Production number 9 K 10 13 Production number 10 K 10 14 Production number 11 K 10 15 Empty M 5 Record type 719: Trailer record of delivery note/transport data Item Data element M/O Length Comment 01 Record type M 3 719 02 Version M 2 02 03 Counter record 711 M 7 04 Counter record 712 M 7 05 Counter record 713 M 7 06 Counter record 714 M 7 07 Counter record 715 M 7 08 Counter record 716 M 7 09 Counter record 717 M 7 10 Counter record 718 M 7 11 Counter record 719 M 7 12 Empty M 60

122

10.17 VDA 4913 consignment note Leipzig, VG 30, 32, 33, 36

Record type 711: delivery note and transport data Item Data element M/O Length Comment 01 Record type M 3 711 02 Version M 2 03 03 Data recipient number M 9 Supplier no. 04 Data sender number M 9 Porsche ID (ESP) 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 08 Sub-supplier number K 9 09 Carrier number K 9 10 Warehouse code K 1 1 11 Delivery identifier M 1 12 Empty M 69 Record type 712: Transport data Item Data element M/O Length Comment 01 Record type M 3 712 02 Version M 2 03 03 Shipment reference number M 8 04 Supplier plant K 3 05 Carrier M 14 06 Carrier handover date M 6 07 Carrier handover time M 4 08 Gross shipment weight M 7 09 Net shipment weight K 7 10 Freight terms code K 2 11 Forwarder's EDI code K 1 12 No. of packages K 4 13 Transport partner number K 14 14 Means of transport code M 2 15 Means of transport number M 25 16 code (postcode=1, 2=HGV reg. no.)

at item 17 K 1

17 Content as per item 16 K 8 18 Target date of arrival K 6 19 Target time of arrival K 4 20 Loading metres K 3 21 HGV type code K 1 22 Empty M 3

123

Record type 713: Delivery note header data Item Data element M/O Length Comment 01 Record type M 3 713 02 Version M 2 03 03 Delivery note number M 8 VG 30, 32, 33: Delivery note no. of

supplier delivery VG 36: (CDDN1) Porsche (ESP) delivery note no. -> internal ERP CDDN delivery note no. against which the supplier can invoice

04 Shipping date M 6 VG 30, 32, 33: Report date VG 36: Delivery note data for item 3 (dispatch data)

05 Unloading point M 5 VG 36: current unloading point at Porsche (ESP) acc. to call-off

06 Shipment type M 2 07 Customer identifier (delivery

instruction) K 4

08 Order no. M 12 VG 36: Order number from delivery schedule

09 Process code M 2 VG 30: 30 VG 32: 32 VG 33: 33 VG 36: 36

10 Empty M 4 11 Customer plant M 3 VG 36: First 3 digits from unloading point 12 Consignment K 8 13 Goods recipient number K 9 VG 30, 36: Porsche ID (customer) 14 Empty M 1 15 Customer storage location K 7 16 Supplier number M 9 17 Point of consumption M 14 18 Call-off number K 4 19 Customer identifier (for individual

orders) K 6

20 Document no. Customer K 14 21 Empty M 5

124

Record type 714: Delivery note item Item Data element M/O Length Comment 01 Record type M 3 714 02 Version M 2 03 03 Customer part number M 22 Porsche editing for printing! 04 Supplier part number M 22 Customer part no. = Supplier part no.

Porsche editing for printing! 05 Country of origin M 3 06 Delivery quantity 1 M 13 07 Unit of quantity 1 M 2 08 Delivery quantity 2 K 13 not used 09 Unit of quantity 2 K 2 not used 10 VAT rate K 3 11 Empty M 1 12 Delivery note item number M 3 13 Call-off code K 1 not used 14 Batch number K 15 not used 15 Usage code M 1 16 Hazardous materials code K 8 17 Preferential status M 1 18 Dutiable goods M 1 19 Empty M 1 20 Inventory status M 1 21 Changed version code M 2 22 Original delivery note number K 8 VG 36: Original delivery note number for

consignments Record type 715: Packaging data Item Data element M/O Length Comment 01 Record type M 3 715 02 Version M 2 03 03 Customer packaging number M 22 04 Supplier packaging number M 22 Customer packaging = Supplier packaging 05 No. of packaging units M 13 06 Delivery note item number M 3 07 Capacity M 13 depending on label identifier (record type

715, item 13): G or blank = 0, M = total quantity in container, S = capacity of individual cases

08 Package number from M 9 VG 36: if ext. package no. available Supplier -

09 Package number to M 9 10 Packaging dimensions K 12 not used 11 Stacking parameter K 1 not used 12 Stock call-off number K 15 not used 13 Label identifier M 1 14 Packaging identifier K 1 not used 15 Ownership identifier K 1 not used 16 Empty M 1

125

Record type 716: Text on delivery note item Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Text 1 K 40 not used 04 Text 2 K 40 not used 05 Text 3 K 40 not used 06 Empty M 3 not used Record type 717: Package record for item Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Individual package number M 15 not used 04 Delivery quantity 1 K 13 not used 05 Unit of quantity 1 K 2 not used 06 Delivery quantity 2 K 13 not used 07 Unit of quantity 2 M 2 not used 08 Batch number K 15 not used 09 Empty M 63 not used Record type 718: Production numbers data Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Delivery note number M 8 not used 04 Production number 1 M 10 not used 05 Production number 2 K 10 not used 06 Production number 3 K 10 not used 07 Production number 4 K 10 not used 08 Production number 5 K 10 not used 09 Production number 6 K 10 not used 10 Production number 7 K 10 not used 11 Production number 8 K 10 not used 12 Production number 9 K 10 not used 13 Production number 10 K 10 not used 14 Production number 11 K 10 not used 15 Empty M 5 not used

126

Record type 719: Trailer record of delivery note/transport data Item Data element M/O Length Comment 01 Record type M 3 719 02 Version M 2 02 03 Counter record 711 M 7 04 Counter record 712 M 7 05 Counter record 713 M 7 06 Counter record 714 M 7 07 Counter record 715 M 7 08 Counter record 716 M 7 09 Counter record 717 M 7 10 Counter record 718 M 7 11 Counter record 719 M 7 12 Empty M 60

127

10.18 VDA 4913 consignment note Leipzig, VG 35

Record type 711: delivery note and transport data Item Data element M/O Length Comment 01 Record type M 3 711 02 Version M 2 03 03 Data recipient number M 9 Supplier no. 04 Data sender number M 9 Porsche ID (ESP) 05 Transmission number old M 5 06 Transmission number new M 5 07 Transmission date M 6 08 Sub-supplier number K 9 09 Carrier number K 9 10 Warehouse code K 1 1 11 Delivery identifier M 1 12 Empty M 69 Record type 712: Transport data Item Data element M/O Length Comment 01 Record type M 3 712 02 Version M 2 03 03 Shipment reference number M 8 04 Supplier plant K 3 For PLG=L01 05 Carrier M 14 06 Carrier handover date M 6 07 Carrier handover time M 4 08 Gross shipment weight M 7 09 Net shipment weight K 7 10 Freight terms code K 2 11 Forwarder's EDI code K 1 12 No. of packages K 4 13 Transport partner number K 14 14 Means of transport code M 2 15 Means of transport number M 25 16 code (postcode=1, 2=HGV reg. no.)

at item 17 K 1

17 Content as per item 16 K 8 18 Target date of arrival K 6 19 Target time of arrival K 4 20 Loading metres K 3 21 HGV type code K 1 22 Empty M 3

128

Record type 713: Delivery note header data Item Data element M/O Length Comment 01 Record type M 3 713 02 Version M 2 03 03 Delivery note number M 8 "00000000" 04 Shipping date M 6 Inventory date

Local time 05 Unloading point M 5 Acc. to call-off 06 Shipment type M 2 07 Customer identifier (delivery

instruction) K 4

08 Order no. M 12 Acc. to Goods receipt logged in consignment store = VDA 4905 call-off record type 512/10

09 Process code M 2 35 10 Empty M 4 11 Customer plant M 3 12 Consignment K 8 13 Goods recipient number K 9 Porsche ID (customer) 14 Empty M 1 15 Customer storage location K 7 16 Supplier number M 9 Supplier number 17 Point of consumption M 14 18 Call-off number K 4 19 Customer identifier (for individual

orders) K 6

20 Document no. Customer K 14 21 Empty M 5

129

Record type 714: Delivery note item Item Data element M/O Length Comment 01 Record type M 3 714 02 Version M 2 03 03 Customer part number M 22 Porsche editing for printing! 04 Supplier part number M 22 Customer part no. = Supplier part no.

Porsche editing for printing! 05 Country of origin M 3 06 Delivery quantity 1 M 13 07 Unit of quantity 1 M 2 08 Delivery quantity 2 K 13 not used 09 Unit of quantity 2 K 2 not used 10 VAT rate K 3 11 Empty M 1 12 Delivery note item number M 3 13 Call-off code K 1 14 Batch number K 15 15 Usage code M 1 16 Hazardous materials code K 8 17 Preferential status M 1 18 Dutiable goods M 1 19 Empty M 1 20 Inventory status M 1 Stock status (Blank = released, 1=locked) 21 Changed version code M 2 22 Original delivery note number K 8

130

Record type 715: Packaging data Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Customer packaging number M 22 not used 04 Supplier packaging number M 22 not used 05 No. of packaging units M 13 not used 06 Delivery note item number M 3 not used 07 Capacity M 13 not used 08 Package number from M 9 not used 09 Package number to M 9 not used 10 Packaging dimensions K 12 not used 11 Stacking parameter K 1 not used 12 Stock call-off number K 15 not used 13 Label identifier M 1 not used 14 Packaging identifier K 1 not used 15 Ownership identifier K 1 not used 16 Empty M 1 not used Record type 716: Text on delivery note item Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Text 1 K 40 not used 04 Text 2 K 40 not used 05 Text 3 K 40 not used 06 Empty M 3 not used Record type 717: Package record for item Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Individual package number M 15 not used 04 Delivery quantity 1 K 13 not used 05 Unit of quantity 1 K 2 not used 06 Delivery quantity 2 K 13 not used 07 Unit of quantity 2 M 2 not used 08 Batch number K 15 not used 09 Empty M 63 not used

131

Record type 718: Production numbers data Item Data element M/O Length Comment 01 Record type M 3 not used 02 Version M 2 not used 03 Delivery note number M 8 not used 04 Production number 1 M 10 not used 05 Production number 2 K 10 not used 06 Production number 3 K 10 not used 07 Production number 4 K 10 not used 08 Production number 5 K 10 not used 09 Production number 6 K 10 not used 10 Production number 7 K 10 not used 11 Production number 8 K 10 not used 12 Production number 9 K 10 not used 13 Production number 10 K 10 not used 14 Production number 11 K 10 not used 15 Empty M 10 not used Record type 719: Trailer record of delivery note/transport data Item Data element M/O Length Comment 01 Record type M 3 719 02 Version M 2 02 03 Counter record 711 M 7 04 Counter record 712 M 7 05 Counter record 713 M 7 06 Counter record 714 M 7 07 Counter record 715 M 7 08 Counter record 716 M 7 09 Counter record 717 M 7 10 Counter record 718 M 7 11 Counter record 719 M 7 12 Empty M 60

132

Example file: 71103RVS 400012 0000400005071120 000045216 7120310811061010Nybrok Oy 07082910360004529000452801 0045 01WCK-857 00000000000000 7130310069224070828KA 03 200000 60100000000 0006 71403987.552.101.13 A11 987.552.101.13 A11 0040000000001000ST0000000000000ST000 001 S G 71802100692240001480450 71403987.552.101.12 9C6 987.552.101.12 9C6 0040000000001000ST0000000000000ST000 002 S G 71802100692240001480455 71403987.552.101.12 9D7 987.552.101.12 9D7 0040000000001000ST0000000000000ST000 003 S G 71802100692240001480452 71403987.552.101.12 9L4 987.552.101.12 9L4 0040000000001000ST0000000000000ST000 004 S G 71802100692240001380748 71403987.552.102.12 9L4 987.552.102.12 9L4 0040000000001000ST0000000000000ST000 005 S G 71802100692240001480458 71403987.552.101.11 N12 987.552.101.11 N12 0040000000001000ST0000000000000ST000 006 S G 71802100692240001380731 […] 7130310069251070828KA 03 60100000000 0006 71403987.552.102.11 8G2 987.552.102.11 8G2 0040000000001000ST0000000000000ST000 001 S G 71802100692510001380768 71403987.552.101.12 9L4 987.552.101.12 9L4 0040000000001000ST0000000000000ST000 002 S G 71802100692510001480484 71403987.552.102.12 9D7 987.552.102.12 9D7 0040000000001000ST0000000000000ST000 003 S G 71802100692510001380766 71403987.552.101.11 3S9 987.552.101.11 3S9 0040000000001000ST0000000000000ST000 004 S G 71802100692510001480467 If you require an example file with special content, please get in touch with your Porsche EDI contact.

133

10.19 PLG VDA 4921 waybill

Record type 751: Header record Item Data element M/O Length Comment 01 Record type M 3 751 02 Version M 2 01 03 Data recipient number M 9 04 Data sender number M 9 05 Transmission number old M 5 06 Transmission number new K 5 6-digit 07 Transmission date M 6 YYMMDD 08 Empty M 89 Record type 752: Transport vehicle identification Item Data element M/O Length Comment 01 Record type M 3 752 02 Version M 2 01 03 Means of transport code M 2 04 Means of transport number M 25 05 Bordereau number M 17 05.1 Empty K Item 5 (15) item 5.1 (2)-digit blank;

corresp. to item 5( 17-digit) in acc. with VDA

06 Bordereau date M 6 07 Bordereau correction code M 1 <> "Blank" -> bordereau deletion,

reattachment; ="L" -> deletions and correction counters only, "1", "2", "…"

08 Special trip number K 8 09 Shipment volume K 6 10 Shipment loading metres K 12 11 Empty M 46 Record type 753: Transport identification (1 per vehicle) Item Data element M/O Length Comment 01 Record type M 3 753 02 Version M 2 01 03 Means of transport stopover date K 6 YYMMDD 04 Means of transport stopover time K 4 HHMM 05 Means of transport stopover location K 35 06 Scheduled arrival date K 6 YYMMDD 07 Scheduled arrival time K 4 HHMM 08 Information correction code M 1 <> "Blank" -> existing bordereau number

supplemented with transport data (record type 752, 753 allowed once only)

09 Empty M 67 free text

134

Record type 754: Shipping record supplement (1 per shipment ref. no.) Item Data element M/O Length Comment 01 Record type M 3 754 02 Version M 2 01 03 Supplier number M 9 03.1 Empty K Item 3 (6) item 3.1 (3) -> corresp. item 3 (

9-digit) in acc. with VDA 04 Shipment load reference number M 8 05 Shipping order number K 17 06 Shipping log date K 6 YYMMDD 07 Shipment scope code K 1 08 Gross shipment weight K 7 no decimal point 09 Net shipment weight K 7 no decimal point 10 No. of packages K 4 11 Unloading point K 5 as per Porsche AG specification 12 Supplier plant M 3 13 Customer plant M 3 14 Empty M 53 Record type 755: Delivery note directory (n per shipment ref. no. Item Data element M/O Length Comment 01 Record type M 3 755 02 Version M 2 01 03 Cargo delivery note table (delivery

note number) M 8

04 Delivery note number K 8 Left-aligned with no zeros 05 Delivery note number K 8 06 Delivery note number K 8 07 Delivery note number K 8 08 Delivery note number K 8 09 Delivery note number K 8 10 Delivery note number K 8 11 Delivery note number K 8 12 Delivery note number K 8 13 Delivery note number K 8 14 Delivery note number K 8 15 Delivery note number K 8 16 Delivery note number K 8 17 Delivery note number K 8 18 Delivery note number K 8 19 Empty M 3 Record type 759: Trailer record Item Data element M/O Length Comment 01 Record type M 3 759 02 Version M 2 01 03 Counter record 751 M 7 04 Counter record 752 M 7 05 Counter record 753 M 7 06 Counter record 754 M 7 07 Counter record 755 M 7 08 Counter record 759 M 7 09 Empty M 81

135

10.20 PLG VDA 4921 waybill to logistics service provider

Record type 751: Header record Item Data element M/O Length Comment 01 Record type M 3 751 02 Version M 2 01 03 Data recipient number M 9 04 Data sender number M 9 6-digit 05 Transmission number old M 5 06 Transmission number new K 5 07 Transmission date M 6 YYMMDD 08 Empty M 89 Record type 752: Transport vehicle identification Item Data element M/O Length Comment 01 Record type M 3 752 02 Version M 2 01 03 Means of transport code M 2 04 Means of transport number M 25 05 Bordereau number M 17 05.1 Empty K Item 5 (15) item 5.1 (2)-digit blank;

corresp. to item 5( 17-digit) in acc. with VDA

06 Bordereau date M 6 07 Bordereau correction code K 1 <> "Blank" -> bordereau deletion,

reattachment; ="L" -> deletions and correction counters only, "1", "2", "…"

08 Special trip number K 8 09 Shipment volume M 6 10 Shipment loading metres M 12 11 Empty M 46 Record type 753: Transport information Item Data element M/O Length Comment 01 Record type M 3 753 02 Version M 2 01 03 Means of transport stopover date K 6 YYMMDD 04 Means of transport stopover time K 4 HHMM 05 Means of transport stopover location K 35 06 Scheduled arrival date M 6 YYMMDD 07 Scheduled arrival time M 4 HHMM 08 Information correction code K 1 <> "Blank" -> existing bordereau number

supplemented with transport data (record type 752, 753 allowed once only)

09 Empty M 67 free text

136

Record type 754: Shipping record supplement (1 per shipment ref. no.) Item Data element M/O Length Comment 01 Record type M 3 754 02 Version M 2 01 03 Supplier number M 9 03.1 Empty K Item 3 (6) item 3.1 (3) -> corresp. item 3 (

9-digit) in acc. with VDA 04 Shipment load reference number M 8 05 Shipping order number M 17 06 Shipping log date K 6 YYMMDD 07 Shipment scope code K 1 08 Gross shipment weight M 7 no decimal point 09 Net shipment weight M 7 no decimal point 10 No. of packages M 4 11 Unloading point M 5 as per Porsche AG specification 12 Supplier plant K 3 13 Customer plant M 3 14 Empty M 53 Record type 755: Delivery note directory (n per shipment ref. no. Item Data element M/O Length Comment 01 Record type M 3 755 02 Version M 2 01 03 Cargo delivery note table (delivery

note number) M 8

04 Delivery note number K 8 right-justified with leading zeros. 05 Delivery note number K 8 06 Delivery note number K 8 07 Delivery note number K 8 08 Delivery note number K 8 09 Delivery note number K 8 10 Delivery note number K 8 11 Delivery note number K 8 12 Delivery note number K 8 13 Delivery note number K 8 14 Delivery note number K 8 15 Delivery note number K 8 16 Delivery note number K 8 17 Delivery note number K 8 18 Delivery note number K 8 19 Empty M 3

137

Record type 759: Trailer record Item Data element M/O Length Comment 01 Record type M 3 759 02 Version M 2 01 03 Counter record 751 M 7 04 Counter record 752 M 7 05 Counter record 753 M 7 06 Counter record 754 M 7 07 Counter record 755 M 7 08 Counter record 759 M 7 09 Empty M 81 Example file 75101200002 256280 1300313004080117 7520112H-VV1871 KS-S4536 B080117A 080116 000015000000000004 753010000000000 0801171300 7540122158 F080117A14982155 080116 000215500014390004BLECH W5 75501L080117A 7540114482 F080117A14982164 080116 000128400003980010BLECH W5 75501L080117A 7540117436 F080117A14982164 080116 000128400003980010BLECH W5 75501L080117A 75901000000100000010000001000000200000020000001 If you require an example file with special content, please get in touch with your Porsche EDI contact.

138

10.21 VDA 4927 empties processing

Record type 721 Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Recipient STRINGE 9 04 Sender STRINGE 9 05 Transmission number old NSTRINGE 5 06 Transmission number new NSTRINGE 5 07 Transmission date NSTRINGE 6 08 Transmission purpose code NSTRINGE 2 09 Text 1 STRINGE 40 10 Text 2 STRINGE 40 11 Empty STRINGE 7 Record type 722 Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Supplier number STRINGE 9 04 Supplier location code STRINGE 5 05 Customer number STRINGE 9 06 Customer location code STRINGE 5 07 Text 1 STRINGE 40 08 Text 2 STRINGE 40 09 Empty STRINGE 15 Record type 723 Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Customer part number STRINGE 22 04 Load carrier group STRINGE 9 05 Supplier part number STRINGE 22 06 No. of load carriers order old NSTRINGE 13 07 Plus/minus sign order old STRINGE 1 08 Booking date order old NSTRINGE 6 09 No. of load carriers order new NSTRINGE 13 10 Plus/minus sign order new STRINGE 1 11 Booking date order new NSTRINGE 6 12 Process data STRINGE 1 13 Target value of number NSTRINGE 13 14 Target value, days NSTRINGE 3 15 Empty STRINGE 13

139

Record type 724 Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Process code NSTRINGE 2 04 Document number STRINGE 8 05 Document item number 1 NSTRINGE 3 06 Document item number 2 NSTRINGE 3 07 Date of receipt NSTRINGE 6 08 Number of load carriers NSTRINGE 13 09 Plus.minus sign, number of

load carriers STRINGE 1

10 Book date NSTRINGE 6 11 Transport partner number STRINGE 14 12 Reference document number NSTRINGE 8 13 Reference document item 1 NSTRINGE 3 14 Reference document item 2 NSTRINGE 3 15 Reference document date NSTRINGE 6 16 Reference count NSTRINGE 13 17 Reference to plus/minus sign

for count STRINGE 1

18 Reference book date NSTRINGE 6 19 Delivery date NSTRINGE 6 20 Customer plant STRINGE 3 21 Empty STRINGE 18 Record type 725 Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Text 1 STRINGE 40 04 Text 2 STRINGE 40 05 Text 3 STRINGE 40 06 Empty STRINGE 3 Record type 729 Item Data element Field

type Length Default/Remark

01 Record type STRINGE 3 02 Version STRINGE 2 03 Counter record 721 NSTRINGE 7 04 Counter record 722 NSTRINGE 7 05 Counter record 723 NSTRINGE 7 06 Counter record 724 NSTRINGE 7 07 Counter record 725 NSTRINGE 7 08 Counter record 729 NSTRINGE 7 09 Empty STRINGE 81 If you require an example file, please get in touch with your Porsche EDI contact.

140

Abbreviations or or EDI Electronic Data Interchange i.e. that is EDI Electronic Data Interchange CRQ Cumulative received quantity etc. et cetera DCO DCO FMEA Failure Mode and Effects Analysis HHMM time information (hour, hour, minute, minute) JIS Just-in-Sequence YYMM00 Time info (year, year, month, month) YYMMDD Time info (year, year, month, month, day, day) YY00WW Time info (year, year, week, week) CW calendar week DR delivery instruction LSP Logistics service provider HGV heavy goods vehicle Acc. to according to m metre NOK not OK os. or similar JIT/JIS call-off production synchronised call-off PAG Dr. Ing. h. c. F. Porsche AG PDP Product development process PLG Porsche Leipzig GmbH Item Position SDN Sequence dispatch note SLC Special load carrier soc. so called SOP Start of Production Tel. telephone CDDN Cumulative daily delivery note incl. including ITI Installation time information VDA Verein deutscher Automobilindustrie (Association of the German Automotive Industry) WE goods receipt e.g. for example