In customer system customer developments are translated into production languages and modifications of translations of the SAP standard are made.These translations should be transported into subsequent systems (test, production).
In Release 4. 0 translations can only be transported on the basis of development classes. Only as of Release 4.5 an object related transport on the basis of transport requests is possible.
Procedure for Release 4.0A
1. Translation system
The translation occurs in any client of the system, which does not have to be client 000. For a translation in a client <> 000 you must ensure that all client-specific tables in the translation client are current.
2. Language export
Carry out the language export with report RSLTEXPO. Create a variant for report RSLTEXPO with the name of the export directory and the languages to be exported in the translation client. Select 'Customer-development' as transport type and 'Development classes' as mode. With the pushbutton 'Selection', you reach a dialog box in which you can mark the development classes to be transported. At the end, you also find development classes starting with Y* and Z*.
Save your selection.
Start report RSLTEXPO with the generated variant in the background. Several files are generated as a result (<l><iso>TX.EXT, <l><iso>DC.EXT, ...) where <l> specifies the language indicator <iso> thus the ISO code. Note that you must specify the name of the main directory under the export directory. For every language to be exported, a subdirectory <l>_<iso> must exist !
Generally, report RSLTEXPO exports only the table entries which can be modified by SAP for tables for which separate customer areas can be defined. In customer systems, this restriction can be cancelled so that ALL table entries are transported. You can cancel the restriction by setting an unconditional modes. To do this you must enter function UCON in the command line according to the definition of the development classes to be exported. In the dialog box displayed subsequently, select the line "Customer - Ignore TRESC".
In Release 4. 0B, not all texts are taken with the language export for some objects. The problems known to us as well as the respective solution are described in detail in Note 100168.
3. Language Import
To import the files use in the target system Transaction SMLT.
Select "Schedule import" and enter the main directory of the language files (see point 2.). On the selection screen, select -> Special imports -> Development classes -> Export set (development classes). Subsequently proceed as if you were to schedule a standard language import. You can schedule the replenishment implicitly or standalone upon completion of the import.
4. Customizing tables
Note that the import for Customizing tables is analogous to the import of standard translations, that is Customizing entries are imported exclusively in client 000 (see also Note 28148). If you translated Customizing texts and want to import these in the target system in client <> 000, use report RSREFILL upon completion of the language import to transfer entries from client 000 to other clients. Refer for the procedure to the online documentation for report RSREFILL.
Read the current language notes of the respective releases (4.0A: 83997 and so on). Also read note 18601 which contains frequently asked questions on the language transport.
Make sure that table NOTRA is maintained in the source and the target system. Table NOTRA contains the tables which must be ignored for the language export or with language replenishment.
If you have separate tables, which you do not want to transport, you must enter this in table NOTRA manually. To do this use Transaction SM30 and enter as reason for the exclusion of the respective table value 'T' (= "for technical reasons").
Please note that the language export must be carried out from a translation client (to be configured using Transaction SE63) since otherwise language files are created that cannot be imported into another system.
Get more ideas about SAP Basis Transaction Codes
Procedure for Releases 4.5 and 4.6A/B
Transport of translations based on object lists.
In addition to the above described procedure, it is possible as of Release 4.5, to transport customer translations by object based on transport requests or piece lists.
However, note that this is only possible for translation transports to already existing transport requests. Transport requests within the translation environment in order to log the translations will still not be generated !
You need to create the transport requests or the piece lists on which you want to base the language export by using the Transport Organizer (Transaction SE01).
Also consider, that you can only transport translations for system objects (PROG, FUGR, DTEL, ...). Translations for logical objects (Transaction SOBJ) as well as objects of the view and text maintenance will not be transported.
Since you will basically use the same procedure as described above for the transport, the following will only describe the differences.
1. You select mode 'Change requests' instead of 'Development classes' when you export on the the selction screen of RSLTEXPO. In the following dialog box you can specify up to ten requests. Translations for the objects of the requests are exported.
2. The translations are imported via SMLT -> Schedule import -> Special imports -> Export set (request-related)
Procedure as of Release 4.6C
As of Release 4. 6C, a transport link is available in Transaction SE63 and the SAP standard transport programs (tp and R3trans) are able to transport translations to objects.
For further information, refer to the online documentation of Transaction SE63.
Find more on SAP BASIS