Solution : https://service.sap.com/sap/support/notes/13876 (SAP Service marketplace login required)
Summary :
The frontend cannot communicate with the application server if the SAP_CODEPAGE environment variable is set to a character set different from the application server's. This often occurs in R/3 systems using ISO8859-x code pages. When R/3 is regenerated, SAPGUI terminates with an "Abnormal Termination" error, even requiring a Windows restart. The issue arises because the necessary conversion file is absent in the frontend, crucial for SAPGUI during data transmission via RFC. The solution involves generating the conversion file using transaction SM59 and transferring it to the frontend SAPGUI directory, setting the PATH_TO_CODEPAGE variable appropriately.
Key words :
call sm59 menu option rfc -> generate conv, file <source-code-page><target-code-page>, cp 1504 = ms windows cp 1251, additional key words error, platform specific path identifier, set path_to_codepage=<sapgui working_directory>, source code page, target code page, set sap_codepage=1504 set path_to_codepage=, frontend environment variable sap_codepage
Related Notes :
86060 | Add. Infor: Add-On P1K install. for R/3 3.1H(Korea) |
81439 | Additional Info: Upgrading to Japanese 31H DB2 |
81438 | Additional Info: Upgrading to Japanese 31H MSSQLSRV |
81434 | Additional Info: Upgrading to Japanese 31H ADABAS D |
81433 | Additional Info: Upgrading to Japanese 31H INFORMIX |
81432 | Additional Info: Upgrading to Japanese 31H ORACLE |
65723 | Additional Info: Upgrading to Japanese 30F ADABAS |
65722 | Additional Info: Upgrading to Japanese 30F INFORMIX |
65721 | Additional Info: Upgrading to Japanese 30F ORACLE |
47976 | Additional Info: Upgrading to Japanese 30E ADABAS |
47975 | Additional Info: Upgrading to Japanese 30E INFORMIX |
47933 | Additional Info: Upgrading to Japanese 30E ORACLE |
47408 | Taiwanese R/3 |
47036 | Chinese (Main land China) R/3 System |
45463 | Thai installation procedure |
39473 | locale and TCP0C |