Start of Content Area

Procedure documentation Filling Transport Requests With Translations  Locate the document in its SAP Library structure

Use

Translation transport requests are created individually for each target language. You can collect translations in a transport request in accordance with the following criteria:

·        Object types that are translated in the system

·        A date range

·        A user

·        A package/collection

·        A software component

Example

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.

The transport requests can be imported into other systems automatically. If your translation project is long-term and you need to perform transports before the project is complete, you can perform a delta transport for your target systems.

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.

·        You can only use transport recording if your user profile includes the authorization object S_TRANSPRT with activity CREA and type TRAN (Transport of Copies) or DTRA (Workbench Request).

Procedure

...

       1.      Call transaction SLXT.

The SE63 Translation Transport screen is displayed.

       2.      In the Target Language field, enter the four-character ID of the target language for which you want to perform transport recording.

       3.      If you want to use an existing transport request, deactivate the Create New Request checkbox. Select a transport request by using the input help function for the Transport Request field that is now displayed.

       4.      If you want a transport request to be generated, leave the Create New Request checkbox selected.

       5.      Select the Transport of Copies or Workbench Request transport type.

       6.      Enter the target system.

       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.

Note

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 selection 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 Dateto fields in the Time Period group box to specify the period.

¡        The Object Typeto fields in the Filter group box enable you to enter one object type, several object types, or a range of object types to be included in the transport request. If you leave these fields blank, the translations of all object types are recorded in the transport request.

¡        In the Object Processor fields in the Filter group box, enter the translator or translators whose translations need to be recorded. If you leave these fields blank, the translations of all translators are taken into account.

¡        In the Package/Collection fields in the Filter group box, enter the package/collection whose translations need to be transported. 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 corresponding fields in the Filter group box. Otherwise, leave them blank.

       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.

Note

If you want to change the default start date for the delta transport, choose the Delta pushbutton. 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 in the Options group box. 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, you are advised to select the Exclude Original Language checkbox in the Options group box. This prevents language entries from being transported whose target language is the same as the original language.

   12.      The Client Options input field in the Options group box 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 Program Execute in Background 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.

Result

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.

 

 

 

End of Content Area