TecDoc-Data-Format Version 2022 Changes Public
TecDoc-Data-Format Version 2022 Changes Public
Change history
Contents
1 General Information and Roadmap 4
2 Breaking Changes 6
2.1 Change Primary Key of table 232 (Allocation of Graphics to Article Numbers) .......................................... 6
2.2 Change Primary Key of table 401 (Linkage Text Modules) .......................................................................... 7
2.3 Image Document Types limitations ............................................................................................................... 8
2.4 New: Change Primary Key of table 432 (Linkage-depended Graphics/Documents) .................................. 9
2.5 New: Change Primary Key of table 206 (Article Text Modules) ................................................................. 10
2.6 New: GTIN 14 extension of table 209 .......................................................................................................... 11
They are – in most cases – designed as AddOns what means that each user should be able to use the TecDoc
Format in an unchanged way and is free to add the changes to the interfaces whenever it seems best.
We think that the proposed changes include topics that are going to help to improve the entire TecDoc Data
Supply Chain and with that should support you to sell more products and services.
Please note that the extensions become official as soon as they will be added to the well known TecDoc Format
documentation.
The following roadmap indicates the Data Release for the change to become effective in productive TecDoc Data
Distribution environment.
That means that the data is available in any Data Package or IDP based interface as well as it can be used and/or
maintained inside TA PIM system(s) as well as via the IDP Data Supplier API.
Please note that some of the proposed extensions are not yet part of the roadmap
This does not necessarily mean that hey will not be implemented during 2022 or later. It just indicates that there
are pending issues in terms of content, quality rules and other relevant topic for a productive usage in TecDoc
infrastructure.
Any change in roadmap will be communicated via the regular Data Distribution mailings.
We reserve the option to implement or publish schedules for AddOns that do not have impact on existing data
processing at any time.
Schedule 2022
Data Release
Quarter
Chapter
Topic
Date
2 Breaking Changes
Breaking changes require customers who use the effected part of the data to adjust systems and interfaces.
The field “CountryCode” will be added to the Primary Key in order to avoid increasing risk of overflows in field
(SortNo). A “blank” Country Code is a valid “Key” as well.
We regard this to be the less “breaking” change as the positions of the fields are not changed and as we think
that grouping for countries is probably already part in most of the implementations.
Exclude Exclude 034 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
The field “CountryCode” will be added to the Primary Key in order to avoid increasing risk of overflows in field
(SortNo). A “blank” Country Code is a valid “Key” as well.
We regard this to be the less “breaking” change as the positions of the fields are not changed and as we think
that grouping for countries is probably already part in most of the implementations.
The amount of documents to be distributed via the TecDoc data distribution platforms is still increasing. This is
basically good news as the product images are an important part of today’s catalogue systems.
However the size of images is becoming a problem. While in the past the size of documents in TecDoc Data
was not part of some validation it now becomes a key success factor for the acceptance of data to limit the
size of images as the amount of downloads for a data user is a time (and cost) consuming process. The
TecDoc data today contains about 1,4 TB of documents – and the trend is further upwards.
Therefore we kindly ask all data suppliers to limit the size of image files and PDF documents to a maximum size
of 200kB.
Especially users of BMP format are recommended to change the format to JPG (or BMP) as BMP file format is
not compressed.
As the first announcement for that dates back to June 2021 we may implement the limitation at any time after a
notification via Data Distribution mailing.
Please note that this is not a breaking change in terms of the format structure. This remains unchanged.
The field “CountryCode” will be added to the Primary Key in order to avoid increasing risk of overflows in field
(SortNo). A “blank” Country Code is a valid “Key” as well.
We regard this to be the less “breaking” change as the positions of the fields are not changed and as we think
that grouping for countries is probably already part in most of the implementations.
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.
2.5 New: Change Primary Key of table 206 (Article Text Modules)
The field “CountryCode” will be added to the Primary Key in order to avoid increasing risk of overflows in field
(SortNo). A “blank” Country Code is a valid “Key” as well.
We regard this to be the less “breaking” change as the positions of the fields are not changed and as we think
that grouping for countries is probably already part in most of the implementations.
Exclude Exclude 049 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
The length of GTIN field needs to be extended as TecDoc data more and more includes items that are identified
with this standard.
Exclude Exclude 046 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
The existing tables 544, 545 and 546 are brought to life.
The first step in 2022 is to integrate the already existing passenger car transmission and add the missing
allocations from
- Vehicle to transmission (new table 547 – or adjustment of table 546)
- Engine to transmission (new table 548 – no content available)
This is about the combination of engine/transmission that can be or is linked to the TecDoc vehicles.
New tables:
Table 547:. Allocation of a transmission to a PC (same as 546 – except NTypNo → KTypNo)
Maintenance of product linkages to vehicles are often based on more or less automated processes where
products are linked to groups of vehicles following company specific rules and algorithms.
However as the diversity of vehicles is increasing we are facing more linkages that contain some useless and
incorrect information – like allocation of exhaust related products to an electric vehicle.
Providing better information for electric and hybrid vehicles is one part of improving the situation. TecAlliance
will announce and implement reasonable changes in 2022.
It is further intended to make up allocations of Generic Articles to Engine Types (Key Table 80 entries) to
support data maintenance and to allow a validation of data in order to avoid these constellations.
Source: TecDoc
Contents: Permitted allocations of Engine Types to Generic Articles (*)
Length: 15
Sorting: GenArtNo, EngineType
Primary Key: GenArtNo, EngineType
(*) Any combination is permitted in case a Generic Article does not appear in this table at all
In many use cases the product to be part of the TecDoc data is not directly linked to vehicle but to a more
complex spare part (like an alternator). These more complex and expensive spare parts might be subject to an
own repair-case but there is no official option today to link these parts.
The only similar options to use the accessory structure for these use cases. This is often done so by some
brands but it does not really fit as an accessory is something else as a spare part.
However – the accessory structure fits to this use case and table 222 offers an unused reserved field at
position 72.
This will be named to “IsSparePart”, is optional and can be set to ‘1’ in case the article AccArtNo is a spare part
and not an accessory for the article ArtNo.
Today the following Linkage targets are possible to use inside the linkage tables 400 ff:
Attention:
In case you are going to use this option as a data supplier you need to take care of changes in the allocation of
vehicles to model series in order to keep your data up-to-date and to avoid wrong linkages.
The announcements of major changes in the TecDoc reference data today is provided in Excel and PDF files
that are hard or even impossible to use for an automated process.
Reference Data will therefore be extended by information about proposed deletions or significant changes like
changing a criteria’s name.
Source: TecDoc
Contents: Announcements for Reference Data deletions
Length: tbd
Sorting: DelType, DelNo, DelStatus
Primary Key: DelType, DelNo, DelStatus
ReplacementNo 035 9 (N) Number of object the replaces the one that is
(proposed to be) deleted
Proposed changes:
1) You can use any Document Type (table 014) except 01 (BMP) or 07 (GIF)
2) Table 231.DocTermNo must be set to value ‘6’ (Safety Data Sheet)
(The field is named “Standard Description” in DMM)
In most cases the documents probably will be delivered as PDF files or as URL (linking to the document hosted
by the supplier).
However the content is under the responsibility of the supplier. He needs to take care that he required
information is provided.
It is often requested to adjust and extend the existing data - especially the vehicle information – to be 100%
ready to meet the challenges of electric mobility vehicles and products.
One AddOn about extended power information about vehicles in general and about electromobility in particular
is already designed and proposed below.
Further necessary extensions are still under discussion and will be published as soon as we have an aligned and
reliable proposal.
Not all performance is the same. Especially when it comes to vehicles containing electric engines the
performance figures might be based on different physical key figures.
For that reason another table is added to allocate multiple power outputs to linkage targets in general and
vehicles in particular.
Source: TecDoc
Contents: Power Output
Length: 30
Sorting: LnkTargetType, LnkTargetNo, PowerOutputType, FuelType
Primary Key: LnkTargetType, LnkTargetNo, PowerOutputType, FuelType
Current way to provide country information is not very efficient. Each record is just able to store one country or
country group. In a growing number of cases this results in a significant increase of records in some data tables
(e.g. 202, 212, 403).
On top of this the number of countries together with the option to use the exclude feature makes the
interpretation of the data a challenge sometimes.
Therefore we like to offer – as a first pilot – an additional way to represent the country information in a Data
Package table. The basic idea is to have one record that contains a comma separated list including all countries
the content is valid for.
We are going to start with the most important tables – 202 and 403 - where the most benefit is expected.
Further tables might be added.
This information will be added to your data package. So you are free to leave your entire data processing
unchanged. And you are invited to check and test the new data and – if you like – let it become part of your data
processing routines.
In the end each record is much longer then the ones today but the amount of records and the amount data will
decrease and – very important – there is no doubt about the interpretation.
Important annotation:
This is just a feature for the Data Package output. It is not intended to make this part of the import routines of
DMM. It might by the way be an interesting information that the IDP system is going to work exactly this way
whenever country information is required. No structures are repeated but an array of country codes is part of
any content related structure.
Customer has a product and claims to provide the information that the usage/installation of this product
requires another product that is not part of the customers product portfolio.
e.g.: the producer of windshields wants to inform that a specific sort of glue is required to install the windshield
– reference is only to specify a product (group) and not a specific product of a specific brand.
Vice versa:
e.g.: the producer of glue wants to inform that a specific glue is required to use/install specific windshields.
To solve this – basically to additional information objects need to be added to the TecDoc data:
1) An option for the supplier to link a product to product groups (Generic Articles) incl. the option to
specify the allocation target with one or more criteria.
a. Extended option might be to link all products of a product group (Generic Article) of a suppliers
portfolio to product groups (of other suppliers)
b. The allocation need to incl an indicator to distinguish the two meanings of the allocation.
2) A new Reference Data information object indicating permitted allocations (pairs of Generic Articles) to
avoid data waste right from the start.
Source: TecDoc
This table includes the permitted allocations as provided by Data Suppliers in new table 240:
UseCase = ‘0’
(240.GenArtNo1/CritNo1 = 321. GenArtNo1/CritNo1
AND
240.GenArtNo2/CritNo2 = 321. GenArtNo2/CritNo2)
OR
(240.GenArtNo1/CritNo1 = 321. GenArtNo2/CritNo2
AND
240.GenArtNo2/CritNo2 = 321. GenArtNo1/CritNo1)
The CV subtype information has not been maintained for a long time.
We will stop the delivery of tables 534 and 535 and will further not maintain the CV Sub Type anymore:
In order not to break the format we leave the table and its keys unchanged. The field NTypSubNo is therefore
always set to constant value ‘000’
It is intended to evaluate the approach and we will – if required – come back with a more reliable structure
and/or content based on a future-proof structure.
The official calendar will be published via the regular data Distribution mailing and in the download area of
https://www.tecalliance.net