Translation Data Transports

The term translation data refers to the proposal pool and fingerprints in a translation system. Proposals give translated status to translation lines in short text objects, whereas fingerprints give translated status to long text objects created in transaction SE61 and to SAPscript forms and styles.

Transporting proposal pools and fingerprints from one translation system to another is an efficient way of saving time and money and improving translation quality. It is possible to transport proposal pools and fingerprints together using the exporting and importing translation data reports, or you can transport proposal pools and fingerprints independently of each other.

Proposal pools and/or fingerprints exist for the required source and target language combinations. For example, while translating objects into five different target languages you created proposals in the proposal pool, and generated fingerprints by saving long text translations actively.

You must be confident that the translation data you transport is of an acceptable quality. Otherwise you will just be spreading errors from one system to the next.

• You can run a report that deletes superfluous proposals in the proposal pool. It is an especially good idea to run the report before transporting the proposal pool from one system to another, so that you do not waste time exporting and then importing obsolete proposals. For more information, see Deleting Superfluous Domain Standards.
• Why not organize a proposal pool cleanup 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 created proposals with high quality statuses.
• You could export only those fingerprints that have been created by experienced translators.

• You can transport all of the translation data from one system to another, or you can restrict the transport to just some of the translation data according to a wide range of criteria.
• You can transport deleted proposals. It is a good idea to transport deleted proposals if you have cleaned up the proposal pool in one system, and want to ensure that the same poor-quality proposals are also deleted in another system in which you translate.
  Example

  In system <ABC>, a translator discovers the following entries in the German to English proposal pool for the German source text Aktivität:

  Type of Proposal	Proposal	Quality Status
  System standard	Activity	S (standard quality status)
  System standard	Action	B (created by a new translator)
  Domain standard in domain SD	Action	X (not recommended for distribution)

  The translator changes the proposals on April 15, 2014 as follows:

  Type of Proposal	Proposal	Quality Status
  System standard	Activity	A (flag for distribution)
  System standard	Action	Z (deleted)
  Domain standard in domain SD	Action	S (standard quality status)

  On January 10, 2014 you transported the entire German to English proposal pool from system <ABC> to system <XYZ>. As a result, the entries in the German to English proposal pool in system <XYZ> for the German source text Aktivität look just like the entries in <ABC> before the translator made any changes.

  On May 22, 2014 you export just the deleted proposals from system <ABC>, and import them in overwrite mode into system <XYZ>. After the import, the entries in the German to English proposal pool in system <XYZ> for the German source text Aktivität look like this:

  Type of Proposal	Proposal	Quality Status
  System standard	Activity	S (standard quality status)
  System standard	Action	Z (deleted)
  Domain standard in domain SD	Action	X (not recommended for distribution)

  Alternatively, you could have decided to export all proposals, including deleted proposals, from system <ABC> and then import them in overwrite mode into system <XYZ>. If you had done this instead, the entries in the German to English proposal pool in system <XYZ> for the German source text Aktivität would have looked like this after the import:

  Type of Proposal	Proposal	Quality Status
  System standard	Activity	A (flag for distribution)
  System standard	Action	Z (deleted)
  Domain standard in domain SD	Action	S (standard quality status)

• You can transport proposal pools and fingerprints together, or you can transport them independently of each other.
• You can transport translation data for any number of source and target language combinations in the system.
• When you export translation data, you do not have to specify the file names yourself. They are generated automatically by the system.
• You can enter a meaningful description for the export and import.

You need to perform the following steps for each source and target language combination:

1. Export the translation data (proposal pool and/or fingerprints) from the source system.

2. Import the translation data (proposal pool and/or fingerprints) into the target system.