Texts are not displayed in logon language. It is assumed that the respective translation is missing.
Reason and Prerequisites
SAP products are translated into more than 30 languages.
Additional languages are supported. If a language is supported by SAP, it does not necessarily mean that SAP delivers translations for this particular language for a particular product and / or release.
And even if translations are delivered by SAP there is an difference as to how “broadly” and “deeply” a particular language is translated.
To ensure system stability with regard to texts in different languages, we recommend that you run language supplementation in client 000 and in the working client (which is different from 000) after importing languages and after importing Support Packages and / or AddOn Packages.
Only language EN is a “so called 100% language” where every text should exist.
So EN is the preferred language for language supplementation.
Please find further information about supported SAP languages at
-> Language Information
This note gives you information on finding the reason for missing texts in an SAP system and provides a checklist for analyzing the issue and finding a feasible solution.
There are steps which can / should be done by customers themselves.
Other steps should be done by SAP Support.
Language import – correct components? // Customer (and SAP Support)
- Check if the correct language file is imported.
To check if the correct language file is imported please call transaction SMLT and expand all “language nodes”.
Compare the imported language file with note: 330104
Please double check table CVERS (using SE16) for software components which are present in your SAP system versus those which are covered by the installed language file.
Please be aware that it is technically possible to import a language file for SAP NetWeaver (which covers SAP_BASIS,SAP_ABA and SAP_BW) into an SAP ERP or SAP CRM or an SAP SCM system. But this does NOT make any sense because than all “application specific translations” will be missing later on of course. And it is not necessary either because those language files for SAP ERP, SAP CRM, SAP SCM, and SAP SRM already contain the respective SAP NetWeaver texts anyway.
The texts for DE (German) and EN (English) are in every SAP system by default. Running an extra language import for DE / EN is usually not necessary.
Language import – correct sequence? // Customer (and SAP Support)
- Check if the language import has been carried out in the correct sequence concerning import of Support Packages and or further AddOn products.
Usually the ideal sequence would be:
– Importing language then
– (Optionally installing AddOn , then)
– Applying Support Packages
If this ideal sequence is not used further steps have to be carried out after the language import is done.
There may be separate language files for AddOns. There is an SAP note for every AddOn which describes if there are separate language files and which languages are translated for the AddOn. If so, then these language files should be imported now.
On the other hand translations for an AddOn can be part of the AddOn installation / upgrade transport file. These translations have to be extracted from the data file now. The same applies for Support Packages. There the translations are part of the Support Package data file. Note 195442 describes how to extract those texts from Support Package / AddOn data files.
Starting with ERP 2005 (ECC 600) SAP introduced the so called “Switch Framework”. So former AddOns became SAP standard and could be switched on or off (default).
There are texts which where delivered in BC Sets for “switched application parts”. After importing an language file using SMLT these texts have to be “unpacked” / distributed from the BC Set tables into the target tables of the “switched application”. This can be done using SFW5. See note 876718.
Client dependency of texts // Customer (and SAP Support)
- Are the texts missing in Client 000 or an Client other than 000?
Language import has to be carried out in Client 000.
Parts of the texts are not client-dependent.
Other parts of texts are client-dependent.
Note 2857 describes how the different table classes are handled concerning client data.
The ideal sequence concerning language import and clients would be:
– Importing language (including AddOn languages and Support Packages)
– Doing the client copy
If the texts are present in Client 000 but are missing in an Client different from 000 there are different tools to bring the texts from client 000 into the Client other than 000.
– RSTLAN_SUPPLEMENT_UNI, described in notes 43853 and 211226
– Client Maintenance function in SMLT
– (only valid up to SAP_BASIS 6.10: RSREFILL, described in note 48047)
Please keep in mind:
Data in clients other than 000 are treated as customer data. Existing texts will not be overwritten there. (see Note 2857)
Runtime representation of texts // Customer and SAP Support
- The texts are present in Client 000 and Client different from 000 but are not displayed correctly.
Before texts are displayed, a runtime representation is compiled for them.
To be sure that the runtime is current please run RSLANG20 as described in note 110910.
If you belive that everything is fine up to here but the texts are still missing, then create a problem message for SAP.
In this message please describe as accurately as possible which texts are missing and how to reproduce this in the system. Screen shots will only help in the last phase of analysis to identify the “missing texts” on a particular screen.
Necessary information for a Problem Message // Customer
- Helpful information in the customer problem message:
Please attach a screen shot of the contents of table CVERS of the system. Contents of CVERS can be shown using SE16.
Please attach a screen shot of SMLT which should show all imported language packages for the language where the texts are missing.
Please provide logon data.
Please put the message onto the application queue where the missing texts are probably located.
Ask the application experts to clarify where the missing texts should technically come from / where they are stored / which technical objects they belong to.
Ideally, the following information is required:
– the transport object,
– the software package and
– the software component for which the texts are missing.
Finding the Root Cause // SAP Support – Application Support
- Please locate the development objects, table entries, programs, DYNPROs and so on where the translations are missing and the customer is complaining about.
- It is nearly impossible for SAP translation department (XX-TRANSL-<ISO>), “Language Transport Tool Queue” (BC-CTS-LAN) and “Translation Tool Queue” (BC-DOC-TTL) to do the detailed analysis for finding the texts which should have been translated if every before mentioned step did not help to find the reason for missing translations.
- These people are not familiar with the application itself and need the following information to proceed further:
- Ideally, the following information is required:
- – the transport object,
- – the software package and
- – the software component for which the texts are missing.
- – table where the “missing texts” are stored
- – table key for missing texts
- If this information is available, please include it in the customer’s message and forward it to XX-TRANSL-<ISO>, where <ISO> is the ISO language sign for the language in which the translations are missing.
Source: SAP Note 1000586