electronic data interchange manual...electronic data interchange manual daimler ag issued december...
Post on 11-Apr-2020
4 Views
Preview:
TRANSCRIPT
Daimler AG
Issued December 2014
Electronic Data
Interchange Manual
(EDI)
Electronic Data
Interchange Manual
Daimler AG
Issued December 2014
Dear supplier,
This manual describes the structure of the information flows involved in the Daimler AG procurement process
for the passenger car and commercial vehicle (*) divisions.
In order to ensure a consistent, fault-free and prompt flow of information, optimising the interchange of the
data required for the delivery process is an important objective in the global automotive industry.
This manual provides advice on setting up essential support facilities and on making the transition to
communication by EDI (Electronic Data Interchange). This will help you maintain and increase your
competitiveness in the marketplace.
The following aspects are described in turn:
the general role of electronic data interchange in the supply process
the messages used in communications
the technical prerequisites
the required set-up procedures for starting electronic data interchange and the testing procedure.
There is also an Appendix listing the names of contact persons for specific message types in the various
plants.
All comments, remarks or questions relating to this manual should be referred to:
SC/SET department
HPC F201
71059 Sindelfingen
Phone +49-7031-90-26 53
050_dqm@daimler.com
Questions of a specialised technical nature may be referred to one of the contact persons listed in Chapter 12.
* Wherever the term “Daimler AG plants” is used, this refers to the PC division (Mercedes-Benz Cars and
Vans) and CV division (Daimler Trucks and Buses).
Electronic Data
Interchange Manual
Daimler AG
Issued December 2014
Electronic data interchange with Daimler AG
Chapter 1 EDI as the communication channel for the procurement process 4
at Daimler AG
Message types
Chapter 2 Call-off messages 8
VDA 4905 -> Call-off
VDA 4915 -> Detailed call-off
VDA 4905/2 -> Call-off based on the ODETTE message DELINS
Chapter 3 Delivery note and transport data according to VDA 4913 28
Chapter 4 Goods accompanying slip according to VDA 4912 (document) 68
Chapter 5 Material label according to VDA 4902, version 4 70
Chapter 6 Forwarding instruction according to VDA 4922 73
Chapter 7 Package data sheet according to VDA 4931 76
Chapter 8 Container account statements according to VDA 4927 77
Chapter 9 Transport data for shipments according to VDA 4921 83
Chapter 10 Invoice data according to VDA 4906 100
Working with EDI
Chapter 11 From procedure test to productive use 104
Chapter 12 Daimler AG contact persons 109
Modifications
Chapter 13 Version administration 119
Chapter 1 Electronic Data
Interchange Manual
Page 4
Daimler AG
Issued December 2014
EDI as the communication channel for the Daimler AG procurement
process
Content overview
1 EDI as the communication channel for the Daimler AG procurement process 5
1.1 Benefits of electronic data interchange 5
1.2 Using electronic data interchange in the Daimler AG procurement process 6
1.2.1 The following messages will be used for EDI communications with Daimler AG plants: 6
1.3 Use of the ODETTE/EDIFACT international message standard 7
Chapter 1 Electronic Data
Interchange Manual
Page 5
Daimler AG
Issued December 2014
1 EDI as the communication channel for the Daimler AG procurement
process
1.1 Benefits of electronic data interchange
Daimler AG began using electronic data interchange back in 1983, as what was then a very new way of
exchanging information. EDI is now well established as a reliable state-of-the-art channel of communication
for doing business in today’s world.
Particularly in view of advances in logistics, Daimler AG plants and their suppliers will be working more
closely together than in the past. This will mean increased process synchronisation, which would not be
feasible without the use of electronic communication channels.
The main aims of EDI communication are as follows:
fast and secure data interchange
paper-free data interchange
elimination of repeated data entry by the recipient (time and cost)
reduction of errors caused by having to re-input the data
standard interfaces for processing regularly recurring bulk data communications
no printing on expensive multiple-copy forms
However, EDI is more than just another channel of communication. By enabling fast, standardised data
interchange, it creates the basis for enhancements to other related processes, thereby generating potential
savings.
Examples of these enhancement opportunities include:
Reductions in administration expenses through:
- standardisation of work processes, and therefore simplification of processes both across multiple
workplaces and within individual workplaces
- immediate availability of data for further processing with user programs
Faster flow of information, resulting in
- immediate reaction to changed requirements
- faster flow of goods
- fewer one-off operations, such as special transport consignments
- more accurate planning
- greater flexibility
- less capital tied up in inventories
These enhancements are available to all parties involved in the communication process.
The prerequisite is the successful integration of EDI into internal systems and processes.
We expect all our partners, including component suppliers, area contract freight forwarders and external
service providers, to make effective use of these state-of-the-art communication technologies and resources,
becoming more competitive in the process.
Chapter 1 Electronic Data
Interchange Manual
Page 6
Daimler AG
Issued December 2014
We see this as a fundamental requirement for our mutual efforts to optimize the costs and processes of our
business operations.
Our purchasing partner selection decisions will be based not only on optimum quality of the actual service,
e.g. material or transport, but also implicitly on the provider’s readiness to display flexibility and innovation,
and therefore the ability to use state-of-the-art communication systems.
This attitude is also shared by other automotive producers and in other sectors, so showing some initiative in
this area is very much in your own best interests as well.
Accordingly, these requirements – which we have been voicing for some years now – are not seen as an
appropriate area for any investment contribution on our part.
As far as transmission fees are concerned, Daimler AG has always followed the principle of “sender pays”.
To enable our partners to remain competitive and to protect their investment, Daimler AG undertakes to
comply with established message standards.
1.2 Using electronic data interchange in the Daimler AG procurement process
For the formalisation of interchange data, Daimler AG follows the message formats developed by the VDA
(German Automotive Industry Association), published as “VDA recommendations 49xx”.
1.2.1 The following messages will be used for EDI communications with Daimler AG plants:
VDA 4905 EDI for call-offs
VDA 4906 EDI for invoices
VDA 4907 EDI for remittance advices*)
VDA 4908 Credit note procedure
VDA 4913 EDI for delivery note and transport data
VDA 4915 EDI for detailed call-offs
VDA 4916 EDI for JIS call-offs
VDA 4927 EDI for container account statements and container
movements *)
VDA 4938 EDI for invoice
VDA 4938 Credit note procedure
*)
Optional: message exchange at supplier’s request
The following recommendations apply as for goods accompanying documents:
VDA 4902/version 4 material label
VDA 4912 EDI goods accompanying slip
VDA 4922 forwarding instruction
Descriptions of the VDA messages are available at:
http://www.vda.de
Chapter 1 Electronic Data
Interchange Manual
Page 7
Daimler AG
Issued December 2014
Daimler AG purchasing contracts include the “Mercedes-Benz Special Terms” as a legally binding component.
You are requested to note the following Mercedes-Benz Special Terms (MBST) in particular, since they include
Daimler-specific details.
Mercedes-Benz Special Terms No. 28
Use of containers of
Daimler AG
Mercedes-Benz Special Terms No. 29
Material label as per VDA
4902, version 4 recommendation
Mercedes-Benz Special Terms No. 35
Communication with Daimler AG plants
by EDI
Your Sales department has copies of these documents. Further copies are available from:
Daimler AG
Vertragsmanagement
Department: MP/SC3
HPC G036
D-71059 Sindelfingen
1.3 Use of the ODETTE/EDIFACT international message standard
In view of the increasing globalisation of the automotive industry, as well as using EDI according to VDA
recommendations, Daimler AG also works with the ODETTE and EDIFACT international standards.
The necessary conversions are being developed progressively for the various message types.
Please ask the contact person for the specific message type you require for details of the facilities available.
We will then forward the appropriate documents separately.
By way of example, this manual presents the conversion of the call-off message according to VDA 4905/2
(DELINS in the ODETTE system).
Chapter 2 Electronic Data
Interchange Manual
Page 8
Daimler AG
Issued December 2014
Call-off messages
VDA 4905 -> Call-off
VDA 4915 -> Detailed call-off
VDA 4905/2 -> Call-off based on the ODETTE message DELINS
Content overview
2 Call-off messages 9
2.1 Call-off according to VDA 4905 9
2.1.1 Objectives of call-off 9
2.1.2 Fundamentals 9
2.1.3 Issuing a call-off 10
2.1.4 The VDA 4905 message 10
2.1.5 Form contents and explanation of fields 11
2.1.6 Example of generating a VDA 4905 16
2.2 Detailed call-off according to VDA 4915 18
2.2.1 Objectives/area of application of a detailed call-off 18
2.2.2 The VDA 4915 message 18
2.2.3 Example of generating a VDA 4915 23
2.3 Call-off message according to VDA 4905/2 24
2.3.1 Message VDA 4905/2 24
2.3.2 Using the UNB segment 25
2.3.3 Segment sequence of the message itself 25
2.3.4 Special features 26
2.3.5 Example for generation of a VDA 4905/2 27
2.4 Alternative EDI web 27
Authors of section 2.1/2.2
Ms Radermacher-Pillnick Mr Herbig Mr Tombor
Bremen plant Sindelfingen plant Wörth plant
Department: LOG/SPL Department: LOG/SPL Department: ML1-T6
Phone +49(0)4 21- 4 19 37 21 Phone +49(0) 70 31-90-73 28 Phone +49(0) 72 71-71-29 52
Fax +49 (0)4 21- 4 19 79 37 21 Fax +49(0) 70 31-90-8 12 02 Fax +49(0) 72 71- 71-69 65
Author of Chapter 2.3
Mr Miethe
T-Systems
Chapter 2 Electronic Data
Interchange Manual
Page 9
Daimler AG
Issued December 2014
2 Call-off messages
EDI transmission of call-off data is the part of the process chain starting from the customer request and
proceeding through the issuing of purchase order or call-off data to goods receipt of the ordered material.
The demand data is sourced from different upstream systems, so the delivery intervals vary, and in some
cases there can even be multiple deliveries in a single day.
The required data is generated at individual locations, according to the following VDA recommendations:
VDA 4905 EDI for call-offs
VDA 4905/2 EDI for call-offs based on the ODETTE message DELINS
VDA 4915 EDI for detailed call-offs
VDA 4916 EDI for JIS call-offs
You should consult with the relevant plant MRP controller on whether messages according to
VDA 4915 or VDA 4916 are to be generated in addition to the VDA 4905 message.
In view of the increased emphasis on international supplier relationships and the increasing implementation
of EDI messages according to the ODETTE standard (Organisation for Data Exchange by Teletransmission in
Europe -> European automotive associations grouping), the ODETTE call-off message DELINS (“Delivery
Instruction”), corresponding to VDA recommendation 4905/2, is to be provided for receiving call-offs in
ODETTE format (see section 2.3.).
This message is an alternative to the familiar VDA messages, which Daimler AG will continue to maintain.
2.1 Call-off according to VDA 4905
VDA recommendation VDA 4905 is used for call-offs for productive material.
In general, purchase orders for non-productive material (ancillary materials and supplies, capital goods,
etc.) will be processed using eDOCS wherever possible. Please consult your MRP controller.
2.1.1 Objectives of call-off
Along with the general benefits of EDI communication (e.g. fast, paper-free data transmission), the
interchange of call-offs in this way results in the following specific benefits:
immediate availability of the data for further processing
rapid response to changes in requirements
better service
enhanced competitiveness
2.1.2 Fundamentals
A call-off notifies the supplier of requirement quantities in the near, medium and distant future. This provides
the supplier with the basis for production scheduling and primary material scheduling and shipping
management.
EDI data has the same legally valid status as data in hard-copy documents.
The party generating the data is responsible for checking the completeness of the information in call-offs sent
by electronic channels. On receipt of the communication, the data is saved and checked, and in-house data
required for further computer processing is added.
We recommend that you store the data on a data carrier for a certain time.
Chapter 2 Electronic Data
Interchange Manual
Page 10
Daimler AG
Issued December 2014
The data received can be uniquely assigned via the following sort criteria:
Customer plant
Customer part number
Delivery point
New LAB (call-off) replaces old LAB
2.1.3 Issuing a call-off
Call-offs are based on the Daimler AG production program for:
JIT,
JIS,
LLZ,
warehouse and
frequency.
VDA standard 4905 is used for standard deliveries to warehouses and LLZs.
VDA standards 4915 or 4905 apply to standard detailed deliveries.
LPS = Lieferabruf- und Produktionsverbund-System
(German acronym for call-off and coordinated production)
Call-off data is issued via LPS or SAP as the base system. The output data is VDA-compliant, with no
requirement for confirmation of delivery dates and quantities.
2.1.4 The VDA 4905 message
The VDA 4905 message comprises the following records:
Record type Contents
511 Call-off data header record (1x per EDI run)
512 One-off data elements for call-off (1x per sort criterion)
513 Demarcation and call-off data (1x per sort criterion)
514 Other call-off data (x times per sort criterion)
515 Additional LAB (call-off) information (1x per sort criterion)
517 Packing material data (x times per sort criterion)
518 Text data (x times per sort criterion)
519 Call-off trailer record (1x per EDI run)
Chapter 2 Electronic Data
Interchange Manual
Page 11
Daimler AG
Issued December 2014
Note on record type 512, pos. 4, LAB number:
Definition: The LAB number is used to identify the call-off.
It is a 9-character term, structured as follows:
Character Meaning Example
1 Plant number 10
2
3
4 Last digit of year “6” for 1996
5 Month according to PTB “7” for PTB run month 7
6
7 LAB serial number Numbering begins with “00” for
PTB main carriage run
8
9 Requirement origin identifier P -> Main carriage run
N -> On-carriage run
H -> HTS run
A -> ATB/TBE run or daily run for differently
managed positions
C -> BTD run
M -> Manual MRP
Z -> LAB for changed MDI/TPM or ABS
S -> Cancellation call-off for unloading point
change
* -> Online requirement input
(see examples on following pages)
2.1.5 Form contents and explanation of fields
Note: Up to and including 2006, this section was part of Mercedes-Benz Special Terms, Appendix 17 (MBST
17 Anlage). The information has been removed from that document following its inclusion here.
2.1.5.1 Form header
Field
no.
Field name/
data element
Mandatory
Optional
Adjustment Alpha/
num.
Explanation
(1) Orderer’s
word/pictorial mark
M – A Name/acronym and additional
characterisation of orderer
completing call-off.
(1.1) KN O 9 A/N Customer number, i.e. the ID number
the supplier has assigned to the
orderer.
(1.2) Orderer’s postal
address
M – A
(5) Supplier’s postal
address
M – A 40 x 85 mm, with reference mark
(5.1) LN M 9 Supplier number, i.e. the ID number
the orderer has assigned to the
supplier.
Chapter 2 Electronic Data
Interchange Manual
Page 12
Daimler AG
Issued December 2014
2.1.5.2 Reference character section
Field
no.
Field name/data
element
Mandatory
Optional
Adjustment Alpha/
num.
Explanation
(10) Orderer characters M 4 A Department acronym, ref.,
MRP controller ID, or similar.
(15) Additional orderer
data
O 4 A Additional data for field 10.
(26) Delivery point M 5 A Delivery location within plant
specified in field 25.
(31) Quantity unit M 2 A/N Codes used:
ST = pieces
M = metre
M² = square metre
M³ = cubic metre
L = litre
T = tonne
KG = kilogram
KM = kilometre
Package-based quantity units (e. g.
dozen, gross, set, bag, box, sack, etc)
are not permitted. Such items
must be converted into the
permitted quantity units which
may involve the assignment of a
new part number. The package-
based unit may be stated if required
in the description of goods/services
(field 29).
(50) Call-off no. M 9 A Assigned by party generating the
call-off in ascending order/for each
call-off document 1)
(51) Call-off date M 8 A DD.MM.YY
(52) Replaces call-off no. O 9 A Indication of the preceding call-off,
which is being replaced by this one.
(52.1) Replaces call-off date O 8 A Indication of the most recent call-off
date, DD.MM.YY
(25) Shipping address O 30 A Goods recipient’s address if different
from orderer’s address.
(11) Contract/purchase
order no.1
O 12 A Indication of the contractual basis
for the call-off.
(11.1) Contract/purchase
order date2
O 8 A DD.MM.YY
(53) Name/phone number
of contact person in
orderer’s
organisation
O 15/5 A For any subsequent enquiries.
1At this point plant 010 sends the internal call-off no. from SAP, which is not the same as the purchasing
contract no. (contractual basis). 2 At this point plant 010 sends the internal call-off creation date in the form DD.MM.YYYY.
Chapter 2 Electronic Data
Interchange Manual
Page 13
Daimler AG
Issued December 2014
1) The following flags may be used as the last character:
A = ATB requirement (= ordered parts requirement)
H = HTS requirement (= in-house parts management)
P = Main carriage run
N = On-carriage run
C = CIMOS requirement
* = LAB (call-off) with manual changes (computerised timeframe)
M = Manual LAB (quantity and date (if applicable) entered manually)
J = Recoded manual LAB (01 replaced by “M” in main carriage run)
Z = LAB for change in master data (change in means of transport or MDI change [= material purchasing
MRP controller])
Field
no.
Field name/
data element
Mandatory
Optional
Adjustment Alpha/
num.
Explanation
(28) Orderer’s part
number
M 22 A The part number is used to identify a
material/sales article. Appears as
print format/template (as specified
by orderer, with special marks,
spaces, etc.)
(54) Name/phone
number of supplier
contact person
O 15/5 A Left free for entry of supplier data.
(28.1) Supplier’s part
number
O 22 A Supplier part numbers administered
by the orderer are printed in this
field. Appears as print
format/template (as specified by
supplier, with special marks, spaces,
etc.).
(29) Identification of
goods/services
M 3 x 50 A Text field for identification of
material/sales article, including
Daimler delivery rules.
(55) Left free for supplier O – – Reserved field for supplier’s
in-house processing remarks.
(56) Total call-off
cumulative
quantity/old
O 10 N Cumulative quantity shown under
last “call-off quantity” field of
previous call-off.
(57) Difference between
total call-off
cumulative
quantity/old and
new
O 10 N The difference (+/) shows the
variance between the total call-off
cumulative quantity in this call-off
invoice (new) and the previous one
(old).
(58) Production release
(mth)
M 10 N The orderer assumes an acceptance
obligation for the material/sales
article identified in field 29 for the
quantities shown in this period.
(59) Additional material
release (mth)
M 10 N The orderer assumes an acceptance
obligation for part-related input
material for the quantities shown in
this period.
(61) Other O 50 A Text field, e.g. non-serial part,
payment or delivery condition.
Chapter 2 Electronic Data
Interchange Manual
Page 14
Daimler AG
Issued December 2014
2.1.5.3 Body of form
Field
no.
Field name/
data element
Mandatory
Optional
Adjustment Alpha/
num.
Explanation
(62) Date of last
recorded delivery
M 8 A Shipping date, DD.MM.YY
(30) Quantity of last
recorded delivery
M 13 N 3 decimal places are provided.
(63) Cumulative
received quantity
(from date)
M 10 N Cumulative quantity comprising all
positive/negative posted deliveries to
orderer from a particular date (e. g.
from 1.1. of current year) until date of
this call-off invoice.
(64) Delivery note no. O 8 A
(18) Dates M 8 A/N Dates may be expressed as days,
weeks or months. A day specified for call-off quantities
refers to the date for arrival of the
shipment at the orderer’s premises.
Special forms for dates are “backlog”
[Rückstand], “immediate
requirement” [Sofortbedarf] and
“remainder” [Rest]. A backlog is the positive difference
between the cumulative quantity as
of the date of this call-off invoice
minus the cumulative received
quantity.
The call-off cumulative quantity as of
the call-off date is always taken as the
smaller of the values from the
mathematical comparison between
the old and new call-off cumulative
quantities.
The call-off cumulative
quantity/old [Abruf-Fz/alt] is the
value forecast in the previous call-off
invoice for the date of the present
call-off invoice, whereas the call-off
cumulative quantity/new [Abruf-
Fz/neu] is the value stated as of the
date of the present call-off invoice for
that same date.
Accordingly,
any backlog is diminished by
retrospective programme reductions;
but not increased by retrospective
program increases.
Chapter 2 Electronic Data
Interchange Manual
Page 15
Daimler AG
Issued December 2014
(18) Deadlines
(continued)
M 8 A/N An immediate requirement is
generally only indicated if the call-off
cumulative quantity/new is higher
than the call-off cumulative
quantity/old on the call-off date.
The immediate requirement is then
the positive difference between the
call-off cumulative quantity/new
[Abruf-Fz/neu] and the sum total of
the cumulative received quantity
[Eingangs-Fz] and the backlog.
Also added to the immediate
requirement may be further call-off
quantities whose arrival date falls
within an “immediate requirement
period” [Sofortbedarfs-Frist] set at the
orderer’s discretion.
Examples of an immediate
requirement period could include:
the period up until the date of the
next call-off invoice
the period up to the end of the
week or plan period in which the
date of the present call-off invoice
falls
a certain number of workdays
within the period up to the date of
the next call-off invoice.
Negative values for backlog and
immediate requirement are not
shown, but instead netted off against
other requirement quantities until
such time as the balance is again
positive. This positive remainder then
forms the first dated call-off quantity
of the present call-off.
The remainder [Rest] may be the
sum total of forecast quantities for
several subsequent months beyond
the month specified in the
immediately preceding call-off field.
(30) Quantity M 10 N No decimal places.
(63) Call-off cumulative
quantity (Abruf-Fz)
M 10 N Cumulative quantity that must have
been met by all deliveries posted by
the orderer from a date (e.g. 1.1. of
the current year) up to the specified
call-off deadline date. The call-off
cumulative quantity is formed on the
basis of the cumulative received
quantity by ongoing accumulation of
the call-off quantities (including
backlog and immediate requirement).
(65.1) Difference (D) O 10 N The difference [Differenz] indicates
significant changes in the orderer’s
requirement structure.
Chapter 2 Electronic Data
Interchange Manual
Page 16
Daimler AG
Issued December 2014
(67) Container O 20 A Field showing container type and
notional capacity (67.1) and container
identification (67.2).
(68) Remarks O 50 A Additional field for notes to supplier.
2.1.6 Example of generating a VDA 4905
Record type Pos Data element Example
511 01 Record type 511
02 Version number 02
03 Customer number 123456789
04 Supplier number 123456789
05 Interchange no. old 00860
06 Interchange no. new 00861
07 Interchange date 040813
08 Date of resetting
Cumulative received qty
040125
Record type Pos Data element Example
512 01 Record type 512
02 Version number 01
03 Customer plant 10_
04 Call-off no. new 10_40703A
05 Call-off date new 040813
06 Call-off no. old 10_40702A
07 Call-off date old 040810
08 Customer part number A1112223344
09 Supplier part no. Empty (opt. field)
10 Contract/PO no. Empty (opt. field)
11 Delivery point 913A_
12 Customer characters 51_
13 Quantity unit ST
14 Delivery interval L
15 Production release 1
16 Material release 1
17 Use code S
18 Account assgnmt code 31
19 Warehouse empty
Record type Pos Data element Example
513 01 Record type 513
02 Version no. 01
03 Last recorded goods entry date 040723
04 Delivery note no. for last goods
entry
00515943
05 Delivery note date for
last goods entry
040722
06 Quantity of last goods entry 000010188
07 Cumulative rec. qty 0000000675782
08 Call-off date 1 33333 (backlog)
09 Call-off quantity 1 000069914
10 Call-off date 2 44444 (immed. req.)
11 Call-off quantity 2 000015976
12 Call-off date 3 040814
13 Call-off quantity 3 000095290
14 Call-off date 4 040815
15 Call-off quantity 4 000101905
16 Call-off date 5 040816
17 Call-off quantity 5 000087250
Chapter 2 Electronic Data
Interchange Manual
Page 17
Daimler AG
Issued December 2014
Record type Pos Data element Example
514 01 Record type 514
02 Version number 01
03 Call-off date 6 040819
04 Call-off quantity 6 000044913
05 Call-off date 7 040820
06 Call-off quantity 7 000108640
07 Call-off date 8 040821
08 Call-off quantity 8 000070172
09 Call-off date 9 040822
10 Call-off quantity 9 000006333
11 Call-off date 10 960913
12 Call-off quantity 10 000058720
13 Call-off date 11 861014
14 Call-off quantity 11 000060221
15 Call-off date 12 961115
16 Call-off quantity 12 000058432
17 Call-off date 13 999999
(remainder qty)
18 Call-off quantity 13 000050000
Record type Pos Data element Example
515 01 Record type 515
02 Version no. 02
...*
13 For reset of cumulative
quantity reached
* Positions 03–12 are filled with an initial value.
For alphanumeric defined fields: blank
For numeric defined fields: “0”
Record type Pos Data element Example
517 01 Record type 517
02 Version number 01
03 Cust. packing material no. 4314
04 Suppl. packing mat. no. Empty (opt. field)
05 Capacity 0010000
Record type Pos Data element Example
518 01 Record type 518
02 Version number 01
03 Call-off text 1 abcdefgh...
04 Call-off text 2 Opt. field
05 Call-off text 3 Opt. field
Record type Pos Data element Example
519 01 Record type 519
02 Version number 03
03 Counter record type 511 0000001
04 Counter record type 512 0000004
05 Counter record type 513 0000004
06 Counter record type 514 0000005
07 Counter record type 517 0000004
08 Counter record type 518 0000004
09 Counter record type 519 0000001
10 Counter record type 515 0000001
Note: In record type 512, a cancellation is indicated with an “S” at character 29, and the correct data is then provided in the same file. For LLZ: Record type 515 Position 14 (character 111): Indicator for interchange type minimum coverage (R/B) Position 15 (characters 112–123): Minimum stock in workdays/stock
Chapter 2 Electronic Data
Interchange Manual
Page 18
Daimler AG
Issued December 2014
2.2 Detailed call-off according to VDA 4915
2.2.1 Objectives/area of application of a detailed call-off
Objective of detailed call-off
The aim is to generate call-offs for a selected range of parts, daily or even several times a day, in response to
changing production and assembly requirements, in order to optimise information and material flows.
The following are particularly suitable areas of application:
Parts families where the volumes involved require timely deliveries close to one or more user locations
without the use of interim depots.
Parts families subject to wide fluctuations in demand, requiring frequent updates to ensure deliveries are
made according to production requirements.
Detailed call-offs can also serve a number of purposes for the supplier:
precise shipping instructions
where applicable, as a tool for fine-tuning production schedules
advance notification of JIS call-offs (VDA 4916)
Advantages of detailed call-offs:
ability to process demand data in response to current requirements
ability to post special requirements arising within a workday
preliminary planning on hourly basis
timetable management
same-day call-off invoice
flexible interchange of demand data
flexible calendar management
early EDI dispatch (as VDA 4905)
low interchange volume (5 to 15 days)
2.2.2 The VDA 4915 message
The VDA 4915 message comprises the following records:
Record type Contents
551 Detailed call-off header record (1st record of EDI run)
552 One-off data elements of detailed call-offs (1x per sort criterion)
553 Detailed call-off demarcation data (max. 3x per sort criterion)
554 Detailed call-off data (x times per sort criterion )
555 Additional data for detailed call-off (1x per sort criterion)
556 Packing material data for detailed call-offs (max. 3x per sort criterion)
557 Detailed call-off text data (max. 3x per sort criterion)
559 Detailed call-off trailer record (last record in EDI)
Chapter 2 Electronic Data
Interchange Manual
Page 19
Daimler AG
Issued December 2014
Notes on individual record types
Record type 552
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 15 N 10 O Cumulative quantity
difference
Description:
The calculation of quantities for delivery must take account of over- and under-deliveries. In the example
shown below, this is done in the “UL/ÜL” field (= under- and over-delivery respectively).
Under-deliveries:
If a negative value is shown in the “UL/ÜL” field, you have to add this value to the ordered quantity.
Example:
The value “–10” appears in the “UL/ÜL” field. For your delivery operation, this means that on 28.11.95 you
are required to deliver a further 10 items in addition to the specified quantity of 14 (= 24).
DATUM 27.11.1995 ZEIT 09:53 FAB-NR 001 LSNR DATUM ZEIT MENGE
WE-FZ 1567 AVIS-MENGE 0 1. 00106348 24111995 07:30 36
LFT-KURZ ??? Status V 2. 00105689 23111995 07:30 36
BEN Gruppe 52HA1 3. 00105392 22111995 07:30 36
UL/ÜL Termin 28.11.95 29.11.95 30.11.95 01.12.95 02.12.95
-10 Zeit 07:30 07:30 07:30 07:30 07:30
Abruf-FZ Menge 14 18 18 25 22
1577 FZ 1591 1609 1627 1652 1674
Diff 0 6 18 25 22
Over-deliveries:
If a positive value appears in “UL/ÜL”, this quantity has to be subtracted from the ordered quantity.
Example:
The value “439” appears in the “UL/ÜL” field. For your delivery operation, this means that you will not have
delivered anything on 28.11.95, and only 19 items on 29.11.95.
DATUM 27.11.1995 ZEIT 09:53 FAB-NR 001 LSNR DATUM ZEIT MENGE
WE-FZ 16707 AVIS-MENGE 0 1. 00105924 24111995 07:30 240
LFT-KURZ ??? Status V 2. 00105914 23111995 07:30 240
BEN Gruppe 52HA1 3. 00105389 22111995 07:30 240
UL/ÜL Termin 28.11.95 29.11.95 30.11.95 01.12.95 02.12.95
439 Zeit 07:30 07:30 07:30 07:30 07:30
Abruf-FZ Menge 239 219 198 212 143
1577 FZ 16507 16726 16924 17126 17279
Diff 42 23 198 212 143
– 439 – 200
=
– 200 19
Any quantities already delivered that are not shown in the purchase order also have to be deducted from the
ordered quantity.
Referral to the correct last goods received data
Record type 553 shows the last three deliveries:
The first data fields (characters 16 to 48) contain the third to last delivery.
The second data fields (characters 49 to 81) contain the second to last delivery.
The third data fields (characters 82 to 114) contain the last delivery.
Chapter 2 Electronic Data
Interchange Manual
Page 20
Daimler AG
Issued December 2014
Example record type 553, characters 16 to 48
Record type 553
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos: 04 N 6 M Arrival date 1 091202
Description:
The customer posted the delivery as incoming goods on this day. Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos: 05 N 8 M Delivery note no. 1 23456789
Description:
ID number that the supplier assigns to a delivery note. Right-justified with leading zeroes.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos: 06 N 6 M Delivery note date 1 091130
Description:
Delivery date for the delivery posted at the customer’s site. Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos: 07 N 12 M Delivery quantity 1 000000300000
Description:
Quantity that the supplier reports in the delivery note; right-justified with leading zeroes. Three decimal
places.
Record type 552
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos: 08 A 5 O Unloading point 999
Description:
Specifies the point in the customer’s plant where the goods are to be unloaded. Customer’s codes used. Left-
justified.
Unloading point display variants in the call-off (VDA 4905) and associated detailed call-off (VDA 4915)
1. Part number with one unloading point:
a) Call-off and detailed call-off with the same 5-character unloading point.
Example: Call-off Detailed call-off
Unload. point: 470S0 470S0
Chapter 2 Electronic Data
Interchange Manual
Page 21
Daimler AG
Issued December 2014
b) Call-off has the dummy unloading point “9999”, indicating that this call-off is to be used solely for
planning purposes. The detailed call-off then has the actual 5-character unloading point.
Example: Call-off Detailed call-off
Unload. point: 9999 470S0
2. Part number with several unloading points:
a) There is a call-off for every detailed call-off. The unloading points are filled in in exactly the same
way for each call-off/detailed call-off, with five characters.
Example: Call-off Detailed call-off
1st unload. point: 332X0 332X0
2nd unload. point: 386C0 386C0
3rd unload. point: 470S0 470S0
b) In this case there is only one call-off, assigned the dummy unloading point “9999”, representing the
sum total of all planned requirements for the unloading points in question. In contrast, the detailed
call-offs contain the 5-character unloading points for which the unloading point-based requirements
will be shown.
Example: Call-off Detailed call-off
Unload. point: 9999 1.: 332X0
2.: 386C0
3.: 470S0
Variants a) and b) are available both for part numbers with one unloading point and for those with
multiple unloading points, by arrangement.
Record type 554
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos: 06 A 1 O Requirement status –
code 1
B
Description:
Use and explanation of requirement status
Code “B”. One field for each call-off time and call-off quantity:
“Bedarfsstatus bis “Bedarfsstatus Schlüssel 1“ Schlüssel x“ [= “requirement status to “requirement status
code 1” code x”]
This field is an optional field, i.e. it need not be filled in. It is, however, frequently used by Daimler AG by
arrangement with the suppliers involved.
Explanation:
The “B” code indicates, for the relevant call-off time/quantity, that there has been no change with respect to
the preceding call-off invoice, i.e. for a specified period these requirement quantities are “frozen”, and the
supplier can therefore take them from the previous call-off.
How requirements are frozen, and for how long, depends on two parameters, which are defined and entered
in the “detailed call-off” system in consultation with the supplier.
Chapter 2 Electronic Data
Interchange Manual
Page 22
Daimler AG
Issued December 2014
Time parameter
AV (call-off lead time)
This is the time between the call-off invoice EDI and shipment from the supplier (delivery note EDI).
3. TV (transport lead time)
This is the time between shipment from the supplier (delivery note EDI) and arrival at goods receipt.
The timeframe for frozen requirement numbers comprises AV + TV.
Example:
Timetable (delivery time per day):
08:00/12:00/16:00/20:00
AV: 2 hrs TV: 4 hrs
Deadline dates between AV + TV are given requirement status code = “B”.
This means that these deadline dates (requirement quantities) will not now be changed, because the
supplier’s response time is 6 hours, and the supplier is therefore unable to react to any further fluctuation in
requirements within AV + TV.
Abrufrechnung DFÜ
AV _____ TV _____
06:00
07:00 09:00
06:0010:00
11:00
12:00
13:00
06:0014:00
15:00
16:00
17:00
06:0018:00
19:00
20:00
21:00
06:0022:00
23:00
06:00
07:00
06:0008:00
09:00
10:00
11:00
06:0012:00
13:00
14:00
15:00
06:0016:00
17:00
18:00
19:00
06:0020:00
21:00
22:0008:00
Anlieferung
= “B“ *)
Anlieferung
= “B“ **)
Anlieferung Anlieferung Anlieferung Anlieferung Anlieferung Anlieferung
Chapter 2 Electronic Data
Interchange Manual
Page 23
Daimler AG
Issued December 2014
2.2.3 Example of generating a VDA 4915
Record type Pos Data element Example
551 01 Record type 551
02 Version number 01
03 Customer number 123456789
04 Supplier number 12345678_
05 Interchange no. old 00389
06 Interchange no. new 00390
07 Interchange date 960620
08 Year changeover
Date
960126
Record type Pos Data element Example
552 01 Record type 552
02 Version number 01
03 Customer plant 67_ or 50_
04 Detailed call-off no. new,
poss. several per day
67_20061_ or
50_20061_
05 Detailed call-off date 960260
06 Customer part number A2026900362_
00007167
07 Supplier part no. empty
08 Delivery point 123D1 or 12340
09 Customer storage location empty
10 Critical stock code K
11 Use code S
12 Detailed call-off horizon 000000
13 Deadline date code empty
14 Completion order number empty
15 Progress number difference -000000009
16 Assembly location 9003OTVU10
Record type Pos Data element Example
553 01 Record type 553
02 Version no. 01
03 Cumulative received qty 0000010900
04 Arrival date 1 960617
05 Delivery note no. 1 96511312
06 Delivery note date 1 960614
07 Delivery quantity 1 000000300000
08 Delivery status code I
09 Arrival date 2 960618
10 Delivery note no. 2 96511407
11 Delivery note date 2 960617
12 Delivery quantity 2 000000220000
13 Delivery status code 2 I
14 Arrival date 3 960619
15 Delivery note no. 3 96511523
16 Delivery note date 3 960618
17
18
Delivery quantity 3
Delivery status code 3
000000260000
I
Record type Pos Data element Example
554 01 Record type 554
02 Version number 01
03 Call-off date 1 960620
04 Call-off time 1 0700
05 Call-off quantity 1 000000280
06 Requirement status 1 B
07 Call-off date 2 960621
08 Call-off time 2 0700
09 Call-off quantity 2 000000240
10 Requirement status 2 -
ff. as per pos. 07–10
Chapter 2 Electronic Data
Interchange Manual
Page 24
Daimler AG
Issued December 2014
Record type Pos Data element Example
555 01 Record type 555
02 Version number 01
03 Intermediate supplier *
04 Additional part no. *
05 For reset of cumulative quantity
reached
0000007200
* These fields are filled with blanks.
Record type Pos Data element Example
557 01 Record type 557
02 Version number 01
03 Text 1
04 Text 2
05 Text 3
Record type Pos Data element Example
559 01 Record type 559
02 Version number 01
03 Counter record type 551 0000001
04 Counter record type 552 0000020
05 Counter record type 553 0000020
06 Counter record type 554 0000020
07 Counter record type 556 0000020
08 Counter record type 557 0000005
09 Counter record type 559 0000001
10 Counter record type 555 0000001
2.3 Call-off message according to VDA 4905/2
The call-off created by Daimler AG on the basis of the ODETTE DELINS message, version 3, edition of June
1990, is described in the following sections. This call-off corresponds to VDA recommendation 4905/2.
2.3.1 Message VDA 4905/2
The following table shows the segments in the ODETTE useful data section. The last column shows the
segments used in an interchange.
Segment
ID
Vers.
No.
Segment name/content
HL
ST
Reusability at Daimler AG
UNA
UNB
UNG
UNH
UNT
UNE
UNZ
1
1
1
1
1
1
1
Separator segment
Interchange header
segment
Header segment
Message group
Message header segment
Message end segment
End segment
Message group
Useful data segment
0
0
1
2
2
1
0
O
M
O
M
M
O
M
1x per interchange
1x per interchange
1x per interchange
1x per interchange
1x per interchange
Explanations:
HL = hierarchy/level of segment within message
ST = segment status -> M = mandatory segment, O = optional segment
Chapter 2 Electronic Data
Interchange Manual
Page 25
Daimler AG
Issued December 2014
2.3.2 Using the UNB segment
The content of the segment UNB is now discussed in greater detail:
Tag Element name Content
0001 Character set “UNOA”
0002 Version number “1”
0004 Sender ID ODETTE ID of the sender plant
e.g. for Wörth (plant 060): “O0013000577MB060000EDICS”
0010 Recipient ID ODETTE ID of the supplier
0017 Date of creation “960610”
0019 Generation time “0657”
0020 Reference no. 5-char. numeric entry with leading zeroes
e.g.: “00746”
2.3.3 Segment sequence of the message itself
The segments in the ODETTE message DELINS, version 3, are listed in the table below. The last column shows
the segments used in an interchange.
Segm
ID
Vers.
No.
Segment name/content
HL
ST
Reusability at Daimler AG
MID 3 Message recognition 0 M 1x per interchange
SDT 3 Supplier information 0 M 1x per interchange
MDT 3 Manufacturer information 0 O Not for VDA
BDT 3 Customer details 0 M 1x per interchange
ARI 3 Additional call-off
information
0 O 1x per interchange
CSG 3 Recipient information 1 M Unlimited
ITA 3 Recipient of the invoice 2 O Not for VDA
ARD 3 Parts information 2 M Unlimited
PDI 3 Preceding call-offs 3 O 1x per ARD
SAD 3 Additional parts information 3 O 1x per ARD
PDN 3 Last delivery note posted 3 M Max. 3x per ARD
SID 3 Acceptance obligation 3 O Max. 4x per ARD
DEL 3 Requirement details 3 M Unlimited
TCO 3 Packing mat. details 3 O Unlimited
ADI 1 Article call-off no. 3 O 1x per parts no.
DLP 3 Transport handover
agreement
0 O Not for VDA
FTX 3 Free text 1 O 1x per interchange
Explanations:
HL = hierarchy/level of segment within message
ST = segment status -> M = mandatory segment, O = optional segment
Chapter 2 Electronic Data
Interchange Manual
Page 26
Daimler AG
Issued December 2014
2.3.4 Special features
There are some special points to be noted for the following segments:
MID segment:
Daimler AG assigns call-off numbers on a parts number basis. For this purpose, VDA recommendation
4905/2 provides the option of entering the value “ARD” in the element MID-1004 (call-off no.), and leaving all
the other MID elements empty. The call-off no. and call-off date are sent in ADI-1004 and ADI-2007.
ARI segment:
The ARI segment is not sent. According to VDA recommendation 4905/2, the element ARI-7903 (call-off date
code) then implicitly has the value “2”, i.e. the call-off date refers to the arrival date.
DST segment:
Element DST-6804 is used to send the cumulative received quantity (EFZ). This EFZ is reset to zero at the
beginning of a new accumulation period (generally change of year).
DEL segment:
Daimler AG uses element DEL-2836 to send a preview period, in the format “YYWWYYWW” (Y=year,
W=week). Accordingly, this period always has a set starting date and ending date. However, Daimler AG also
often provides a preview period denoting the “remainder” (Rest) of the most recent explicitly defined preview
period. This is shown in DEL-2836 as “99999999”.
Chapter 2 Electronic Data
Interchange Manual
Page 27
Daimler AG
Issued December 2014
2.3.5 Example for generation of a VDA 4905/2
The following is an example of a ODETTE DELINS message as sent by Daimler AG.
UNA: + . ?’
UNB+UNOA:1+O0013000583MB060000+O0013000123MAIER001+960504:0857+00787’
UNH+1+DELINS: 3 : :OD’
MID+ARD’
SDT+12345678’
BDT+10491’
CSG+69+801’
ARD+R6584210001 : 353135+ :PCE+000001’
PDI+69 60400*+960411’
SAD+1+185’
FTX+NEW PART:DELIVERY CAN BE MADE TO JKD 1734 3640’
DST+960502+ :19490’
PDN+00009513 : 960430+360’
DEL+960506+720’
DEL+960507+360’
DEL+960508+360’
DEL+960509+360’
TCO+:5003++20’
ADI+69 60402*+960503’
CSG+ ...
...
...
...
ADI+ ...
UNT+64+1’
UNZ+1+00787’
2.4 Alternative EDI web
For VDA messages – for example a call-off – participants without EDI facilities can also use the Web EDI
process. For further information on Web-based EDI, go to:
http://ediweb.supplier.daimler.com/
Chapter 3 Electronic Data
Interchange Manual
Page 28
Daimler AG
Issued December 2014
Delivery note and transport data according to VDA 4913
Content overview
3 Delivery note and transport data according to VDA 4913 29
3.1 How the delivery note and transport data message according to VDA 4913 fits into
the goods receipt process at Daimler AG plants 29
3.2 Objectives of the delivery note and transport data EDI according to VDA 4913 30
3.3 The VDA 4913 message 30
3.4 Process optimisation by data quality management (DQM) 31
3.5 Structure of the VDA 4913 message 31
3.6 Notes on record types and data elements 32
3.6.1 Description of fields 32
3.7 Special cases for the delivery note and transport data message 53
3.7.1 Corrections 53
3.7.2 EDI resend capability 53
3.7.3 EDI problems 53
3.7.4 Emergencies 53
3.7.5 Sample deliveries 53
3.7.6 Return of empties 53
3.7.7 Central Loadunit for deliveries via courier Service 53
3.8 Contact person for problems with the EDIS communication 54
3.9 Tips and useful information 54
3.10 Transport management 55
3.10.1 Data transmission 55
3.10.2 Notes on record types and data elements 55
3.11 Generation by JIT and JIS suppliers (VDA 4913/JIT) 58
3.11.1 Short description of JIT and JIS suppliers 58
3.11.2 Notes on record types and data elements 58
3.12 Triangular traffic 59
3.12.1 Data sender via VDA 4913 59
3.12.2 Data sender via Edifact 60
3.12.3 Data sender via DQM 60
3.13 Generation by EDL (VDA 4913/EDL) 61
3.13.1 Brief description 61
3.13.2 Notes on record types and data elements 61
Author of Chapter 3
Ms Pischka
SC/SET department
Sindelfingen plant
050_dataquality@daimler.com
Chapter 3 Electronic Data
Interchange Manual
Page 29
Daimler AG
Issued December 2014
3 Delivery note and transport data according to VDA 4913
The delivery note and transport data EDI, according to VDA 4913, is the core message for material-
accompanying information. Our company has supported this application since 1984. It is our assumption that
all incoming goods shipments will be notified in advance with a delivery note EDI.
Delivery note data according to VDA 4913 are to be provided by:
suppliers (of series and non-series material)
JIT and JIS suppliers
external service providers (EDL)
LLZ
Some special requirements for completing the data fields apply for certain data sender groups.
Instructions and rules applicable to all groups are explained in sections 3.1 to 3.6. The special requirements
for generating VDA 4913 data for JIT and JIS suppliers, external service providers and area contract freight
forwarders are then discussed separately.
3.1 How the delivery note and transport data message according to VDA 4913 fits
into the goods receipt process at Daimler AG plants
Immediately on arrival in the plant, the truck driver reports to the truck management station. Provided the
EDI was sent in good time, the data is already in our user systems in an AVIS file (“Avis” = advice
notification). The data is actually received by the T-Systems EDIS system, and automatically forwarded to the
target user systems.
The staff at the counter input the keys shown in the waybill into the Daimler AG goods receipt systems, and
the data as per the advice notification are posted as a goods entry.
Your EDI data is handed to the truck driver as an unloading list and clearance voucher, with comments
confirming arrival of the consignment, for presentation to the unloading points. The truck is then driven to
the unloading point(s) in the plant.
Unfortunately, for process reliability reasons it is not possible to eliminate all hard-copy documentation for
supplier information accompanying goods consignments.
There are two options for hard-copy documents for EDI delivery notes:
EDI goods accompanying slip according to VDA 4912 (see Chapter 4). The use of this slip significantly
reduces the volume of paper documents. The submission of an EDI goods accompanying slip is
mandatory for all Daimler AG plants.
Delivery note according to DIN 4991 (fallback for special cases only).
Chapter 3 Electronic Data
Interchange Manual
Page 30
Daimler AG
Issued December 2014
3.2 Objectives of the delivery note and transport data EDI according to VDA 4913
Advance notification by EDI to the goods recipient advising that a shipment is on the way: the
information arrives before the goods.
High material availability with minimum stock. The material in the process of being transported can be
included in the assessment of stock and available material. This means fewer queries from the ordering
party to the sender/supplier.
Easier entry of delivery note and transport data for the recipient of the data.
Possibility of “automatic” GR processing, sometimes even “self-service” processing by the truck driver;
this will become an increasingly widely used method.
State-of-the-art goods receipt process by scanning of package labels, based on packing material data
according to VDA 4913.
The invoice checking desk receives the EDI delivery note data via an interface. There are fewer delays
with processing payments, since receiving the data by EDI eliminates all data entry errors by the goods
recipient.
3.3 The VDA 4913 message
The delivery note and transport data message according to VDA 4913 is one of the main messages and an
absolute requirement.
It demands an especially high level of process quality, and compliance with the following requirements is
particularly important:
Timely transmission
To ensure the early detection and efficient elimination of errors in information flows, the data must be
sent sufficiently early in the process to leave time for the initiating party (data sender) to correct any
errors using the Internet-based Daimler data quality management (DQM) application (see item 3.4).
The data must be sent to the goods recipient by no later than immediately after the consignment
handover to the goods recipient. Reason: For groupage consignments, our area contract freight forwarders
generate a transport EDI according to VDA recommendation 4921. VDA 4921 quotes the shipment
reference number and the delivery note numbers in the VDA 4913 message.
With certain processes, it may be necessary to send the data even earlier (see e.g. item 3.8).
Demarcation of consignments
The Consignment loading reference number (record type 712) is used to group 1 to n delivery notes
into a single consignment. The EDI and actual loading details must be exactly the same.
Packaging information
Record type 715 shows packing material information. One of its functions is to make the link with the
material label according to VDA 4902. The EDI and the label must correspond, because the barcode scan
is checked against the EDI content. This is described in detail in the VDA message.
In order to avoid problems and queries with the data flow and goods receipt process, please be particularly
careful to observe the requirements described in the next few pages.
Chapter 3 Electronic Data
Interchange Manual
Page 31
Daimler AG
Issued December 2014
3.4 Process optimisation by data quality management (DQM)
Daimler AG provides an Internet-based data quality management system (DQM) in order to improve the
quality of data. This gives suppliers a very simple and effective way to check their EDI messages for
completeness and correctness immediately after transmission, and to make corrections if necessary.
If it you are not able to create all the delivery note data using standard EDI (e.g. according to VDA 4913),
special transactions can be created and sent in DQM under the navigation item Create delivery notes (600).
Comprehensive information on the DQM application and the delivery note EDI is available on the Daimler
suppliers portal, at
http://daimler.covisint.com
in the Navigation "Collaboration" - "Production and Logistics" in the subject block "Data Communication
with Daimler AG".
DQM hotline:
Telephone: +49-7031-90-77 33 9
E-mail: 050_dataquality@daimler.com
Service hours: Monday to Friday, 6:30 a.m.–7:00 p.m.
3.5 Structure of the VDA 4913 message
Current VDA recommendation:
1st edition of Version 04 (date: March/96).
Data records
Record type Description Notes
711 Header record Identifies the partners. Defines purpose of communication
712 Transport record Transport description
713 Delivery note header
record
Contains delivery note number, unloading point, etc.
714 Delivery note position
record
Describes item and delivery quantity
715 Packing material record Describes packaging. Links EDI to VDA 4902 material label
716 Text record on delivery
note position
Used to indicate the change status
717 Individual package
support record
Optional for external service provider processing DO NOT send to
Daimler
718 Production number
record
Only for JIT/JIS
719 Trailer record Contains the statistics of the data transfer
Chapter 3 Electronic Data
Interchange Manual
Page 32
Daimler AG
Issued December 2014
3.6 Notes on record types and data elements
In order to minimise problems when creating messages, various items are described below.
Header
This is part of the interchange protocol, not the message. The routing of the message into the “right” goods
receipt system takes place through the entry of the filename in the SFID. If you have any further enquiries,
please contact the T-Systems EDI Customer Support (Contact person in Chapter 11.2.1.3)
Example of the header structure for the VDA 4913 message:
3.6.1 Description of fields
3.6.1.1 Record type 711
Record type 711
Identifies the partners. Defines purpose of communication
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 03
Description:
Here must be registered 03
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 AN 9 M Data recipient plant 10005007 for
Sindelfingen
Description:
ID number of the Daimler AG plant that the data is sent to.
MB 050 WES
Char. 6 to 8: Name of the systems
Char. 3 to 5: Plant no. of Daimler (data recipient)
Char .
Chapter 3 Electronic Data
Interchange Manual
Page 33
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 AN 9 M Data sender number 12345678A
Description:
Numeric entry of the supplier number; flush left (no slash). 9th character must be a SPACE if there is only
one supplier location. For multiple supplier locations, the 9th character must contain the assigned index.
Where an index is required for a new supplier location, an application to this effect has to be submitted to the
responsible Daimler AG MRP controller for the material.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 5 M New interchange
number 12345
Description:
ID number for EDI.
Numeric entry, right-justified with leading zeroes. The value must be at least one higher than the
interchange no. OLD. Jumps in number assignments are permitted for data transmissions to Daimler AG.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 6 M Interchange date 190609
Description:
Date of the data transfer.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 AN 9 O Transport data recipient 12345678
Description:
ID number of the forwarding agent to whom the transport data could be sent.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 AN 1 O Storage operator code [Blank]
Description:
Code for the EDI creator, see VDA 4913 recommendation.
[Blank] = space
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 AN 1 O Delivery ID [Blank]
Description:
Code for the type of delivery, see VDA 4913 recommendation.
[Blank] = space
Chapter 3 Electronic Data
Interchange Manual
Page 34
Daimler AG
Issued December 2014
3.6.1.2 Record type 712
Record type 712
Describes the transport
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 03
Description:
Here must be registered 03
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 N 8 M Consignment/load
reference no.
12345678
Description:
Reference number assigned by the sender of the consignment.
A consignment number may not be repeated within the same year. Please note the instructions in Appendix
2 to the VDA specification. Generally speaking, SLB numbers can be assigned either for each unloading
point or for each delivery address.
The SLB number must always be shown in field 8 of the forwarding instruction/waybill according to VDA
4922. It is an access key for the goods recipient.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 AN 3 O Supplier plant AAA
Description:
Supplier’s plant from which the delivery is sent (supplier’s codes used). Must be coordinated with Daimler
AG.
No input is now required here (see record type 711, pos. 03). In a system changeover scenario, as a
transitory arrangement in a multiple locations situation, the supplier no. may be sent as an entry in the Werk
Lieferant (= supplier plant) field. There is no longer any reassignment.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 AN 14 M Freight forwarder Miller
Description:
Name of the company that carries out the transport.
• In the event of own deliveries, enter your company name.
• In the event of collection by Daimler AG, enter D AG collection.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 6 M Freight forwarder
handover date
190609
Description:
Date that goods are loaded or collected at the supplier’s site.
Chapter 3 Electronic Data
Interchange Manual
Page 35
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 4 M Freight forwarder
handover time
1200
Description:
Time at which the goods are planned to be transferred to the freight forwarder.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 7 M Gross weight 0000100
Description:
The gross weight of the consignment refers to the goods, including packaging and/or loading equipment. The
field content must correspond with the weight shown in the waybill. Entered without decimal places.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 N 7 O Net weight 0000050
Description:
Weight of goods including packaging but not loading equipment. Entered without decimal places.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 N 2 M Freight terms code 01
Description:
Information about the freight costs. For the codes used, see VDA 4913 recommendation
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 9 O Transport partner no. 12345678
Description:
ID number assigned by Daimler AG for the transport company in question.
In cases where Daimler is paying the freight costs, the freight forwarder number must be shown here. The
format is as per the supplier number structure. Below is a selection of the transport partners that are
currently allowed.
Chapter 3 Electronic Data
Interchange Manual
Page 36
Daimler AG
Issued December 2014
Area contract freight forwarders
Area Supplier no. Name Country Area code Town Street
01 10412468 Fachspedition Karl
Dischinger GmbH D 79238
Ehrenkirchen-
Kirchhofen
Gewerbepark
Niedermatten
03 17129339 LGI Logistics Group Inter.
GmbH D 72766 Reutlingen Max-Planck-Str. 77
05 17127218 Logtrans Spedition + Log. D 14974 Ludwigsfelde Rudolf-Diesel-Str. 2
06 11320363 DHL Freight GmbG D 50735 Köln Geestemünder Str. 2 -
8
07 16533234 Rhenus Freight Logistics
GmbH & Co. KG D 40721 Hilden Im Hülsenfeld 25
12 10733772 Große-Vehne Speditions
GmbH D 71701 Schwieberdingen
Laiblinger Weg
7
14 17129347 LGI Logistics Group Inter.
GmbH D 72766 Reutlingen Max-Planck-Str. 77
15 10411445 Dachser GmbH & Co. KG D 87700 Memmingen Fraunhoferstr. 15
16 16826158 Hellmann Internationale
Spedition GmbH & Co. KG D 86156 Augsburg Nürnberger Straße 4
17 17825944 Schenker Deutschland AG D 94535 Eging am See Kollmering 10
18 11312105 DHL Freight GmbH D 58708 Menden Meisenweg 26
19 10819662 Rhenus Freight Logistics
GmbH & Co. KG D 40721 Hilden Im Hülsenfeld 25
20 17823840 P.Schockemöhle Logistics D 49439 Mühlen Rienshof 2
21 17408923 Offergeld Logistik GmbH &
Co. OHG D 21502 Geesthacht Am Schleusenkanal 42
22 11616430 Schenker Deutschland AG D 30855 Langenhagen Bayernstr. 38-44
24 18334821 Weck+Poller Spedition
GmbH D 08058 Zwickau Reichenbacher Str. 67
25 16733925 Geis Eurocargo GmbH &
Co. KG D 90451 Nürnberg Hamburgerstr.24
26 16733933 Hans Geis GmbH + Co. D 97616 Bad Neustadt Rudolf-Diesel-Ring
24
51 15551898 Ohl Logistics A/S S 21124 Malmö Hemsögatan 6
52 15401870 Ohl Logistics A/S S 21124 Malmö Hemsögatan 6
53 15470750 Rhenus Logistics Limited GB M17 1QS Trafford Park,
Manchester
2 Westp.Enterpr,
Clarence Ave
57 15520406 Duvenbeck Logistik S.R.O. CZ 33822 Volduchy Volduchy 398
58 17129354 LGI Logistics Group Inter.
GmbH D 72766 Reutlingen Max-Planck-Str. 77
62 11631553 H. Ristelhueber's
Nachfolger D 79761 Waldshut-Tiengen Rheinbrückenstraße 1
67 15402068 Rhenus Logistics S.A. E 20305 Irun (Guipuzcoa) C/Antxotxipi, 6
Terminal Zaisa
67 12597142 Transbidasoa S.A. E 31789 LESAKA
(NAVARRA) C/ ZIOBI, S/N
68 18529578 Rhenus IHG Iberica, S.A. E 08820 Prat de Llobregat PG PRATENSE, CALLE
100, 20
68 15321748 Transbidasoa S.A. E 31789 LESAKA
(NAVARRA) C/ ZIOBI, S/N
70 17129362 LGI Logistics Group Inter.
GmbH D 72766 Reutlingen Max-Planck-Str. 77
72 12542536 Transports Breger S.A. F 53942 St. Berthevin
Cedex 28, rue des chênes
73 12532347 Fercam S.P.A. I 39100 Bozen Marie Curie Str. 2
Chapter 3 Electronic Data
Interchange Manual
Page 37
Daimler AG
Issued December 2014
Parcel delivery services
Number Name Area code Town
10439362 Deutsche Post
10442283 Deutscher Paketdienst 13627 Berlin
10735868 German Logistic Systems 36285 Neuenstein
12006508 TNT-Express 53842 Troisdorf
12010740 Trans-O-Flex 69451 Weinheim
12102349 United Parcel Service 51140 Köln
12105979 United Parcel Service 41456 Neuss
For suppliers with “ex works” purchasing conditions, “UPS” should be used as the parcel delivery service (for
more details see Mercedes-Benz Special Terms No. 29 – “Shipment of goods for Daimler AG”). In addition to
the partners listed above, there are some other partner numbers, particularly for direct-contract freight
forwarders. For instructions on the numbers to be used, contact the recipient plant.
Chapter 3 Electronic Data
Interchange Manual
Page 38
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 N 2 M Means of transport
code
02
Description:
This code refers to the following means of transport numbers, thereby specifying which type the following
entered number is. For the codes used, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 15 AN 14 M Means of transport no. 471112345
Description:
The means of transport number depends on the selected means of transport code.
• If KFZ-Zeichen (registration number) was selected in the Transportmittelinformations-Schlüssel (means of
transport code) field, enter the registration number of the vehicle. If you do not know it, enter “LKW” (truck).
• If you selected a different means of transport code, the following applies for the code:
- General cargo number -> the assigned general cargo number
- Express delivery number -> the express delivery number assigned by the parcel
or courier service
- Railway carriage number -> the number of the railway carriage
- Post parcel -> the parcel number assigned by the postal service
- Parcel service -> the parcel number assigned by the parcel service
- Bordereau/loading list number -> the bordereau number assigned by the forwarding agent
If you do not know the relevant number when entering the data, enter “9”.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 16 AN 1 O Means of transport
information code
(code for pos. 17)
2
Description:
If Bordero-/Ladelistennummer (bordereau/loading list number) was entered in the Transportmittel-Nummer
(mode of transport number) field, an entry is required here. The Bordero number must be coordinated with
the appropriate carrier
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 17 AN 8 O Means of transport
information (content as
per code in pos. 16)
HH-DD123
Description:
The mode of transport information depends on the selected code:
If KFZ-Kennzeichen (registration number) was selected in the Transportmittelinformations-Schlüssel
(means of transport information code) field, you have to enter the registration number of the vehicle.
If Postleitzahl (post code) was selected in the Transportmittelinformations-Schlüssel (means of
transport information code) field, you have to enter the post code of the address of the shipping plant.
Chapter 3 Electronic Data
Interchange Manual
Page 39
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 18 N 6 O Target arrival date 190609
Description:
Date on which the goods are to be delivered to Daimler AG.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 19 N 4 O Target arrival time 0700
Description:
Time at which the goods are planned to arrive at the relevant Daimler AG plant. If specifying a time slot for
the arrival, enter the start of the time slot in this field (example: for 07:00 a.m.–08:00 a.m., enter 0700 here).
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 20 N 3 O Load metres 093
Description:
Specifies how many metres of the loading deck are occupied (one decimal place).
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 21 N 1 O Truck type 1
Description:
Information about the truck type.
3.6.1.3 Record type 713
Record type 713
Contains delivery note number, unloading point, etc.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 03
Description:
Here must be registered 03
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 N 8 M Delivery note no. 12345678
Description:
ID number that the supplier assigns to a delivery note.
You can select any number here. However, the number must not be repeated within the same calendar year.
Group together all delivery notes for one unloading point under a single consignment number.
Chapter 3 Electronic Data
Interchange Manual
Page 40
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 AN 5 M Unloading point 123
Description:
Unloading point specified in the order. Digits 1–3: numerical, digit 4: alphanumerical.
For detailed call-offs, the unloading point can be 5-digit.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 2 M Delivery method 02
Description:
Information about the type of forwarding. For the codes used, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 12 M Contract/
PO number
9
Description:
Purchase order or contract number specified in the order. If no information is entered, enter “9” here.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 N 2 O Transaction code 40
Description:
If only EDL is used, fill the field according to the selection with the code “40” (see item 3.10).
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 N 3 M Customer plant 050
Description:
The customer’s plant that is to be supplied. The codes to be used must be coordinated with Daimler AG.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 12 N 8 O Consignment 12345678
Description:
Number of the delivery note with which the goods were sent by Daimler AG to the supplier.
In the case of normal deliveries, no information is entered here.
Field only to be filled when returning consignment material.
Chapter 3 Electronic Data
Interchange Manual
Page 41
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 9 O Goods recipient
number
12345678
Description:
ID number that the customer assigns to a goods recipient.
In the case of normal deliveries, no information is entered here.
This field is only relevant for deliveries to third parties and external service provider processing.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 16 AN 9 O Supplier no. 12345678
Description:
ID number that the customer assigns to supplier (only in the case of external service provider processing).
In the case of normal deliveries, no information is entered here.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 17 AN 14 O Point of
consumption
12345
Description:
Specifies the point in the customer’s plant where the goods is consumed.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 18 N 4 O Call-off number 1234
Description:
Number of the call-off for individual orders.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 19 AN 6 O Ordering party 740
Description:
Ordering party’s index.
Chapter 3 Electronic Data
Interchange Manual
Page 42
Daimler AG
Issued December 2014
3.6.1.4 Record type 714
Record type 714
Describes item and delivery quantity
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 03
Description:
Here must be registered 03
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 AN 22 M Customer part no. A2206601234
Please consider there is a new detailed description in the Part number manual!
The “Part number manual” is available at the Daimler Supplier Portal
http://daimler.covisint.com in the navigation "Collaboration & Tools" in the subject "Downloads"
Note: To each Customer part number the partial Weight must be entered. The entry is made in the record
type 716, pos. 05, see chapter 3.6.1.6.
Description:
Daimler AG part number is specified in the purchase order.
alid Daimler AG part numbers generally consist of a letter (“A”, “B”, “H”, “Y” or “T” (for new containers)) and
8–11 numbers.
No blank spaces or special characters.
Exceptions: part numbers with supplementary codes ES1 and ES2
Example 1: Daimler part number without supplementary code
Character Customer
part number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Entry Daimler
part number A 1 2 4 4 0 1 1 2 6 1 S P A C E
Example 2: Daimler part number for “coloured” parts with indicator letter A and supplementary code
(ES1), ES2
Character Customer
part number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Entry Daimler
part number A 1 2 4 4 0 1 1 2 6 1 0 0 0 0 9 0 6 1
Example 3: Daimler part number for indicator letter A and supplementary code ES1
Character Customer
part number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Entry Daimler
part number A 1 2 4 4 0 1 1 2 6 1 8 0 0 0
Example 4: Standard entry where Daimler part number not available
Chapter 3 Electronic Data
Interchange Manual
Page 43
Daimler AG
Issued December 2014
There may be particular cases where a Daimler part number does not exist (e.g. for non-productive material).
However, as this is a required field according to the VDA recommendation, a dummy part number is entered:
View:
Character 1: Q (indicator letter)
Char. 2–5: TEXT (keyword)
Record type 716 (text record) is also to be sent. The item description is to be provided in this record.
Character Customer
part number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Entry Daimler
part number Q T E X T
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 AN 22 M Supplier part no. A2206601234
Description:
Supplier’s part number or item designation. If no supplier part number is available, the customer’s part
number can be specified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 N 3 M Country of origin 004
Description:
See list of countries for foreign trade statistics.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 13 M Customer delivery
quantity
0000010000000
Description:
Specifies the customer’s delivery quantity (with up to three decimal places).
Right-justified entry with leading zeroes.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 AN 2 M Customer quantity unit ST
Description:
Specifies the customer’s unit of quantity.
For the codes used, see VDA 4913 recommendation.
Additional codes used specifically for Daimler AG are summarized in the following table:
Code Description (German) Description (English)
16 Blatt sheet
17 Packungen packing
18 Pack pack
Chapter 3 Electronic Data
Interchange Manual
Page 44
Daimler AG
Issued December 2014
19 Rollen rolls
21 Spulen spooling
23 Karton carton
26 Dosen cans
32 Verpackungseinheit packing unit
36 Kanister canister
37 Gebinde bundle
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 13 O Supplier delivery
quantity
0000010000000
Description:
Specifies the delivery quantity (with up to three decimal places), if this is different to the customer’s delivery
quantity. Right-justified entry with leading zeroes.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 AN 2 O Supplier unit of quantity KG
Description:
Specifies the supplier’s unit of quantity if this is different to the customer’s unit of quantity. For the codes
used, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 N 3 O VAT rate 190
Description:
Used, by arrangement, for credit note procedure (one decimal place).
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 1 O Call-off code [Blank]
Description:
Information about the type of delivery.
For the codes used, see VDA 4913 recommendation.
[Blank] = space
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 AN 15 O Batch no. CH12345678
Description:
ID number that the supplier assigns to a batch.
Field Field Field Optional/Mandatory Designation Example of an entry
Chapter 3 Electronic Data
Interchange Manual
Page 45
Daimler AG
Issued December 2014
format length
Pos: 15 AN 1 M Usage code S
Description:
Information about the type of usage.
For the codes used, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 16 AN 8 O Hazardous
materials code
Description:
Specification from the Directive of Transporting Hazardous Materials. Digits 1–4: class, digits 5–6: section,
digits 7–8: letter.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 17 AN 1 M Preference status G
Description:
Information about the preference status in code form, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 18 AN 1 M Dutiable goods [Blank]
Description:
Information about whether the goods are dutiable.
For the codes used, see VDA 4913 recommendation.
[Blank] = space
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 21 AN 2 M Version change
code
[Blank]
Description:
Specifies the version code for changed parts in the context of supplying the development area.
Note the following when entering data:
The drawing geometry level, Q/E status, pre-production test batch and KEM fields can only be filled if the
following was selected in the version change code field:
G T: first regular delivery of changed part
[Blank] T: each subsequent delivery of the changed part
Only specify the version change code if requested to do so by Daimler AG and/or the code was specified in the
purchase order. If you have any questions regarding this subject, please contact your MRP controller.
[Blank] = space
3.6.1.5 Record type 715
Chapter 3 Electronic Data
Interchange Manual
Page 46
Daimler AG
Issued December 2014
Record type 715
Describes packaging. Links EDI to VDA 4902 material label
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 03
Description:
Here must be registered 03
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 AN 22 M Cust. packing
material no.
2032
Description:
Use the number specified in the purchase order for a packing material or a container here. In the case of
disposable packaging, use a code according to the VDA recommendation 4913, Appendix 10.
Daimler codes are 4 - 7 - digit.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 AN 22 M Supplier packing
material no.
K123
Description:
Supplier’s number or designation for a packing material or container.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 N 13 M No. of packing
materials
20
Description:
Specifies the number of packing material in question.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 13 O Filling quantity 100
Description:
Specifies the filling quantity per container (with a maximum of 3 decimal places).
For certain processes, this field can be mandatory.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 AN 9 O Package number
from
00000001
Description:
The number must not be repeated within the same year.
For certain processes, this field can be mandatory.
Chapter 3 Electronic Data
Interchange Manual
Page 47
Daimler AG
Issued December 2014
For several packages with the same part number:
a) For an unbroken ascending sequence of package numbers, enter the lowest value in this field. The
highest value should be entered in the Package number to (Packstück-Nummer bis)
(pos. 09) field.
b) If there is not an unbroken ascending sequence of package numbers, a separate record type 715
must be sent for each package. In this situation there is no entry as per the above description in the
Package number to (Packstück-Nummer bis) (pos. 09) field.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 AN 9 O Package number
to
00000019
Description:
The number must not be repeated within the same year. If this element is used, there must be an an
unbroken ascending number sequence.
Chapter 3 Electronic Data
Interchange Manual
Page 48
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 N 12 O Packaging
dimensions
100020000800
Description:
Specified in millimetres.
Digits 97–100 length
Digits 101–104 width
Digits 105–108 height
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 N 1 O Stacking factor 2
Description:
Specifies the permissible stackability of the unit designated in the packaging type. Code form:
1 = can be stacked singly
2 = can be stacked doubly, etc.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 1 O Label ID S
Description:
Barcode ID for the material label.
For the codes used, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 AN 1 O Packaging ID M
Description:
Describes the type of packaging.
For the codes used, see VDA 4913 recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 15 AN 1 O Ownership ID O
Description:
Information about the packaging owner.
For the codes used, see VDA 4913 recommendation.
Chapter 3 Electronic Data
Interchange Manual
Page 49
Daimler AG
Issued December 2014
3.6.1.6 Record type 716
Record type 716
Text record or indication of change status
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 02
Description:
Here must be registered 02
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 AN 40 O Position text 1,
delivery designation
Screws for table
Description:
Text area that can be used to indicate any additional information.
The position text becomes a mandatory field if the relevant entry was made in the “Version change key” field
(Geänderte-Ausführung-Schlüssel) (record type 714, pos. 21). In this case, note the following:
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 3.1 AN 1 M ZGS (drawing geometry
state)
Z
Description: Designation indicator “Z” for ZGS
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 3.2 N 3 M Drawing geometry state 001
Description:
Design change status or drawing geometry state.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 3.4 AN 1 M Q or E status E
Description:
Q or E status has to be specified here:
Q = quality status
E = development status
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 3.5 AN 8 M Q/E status 12345
Description:
Information about the Q/E status
Chapter 3 Electronic Data
Interchange Manual
Page 50
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 3.6 AN 10 M Pre-production test batch B1205
Description:
Specific number of vehicles in a start-up project that have the same part revision level. The pre-production
batch test can be taken from the purchase order, if present.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 3.9 AN 16 M KEM KEM123054
Description:
The design implementation notice can be taken from the purchase order, if present.
Additional rule
applicable for transferring revision level information and MTC deliveries for the passenger car plants of the
Mercedes-Benz and Maybach brands, as well as the Berlin-Marienfelde, Ludwigsfelde and Düsseldorf plants
Note:
For all parts, text field 1 of record type 716 is to be filled with the data elements described in Table 3.6.1.6.
Additional Rules.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 5 AN 13 M Text 3 GEW0012310000
Description:
In the Data creation the article weight has to betransferred in field as shown.
The information of the inquiry criterion „GEW “must take place in the position 86-88. The Weight can be
entered in the position 89 – 98 (10 digits including 4 decimal places).
3.6.1.7 Record type 717
Record type 717
Individual package record
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Description:
NOT to be sent to Daimler AG.
3.6.1.8 Record type 718
Record type 718
Production number record
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Chapter 3 Electronic Data
Interchange Manual
Page 51
Daimler AG
Issued December 2014
Description:
Only for JIT/JIS (see item 3.9).
3.6.1.9 Record type 719
Record type 719
Trailer record
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Description:
Contains the statistics of the data transfer.
Chapter 3 Electronic Data
Interchange Manual
Page 52
Daimler AG
Issued December 2014
Table 3.6.1.6. Additional Rules Item Data element Data content Start-
up/
series
O/M
MTC
O/M
BYT
E
From/to Description
1 Record type 716 M M 3 1–3 Constant, “716”
2 Vers. No. 02 M M 2 4–5 Entry =02
3 Text 1
3.1 ZGS indicator Z M M 1 6 Designation indicator “Z” for ZGS
3.2 ZGS (drawing
geometry
state)
ZGS (drawing
geometry state)
M M 3 7–9 Indication of the delivered ZGS, e.g. 003
3.3 E/Q status
indicator
E or Q M O 1 10 If an E/Q status is sent, enter this
indicator accordingly
Status indicator for E or Q status
Entry: E – for E status
Q – for Q status
3.4 E/Q status E or Q status M O 3 11–13 Entry of E or Q status.
e.g. 003
3.5 Pre-
production
test batch
indicator
B O O 1 14 Indicator for pre-production test batch.
If pre-production test batch data is being
sent, enter a “B” in this field.
3.6 Pre-
production
test batch
Pre-production
test batch
O O 3 15–17 Entry of the relevant pre-production test
batch
3.7 Purchase
order position
indicator
P * M 1 18 Entry of the indicator P
3.8 PO pos. Purchase order
position
* M 3 19–21 Indication of purchase order position for
the respective consignment
3.9 KEM Engineering
change notice
M O 13 22–34 Indication of the engineering change
notice specified in the purchase order
under KEM (MTC) or as indicated in the
drawing (plants)
3.10 Version
number Version
number
* O 11 35–45 Indication of the version number specified
in the order under “Vers-Nr.”
(left-justified)
4 Text 2 *
4.1 Veh. no.,
sub-assembly
no.
Vehicle or
sub-assembly
number
* O 8 46–53 Indication of vehicle or sub-assembly
number as specified in the purchase order
under vehicle no. (Fzg-Nr.)/sub-assembly
no. (Aggregate-Nr.)
4.2 FINAS ID no. Finas ID no. or supplier ID no.
* O 26 54–79 Indication of the Finas ID number as
specified in the purchase order or the
supplier ID no.
4.3 KE Indicator for
Finas ID no.
field
* O 1 80 Specification of the indicator for Finas ID
no.
F- for Finas ID no.
L- for supplier ID no.
4.4 * 81–85 empty
5 Text 3 *
5.1 Drawing date Drawing date * O 6 86–91 Indication of drawing date for ZGS status;
format YYMMDD
5.2 Project Project * O 10 92–101 Indication of the project referenced in
purchase order
5.3 Notes text
indicator
A * O 1 102 “A” indicates general notes text
5.4 Notes text Notes text * O 23 103–125 A- General notes text
All fields marked with * apply only to MTC deliveries.
Chapter 3 Electronic Data
Interchange Manual
Page 53
Daimler AG
Issued December 2014
3.7 Special cases for the delivery note and transport data message
3.7.1 Corrections
If content corrections are required after the data have been sent, the changes have to be made in DQM (see
item 3.4).
3.7.2 EDI resend capability
It must be possible to resend EDIs. We expect this capability for the three most recent communications for
each recipient.
3.7.3 EDI problems
In a few very rare cases it may be impossible to send the delivery note data (e.g. special trips, computer
failure, line problems, reception problems, etc.).
In this case, delivery notes can be created and sent in DQM under the navigation item Create delivery notes
(600) (see item 3.4).
If this is not possible, all copies of the delivery note and waybill must be clearly marked (with a stamp if
possible) (see Emergencies).
3.7.4 Emergencies
If we do not receive VDA 4913 messages, it is important to ascertain the cause for this problem. Internal
follow-up is ensured via EDIS enquiries. A contact name must be provided for follow-up enquiries with the
supplier.
During brief EDI malfunctions it is possible to enter the data manually in the target system. However, this
capacity is limited and it incurs extra costs for us which may be passed on to the supplier.
Input documents are the delivery papers carried by the driver (delivery note or EDI goods accompanying slip).
3.7.5 Sample deliveries
The “sample” identification must be entered in the EDI for sample deliveries.
For consignments according to VDA 4913, Y = Sample must be entered in the record type 714 under position
106.
For consignments made over the Internet (DQM), “Sample” must be selected in the application key field in
the delivery note position data.
3.7.6 Return of empties
Customer Articel number: QLEERGUT
Delivery Quantity: 1
Quantity units: Pieces
Customer packaging number: the specific package number (e.g. 9040)
Number of packaging items: The number of items being returned
Chapter 3 Electronic Data
Interchange Manual
Page 54
Daimler AG
Issued December 2014
3.7.7 Central loading unit for deliveries via courier service
For the deliveries via a courier service a central loading unit is needed (see VDA 4913 example 3a). In order
to guarantee this with the dispatch of individual small load carrier (so far no regular pallet is sent),
additionally a dummy pallet in the delivery notes must emerge for the packing code of the small load carrier
(see VDA 4913 record type 715, pos. 03, columns 6-27) at first position. For this pallet the packing code
“0000BUN” should be used. This dummy pallet must be provided additionally with a master label “M” (see
VDA 4913 record type 715, pos. 13, column 125). In addition, this master label must be printed and be
attached on the small load carrier. The storage of the sent goods can take place using this master label.
For a better understanding an example is in the following specified. This example exclusively refers to the
record type 715, pos. 02, pos. 03 and pos. 13.
Record type version no. packing code label
715 03 0000BUN M
715 03 4315 S
Please pay attention to the correct information and order of the load carriers. The master label and/or the
“pallet” must be listed always at first position. Please use the DQM (see Chapter 3.4) in order to examine and
if necessary to correct your data before the goods get in storage.
3.8 Contact person for problems with the EDIS communication computer:
T-Systems EDI Customer Support (Contact person in Chapter 11.2.1.3)
3.9 Tips and useful information
Demarcation of consignments <-> link to waybill
The following must be shown on the waybill/forwarding instruction:
Field 2: Supplier no. (from record type 711)
Field 8: Consignment/load ref. no. (SLBN from record type 712)
Field 10: Forwarding agent no. (from record type 712)
Field 18: Deliverynote number(s) (from record type 713)
And for “direct-contract” transport consignments, also the following:
Field 13: Bordereau no.
These data elements are:
a) Access keys at the truck management points at Daimler plants for locating EDI data.
b) Key terms for freight billing.
Important notes:
Always ensure that the EDI data (demarcation as per record type 712) correspond exactly to the
loading scope.
Multiple consignment numbers on the same waybill are not permitted in any circumstances.
Chapter 3 Electronic Data
Interchange Manual
Page 55
Daimler AG
Issued December 2014
VDA specification 4922 permits the issuing of waybills by unloading point or by shipping address (a
similar arrangement applies for the SLB no.). This is to be agreed bilaterally between the parties.
Rules for Daimler AG:
For groupage consignments via our area contract freight forwarders: waybill for each unloading
point
For other transport scenarios:
waybill for each delivery address
So for the Sindelfingen plant address, for example, separate waybills are required for its outposts, i.e.
Böblingen-Hulb, etc.
Chapter 3 Electronic Data
Interchange Manual
Page 56
Daimler AG
Issued December 2014
3.10 Transport management
Generally, the VDA 4913 specification applies. Deviations from the specification, with regard to transport
management, are described in this section.
3.10.1 Data transmission
The data sender is to transmit the data by no later than 2 hours before loading. This is essential to ensure that
the driver can download the data for the packages to be collected (electronic target loading list) on their
mobile phone.
3.10.2 Notes on record types and data elements
The sequence of record types must be exactly as per the VDA specification. Additionally, the changes
described below must be complied with.
Record type 712
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 9 M Transport partner
no.
12345678
Description:
Enter the freight forwarder no. (max. 9 char.) for the freight forwarder contracted. This number is assigned by
Daimler AG.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 N 2 M Means of
transport code
02
Description:
Constant value: 02
This indicates that the value in the following position 15 (means of transport number) is to be interpreted as a
bordereau number.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 15 AN 14 M Means of
transport no.
30141234
Description:
Char. 1–4: manifest header record, specified to freight forwarder by Daimler AG.
Char. 5–8: assigned by freight forwarder for each truck/transport unit (generally serial no.).
Please agree on these numbers in advance with the freight forwarder (e.g. what numbers are to be assigned
for which truck/transport unit?).
This field is alphanumeric. Complete in flush left format. Since the bordereau number also has
8 characters, only characters 78–85 should be filled; the remaining characters, 86–102, should be left empty.
Chapter 3 Electronic Data
Interchange Manual
Page 57
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 16 AN 1 M Means of transport
information code (code
for pos. 17)
2
Description:
Constant value: 2
This indicates that the value in the following position 16 (means of transport information) is to be interpreted
as the official number plate of the transport vehicle (tractor unit).
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 17 AN 8 M Means of transport
information (content as
per code in pos. 16)
HH-DD123
Description:
Official number plate of transport vehicle (tractor unit).
Ask the freight forwarder for the official plate number.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 18 N 6 O Target arrival date 190609
Description:
Date specified by Daimler for arrival of the consignment. Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 19 N 4 O Target arrival time 1001
Description:
Time slot agreed between the freight forwarder and Daimler AG for arrival of the truck at the plant. Format:
HHMM
Please consult with the freight forwarder (for what time does the truck/transport unit have a time slot?) and
send this information with every EDI. The notified target arrival time must correspond to the time slot
number and therefore the start of the time slot. Example: time slot 10.01–11.01 a.m. = time slot number 1001.
Record type 715
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 N 13 M No. of packing
materials
0000000000020
Description:
In this field, enter the number of packages of each type. The entry is to be flush right, with leading zeroes and
without decimal places.
If the number of packages is > 1, the package numbers are to be in an unbroken ascending sequence (3.9.2.1).
The packing material record will then contain several packages with the same part number. This compressed
information has to be broken down by Daimler to generate the target loading list.
If the number of packing materials = 1, then the packing materials record refers to a single package (3.9.2.2).
Chapter 3 Electronic Data
Interchange Manual
Page 58
Daimler AG
Issued December 2014
3.10.2.1 Multiple packages
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 AN 9 M Package number
from
000000001
Description:
Number of the first package; this number must not be repeated within the same year.
The field is to be filled left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 AN 9 M Package number
to
000000019
Description:
Number of the last package; this number must not be repeated within the same year.
The field is to be filled left-justified.
3.10.2.2 Single package
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 AN 9 M Package number
from
000000001
Description:
Number of the first package; this number must not be repeated within the same year.
The field is to be filled left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 AN 9 O Package number
to
000000001
Description:
This field must contain either the same number as for “package number from”, or be left empty.
The field is to be filled left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 1 M Label ID S
Description:
Barcode ID for the material label.
For the codes used, see VDA 4913 recommendation.
G = Mixed package (with sub-packages and different part numbers)
M = Master label (with sub-packages and the same part numbers)
S = Single label (1 package)
Chapter 3 Electronic Data
Interchange Manual
Page 59
Daimler AG
Issued December 2014
3.11 Generation by JIT and JIS suppliers (VDA 4913/JIT)
The requirements are generally the same as per the basic VDA 4913 message as described in the preceding
pages. The differences for message generation by JIT suppliers are described below.
3.11.1 Short description of JIT and JIS suppliers
A material call-off (VDA 4916) is required for each production number.
Delivery is based on picking in production number sequence. VDA 4913 has production numbers shown in
record type 718. The following special features need to be taken into account in the EDI:
3.11.2 Notes on record types and data elements
The sequence of record types must be exactly as per the VDA specification.
Record type 711
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 AN 1 M Delivery ID J
Description:
Code for the type of delivery, see VDA 4913 recommendation.
J = JIT delivery
Record type 714
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 1 M Call-off code P
Description:
Information about the type of delivery. P = just-in-time call-off (according to VDA 4916 recommendation)
Record type 718
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 04 and
the
following
AN 10 M Production
number 1
Description:
The production numbers contained in the consignment must be shown here. Several 718 record types without
change of group are permitted.
Chapter 3 Electronic Data
Interchange Manual
Page 60
Daimler AG
Issued December 2014
3.12 Triangular traffic
In the triangular traffic process, the data sender has to specify the following additional fields in VDA 4913.
The process should only be used after consultation with the relevant Daimler AG contact persons and with the
goods recipient.
3.12.1 Data sender via VDA 4913
Important:
File name the file name MB050DRV must be used instead of MB050WES.
Record type 711
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 AN 1 M Delivery ID H
Description:
The entry “H” is essential here in order that the data can be identified as triangular traffic.
Record type 713
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 9 M Goods recipient
number
12345678A
Description:
ID number that the customer assigns to a goods recipient. The ordering party/controller must inform you of
the goods recipient number.
Chapter 3 Electronic Data
Interchange Manual
Page 61
Daimler AG
Issued December 2014
3.12.2 Data sender via Edifact
Important:
File name the file name MB050DRVE must be used instead of MB050DESA.
Edifact segment BGM.1225
VDA
element
Field
format
Field
length
Optional/Mandatory Designation Example of an entry
71111 AN 1 M Delivery ID H
Description:
The entry “H” is essential here in order that the data can be identified as triangular traffic.
Edifact segment NAD.3039 (NAD.3035= DP)
VDA
element
Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 AN 9 M Goods recipient
number
12345678A
Description:
ID number that the customer assigns to a goods recipient. The ordering party/controller must inform you of
the goods recipient number.
3.12.3 Data sender via DQM
There is a detailed manual available for deliveries to third parties via DQM. You can find it in DQM (see
Chapter 3.4) in the online help.
3.12.3.1 Further tracking of the consignment
The consignment can be tracked further in DQM under the navigation item “Recording delivery notes (600)”.
See item 3.4 for information about DQM.
o The data is processed in the deliveries to third parties archive.
o For further processing, see the manual (online help): Deliveries to third parties – data
sender
3.12.3.2 Confirmation of the data by the goods recipient
The data must be confirmed in DQM under the navigation item “Recording delivery notes (600)”. There is a
detailed manual for this function. You can find it in DQM (see Chapter 3.4) in the online help.
Chapter 3 Electronic Data
Interchange Manual
Page 62
Daimler AG
Issued December 2014
Generation by EDL (VDA 4913/EDL)
The requirements are generally the same as per the basic VDA 4913 message as described in the preceding
pages. The differences for message generation by external service providers are described below.
3.12.4 Brief description
Owing to shared storage arrangements between suppliers and Daimler AG, at some plant locations there are
storage facilities close to the plant operated by external service providers (EDL).
EDI generation by external service providers is described in Chapter 3 of the VDA recommendation. Other
points are agreed bilaterally between the parties when the contract is signed.
The warehouse stock belongs to the supplier. When a call-off is issued for the material, the EDL, acting on the
supplier’s instructions, prepares the delivery note data in VDA 4913 format. Stock data are also transferred,
again with VDA 4913 and a special procedure.
3.12.5 Notes on record types and data elements
Record type 711
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 AN 1 M Storage operator
code
1
Description:
Code for the EDI creator, see VDA 4913 recommendation.
“1” = EDI generated by EDL.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 AN 1 M Delivery ID [Blank]
Description:
Code for the type of delivery, see VDA 4913 recommendation.
[Blank] = Stock is transferred in delivery quantity 2 (record type 714).
1 = No stock is transferred in delivery quantity 2 (record type 714).
Record type 712
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 6 M Freight forwarder
handover date
190609
Description:
Date that goods are loaded or collected at the supplier’s site.
This field also has to be completed for transaction type 35. In this case the field content refers to the time the
EDI was generated.
Chapter 3 Electronic Data
Interchange Manual
Page 63
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 4 M Freight forwarder
handover time
1200
Description:
Time at which the goods are planned to be transferred to the freight forwarder.
This field also has to be completed for transaction type 35. In this case the field content refers to the time the
EDI was generated.
Record type 713
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 AN 1 O Storage operator
code
40
Description:
For delivery note data, enter 40. For stock data, enter 35.
No other entries are permitted for messages to Daimler AG.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 16 AN 9 O Supplier no. 12345678
Description:
The delivery location index may be entered at character 9. Note that within a consignment as per record type
712, for a given supplier it is always the delivery location of the 1st record of record type 713 that is used.
If multiple delivery locations for one supplier are shown in an EDI, initiate a change of group with a new
record type 712.
Record type 714
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 13 O Supplier delivery
quantity
0000010000000
Description:
For transaction type 40, also enter the current stock level at this point, according to the field content in record
type 711, char. 59.
Chapter 3 Electronic Data
Interchange Manual
Page 64
Daimler AG
Issued December 2014
3.13 Generation by EDL (external service providers) (VDA 4913/EDL)
The requirements are generally the same as per the basic VDA 4913 message as described in the preceding
pages. The differences for message generation by external service providers are described below.
3.13.1 Brief description
Owing to shared storage arrangements between suppliers and Daimler AG, at some plant locations there are
storage facilities close to the plant operated by external service providers (EDL).
EDI generation by external service providers is described in Chapter 3 of the VDA recommendation. Other
points are agreed bilaterally between the parties when the contract is signed.
The warehouse stock belongs to the supplier. When a call-off is issued for the material, the EDL, acting on the
supplier's instructions, prepares the delivery note data in VDA 4913 format. Stock data are also transferred,
again with VDA 4913 and a special procedure.
3.13.2 Notes on record types and data elements
Record type 711
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos.: 10 AN 1 M Storage operator
code
1
Description
Code for the EDI creator, see VDA 4913 recommendation.
“1“ = EDI generated by EDL.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos.: 11 AN 1 M Delivery ID [Blank]
Description
Code for the type of delivery, see VDA 4913 recommendation.
[Blank] = Stock is transferred in delivery quantity 2 (record type 714).
1 = No stock is transferred in delivery quantity 2(record type 714).
Record type 712
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos.: 06 N 6 M Freight forwarder
handover date
190609
Description:
Date that goods are loaded or collected at the supplier's site.
This field also has to be completed for transaction type 35. In this case the field content refers to the time the
EDI was generated.
Chapter 3 Electronic Data
Interchange Manual
Page 65
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 4 M Freight forwarder
handover time
1200
Description:
Time at which the goods are planned to be transferred to the freight forwarder.
This field also has to be completed for transaction type 35. In this case the field content refers to the time the
EDI was generated.
Record type 713
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos.: 10 AN 1 K Storage operator
code
40
Description
For delivery note data, enter 40. For stock data, enter 35.
No other entries are permitted for messages to Daimler AG.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos.: 16 AN 9 K Supplier no. 12345678
Description:
The delivery location index may be entered at character 9. Note that within a consignment as per record type
712, for a given supplier it is always the delivery location of the 1st record of record type 713 that is used.
If multiple delivery locations for one supplier are shown in an EDI, initiate a change of group with a new
record type 712.
Record type 714
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos.: 08 N 13 K Supplier delivery
quantity
0000010000000
Description:
For transaction type 40, also enter the current stock level at this point, according to the field content in record
type 711, char. 59.
3.14 Confirmation of receipt as per VDA4913 VA30 mod
The requirements are generally the same as per the basic VDA 4913 message as described in the preceding
pages. The differences for message generation for the confirmation of receipt as per VDA4913 VA30 mod
external service providers are described below.
Record type 711
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Chapter 3 Electronic Data
Interchange Manual
Page 66
Daimler AG
Issued December 2014
Pos: 03 A 9 M Data recipient no. 10005007 for
Sindelfingen
Pos: 04 A 9 M Data sender no. EDL supplier no.
Pos: 11 A 1 K Delivery ID Fix = "M"
Record type 713
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 N 2 K Transaction code Fix = "30"
Pos: 16 A 9 M Supplier no. Supplier number of
the original supplier
Record type 714
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 13 M Customer delivery
quantity
"0000000060000"
Description:
Enter the delivery quantity (up to three decimal points) of the customer.
Legally-binding entry with leading zeros.
Record type 714
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 13 K Supplier delivery
quantity
"0000010000000"
Description:
Enter the delivery quantity (with up to three decimal spaces), if it differs from the quantity of the customer.
Legally-binding entry with leading zeros.
Only process if pos: 19 = "T": In pos: 08 you can see the (total) position quantity received to date as incoming
parts, while in this case delivery quantity 1 indicates the expected total quantity.
A position is closed:
either pos: 019 = blank
or pos: 019 = "T" and customer delivery quantity = supplier delivery quantity.
Record type 714
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 19 A 1 M Partial goods receipt
ID
"T"
Description:
Blank = Received goods position has been completely processed.
Chapter 3 Electronic Data
Interchange Manual
Page 67
Daimler AG
Issued December 2014
"T" = Received goods position is not yet complete (i.e. partial receipt), there will be further partial
receipts of goods.
I.e.: as long as the partial goods receipt ID is set to "T", further partial goods receipts or a closing receipt of
goods (pos: 019 = blank) are expected.
Chapter 4 Electronic Data
Interchange Manual
Page 68
Daimler AG
Issued December 2014
Goods accompanying slip according to VDA 4912
Content overview
4 Goods accompanying slip according to VDA 4912 69
4.1 Brief description of VDA 4912 69
4.2 Layout sample 69
Author of Chapter 4
Ms Pischka
SC/SET department
Sindelfingen plant
050_dqm@daimler.com
Chapter 4 Electronic Data
Interchange Manual
Page 69
Daimler AG
Issued December 2014
4 Goods accompanying slip according to VDA 4912
4.1 Brief description of VDA 4912
The increasing use of the delivery note and transport data EDI according to VDA recommendation 4913
between suppliers and automotive producers means that we are moving closer to the day when delivery note
forms will no longer be required.
The EDI goods accompanying slip can be regarded is the paper form of the EDI according to VDA 4913.
Even with the use of an EDI system, a hard-copy document is still required for the physical goods receipt
process. The EDI goods accompanying slip is an effective way to reduce the volume of paper documents.
Further cost savings for forms are achieved by the use of blank paper.
This presentation of delivery information in condensed form at unloading point level (for multiple delivery
note nos.) is an extract from the data fields and content from the EDI message according to VDA 4913.
The EDI goods accompanying slip also provides a backup so that processing can continue during EDI
outages. In this case the slip is used as a record for data entry by the recipient of the goods.
An EDI message communicating delivery note data according to VDA 4913 is also expected in the case of
goods shipment with a parcels service operator. In this case the EDI goods accompanying slip should be
placed in the pouch provided for accompanying documents.
If this is not possible for process management reasons, it is sufficient to enter the consignment loading
reference no. on the delivery note.
If this is also not possible, the absolute minimum requirement is to enter the letters “EDI”.
4.2 Layout sample
Chapter 5 Electronic Data
Interchange Manual
Page 70
Daimler AG
Issued December 2014
Material label according to VDA 4902, version 4
Content overview
5 Material label according to VDA 4902, version 4 71
5.1 Special notes on usage 71
5.2 Layout specimen for standard label 72
5.3 Layout sample for small label (for small containers) 72
Author of Chapter 5
Mr Krodel
Sindelfingen plant
Department: SC/SET
Phone +49(0) 70 31- 90-26 53
Harald.Krodel@daimler.com
Chapter 5 Electronic Data
Interchange Manual
Page 71
Daimler AG
Issued December 2014
5 Material label according to VDA 4902, version 4
VDA has developed a standard material label. This document is also recommended by ODETTE.
New techniques for Goods Receipt operations have made barcodes particularly important. Under the package
system, the barcode is scanned. A comparison with the 4913 EDI is run in the background. The quality of the
barcode is crucial.
5.1 Special notes on usage
Attachment
For occupational safety reasons and also for ease of disposal of old labels, only use plastic clips or spots of
glue.
Gluing over the entire surface is not permitted. This can make plastic containers unusable. In such cases, we
have to pass the recycling, replacement and repacking costs on to the party causing the problem.
Attachment location, number of material labels see table below.
Any other attachment locations must be agreed on in writing by the supplier and recipient.
Font size
The unloading point and part number must be shown in characters at least 10 mm high.
Container type Attachment point
Wire-mesh rack Bottom right on broad side of base
(1 standard label)
Sealed-wall container Bottom right on broad side of base
(1 standard label)
Insert rails-type load unit Bottom right on broad side of base
(1 standard label)
VDA small
container
a) Bottom right on broad side of base
(1 standard label)
b) End face (narrow side) in the document
pouches/label holders provided on each small
container (1 small label)
Chapter 5 Electronic Data
Interchange Manual
Page 72
Daimler AG
Issued December 2014
5.2 Layout specimen for standard label
Sample is not to scale!
5.3 Layout sample for small label (for small containers)
Sample is not to scale!
Chapter 6 Electronic Data
Interchange Manual
Page 73
Daimler AG
Issued December 2014
Forwarding instruction according to VDA 4922
Content overview
6 Forwarding instruction according to VDA 4922 74
6.1 Brief description 74
6.1.1 Groupage consignments 74
6.1.2 Direct transport operations 74
6.2 Notes on issuing the document 75
6.2.1 Groupage consignments 75
6.2.2 Direct-contract 75
6.2.3 Other important fields 75
Author of Chapter 6
Ms Pischka
SC/SET department
Sindelfingen plant
050_dqm@daimler.com
Chapter 6 Electronic Data
Interchange Manual
Page 74
Daimler AG
Issued December 2014
6 Forwarding instruction according to VDA 4922
6.1 Brief description
The VDA, in cooperation with the German Freight Forwarding and Storage Association (BSL), has developed a
standard transport accompanying document. The results are described in VDA recommendation VDA 4922
(forwarding instruction). The document has also been standardised by DIN under no. 5018 (see VDA
recommendation, Appendix 1–3 for a sample).
Another advantage of this document besides reducing processing costs is its close integration with the
delivery note and transport data EDI according to VDA recommendation 4913. The forwarding instruction
contains the significant fields from that message which are required for goods receipt purposes.
There are two main areas of application:
6.1.1 Groupage consignments
Our company has introduced an area contract freight forwarding category for groupage consignments. A
forwarding instruction has to be issued for preliminary transport from supplier
-> freight forwarder (transshipment point). The freight forwarder then draws up a loading list on the
basis of the data in the forwarding instruction.
The loading list is also sent in the EDI according to VDA 4921, and is used for freight billing, for example.
6.1.2 Direct transport operations
A forwarding instruction is also required for direct-contract transport operations, i.e. transport directly
from the supplier to us. In this case the manifest number (which is also the freight billing number) is
shown on the forwarding instruction.
The issue of a forwarding instruction is mandatory for every transport operation.
Chapter 6 Electronic Data
Interchange Manual
Page 75
Daimler AG
Issued December 2014
6.2 Notes on issuing the document
6.2.1 Groupage consignments
n waybills for a given unloading point
A waybill must be issued for each unloading point (= 1 to n consignment loading reference nos.).
Example:
If a truck stops at five unloading points in a plant section, five waybills must be issued.
The following fields, among others, must be completed:
Field 2 Supplier no.
Field 8 Consignment loading reference no.
Field 10 Freight forwarding no.
Field 18 Delivery note no.(s)
Note on assignment of manifest no.:
The manifest number for groupage consignments is assigned by the freight forwarder. No entry should be
made in the forwarding instruction.
6.2.2 Direct-contract
1 waybill per delivery address
Issue one waybill for each delivery address (= 1 Consignment loading reference no.). In this case there is only
one VDA 4913 (supplier) and no VDA 4921 (freight forwarder).
Example:
If a truck stops at two external warehouses of the same plant, two waybills must be made out.
The following fields, among others, must be completed:
Field 2 Supplier no.
Field 8 Consignment loading reference no.
Field 10 Freight forwarding no.
Field 13 Bordereau/loading list no.
Field 18 Delivery note no.(s)
6.2.3 Other important fields
In addition to the fields mentioned above, the following fields are also particularly important for goods receipt
and freight checking:
Field 16 Arrival date
Field 23 Loading equipment weight kg
Field 24 Gross weight kg
Chapter 7 Electronic Data
Interchange Manual
Page 76
Daimler AG
Issued December 2014
7 Package data sheet according to VDA 4931
The EDI dispatch of package data sheets according to VDA 4931 is not supported.
Package data sheets can be viewed and downloaded via the eCon (electronic Container Management) Internet
application only.
The eCon application can be found in the supplier portal after logging on
http://daimler.covisint.com
under “My Daimler applications”.
Please consult the process manual container management for more details.
You can access the process manual in eCon in the “Home” menu, under “Information”/“Process manual
Container Management”.
Author of Chapter 7
Ms Marion Städele
Department: T/WTM, B380
Phone +49 (0)7031 90-41041
Fax +49 (0)7031 90-77530
Marion.Staedele@Daimler.com
Chapter 8 Electronic Data
Interchange Manual
Page 77
Daimler AG
Issued December 2014
Container account statements according to VDA 4927
Content overview
8 Container account statements according to VDA 4927 78
8.1 Brief description of VDA 4927 78
8.2 Functional diagram of Daimler data network 78
8.3 Information on account statement processing 79
8.4 Posting types used 79
8.5 Notes on record types and data elements 80
Author of Chapter 8
Ms Natalie Brösamle
Department: SC/WTM, B380
Phone +49 (0)7031 90-2606
Fax +49 (0)7031 90-77530
natalie.broesamle@daimler.com
Chapter 8 Electronic Data
Interchange Manual
Page 78
Daimler AG
Issued December 2014
8 Container account statements according to VDA 4927
8.1 Brief description of VDA 4927
Daimler AG provides its partners with a monthly container account statement for centrally account-managed
containers for checking and reconciliation purposes. The account statements contain the container receipt
and dispatch postings of group plants that are members of the Daimler container pool.
Note:
For partners who are unable to process this EDI, we also offer a download option over our eCon (electronic
Container Management) Internet application.
8.2 Functional diagram of Daimler data network
Daily data transfers of container postings (receipt, dispatch and correction postings) to headquarters:
Daimler
Werk 1
Daimler
Werk 2
Daimler
Werk n
Daimler
Werk Vitoria
EvoBus
Werk Mannheim
smart France
Hambach
Zentrale LT-Bestandsführung
Aufgabenträger: Container Management CM (Standort Sindelfingen)
Internetapplikation eCon: Aufbereitung / Darstellung LT-Kontoauszüge
Alle Lieferanten mit LT-Konten
Hinweis: Korrekturen können nur von den Werken durchgeführt werden!
. Optional
- VDA 4927
-Internet
Daimler
Werk 1
Daimler
Werk 2
Daimler
Werk n
Daimler
Werk Vitoria
EvoBus
Werk Mannheim
smart France
Hambach
Zentrale LT-Kontoführung
Container Management CM (Standort Sindelfingen)
Internetapplikation eCon: Aufbereitung / Darstellung LT-Kontoauszüge
Alle Lieferanten mit LT-Konten
Hinweis: Korrekturen können nur von den Werken durchgeführt werden!
.
-
-
Daimler
Werk 1
Daimler
Werk 2
Daimler
Werk n
Daimler
Werk Vitoria
EvoBus
Werk Mannheim
smart France
Hambach
Internetapplikation eCon: Aufbereitung / Darstellung LT-Kontoauszüge
Alle Lieferanten mit LT-Konten
Hinweis: Korrekturen können nur von den Werken durchgeführt werden!
.
Daimler
Plant 1
Daimler
Plant 2
Daimler
Plant n
Daimler
Plant Vitoria
EvoBus
Plant Mannheim
smart France
Hambach
Internet application eCon: Preparation / Display of container account statements
All suppliers with container accounts-
Note: Corrections can only be made by the plants!
.Monthly
creation
Central account management of containers
Container Management CM (Location Sindelfingen)
Daimler
Werk 1
Daimler
Werk 2
Daimler
Werk n
Daimler
Werk Vitoria
EvoBus
Werk Mannheim
smart France
Hambach
Zentrale LT-Bestandsführung
Aufgabenträger: Container Management CM (Standort Sindelfingen)
Internetapplikation eCon: Aufbereitung / Darstellung LT-Kontoauszüge
Alle Lieferanten mit LT-Konten
Hinweis: Korrekturen können nur von den Werken durchgeführt werden!
. Optional
- VDA 4927
-Internet
Daimler
Werk 1
Daimler
Werk 2
Daimler
Werk n
Daimler
Werk Vitoria
EvoBus
Werk Mannheim
smart France
Hambach
Zentrale LT-Kontoführung
Container Management CM (Standort Sindelfingen)
Internetapplikation eCon: Aufbereitung / Darstellung LT-Kontoauszüge
Alle Lieferanten mit LT-Konten
Hinweis: Korrekturen können nur von den Werken durchgeführt werden!
.
-
-
Daimler
Werk 1
Daimler
Werk 2
Daimler
Werk n
Daimler
Werk Vitoria
EvoBus
Werk Mannheim
smart France
Hambach
Internetapplikation eCon: Aufbereitung / Darstellung LT-Kontoauszüge
Alle Lieferanten mit LT-Konten
Hinweis: Korrekturen können nur von den Werken durchgeführt werden!
.
Daimler
Plant 1
Daimler
Plant 2
Daimler
Plant n
Daimler
Plant Vitoria
EvoBus
Plant Mannheim
smart France
Hambach
Internet application eCon: Preparation / Display of container account statements
All suppliers with container accounts-
Note: Corrections can only be made by the plants!
.Monthly
creation
Central account management of containers
Container Management CM (Location Sindelfingen)
Chapter 8 Electronic Data
Interchange Manual
Page 79
Daimler AG
Issued December 2014
8.3 Information on account statement processing
Container account statements by EDI
Container account statements over EDI allow a computerised reconciliation of container movement data.
Partners have the option of having all EDI data sent to the main number (index at 9th character of supplier
no. = blank) or individually to the delivery locations (index at 9th character of supplier no. blank).
Container account statements via Internet
Account statements are made available over the Internet through our Container Management department.
Account management by delivery location
Our account management is based on “delivery locations”. For the supplier number, the internal Daimler
supplier no. index is used (9th character of the supplier no.). When reconciling the posting data, remember
that the posting may be found under another index.
Note:
The current scope of centrally account-managed containers is documented solely in the eCon Internet
application within the Daimler supplier portal. The scope of centrally account-managed containers is updated
several times a year. Our partners are required to reconcile their postings via eCon and to keep accounts of
their containers.
8.4 Posting types used
Document or transaction type Current year Prior year
Receipt
Daimler
Dispatch
Daimler
Receipt
Daimler
Dispatch
Daimler
Supplier delivery note,
Daimler dispatch delivery note
10 23 90 91
Substitute delivery note
(issued by Daimler)
12 23 90 91
Transport contract,
Waybill/forwarding instruction
14 21 90 91
Intermediate transport,
3- and 4-point transport operations
30 31 90 91
Correction 50 51 52 53
Inventory correction
(difference amount)
70 71 - -
Chapter 8 Electronic Data
Interchange Manual
Page 80
Daimler AG
Issued December 2014
8.5 Notes on record types and data elements
Record type 721
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
04 A 9 M Data sender
number 10005007_
Description:
Your customer number for the Sindelfingen plant is entered here.
If this number is not known, 10005007_ (_= space) is entered.
Record type 721
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
08 N 2 M Purpose of
communication
code
01
Description:
Enter 01 (= full account statement) here. For the moment, this is the only purpose of communication
supported.
Record type 722
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
03 A 9 M Supplier no. 12345678A
Description:
Entry of the 8-character supplier number and the delivery location index (if applicable) as the 9th character
(the index in the 9th character slot can also be a space).
If you are not aware of our index assignments, please contact Container Management.
Record type 722
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
05 A 9 M Customer
number 000000519
Description:
Entry of the customer number according to the numbers you have assigned to our plants. These numbers are
agreed upon between Container Management and you prior to implementation of
VDA 4927.
Chapter 8 Electronic Data
Interchange Manual
Page 81
Daimler AG
Issued December 2014
Record type 722
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
06 A 5 O Customer
location code 050__
Description:
Entry of our plant number which you already know from other processes. This is the number of the plant
making the posting.
Format example: 050__ (_= space)
Record type 724
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
05 N 3 O Doc. pos. no. 1 001
Description:
Entry of the position number of the material position on the delivery note (if applicable, the EDI according to
VDA 4913). Our systems are numbered in a continuous ascending sequence from 001.
Record type 724
Field Field
format
Field
length
Optional/Mandatory Designation Example of
an entry
Pos:
06 N 3 O Doc. pos. no. 2 001
Description:
Entry of the position number of the container position under a material position on the delivery note (if
applicable, the EDI according to VDA 4913). Our systems are numbered in a continuous ascending sequence
from 001.
Examples for the pos. 05 and pos. 06 fields:
Material pos. no. (= VDA field POS-NR 1)
Container pos. no. (= VDA field POS-NR 2)
Quantity
LC type
001
001
001
002
1-5003
20-4314
002
002
002
001
002
003
1-5010
30-6428
1-9040
However, under the package system it is possible to have several container positions with the same container
type which are combined in one material position (to reduce the transfer volume).
The base value of this “compressed” container position no. is then 401 ff rather than 001.
Chapter 8 Electronic Data
Interchange Manual
Page 82
Daimler AG
Issued December 2014
Record type 724
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos:
12 A 8 O Ref. document
no.
20090620
Description:
For orders of the Shared Container Network rebookings from the delivering plant to the plant with
requirements the original delivery note number is entered here.
The fields
Ref. document no. pos. no. 1 (pos. 13)
Ref. document no. pos. no. 2 (pos. 14)
Ref. document date (pos. 15)
Ref. entry date (pos. 18)
are not filled-in by Daimler.
The relevant correction operations are displayed with the original data in pos. 04 to pos. 10, in combination
with the appropriate transaction code.
Record type 725
Field Field
format
Field
length
Optional/Mandatory Designation Example of an
entry
Pos:
03 A 40 M Text 1 12345678C
Description:
The original supplier number is entered here. Only shown when the container has been rebooked from a
supplier number / location or a rebooking was made for an order of the Shared Container Network.
Chapter 9 Electronic Data
Interchange Manual
Page 83
Daimler AG
Issued December 2014
Transport data for shipments according to VDA 4921
Content overview
9 Transport data for shipments according to VDA 4921 84
9.1 Communication model for inclusion of shipment consignments 84
9.1.1 Supplier to freight forwarder (“electronic forwarding instruction”) 84
9.1.2 Freight forwarder to auto manufacturer (“electronic loading list”) 84
9.2 Brief description of VDA 4921 85
9.3 Time relationships between VDA 4913 and VDA 4921 85
9.4 Notes on record types and data elements 86
9.5 Transport management 95
9.5.1 Data transmission 95
9.5.2 Note on record types and data elements 95
9.6 Exchange dropside body concept (Wechselbrückenkonzept) 98
Author of Chapter 9
Mr Krodel
Sindelfingen plant
Department: LOG/SPL, F201
Phone +49(0) 70 31- 90-26 53
Fax +49(0) 70 31- 90-8 12 47
Harald.Krodel@daimler.com
Chapter 9 Electronic Data
Interchange Manual
Page 84
Daimler AG
Issued December 2014
9 Transport data for shipments according to VDA 4921
9.1 Communication model for inclusion of shipment consignments
Transport is an important link in the external material flow process. To ensure comprehensive process
information, it is essential to include transport contractors in the electronic data interchange process.
The VDA recommendations for EDI communications and documents for transport data outlined below were
developed in collaboration with the German Federal Freight Forwarding and Warehousing Association,
Bonn (BSL).
9.1.1 Supplier to freight forwarder (“electronic forwarding instruction”)
This information is an extremely important basis for rational and efficient transport processes.
The following recommendations are available:
a) VDA recommendation 4920
This document has not been generally accepted.
b) VDA/ODETTE recommendation TRINAD
On the basis of the EDIFACT message IFTMIN, the VDA has developed the TRINAD subset
(Transport Instruction Advice), working in close collaboration with ODETTE and BSL members.
Plans are being made for the implementation of this new message at Daimler AG.
Our company is likely to recommend the ODETTE message TRINAD (subset of the IFTMIN EDIFACT
message).
9.1.2 Freight forwarder to auto manufacturer (“electronic loading list”)
a) VDA recommendation 4921
The data exchange according to VDA 4921 is already a standard application with our area contract
freight forwarders.
b) VDA/ODETTE recommendation CONSUM
On the basis of the EDIFACT message IFCSUM, VDA has developed the CONSUM
(Consolidation Summary Message) message.
Daimler AG is not able to process this message at this stage.
This is how it should be: functional diagram
SpeditionSpedition
Absender
(Lieferant)
Absender
(Lieferant)
Empfänger
(Werke der
DCAG)
Empfänger
(Werke der
DCAG)
VDA 4913
- VDA 4913 (noch in Abstimmung)
- ODETTE TRINAD (geplant)
- VDA 4921
- ODETTE CONSUM (geplant)
In Absprache mit dem Waren-
empfänger und dem Spediteur
Chapter 9 Electronic Data
Interchange Manual
Page 85
Daimler AG
Issued December 2014
9.2 Brief description of VDA 4921
The VDA 4921 communication is generated by our area contract freight forwarders.
This message plays a key role in ensuring rational and efficient goods receipt processing at the consignee’s
location. Daimler AG is therefore planning to set up “driver self-service goods receipt stations”, based on
full EDI advice notifications with VDA 4913 and VDA 4921.
The communication concept comprises the following modules:
9.3 Time relationships between VDA 4913 and VDA 4921
VDA 4913 has a major impact on the functionality of VDA 4921.
VDA 4921 refers to VDA 4913 via the consignment loading reference no. and the delivery note list.
• First the VDA 4913
• Then the VDA 4921
For groupage consignment trucks, VDA 4921 provides the possibility of changing the consignment
composition as per the VDA 4913 according to the cargo actually loaded or trans-loaded at the freight
forwarding terminal (e.g. for consignment make-up according to unloading points).
Gebiets-
spediteur
Gebiets-
spediteurDC-
Werke
DC-
Werke
DFÜ: Liefer-
berechtigungs-
daten
Diskette:
LT-Stammdaten
DFÜ: Liefer-
scheindaten
VDA 4913
(für Nicht-DFP-
Lieferanten)
DFÜ 4912
Merce
des-
Benz
Chapter 9 Electronic Data
Interchange Manual
Page 86
Daimler AG
Issued December 2014
9.4 Notes on record types and data elements
9.4.1.1 Record type 751
Record type 751
Delivery note and transport data header record
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 01 N 3 M Record type 751
Description:
Constant “751”. Must be present once for each EDI run, otherwise there is no processing.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 01
Description:
Indicates how up-to-date a record type is. Listed in an unbroken ascending order for each record type. The
indicator is increased by 1 after each change to a record type completed by the “Print forms/data exchange”
VDA worker. Permissible: 01–99. Documented version: “01”.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 A 9 M Data recipient
number
123456789
Description:
ID number that the data recipient agrees with the data sender. All the data in a record structure that contains
the data sender number field is covered by data protection. Left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 A 9 M Data sender
number
12345678
Description:
ID number that the data recipient agrees with the data sender. All the data in a record structure that contains
the data sender number field is covered by data protection. Left-justified. Enter your valid Daimler supplier
number here, with index, if applicable.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 N 5 M Interchange
number old
00001
Description:
Right-justified entry with leading zeroes. No decimal places. See Interchange number new. In the first
interchange, the interchange number old = interchange number new.
Chapter 9 Electronic Data
Interchange Manual
Page 87
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 5 M Interchange
number new
00002
Description:
The data creator assigns an interchange number for each EDI run. The data creator and data recipient retain
this number for each functional area until the next interchange in the same functional area. As the data
creator also specifies the interchange number for the previous EDI run within the same functional area, the
recipient can check whether the EDI datasets in each functional area are complete. As a result, it is not
necessary for the numbers to ascend in an unbroken sequence. Right-justified entry with leading zeroes, no
decimal places.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 6 M Interchange date 091130
Description:
Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 A 89 M Blank [Blank]
Description:
[Blank] = space
9.4.1.2 Record type 752
Record type 752
One-off data for the transport
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 01 N 3 M Record type 752
Description:
Constant “752”
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 01
Description:
Indicates how up-to-date a record type is. Permissible: 01–99. Documented: “01”.
Chapter 9 Electronic Data
Interchange Manual
Page 88
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 N 2 M Means of
transport code
01
Description:
For the codes used, see VDA recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 A 25 M Means of
transport number
BB-AA 1235
Description:
Specifies the more detailed designation or number for the means of transport named in the preceding field.
Example: If the means of transport code is “01” motor vehicle, enter the tractor unit’s and/or trailer’s license
plate number or the exchange dropside body. Left-justified. Separate multiple license numbers with BLANKS.
[Blank] = space
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 A 17 M Manifest number 30141234
Description:
ID number that the forwarding agent assigns to a bordereau note. The bordereau is a combination of
individual consignments from a forwarding agents for a single goods recipient. Left-justified, in print form.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 6 M Bordereau date 091130
Description:
Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 1 M Bordereau
correction code
[Blank]
Description:
Code used: [Blank] = no change, 1 = 1st change, 2 = 2nd change, L = delete
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 A 8 O Extra tour no. 12345678
Description:
Order number assigned by the customer to identify an extra tour with freight calculation. Left-justified.
Chapter 9 Electronic Data
Interchange Manual
Page 89
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 N 6 O Consignment
volume
000654
Description:
Specifies the cubic metres, calculated from the largest length, width and height. Right-justified entry with
leading zeroes. No decimal places.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 N 12 O Consignment load
metres
000000000340
Description:
Specification in m (load metres). Right-justified entry with leading zeroes. No decimal places.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 A 46 M Blank [Blank]
Description:
[Blank] = space
9.4.1.3 Record type 753
Record type 753
One-off data for the delivery note
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 01 N 3 M Record type 753
Description:
Constant “753”.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 02
Description:
Indicates how up-to-date a record type is. See record type 751.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 N 6 O Means of
transport location
date
091130
Description:
Date on which the means of transport is at the specified location. Format: YYMMDD
Chapter 9 Electronic Data
Interchange Manual
Page 90
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 N 4 O Means of
transport location
time
1345
Description:
Time at which the means of transport is at the specified location. Format: HHMM
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 A 35 O Means of
transport location
Stuttgart
Description:
Location of the means of transport. Left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 6 O Planned arrival
date
091203
Description:
Date planned by the supplier for the arrival of the consignment at the customer’s site. Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 4 O Planned arrival
time
1400
Description:
Time planned by the supplier for the arrival of the consignment at the customer’s site. Format: HHMM
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 1 M Information
correction code
Description:
For the codes used, see VDA recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 A 67 O Text
Description:
Free continuous text. Left-justified.
Chapter 9 Electronic Data
Interchange Manual
Page 91
Daimler AG
Issued December 2014
9.4.1.4 Record type 754
Record type 754
Delivery note position data
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 01 N 3 M Record type 754
Description:
Constant “754”.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 03
Description:
Indicates how up-to-date a record type is, see record type 751.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 A 9 M Supplier no. 12345678A
Description:
ID number that the customer assigns to a supplier (contractual partner). All the data in a record structure that
contains the supplier number field is covered by data protection. Left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 N 8 M Consignment/
load reference no.
00555554
Description:
Reference number assigned by the sender/supplier to the consignment/load. Right-justified entry with
leading zeroes. This number must not be repeated within a period of one year. The sender enters this number
in field 8 of the “forwarding instruction VDA 4922” or in field 13A of the railway consignment note.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 A 17 O Forwarding
instruction no.
Description:
ID number that the forwarding agent assigns to an order. Left-justified.
Chapter 9 Electronic Data
Interchange Manual
Page 92
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 6 O Forwarding entry
date
091129
Description:
Assigned by freight forwarder. Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 A 1 O Consignment
code
Description:
For the codes used, see VDA recommendation.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 N 7 O Consignment
gross weight
0000490
Description:
Weight of goods, including packaging and/or loading equipment, but only the freight forwarder’s containers.
(Specification from waybill, similar to TDED 6292.) Quantity unit: kg, right-justified entry with leading zeroes,
no decimal places.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 N 7 O Consignment
net weight
0000460
Description:
Weight of goods, including the packaging without loading equipment and the freight forwarder’s containers
(similar to TDED 6160). Quantity unit: kg, right-justified entry with leading zeroes, no decimal places.
For certain processes, this field can be mandatory.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 N 7 O No. of packages 5
Description:
Total of all packages included in the consignment that are visible to the freight forwarder/forwarding agent,
regardless of packing material types.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 A 5 O Unloading point 499
Description:
Specifies the point in the customer’s plant where the goods are to be unloaded. Customer’s codes used. Left-
justified.
Chapter 9 Electronic Data
Interchange Manual
Page 93
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 12 A 3 M Supplier plant AAA
Description:
Supplier’s plant from which the delivery is sent, supplier’s codes used. Left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 A 3 O Customer plant 050
Description:
The customer’s plant that is to be supplied. Customer’s codes used. Left-justified.
In particular cases another entry can be demanded here by the Daimler AG. Then the field becomes the
mandatory field.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 A 53 M Blank
Description:
[Blank] = space
9.4.1.5 Record type 755
Record type 755
Packing material data
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 01 N 3 M Record type 755
Description:
Constant “755”.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 02 N 2 M Version number 01
Description:
Indicates how up-to-date this record type is. Permissible: 01–99. Documented: “01”.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 M Shipment
delivery note
table
Chapter 9 Electronic Data
Interchange Manual
Page 94
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 A 8 O Delivery note no. 00000001
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 05 A 8 O Delivery note no. 00000002
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 A 8 O Delivery note no. 00000003
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 A 8 O Delivery note no. 00000004
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 08 A 8 O Delivery note no. 00000005
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 09 A 8 O Delivery note no. 00000006
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Chapter 9 Electronic Data
Interchange Manual
Page 95
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 A 8 O Delivery note no. 00000007
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 A 8 O Delivery note no. 00000008
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 12 A 8 O Delivery note no. 00000009
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 13 A 8 O Delivery note no. 00000010
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 A 8 O Delivery note no. 00000011
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 15 A 8 O Delivery note no. 00000012
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Chapter 9 Electronic Data
Interchange Manual
Page 96
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 16 A 8 O Delivery note no. 00000013
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 17 A 8 O Delivery note no. 00000014
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 18 A 8 O Delivery note no. 00000015
Description:
ID number that the supplier assigns to a delivery note. Right-justified entry with leading zeroes. Ascending
sequence.
9.5 Transport management
Generally, the VDA 4921 specification applies. Deviations from the specification, with regard to transport
management, are described in this section.
9.5.1 Data transmission
The transport EDI is to be sent by no later than 2 hours before loading to the main run. This is essential to
ensure that the loader can download the data for the packages to be collected (electronic target loading list) on
their mobile phone.
9.5.2 Note on record types and data elements
The sequence of record types must be exactly as per the VDA specification.
Record type 752
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 A 25 M Means of
transport number
BB-AA123456
Description:
Official number plate of transport vehicle (tractor unit). Fill in the field left-justified.
Value: e.g. BB-AA123456
Chapter 9 Electronic Data
Interchange Manual
Page 97
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 05 A 17 M Bordereau
number
30141234
Description:
Characters 1–4: Bordereau header record, specified to freight forwarder by Daimler AG.
Characters 5–8: Issued by freight forwarder for each truck/transport unit (generally as a serial number).
This is an alphanumeric field. Fill in the field flush to the left. As the bordereau number is comprised of 8
characters, only.
Characters 33–40 should be filled-in. The remaining characters should be left empty.
Value: e.g. 30141234
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 07 N1 17 M Bordereau
correction code
1
Description:
Code used: BLANK = no change, 1 = 1st change, 2 = 2nd change, L = delete
Record type 753
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 06 N 6 O Target arrival
date
091130
Description:
Date specified by Daimler AG for arrival of the consignment. Format: YYMMDD
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 07 N 4 O Target arrival
time
1001
Description:
Time slot agreed between the freight forwarder and Daimler AG for arrival of the truck at the plant. Format:
HHMM. The notified target arrival time must correspond to the time slot number and therefore the start of the
time slot.
E.g.: time slot 10.01–11.01 a.m. = time slot number
Record type 754
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 A 9 M Supplier no. 12345678
Description:
The ID no. of the supplier is assigned by Daimler AG. Complete in flush left format.
Chapter 9 Electronic Data
Interchange Manual
Page 98
Daimler AG
Issued December 2014
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 04 N 8 M Consignment/load
reference no. I
00296471
Description:
This is the reference number assigned by the sender/supplier to the consignment/load. To be filled-in in flush
right format with leading zeroes.
Record type 755
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 M Shipment
delivery note list
Description:
This table can be used to list up to 15 delivery notes whose content is included in the relevant load. The first
field must be completed. All unused fields must have BLANKs.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 04 A 8 O Delivery note no.
I
00000001
Description:
In each of fields 1–15, an 8-character delivery note no. can be entered, flush right with leading zeroes.
Delivery note numbers should be provided in ascending order.
Chapter 9 Electronic Data
Interchange Manual
Page 99
Daimler AG
Issued December 2014
9.6 Exchange dropside body concept (Wechselbrückenkonzept)
Record type 752
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 03 N 2 M Means of
transport code
02
Exchange dropside body concept
Applies only to exchange dropside bodies processed via a TRAILER YARD at the recipient’s site:
Enter code 02 (= swap operations)
(Deviation from VDA specification)
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 04 A 25 M Means of
transport number
S-AM 713
Exchange dropside body concept
Applies only to exchange dropside bodies processed via a TRAILER YARD at the recipient’s site:
From char. 8: enter 1st exchange dropside body
From char. 20: enter 2nd exchange dropside body
Record type 754
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 04 N 8 M Consignment/
load reference no.
12345678
Exchange dropside body concept (record type 752, pos. 03 = 02)
Applies only to exchange dropside bodies processed via a TRAILER YARD at the recipient’s site:
The same Consignment loading reference no. (SLBN) may appear in two 754 records.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 07 A 3 M Consignment code 1
Exchange dropside body concept (record type 752, pos. 03 = 02)
Applies only to exchange dropside bodies processed via a TRAILER YARD at the recipient’s site:
Entry is 1 for 1st exchange dropside body
Entry is 2 for 2nd exchange dropside body
Chapter 10 Electronic Data
Interchange Manual
Page 100
Daimler AG
Issued December 2014
Invoice data according to VDA 4906
Content overview
10 Invoice data according to VDA 4906 101
10.1 Objectives of the invoice EDI 101
10.2 Notes on the use of the invoice EDI at Daimler AG 101
10.2.1 Recipient plant for an invoice EDI 101
10.2.2 Scope of an EDI communication 102
10.2.3 Billing with summary invoices 102
10.3 Structure of the VDA 4906 message 102
10.4 Notes on completion of the data records 102
Author of Chapter 10
Ms Appelmann
Wörth plant
Department: CL/E-RP
Phone +49(0) 72 71-71-54 11
Fax +49(0) 72 71- 71-68 06
Chapter 10 Electronic Data
Interchange Manual
Page 101
Daimler AG
Issued December 2014
10 Invoice data according to VDA 4906
Daimler AG has had consistently good results from the use of EDI for invoicing over a period of years. We
regard this process as a logical enhancement to conventional invoicing methods.
10.1 Objectives of the invoice EDI
The main objectives of the communication of invoice data by EDI are as follows:
Rapid communication of invoicing data from the supplier to the recipient of the goods or services
Elimination of the multiple-copy sets of invoice forms according to DIN 4991
Avoiding the re-entry of data by the recipient, with the attendant data entry errors and payment delays
Computerised processing of regularly recurring bulk invoice data via standardised interfaces
Automatic provision of invoice data for suppliers’ Finance departments, and the recipient’s invoice
checking, creditor processing and book-keeping desks, for example
10.2 Notes on the use of the invoice EDI at Daimler AG
10.2.1 Recipient plant for an invoice EDI
In some cases invoicing processing operations are carried out at a single location for several different plants.
Therefore, the procedure for invoice EDIs is as follows:
The table below shows the plants for which invoices are processed at a single location. Invoices for these
plants must be combined in the same data packet.
Plant location Posting plant for record type 812
000 000, 010, 020, 030, 960
010 100
019 040, 050, 190
020 200, 270, 330
020 280*
030 300, 240, 250, 340
040 400
050 500, 510
054 540
059 590
060 060, 380, 600
065 155, 420, 650
*Invoices for the EVO bus plant in Mannheim are to be
sent separately.
The invoices differ in terms of the information in record type 812, pos. 10, customer plant.
The complete data package may include invoices for different plants. This data package is to be sent to the
plant shown in the “plant location” column above.
Chapter 10 Electronic Data
Interchange Manual
Page 102
Daimler AG
Issued December 2014
10.2.2 Scope of an EDI communication
To make the invoice EDI process as economically efficient as possible, an invoice should be drawn up for each
delivery note. The total invoice amount should then be combined in billing plant-specific data packets, and
forwarded to the plants once a week.
10.2.3 Billing with summary invoices
According to Art. 14 UStG (German Value Added Tax Act), the invoice recipient is required to archive a
summary invoice (totals sheet) for each data packet posted. The data sender is required to compile a summary
invoice for each data packet sent, as per VDA recommendation 4906, Appendix 11.
This summary invoice is to be forwarded to the contact person at each plant as specified in Chapter 12, by a
clearly legible fax, immediately after dispatch of the data packet.
10.3 Structure of the VDA 4906 message
The communication of invoice data by EDI is to be carried out in accordance with “VDA recommendation
4906”, edition of May 1993.
The following record types are used:
Record type Description Notes
811 Header record Identifies the partners.
Defines purpose of communication
812 Invoice data Incl. invoice no., invoice date, final amount
813 Delivery data Incl. delivery note no., unloading point
814 Invoice
position data
Incl. part number, delivery quantity, unit price
819 Trailer record Contains the statistics of the data transfer
10.4 Notes on completion of the data records
This section addresses specific message fields that have frequently been the subject of queries and confusion.
Record type 811
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos. 08 A 20 O Recipient VAT
identification no.
(VAT ID no.)
DE812526315
Description:
Tax ID no. of the national tax administration of the recipient.
Tax ID no. for Daimler AG: DE812526315
Chapter 10 Electronic Data
Interchange Manual
Page 103
Daimler AG
Issued December 2014
Record type 812
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 07 N 3 M Currency 978
Description:
For invoices in EURO, enter ISO code “978” here.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 10 N 3 O Customer plant 030
Description:
The customer’s plant that is being invoiced. This entry must always be left-justified.
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 12 A 51 M “Spare character
slots”
Description:
Variable entry according to invoice type. Content to be agreed with Daimler AG.
Record type 813
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 11 A 60 M “Spare character
slots”
Description:
Variable entry according to invoice type. Content to be agreed with Daimler AG.
Record type 814
Field Field
format
Field
length
Optional/Mandatory Designation Example of an entry
Pos: 14 A 25 M “Spare character
slots”
Description:
Variable entry according to invoice type. Content to be agreed with Daimler AG.
The data transfer should be carried out according to the rules of VDA 4906. Please note the instructions on
the left/right justification of entries and the number of leading zeroes.
Chapter 11 Electronic Data
Interchange Manual
Page 104
Daimler AG
Issued December 2014
From procedure test to productive use
Content overview
11 From procedure test to productive use 105
11.1 General procedure 105
11.1.1 Procedure test with T-Systems 105
11.1.2 Individual message transmission test 105
11.1.3 Setting up EDI connections with plants 106
11.2 Information for addressing Daimler AG plants in OFTP 106
11.2.1 Actions to be carried out when starting to use EDI or making change notifications 106
Author of Chapter 11
Mr Krodel
Sindelfingen plant
Department: SC/SET, F201
Phone +49(0) 70 31- 90-26 53
Harald.Krodel@daimler.com
Chapter 11 Electronic Data
Interchange Manual
Page 105
Daimler AG
Issued December 2014
11 From procedure test to productive use
11.1 General procedure
As soon as you have completed the preparations at your location for setting up an EDI interface, please make
sure you have completed the following steps before setting up an EDI connection with our plants:
11.1.1 Procedure test with T-Systems
Line connections must be tested before any data interchanges with our plants.
Please contact T-Systems
Email: edi.hotline@t-systems.com
Phone: 0049 (0)39159762016
The Daimler AG has to assign it, if this is the first data transmission between the data sender and the Daimler
AG.
After the procedure tests have been successfully completed, please contact your contact persons at the
Daimler AG plants.
11.1.2 Individual message transmission test
11.1.2.1 Test of transfer of call-up data according to VDA 4905/4915
Tests will be carried on the transmission of VDA 4905/4915 call-up messages to you from each plant.
To set up the tests, please get in touch with the plant contact persons named in Chapter 12.
11.1.2.2 Test of transmission of delivery note and transport data according to VDA 4913
The transmission of the data can be send to the Daimler plant Sindelfingen, if the data sender the test data
VDA4913 developed.
You have to note, that no delivery number in the plant Sindelfingen which was already booked in the last 12
months can be used. For this reason you can use a pseudo address for example: 99999999 and also a pseudo
send address for example: 99999999
After the test data were sent, the data sender has to control the rightness of the data transmission in the
DQM-System (Data Quality Management). You will get the access through the supplier system (chapter 3.4).
If the test data is not correct and they have an error, than the data sender has to eliminate the errors and the
mapping for right data transmission must adapted in future.
The data sender must inform our DQM-CUHD about the successful test data transmission, if the test data was
correct (status green in DQM).
After that, the CUHD will inform all Daimler plants for the connection of the data sender as a new member for
the bill delivery data transmission.
Contact data CUHD:
Email: 050_datenqualitaet@daimler.com
Phone: 0049 (0)7031 90 77339
Tip:
If the test data successfully transmitted in the DQM cannot be found, than possibly a hierarchy mistake
exists. The hierarchy mistakes are apparent in the DQM in the function transmission data under search
transmission data packets (D101).
Chapter 11 Electronic Data
Interchange Manual
Page 106
Daimler AG
Issued December 2014
Tip:
If it doesn’t an EDL processing (another service provider), then the field ''supplier number (EDL)'' should not
be filled in the sentence type 714 in place 77-85 with the supplier’s number.
Please leave the field empty.
Only when an EDL processing with the transaction key 40, the supplier’s number may be entered here.
See also descriptions in the VDA 4913 recommendation.
If you have supplier relationships with the Sindelfingen plant, Sindelfingen will be the pilot plant for sending
the VDA 4913 delivery note and transport data message.
Please get in touch with the contact person at the Sindelfingen plant to arrange a time and date for the test:
Mr Rolf Weber
Tel.: 07031-90-81 395
E-mail: rolf.rw.weber@daimler.com
If you do not supply the Sindelfingen plant, please test the VDA 4913 message with a plant which you do
supply products to. Please get in touch with the plant contact persons named in Chapter 12.
Chapter 11 Electronic Data
Interchange Manual
Page 107
Daimler AG
Issued December 2014
11.1.2.3 Test of transmission of invoice data according to VDA 4906
Please contact the person from chapter 12.2.
The message to T-Systems will be initiated and tested by FAO/G for all plants.
An EDI-agreement must be concluded between you the Daimler AG for using the VDA 4904.
FAO/G will provide you this form in the beginning.
The transfer of the message VDA 4906 “commitment” will be tested in the plant where you have the most
supply relationships.
The purpose of this test is to check the content of the data transmitted against the requirements of the
receiving systems, which are identical at all plants.
11.1.3 Setting up EDI connections with plants
T-Systems will inform you about the successful implementation of the test. After that you can begin with
FAO/G the production startup for all plants.
Following notification from T-Systems or pilot plants regarding successful completion of these tests, you need
to contact the EDI managers of the various plants (Chapter 12).
You must be authorised in the reception systems of the relevant plants before carrying out any data
interchanges – otherwise it will not be possible to process your data.
Careful testing helps all parties to set up a reliable and secure data interchange, in terms of both technical
and content aspects.
11.2 Information for addressing Daimler AG plants in OFTP
11.2.1 Actions to be carried out when starting to use EDI or making change notifications
If you are planning to set up electronic data interchange with Daimler AG, or to change your existing EDI
connections, please complete the following 9 steps:
1. Please contact the partners (Chapter 12) for the relevant message type.
2. Enter all the communication parameters for data interchange with Daimler AG in your system or ask
your software supplier to do this for you.
3. Complete the form (provided by T-Systems) with your OFTP partner data and fax or mail it to:
T-Systems International GmbH
EDI Customer Support
Phone: +49 391 5976 2016
Fax: +49 391 580 211 271
Mail: edi.hotline@t-systems.com
4. If you are using EDI for the first time, complete the first time EDI users form (provided by
T-Systems) and fax it to the same number or mail.
5. Then arrange a date and time for a procedure test with the EDIS system with our EDI Customer
Supports.
6. Completion of the procedure test with the EDIS test system.
7. On successful completion of the procedure test, fax or mail your communication readiness notification
form to the EDI Customer Supports.
8. A data test with the relevant plant must then be made. Please inform your contact partner after the first
test data is sent.
Chapter 11 Electronic Data
Interchange Manual
Page 108
Daimler AG
Issued December 2014
9. After the data test has been made successfully, the contact partners in the other plants (Chapter 12) can
be informed by e-mail.
11.2.1.1 Remarks
If you wish to change your communication parameters, send the OTFP partner data form to the
EDI Customer Support.
To register EDI with additional VDA data formats, send the communication readiness notification
form to the EDI Customer Support.
11.2.1.2 Communication readiness
Individual Daimler AG plants are constantly producing data. Then this data has to be sent directly to their
communication partners (suppliers). This means that it is important to keep your communication system
ready to receive at all times. In any case, please enter the times at which your communication system can
receive data in the Communication readiness notification form.
11.2.1.3 Contacts
The contact point for changing, setting up or testing communication connections to Daimler AG
communication partners and receiving error reports regarding communication with EDIS systems is
generally the T-Systems EDI Customer Support.
When you contacting the T-Systems EDI Customer Support please be ready to give your Daimler AG
supplier no.
T-Systems International GmbH
EDI Customer Support
Telefon: +49 391 5976 2016
E-Fax: +49 391 580 211 271
E-Mail: edi.hotline@t-systems.com
The T-Systems EDI Customer Support is available 24 hours, 365 days a year.
A processing of new installations and changes will only Monday to friday 6:00 bis 18:00 clock clock
time German and not on national holidays
Outside of these hours only processing disorder.
Chapter 12 Electronic Data
Interchange Manual
Page 109
Daimler AG
Issued December 2014
Daimler AG contact persons
Content overview
12 Daimler AG contact persons 110
12.1 HQ contact persons 110
12.2 Contact persons at the plants 111
Chapter 12 Electronic Data
Interchange Manual
Page 110
Daimler AG
Issued December 2014
12 Daimler AG contact persons
12.1 HQ contact persons
Any questions about EDI set-up or ongoing operation should be referred to the plant contact persons specified
in the next few pages. All Daimler AG plants use the same receiving and sending systems, so the answers will
apply across multiple plants.
The following individuals are also available as HQ contact persons for applications:
Call-off (VDA 4905)/detailed call-off (VDA 4915)
Contacts Department Phone E-mail Plant
Mr Schopenhauer
LOG/PPS,
HPC B251
+49(0) 70 31
90-22 11
Oswald.Schopenhauer@
daimler.com
Plant 050,
71059
Sindelfingen
Call-off (VDA 4905)/detailed call-off (VDA 4915)/JIS call-off (VDA 4916)
Contacts Department Phone E-mail Plant
Mr Neschen
VAN/PSM
HPC PS26
+49(0)2 11
9 53-27 50
michael.neschen@
daimler.com
Plant 065,
40467 Düsseldorf
Delivery note (VDA 4913)/EDI goods accompanying slip (VDA 4912)/transport data (VDA 4921)
Contacts Department Phone E-mail Plant
Mr Krodel
SC/SET, HPC:
F201
+49(0) 7031
90-2653
Harald.Krodel@
daimler.com
050,
71059
Sindelfingen
Invoice (VDA 4906)/(supplier invoices)
Contacts Department Phone E-mail Plant
Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
All plants
Container account statement (VDA 4927)
Contacts Department Phone E-mail Plant
Ms Woehe
T/WTM
HPC: B380
+49(0) 70 31
90-77 353
sibylle.s.woehe@
daimler.com
050,
71063
Sindelfingen
Freight forwarder invoices
Contacts Department Phone E-mail Plant
Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
All plants
Chapter 12 Electronic Data
Interchange Manual
Page 111
Daimler AG
Issued December 2014
Remittance advice (VDA 4907)
Contacts Department Phone E-mail Plant
Ms Scheel/Mr Ebert
FAQ/R, HPC:
T121
+49(0)7 11
17-5 19 24
manuela.scheel@
daimler.com
096,
70546 Stuttgart
Mr Ebert
FAQ/R, HPC:
T121
+49(0)7 11
17-5 45 28
andreas.ebert@
daimler.com
096,
70546 Stuttgart
General questions about EDI
Contacts Department Phone E-mail Plant
Team EDI
SC/SET, HPC:
F201
+49(0)70 31
90-26 53
050_dqm@
daimler.com
050,
71059
Sindelfingen
12.2 Contact persons at the plants
Plant 006 Global Logistics Centre
Daimler AG
76725 Germersheim
Application Contacts Department Phone E-mail
Call-off Mr. Engel GSP/LSS +49(0) 72 74-
56-38 12
jens.engel@daimler.co
m
Delivery note/
transport data/
material label/
forwarding instruction
Mr. Fischer CWA/SWL
+49(0) 72 74-
56-41 48
simon.fischer@daimle
r.com
Plant 010 Untertürkheim
Daimler AG
70546 Stuttgart
Application Contacts Department Phone E-mail
Call-off Ms Ebinger
ITP/AL HPC M414
+49(0)7 11- 17-
6 48 78
andrea.a.ebinger@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr Deutsch
Mr Jockers
LOG/TM
LOG/TM
+49(0)7 11- 17-
3 32 02
+49(0)7 11- 17-
5 23 63
andreas.deutsch@
daimler.com
manfred.jockers@
daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Chapter 12 Electronic Data
Interchange Manual
Page 112
Daimler AG
Issued December 2014
Plant 020 Mannheim engine production
Plant 028 EvoBus GmbH Mannheim
Daimler AG
Motoren
68299 Mannheim
EvoBus GmbH
68299 Mannheim
Application Contacts Department Phone E-mail
Call-off plant 020 Mr Werner TG/ONC-M1
HPC G103
+49(0)6 21-
3 93-27 10
lothar.werner@daimle
r.com
Call-off plant 028 Mrs Kritzler MLO/MDWH
PC R532
+49(0)7 31 –
18 15 481
Anke.kritzler
@daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr Herrmann
Mr Lopes
TG/ONC-M1
HPC G103
MLO-LT/LV
+49(0)6 21-
3 93- 72 23
+49(0) 731-
181 12 888
juergen.h.herrmann@
daimler.com
carlos_alberto.lopes_d
e_almeida@daimler.co
m
Plant 030 Gaggenau Daimler AG
76568 Gaggenau
Application Contacts Department Phone E-mail
Call-off Mr Karotsch PZ-DVA
HPC 273
+49(0) 72 25-
61-41 64
axel.karotsch@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr Dreixler TDL-EL
HPC 021
+49(0) 72 25-
61-26 97
juergen.dreixler@
daimler.com
Plant 037 Ludwigsfelde
Daimler AG
Ludwigsfelde GmbH
Postfach 51
14961 Ludwigsfelde
Application Contacts Department Phone E-mail
Call-off Mr Ullrich LOG/MTS +49(0) 33 78-
83-20 30
georg.ullrich@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr. Blödorn VAN/PSL +49(0) 33 78-
83-40 15
dominik.bloedorn@
daimler.com
Chapter 12 Electronic Data
Interchange Manual
Page 113
Daimler AG
Issued December 2014
Plant 038 Wörth –
Unimog/special vehicles production area
Daimler AG
PBS
76742 Wörth
Application Contacts Department Phone E-mail
Call-off Mr Dörr PBS/TLP +49(0) 72 71-
71-70 89
bernd.doerr@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Ms Kochner TGE/OSS-G +49(0) 72 71-
71-3002
daniela.kochner@
daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Plant 040 Berlin-Marienfelde
Daimler AG
12274 Berlin, Germany
Application Contacts Department Phone E-mail
Call-off Ms Kamann L/SMD +49(0) 30-
74 91-23 05
Delivery note/
transport data/
forwarding instruction
Mr Köhn L/LPC +49(0) 30-
74 91-22 28
hans-bernd.koehn@
daimler.com
Material label Mr Schulte L/BL +49(0) 30-
74 91-28 20
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Plant 050 Sindelfingen
Daimler AG
71059 Sindelfingen
Application Contacts Department Phone E-mail
Call-off/
detailed call-off/
JIS call-off
Mr Breitling LOG/SPL
HPC F201
+49(0) 70 31-
90-56 15
Walter.Breitling@
daimler.com
Delivery note data/
transport data/
EDI goods accompanying
slip
Mr Weber SC/SET +49(0) 70 31-
90-8 13 95
Rolf.RW.Weber@
daimler.com
DIN delivery note/
material label
Mr. Lorenz SC/SET
HPC F100
+49(0) 70 31-
90-8 70 73
ferdi.lorenz@
daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Chapter 12 Electronic Data
Interchange Manual
Page 114
Daimler AG
Issued December 2014
Plant 051 Mercedes-Benz
Consolidation Center Europe
Daimler AG
71059 Sindelfingen
Application Contacts Department Phone E-mail
Call-off Mr Hammersdorf IPB/CPL1 +49(0) 70 31-
8 06 98
kai.hammersdorf@daim
ler.com
Delivery note/
transport data/
material label
Mr Kussmaul IPB/CPL1 +49(0) 70 31-
8 74 46
uwe.kussmaul@daimle
r.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Plant 054 Rastatt
Daimler AG
76432 Rastatt
Application Contacts Department Phone E-mail
Call-off Mr Wieser LOG/LCA +49(0) 72 22-
91-2 28 45
frank.wieser@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr Bittmann LOG/LCA +49(0) 72 22-
91-2 36 89
thomas.t.bittmann@
daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Plant 060 Wörth
Daimler AG
76742 Wörth
Application Contacts Department Phone E-mail
Call-off/detailed call-off Mr Tombor LW/S-GPV +49(0) 72 71-
71-29 52
hansguenter.tombor@
daimler.com
JIS call-off Mr Horr
LW/S-MI +49(0) 72 71-
71-33 36
Andreas.horr@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Ms Kochner TGE/OSS-G +49(0) 72 71-
71-3002
daniela.kochner@
daimler.com
Material label Ms Senger TGE/OSS-G +49(0) 72 71-
71-5320
Josianne.senger@
daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Chapter 12 Electronic Data
Interchange Manual
Page 115
Daimler AG
Issued December 2014
Plant 065 Düsseldorf Daimler AG
40467 Düsseldorf
Application Contacts Department Phone E-mail
Call-off Ms Langer LOG/BL-
MDT
+49(0)2 11-
9 53-21 02
christine.langer@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr Draga LOG/BL-WE +49(0)2 11-
9 53-29 33
Gerhard.Draga@
daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Plant 067 Bremen
Daimler AG
28190 Bremen
Application Contacts Department Phone E-mail
Call-off Mr Neumann LOG/SPL +49(0)421-
419 - 3078
michael.neumann@
daimler.com
Delivery note/
transport data/
forwarding instruction/
material label
Mr Abendroth/
Ms Radermacher-
Pillnick
LOG/SPL
LOG/SPL
+49(0)421-4194866
+49(0)421-4193721
alexander.abendroth@
daimler.com
birgit.radermacher-
pillnick@daimler.com
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Plant 068 Hamburg-Harburg Daimler AG
Postfach 910164
21160 Hamburg
Application Contacts Department Phone E-mail
Call-off Mr Wieczorek AFS +49(0) 40- 79
20-23 57
helmut.wieczorek@
daimler.com
Delivery note/
transport data/
forwarding instruction
Mr Krüger TLG +49(0) 40- 79
20-24 41
hans-juergen.krueger@
daimler.com
Material label Mr Wolfner TLG +49(0) 40- 79
20-25 74
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Chapter 12 Electronic Data
Interchange Manual
Page 116
Daimler AG
Issued December 2014
Plant 069 Kassel
Daimler AG
34112 Kassel
Application Contacts Department Phone E-mail
Call-off Mr Nöding OD3
HPC 280A
+49(0)5 61-
8 02-27 36
Juergen.Noeding@
daimler.com
Delivery note/
transport data/
material label/
forwarding instruction
Mr Giesler PKL
HPC 560A
+49(0)5 61-
8 02-23 22
Stephan.Giesler@
daimler.com
Werk 1521 Türkei
Daimler AG
MB Türkei, Aksaray
Application Contacts Department Phone E-mail
Delivery note/
transport data/
material label/
forwarding instruction
Mr Gungor
ITC/BT +90 3822151639
5434
erhan.gungor@
daimler.com
Werk 157 Spanien
Daimler AG
MB Spanien, Vitoria
Application Contacts Department Phone E-mail
Delivery note/
transport data/
material label/
forwarding instruction
Mrs
Jose Escoriaza
Jimenez
VAN/PSP
HPC PS71
+34 945 185176 maria-jose.escoriaza@
daimler.com
Plant 371 Ungarn Daimler AG
MB Ungarn, Kecskemét
Application Contacts Department Phone E-mail
Delivery note/
transport data/
material label/
forwarding instruction
Mr Gyurus
LOG/PK +36 7630 6178 bence.gyurus@daimler.
com
Mr Hahn LOG/PK +36 7630 2539 michael.mi.hahn@daim
ler.com
Chapter 12 Electronic Data
Interchange Manual
Page 117
Daimler AG
Issued December 2014
Delivery and unloading points for purchased parts, PLANT 006:
Plant 006 Germersheim Delivery and unloading points for
purchased parts
Unloading point Name Phone Fax
Daimler AG
Inter-Park Offenbach
76877 Offenbach/Queich
682 Goods
receipt
office
+49(0) 72 71-
71-57 71
40 23
Daimler AG
Gebäude 18
76742 Wörth
640/641/642/
643/648
Goods
receipt
office
+49(0) 72 71-
71-57 71
40 23
Daimler AG
Gebäude 24
76742 Wörth
646 Goods
receipt
office
+49(0) 72 71-
71-57 71
40 23
Daimler AG
Zelt E+F
76742 Wörth
647 Goods
receipt
office
+49(0) 72 71-
71-57 71
40 23
Daimler AG
Gebäude 20
76742 Wörth
649 Goods
receipt
office
+49(0) 72 71-
71-57 71
40 23
Daimler AG
Direktanlieferung
CKD/Halle 20
76742 Wörth
201 Goods
receipt
office
+49(0) 72 71-
71-57 71
40 23
Daimler AG
Zeppelinstraße 21-29
76275 Ettlingen
681/688/004 Goods
receipt
office
+49(0) 72 43-
3 25-1 10
1 64
Daimler AG
Industriegebiet Nord
Hafenstraße 1
76725 Germersheim
650/900/902/
907/908/910/
926/935/945
Ms
Verlohner
+49(0) 72 74-
56-41 44
41 32
Chapter 12 Electronic Data
Interchange Manual
Page 118
Daimler AG
Issued December 2014
The same EDI requirements specified in this manual also apply for certain deliveries to Steyr-Daimler-Puch
AG, Austria.
All questions concerning this matter must be referred to the following contact persons only:
Steyr-Daimler-Puch AG
Austria
Steyr-Daimler-Puch
Fahrzeugtechnik AG & Co AG
Potash 823
A-8011 Graz
Application Contacts Department Phone Fax
Call-offs for
purchased parts
Mr Pölzgruber GPL +43(3 16) 4 04-29
77
29 16
Call-off
sub-assemblies
Mr Schrei GPL +43(3 16) 4 04-21
74
29 27
JIS call-off Mr Vogrinec GPL +43(3 16) 4 04-37
47
29 27
Delivery note data/
transport data/
material label
forwarding instruction/
loading lists
Mr Kohlberger ZLMW +43(3 16) 4 04- 27
26
32 06
Invoice Mrs Erzberger
FAO/G
HPC T121
+49(0) 711-
17-83115
Richard.Erzberger@
daimler.com
Chapter 12 Electronic Data
Interchange Manual
Page 119
Daimler AG
Issued December 2014
13 Modifications
13.1 Version administration:
Version Cause Amendment Chapter
March 2013 update contact person data Contact person data was updated 12
March 2013 update description The description was updated 9
July 2013 update contact person data Contact person data was updated 12
November 2013 update contact person data Contact person data was updated 12
November 2013 update contact data Changes are marked yellow 11
January
2014
update contact person data Changes are marked yellow 1.2.1,
10, 11, 12
January
2014
update description Changes are marked yellow 11
August 2014 update contact person data Contact person data was updated 12
August 2014 update contact person data
and update description
Changes are marked yellow 8
December 2014 update contact person data Changes are marked yellow 1
December 2014 update contact data Changes are marked yellow 2
December 2014 update area contract freight
forwarders
Changes in the list of the area contract freight
forwarders
3.6
December 2014 extension Additional units of quantity 3.6
January 2015 extension (new chapter) Generation by EDL (external service providers) 3.13
January 2015 extension (new chapter) Confirmation of receipt (VDA4913 VA30 mod) 3.14
January 2015 update contact person data Contact person data for Wörth was updated 12
top related