Exporting the Proposal Pool 

Use

You can only transport proposal pools if the proposal pool(s) has/have already been exported from the source system(s). You can export the entire proposal pool or just part of the proposal pool.

When exporting or importing a proposal pool, you can set parameters to restrict the exported and/or imported data. For example, if a proposal pool already exists in the target system, or if you need to import proposal pools from several systems into the target system, you can avoid conflicts when the data is imported by setting appropriate export and/or import parameters. Such conflicts can arise if the same source text has different translations in different proposal pools, and these various translations all exist at the same level (that is, as a system standard or application standard for the same domain) and with the same quality status. You can export the following parts of a proposal pool individually or in combination with each other:

·        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

·        Date on which proposal was first entered for the source text

·        Translator who first translated the source text

·        Date of last change

·        Translator who last changed a translation

·        Export of proposals only

·        Export of abbreviations only

·        Export of exceptions only

·        Export of proposals for all of the objects in an object list.

·        For examples of proposal pool exports, see the examples below.

You do not have to import the exported proposal pool file in its entirety. The import parameters enable you to import just parts of the export file. You should therefore ask yourself whether you want to import the export file into just one other system, or whether you want to import the export file into more than one system. The latter scenario can arise if a translation system is used as the basis of many other translation systems, or if its terminology is considered the standard on which terminology in other translation systems is based.

If you only want to import the export file into one other translation system, you are advised to set the export parameters so that they meet as many of the target system’s requirements as possible. This reduces the size of the export file, and accelerates the transport process. However, if you intend to import the export file into numerous translation systems, you are advised to perform a complete export and then use the import parameters to ensure that only relevant data is imported into each target translation system.

Prerequisites

A source system exists with a proposal pool containing proposals that are suitable for the target system.

You are authorized to start reports in transaction SE38 and write export files to a directory. This directory could be the source system’s transport directory. However, it could also be any other directory on a server or computer that the source system can access.

 

Procedure

...

       1.      In the source system, call transaction SE38.

       2.      Start report RS_TRANSLATION_EXPORT_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.

You can also use the input help function to display a list of available source and target languages.

       4.      Specify the name of the export directory under DIRECTRY, and the name of the export file under FILENAME.

You are advised to enter a meaningful name for the export file. You could use the following naming convention:

TRM<source language ID><target language ID>.<system ID>

For example, TRMDE.BA1 indicates that this export file was created to export the proposal pool (translation memory = TRM) with source language German and target language English from translation system Banken1. The export file does not have a preset file name extension.

       5.      If the language ID in the target system consists of two characters, select the SIMP_LNG field.

       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 export proposals irrespective of the domain type, enter *.

       7.      If you want to export 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 export proposals from all domains, enter * in the field.

If you want to export proposals from several domains, start a separate export for each domain.

       8.      Enter the numerical value of the quality status as of which proposals are exported in the MIN_STAT field.

       9.      If you only want to export the proposals created by a specific translator, enter this translator’s user name in the F_NAME field. If you want to export proposals created by all translators, enter *.

If you want to perform separate exports of proposals created by several translators, start a separate export for each translator.

   10.      Enter the creation date as of which proposals are exported in the F_DATE1 field. Enter the creation date up to which proposals are exported in the F_DATE2 field.

   11.      If you only want to export the proposals that were last changed by a specific translator, enter this translator’s user name in the L_NAME field. If you want to export proposals created by all translators, enter *.

   12.      Enter the last change date as of which proposals are exported in the L_DATE1 field. Enter the last change date up to which proposals are exported in the L_DATE2 field.

   13.      To export proposals, select the FL_PP field. If you do not want to export proposals, leave the field blank.

   14.      If you want to export abbreviations, select the FL_PPA field. If you do not want to export abbreviations, leave the field blank.

   15.      The FL_PPX field enables you to export exceptions. If you do not want to export exceptions, leave the field blank.

For example, if you only want to export abbreviations, just select the FL_PPA field. If you want to export abbreviations and proposals, select the FL_PP and FL_PPA fields.

   16.      To start the export as a background job, select the BATCH field.

If you execute the report online, the export job could quickly terminate. This depends on the timeout setting for online processes in your system. You are therefore advised to schedule these export jobs as background processes.

   17.      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.

   18.      If necessary, repeat the procedure for each additional domain to be exported, or for each additional translator whose proposals need to be transported. If you require proposal pools from several source systems, follow the same procedure in the other source systems.

Export of proposals for objects in an object list

If you want to export proposals for objects in a specific object list that was created in transaction LXE_MASTER:

...

       1.      Access transaction SE38 and call up the report RS_TRANSLATION_EXPORT_PP_II.

       2.      Use the input help for the OBJLIST field to select the required object list.

       3.      Maintain the other fields as described above.

 

Result

The system creates an export file containing proposals that satisfy the criteria you entered.

 

Example

Complete Export 1

To translate version 2 of your bank software, you want to set up a new translation system called Banken2 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.

You export the entire proposal pool for German and English from translation system Banken1 with the following parameters:

 

T_LANG	EN	DE
DOMATYP	*	*
DOMANAM	*	*
MIN_STAT	1	1
SIMP_LNG	<no selection>	<no selection>
F_NAME	*	*
F_DATE1	01.01.2002	01.01.2002
F_DATE2	<current date>	<current date>
L_NAME	*	*
L_DATE1	01.01.2002	01.01.2001
L_DATE2	<current date>	<current date>
FL_PP	X	X
FL_PPA	X	X
FL_PPX	X	X
BATCH	X	X

 

Complete Export 2

Basic domains such as the ABAP domains Basis (BC), Financial Accounting (FI), and Payroll (PY) have been translated since January 01, 2001 in translation system Standard1. You assume that some of these domains are needed as a basis for translation in many other areas, such as a banking system for asset/liability management and another system for loans. You therefore run a complete export from the Standard1 system, but only import proposals into other translation systems for the domains that exist in both the source and target translation systems. You enter the export settings as described under Complete Export 1.

Partial Export

You need to set up a new banking translation system called Banken2. It will be used to translate banking-specific texts from the NetWeaver 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 Basis 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.

You run a complete export for German and English from translation system Banken1. You do this by following the instructions under Complete Export 1.

You run a partial export from translation system Standard1 using the following parameters:

 

T_LANG	DE	EN
DOMATYP	R	R
DOMANAM	BC	BC
MIN_STAT	90	1
SIMP_LNG	<no selection>	<no selection>
F_NAME	*	*
F_DATE1	01.01.2001	01.01.2001
F_DATE2	<current date>	<current date>
L_NAME	*	*
L_DATE1	01.01.2001	01.01.2001
L_DATE2	<current date>	<current date>
FL_PP	X	X
FL_PPA	X	X
FL_PPX		X
BATCH	X	X