Show TOC

Exporting Translation Data Without an Object ListLocate this document in the navigation structure

Prerequisites

See the list of prerequisites in Exporting Translation Data.

Procedure

  1. Call transaction LXE_MASTER and choose Start of the navigation path Transport Next navigation step Translation Data Next navigation step Export End of the navigation path.

    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 language keys in the Target Languages field of the target language(s) for which you want to export translation data. You use the input help to specify one target language, or select one of the following pushbuttons:
    • Multiple Selection allows you to enter several language keys.
    • Insert from Graphs inserts all of the target languages that have been defined in the translation graphs.
    • Translation Languages inserts all of the target languages that have been defined on the Languages tab in transaction LXE_MASTER.
  4. Do not select the Object List Export checkbox.

    This makes the Object List field irrelevant.

  5. In the field Description (Optional), you are advised to enter a meaningful description for your translation data exports so that you can easily recognize them later in table LXE_LOG_DATA_TRP.
  6. If necessary, enter a source language in the Source Language (Optional) field. If you do not enter a source language, the system exports proposal pools and fingerprints for all of the specified target languages irrespective of their source language.
  7. In the Data Selection group box, use the checkboxes to specify whether you want to export proposal pools, fingerprints, or both.
  8. Maintain the parameters in the Proposal Pool Options group box to determine which proposals are included in the export.
    • If you want to export the entire proposal pool for the specified source and target language combinations, leave the default settings unchanged.
      Note The default settings ensure that all existing proposals are exported. Deleted proposals are not included in the export.
    • If you only want to export proposals for a specific domain, use the input help to specify the domain in the Domain Name field.
    • If you only want to export proposals with specific quality statuses, use the input help for the Quality Status (From) and Quality Status (To) fields to specify the required quality statuses.
      Example

      If you only want to export proposals with status A, use the input help to select A for both fields.

      If you only want to export proposals with quality statuses S and A, use the input help to select S in the Quality Status (From) and A in the Quality Status (To) fields.

      Note

      If you want the proposal pool file to include deleted proposals, make sure that the Quality Status (From) field is empty. If you want to restrict the proposal pool export to deleted proposals only, make sure that the Quality Status (From) and Quality Status (To) fields are both empty.

      You can only import deleted proposals into a system that is on SAP NetWeaver 7.0 or higher. In the case of the following SAP NetWeaver releases, you can only import deleted proposals if the system is also on the following Support Package level or higher:

      SAP NetWeaver 7.0 SP26

      SAP NetWeaver 7.0 EHP1 SP11

      SAP NetWeaver 7.1 SP14

      SAP NetWeaver 7.1 EHP1 SP09

    • If you only want to export proposals that were created or changed during a specific period, maintain the Creation Date (From), Creation Date (To), Change Date (From), and Change Date (To) fields.
      Example

      If you only want to export proposals that were changed after January 01, 2010, enter 01.01.2010 in the Change Date (From) field.

    • If you only want to export proposals that were created or last changed by a specific translator, enter the translator's name in the Created By or Last Changed By fields.
    • Use the checkboxes to determine whether the export includes standard proposals (that is, system standards and domain standards), abbreviations, or exceptions. You can select more than one checkbox.
    • The Old Language Keys checkbox must be selected if the target system for this proposal pool export runs on SAP NetWeaver 6.20 SP25 (or higher), or SAP NetWeaver 6.40. If the target system for this proposal pool export runs on SAP NetWeaver 7.0 or higher, do not select this checkbox.
  9. Maintain the parameters in the Fingerprints Options group box to determine which fingerprints are included in the export.
    • If you want to export all fingerprints for the specified source and target language combinations, leave the default settings unchanged.
    • If you only want to export fingerprints that were last changed by a specific translator, enter the translator's name in the Last Changed By field.
    • If you only want to export fingerprints that were changed during a specific period, maintain the Change Date (From) and/or Change Date (To) fields.
  10. Schedule the job to run in the background by choosing Start of the navigation path Program Next navigation step Execute in Background End of the navigation path.

Results

The system creates export files containing the proposals and fingerprints that satisfy the criteria you specified. Proposals and fingerprints are stored in separate files. The file names are generated automatically and look like this:

  • P_deDE_enUS.ABC contains proposals for source language German and target language English that were exported from system <ABC>.
  • FIPR_deDE.ABC contains fingerprints for target language German from source system <ABC>.

You can view your translation data exports in table LXE_LOG_DATA_TRP.

Next Steps

Importing Translation Data
Related Information