Solution : https://service.sap.com/sap/support/notes/1036341 (SAP Service marketplace login required)
Summary :
SAP Unicode executables assume UTF-8 encoding during file reads, per SAP standards. Errors occur when non-Unicode encoded text files are read, leading to third-party illegal byte sequence detection and message generation indicating corrupted UTF-8 bytes in hexadecimal form. For instance, Common issues include the misinterpretation of Western European diacritics and Shift-JIS encoded Japanese text. Solution involves using 'sapiconv' tool to convert and check text files for corruption, supporting various code pages depending on the original encoding.
Key words :
fgetcu16 invalid utf-8 unicode interface file input reason, c4 6e--- unicode interface ------ end, shift-jis encoded japanese text, sap unicode executable writes messages, west-european diacritical characters, application server parameter files, legal byte sequences start, profile parameter file, --- unicode interface [u16_get, invalid utf-8 encountered
Related Notes :
1319517 | Unicode Collection Note |
1071731 | Unicode C-programs and access to OS environment |
11682 | Compiling RFC programs |