4.2.34. Load language mapping (SuCri2OpenLanguageMapping)
On this page
Note: In the current development version, the SuCri2OpenLanguageMapping command has been discontinued. You edit the language map for the MTO in the vendor data editor (SuCri2VendorData).
Overview
The Language map (language mapping) defines the language in which the article descriptions appear in the MTO export. For each manufacturer there is an MTO language table in which the descriptions in additional languages are stored for each item code. Which language is used is determined by the MTO language setting.
Where can I find the function?
You open the table in the vendor data editor: dashboard (SuCri tab, Module 2 group, manufacturer button), Settings page, Vendor data... button, then the MTO language file for the desired manufacturer. Alternatively, you start the editor with SuCri2VendorData.
You select the language on the same Settings page under MTO language.
Plant 3D™ command
Property | Value |
Command | SuCri2VendorData (replaces SuCri2OpenLanguageMapping) |
Ribbon | SuCri > Module 2 > manufacturer button > Settings > Vendor data... > MTO language |
How it works in detail
MTO language table: Each row represents an item code. The columns have names of the form <language>_<description column>, for example a language column ENG or DEU combined with the property that is output as the article description in the MTO.
MTO language setting: With Default, the descriptions remain as they are in the model. If you select a language column, the MTO export replaces the description of every item whose item code is in the table with the entry for that language. Items without an entry keep their original description.
Editing: Adding and changing rows, exporting to Excel and importing again works as with all tables of the vendor data editor.
Earlier versions: There, SuCri2OpenLanguageMapping performed the same Excel conversion as SuCri2LoadDynamicProperty: select an Excel file, and each sheet is saved as a JSON file next to the Excel file.
Application examples
Example 1: English bill of materials for an international customer
Check in the MTO language table whether an English column is filled for the items used, set the MTO language setting to this column and run the MTO export.
Tips and best practices
- The item code is the key: A translation only takes place if the item code in the model exactly matches a row of the table.
- Column matching the description: The language column must match the property selected in the Article description column setting.
- Default for comparison: To check, briefly switch back to Default to see the original texts.
Troubleshooting
- Description remains untranslated: There is no row for the item code, or the column for the language and description type is empty.
- Table is read-only: The manufacturer is not licensed on this computer.
- SuCri2OpenLanguageMapping command unknown: It has been discontinued in the current version. Use SuCri2VendorData.
Related articles
- MTO in a different language, describes the output of the bill of materials in a different language.
- MTOArticleDescription, defines which property is output as the article description.
- MTO, creates the bill of materials in which the translation takes effect.
Copyright © 2026 by IntegaDesign GmbH. All Rights Reserved.