News Archive
New allocations of engines to KType vehicles
New allocations of engines to KType vehicles
Close gap on KType data and start allocating engines where still missing.
Please refer to April mailing for more details.
The list of new allocations is available here.
January 28, 2022
Model Series names changes in versions 0221 – 0521
Model Series names changes in versions 0221 – 0521
Model Series names changes in versions 0221 – 0521
March 30, 2021
Corrections SKODA OCTAVIA - 0521
Deletions of Motorcodes in release 0919
Deletions of Motorcodes in release 0919
We have announced the deletion of a large number of motor codes for the reference data version 0919 in due time. Since this is an unusually large number and a total of 2503 vehicles are affected, we would like to point out to all data suppliers that they may have to adapt to a large number of changes in this way as well. The brands affected are AC, AM GENERAL, BUICK, BUICK (SGM), CADILLAC, CHEVROLET, CHEVROLET (SGM), GMC, HOLDEN, HSV (HOLDEN SPECIAL VEHICLES, HUMMER, ISUZU, OLDSMOBILE, PONTIAC, SAAB, SATURN and VAUXHALL. Please refer to this list for more details.
05-June-2019
Keytable 271
Keytable 271 – new entries with DR0119Keytable 271 – new entries with DR0119
In preparation for the recently announced rollout of new and more flexible data exchange structures, further types of linkage targets will be defined for data exchange. New entries will be made in key table 271 with Data Release 0119.
Data delivery on September
Data delivery on September, 24th 2018 - ContiTech becomes Continental CTAM (Brand Number 31)Data delivery on September, 24th 2018 - ContiTech becomes Continental CTAM (Brand Number 31)
Continental is realigning its brand strategy to meet the special requirements of dealers and workshops in the aftermarket. For data users of the ContiTech brand (brand number 31 – manufacturer no. 531), this means that the brand name in the TecAlliance catalogs will change to Continental CTAM. The brand number and manufacturer number remain unchanged and nothing changes in the products. In connection with the new brand name, a changed brand logo will also be sent for the first time with the data on September 24, 2018.
Removal of country specific deviation on capacity liter
Removal of country specific deviation on capacity liter
For a better identification of differences in vehicles we decided to remove capacity liter from ktypes.
Each deviation will lead to a creation of a Ktype and will be implemented in the Release 1220.
This affects 50 Ktypes, the complete list of changes can be found here.
Transport encryption of e-mails
Transport encryption of e-mails
For some time now, the transfer between the TecAlliance eMail Gateway and the mail provider has been carried out using TLS for transport encryption. In order to encrypt the entire mail dispatch on the transport route, we recommend to activate the TLS transport encryption on the mail gateway(s) of your company.
Extended Unicode Support will start March 2019
Extended Unicode Support will start March 2019
Version 4.1 of the Data Manager enables Unicode data exchange in additional fields.
The extension includes:
– Brand name in record type 001 (header record)
– All text fields in the company address data (Tables 040 du 043 in TAF 2.4 ff)
– The short indicator in the manufacturer table 100
– All appearances of the article number
For details, please refer to the format descriptions 2.4 and 3.0-2019/01 as of version 1.1.0.8.
The first data packages with the extension used can occur with Data Release 0519.
Decompress TecDoc Data Packages
Decompress TecDoc Data Packages
We recommend to use the most up to date version of the 7z tools to decompress the files of the regular data packages.
As of DR1018 please use at least version 16.02.
Change in validations inside the Data Manager
Change in validations inside the Data Manager
With version 4.0 (delivered in December), the following validations are transferred from the status “Warning” to the status “Error”. We have already informed about this in May 2018 by mailing:
1316: Criteria value must conform with the character set from ISO-8859-1
1342: TBSNo may only contain printable characters (7-bit ASCII [ -~])
These changes become effective with data updates as of DR0219
Furthermore, with version 4.1 in March 2019, violations of the rules for numerical criteria will be considered “errors”. These rules were also documented in May 2018 mailing:
Errorcodes 1372, 1373, 1374, 1375
– Characters “0” to “9”, comma “,” as well as plus “+” and minus “-” are permitted
– A comma may not be used at the beginning or end of the value
– A comma may only be used once within a value
– Only the comma may be used as the decimal separator
– Thousands separators must not be used
– Exactly one “+” or exactly one “-” may only be used at the beginning of a numeric value
– Spaces must not be used
– All(!) characters are part of the maximum length of an attribute.
These changes become effective with data updates as of DR0519
Please check your current error logs carefully for warnings. Please correct the defects at the latest at the specified times. Otherwise the complete articles including links will be excluded from the data transfer.
Valid prefixes for documents of document type URL
Valid prefixes for documents of document type URL
With version 4.0 (delivered in December), the following validations are transferred from the status “Warning” to the status “Error”. We have already informed about this in May 2018 by mailing:
1316: Criteria value must conform with the character set from ISO-8859-1
1342: TBSNo may only contain printable characters (7-bit ASCII [ -~])
These changes become effective with data updates as of DR0219
Furthermore, with version 4.1 in March 2019, violations of the rules for numerical criteria will be considered “errors”. These rules were also documented in May 2018 mailing:
Errorcodes 1372, 1373, 1374, 1375
– Characters “0” to “9”, comma “,” as well as plus “+” and minus “-” are permitted
– A comma may not be used at the beginning or end of the value
– A comma may only be used once within a value
– Only the comma may be used as the decimal separator
– Thousands separators must not be used
– Exactly one “+” or exactly one “-” may only be used at the beginning of a numeric value
– Spaces must not be used
– All(!) characters are part of the maximum length of an attribute.
These changes become effective with data updates as of DR0519
Please check your current error logs carefully for warnings. Please correct the defects at the latest at the specified times. Otherwise the complete articles including links will be excluded from the data transfer.
Change in validations inside the Data Manager
Change in validations inside the Data Manager
With version 4.0 (delivered in December), the following validations are transferred from the status “Warning” to the status “Error”. We have already informed about this in May 2018 by mailing:
1316: Criteria value must conform with the character set from ISO-8859-1
1342: TBSNo may only contain printable characters (7-bit ASCII [ -~])
These changes become effective with data updates as of DR0219
Furthermore, with version 4.1 in March 2019, violations of the rules for numerical criteria will be considered “errors”. These rules were also documented in May 2018 mailing:
Errorcodes 1372, 1373, 1374, 1375
– Characters “0” to “9”, comma “,” as well as plus “+” and minus “-” are permitted
– A comma may not be used at the beginning or end of the value
– A comma may only be used once within a value
– Only the comma may be used as the decimal separator
– Thousands separators must not be used
– Exactly one “+” or exactly one “-” may only be used at the beginning of a numeric value
– Spaces must not be used
– All(!) characters are part of the maximum length of an attribute.
These changes become effective with data updates as of DR0519
Please check your current error logs carefully for warnings. Please correct the defects at the latest at the specified times. Otherwise the complete articles including links will be excluded from the data transfer.
Reference Data Archive
Termination of CV model groupings
Termination of CV model groupings
In the area of N-types, a number of model series have been grouped together, especially at Scania. For example, the 5534 model series with “P,G,R,T – series”.
We have decided to dissolve this grouping. For the N-types, the N-type number will remain the same, if possible. It could also lead to the splitting of N-types like 8289 with “P 230, R 230”.
The changes will become effective with the Reference data Version 0321 that will be published to Data Supplier on February, 2nd 2021
A list of effected NType numbers is available here.
09-December 2020
Removal of country specific deviation on capacity liter
Removal of country specific deviation on capacity liter
For a better identification of differences in vehicles we decided to remove capacity liter from ktypes.
Each deviation (field “Lit” in table 120 will lead to a creation of a vehicle (KType) and will be implemented in the Release 1220.
This affects 50 KType, the complete list of changes can be found here.
28-October 2020
Change in Country Specific Model Names
Change in Country Specific Model Names
If a vehicle is sold in a market area with two different names, we currently did use a slash for capturing those. As example „BRIO / SPAZIO“ is valid for Argentina. We have decided to become more granular and create new model series and the related KTypes. The current model-series stays untouched, the complete list of affected model names can be found here.
We will start the implementation in release 0221 and will complete it in 0321.
09-December-2020
Data correction on engine codes
Data correction on engine codes
For a more precise identification of vehicle- and spare parts information on VIN level, we need to align our engine codes with the EPC writing of the vehicle manufacturer. Since engine codes are one of the most important attributes, we want to inform you about our planned changes.
We analyzed the current engine codes and compared them with the engine codes used in the EPCs.
You can find our results of the changes here.
We plan to implement those changes within the Reference Data Version 0321.
30-September-2020
Hybrid vehicles in TecDoc Reference Data
Hybrid vehicles in TecDoc Reference Data
Following several requests for a more detailed description of hybrid vehicles we like to inform about recent and future activities and changes.
In our May-Mailing, we have informed about our activities on hybrid vehicles.
We have now analyzed our current vehicle-tree and hav identified the future hybrid types.
Please check out the list of changes in our Data Distribution Wiki at tecalliance.net for our results.
We will apply the hybrid changes within the main-release RD1220 – distributed on November, 2nd to all data suppliers and on November, 14th as part of all data packages.
23-July-2020
India: Optimized country allocation on vehicle data
India: Optimized country allocation on vehicle data
To extend the acceptance of the TecDoc system in India and therefore to help products to be sold in this market by using TecDoc data some unnecessary vehicles (kType only) are removed from the reference data with immediate effect.
22-June-2020