Codepage issue

[former_member237879]

Hello everybody,

I would like to know from where the function CUR_LCL extracts its CODEPAGE parameters, as it still outputs on an unicode system where 4110 (UTF8) codepage should be used, 4103 (UTF16), so a conversion is automaticly performed when an abap read dataset is done on a file which contains accentuated characters like 'é', that leads to a dump with exception CX_SY_CONVERSION_CODEPAGE.

You cannot convert the character set.

utf8 locales are installed on a Linux where stands the unicode A.S. (ECC5). I got the same issue with a 4.7x200 unicode system.

the system locale are set LC_ALL=fr_FR;LANG=fr_FR

the result of RSCP0018 says so :

kernel>: OPSYSREL

tous Linux

kernel>: OSRELEAS

tous 2.4.21-13

kernel>: UC_LN

tous 2

wp> : ASPLANGS

tous DEF

wp> : CODEPAGE

tous 4103

wp> : GUICP

tous 4110

wp> : LANG

tous F

wp> : LOCALE

tous C

wp> : LOCCOLLA

tous C

wp> : LOCCTYPE

tous C

install/codepage/appl_server

tous 4110

RSCPINST says all is OK

Thank you in advance for any information.

Regards

NORKA F.

[Former Member]

Hello,

I have the same problem. Did you have an issue ?

Thanks in advance !!!

Hicham F.

[vincentlim826]

Hi,

SAPs Unicode systems are running always with the code page 4102 or 4103

depending on the hardware the application server is installed

(UTF-16 little or big endian). It is independent of the operating

system locales. We are using an internal library (ICU) to

cover all locale functions in a operating system independent way.

Therefore CUR_LCL does not output the operating systems active

locale, but the currently active SAP codepage of the application server.

Regards,

Vincent