Frontend cannot communicate with the application server if the frontend environment variable SAP_CODEPAGE is set to a character set unlike that of the application server.
This is normally the case for the R/3 Systems, which use the code page ISO8859-x, x=2...,9 (for example Russian: ISO8859-5 = Codepage 1500, frontend SAP_CODEPAGE=1504).
Whenever R/3 is automatically regenerated, and the message "Compiling ..." appears in the status line of the SAPGUI: The SAPGUI terminates with the error message "Abnormal Termination ...".
Even Windows must then be restarted in order to be able to use SAPGUI again.
The conversion file for character conversion does not exist in Frontend. This file is needed if the RFC interface is to send data to the SAPGUI (for example, during regeneration).
The SAP_CODEPAGE parameter has two effects:
- 1. The character set of the frontend is sent to the R/3 kernel. The kernel undertakes further conversions by using conversion tables in the databank (maintain with transaction SPAD).
- 2. The RFC receiver in SAPGUI is set to this codepage. Since during RFC the receiver must perform the conversion and the frontend has no direct access to the databank, a conversion file must be available for the conversion.
The corresponding conversion file must be recognized by the SAPGUI and generated from R/3:
1. Login R/3, user SAP*. client 0002. Call SM59 menu option RFC -> Generate conv. tab. or start the report RSRFCPUT using SE38.
Parameter:
a) Source code page (= APPL server character set, for example, 1500 for Russian), (Check: SE38: RSPARAM: parameter value install/codepage/appl_server)b) Target code page: Code page, which is set as the DOS Paremeter SAP_CODEPAGE, and runs in the SAPGUI.
(check: DOS shell, then "set" shows the SAP_CODEPAGE)
c) Path: The path on the application server (on UNIX, for example, /tmp/), in which the generated conversion file is stored.
Caution:
The path must end with a path identifier (for UNIX: SLASH)
Effect: A file
File format:
Each line contains a number in Hex format. For example: during a
conversion in which all characters are transferred indentically,
each line contains the line number in Hex format--as follows
0x00 (Meaning: Character 0x00=Line 0 is changed to character 0x00)
0x01
0x02
....
0xFF
2a. If 2. is not possible because SM59 is also compiling and the SAPGUI terminates once again, it is possible (from 3.0B) to switch off the conversion at the front end temporarily. Simply set PATH_TO_CODEPAGE to NONE. The path is "fixed" only when the codepage is generated with SM59.
2b. If you have 3.0A or an older release, you can call the c program ldcdprfc on the application server. Enter the appropriate connect options and do not forget -3 as an option.
Example: ldcdprfc -d C11 -3 =s 00 -h myhost -u SAP -p PASS -S 1100
-T 1105 -P /usr/sap/C11/
This program creates the codepage files without using the GUI.
3. The file generated must be transferred to the frontend (for example with ftp, binary), into the SAPGUI working directory.
The file has the extension CDP.
4. In the AUTOEXEC.BAT file on the frontend, a line must be created with the DOS environment variable:
SET PATH_TO_CODEPAGE=
Do not forget the platform specific path identifier at the end.
Example:
a) the application server uses code page 1500 (Russian ISO8859-5)
b) The Frontend uses CP 1504 = MS Windows CP 1251 (Russian MS Windows);, the SAPGUI working directory is C:\SAPGUI
- The conversion file should be called: 15001504.CDP - in AUTOEXEC.BAT: SET SAP_CODEPAGE=1504
SET PATH_TO_CODEPAGE=C:\SAPGUI\
- in R/3 SM59: source CP: 1500, target CP: 1504, Path: /tmp/- on the application server, the file /tmp/15001504.CDP is generated, which must then be transferred to the C:\SAPGUI directory on the PC.
Additional key words
Error in the application program, SAPGUI crash, code page, conversion
Key word: Code page. Conversion, character set, SAP_CODEPAGE, SAPGUI
No comments:
Post a Comment