Show TOC

Procedure documentationExporting Translation Data Locate this document in the navigation structure

 

Translation data includes both fingerprints (for long texts) and the proposal pool (for short texts). This function allows you to export fingerprints and proposal pools in separate files at the same time. We recommend using the translation data export function to transport translation data to another system. You should export in the following situations:

  • You have created fingerprints by translating long texts and saving them actively in system ABC. Now translation is to start in system DEF. You can save time and money if you export the fingerprints from ABC and import them into system DEF.

  • You have created proposals while translating short texts in system ABC. Now translation is to start in system DEF. You can save time and money and ensure consistent translations across your systems, if you export the proposal pools from ABC and import them into system DEF.

Prerequisites

  • Translation data must exist in the source system for the source and target language combination for which you want to export.

    You can check whether fingerprints exist for a specific source and target language combination:

    1. In the source system, call transaction SE16, enter LXE_FIPR in the Table Name field and choose Enter.

    2. Enter the 4–character language ID for the target language in the T_LANG field (for example, enUS for English).

    3. Enter the 4–character language ID for the source language in the S_LANG field (for example, deDE for German).

    4. Choose Number of Entries.

      The system displays how many fingerprints are stored in this fingerprint table. If this number is 0, then there are no fingerprints for this source and target language combination.

    You can check whether proposals exist for a specific source and target language combination:

    1. In the source system, call transaction SE16, enter LXE_PP___1 in the Table Name field and choose Enter.

    2. Enter the 4–character language ID for the target language in the T_LANG field (for example, enUS for English).

    3. Enter the 4–character language ID for the source language in the S_LANG field (for example, deDE for German).

    4. Choose Number of Entries.

      The system displays how many proposals are stored in this proposal table. If this number is 0, then there are no proposals for this source and target language combination.

  • You need to pinpoint a directory to which you export the translation data. You could use the transport directory of the source system. Alternatively you could use a directory on a server that the source system can access. Ideally, the target system can also access the directory to which you export the translation data. Otherwise, you will have to copy the fingerprint and/or proposal pool files to a directory that the target system can access.

  • If you only want to export translation data for the source texts that appear in objects in a specific object list, then the object list must exist. For more information, see Creating Object Lists.

Procedure

There are two different procedures for exporting translation data, depending on whether you want to export according to the objects in an object list or not.

Exporting Translation Data of Objects in a Specific Object List

  1. In the source system, call transaction LXE_MASTER and choose   Transport   Translation Data   Export   (or choose Ctrl + F1).

    The Export Translation Data screen appears.

  2. In the Directory field, enter the name of the directory to which you want to export the translation data.

  3. Enter the 4–character language ID in the Target Languages field of the target language(s) for which you want to export translation data. You use either F4 input help or select one of the following pushbuttons:

    • Multiple Selection (Multiple Selection) allows you to enter more than one 4–character language code at once.

    • Insert from Graphs (Insert from Graphs) inserts all of the target languages that are translated according to the translation graphs.

    • Translation Languages (Translation Languages) inserts all target languages defined in transaction LXE_MASTER.

  4. Select the Object List Export checkbox and use F4 on the Object List field to select the object list that you want to use as the basis for this export.

    Note Note

    It is not possible to select more than object list. If you want to use the objects in multiple object lists as the basis for the export, you need to merge them first.

    End of the note.

  5. In the field Description (Optional), we recommend that you enter a meaningful description for your translation data exports so that you can easily recognize them later in table LXE_LOG_DATA_TRP.

  6. In the Data Selection group box, use the checkboxes to specify whether you want to export fingerprints, proposal pools, or both.

    Note Note

    If you choose to include proposal pools in your export, the following checkboxes are relevant to you in the Proposal Pool Options group box:

    • The Old Language Keys checkbox is relevant if the target system for this proposal pool export runs on Basis Release 6.40 or lower. If the target system for this proposal pool export runs on Basis Release 7.00 or higher, leave this checkbox unselected.

    • The Add Best Proposal checkbox ensures that, in addition to exporting the proposals used as the translation of the source texts for the objects in this object list, you also export the best proposals for this source texts in the cases where a proposal other than the best proposal is used to translate the source text.

    End of the note.

  7. Schedule this job to run in the background using   Program   Execute in Background   or by pressing F9.

Exporting Translation Data not Based on a Specific Object List

  1. Call transaction LXE_MASTER and choose   Transport   Translation Data   Export   (or choose Ctrl + F1).

    The Export Translation Data screen appears.

  2. In the Directory field, enter the name of the directory to which you want to export the translation data.

  3. Enter the 4–character language ID in the Target Languages field of the target language(s) for which you want to export translation data. You use either F4 input help or select one of the following pushbuttons:

    • Multiple Selection (Multiple Selection) allows you to enter more than one 4–character language code at once.

    • Insert from Graphs (Insert from Graphs) inserts all of the target languages that are translated according to the translation graphs.

    • Translation Languages (Translation Languages) inserts all target languages defined in transaction LXE_MASTER.

  4. In the field Description (Optional), we recommend that you enter a meaningful description for your translation data exports so that you can easily recognize them later in table LXE_LOG_DATA_TRP.

  5. If necessary, enter a source language in the Source Language (Optional) field. If you do not enter a source language, the system will export fingerprints and/or proposal pools for all of the target languages that you specified irrespective of their source language.

  6. In the Data Selection group box, use the checkboxes to specify whether you want to export fingerprints, proposal pools, or both.

  7. If you want to export the complete proposal pool, for the specified source and target languages combinations, leave the default settings unchanged and proceed to step 11 of this procedure.

    Note Note

    If you choose to include proposal pools in your export, the following checkboxes are relevant to you in the Proposal Pool Options group box:

    • The Old Language Keys checkbox is relevant if the target system for this proposal pool export runs on Basis Release 6.40 or lower. If the target system for this proposal pool export runs on Basis Release 7.00 or higher, leave this checkbox unselected.

    End of the note.

  8. If you want to export only those proposals that were created or changed since a specific date, then enter this date in the Change Date (From) field.

  9. If you want to export only those proposals that have a specific minimum quality status, then proceed as follows:

    • To export only proposals with status A, select A using F4 help in the Quality Status (From) field.

    • To export only proposals with status S or higher, select S using F4 help in the Quality Status (From) field.

  10. If you want to export only those fingerprints that were created by a specific user, enter the user name in the Last Changed By field in the Fingerprints Options group box. Likewise, if you want to export only those fingerprints changed since a specific date, then enter this date in the Change Date (From) field. Or enter a date range using the Change Date (To) field.

  11. Schedule this job to run in the background using   Program   Execute in Background   or by pressing F9.

Result

The system creates export files containing the fingerprints that satisfy the criteria you specified. If you chose to export proposal pools as well, then these are stored in separate files. The file names are generated automatically and look like this:

  • FIPR_deDE.ABC contains fingerprints for target language German from source system ABC.

  • P_deDE_enUS.ABC contains a proposal pool for source language German and target language English from source system ABC.

You can view your translation data exports in table LXE_LOG_DATA_TRP.