Solution : https://service.sap.com/sap/support/notes/838402 (SAP Service marketplace login required)
Summary :
SAP has announced that starting from the 2007 releases of SAP NetWeaver and related applications, new installations will not support non-Unicode systems, aligning with a broader strategic direction towards Unicode. Current non-Unicode systems will continue to receive support; however, SAP recommends converting to Unicode, especially when upgrading to NetWeaver 7.0 or later to avoid inherent limitations and potential data loss associated with non-Unicode systems. Key issues include support for only one non-Unicode code page per system, unsupported characters in different languages, and compatibility challenges with Unicode-based technologies that may result in uncontrolled data loss.
Key words :
ms-office integrationin ms-office user, -unicode sap system uncontrolled data loss, http/htmlin web based frontend, world-wide existing character sets, -unicode code pages sap recommends, technology independentduring data exchange, attached customer letter customer_letter_64_u, single code page reason, -unicode code pages support, unicode based technologiesmost technologies
Related Notes :
| 1489357 | No support for code page 1810 in release 7.00 and higher |
| 1413544 | Implementation recommendations for SCM 5.0 |
| 1400236 | Prerequisites for Xcelsius usage with NetWeaver BI/BW |
| 1359215 | Technical prerequisites for using enterprise services |
| 1358929 | Deprecation of SOA features with non-Unicode Backend |
| 1319517 | Unicode Collection Note |
| 975768 | Deprecation of Java features with non-Unicode Backend |
| 910707 | Linux: Japanese locale (ja_JP.SJIS) on Linux |
| 869757 | Table TCUSC correction after Unicode conversion |
| 832393 | Release Restrictions for SCM 5.0 |
| 658052 | TREX 6.1/7.00: additional info about TREX ABAP client |
| 447596 | Euro sign/Trademark sign: processing |
| 79991 | Multi-Language and Unicode support of SAP applications |
| 73606 | Supported Languages and Code Pages |