Start of Content Area

Function documentation Proposal Pool Transport  Locate the document in its SAP Library structure

Use

Whenever a new translation system is set up or a development (or part of a development) moves from one translation system to another, you may need to transport the proposal pool from the source system (such as the legacy system, a general reference system, or the system previously used to translate the development) to the new translation system (target system). This ensures that the target system contains proposals for translations that already exist. The source text lines in question therefore have the translation status Translated and do not need to be edited again. You can also use translations stored in the source system’s proposal pool for source text lines that need to be translated in the new translation system, or for which you want to perform automatic distribution.

 

Prerequisites

A suitable proposal pool exists. For example, it originates from one of the following systems:

·        Legacy system of the system to be set up

·        General reference system

·        System in which the imported development, or part of a development, was originally translated

 

Features

You can transport a translation system’s entire proposal pool to another translation system, or you can transport just part of a proposal pool (delta). For example, you could restrict the transport to proposals changed after a certain date, or proposals that belong to a specific domain. When deciding whether to export the entire proposal pool or just part of the proposal pool, you must consider the following:

·        Type of target system

¡        If you set up a translation system whose contents are based on an existing translation system (for example, a translation system in which a later release of the same product is translated), it is usually the case that many of the translation-relevant domains match. (Domains are the approximate equivalent of components in earlier releases of the ABAP environment.) In this situation, it is a good idea to import the source system’s entire proposal pool. The prerequisite is that the quality of proposals in the source system’s proposal pool is satisfactory. For more information, see the next point.

¡        If just some of the target system’s contents match the contents of an existing translation system (for example, part of a development moves from one system to another), it is usually the case that most domains do not match. In this situation, you should only transport that part of the proposal pool for which the target system contains suitable source text entries.

Example

The standard translation system at your company has been used to translate source texts from the domains Basis (BC), Financial Accounting (FI), Payroll (PY), and Logistics (LO). A new translation system for the area of banking is needed to translate source texts from the domain Bank Components (IS-B), and source texts from the domains BC and FI. The domains PY and LO are irrelevant for the banking translation system. In this situation, you should only transport the proposal pool for the domains BC and FI from the standard translation system to the banking translation system.

·        Quality of Existing Proposal Pool

¡        If you transport a proposal pool, all of the source text lines in the target system for which the transported proposal pool contains valid translations are assigned the translation status Translated. This means they are no longer automatically included in translation worklists. Therefore, you should only transport proposal pools if you are sure that their translations are relevant and correct for the new translation system. However, if you know that the legacy system contains many translations whose terminology is incorrect (because the legacy system’s proposal pool already contains a mixture of other systems’ proposal pools, for example, or because the translations in the legacy system are incorrect), you are advised to refrain from importing the proposal pool into the new translation system or to use a proposal pool from a reference system whose terminology is correct.

§         If you do not import a proposal pool, the system cannot assign valid proposals to the translations in the new translation system, so that the translations are assigned the translation status Modified. You can then check the quality of the translations manually. However, if you import a proposal pool from a reference system whose terminology is correct, translations that were created in your new translation system’s legacy or original system will probably be missing. The advantage though is that you can be sure the imported proposals are correct.

Note

If some but not all of the proposal pool is incorrect or of dubious quality, you can use the selection criteria for exports and/or imports to ensure that low-quality parts of the proposal pool are excluded from the transport, while the correct parts of the proposal pool are transported. For example, if translations belonging to the domain Finances are the only ones that are incorrect in a legacy system, you can transport the proposal pool for all other domains in the system.

·        Performance Considerations

¡        The proposal pool is used to perform many different tasks within the translation environment. If proposal pools are very large (that is, if they contain more than one million entries per target language), performance may suffer whenever the proposal pool is accessed. If your proposal pools have grown over a number of years, it is safe to assume they contain many translations that are no longer required. You are therefore advised to clean up the proposal pool regularly. For example, you can use an object list to restrict your transport to just those proposals that were really used as a translation in the source system.

 

You can also import proposal pools from several source systems into a target system. This could be necessary if, for example, you need to set up a new banking system that also contains a number of Basis functions. If the Basis functions and banking functions have been translated in different translation systems, you need to set up the new banking system by importing the proposal pools from the Basis and banking systems.

In this situation, it is possible for the same source text to have different translations in the two translation systems. If both source texts have been defined as a system standard or application standard for the same domain, and if the system standards or application standards have the same quality status, then a conflict occurs. The system then inserts both terms at the same level and with the same quality status into the proposal pool.

Example

You are setting up a new banking system for which you need proposal pools from the Basis and legacy banking systems. In the Basis system, the term Client has been translated into German as Mandant and defined as a system standard with quality status S. In the banking system, the term has been translated as Kunde and also defined as a system standard with quality status S. If you import both proposal pools into the new banking system, the resulting proposal pool will contain two German translations of the English source text Client, namely Mandant and Kunde. Both are system standards with quality status S.

Caution

If the proposal pool contains two proposals at the same level with the same quality status, the best proposal and automatic distribution are turned into a lottery for the source text in question because either of the coexistent proposals could be selected. You can usually avoid this situation by always defining proposals as application standards, and then turning them into system standards only after you are absolutely sure that the translation is unique.

 

Activities

The proposal pool transport consists of the following steps:

...

       1.      Export the proposal pool(s) from the source system(s)

       2.      Import the proposal pool(s) into the target system

 

End of Content Area