TecDoc-Data-Format Version 2.6 en
TecDoc-Data-Format Version 2.6 en
Change history
Grouping of tables
in Information
Domains
2.0 2.0.1 July 2020 Table 115 Error correction in „Pos“-column
Table 001 Error correction (BrandNo Reference)
Table 053 Error correction (wrong table references)
General Some additional information on Primary Keys
Information
2.0.1 2.0.2 August General This documentation is the only official one since August
2020 2020 as 2.4 version is a subset of the 2.5 version.
More detailed information on Unicode characters
General
Information Maximum permitted size added
Table 053
2.0.2 2.0.3 September Table 053 Error corrections in references to table 030/031
2020
“Vehicle Classes” Change in field names was not performed in version 2.0.2
-> corrected in 2.0.3
Table 053 Multiple fields not used anymore. One of these is used
different now: CritUsage
Product information
2.0.8 2.0.9 May 2021 Table 231 Some error correction on filetypes in comment
Comment added
Table 333
Type of field QuantUnit corrected to ‘N’
Table 212
2.0.11 2.0.12 September General First general part restructured
2021
New chapter “About packaging …” added
Table 100 New rules for image files of type JPG, PNG, BMP
Error correction in record length (41 → 40)
Contents
1 General Information 10
307 The Allocation of Quick-start Icons to Nodes/Leaves within one Product Area ..............................106
5 ANNEX 1: Logistic Criteria for end user units (table 053 and 213) 171
1 General Information
Data Packages
Unicode
All information on record length refers to the maximum record length plus CR/LF.
A record may be shorter if the rest of the record consists only of blanks. However, records always end with a
CR/LF (Carriage Return (decimal 13) / Line Feed (decimal 10) combination.
References to Key Tables within this format description are abbreviated with “KT”.
References to other data tables in the format description are marked with “->“.
The format is Unicode-compatible. The following points have to be observed:
• all data tables are coded in UTF-8.
• Unicode characters may only be used in language-dependent fields in the tables 012, 030, 031, 035 and 327.
These fields are marked with the data type “U” in the column “Type”.
• Unicode in terms of the TecAlliance services is restricted to characters of the Basic Multilingual Plane of
the categories L (Letter), M (Mark), N (Number), P (Punctuation), S (Symbol), und Zs (Space)
The regular format for data exchange is based on text files in which the fields within the individual data records
of the tables have a fixed length and a fixed position.
The documentation of the individual tables in this document reflects exactly this table structure. Each field has
a length and a position (column) within the table. This format is established and recognized in the market.
With the beginning of the third quarter of 2020, the recipients of data packages (data users) will alternatively
have the data packages available in CSV format.
In this CSV format, the individual fields in each data record (row) are delimited by a fixed separator.
Recipients of data packages can choose to be delivered in the classic TAF format (fixed record lengths) or in CSV
format. A comprehensive stock of test data in CSV format is available.
It turns out in the past months and years that new requirements for new content in TecDoc data are a constant
flow of input and in many cases need to be processed immediately – e.g. to support new validations in order to
increase data quality and to support DQM measures.
Therefore we reserve the option to provide additional structures and to extend existing tables by additional
fields at the end of the table structure without a pre-announcement six months upfront.
We will of course announce the additional content but the time between announcement and implementation
might be shorter.
Please note that this only applies for additional structures that do not interfere with the existing structures and
content in a way that you would not be able to use the existing data without any change.
The version 2.5 is published in order to add tables for article criteria from the logistics area of application.
“Logistic information” in this case means any logistic information concerning the article itself.
Any further information on packaging hierarchies is not part of the TecDoc Format 2.5.
To make the usage possible as an optional AddOn without interfering with existing data and processes we add
three tables that include the necessary information.
The structure follows the generic approach of article criteria as given and used in the tables 50, 30 and 202.
The new tables are added as follows:
Furthermore we integrated some minor extensions in order to close gaps or correct errors from the past
versions.
Please read the chapter “Format Changes” for all the details.
More detailed information about the specific criteria and the schedule have been and will be published in the
regular Data Distribution Mailings and in the Data Distribution wiki at www.tecalliance.net
Changes in TecDoc Format version 2.6 (not available before July 2021)
The data Quality activities carried out continuously by the TecAlliance in close alignment with customer experts
resulted in a more standardized way to use criteria in two ways:
- Which criteria to use for specific Generic Article
- How to format the value of a criteria
- New table 332 containing the permitted key values for the key-table criteria of table 331 (similar to able
330)
- New table 333 containing formatting constraints for criteria. General constraints or some special rules
for specific Generic Article context are given.
The structure and content of tables 328 / 329 /330 remains available for compatibility reasons and for those
Generic Articles where the DQM measures have not been finished.
Minor changes:
Tables 328/329 do not contain any country restriction option any more. The field was not used at all and will be
set to “reserved”
The fields Art and Lnk in table 329 are not used anymore and are set to const=0 for compatibility reasons. Table
050 is the single point of truth for this information.
2) Logistic Information
The option to add logistical criteria to end user units (Format Version 2.5 extension) is further extend by the
option to give information about the packaging hierarchy for shipping.
- New table 214 containing the packaging items including the amount objects inside and the type,
measurement and weight of the packaging unit. A standard for measuring packaging objects is
provided as well.
9-digit KTypNr/NTypNr
Of the 9 digits in the fields KTypNr/NTypNr, or their counterparts in VKN_VALUE and VknZielArt, currently only
the last 6 digits are used for the numbering of vehicles. The first three digits remain unused until further notice
and are to be filled with leading zeros “000” in the data exchange format.
Please Note: The field VKN_VALUE in the data table 222 is currently only 6 digits. This designing error was only
noticed in April 2013 and will be rectified at the next format version. Due to the lack of time until the first pilot in
the fall of 2013 the adaptation to 9 digits will not be done now.
Affected tables:
120 Vehicle types
121 KBA type allocation
122 Vehicle country restriction
123 TypeMine type allocation
124 Vehicle country speciications
125 Engine number allocation to vehicle types
126 Swiss type number allocation to vehicle types
127 Allocation of Dutch number plate to vehicle type
128 Allocation of Swedish number plates to vehicle types
129 Austrian NatCodes
144 Additional vehicle type descriptions
145 Build types
147 Drive type synonyms
164 Allocation of axle typest o CV types
222 Accessory lists (VKN_VALUE) -> see note above
400 Article linkage (VknZielNr)
401 Search menu information texts (VknZielNr)
402 Linkages not to be displayed in certain countries (VknZielNr)
403 Country restricton of the linkage (VknZielNr)
404 Sorting of the linkage (VknZielNr)
410 Linkage attributes (VknZielNr)
432 Linkage-dependent graphics/documents (VknZielNr)
532 CV types
533 CV types country restrictions
534 CV country specific deviations
535 CV secondary types
536 CV secondary type country restrictions
537 CV types engine mapping
538 Mapping of CV to CV-ID numbers
539 Country restriction of the mapping of CV to CV-ID numbers
Vehicle Classes
The following additions will be available for productive use in the fourth quarter of 2019 at the earliest.
Please note the announcements of TecAllianice via data Distribution Mailing.
The format provides a definition for a fine-grained classification of vehicles. This classification opens up the
possibility to clearly identify further vehicle classes within the vehicle tables 120 (passenger car/kTyp) and 532
(commercial vehicle/nTyp). This extension goes beyond the existing vehicle classes "Transporter" and
"Motorcycles" and focuses primarily on the field of electromobility.
Without adjustments in the data exchange structure, it is thus possible to derive further vehicle classes (e.g.
electric motorcycles) from the identifying keys kType and nType according to a fixed set of rules.
These new vehicle classes can be understood as extensions in the sense of the linkage target types of the data
structure. You can find these valid linkage target types in key table 271 as follows:
2 TecDoc PC
3 TecDoc Motorcycle
4 TecDoc E-PC
5 TecDoc E-LCV
6 TecDoc E-Motorcycle
16 TecDoc CV
17 TecDoc Bus
18 TecDoc Tractor
20 TecDoc E-Bus
999 TecDoc LCV
In the context of linkages (tables 400ff), only linkage target types 2 (passenger cars) and 16 (commercial
vehicles) are used so far. The present set of rules now permits a resilient and comprehensible transfer of this
rather rough view into a more fine-grained vehicle structure.
1) A list of the vehicle classes in the TecDoc data (KT271 - see above).
2) A set of rules for the conversion of the kTyp/nTyp system into a more detailed view.
3) A reference to the respective attributes provided for the vehicle classes in Tables 120 and 532.
4) A new record type 115 with the current mappings of kType/nType relationship target types (2/16)
derived from 2) for the extended view according to key table 271 (see above). This record type is part of
the data packages until further notice.
Logistic information about packaging and batch/lot size information is part of TecDoc data for a long time and
is going to be extended by more reliable and well structured options step by step starting with version 2.6 of the
TecDoc format.
The „classic“ part of the TecDoc data can be found inside the tables 200 and 212.
Both tables refer to the end-user unit. Table 212 allows information on the standard packaging of this end-user
unit - how many units (QuantUnit) with how many items each (QuantPerUnit)?
In relation to these units (QuantUnit), two batch sizes (BatchSize1, BatchSize2) can be listed in table 200 - in the
sense of a hierarchy (BatchSize2 must be multiple of BatchSize1)
The new logistical information in table 214 (and 216) is intended to supplement (or also replace) this in a
manner that a complete packaging hierarchy can be provided in which each outer packaging has its own article
number.
Table 218 extends this option to include lot sizes that are uniquely assigned to the end-user unit or to a defined
outer packaging and that can optionally also be provided individually for defined trading partners. For the latter
option, please refer to the mailing to be published at the beginning of August.
In fact, there are two areas that contain similar information. We have chosen this approach in order not to force
anyone into using a new structure. We believe that the new structures will be easier, clearer and more flexible to
use for logistical purposes. We therefore recommend any data supplier to switch to this new structure as soon
as data maintenance is available in DMM software (please follow the announcements).
001 Header
Source: Data Supplier / TecDoc
Contents: Header stating version and date
Length: 58
Data Release Data Release 007 4 N Version (Data Release) in the format xxyy
DeleteFlag Lösch-Flag 057 1 N 1=Delete all data records of the brand, otherwise
‘0’
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
The delete-flag in table 001 differs in the treatment from the delete-flags of the other
tables. It indicates the deletion of a complete brand.
Source: TecDoc
Contents: Description of all countries and relevant information
Length: 71
Sorting: CountryCode
Primary Key: CountryCode
Source: TecDoc
Contents: Country-dependent descriptions
Length: 104
Sorting: TermNo, CountryCode, LanguageNo
Primary Key: TermNo, CountryCode, LanguageNo
Annotation:
CC is an optional attribute what may be a problem from a technical point of view. Some Database Management
Systems are not able to handle this 1:1. We recommend to implement a lookup on an artificial “CC” that is not
used by TecDoc. We are working on future format generations that will not use constellations like that.
Source: TecDoc
Contents: Allocation of countries to country groups
Length: 35
Sorting: CountryGrp, CountryCode
Primary Key: CountryGrp, CountryCode
Source: TecDoc
Contents: Definition of document types
Length: 43
Sorting: DocType
Primary Key: DocType
Extension Extension 040 3 (C) File Extension (three blanks with document type
“URL”)
(*) This type is not part of inbound data processing so as a Data Supplier you are not able to choose this
document type via DMM software. It is just set up in case a Data User intends to integrate the 360° images
into TecDoc format tables. Please read the information sheet for 360° grafics in case you like to know more.
020 Language
Source: TecDoc
Contents: Description of the languages used
Length: 47
Sorting: LangNo
Primary Key: LangNo
ISOCode ISO Code 041 2 (C) 2-digit ISO 639-Code of the language
BrandNo DLNr 022 4 N Data Supplier Number Constant and 9999 for
reference data
Notes: Text such as article additional descriptions are not saved with the article but are
registered in a separate language table for reasons of international compatibility.
Access to the relevant text is facilitated by means of a description number and the
relevant language number.
Data suppliers can create their own language-specific texts apart from the data table of
description texts provided by TECDOC. The first 100000 numbers are reserved for
TECDOC descriptions.
Source: TecDoc
Contents: Description of all criteria
Length: 59
Sorting: BrandNo, CritNo
Primary Key: BrandNo, CritNo
OKArticle OK-Artikel 023 1 N Criterion may be used for article (SA 210)
(0 = No, 1 = Yes)
TabNo TabNr 024 3 (N) Number of the Key Table for type ‘K’
OKDrivCab OK- 030 1 N Criterion may be used for Driver Cab linkages
Fahrerhaus
(0 = No, 1 = Yes)
1. Characters "0" to "9", comma "," as well as plus "" and minus "-" are permitted
2. A comma may not be used at the beginning or end of the value
3. A comma may only be used once within a value
4. Only the comma may be used as the decimal separator
5. Thousands seperators must not be used
6. Exactly one "+" or exactly one "-" may only be used at the beginning of a numeric value
7. Spaces must not be used
8. All(!) characters are part of the maximum length of an attribute.
Source: TecDoc
Contents: Table definition
Length: 43
Sorting: KeyTabNo
Primary Key: KeyTabNo
1 References to Key Tables within this format description are designated by ‘KT’
Source: TecDoc
Contents: Key Table Entries
Length: 48
Sorting: KeyTabNo, SortNo
Primary Key: KeyTabNo, Key
Source: TecDoc
Contents: Descriptions in different languages
Length: 79
Sorting: TermNo, LangNo
Primary Key: TermNo ,LangNo
BrandNo DLNr 000 4 N Data Supplier Number Constant and 9999 for
reference data
Notes: Text such as article additional descriptions are not saved with the article but are
registered in a separate language table for reasons of international compatibility.
Access to the relevant text is facilitated by means of a description number and the
relevant language number.
Data suppliers can create their own language-specific texts apart from the data table of
description texts provided by TECDOC. The first 100000 numbers are reserved for
TECDOC descriptions.
This is not a 1:1 copy of table 30 as those parts of table 30 are removed that are not used anymore (reserved
characters at the beginning, DeleteFlag)
Source: TecDoc
Contents: Description of all criteria
Length: 59
Sorting: BrandNo, CritNo
Primary Key: BrandNo, CritNo
OKArtikel OK-Artikel 023 1 N Criterion may be used for article (SA 213)
(0 = No, 1 = Yes) --- const = 1
TabNo TabNr 024 3 (N) Number of the Key Table for type ‘K’
Multiple Mehrfach- 033 1 N Criterion may be used more than once within a
verwendung
criteria (0 = No, 1 = Yes)
TermNoAbbr BezNrAbk 034 9 (N) Description number for the abbreviation (->031)
Notes: Any Data Supplier may request TecDoc to create new criteria needed for their
articles/linkages. Such new criteria then also become available to all the other Data
Suppliers.
Criteria of type 'D' (date) must be given in the format 'yyyymm' (four-digit year, two-digit
month, e.g. 202110 for October 2021)
(*) This is for future use if more criteria on packaging level items will be needed as given in table. With start
of 2.6 this is const=0
1. Characters "0" to "9", comma "," as well as plus "" and minus "-" are permitted
2. A comma may not be used at the beginning or end of the value
3. A comma may only be used once within a value
4. Only the comma may be used as the decimal separator
5. Thousands seperators must not be used
6. Exactly one "+" or exactly one "-" may only be used at the beginning of a numeric value
7. Spaces must not be used
334 Generic Articles requiring a Safety data Sheet … New table in format
version 2.6
Definition
for certain products the provision of a safety data sheet is mandatory or strongly recommended. Safety data
Sheets can already be distributed as digital assets (documents)= using tables 213 and 232 and indicating the
document to be a Safety Data Sheet (231.DocTermNorm = 6).
To improve the quality of data and support the industry during data maintenance process this table includes
those Generic Articles where the delivery of a safety data Sheet is at least strongly recommended.
Source: TecDoc
Reserved n/a 007 27 n/a For future uses – filled with blank characters
100 Manufacturer
Source: TecDoc
Contents: Description of all manufacturers
Length: 40
Sorting: ManNo
Primary Key: ManNo
Source: TecDoc
Contents: Allocation of KBA code to manufacturer
Length: 39
Sorting: KBANo, ManNo
Primary Key: KBANo, ManNo
Source: TecDoc
Contents: Description of all vehicle model series
Length: 47
Sorting: KModNo
Primary Key: KModNo
SortNo SortNr 027 3 N Sorting key for the sorting within one manufacturer
(ManNo)
Note: PC/CV: One of theses fields must contain the value =1; both fields can also be set
to the value = 1.
Source: TecDoc
The entries in the LTTypeExtended field allow a more detailed differentiation of vehicles in the links (tables
400ff). The following link target types are possible by using the mappings of table 115
2 TecDoc PC
3 TecDoc Motorcycle
4 TecDoc E-PC
5 TecDoc E-LCV
6 TecDoc E-Motorcycle
16 TecDoc CV
17 TecDoc Bus
18 TecDoc Tractor
20 TecDoc E-Bus
999 TecDoc LCV
If you as a data user want to make use of this extended option in your systems, you can replace the entry in the
VKNZielArt field in the provided linkage tables (400ff) according to the mapping in table 115. To do this,
proceed as follows:
The breakup of the kTyp/nTyp system represents a fundamental paradigm shift, which can be accompanied
by extensive consequences for interfaces and application systems. For this reason, we provide this mapping
rule as an optional supplement. There is no obligation to use it.
Source: TecDoc
Contents: Description of all vehicle types
Length: 107
Sorting: KTypNo
Primary Key: KTypNo
Source: TecDoc
Contents: Allocation of KBA codes to vehicle types
Length: 129
Sorting: KBANo, KTypNo
Primary Key: KBANo, KTypNo
Source: TecDoc
Contents: Inclusion/Exclusion of certain countries for a vehicle
Length: 42
Sorting: KTypNo, CountryCode
Primary Key: KTypNo, CountryCode
Source: TecDoc
Contents: Allocation of Type Mine numbers to vehicle types
Length: 31
Sorting: TypMine, KTypNo
Primary Key: TypMine, KTypNo
Source: TecDoc
Contents: Description of all country specific deviations of vehicle types
Length: 88
Sorting: KTypNo, CountryCode
Primary Key: KTypNo, CountryCode
Source: TecDoc
Contents: Allocation of Swiss type numbers to vehicle types
Length: 23
Sorting: ChTyp, KTypNo
Primary Key: ChTyp, KTypNo
Source: TecDoc
Contents: Allocation of Netherlands number plates to vehicle types
Length: 22
Sorting: NLTyp, KTypNo
Primary Key: NLTyp, KTypNo
Source: TecDoc
Contents: Allocation of Swedish number plates to vehicle types
Length: 22
Sorting: STyp, KTypNo
Primary Key: STyp, KTypNo
Source: TecDoc
Contents: Allocation of Austrian NatCodes to vehicle types
Length: 22
Sorting: NatCode, KTypNo
Primary Key: NatCode, KTypNo
Source: TecDoc
Contents: Additional information on all vehicle model series
Length: 30
Sorting: KModNo
Primary Key: KModNo
Notes on LbezNr1 and LbezNr2: One of the fields is always filled. When only one field is filled, the other one
contains ‘000000000’.
Source: TecDoc
Contents: Allocation of model types to model series
Length: 30
Sorting: KmodNo, CountryCode, SortNo
Primary Key: KmodNo, CountryCode, ModelType
Source: TecDoc
Contents: Additional information on all vehicle types
Length: 56
Sorting: KTypNo
Primary Key: KTypNo
Note on CTermNo1 and CTermNo2: One of the fields is always filled. When only one field is filled, the other
contains ‘000000000’.
Source: TecDoc
Source: TecDoc
Source: TecDoc
Contents: Drive Type Synonyms
Length: 50
Sorting: DriveType, KTypNo
Primary Key: DriveType, KTypNo
532 CV Types
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Contents: Inclusion of certain countries for the allocation of CV primary and secondary types
to manufacturer ID numbers
Length: 50
Sorting: NTypNo, NTypSubNo, ManIDNo, CountryCode
Primary Key: NTypNo, NTypSubNo, ManIDNo, CountryCode
Source: TecDoc
Contents: Allocation of different voltages for CV primary and secondary types and to
manufacturer ID numbers.
Max. Length: 49
Sorting: NTypNo, NTypSubNo, SeqNo
Primary Key: NTypNo, NTypSubNo, SeqNo
Exclude Exclude 048 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
Source: TecDoc
CTermNo LBezNr 053 9 N Description number (-> 012) for the sales
description
Source: TecDoc
Source: TecDoc
Exclude Exclude 063 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
544 Transmission
Source: TecDoc
Source: TecDoc
Source: TecDoc
Exclude Exclude 063 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
550 CV Wheelbase
Source: TecDoc
Exclude Exclude 055 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
551 CV Suspension
Source: TecDoc
Exclude Exclude 052 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
552 CV Tyres
Source: TecDoc
Exclude Exclude 052 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
553 CV Chassis
Source: TecDoc
Exclude Exclude 056 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
554 CV Producer-IDs
Source: TecDoc
Source: TecDoc
Engine Information
Source: TecDoc
Contents: Allocation of engine numbers to vehicle types
Length: 62
Sorting: KTypNo, SeqNo
Primary Key: KTypNo, SeqNo
Exclude Exclude 061 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
155 Engines
Source: TecDoc
Contents: Description of all engine types
Length: 263
Sorting: EngNo
Primary Key: EngNo
Source: TecDoc
Contents: Country restrictions for engines
Length: 15
Sorting: EngNo, CountryCode
Primary Key: EngNo, CountryCode
The country code field CountryCode must contain a valid country code (<> Blank).
Source: TecDoc
Exclude Exclude 064 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
Axle Information
160 Axle
Source: TecDoc
Contents: Description of all Axle types
Length: 121
Sorting: ATypNo
Primary Key: ATypNo
Source: TecDoc
Contents: Allocation of body types to Axle types
Length: 39
Sorting: ATypNo, SortNo, CountryCode
Primary Key: ATypNo, SortNo, BodyType
162 Axle-Wheelbases
Source: TecDoc
163 Axle-Brake-Size
Source: TecDoc
Source: TecDoc
Search Structure
Source: TecDoc
TreeTypNo TreeTypNr 036 3 N Product section of the search node (KT 999)
SortNo SortNr 048 2 N Sorting order of the search node that belongs to
a Node_Parent_ID.
2 Level 1 is the highest hierarchical level. The limitation to 4 hierarchical levels is removed with the Data Release 0914
(Quarter 04/2014)
3 This field is empty when the data record describes an entry in the superior hierarchy level.
Source: TecDoc
Source: TecDoc
Contents: Allocation of criteria to combinations of search tree nodes and generic articles
within the TecDoc search structure
Length: 46
Sorting: Node_ID, GenArtNo, SortNo
Primary Key: Node_ID, GenArtNo, CritNo, CritVal
Source: TecDoc
Source: TecDoc
Contents: The allocation of quick-start icons to the product areas (PC, CV, etc.)
Length: 17
Sorting: TreeTypNo, QS_Id
Primary Key: TreeTypNo, QS_Id
SortNo SortNr 014 3 N Quick-start icons sorting within the product area
Source: TecDoc
Contents: Allocation of quick-start icons to Nodes/Leaves within one product area (PC, CV,
etc.)
Length: 24
Sorting: TreeTypNo, QS_Id, Node_ID
Primary Key: TreeTypNo, QS_Id, Node_ID
Generic Articles
With the TecDoc Format version 2.6 some adjustments and extensions become effective to further improve the
quality of the TecDoc catalogue data.
The changes follow the already published and reported new rules of the TecDoc Data Quality Management
(DQM) initiative started in 2020.
The use of criteria can be limited - depending on the generic article - as follows:
Mandatory Criteria:
Generic Articles may expect specific criteria for a mandatory usage.
The information is given in table 328 as before.
Even if table 329 incl. proposed criteria still remains for now, all other criteria can still be used but must not be
displayed on the first catalogue page.
As this is not a very comfortable way of referencing data we provide a (redundant) extension by introducing
table 331 that is basically a merge of tables 328 and 329. It does not provide new content but a more
comfortable way to handle table 330 restrictions.
One of the main points of criticism about quality of TecDoc data was the nearly arbitrary use of criteria of type N
(numerical) or C (Character). Especially comparing the content of the same numerical criterion values of
different brands to identify a spare part shows huge differences in formatting that makes catalogues hard to
use.
Source: TecDoc
Comments: A flag OK-LCV is currently not planned. All generic articles with the flag OK-PC are
allowed for a linkage to LCV.
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Source: TecDoc
Reserved2 n/a 037 3 (C) Former Country Code (not used anymore)
Source: TecDoc
(*): The pair GenArtNo/SeqNo is identifying exactly one entry from table 328 or table 329. These two tables
together deliver a unique set of GenArtNo/SeqNo values.
331 Criteria allocated to Generic Articles … New table in format version 2.6
Attention:
This table provides a merge of the table 328 content and the new DQM standard for optional criteria in order to
provide an easy to use way to integrate the new and extended standardisation of criteria usage for display on
the first catalogue page.
It is as well possible to continue using tables 328 and 329 (please take care of adjusted content!).
Source: TecDoc
Contents: Permitted Generic Article/Criteria combinations for use on first catalogue page
Length: 22
Sorting: GenArtNo, SortNo , CritNo
Primary Key: GenArtNo, CritNo
SortNo 012 4 (N) Sort order for display of criteria on first catalogue page.
Needs to be unique for all entries of one GA. Not
required for usage=2 criteria
(*) For GA/Criteria combinations that are already standardised by DQM measures only the values 1 and 0 are
part of the data. For all other GA/criteria combinations the values are 1 or 2, what indicates recommended
attributes like the ones given in table 329
(**) Will be delivered first with version 1121 on October, 14 th 2021
All criteria not listed in this table are not recommended for use at all. If they are still used they must not be
flagged for display on the first catalogue page. The validations in TecAlliance data maintenance tools and
interfaces will take care.
Source: TecDoc
GenArtNo 007 5 N
References entry in table 331
CritNo 012 4 N
Source: TecDoc
Constraint n/a 019 100 C Rule for value of CritNo used for article of
GenArtNo. Provided as Regular Expression
following <tbd> standard notation
In case of multiple entries for one CritNo, the ones including a GenArtNo have always a higher priority then the
one without a GenArtNo.
The semantics in this case is that in general the Criteria CritNo requires a format <RegEx1> but if CritNo is used
for an article allocated to Generic Article GenArtNo it requires a format <RegEx2>
Notes: A text module may contain blank lines but may not consist of blank lines only.
The sequential number starts at 001 and increases with one for each text line of a
module.
A sequential number should not be repeated within one language and text module.
Note: One data record that contains the address type ‘General Address’ must be present.
Notes: CountryCode ‘Blank’ takes the main address from the DT 040
The combination BildNr, Dokumentenart must be contained in the DT 231.
The usage of “DokumentenArt” URL is not permitted (-> DT 014)
The BildNr used in the DT 042 must be of the document type ‘Logo’ in the DT 231.
(KT 143, Entry 02)
Maximum size of Logo is 130 x 90 Pixel
TermNo BezNr 029 9 (N) Description text number in the language key
table
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Price Preis 029 10 (N) Gross price with two decimal spaces or blank
for price on demand
CountryCode LKZ 061 3 C Country code for currency country (-> 010).
Notes: Each article may contain more than one valid price information record for different
countries, price types, currencies, and dates of validity.
Only individual countries and no country groups may be entered in the field
CountryCode.
Price validity dates for the same country (currency) must be individually conclusive.
Each ArtNo must be contained in the data table (->DT200).
It is also possible to state that an article is valid for all countries except ….
In such a case one should set the code Exclude to ‘1’. Country codes may not overlap.
When, for instance, three records are delivered for one article with the inclusion set for
‘EU’, ‘USA’, and ‘D’, this will not be permissible since D (Germany) is a member of the EU
and this was already specified as an inclusion.
All country codes for one article must either be set as inclusion or as exclusion. The
mixing of these specifications is not allowed.
Additive Additiv 066 1 N 0/1: Record builds a block with the parent
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Country in-/exclusions for the same reference number may not contradict one another.
Country codes may not overlap. When, for instance, three records are delivered for one
Article Number/OE Number combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’,
this will not be permissible since D (Germany) is a member of the EU and this was
already specified as an inclusion.
All country codes for an Article/reference number combination must either be set as
inclusion or as exclusion. The mixing of these specifications is not allowed.
The column Sort allow the sorting of the reference numbers (RefNo) below the Article-
number (ArtNo). The DMM R2 / PMD R2 allocate the Sort-numbers automatic, when
there’s not given a specified sequence by the user.
The ReferenzInfo allows to further define an article reference, e.g. if an article differs in
the scope of delivery from the part it refers to.
Exclude Exclude 054 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes:
This data table is to be used when the current article number supersedes another article SupersNo. Both the
superseding as well as the superseded articles must be contained in the data table (-> 200).
Country codes may not overlap. When, for instance, three records are delivered for one Article
Number/Superseded Number combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’, this will not be
permissible since D (Germany) is a member of the EU and this was already specified as an inclusion.
Each ArtNo must be contained in the data table (-> 200).
All country codes for an Article/Superseded Number must either be set as inclusion or as exclusion. The
mixing of these specifications is not allowed.
Recursion is not permitted (i.e. article A supersedes B, B supersedes C, C supersedes A).
The column Sort allow the sorting of the Trade-numbers (GebrNr) below the Article-number (ArtNr). The DMM
R2 / PMD R2 allocate the Sort-numbers automatic, when there’s not given a specified sequence by the user.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Describes what component parts PartNo makes up the main article ArtNo. Both article
numbers must be contained in the DT 200. The component part may contain further
parts lists, so that it may be contained again in the position ArtNo in the data table (->
205). Interleaving is random, a recursion (i.e. article A contains article B, article B
contains article C and article C again contains article A) is not permitted.
Country codes may not overlap. When, for instance, three records are delivered for one
Article Number/Parts List Article combination with the inclusion set for ‘EU’, ‘USA’, and
‘D’, this will not be permissible since D (Germany) is a member of the EU and this was
already specified as an inclusion.
All country codes for one Article/Parts List combination must either be set as inclusion
or as exclusion. The mixing of these specifications is not allowed.
A further use of this table is to create pseudo articles, which are then linked to vehicles
(or to other linkage targets). The components of a pseudo article should generally not
be linked as single components, but may only be shown in context with the other
components of the pseudo article. Two examples:
• A manufacturer offers motor oil in different package sizes and would like to
present them clearly. He therefore defines a pseudo article “Oil XY 10W40” and
add it as parts list components in table 205 the single package sizes which can be
ordered. By linking the pseudo article to a vehicle, the package sizes do not have
to be linked separately. If the manufacturer adds a further package size, it is
already added automatically to all vehicles of the pseudo article. In this case, it
could be that the 22 characters of the article number are not sufficient to describe
the pseudo article. In this case the additional article description of the pseudo
article should be used accordingly but the brand name should not be contained in
the additional article description.
Exclude Exclude 049 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Information texts on articles that could not be specified with criteria, (-> 210). The usage
of the data table (-> 210) for such information is always preferred.
Only information that relates exclusively to the article, irrespective of what vehicle the
article is linked to, may be specified here.
Text may be defined with different information types. The display sequence of the text
with different information types is regulated by means of the SortNr.
Country codes may not overlap. When, for instance, three records are delivered for one
Article/Sorting Number combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’, this
will not be permissible since D (Germany) is a member of the EU and this was already
specified as an inclusion.
All country codes for one Article/Sort. No. combination must either be set as an
inclusion or as exclusion. The mixing of these specifications is not allowed. Each article
must be contained in the data table 200.
Exclude Exclude 067 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country Code
is an inclusion.
FirstPage AnzSofort 068 1 (N) 0 = Trade number is only shown on the 2 nd article
page, 1 = Trade number is shown on the 1 st article
page.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Entry of generally accepted trade numbers (short codes) for the articles ArtNo that must
be contained in the data table (-> 200). This number can be used to search for the article
in the parts catalogue.
Trade numbers should not be duplicated for one article within one country.
Country codes may not overlap. When, for instance, three records are delivered for one
Article Number/Trade Number combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’,
this will not be permissible since D (Germany) is a member of the EU and this was
already specified as an inclusion.
All country codes for one Article/Trade Number combination must either be set as an
inclusion or as exclusion. The mixing of these specifications is not allowed. Each article
must be contained in the data table 200.
The column Sort allow the sorting of the Trade-numbers (TradeNo) below the Article-
number (ArtNo). The DMM R2 / PMD R2 allocate the Sort-numbers automatic, when
there’s not given a specified sequence by the user.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Note: The combination ArtNo and SeqNo1 must be contained in the DT205.
209 GTIN
Exclude Exclude 045 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes:
Entry of generally accepted GTIN for the articles ArtNo which must be contained in the data table (-> 200). This
number can be used to search for the article in the parts catalogue.
GTIN should not be duplicated for one article. A GTIN may have 8, 12 or 13 digits. Further details can be found
at https://www.gs1.org/standards/id-keys/gtin
Leading ‘0’ must not be ignored. Otherwise the result in general is not valid.
Country codes may not overlap. When, for instance, three records are delivered for one Article/GTIN
combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’, this will not be permissible since D (Germany) is a
member of the EU and this was already specified as an inclusion.
All country codes for one Article/GTIN combination must either be set as inclusion or as exclusion. The mixing
of these specifications is not allowed.
Each ArtNo must be contained in the data table (-> 200).
Contents: Fixed article criteria that are not related to vehicle links
Max. Length: 67
Sorting: ArtNo, SortNo
Primary Key: ArtNo, SortNo
Exclude Exclude 065 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Entry of explanatory criteria for an article ArtNo that must be contained in the data table
(-> 200).
Country codes may not overlap. When, for instance, three records are delivered for one
Article/Criteria combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’, this will not be
permissible since D (Germany) is a member of the EU and this was already specified as
an inclusion.
All country codes for an Article must either be set as inclusion or as exclusion. The
mixing of these specifications is not allowed.
Criteria may be used more than once within one country, but may then not contain
identical values.
Only criteria that are allowed for (-> 210) may be used (OK-Article = 1, -> 050).
1Criteriawith this code are displayed immediately on the first article page in the
presentation system, (Article Overview window).
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Note: Each article has at least one generic article associated with it.
If more than one generic article is assigned to an article, these generic articles must
have the same standard name (320.NArtNo).
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: The field CountryCode must be filled with a correct Country Code ( a blank is allowed for
“worldwide”).
If the field QuantPerUnit is filled, the field QuantUnit must be filled, too.
If the field StatusDat is filled, the field ArtStat must be filled, too.
If the fields QuantUnit and/or ArtStat are filled, it is not imperative to fill the fields
QuantPerUnit and/or StatusDat too, but it is strongly recommended
Every article should have an article-status in table 212 (Country-Specific Article-data).
Article-numbers, without any article-status in table 212, will get the default article-status 1
(Normal-status) per DVM (Data Validation Modul).
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: When LnkType 3, 4 or 5 is used in table 222 the criteria 2, 14, or 16 must not be used in
table 228 (Equals exclude one another!)
When the LnkType 3 (PC) is used in table 222, the criterion 16 must not be used in
table228.
When the LnkType 4 (CV) is used in table 222, the criterion 2 must not be used in table
228.
Criterion 2 = PC
Criterion 16 = CV
Criterion 14 = Engine
URL URL 100 300 (C) URL to which the link is made. Only if
DokumentenArt = URL
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes : Each DocNo/DocType – combination must contain a data record with the language number 255
(Universal); this will be displayed for languages that are not covered by the delivered languages.
The documents have to correspond to a document type in data table 014. Currently allowed are BMP,
PDF, JPG, PNG, GIF and URL.
The image name has to be stated with the document types BMP, PDF, PNG, GIF and JPG; the URL has
to be stated with the document type URL.
Rules for picture files of JPG, PNG and BMP type (starting November 2021)
We offer the possibility to make documents (!) available to the market not only as files via the distribution
platform but alternatively as a link (URL) to such documents.
For this purpose, we have integrated a new document type "URL" into the format and equipped the DMM R2 /
PMD R2 accordingly.
The entire TecAlliance catalog data exchange format is designed to exchange documents that can be displayed
in catalogs. Information on image type and standardized caption can be used to transmit documents for
different applications (image, installation instructions, safety data sheet, etc.).
The same applies to documents of the document type URL: Documents must be linked that correspond to one
of the use cases defined by the exchange format.
The following rules apply to this document type:
- The link must contain a valid URI according to RFC 39865
- Allowed network protocols are http and https
- The link must point to a document with one of the following file types:
BMP, JPG, JPEG, PNG, GIF, PDF, M4A, MP4, MPG, MPEG, AVI
- Also allowed are references to Youtube videos. The links must begin with the following string:
https://www.youtube.com/embed/
or
https://www.youtube-nocoookie.com/embed/
Please note that Youtube links are not available in some regions of the world.
- Further URL prefixes (analogous to youtube) can be requested from the TecAlliance for use, provided
that they obey the above rules and are used exclusively (!) for the reproduction of media content.
Extended rules for the document type "ZIP" (360° product images) (not yet avaliable)
This section has been removed from the documentation, as this information is exchanged via a separate
channel.
The TecDoc data maintenance software DMM/PMD is not used. The documents are not part of the regular data
packages.
You will receive information on this - after completion of the pilot project - as part of the regular Data
Distribution Mailings.
Exclude Exclude 034 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Multiple graphics are allowed for each article. One graphic can also be used by more
than one article.
The combination DocNo, DocType must be contained in the DT231.
The DocNo must be contained in the DT 231 and have the DocType ‘Article’ there.
When multiple Graphics are linked to one article we recommend to use the same
colour palette!
Notes: Origin is always left top. When Type = 1, then Y2 is a mandatory field!
Country restrictions for the whole graphic can be entered in DT 232.
The usage of “DokumentenArt” URL is not permitted (-> DT 014)
Contents: Fixed logistics article criteria that are not related to vehicle links
Max. Length: 61
Sorting: ArtNo, SortNo
Primary Key: ArtNo, SortNo
Exclude Exclude 060 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
Notes: Entry of explanatory logistics criteria for an article ArtNo that must be contained in the
data table (-> 200).
Country codes may not overlap. When, for instance, three records are delivered for one
Article/Criteria combination with the inclusion set for ‘EU’, ‘USA’, and ‘D’, this will not be
permissible since D (Germany) is a member of the EU and this was already specified as
an inclusion.
All country codes for an Article must either be set as inclusion or as exclusion. The
mixing of these specifications is not allowed.
Logistics criteria may be used more than once within one country, but may then not
contain identical values.
Only logistics criteria that are allowed for (-> 210) may be used (OK-Article = 1, -> 050L).
1Logisticscriteria with this code are displayed immediately on the first article page in
the presentation system, (Article Overview window).
Definition:
This table contains all packaging objects in the entire packaging hierarchy that are used to transport or store the
end user units as given in the basic article table 200. All packaging information given in table 200 is only
describing this end user unit.
The Article Packaging Items table 214 therefore always contains one or more objects of either the end user unit
(200.ArtNo) or another entry from table 214 in order to build a complete hierarchy from cardboard box up to a
pallet.
InclArtNo 049 22 U Article Number (-> 200) if item contains end user
unit (*)
(*)
To measure a product package you need to put the product on its natural base and then identify the default
front of the item.:
follows:
Height: from the base to the top
Width: the shorter side of the natural base
Depth: the longer side of the natural base
If it is not possible to identify a “Natural Base” the following measurement rules are given:
Height: the shortest dimension
Width: the next longest dimension
Depth: the longest dimension
For completeness the basic measurement rule for end user units is given here as well (needs to be considered
for logistics article measurement attributes in used in table 213):
PackArtNo If only a GTIN exists and no (internal) article number, the GTIN is
as well given in the field “PackArtNo”
Definition:
This table contains information if a packaging unit as specified in table 214 is restricted to certain countries.
Please note that no “Exclude” flag is given anymore. Countries always are provided as list of valid countries for
a specific Packaging Item. If no limitation is given the Packaging Item is valid in the same countries as the end
user unit (article as given in table 200).
218 Packaging Items Lot Sizes … New table in format version 2.6
Definition:
This table contains information about the number of packaging items that is typically shipped to customers.
This amount can be given as a general information (format 2.6) or for specific customers (later version).
ArtSwitch 022 1 C 0: end user unit (->200) ; 1: packing unit (-> 214)
RecipientID 034 4 (C) Just for distribution control – for future use
(*)If this field is missing, the data record just contains one entry per packaging item for the standard lot size for
the packaging item – if any exists. It is a mid term objective to make this information partly non-public what
means that supplier can provide information for specific recipients, e.g. special delivery options for single
wholesalers. Any projects with Data Supplier will be announced to the Data Users affected in due time.
Annotation:
A standard lotsize can either be defined based on the end user unit what then refers to entry in article table 200.
It can as well be given based on an existing packaging unit as soon as the specific lot size is provided via
several items of a package item. In this case ItemNo refers to a table 214 entry.
LnkTargetType VknZielArt 034 3 N Type of the linkage target (PC, CV, engine, …)
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Linkage of an article ArtNr, that is contained in the data table (-> 200), with a generic
article and vehicle as well as criteria. The combination Article Number and Generic
Article Number must be contained in the data table (-> 211).
In the key table 271 for the linkage target types, the current criteria number which
expressed a linkage since the format version 2.2 remained: (2 = PC-Ktype-No, 7 =
ManID-No, 14 = EngineNo, 16 = CV-Type-No, 19 = Axle-Type-No). Therefore, no
conversion of the values has to take place when making a format conversion.
Linkages of the same article with the same vehicle and the same generic article must
differ in any relevant point.
LnkTargetType VknZielArt 034 3 N Type of the linkage target (PC, CV, engine, …)
Exclude Exclude 070 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Notes: Listing of information text to article linkages that could not be specified in criteria, (->
410). Usage of the data table (-> 410) is always preferred.
Only information that is relevant to the use of articles in different vehicles may be
specified here. Information that is relevant only to the article, irrespective of the vehicle
wherein it is used, should be specified in the data table (-> 206).
Text can be defined with different types of information. The display sequence of text
with different information types in the presentation system is specified by means of the
SortNo.
Country in-/exclusions may not be contradictory. When a text is defined for the country
group ‘BEN’, additional text may not be included for the country ‘NL’.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
Comments: If the sorting is not specified for all articles linked to a linkage target, the articles without
explicit sorting order will be shown in ascending order of their article numbers after
those articles, which have an explicit sorting order.
If the data supplier does not specifiy a sorting, all articles for the linkage target are
sorted by their article number (and then after their SeqNo in the data table 400).
If an article with the same generic article is linked several times to the same linkage
target, the display of these linkages will be set by the SeqNo in the data table 400.
The data checks by TecDoc will not check the completeness of the sorting.
.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
LnkTargetType VknZielArt 034 3 N Type of the linkage target (PC, CV, engine, …)
Exclude Exclude 071 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
(*) Type ‘U’ starting Data Release 0519 – type ‘C’ until then
This is part of the TecDoc Format 2.5 extension and forms the first step to extend catalogue information with
data required for logistic purposes.
Amount of Articles
Combined Nomenclatura
Packaging Type
This list might be extended by further content of the DQM Data Guide in the future.
The language provided will be English in the first version. Further languages might follow in the future.
The two tables are only provided as CSV files according to structure as defined in chapter “TAF vs CSV” at the
beginning of this documentation. The table structure therefore contains no “Pos” column.
Source: TecDoc
Contents: Rules and guidelines for the correct use of specific TecDoc reference data content
Sorting: Usage, UniqueNumber 1, (UniqueNumber 2), (UniqueNumber 3)
Primary Key: Usage, UniqueNumber 1, (UniqueNumber 2), (UniqueNumber 3)
Source: TecDoc
Contents: Content for TecDoc® data guide – as plain text or as reference to a document
Sorting: DQMTermNo, LangNo(, SeqNo)
Primary Key: DQMTermNo, LangNo(, SeqNo)
(*)
The table allows just one entry for each Data-Guide entry. This entry contains a plain text of maximum 600
characters and/or a URL to a document attached.
The document type is not fixed and can be text based, an image or a video format.
(**)
Plain text and documents should always contain just one single language. Language Code 255 is therefore not
permitted in this table.