AIE - with non-unicode system?

[Former Member]

Hello,

today i have tried to connect to one of our non-unicode SAP development systems.

This system is based on 7.31 SP4. SAP-KERNEL 7.20 - 201

In the ABAP project creation wizard i got the error:

"Logon to system xxx failed (System failure: "A character set conversion is not possible." (For detailed information, check the generated short dump in transaction ST22 of system "XXX"))"

In the ST22 the following dump appeared:

Category               ABAP Programming Error

Runtime Errors         CONVT_CODEPAGE

Except.                CX_SY_CONVERSION_CODEPAGE

ABAP Program           CL_ABAP_CONV_IN_CE============CP

Application Component  BC-ABA-LA

Date and Time          31.07.2013 12:37:36

Short text

     A character set conversion is not possible.

What happened?

     At the conversion of a text from codepage '4102' to codepage '1100':

     - a character was found that cannot be displayed in one of the two

     codepages;

     - or it was detected that this conversion is not supported

     The running ABAP program 'CL_ABAP_CONV_IN_CE============CP' had to be

      terminated as the conversion

     would have produced incorrect data.

     The number of characters that could not be displayed (and therefore not

     be converted), is 1. If this number is 0, the second error case, as

     mentioned above, has occurred.

Does AIE only work with an unicode backend server?

Regards,

Christian

[Former Member]

ok, it seems to be there is an oss note availible but not yet released.

1810699 - Dump CX_SY_CONVERSION_CODEPAGE in CL_ABAP_CONV_IN_CE

i will try.

Christian

[Former Member]

Now i have implemented the note 1810699.

Without changing the default encoding of eclipse (UTF-8) it is not possible to access the non-unicode system. After switching to ISO-8859-1 the connection works fine.

But this means that i have to setup a second eclipse workspace to access our non unicode development systems.

Christian

[RaymondGiuseppi]

For me this note looks already released (vaid since Jul 29, 2013) ?

Regards,

Raymond

[schneidermic0]

I would expect that you can use the same workspace for both systems. If you use ADT >= 2.7 you also shouldn't need to adjust the default encoding of Eclipse, since the editors user internally UTF-8 as encuding (independet to your settings).

If this is not the case, I would like to ask you to create an ticket, so that we can analyze this in more detail.

BTW: There are two further notes related to using ABAP development tools with non-unicode systems:

• Note 1810540 - AiE debugger:Program termination in CL_TPDA_ADT_RES_DEBUGGER
• Note 1767013 - Dump CONVT_CODEPAGE when using ABAP Development Tools

Michael

[Former Member]

Yes you are right. I have opended the german version of this note and there i got an hint that there is a newer version in a different language availible.

My fault.

Christian

[Former Member]

Hello Michael,

i'm using 2.13 with a workspace/eclipse setup in UTF-8.

If i try to connect to the non unicode system the error

Logon to system WL1 failed (System failure: "A character set conversion is not possible." (For detailed information, check the generated short dump in transaction ST22 of system

still occurs. I will open a ticket.

Christian

[Former Member]

Hello Mr. Schneider,

With the implementation of oss-note 1767013 it work fine!

Thanks

Christian

[schneidermic0]

Thanks for the update!