topic Re: Runtime error CONVT_CODEPAGE while writing file to application server in Application Development and Automation Discussions

Runtime error CONVT_CODEPAGE while writing file to application server

Former Member — Thu, 22 Mar 2012 07:53:46 GMT

Hi All,

We are facing runtime error CONVT_CODEPAGE (Exception CX_SY_CONVERSION_CODEPAGE) while writing a file to application server. I have analysed the error and found that it is caused at transfer statement, because some characters couldn't be written to the file, due to a code page error.

-----------------------------------------------------------------------------------------------------------------------

Extract of short dump:

While a text was being converted from code page '4103' to '1100', one of

the following occurred:

- an character was discovered that could not be represented in one of

the two code pages;

- the system established that this conversion is not supported.

-----------------------------------------------------------------------------------------------------------------------

Open dataset in this case is written as:

OPEN DATASET OUT_FILE FOR OUTPUT IN text MODE
encoding non-unicode type 'NT'. (System where error ocurred is 4.7 Unicode)

I know that short dump can be prevented by the addition of IGNORING CONVERSION ERRORS. But this will just ignore certain characters.

Is there any other way in ABAP by which code page conversions can be controlled, so that conversions take place properly? Is there any Basis fix for this?

Thanks in advance.

Regards,

Arun Mohan

Re: Runtime error CONVT_CODEPAGE while writing file to application server

Former Member — Thu, 22 Mar 2012 08:13:18 GMT

Hi Arun,

Can you check do you have these classes in your version hope it will be there

cl_abap_conv_OUT_ce and cl_abap_conv_IN_ce

if so you can try them as well .by the above class you can convert your codepage 4103 text into xstring, and convert it back into text of codepage 1110.

Thanks,

Deb

Re: Runtime error CONVT_CODEPAGE while writing file to application server

nils_buerckel — Fri, 23 Mar 2012 12:07:44 GMT

Hi Arun,

if the characters included in your content are not supported in the selected Non-Unicode code page (ISO-8859-1 - in SAP 1100), you will not be able to save them. You could use the Unicode mode and create a file in UTF-8. Then all special characters should be preserved.

So are you able to describe the problematic characters ?

Best regards,

Nils