Importing the Proposal Pool
Use
If you
import
proposal pools
into a translation system, translations that have been written before in other
translation systems are made available in this translation system to support
the translation of different objects. This enables you to access
proposals created
in other translation systems, which means you do not need to retranslate
source texts that have already been translated in other systems. However,
there is also a danger of you transporting the
wrong translations from one translation system to another, or translations whose terminology is incorrect.
This is particularly likely to happen if translations are written for specific
domains, but defined in the proposal pool as system standards instead of
application standards. The same applies if there is a large gap between the
release levels of both systems, such as if the source system is on Release
4.6B but the target system is on Release 7.00. It is safe to assume in such
cases that major terminology changes have occurred between the two releases.
To avoid such situations, use the following criteria to restrict the data that
is imported from the export file:
● Source language
● Target language
● Domain type
● Domain
The domain is the equivalent of the highest component level of the application component hierarchy in earlier releases of the ABAP environment.
● Quality status
● Export of proposals only
● Export of abbreviations only
● Export of exceptions only
If you import proposal pools from several source systems, and if different proposals exist in these proposal pools for the same source text, and if these various proposals are all assigned to the same level (system standard, application standard) and have the same quality status, then the proposals are all inserted at the same level and with the same quality status into the target system’s proposal pool. This turns the best proposal and automatic distribution into a lottery for this source text because any of the coexistent proposals could be selected.
Prerequisites
The proposal pool has been exported from at least one suitable source system.
You are authorized to run reports using transaction SE38. The target system can access the directory that contains the files to be imported.
Procedure
...
...
1. In the target system, call transaction SE38.
2. Start report RS_TRANSLATION_IMPORT_PP.
3. Enter the source language in the S_LANG field, and the target language in the T_LANG field. Each of these entries consists of four characters.
4. Enter the name of the directory that contains the proposal pool export file to be imported under DIRECTRY. Specify the name of the export file under FILENAME.
5. In the COMMENT field, you can enter a comment on the proposal pool import.
6. Enter the name of the domain type under DOMATYP.
The domain type for ABAP applications is R. The domain type for non-ABAP applications is X. If you want to import proposals irrespective of the domain type, enter *.
7. If you want to import proposals that belong to a specific domain, enter the name of the domain in the DOMANAM field. For example, BC for proposals from the Basis domain. If you want to import proposals from all domains included in the export file, enter * in the field.
If you do not want to import proposals that belong to domains included in the proposal pool export file, you must start a separate import for each domain to be imported.
8. Enter the numerical value of the quality status as of which proposals are imported in the MIN_STAT field.
9. To import proposals, select the FL_PP field. If you do not want to import proposals, leave the field blank.
10.
If you want
to import
abbreviations,
select the FL_PPA field. If you do not want to import
abbreviations, leave the
field blank.
11.
The FL_PPX
field enables you to import
exceptions. If you
do not want to import exceptions, leave the field blank.
For example, if you only want to import abbreviations, just select the FL_PPA field. If you want to import abbreviations and proposals, select the FL_PP and FL_PPA fields.
12. To start the export as a background job, select the BATCH field.
13. Choose Execute (F8).
If you selected the BATCH field in step 13, the report is executed in the background. Otherwise, the report is executed online.
14. If necessary, repeat this procedure for each additional domain to be imported. If you require proposal pools from several source systems, follow the same procedure for each export file.
The more proposal pools you import into your target system from different source systems, the greater the risk of conflicts occurring.
Result
The system writes proposals from the export files into the target system’s proposal pool in accordance with the criteria you selected.
Example
Complete Import
To translate version 2 of your bank software, you want to set up a new translation system for English, German, French, and Spanish. Version 1 of this software has been translated into English and German in translation system Banken1 since January 01, 2001. The domains in the source and target text systems all originate from the NetWeaver area and are virtually identical. You do not want to make any terminology changes. The complete proposal pool has already been exported from translation system Banken1.
You import the entire proposal pool for German and English from translation system Banken1 with the following parameters:
T_LANG |
DE |
EN |
DOMATYP |
* |
* |
DOMANAM |
* |
* |
MIN_STAT |
1 |
1 |
FL_PP |
X |
X |
FL_PPA |
X |
X |
FL_PPX |
X |
X |
BATCH |
X |
X |
Partial Import
You need to set up a new banking translation system called Banken2. It will be used to translate banking-specific texts from the ABAP domain Bank Components (IS-B), and texts from the NetWeaver domain Basis (BC), into English and German. The banking-specific texts have been translated into German and English in translation system Banken1 since January 01, 2002. The NetWeaver texts have been translated into German, English, French, and Italian in translation system Standard1 since January 01, 2001. Translation system Standard1 is also used to translate texts from the NetWeaver domains Financial Accounting (FI), Payroll (PY), and Logistics (LO). However, you do not need these domains in translation system Banken2. A number of inexperienced translators have recently translated into German in translation system Standard1 and you have not had time to check the quality of these translators’ work. You are satisfied with the quality of the English translations. The proposal pools in translation systems Banken1 and Standard1 have already been exported in their entirety.
You import the complete proposal pool from translation system Banken1, as described under Complete Import.
You import the proposal pool from translation system Standard1 using the following parameters:
T_LANG |
DE |
EN |
DOMATYP |
R |
R |
DOMANAM |
BC |
BC |
MIN_STAT |
90 |
1 |
FL_PP |
X |
X |
FL_PPA |
X |
X |
FL_PPX |
|
X |
BATCH |
X |
X |