Transporting Language and Translation Data

Transactions SMLT and SMLT_EX

• These transactions enable you to transport language data according to software component, package, or transport request.

• Using these transactions you can transport language data irrespective of how it became available in the system.

• These transactions always give you a clear overview of what has been transported.

• Transaction SMLT is the only transaction with which you can import language files from SAP.

• You cannot use these transactions to restrict your transports to language data that only became available via transaction SE63.

• These transactions only transport languages files and not translation data.

• These transactions comprise a two-step process. You must first complete the export using SMLT_EX before starting the import step using SMLT.

Transaction SLXT

• This transaction enables you to restrict your transports to language data that only became available via transaction SE63.

• It is primarily intended for transporting translations from the translation system to other systems, such as test and productive systems, as quickly as possible,

• This transaction only allows you to transport language data that has become available in the system using SE63.

• This transaction does not transport any translation data.

• There is no clear overview of the transports in your system landscape.

RFC Connection During Evaluation ( Copying Texts and Translation Data by RFC)

• This procedure enables you to import precisely those texts that you require to give translation lines and long text objects in the target system translated status.

• It is a single-step procedure - data is fetched by RFC.

• This procedure transports translation data as well as language data.

• You use this procedure to transport language data and translation data into a translation system only.

• This function is first available as of the Releases listed below:

  • SAP NetWeaver 7.0 EHP2 (as of Support Package 12)

  • SAP NetWeaver 7.3 EHP1 (as of Support Package 03)

  • SAP NetWeaver 7.32

• You can only transport data this way by setting up the translation environment and creating an evaluation in transaction LXE_MASTER.

Reports for Transporting Translation Data

• You have many transport options. For example, you can transport the entire proposal pool, or just the proposals that were created or last changed by a particular user, or just the proposals that give translated status to lines in short text objects in an object list.

• The Export Translation Data and Import Translation Data reports enable you to transport proposals and fingerprints at the same time.

• These reports comprise a two-step process. You must first complete the export before starting the import step.

• The proposal pool transport reports do not allow you to transport fingerprints.

RFC Connection During Evaluation ( Copying Texts and Translation Data by RFC)

• This procedure enables you to transport precisely the translation data that you require to give translation lines and long text objects in the target system translated status.

• It is a single-step procedure - data is fetched by RFC.

• This procedure transports language data as well as translation data.

• You use this procedure to transport language data and translation data into a translation system only.

• This function is first available as of the Releases listed below:

  • SAP NetWeaver 7.0 EHP2 (as of Support Package 12)

  • SAP NetWeaver 7.3 EHP1 (as of Support Package 03)

  • SAP NetWeaver 7.32

• You can only transport data this way by setting up the translation environment and creating an evaluation in transaction LXE_MASTER.