Show TOC

Filling Transport Requests with TranslationsLocate this document in the navigation structure

Prerequisites

  • If you want to use a manually created transport request, you must first create it using the same procedure as for automatic transport generation.

Context

You can collect all of the translations created in transaction SE63 in a transport request, according to the following criteria:

  • Target language

  • Translated object types in the system

  • Date range

  • User

  • Package/collection

  • Software component

    For example, you can fill a transport request with translations into target language English for all of the object types in the ABAP package SLXE that have been saved by user SMITHJ since the start of the current week.

Procedure

  1. Call transaction SLXT.
    The Translation Export screen appears.
  2. Under Export Mode, you can define one or more target languages for which you need to create transport requests. You have the following options:
    • If you only want to create a transport request for one target language, select Individual Language. You can use the input help function for the Target Language field above to select the required language.
    • If you want to create a transport request for some, but not all of the target languages in the system, select Multiple Selection. You can use the input help function for the Target Language field above to select the required languages.
    • If you want to create a transport request for all of the target languages in the system, select All Existing Languages.
  3. If you do not want to generate the transport request immediately, but first want to display the objects that will be collected by your settings, select List Objects under Export Mode. If you want to generate the transport request, select Generate Language Transport.
  4. You now have the following options:
    • If you want to generate a new transport request, leave the Create New Request checkbox selected under Transport Request. Enter a description in the Description field.
    • If you do not want to create a new transport request, but want to use an existing transport request that was not created using transaction Translation Transport (SLXT), deselect the Create New Request checkbox under Transport Request. You can now select the Grant Non-SLXT Requests checkbox and can enter the number of the relevant transport request in the Transport Request entry field by using the input help function (F4).
  5. Select the Transport of Copies or Workbench Request transport type under Request Type.
  6. Enter the target system under Request Type.
  7. If you want the request to be released automatically after the translated objects have been collected, select the Release Request in Next Step checkbox under Options.
    If you select Workbench Request and allow the transport request to be released immediately after the translated objects have been collected, the translations are transported automatically.
  8. Now maintain the criteria for collecting translations in the transport request:
    • If you want translations that were created in a specific period to be collected in the transport request, use the Processing Date… to fields under Time Period to specify the period.
    • If you want to collect translations of one or more specific object types in the transport request, enter one, multiple, or a range of object types in the Object Type and to fields under Filter. If you leave these fields blank, the translations of all object types are recorded in the transport request.
    • If you want to collect the translations of one or more translators in the transport request, enter the translator(s) whose translations need to be recorded in the Object Processor and to fields under Filter. If you leave these fields blank, the translations of all translators are taken into account.
    • If you want to collect the translations of objects in specific packages/collections in the transport request, enter the packages/collections whose translations need to be transported in the Package/Collection and to fields under Filter. If you leave these fields blank, all packages are transported.
    • If you want to transport translations that belong to a specific software component, make the appropriate entries in the Software Component and to fields under Filter. If you leave these fields blank, the translations of all software components are transported.
  9. If you want to provide the systems in your system landscape with a delta transport of translations, select the Delta Transports checkbox in the Time Period group box. The start of the delta period is set automatically to the last date on which a delta export occurred. If a delta export has never taken place, the default start date is 01.01.2000.
    If you want to change the default start date for the delta transport, choose Delta Delta. You can then initialize the date (that is, reset it to the default value 01.01.2000), or specify a date manually. With regard to the latter, select the Define Manually radio button. The system displays a calendar for you to select the required date.
  10. If you want the system to check that objects exist before the import takes place, select the Check if Object Exists checkbox under Options. This enables you to prevent superfluous language data from being imported.
  11. If original language switches take place in your development environment, or if you translate into the original language, select the Exclude Original Language checkbox under Options. If language entries have an identical target language and original language, they are not transported.
  12. The Client Options input field under Options enables you to decide whether client-dependent and cross-client objects are exported, or whether the export only takes place for client-dependent or cross-client objects.
  13. If you want to execute the request immediately and just once, choose Start of the navigation path Program Next navigation step Execute in Background End of the navigation path and schedule the job for immediate execution. If you want to perform transports regularly using the same parameters each time, schedule the job for periodic execution.

Results

The system writes the translations that match your selection criteria to the transport request that you selected. The result is output in a report.

The system creates a detailed log, listing any objects that could not be written to the transport request.

You can now display the transport request to view the objects for which translations were recorded. You can release the request to transport the translations to other systems. For more information, see Displaying Transport Requests in Transport Recording.