System Translation- Export

SAP Menu > Tools > ABAP Workbench > Utilities > Translation > System translation > /DBME//TMA_EXP - Translations – Export

Below are explained:

Transaction: /DBME/TMA_EXP - Translations – Export

System Translation – Transaction Menu

Translation Languages

The Export transaction allows to choose source language and up-to two target translation languages:

Export parameters – Translation Languages

Translation Objects

One of three types of the translation objects can be selected:

Export parameters – Translation Objects

Development Objects

Selection of Development Objects can be done based on combination of the following parameters:

• Package,
• Request/Task,
• Object Type (using lookup Help),
• Name of Translation Object (ex. Report name),
• Type of Translation Object (using lookup Help).

Export parameters – Development Objects

Also, it is possible make selection through Application-Tree by clicking on the “Application-Tree” button and selection of the Application Components:

Export parameters – Application-Tree

Customizing Objects

There are four possibilities to select Customizing Objects:

• Selection from Application-Tree:

Export parameters – Selection of Customizing from Application-Tree

• Selection from IMG:

Export parameters – Selection of Customizing from IMG

• Selection of Customizing Object by Name:

Export parameters – Selection of Customizing by Name

• selection of Customizing Object by Request / Task:

Export parameters – Selection of Customizing by Request/Task

Fiori File

To export fiori fields for translation, provide a path to fiori properties source file and/or fiori target files. Source file is obligatory.

Export parameters – Fiori file

Parameters

It is possible to choose whether “All texts” or “Non-translated only” texts will be translated. Also, there is an option to mark ‘Take proposals’:

Export parameters – Control parameters

“All texts” or “Non-translated only”

Parameters (Radio buttons):      All texts (default)

                                                Non-translated only

By default the transaction exports All texts – including the already translated. It is possible to export “Non-translated only” texts.

“Take proposals”

Parameter (Checkbox):              Take proposals

Texts from ‘Proposal Text’ column in the excel file (if there are any) will be copied into the ‘Translation’ column.

“LText – strict paragr. Match”

The program performs the analysis of the long text in the source language and the target language. Based on the content of the texts in the source and target language the program makes a decision, if the translation is needed or not. However, in case of updates, this analysis can be deactivated: if the long text in the target language exists and the parameter is turned off, the text is considered as translated (is considered as already properly translated – will not be added to the excel).

“Tab/View only if MView exists”

If turned off, the database tables / database views are considered as relevant for the translation.

If turned on, the database tables / database views are considered as relevant for the translation only if a maintenance view exists for the table / view. This allows to treat the database tables / views as technical objects (which in general do not have to be translated), but if the maintenance views exists for them, then they start to be relevant for translation (usually the case of configuration or master data tables / views).

Handling of the exceptions

You specify on the selection screen the objects which are the subject for the translation. You can specify on the selection screen for example, that the data elements in the given packages are relevant for the translation in general.

There can be cases however, when you would like to indicate: “This, this and this object is the exception: they are not to be translated. I would like to mark them as not relevant for translation. Once marked, they should be considered as exceptions, not relevant for translation”.

By means of the transactions /DBME/TMA_EXCPT_SM30 or /DBME/TMA_EXCPT_SE16 you maintain the list of objects which are to be considered as not relevant for translation. The exceptions are stored in the database table /DBME/TMA_EXCPT. Depending on the transaction you choose, you will be directed either to the transaction SM30 or SE16N (both maintaining the content of the same database table /DBME/TMA_EXCPT). SM30 should be considered as more state of art approach, however the maintenance using SE16N (because of export to excel, copy & paste, etc.) may be more convenient for you, especially if the number of exceptions is big (e.g. you have long list of exceptions in the Excel).

You specify the object type and object identifier in this table. These are the values which you usually enter in the transaction SE63 (e.g. ‘DTEL’ corresponds to the translation of the data element, ‘DE’ corresponds to the translation of the long text of the data element).

Please notice, that this table is mandant independent table. When using the maintenance view you are not asked for the transport – you maintain the list of exceptions on the development system directly, there is no need to send the content of the table to other systems (to the quality system or the productive system). However if you have such need (e.g. to copy from one development system to another development system) do it manually or by means of any tools you know.

Execute transaction

After selecting the data, it should be possible to execute the transaction. The Excel screen with run result will be shown:

Export Translations – Excel screen

The data can be saved into File:

Export Translations – Save export

Export Translations – Save export as ...

Before passing to translator the saved file can be opened and edited using MS Excel.

Please see Data Extraction Procedure for more details.