As of SAP Web
Application Server Release 6.10 there is a new upgrade procedure, the
The new procedure installs an instance of the target release (shadow system) in parallel with the running source release system on the same database. This parallel system contains all the software of the target release and is used to integrate any Support Packages included in the upgrade, add-ons, and customer modifications into the target release.
The language data is imported into the “shadow” system. This data is merged with customer object data, and only then is it made available to the new runtime environment. This also applies to the corresponding language-specific tables.
As a result, the language import is a part of the upgrade procedure. At the start of the upgrade, the system asks you whether you want to import all installed languages during the upgrade.
English and German are always imported in the upgrade. If you choose to import languages subsequently, that is, after completing the upgrade, you need to use transaction SMLT.
A language import during the upgrade consists of the following phases:
This phase analyzes the available language CDs and add-on CDs, and unpacks the language packages that can be used in the upgrade into the upgrade directory. You are asked which languages you want to update with the language packages during the upgrade.
The analysis of the language CDs is logged. The file PEVALLAN.<SID> is created in the log directory of the upgrade. This file contains additional information about the packages and can help you to find out the source of any problems.
● Phase JOB_RSTLANUPG
This phase sets the SMLT control information for the language packages imported during the upgrade.
The languages are
imported into the system using the same procedure as for Support Packages,
EHPs and Add-ons. This is how translations are loaded into the shadow system
during the SHADOW_IMPORT_ALL phase.
The fact that the language data is always imported before any Support Packages, EHPs, and Add-ons in the upgrade means that there are no sequence problems.
After the upgrade you must use transaction SMLT to supplement the imported languages.
If you use customer language ’Z’ in your system, read SAP Note 964731.