Contents:
Purpose of this document.. 2
Basic documents. 2
Documents in the web. 2
Common OSS notes. 2
Supported Releases. 2
Step-by-step installation of a language.. 3
Preparation phase. 3
Check version of transport tools. 3
Profile maintenance. 3
Maintenance of languages and OS locales. 4
Import phase. 5
Language import 5
Import language of already imported support packages. 6
Language supplementation in client 000. 9
Periodic supplementation in client 000. 10
Copy language to all other clients. 12
Language supplementation in all other clients. 16
Post-treatment of language supplementation. 17
Periodic supplementation in all other clients. 18
Post-Import phase. 20
Activate SAPscript forms. 20
Distribute language templates to ITS servers. 21
Trouble Shooting.. 23
Removing a language. 23
Remove the language supplementation. 23
Remove the language from support packages. 23
Remove the language load. 23
Document created by: Martin Steffke Last change: 13. April 2004
Purpose of this document
This document describes the procedure of how to import a language into an R/3 like system. The complete procedure is reflected in installation guides.
This document does not replace the basic documents from SAP AG.
All information in this document are based on personal exerience and on consulting the developers...
Basic documents
Documents in the web
Please find the basic documents regarding your installed R/3 release in the installation documentation as shown below:
http://intranet.sap.com/instguidesInstallation guides for all SAP products. Follow the document tree on the left:
->
http://intranet.sap.com/notesNotes search for OSS notes. Find the language import / transport in component BC-CTS-LAN
Common OSS notes
Please understand the following OSS to support you while trouble shooting the language import:
048047 - Mode of operation of report RSREFILL
432272 - Transport of language data using tp/R3trans
533888 - Example for Language Import and Error Specification
596982 - Texts are deleted by Support Package
Supported Releases
As of now the following releases are supported by this document:
R/3 rel. 4.x to rel. 6.20
ITS rel. 4.6 to rel. 6.20
Step-by-step installation of a language
The following sections contain all the activities of how to install a language
Preparation phase
The preparation phase can be made in advance. During this phase you must restart the R/3 system.
Check version of transport tools
According to the installation guide (Language transport.pdf) you will need to have a minimum version of the transport tools. See also OSS notes:
195442 - Language import and Support Packages
Check this:
SPAM versionTransaction SPAM -> The dialog shows the version
tp versionTransaction STMS -> Button: System Overview -> Mark the current system -> Button: System configuration -> Tab strip: Transport Tool -> Button: Check Transp. Tool -> Open Result Tree: tp-Call -> tp-Version
R3trans versionLog on to the central instance host on operating system level as user
Profile maintenance
Tell the system about the new languages you are going to install.The parameter zcsa/installed_languages must be set in the DEFAULT profile, not in the instance profile!
Actions:
Login to client 000 as user DDIC oder super-user
RZ10 -> Edit the DEFAULT profile and append the SAP language code (SAP specific) to these parameters: zcsa/installed_languages eu/iwb/installed_languagesIf you don't know SAP language codes: the table T002T contains all SAP language codes:
SE17 -> Table Name = T002T -> Button: Continue -> Fill in the query dialog as shown below:
Press the button: Execute. The result displays all available SAP language codes
Save the DEFAULT profile
Edit the instance profile of all instances and make sure the parameter zcsa/installed_languagesis not contained in any of these profiles.
Save the instance profiles in case you changed them
Restart the R/3 system
Maintenance of languages and OS locales
After restart of the system now introduce the language to the language tool and let the R/3 system check whether all necessary operating system locales are installed.
Did you restart the system after the last check above? (See Profile maintenance). If not, do it now.
Login to client 000 as user DDIC or super user
SE38 -> Start report RSCPINST
In the left part of the screen: Button: Add -> goto the new text line and use the
Be sure to check the item "Enable locale check":
Press button "Simulate"
If you forgot to restart the R/3 system in advance you will see errors like "Please set profile parameters for the new language". In that case repeat the last chapter Profile maintenance.
If a locale is missing, please let the Operating System group install the locale on all application servers. Example error output for the language "Polish" (PL):
Repeat this step until all errors are resolved.
Press button "Back" to go back to the welcome screen
If the simulation displayed no errors, press button: Activate.
Import phase
Language import
This is the step where you import the language and therefore you need the language CD-ROMs at hand, also the installation guide for questions and concerns. Here is the short How-to:
Login to client 000 as user DDIC or super user
Transaction SMLT -> Button: Classify language (or: New language) ->
Select the new language
Select the supplementation language to be the system language as displayed in the same dialog ath the bottom:
Press the save Button
Mark the language -> Menu: Language -> Import PackageThe language import starts. Please follow the instructions of your language installation guide (see: Documents in the web).
After the language import finishes: Look at the status line of your SAP GUI.If you discover some text in the status line like "Glossary... is not completely installed yet", please run report RSTLAN_AFTER_UPGRADE in the background (SE38 -> Program -> Execute -> Background)
Import language of already imported support packages
If your system has already some support packages applied you have to re-import them - but this time only the language information. See also these OSS notes:
195442 - Language import and Support Packages (common information)
110910 - Deleting the language load (special information concerning report RSLANG20)
Actions:
Login to client 000 as user DDIC or super user
Check which support package were already imported. What R/3 release do you have?
R/3 release <= 6.10SE38 -> Report = "RSTLAN_IMPORT_OCS" -> Import Language =
Green traffic light: These support packages are O.K. - no re-import necessary.
Red traffic light: Not O.K. - you need to re-import the support packages
R/3 release >= 6.20SMLT -> Mark the language -> Menu: Language -> Special actions -> Import Support Packages
Green traffic light: These support packages are O.K. - no re-import necessary.
Red traffic light: Not O.K. - you need to re-import the support packages. See below...
Press Button: Go to next screen -> A list of support packages is displayed:
Green traffic light: O.K. These support packages exist in the EPS directory (e.g.: /usr/sap/trans/EPS/in resp. X:\usr\sap\trans\EPS\in)
Red traffic light: Not O.K. You have to download these support packages to the directory DIR_TRANS (e.g.: /usr/sap/trans resp. X:\usr\sap\trans) and to manually unpack them with SAPCAR.
Repeat the following steps as long as there are red traffic lights in the step above:
Download the missing support packages from SAP Service Marketplace and unpack them into DIR_TRANS.(If a package is missing it has the entry "R3trans data file not found" in the column: Status description)
Repeat this step for all downloaded support packages:
Open a new GUI mode (window) with: SE38 -> Report = RSSPDASS -> Press the Button "Yes" only at the first support package, next time press "No":
Enter the name of the support package. You'll find the name in the other GUI mode (window). Press the button: Transport directory
Confirm the upload with "Yes".
Switch back to the GUI mode (window) with the list of support packages and the red traffic lights...
Press button: Back -> Press Button: Go to next screen
Are there still red traffic lights? If yes then repeat all steps from above
Press button: Continue (or: Go to next screen) -> Again check whether all traffic lights are green
If NO: repeat the procedure with the red traffic lights from the last step above
If YES: Press button: Import language data
Dialog: " What should be done with texts of repaired objects" -> Press Button: Overwrite.
Start report RSLANG20 in transaction SE38 -> Fill in the new language, keep all check boxes like this:Start the program as background job: Menu: Program -> Execute in Background -> Select a printer -> select to start the program immediately -> Save the job.
After the Report RSLANG20 finished, enter /$CUA in the OK-code line and press ENTER:
Language supplementation in client 000
Some texts are not yet translated. Anyway the customer needs some text displayed in his GUI. This text is taken from the supplementation language you specified before (see: Language import).
The supplementation job is started first in client 000 since this client is the copy template for languages and forms.
The following OSS notes describe the procedure - sometimes contradictory:
43853 - Language-dependent + client-specific C-tables
211226 - Processing of Customizing in language transport
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SMLT -> Mark the language -> Menu: Language -> Supplement language
In the dialog "Supplement Language" enter a description like: "Supplement with
R/3 release <= 6.10Press button: Select -> then button: Execute
R/3 release >= 6.20Check the checkbox: Customizing tables -> button: Execute
You can follow the progress of the supplementation with:SMLT -> Unfold the tree with your language -> Find the button "Job Log" (white paper with glasses) and press it:
Periodic supplementation in client 000
The periodic supplementation is used to supplement language dependent texts after the import of transports, such as Support Packages. The following OSS notes describe the details:
315375 - Periodic language supplementation
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SE38 -> Start report RSTLAN_SUPPLEMENT_PERIODIC and fill in the dialog as follows:
Supplementation template: press
Do not press the Button "Execute"!Instead create a periodic batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to run periodically every day somewhen in the night (e.g. 23:00 hours). Example:
Save the batch.
Copy language to all other clients
The new language is imported in client 000. Now you should copy the language to all other clients. You have two choices in order to accomplish this:
Client management tools
Advantage: Less post-treatment work at the end. Works better for R/3 application module Logistics..
Disadvantage: More complicated
Language management tools
Advantage: Less complicated
Disadvantage: More post-treatment work due to release-specific implementation.
The following OSS notes concern the copy of languages:
533888 - General procedure
43853 - R/3 release <= 6.10 - Describes the post-treatment measures which OSS note 211226 contains in detail
R/3 release >= 6.20: Transaction SMLT contains all functions mentioned in OSS note 43853
Actions:
Please choose one of the following tools:
Usage of Client management tools
Login to client 000 as user DDIC or super user
SCC4 -> Find out all target clients suitable for the copy process
SCC4 -> Maintain all concerned clients:
The following radiobutton must be cleared: "No changes allowed". If not, clear the flag temporarily. See the dialog with example client 100 below:
SE38 -> Start report RSTLAN_IMPORT_CLIENTS with the following settings:
Field "Import Language Package": Press
Field "Clients": enter all concerned clients. Therefore enter a "000" in the first field and press the button "Multiple selection" to the right. In the following dialog enter all concerned clients from above. Example:
Fill in the remaining fields: "Update mode", "Table class G" and "Display list of tables". Example:
Do not press the Button "Execute"!Instead create a batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to start immediately.
Save the batch job
Check the result of batch RSTLAN_IMPORT_CLIENTS in transaction SM37.Therefore look into the spool list, do not look into the batch job protocol.
Now repeat the batch RSTLAN_IMPORT_CLIENTS in SE38.
Use the same settings as above, but this time select the "Language part from support packages". See the example: Language Dutch (NL) for R/3 rel. 4.6C SR2 (sorry, German text below)
Also, start this report as a background job, scheduled for immediate start. See above for detailled screenshots.
Check the result of batch RSTLAN_IMPORT_CLIENTS in transaction SM37.Therefore look into the spool list, do not look into the batch job protocol.
Repeat this step for all concerned clients:
Login to the concerned client as user DDIC or super user
SE38 -> start report RBZMECHK.
Login to client 000 as user DDIC or super user
SCC4 -> Maintain all concerned clients:
If you cleared the radiobutton "No changes allowed" at the beginning above, then re-enable the radiobutton again. See the dialog with example client 100 below:
Usage of Language management tools
Login to client 000 as user DDIC or super user
SCC4 -> Find out all target clients suitable for the copy process
Repeat this step for all concerned clients:
Login to the concerned client as user DDIC or super user
SE38 -> Start report RSTLAN_SUPPLEMENT_UNI, enter the target language code as needed (press the
Depending on the R/3 release the dialog looks different. Here is how to continue:
R/3 rel. <= 6.10: Button: Processing of Customizing in language transport -> Button: Execute
R/3 rel. >= 6.20: Button: Client Maintenance with Customizing Translations -> Button: Execute
SE38 -> Start report RBZMECHK.
Language supplementation in all other clients
As you already supplemented the languages in client 000 you now should supplement them in all other clients.
The following OSS notes describe the procedure - sometimes contradictory:
43853 - Language-dependent + client-specific C-tables
211226 - Processing of Customizing in language transport
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients:
Login to each concerned client as user DDIC or super user, the logon language must be either DE or EN.
SMLT -> Mark the language -> Menu: Language -> Supplement language
In the dialog "Supplement Language" enter a description like: "Supplement with
R/3 release <= 6.10Press button: Select -> then button: Execute
R/3 release >= 6.20Check the checkbox: Customizing tables -> button: Execute
You can follow the progress of the supplementation with:SMLT -> Unfold the tree with your language -> Find the button "Job Log" (white paper with glasses) and press it:
Post-treatment of language supplementation
The language supplementation is still implemented with lots of errors. In order to correct the errors proceed as follows:
Actions:
Proceed with this step only if these preconditions are met:
R/3 release is less than 6.10
and you copied the language to other clients using the Usage of Language management tools above.
Error: The tables T006A, T006B and T006C (Units of Measurement) were not translated correctly. The OSS note 451720 shows how to correct this error.
You will need a developer key, an object key and you must create a transport request. Be sure to have all information at hand before starting work.
Create a development class (new name: "package") with the name "SZME". Do this in transaction SE80.
Create an empty report with the name RBZMEREFILL, which belongs to the development class "SZME". Save the report.
Implement the OSS note 451720 using the SAP Notes assistent (transaction SNOTE).
Error: The table T006T (Units of Measurement Texts) was not translated correctly. Translate the Texts manually (!!!) using the original language texts from client 000. You can copy-and-paste the translations... The OSS note 169219 shows this procedure with in another context.
Proceed with this step only if these preconditions are met:
R/3 release is less than or equal to 6.20
and you copied the language to other clients using the Usage of Language management tools above.
Error: The table T006T (Units of Measurement Texts) was not translated correctly. The OSS note 595742 shows how to correct the error.
You will need a developer key, an object key and you must create a transport request. Be sure to have all information at hand before starting work.
Create a development class (new name: "package") with the name "SZME". Do this in transaction SE80.
Create an empty report with the name RBZMETRANS, which belongs to the development class "SZME". Save the report.
Implement the OSS note 595742 using the SAP Notes assistent (transaction SNOTE).
After you started the report RBZMETRANS finally run also the report RBZMECHK
Periodic supplementation in all other clients
The periodic supplementation is used to supplement language dependent texts after the import of transports, such as Support Packages. The following OSS notes describe the details:
315375 - Periodic language supplementation
533888 - Example for Language Import and Error Specification
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> find out all concerned clients
Login to each concerned client as user DDIC or super user, the logon language must be either DE or EN.
SE38 -> Start report RSTLAN_SUPPLEMENT_PERIODIC and fill in the dialog as follows:
Supplementation template: press
Do not press the Button "Execute"!Instead create a periodic batch job in menu: Program -> Execute in background
In dialog "Background Print Parameters":
select a printer, for example LP01.
Set the Spool options: Remove the checkbox item "Print immediately".
See the example below:
In dialog "Start time" plan this job to run periodically every day somewhen in the night (e.g. after 00:00 hours).Please make sure that only one batch in any client is active at a time!It has been proven to schedule the batch for each client with a minimum gap of 45 minutes in between.Example:
Save the batch.
Post-Import phase
Activate SAPscript forms
SAPscript forms are imported in client 000 only. The following OSS notes describe how to activate the SAPscript forms:
326801 - Activating SAPscript forms after language transport
Actions:
Proceed with this step only if these preconditions are met:
R/3 release is 4.6C (The BASIS release can also be 4.6D)
Login to client 000 as user DDIC or super user
SCC4 -> Find out the clients concerned
Repeat this step for all concerned clients:
Start report RSTXINSH and enter the dialog as follows:
Start report RSTXINSH again and enter the dialog as follows:
Distribute language templates to ITS servers
If your R/3 uses an ITS (Internet Transaction Server) you will need to publish the language templates to all connected ITS. The following OSS notes describe the procedure:
325149 - Publishing IAC objects
412202 - Publishing IAC objects in subsequent import processing
Actions:
Login to client 000 as user DDIC or super user
Start report W3_PUBLISH_SERVICES, do not fill in any dialog fields and just press the button "Execute".
Select the ITS servers where you like to publish the language templates. Therefore proceed like follows:
R/3 rel. <= 6.10
Press button: "Workbench-Settings".
In the following dialog change to the tab strip "Internet Transaction Server"
Select the radio button "On all defined sites" and press the "OK" button (or: "Transfer").Example:
R/3 rel. >= 6.20
Press button: "Workbench-Settings".
In the following dialog change to the tab strip "Internet Transaction Server"
Inside the tab strip select the tab strip "Publish"
Select the radio button "On all defined sites" and press the "OK" button (or: "Transfer").Example:
Back in the main window "Publish Services Chosen" press button "Select all". Now all entries in the list receive a check mark. Example:
Now press the button "Publish" in order to distribute the language templates. Example: See the picture above for the button...
Trouble Shooting
This section is about troubleshooting the language import. May be something went wrong...
Removing a language
If you need to roll-back some actions here is how it works. The roll-back takes place in 3 steps:
Remove language supplementation
Remove language from support packages
Remove the language load
Remove the language supplementation
This is the first step. There exists no OSS note for this procedure.
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients. Keep client 000 as the last client for login!
Login to the concerned client as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Reset/Cancel Supplementation of Customizing Tables"
Press button "Execute"
Remove the language from support packages
If you have already supplemented the language, please remove the supplementation first! See Remove the language supplementation above for details.
The following OSS-note describe the procedure:
116756 - Removing language-dep. parts from Support Packages
Actions:
Login to client 000 as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Removing Language Specific Parts from Support Packages"
Press button "Execute"
Remove the language load
If you have already supplemented the language, please remove the supplementation first! See Remove the language supplementation above for details.
If you have already imported support packages, please remove them first! See Remove the language supplementation
This is the first step. There exists no OSS note for this procedure.
Actions:
Login to client 000 as user DDIC or super user
SCC4 -> Find out all concerned clients
Repeat this step for all concerned clients. Keep client 000 as the last client for login!
Login to the concerned client as user DDIC or super user
Start the report RSTLAN_SUPPLEMENT_UNI and fill in the dialog as follows:
Field "Target Language": Select the language code of the language to remove
Press button " Reset/Cancel Supplementation of Customizing Tables"
Press button "Execute"
Remove the language from support packages above for details.
Well, there exists no documented procedure for a language removal.
Keep me updated,
Martin
No comments:
Post a Comment