Show TOC

Procedure documentationImporting Proposal Pools Locate this document in the navigation structure

 

Before you import proposals, see Proposal Pool Transports and Exporting Proposal Pools for the benefits of importing existing proposals into a new system where you intend to translate and an explanation of basic concepts.

Prerequisites

  • You must be confident that the proposals you exported are of an acceptable translation quality. Otherwise you will just be spreading errors from one system to the next.

    • Why not organize a proposal pool cleanup in the source system before exporting proposals? For more information, see DEMS Objects for Quality Assurance.

    • To play it safe, you could export or import only those proposals with a specific quality status or higher, as long as you are confident that only experienced translators create proposals with high quality statuses.

  • The proposal pool file(s) that you exported must be available in a directory that the target system can access.

Procedure

  1. In the target system, call up transaction LXE_MASTER and choose   Goto   Proposal Pool   Import  .

    The Import screen appears.

  2. Enter the 4–character language ID for the source language in the S_LANG field.

  3. Enter the 4–character language ID for the target language in the T_LANG field.

    You can also use the input help (F4) on these fields to display a list of the available source and target languages.

  4. In the DIRECTRY field, enter the name of the directory that contains the proposal pool file to be imported.

  5. In the FILENAME field, enter the name of the export file.

  6. In the COMMENT field, you can enter a comment on the proposal pool import. A record of each proposal pool import job is stored in table LXE_PP_IMP and a meaningful comment would help you to recognize it later.

  7. If you want to import all proposals available in the file, you can leave the default settings unchanged and proceed to step 9 of this procedure.

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

    • To import only proposals with status A, enter 90 in the MIN_STAT field.

    • To import only proposals with status S or higher, enter 60 in the MIN_STAT field.

  9. If the target system already contains proposals (see Prerequisites in Exporting Proposal Pools on how to check this) you need to decide whether the proposals in the target system should be overwritten with the proposals from this file — in cases where conflicting proposals exist for the same source text in the target system and file to be imported.

    • If no proposals exist for this source language and target language combination in the target system, leave the NO_UPDTE field blank.

    • If proposals already exist for this source language and target language combination in the target system, and you are not sure of their quality, leave the NO_UPDTE field blank.

      This ensures that in cases of conflicts, the proposals in the target system are overwritten with the proposals in the file to be imported.

    • If proposals already exist for this source language and target language combination in the target system, and you want them to remain unchanged by this import, enter an X in the NO_UPDTE field.

  10. Make sure that the BATCH field contains an X and choose F8 to schedule this job to run in the background.

  11. Repeat this procedure for the next source language and target language combination for which you want to import the proposal pool

Result

The system imports the proposals from the file in accordance with the criteria you specified.

Refer to the spool to see how many proposals have been imported.

Example Example

Source Language:

deDE

Target Language:

enUS

Statistics

Imported

Total

PP

2.050

2.058

PPA

40

40

PPX

5

5

This means that the following proposals for source language German and target language English have been imported:

  • 2.050 system standard / application standards.

    8 of these proposals were not imported, due to the fact that proposals already existed for the source texts in question in the source system, and the NO_UPDTE field contained an X when the import criteria were defined (step 9 of the Procedure above.

  • 40 abbreviations

  • 5 exceptions

End of the example.

The system creates an entry in table LXE_PP_IMP so that you have a permanent record of this import job.