Show TOC

Exporting Translation DataLocate this document in the navigation structure

Use

Translation data includes the proposal pool for short texts and fingerprints for long texts and SAPscript forms and styles. This function allows you to export proposal pools and fingerprints at the same time or independently of each other. You should export in the following situations:

  • 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 short text translations in all of your systems, if you export the proposal pools from system <ABC> and import them into system <DEF>.

  • You have created fingerprints by translating long texts and/or SAPscript forms and styles 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 system <ABC> and import them into system <DEF>.

Prerequisites
  • Translation data must exist for the source and target language combinations for which you want to export.

    Note

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

    1. Call transaction SE16.
    2. Enter LXE_PP___1 in the Table Name field.
    3. Choose Enter.
    4. Enter the language key for the target language, such as enUS for English, in the T_LANG field.
    5. Enter the language key for the source language, such as deDE for German, in the S_LANG field.
    6. Choose Number of Entries.

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

    Note

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

    1. Call transaction SE16
    2. Enter LXE_FIPR in the Table Name field.
    3. Choose Enter.
    4. Enter the language key for the target language, such as enUS for English, in the T_LANG field.
    5. Enter the language key for the source language, such as deDE for German, in the S_LANG field.
    6. Choose Number of Entries.

    The system displays how many fingerprints are stored in this fingerprint table. If the number is 0, then there are no fingerprints for you to export 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 system itself. Alternatively you could use a directory on a server that the system can access. Ideally, the system into which the translation data needs importing can also access the directory to which you export the translation data. Otherwise, you will have to copy the proposal pool and/or fingerprint files to a different directory before you can import the data.
  • If you only want to export translation data for the source texts that appear in objects in a specific object list, then you must create the object list first.