cancel
Showing results for 
Search instead for 
Did you mean: 

What causes that on German PC before loging into ECC system we have "Mandant", "Benutzer","Kennwort" and on an English PC we have "Client

Former Member
0 Kudos

Hello

What causes that on German PC before loging into ECC system we have "Mandant", "Benutzer","Kennwort" and on an English PC we have "Client", "User" and "Password"?

Namely we would like to have on Russian PC their names for those entries. How to achieve that

Thank you in advance

Accepted Solutions (0)

Answers (2)

Answers (2)

tomas_black
Active Contributor
0 Kudos

Hello Jan,

did you install Russian language already? If no, please follow note #1508122 for this, as it describes all the steps necessary to do it, from identifying the correct media and package to all post-install steps.

The german text is correct for german language, so are the english ones. What's the primary language defined on your system? (parameter zcsa/system_language) If you have installed Russian, have you defined it as primary (or at least seconday)?


Here's a brief explanation of the lang parameters:

1) zcsa/system_language -

The system language has two basic functions:

         -   It determines the language on the logon screen.

         -   It is the basic language for all user dialogs (screens).

2) zcsa/second_language -

    If you want to display texts in a language in which the texts are not available, SAP Web AS attempts to display certain objects in another language, the secondary language. This secondary language option is supported for the following objects from SAP Web AS Release 6.20 onwards:

         -   ABAP text elements

         -   Screen (including texts from the ABAP Dictionary)

         -   GUI status

         -   OTR (Online Text Repository)

     The secondary language must be a completely translated language. The secondary language is independent of the logon language.

3)  Supplementation Language

     The secondary language option cannot be implemented for all texts for performance reasons. To use a language, supplement it with transaction SMLT.

     A language supplementation replaces any missing texts in the logon language with texts in the supplementation language.

     Unlike the secondary language, you can set a different supplementation language for each language.

  Secondary Language Access and Language Supplementation:

     There are two different concepts for missing translations: Secondary

     language access and supplementation language. It is best to set the same

     language as the secondary language and supplementation language, since

     both concepts then have the same effect.

     If the supplementation language is different from the secondary

     language, the supplementation language 'wins' for reasons of

     consistency. The secondary language is not accessed.

I hope this helps.

Best regards,

Tomas Black

0 Kudos

Hi,

For this you need to install the Russian language in the system.

Please follow the following steps for correct language installation and supplementation:

1. Import the affected language using transaction SMLT.
    (Please check if the language package is imported correctly. Please refer to SAP note 330104. Note 330104 contains a list of all language packages and compare them with the packages in SMLT).

     You can also check if the language imported is correct as detailed by the following note:

        990606 - Import of an incorrect language package;

2. Import the language part or run report RSTLAN_IMPORT_OCS:
    You can follow one of the two options below:

    A. Import the language part of Support Packages as follows:
    SMLT   > single click in the language to select it   > Language   >
           > Special Actions   > Import Support Packages   >
           > select all the Support Packages with the red light
           > click the 'Go to next screen' (F6) icon

    B. Run report RSTLAN_IMPORT_OCS for the affected language:
    SE38   > Program: RSTLAN_IMPORT_OCS
           > click 'Execute' icon (F8)
           > Import language: <Language>
           > click 'Execute' icon (F8)
           > select all the Support Packages with the red light
           > click the 'Go to  next screen' (F6) icon

    If there aren't any support packages with the red light the report RSTLAN_IMPORT_OCS won't be executed.
    In SAP note 195442 you will find further information regarding report RSTLAN_IMPORT_OCS.

3. If needed, run report RSTLAN_SUPPLEMENT_UNI using the first option:
    "Client Maintenance with Customizing Translations", that will copy the missing translation texts from client 000 to the other clients of your system and will also update the customizing texts of your
clients. Further information on this report can be found in note 211226.

4. Go to transaction SMLT and, if you haven't supplemented the affected language yet, please supplement it with English or German in ALL your clients, starting with client 000. You will find further information about the supplementation in the "Language Transport" guide, that can be downloaded from the SAP Service Marketplace, alias /instguides

5. Once that you have supplemented the affected language, set the parameter zcsa/second_language to the supplemetary language,
    that is:

    A) If you have supplemented the language with English set the
       parameter zcsa/second_language to English
       ( zcsa/second_language = E )
    B) If you have supplemented the language with German set the
       parameter zcsa/second_language to German
       ( zcsa/second_language = D )

6. Now you must run the RSLANG20 report for all the languages selecting all the options (do not forget to set the force mode ON)  and, after that, reset the CUA buffers and the dynpro buffers via
writing /$CUA and /$DYN in the OK-Code field of each application server as per SAP note 110910.

7. Ensure you restart the instance after all this, to make sure the
    changes take effect.

Best Regards,

Abhishek