Skip to Content

Language installation on SAP systems –  Step by Step

 

To use SAP with other languages, you must perform a language import or supplement (use transaction SMLT). Changes in the language environment usually require changes in the code page setup, which requires changes in some database tables and in the profile files.  The language environment that comes with the standard SAP installation includes German and English.

Before starting the language import, read the following SAP Notes

18601

Frequently Asked Questions on Language Import

Recommendations / additional information

43853

Consulting: Language Transport and Customizing Tables

Consulting

352941

Consulting: Languages and Support Packages

Consulting

PREREQUISITES

To correct the language, you need to access the Support Package files. These files can be in several different formats:

• Transport requests

• EPS package in the EPS Inbox

• CAR or SAR archive in the tmp sub directory of the transport directory

• Collection CD.

Make sure you are installing languages in 000 client. Once you installed languages you can not revert back.

First go to SMLT and check the installed languages, by default you find English and German.

First we need to Add the language in I18N to start with installation

Please to I18N tcode and click on System configuration

As per below screen shot please define the language code by clicking on add button

You can see the below screen for New NLS Configuration activation

Click on  Yes to continue, Below screen will display

We need to maintain parameter zcsa/installed_languages in the profile and add new languages being installed in the parameter like below

NEFDiILP4S

Restart SAP for parameter to be activated.

Now we successfully configured CS language, then execute the SMLT tocode

Click on Language create TAB, which is showing in above screen shot, Then it display the screen below

Select the language from General section language tab

Do not forget to mention supplementation language in Supplementation section

Now you have successfully saved the language.

Go to the language which you want to install

Top of the screen you can see language –>Import Packages.

  After you have specified a start time and (optional) target server, choose Execute to import the language package(s) you have selected.

The first three of these options are supported automatically. If you use a Collection CD to access Support Package data, you must specify the path to the CD.

Step: Searching for existing files at the operating system level.

To import Support Packages, you require data in the following form

– R3trans data file of the Support Package request, or

– the PAT file of the Support Package, or the CAR archive of the Support Package.

The tool first searches for R3trans data files in the data directory of the transport directory, followed by PAT files in the EPS Inbox (usually $(TRANS_DIR)/EPS/in), and finally CAR archives in the directory $(TRANSDIR)/tmp.

You have the option of searching for CAR archives in other paths. Enter a path and start the search. The system also searches for sub directories, so that you only need to specify a single path to search a Support Package Collection CD.

Caution: When searching for suitable CAR archives, the system assumes that a CAR archive with the name Kxxxxxx.CAR contains the Support Package SAPKxxxxxx. This is always the case with Sap Net downloads and Support Package Collection CDs.

In the next dialog box, enter the path for the language packages. Choose Find Package(s) to search for any available packages in the path you have entered

 

Click Yes to continue the same.

An import action is created for the appropriate language on the overview screen of transaction SMLT. There are various functions in the overview for managing and monitoring the import.

Please check the above screen shot truck symbols shows that language import is running. you can check the corresponding logs and jobs by click on the options

 

I clicked on job monitoring, it displays the above screen.

After successful implementation you need to import the related support packs,

The green, yellow and red lights next to the packages indicate whether you can import them. Click the lights to display extra information.

A green light indicates that all import conditions have been met, a yellow light indicates that there are warnings, and a red light indicates that the package cannot be imported because checks have detected errors.

Select one or more language packages with green or yellow lights for import.

Import Language Content of Support Packages

PURPOSE

All Support Packages delivered by SAP have been translated completely. Support Packages can be used to deliver missing translations, or correct incorrect translations.

If you install a language after you have imported Support Packages into your system, you may have overwritten new Support Package translations with obsolete translations. The language is then inconsistent.

To correct the language data, you need to import the language part of the Support Package. This program supports you in this with the following functions:

• Check language data to see whether it is correct.

• Determine which Support Packages are in the system, and which Support Package translations need correcting.

INTEGRATION

To access this program, call transaction SMLT and choose Goto -> Other Tools.

Important: Not all required files need to be available at the same time. You can start the import with the first X files and then continue later with file X+1. A restart function is available for doing this.

Using the Program, go to SE38 and run the below report

Use the report RSTLAN_IMPORT_OCS to extract the language-relevant information from each support package

select the language which you want to do the import language support packages

Step: Selecting the Support Packages

All Support Packages are categorized with a traffic light as follows:

Green: No import is required for these Support Packages

Yellow: No import required

Red: Import required

All Support Packages with red lights are already selected. You can also select Support Packages with yellow lights (however, this is not normally necessary).

Go to the next screen (F6). When you do this, the system searches for usable files in the file system.

Proceed to the next screen (F6).

Step: Starting the import

The import queue appears. Choose F6 to start the import process.

Step: Importing

All Support Packages are processed, one by one. The import is online, as in transaction SPAM. There should not be any timeout problems. The import of a Support Package involves the following steps:

• Copy the CAR archive to $(TRANS_DIR)/tmp, if necessary.

• Extract the CAR archive, if necessary. This creates a PAT file.

• Disassemble the PAT file, if necessary. This creates an R3trans data file.

• Import the R3trans file in special mode.

Files created temporarily by the import process (CAR archive in $(TRANS_DIR)/tmp, PAT files and R3trans files) are deleted as soon as possible to avoid overflows in the file system. However, large import logs are written to the log directory of the transport directory.

Possible Errors

Some errors are possible during the import process. If an error occurs, the program stops, and an error message appears in the status bar. You can restart the import process after you have removed the error. Double-click the error message in the status bar to display information about the error and troubleshooting measures.

Logs

Transaction SMLT creates a new action with the name OCS_IMPORT_<(>  <<)>ISO code>_ under the import actions for the language. The processed Support Packages are listed under this action.

Includes used within report:

No INCLUDES are used within this report code!

To report this post you need to login first.

21 Comments

You must be Logged on to comment or reply to a post.

  1. deepa awasthi

    Nice article.

    Thanks for sharing.

    I’ve a query : To import language support packages, from where i can download files in smp.

    Is it under support packages and patches? or it will be covered in Installation media itself.

    Regards,

    Deepa.

    (0) 
      1. Eli Daniel Ramones Silva

        Hi Jacob. I have a question. Install Netweaver 7.11 in the phase post install only apply new support package, now need install language spanish.

        I can install new language after apply support package?

        Best Regards

        (0) 
  2. Nils Buerckel

    Hi Ranjith,

    thanks for the detailed description.

    However I am missing the language supplementation as described in SAP note 1156507.

    This should be done after the language import of the support packages for all clients.

    There are a few exceptions –  e.g. for a translation system  supplementation should be avoided.

    Please also have a look at:

    Online help: Language Installation Procedure

    Best regards,

    Nils Buerckel

    (0) 
  3. Riya Sarkar

    Hi Ranjith,

    Thanks for sharing the steps

    I’ve a query on language install and was wondering if you  could help. Is tehre any best practice/guideline from SAP regarding the same language packs installed in both ECC and BW. Should BW system have the same languages installed as ECC?

    Thanks in advance!

    Have a great day.

    Regards,

    Riya

    (0) 
    1. Mandeep Dhillon

      Hi Riya:

      There is no dependency between Languaga  support packs for ECC/BW systems. It totally depends upon your requirement. In case you have installed an International language for users in ECC and there are reporting requirements as well then certainly you should install same language in BW as well.

      Thanks.

      (0) 
    2. Nils Buerckel

      Hi Ranjith,

      there is no best practices for this question – it usually depends on the end users need. E.g. do they want to do the reporting in their local language or is EN enough ? This needs to be evaluated for all languages and this should be then a piece of the overall language strategy of a system landscape (which is often not defined by customers) …

      Best regards,

      Nils Buerckel

      (0) 
  4. Luis Esteban Moreno Ruiz

    Hi Ranjith Jacob, i would like to know if it is possible to install the Spanish Language in a demo system (SAP EHP 2 for SAP NetWeaver 7.0). It is a Trial Version. I dont know where i can find the files to install this language. Can you help me please?

    Regards.

    (0) 
      1. Luis Esteban Moreno Ruiz

        Hi Mandeep, thanks for your reply.

        I cant find my version there, Component Version SAP EHP 2 for SAP NetWeaver 7.0

        These are my Software Components:

        SAP_ABA 702 0006 SAPKA70206 Cross-Application Component
        SAP_BASIS 702 0006 SAPKB70206 SAP Basis Component
        PI_BASIS 702 0006 SAPK-70206INPIBASIS Basis Plug-In
        SAP_BW 702 0006 SAPKW70206 SAP Business Warehouse

        What can i do?

        Thanks again!

        (0) 
        1. Mandeep Dhillon

          Hi Luis:

          As per the note. Here is is the media.

            • EHP5 FOR SAP ERP 6.0 / NW7.02

                                Material Numbers / Available Languages:
                                51039096_1: DVD_1 and 51039096_2: DVD_2 and  51039096_3: DVD_3
                                DVD 1 / 3
                                AR, BG, CA, CS, DA, DE, EL, EN, ES, ET, FI, FR, HE

            Thanks,

            mandeep

            (0) 
    1. William Lasko

      SMEs – I’m being asked to load about 25 local language packs for a single ECC instance in Europe to accommodate simple local language requirements for system outputs – like Invoices and other forms. I’m concerned that at some point – it may be highly risky to load so many languages – from a  technical perspective.

      Besides the amount of work to install – is there any risk operationally to having 25+ languages installed in ECC ?  Thanks in advance.

      (0) 
      1. Nils Buerckel

        Hi,

        I do not see a risk installing 25+ languages. However I would recommend to think about whether it is really necessary. Maybe a technical installation without language import would be sufficient (maybe with a full supplementation with EN) ?

        Multiple languages cause additional maintenance effort e.g. during an upgrade …

        Best regards,

        Nils Buerckel

        (0) 
        1. William Lasko

          Thank you Nils … you’re spot on. We have a vague capture of the real requirement and are attempting to cover our butts with all languages …

          I appreciate your help sir – many thanks.

          Bill

          (0) 
          1. imahmed basis

            Hi Nills, and William,

            Could you elaborate the term “technical installation without language import. ?”

            Does it mean we add entries in i18N and SMLT and use EN as supplementation language. but we don’t actually import any language packs Since there is no language definitions SAP can’t translate them instead uses the supplementary language EN to translate the text. ? Did this help the requirement in Europe. ?

            -Ahmed

            (0) 
            1. Nils Buerckel

              Hi Ahmed,

              yes, that is one possibility – do the language import as documented, but skip the import of the import file provided by SAP. This is in deed the way how customers can do it if SAP currently does not provide a translation of standard UIs (e.g. Indonesian).

              The requirements in Europe are very heterogeneous and you cannot give a general answer. E.g. in France the “full supplementation with EN” is usually not accepted, while in the Northern part of Europe it could be different. But this also depends e.g. on the industry and in the end it has to be analyzed individually per company.

              Best regards,

              Nils

              (0) 

    Leave a Reply