0% found this document useful (0 votes)
120 views

TecDoc-Data-Format Version 2022 Changes Public

Uploaded by

Perca Iulian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
120 views

TecDoc-Data-Format Version 2022 Changes Public

Uploaded by

Perca Iulian
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 28

TecDoc Data Format

Changes and adjustments in 2022

Author TecAlliance GmbH


Version 1.1
Date 17.03.2022
Status Public

TecAlliance GmbH Copyright © TecAlliance GmbH – The transfer or transmission of


Steinheilstrasse 10 this document in any form, also in part, requires the written
D-85737 Ismaning approval of TecAlliance GmbH.
Germany
TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

Change history

Source Target Published Place of change Short description of change


version version
1.0 06.12.2021 Initial Version

1.0 1.1 17.03.2022 Several changes Chapter 2.3:


following feedback Announcement on 200kB maximum filesize for image
files.
New chapters 2.4, 2.5, 2.6
Chapter 3.2:
Change in basic ruleset
Field validation removed
Chapter 3.3:
Rename changed field to UseCase to allow more than one
additional use case.
Chapter 3.5:
Some minor changes in fields of table
Chapter 5.1.1:
Change in LnkTargetType content
Primary Key change
Chapter 5.2:
Change in table numbers
Chapter 5.5:
Some clarification

Adding “not yet” implemented comments in chapters


that are not yet part of roadmap.

Page 2 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

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

3 New and extended content 12


3.1 Transmission Data ........................................................................................................................................ 12
3.2 DQM – Generic Articles and vehicle classes ............................................................................................... 13
3.3 “Spare Parts for Spare Parts” Use Case ....................................................................................................... 14
3.4 Model Series as Linkage target .................................................................................................................... 15
3.5 Reference Data Announcements (RemainToDelete List) ........................................................................... 16

4 Small and minor Changes 17


4.1 Parts Lists (table 217) ................................................................................................................................... 17
4.2 Safety Data Sheets ........................................................................................................................................ 18

5 Further changes in TecDoc Format 19

5.1 Extensions for electric mobility .................................................................................................................... 19


5.1.1 Engine output and vehicle performance ....................................................................................... 20
5.2 Alternative Country Representation (record count reduction) .................................................................... 21
5.3 Cross brand product references ................................................................................................................... 24
5.4 CV Sub-Type not used anymore ................................................................................................................... 27

6 Operational change in release schedule 28

© TecAlliance GmbH Page 3 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

1 General Information and Roadmap


This document summarises the proposed and scheduled changes to become part of the TecDoc Format in
2022.
To ensure compatibility with content of earlier versions we still leave those parts in the document that are not
yet scheduled – what does not necessarily mean that they will not be implemented.

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.

Most of the changes are build on feedback we received.

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.

Please send any feedback to your known TecDoc contacts or to [email protected]

Page 4 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

Schedule 2022
Data Release
Quarter

Chapter
Topic
Date

2223 13.06.2022 DQM 3.2


2223 13.06.2022 PK 232 2.1
2223 13.06.2022 PK 401 2.2
Q2 2223 13.06.2022 PK 206 2.5
2223 13.06.2022 PK 432 2.4
2223 13.06.2022 Safety Data Sheet 4.2
2213 04.04.2022 Real weekly updates 6

Q3 2236 12.09.2022 RemainToDelete 3.5

2241 17.10.2022 Electric Vehicles (engine output) 5.1.1


Q4
2241 17.10.2022 GTIN 14 (DMM version 7.2) 2.6

© TecAlliance GmbH Page 5 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

2 Breaking Changes
Breaking changes require customers who use the effected part of the data to adjust systems and interfaces.

2.1 Change Primary Key of table 232


(Allocation of Graphics to Article Numbers)

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.

Source: Data Supplier

Contents: The allocation of graphics to article numbers


Length: 47
Sorting: ArtNo, CountryCode, SortNo
Primary Key: ArtNo, CountryCode, SortNo

Name Old Name Pos Length Type Description

ArtNo ArtNr 000 22 U Article Number in the data supplier format

BrandNo DLNr 022 4 N Data Supplier Number Constant (Key 040)

TableNo SA 026 3 N Data Table Constant « 232 »

SortNo SortNr 029 2 N Sequential sorting number for graphics that


belong to the same article, starting with 1 per
article. Used to determine the order of display.

CountryCode LKZ 031 3 (C) Country Code (Key 010)

Exclude Exclude 034 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.

DocNo BildNr 035 9 N Unambiguous Graphics Number (->231)

DocType DokumentenArt 044 2 N Document Type (-> 014)

DeleteFlag Lösch-Flag 046 1 N const = 0

Page 6 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

2.2 Change Primary Key of table 401 (Linkage 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.

Source: Data Supplier

Contents: Search menu dependent information texts


Max. Length: 72
Sorting: LnkTargetType, LnkTargetNo, GenArtNo, ArtNo, SeqNo, CountryCode, SortNo
Primary Key: LnkTargetType, LnkTargetNo, GenArtNo, ArtNo, SeqNo, CountryCode, SortNo

Name Old name Pos Length Type Description


ArtNo ArtNr 000 22 U Article Number in the data supplier format
BrandNo DLNr 022 4 N Data Supplier Number Constant
TableNo SA 026 3 N Data Table Constant "401"
GenArtNo GenArtNr 029 5 N Unambiguous number of the Generic Article (-
>320)
LnkTargetType VknZielArt 034 3 N Type of the linkage target (PC, CV, engine, …)
LnktargetNo VknZielNr 037 9 N Number of the linkage target (KTypeNr, NTypeNr,
MotNr, HerIdNr, …)
SeqNo LfdNr 046 9 N Sequential number within the ArtNo-GenArtNo-
LnkTargetNo-linkage
SortNo SortNr 055 2 N Display sequence
CountryCode LKZ 057 3 (C) Country Code (-> 010)
InfType InfArt 060 3 N Information Type (KT 072)
FirstPage AnzSofort 063 1 N Immediate Display = 1: Information is shown on
the 1 st article page of the presentation system and
repeated in bold on the 2 nd article page.
TxtModNo TBSNr 064 6 C Text module
Exclude Exclude 070 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.
DeleteFlag Lösch-Flag 071 1 N Const=0

© TecAlliance GmbH Page 7 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

2.3 Image Document Types limitations

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.

Page 8 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

2.4 New: Change Primary Key of table 432


(Linkage-depended Graphics/Documents)

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.

Source: Data Supplier

Contents: The allocation of graphics to vehicle linkages


Max. Length: 73
Sorting: LnkTargetType, LnkTargetNo, GenArtNo, ArtNo, SeqNo, CountryCode, SortNo
Key: LnkTargetType, LnkTargetNo, GenArtNo, ArtNo, SeqNo, CountryCode, SortNo

Name Old name Pos Length Type Description

ArtNo ArtNr 000 22 U Article Number in the data supplier format

BrandNo DLNr 022 4 N Data Supplier Number Constant (Key 040)

TableNo SA 026 3 N Data Table Constant "432"

GenArtNo GenArtNr 029 5 N Unambiguous number of the Generic Article (-


>320)

LnkTargetType VknZielArt 034 3 N Type of the linkage target (PC, CV, engine, …)

LnkTargetNo VknZielNr 037 9 N Number of the linkage target (KTypNo, NTypNo,


EngNo, ManIDNo, …)

SeqNo LfdNr 046 9 N Sequential number within the ArtNo-GenArtNo-


LnkTargetNo-linkage

CountryCode LKZ 055 3 (C) Country Code (Key 010)

SortNo SortNr 058 2 N Sorting Order

DocNo BildNr 060 9 N Unambiguous DocNo (-> 231)

DocType DokumentenArt 069 2 N -> DT 014.

Exclude Exclude 071 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.

DeleteFlag Lösch-Flag 072 1 N const = 0

© TecAlliance GmbH Page 9 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

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.

Source: Data Supplier


Contents: Information text for articles
Max. Length: 51
Sorting: ArtNo, CountryCode, SortNo
Primary Key: ArtNo, CountryCode, SortNo

Name Old name Pos Length Type Description

ArtNo ArtNr 000 22 U Article Number in the data supplier format

BrandNo DLNr 022 4 N Data Supplier Number Constant

TableNo SA 026 3 N Data Table Constant « 206 »

Reserved Reserved 029 5 Former GenArtNr

CountryCode LKZ 034 3 (C) Country Code (-> 010)

SortNo SortNr 037 2 N Sorting for display

InfType InfArt 039 3 N Information Type (KT 072)

FirstPage AnzSofort 042 1 N Immediate Display = 1: Information is displayed


on the 1 st article page on the presentation
medium and is repeated boldly on the 2 nd page.

TXTModNo TBSNr 043 6 C Text Module Number

Exclude Exclude 049 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.

DeleteFlag Lösch-Flag 050 1 N const = 0

Page 10 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

2.6 New: GTIN 14 extension of table 209

The length of GTIN field needs to be extended as TecDoc data more and more includes items that are identified
with this standard.

Source: Data Supplier

Contents: GTIN (Global Trade Item Number)


Max. Length: 48
Sorting: ArtNo, GTIN, (CountryCode)
Primary Key: ArtNo, GTIN, (CountryCode)

Name Old name Pos Length Type Description

ArtNo ArtNr 000 22 U Article Number in the data supplier format

BrandNo DLNr 022 4 N Data Supplier Number Constant

TableNo SA 026 3 N Data Table Constant « 209 »

CountryCode LKZ 029 3 (C) Country Code (-> 010)

GTIN GTIN 032 14 N GTIN of articles

Exclude Exclude 046 1 (N) ‘1’ = Country Code is an exclusion, ‘0’ = Country
Code is an inclusion.

DeleteFlag Lösch-Flag 047 1 N const = 0

© TecAlliance GmbH Page 11 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

3 New and extended content

3.1 Transmission Data

Not yet scheduled

The existing tables 544, 545 and 546 are brought to life.

They are changed and extended by further tables in order to

- Provide transmission data for all vehicle types


- Maintain vehicle-transmission allocations
- Maintain vehicle-engine-transmission allocations
- Use Transmission as linkage target

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.

Tables 544, 545 and 546 remain unchanged


Table 546.NTypSubNo → “reserved”

New tables:
Table 547:. Allocation of a transmission to a PC (same as 546 – except NTypNo → KTypNo)

Page 12 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

3.2 DQM – Generic Articles and vehicle classes

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.

This worked and works fine in many cases.

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.

The new table contains of three basic elements:


The Generic Article Number
A valid engine type from key table 80

Source: TecDoc
Contents: Permitted allocations of Engine Types to Generic Articles (*)
Length: 15
Sorting: GenArtNo, EngineType
Primary Key: GenArtNo, EngineType

Name Pos Length Type Description

BrandNo 000 4 N Data Supplier Number Constant = 9999

TableNo 004 3 N Data Table Constant "340"

GenArtNo 007 5 N Generic Article Number (→320)

EngineType 012 3 C → Key Table 080

(*) Any combination is permitted in case a Generic Article does not appear in this table at all

© TecAlliance GmbH Page 13 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

3.3 “Spare Parts for Spare Parts” Use Case

Not yet scheduled.

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.

Name Old name Pos Length Type Description

ArtNo ArtNr 000 22 U Article Number in the data supplier format


BrandNo DLNr 022 4 N Data Supplier Number Constant (Key 040)
TableNo SA 026 3 N Data Table Constant « 222 »
LnkType VKN_ART 029 1 (N) Type of linkage (Vehicle Manufacturer, Model
Series, PC, CV, Engine Manufacturer, Engine)
LnkVal VKN_Value 030 6 (N) HerNr, KModNr, KTypNr, NTypNr or MotNr
SeqNo LfdNr 036 3 N Sequential Number
SortNo SortNr 039 3 N Sorting Number
AccArtNo ZArtNr 042 22 U Relevant accessory part, must be contained in
the DT 200, KZZub must be ‘1’ → <attention>!
Quantity Menge 064 3 N Quantity of accessory parts required
AccGenArtNo ZubGenArtNr 067 5 N Unambiguous number of the accessory generic
article (-> SA320)
UseCase Reserviert 072 1 (C) Indication of use cases that differ from the
accessory use case:
‘1’: AccArtNo is a spare part for the article ArtNo
TermNo BezNr 073 9 (N) Description Number (->030)
DeleteFlag Lösch-Flag 082 1 N const = 0

Page 14 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

3.4 Model Series as Linkage target

Not yet scheduled.

Today the following Linkage targets are possible to use inside the linkage tables 400 ff:

- Passenger Cars / kTYpe (Target Type 2)


- Commercial Vehicles / nType (Target Type 16)
- Engines (Target Type 14)
- Axles (Target Type 19)
- CV Producer IDs (Target Type 7)

- New: Model Series (Target Type 1)


TargetNo is a valid reference to table 110 (KModNo)

Structure of table 400ff remains unchanged.

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.

© TecAlliance GmbH Page 15 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

3.5 Reference Data Announcements (RemainToDelete List)

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.

However the existing Remain To Delete List will be provided as usual.

Source: TecDoc
Contents: Announcements for Reference Data deletions
Length: tbd
Sorting: DelType, DelNo, DelStatus
Primary Key: DelType, DelNo, DelStatus

Name Pos Length Type Description

BrandNo 000 4 N Data Supplier Number Constant = 9999

TableNo 004 3 N Data Table Constant= <tbd>

RdaType 007 3 K Type of object to be announced for deletion


(-> Key table <tbd>)

DelNo 010 9 N ID of object to be announced for deletion

DelStatus 019 3 N Status information (-> Key Table <tbd>)

DelDataRelease 022 4 N Data Release of deletion

DelDate 026 6 (D) Date of deletion YYYYMMDD (Publication)

ReplacementNo 035 9 (N) Number of object the replaces the one that is
(proposed to be) deleted

Reason 044 3 K Reason for deletion (-> Key Table <tbd>)

Comment 047 100 (C) Additional comment (English)

Page 16 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

4 Small and minor Changes


4.1 Parts Lists (table 217)

Not yet scheduled

Proposed changes:

- Field LangNo will not be used anymore.


- The field is set to “reserved”
- No change in position of the other field in table

Source: Data Supplier

Content: The allocation of coordinates to context-sensitive graphics


Length: 51
Sorting: ArtNo, SeqNo, DocNo, DocType, LangNo
Primary Key: ArtNo, SeqNo, DocNo, DocType, LangNo

Name Old name Pos Length Type Meaning

ArtNo ArtNr 000 22 U Article Number in the data supplier format

BrandNo DLNr 022 4 N Data Supplier Number (040)

TableNo SA 026 3 N Constant ‘217’

SeqNo LfdNr 029 3 N Sequential Number from DT 205

DocNo BildNr 032 9 N Unambiguous Graphics Number


( 100.000 * DatSupNo., < 100.000 * (DatSupNo. +
1))

DocType DokumentenAr 041 2 N Document Type (014)


t

Reserved LangNo 043 3 N Former field Language Number (Key 020)

CoordNo KoordinatenNr 046 4 N Coordinate Number

DeleteFlag Lösch-Flag 050 1 N const = 0

© TecAlliance GmbH Page 17 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

4.2 Safety Data Sheets


This is not a real change but a clarification of how a safety data Sheet should be delivered and how a catalogue
system etc. might indicate and distinguish Safety Data Sheets from other documents.

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.

Page 18 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

5 Further changes in TecDoc Format

5.1 Extensions for electric mobility

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.

Please wait for our announcements in first quarter 2022.

© TecAlliance GmbH Page 19 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

5.1.1 Engine output and vehicle performance

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

Name Pos Length Type Description

BrandNo 000 4 N Data Supplier Number Constant = 9999

TableNo 004 3 N Data Table Constant= <tbd>

LnkTargetType 007 3 N 2: KTyp vehicle in table 120


16: NTyp vehicle in table 532
14: EngNo in table 155

LnkTargetNo 010 9 N KTyp, NTyp or EngNo

PowerOutputType 019 3 N → KT <tbd>

FuelType 022 3 N → KT 182

KW 025 5 N Power output

Page 20 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

5.2 Alternative Country Representation (record count reduction)

Not yet scheduled.

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.

© TecAlliance GmbH Page 21 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

252 Article Country Restrictions


Source: Data Supplier

Contents: Country information for an article


Length: 530
Sorting: ArtNo
Primary Key: ArtNo

Name Pos Length Type Description

ArtNo 000 22 U Article Number in the data supplier format

BrandNo 022 4 N Data Supplier Number Constant

TableNo 026 4 C Data Table Constant « 252 »

CountryArray 030 500 C Comma separated list including ISO2-Country


Codes as given in table 010. ISOCode2 or in the
official ISO publications. The countries always
indicate where the information (the article) is
valid to be displayed in catalogue systems.

Page 22 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

453 Country Restriction of Linkage

Source: Data supplier

Contents: Country restriction of the linkage


Length: 556
Sorting: LnkTargetType, LnkTargetNo, GenArtNo, ArtNo, SeqNo
Primary Key: LnkTargetType, LnkTargetNo, GenArtNo, ArtNo, SeqNo

Name Pos Length Type Description


ArtNo 000 22 U Article number in the data supplier format
BrandNo 022 4 N Data supplier number (Key 040)
TableNo 026 4 N constant "453"
GenArtNo 030 5 N Unambiguous number of the generic article (-
>320)
LnkTargetType 035 3 N Type of the linkage target (PC, CV, engine, …)
LnkTargetNo 038 9 N Number of the linkage target (KTypeNr, NTypeNr,
MotNr, HerIdNr, …)
SeqNo 047 9 N Sequential number within the ArtNo-GenArtNo-
LnkTargetNo-linkage
CountryArray 056 500 C Comma separated list including ISO2-Country
Codes as given in table 010. ISOCode2 or in the
official ISO publications. The countries always
indicate where the information (the article) is
valid to be displayed in catalogue systems.

© TecAlliance GmbH Page 23 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

5.3 Cross brand product references

Not yet scheduled

The following use cases need to be solved:

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:

Customer has a product that is required to use/install other products.

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.

Page 24 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

A proposal for the two tables looks like this:

Source: TecDoc

Contents: Permitted Generic Article Allocation


Length: 30
Sorting: GenArtNo1, (CritNo1), UseCase, GenartNo2, (CritNo2)
Primary Key: GenArtNo1, (CritNo1), UseCase, GenartNo2, (CritNo2) (*)

Name Pos Length Type Description


BrandNo 000 4 N Data Supplier Number Constant = 9999
TableNo 004 3 N Data Table Constant= 321
GenArtNo1 007 5 N → 320
CritNo1 012 4 (N) → 050
UseCase 013 1 C ‘0’: both use cases permitted
‘1’: only “requires” use case permitted
‘2’: only “is needed” use case permitted
GenArtNo2 022 5 N → 320
CritNo2 026 4 (N) → 050

(*) A blank entry is a valid “value” as well

This table includes the permitted allocations as provided by Data Suppliers in new table 240:

“requires” use case:


GenArtNo1/CritNo1 indicates the product group that requires a product from another product group given
by GenArtNo2/CritNo2

“is needed” use case:


GenArtNo2/CritNo2 indicates the product of a product group the is needed to use/install a product of
another product group GenArtNo1/CritNo1

© TecAlliance GmbH Page 25 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

Source: Data Supplier

Contents: Product Allocation


Length: 65
Sorting: GenArtNo1, (CritNo1), (CritVal1), GenartNo2, (CritNo2), (CritVal2) (*)
Primary Key: GenArtNo1, (CritNo1), (CritVal1), GenartNo2, (CritNo2), (CritVal2) (*)

Name Pos Length Type Description


BrandNo 000 4 N Data Supplier Number Constant = 9999
TableNo 004 3 N Data Table Constant= 240
UseCase 007 1 C → 321 (field UseCase)
ArtNo 007 22 (C) → 200
GenArtNo1 007 5 N → 320
Crit1 012 4 (N) → 050
CritVal1 016 20 (C)
GenArtNo2 036 5 N → 320
Crit2 041 4 (N) → 050
CritVal2 045 20 (C)

(*) A blank entry is a valid “value” as well

This table needs to be validated against permission in table 321 as follows:

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)

UseCase = ‘1’ (“requires”)


240.GenArtNo1/CritNo1 = 321. GenArtNo1/CritNo1
AND
240.GenArtNo2/CritNo2 = 321. GenArtNo2/CritNo2
UseCase = ‘2’ (“is needed”)

Page 26 of 28 © TecAlliance GmbH


TecDoc Data Format - Changes and adjustments in 2022
1.1, Document property “Status”, 17/03/2022

240.GenArtNo1/CritNo1 = 321. GenArtNo2/CritNo2


AND
240.GenArtNo2/CritNo2 = 321. GenArtNo1/CritNo1

5.4 CV Sub-Type not used anymore

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:

538, 539, 540, 543, 546, 550, 551, 552, 553

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.

© TecAlliance GmbH Page 27 of 28


TecDoc Data Format - Changes and adjustments in 2022
1.1, , 17/03/2022

6 Operational change in release schedule


Starting April 2022 the Data Package infrastructure changes to a really weekly delivery where the main events
always happen on the same day in week as follows:

Thursday: Data delivery Deadlines


Monday: Delivery of Data Packages and Reference Data
Wednesday: Update of TecAlliance Online Solutions (Webservice, Catalogue, …)

The official calendar will be published via the regular data Distribution mailing and in the download area of
https://www.tecalliance.net

Page 28 of 28 © TecAlliance GmbH

You might also like