Objectives
The installation check using transaction SICK validates the consistency of the newly installed SAP system.
The consistency check determines inconsistencies in your SAP system. This function is also called automatically when you start an application server of your SAP system.
The table structures that are checked include the tables SYST, T100, TSTC, TDCT, TFDIR, and others.
You want to check the installation of SAP system S4X.
Check the installation of S4X, using transaction SICK.
Log on to SAP system S4X, client 000 with your newly created user.
Call transaction SICK.
On the SAP Initial Consistency Check screen, look for errors reported in the SAP System Check field.
You want to check the installation of SAP system SMA
Check the installation of SMA, using transaction SICK.
Log on to SAP system SMA, client 000 with your newly created user.
Call transaction SICK.
On the SAP Initial Consistency Check screen, look for errors reported in the SAP System Check field.
SAP systems supports up to 40 different languages. The language with which a user works is specified through entry on the logon screen, by a SAP Logon setting, by a profile parameter, or by a default setting in the user master record. This language must first be imported into the SAP system before users can log on with the desired language. Only German (DE) and English (EN) are initially installed after a new installation of an SAP system.
During installation it is possible to let SAPinst set up the Transport Management System (TMS). If you use this option, you can choose to let SAPinst install additional languages. Therefor you must provide the corresponding language media.
Note
Without SAPinst setting up the TMS, SAPinst can not install additional languages. This is because the language installation relies on a configured TMS.
After the installation, if required, you can use transaction SMLT to import additional languages.
If you select a language (other than German, English), you should note that the selected language is not fully translated. The texts that are not translated in the selected language must be provided using a supplemental language. This supplemental language must be a completely translated language. This can also be recursively configured so that you use a number of supplemental languages, each of which supplements texts that are not translated in the previously configured languages.
Economic, political, and cultural criteria determine the extent to which individual languages need to be imported into the SAP system and the extent to which these languages are completely translated. User acceptance is an important aspect in these considerations.
The figure above shows an overview of the steps that are required for a language import.
Before you can classify a new language in transaction SMLT, you have to configure the required languages using program RSCPINST. For more information on program RSCPINST see SAP Note 42305 - RSCPINST (I18N configuration tool)
You can also use transaction I18N (area: I18N Menu → I18N Customizing → I18N System Configuration). Choose Add Language to select the country code for each language required and then select the Activate button.
To import additional languages call transaction SMLT. Here you can also find tools for language transports at Goto → Other Tools.
SAP delivers SAP Support Packages to correct errors that occur in SAP transactions. SAP Support Packages can contain language-dependent data, such as message texts, ABAP text pool entries, or screen texts. After importing an SAP Support Package with transaction SPAM or using the tool SUM, the translated texts for these objects have the newest status for all languages that exist in the SAP system. Problems can occur if an additional language is to be imported from the language media into an SAP system in which SAP Support Packages have already been imported. Since the language media is created before the first SAP Support Package is shipped and the objects in the SAP Support Packages are only provided with translations for the languages that have already been imported, importing a language subsequently overwrites the objects contained in the SAP Support Packages. Texts can be incorrect or completely missing.
For more information on languages and SAP Support Packages, see SAP Note 352941 - Consultation: Languages and Support Packages.
You must classify each language in transaction SMLT to make it known to the SAP system. Only then is it possible to import a language package or supplement the language.
You can display the current settings for a language any time by choosing the Information button on the initial screen of transaction SMLT. If no supplementation language was specified when classifying a language, then the language can be specified any time. You can use transaction SMLT to import an additional language package. English (EN) and German (DE) are always completely available in newly installed SAP systems. You therefore do not need to import these into SAP systems. After importing the languages, you must also import the language data contained in SAP Support Packages. To do so, select the affected language in transaction SMLT and choose Language → Special Actions → Import Support Packages.
To fill translation gaps that exist in a language, you should start the language supplementation after the language import. The supplementation actions are client-dependent. The language supplementation is performed in the client that you are logged on. If you use multiple clients, you must perform the language supplementation explicitly in each productive client. You can access the texts stored in cross-client database tables simultaneously from all clients. The default setting is set in such a way that cross-client tables are supplemented if you are logged on to client 000.
Languages can have different degrees of translation:
1 – DE/customizing and documentation complete
2 – DE/customizing complete; documentation in parts
3 – DE/customizing complete; no documentation
4 – DE/customizing application-dependent; no documentation
0 – Not classified; not a standard SAP language
9 – Technical language code
This results in restrictions:
Note
See course ADM103 - System Administration II for SAP S/4HANA and SAP Business Suite for details.You want to check the installed languages of SAP system S4X.
In SAP system S4X, check the code page assignment, using program RSCPINST.
Log on to SAP system S4X, client 000 with your newly created user.
Call transaction SA38 and execute program RSCPINST.
On the I18n Language Configuration screen, you should see, that German (DE) and English (EN) are log on languages, are translated, and are assigned to the Unicode code page. Here you can maybe also see additional languages, that were installed by SWPM.
In SAP system S4X, check the language import of DE and EN, using transaction SMLT.
Call transaction SMLT.
On the Language Management screen, expand English and German and look for status Imported completely. Here you can maybe also see additional languages, that were installed by SWPM.
In SAP system S4X, check the profile parameter zcsa/installed_languages, using transaction RSPFPAR.
Call transaction RSPFPAR.
Try to display profile parameter zcsa/installed_languages.
You want to check the installed languages of SAP system SMA.
In SAP system SMA, check the code page assignment, using program RSCPINST.
Log on to SAP system SMA, client 000 with your newly created user.
Call transaction SA38 and execute program RSCPINST.
On the I18n Language Configuration screen, you should see, that German (DE) and English (EN) are assigned to the Unicode code page.
In SAP system SMA, check the language import of DE and EN, using transaction SMLT.
Call transaction SMLT.
On the Language Management screen, expand English and German and look for status Imported completely.
In SAP system SMA, check the profile parameter zcsa/installed_languages, using transaction RSPFPAR.
Call transaction RSPFPAR.
Display profile parameter zcsa/installed_languages.
Business functions can be ENTERPRISE_EXTENSIONS, ENTERPRISE_BUSINESS_FUNCTIONS, or Industry Solutions, for example UTILITIES. In SAP S/4HANA server systems there is also a category S/4H_ALWAYS_ON_FUNCTIONS. Client-independent activation switches allow you to activate these functions.
You activate a business functions by selecting it and using the Activate button in transaction SFW5, the Switch Framework. Transaction SFW5 provides additional information about the business functions. After activating business functions, a batch job is started that switches all objects belonging to the selected business function.
Hint
Business functions are activated manually only in the development system. They are transported to the subsequent SAP systems where they are imported. The import in the subsequent SAP systems automatically starts the batch job for activating the individual object switches.Generally, you cannot deactivate an activated switch because after activation data is maintained in a different way than it would be if the switch was inactive. This depends on the component and the actions performed in the SAP system after activation. SAP recommends activating and testing the switches in a sandbox system before activating them in the development system, because you generally cannot deactivate the switches.
You want to check for available business functions.
Compare the available business functions between SAP systems S4X and SMA, using transaction SFW5.
Log on to SAP systems S4X, client 000 and SMA, client 000 with your newly created users in parallel.
In both SAP systems call transaction SFW5 and confirm the Security Information pop up with Continue. Roughly compare the available business functions.
Log in to track your progress & complete quizzes