Search This Blog

Loading...

Monday, February 7, 2011

SAP Note 195442 - Language import and Support Packages




Symptom
You want to install/import an additional language into a system in which you have already imported Support Packages or Add-On Packages (Add-On installation packages and Add-On Support Packages).
Before you start the import, transaction SMLT displays information telling you that, by subsequently importing the (additional) language, textual inconsistencies may occur for THIS language.
The text inconsistencies may arise as follows:
Technical corrections in Support Packages can also change texts. These texts are delivered with the technical corrections in the Support Package and are imported into the system.
If you want to import a language, you must distinguish between the following cases:

    1. you should import the language in question in the system FIRST: The texts in the Support Packages or Add-On Packages are only imported for those languages that are already installed in the system. If you install a language after you have imported Support Packages or Add-On Packages, this language is only the level of the delivery. Changes due to Support Packages are not taken into account: Texts that are part of an add-on, which does not deliver a language package, are missing completely.
    2. you should import the language in question again in the system: Changes in the texts are imported into the system with the Support Packages BUT the language on the CD also only represents the version at the time of delivery. The changed texts can be overwritten again with the "old" delivery texts when you import.

The problems associated with languages and Support Packages are described in Note
352941.



Other terms
Language import, Support Packages, add-on, OCS import


Reason and Prerequisites
In Release 4.6C, the language transport has been changed to the SAP standard transport tool tp/R3trans.
As of Release 4.5A, you could carry out a language import at any time and subsequently import the language part of the Support Package. This function was not implemented in Releases 4.6C and Basis Release 4.6D respectively.
As of BASIS Release 6.10, the RSTLAN_IMPORT_OCS program is available by default. No restrictions are known regarding the R3trans or tp versions.
For importing the language part of Add-On Packages, SPAM Version 20 is required, and Version 21 is recommended.
A corresponding solution for subsequently importing language parts from Support Packages or Add-On Packages is described below.



Solution
Due to an enhancement in the 'R3trans' and 'tp' programs, we can now provide a solution that you can use to subsequently import the language part from Support Packages or Add-On Packages.


General description of the procedure
If you import a language after you have already imported Support Packages or Add-On Packages in the system, you must subsequently import the language part of all imported Support Packages or Add-On Packages in the correct import sequence. The required versions of the 'tp' and 'R3trans' programs can subsequently import the part of a specific language belonging to a request that was already imported.
The R3trans data files, pat files or corresponding CAR archives from SAPNet or from a Support Package Collection CD must be available for this.



Prerequisites
You require the following tools to use this procedure:
  • R3trans: Release 4.6D, with release date Feb/13/2002 or later.
           Reason: Most recent improvements and error corrections during "post language import".
            Note: If you have imported the LCPs SAPKE46C25 and SAPKE46C33 into your system, you must use the R3trans mentioned above to prevent errors occurring when you import the texts. If you use an older R3trans version, texts may be deleted in the import language, which will take a lot of effort to restore.
  • tp: Release 4.6D, Version 305.12.15 or higher.
           Reason: Starting R3trans in special mode, direct import without buffer entry
           Note that you can only use Release 4. 6D tp or R3trans with the downward-compatible 4.6D kernel.
  • SPAM update: Version 31 or higher (valid for Release 4.6x)
           Reason: Providing the program RSTLAN_IMPORT_OCS, which controls the entire import process.
           Note: The RSTLAN_IMPORT_OCS program was made available up to now in Support Packages of the component SAP_BASIS or as a transport request using sapservX. Due to the close relationship to transaction SPAM, this program will be delivered and further developed in SPAM updates as of SPAM Update Version 31. Note that if you import one of the Support Programs listed below, the program RSTLAN_IMPORT_OCS will be replaced by an earlier version. To use the current version of this program, you may need to import the current SPAM update again. Importing the same SPAM update again is described below.
  • SPAM update: Version 22 (as of Release 6.x)
           This is only required if you also need to import language parts from Installation Packages and Add-On Packages. Otherwise, there are no prerequisites for Releases 6.x and 7.x.
The program RSTLAN_IMPORT_OCS is only able to take add-on imports and upgrade packages into account as of the above-mentioned version.


Start the RSTLAN_IMPORT_OCS program for the newly-imported language to import the Support Package texts.
As of Release 6.10, you can also start the RSTLAN_IMPORT_OCS program directly in transaction SMLT. To do this, call the following menu option: Language -> Special Actions -> Import Support Packages

Operating the RSTLAN_IMPORT_OCS program

Note: Before you start the program, check whether objects are recorded in pending repairs. No language list is imported for repaired objects. Release pending repairs if necessary.
Selection screen
Specify here for which language you want to import the Support Package texts again. A screen is then created in which all imported Support Packages are displayed.
Screen 1: Support Package list
All Support Packages and Add-On Packages are categorized by a traffic light as follows.
green: A subsequent import is not required for these Support Packages.
yellow: A subsequent import is not required, but it is possible.
red: A subsequent import is essential.
In the selection column, all Support Packages with a red traffic light are selected, while all others are not. You can also select further Support Packages with a yellow traffic light (usually this is not required). Switch to the next screen using the F6 key. A search for usable files in the file system is done along the way.
Screen 2: Search for required files
To import the Support Package, data is required 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, then it searches for PAT files in the "EPS inbox" (usually $TRANS_DIR)/EPS/in ), and finally it searches for CAR archives in the directory $(TRANS_DIR)/tmp.
It is possible to search for CAR archives in additional paths. Enter the relevant path in the input field and start the search. In the search path, subdirectories up to depth 1 are also searched so that a Support Package collection CD with a single path specification can be searched.
Note: When you search for matching CAR archives, the following assumptions are made: If the CAR archive is called Kxxxxxx.CAR, it is assumed that it includes Support Package SAPKxxxxxx. This is always the case if it has been downloaded from SAPNet or is on a Support Package Collection CD.Important: Not all files are required at the same time. You can start the import with the first X files and continue the import later with the X+1 files. A relevant restart function is available.
Go to the next screen (F6 key).
Screen 3: Start of the import process
An import queue is displayed here that now needs to be edited. Press the F6 key to start the import process.
Screen 4: Import process
All Support Packages or Add-On Packages are processed consecutively. The import process occurs online, similar to transaction SPAM. Time-out problems should not occur. Import each Support Package in the following way:

    • Copy the CAR archive to $(TRANS_DIR)/tmp, if required.
    • Extract the CAR archive, if required. A PAT file is created.
    • Disassemble the PAT file, if required. An R3trans data file is created.
    • Import the R3trans file in special mode.

Import process files (CAR archive in $(TRANS_DIR)/tmp, PAT files and R3trans files), which have been created temporarily, are deleted again as soon as possible to prevent an overflow in the file system. However, large import logs are written in the 'log' directory of the transport directory.
Possible errors:
Errors are possible in each phase of the import process. The program then stops and displays an error message in the status column. You can continue with the import process after you have eliminated the error. An error code is displayed in the status column if an error occurs.  The relevant error codes and what they mean are explained below.

Possible errors when you copy the CAR file:
10: The source file could not be opened. -> Authorizations correct ?
11: The target file $(TRANS_DIR)/tmp/tmp.CAR could not be created -> Authorizations correct ?
12: Error when you copy the files -> File system full ?

Possible errors when you extract the CAR file:
21 to 25: Error when you read the CAR file -> is the relevant file available and readable?
26 to 30: Error when you extract the CAR file
23+28: Are the programs CAR and SAPCAR available?

Error when you disassemble the PAT file:
40: The extracted PAT file does not contain the transport request you expected.
Caution: Use the SAPCAR tool to access CAR files. 'SAPCAR' succeeds 'CAR', which still exists. Problems may occur at this point since 'SAPCAR' is not downward-compatible to 'CAR' in every respect. We recommend that you move the 'SAPCAR' tool temporarily for this process from the kernel directory to another position in the file system. Therefore, the system reverts to the 'CAR' tool, so this error should not occur again as a result. SAP is aware of this problem and it will be corrected in the next SPAM update.
41 to 49: Error when you disassemble the PAT file

Possible errors when you import the language data
61-67: Error when you create the cofile
71-77: Error when you import the data
81-87: Error during DB - Connect -> System configuration o.k. ?
61, 71 and 81: tp command is not supported: -> Is SPAM update #20 imported?
64, 74 and 84: No authorization to carry out the action
65, 75 and 85: tp could not be called -> System configuration o.k. ?
Activating the translation
( This occurs automatically in a later version. See below).
The translations are transferred into the system after importing, but may not be displayed due to the presence of a language-dependent buffer and runtime objects. Then execute the program RSLANG20 with "/$CUA" to reset this buffer. For further information, see Note
110910.
In addition, you must activate and cascade SAP script forms. To do this, execute the Report RSTXINSH that is described in Note
326801.
Logging
In transaction SMLT, a new action called "OCS_IMPORT_<Iso code>_<Release>" is created in which the processed Support Packages are listed in the import actions for the processed language
Corrections and enhancements to program RSTLAN_IMPORT_OCS
  • Sometimes an incorrect import queue was calculated, which meant that you could not change from screen 1 to screen 2. This error has been corrected.
  • The translation is now activated automatically.
  • Lock to prevent parallel use of the program, handling pending repairs: Overwriting or stopping the import
  • Add-On installation packages and Add-On Packages are now taken into account and imported if necessary. This applies as of SPAM Version 20 (Release 6.x) and SPAM Version 21 (Release 7.x).

Importing the SPAM update again
You can import the current SPAM update as follows:

  • Move all files from the directory (transport directory)/EPS/in to another directory at the operating system level
  • Transaction SPAM -> Support Packages -> Import package
  • -> execute from application server
  • Move the saved files again to the (transport directory)/EPS/in
  • Transaction SPAM -> Support Packages -> Import package-> execute from application server
  • Transaction SPAM -> Support Packages -> Import SPAM update.




Affected Releases
Software
Component
Release
From
Release
To
Release
And
subsequent
SAP_APPL
46C
46C
46C
 
SAP_BASIS
46
46C
46D
 
SAP_BASIS
60
610
640
 
SAP_BASIS
70
700
700
 
SAP_BASIS
71
710
710
X

Correction delivered in Support Package
Support
Packages
Release
Package
Name
SAP_BASIS
46C
SAP_BASIS
46C
SAP_BASIS
46C
SAP_BASIS
46C
SAP_BASIS
46D
SAP_BASIS
46D
SAP_BASIS
46D
SAP_BASIS
46D
SAP_BASIS
46D

No comments:

Post a Comment