CX_SY_CONVERSION_CODEPAGE - Unicode error

[Former Member]

Experts,

I get CX_SY_CONVERSION_CODEPAGE dump while transfering certain material text.

LOOP AT material.

TRANSFER material TO file.

CLEAR material.

ENDLOOP.

The same set of characters work fine in test box but it fails in production box. What would be the reason?

Also, how to handle such errors in general?

Would appreciate your thoughts.

UV

[uwe_schieferstein]

Hello

Difficult to say what might be the error cause. However, you may try to use the OPEN DATASET statement with the following options:

OPEN DATASET ...
             IGNORING CONVERSION ERRORS
             REPLACEMENT CHARACTER rc.

If you are using the second option (replacement) you might able to see in the written file which characters caused problems.

Perhaps the first option (ignoring errors) might allow you to write the file successfully.

Of course you have to check the file contents whether it is the expected one.

Regards

Uwe

[Former Member]

Hi Uwe,

Thanks again.

But is there a way to compare test and productive systems to find out why one worked the other did not not?

Also, how would I identify what code page my program uses (Legacy text mode) and what is the ftp servers' code page (I know it gives a no. in the dump!)?

The actual text that fails is as below

"monster cable (CTI/Complete Unit u2013 Temps"

The dump is as shown below

-

---

While a text was being converted from code page '4102' 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.

If a character could not be converted: Use the transaction SPAD to

analyze the code pages you used. Look for characters that you wanted to

convert and that have not been entered in the table.

If the conversion between code pages 4102 and 1100 has not been defined,

you can avoid the error by using a conversion table known to the system.

Use the transaction SPAD to display the conversion tables that have

been implemented. If you have recently maintained a conversion table,

you must invalidate the character set buffer (CCC) using the transaction

SP12.

-

---

UV

[Former Member]

Hi UV,

Plaese check this link for codepage errors. This is an useful one. Hope it helps for you.

Reward points if it was useful for you.

Regards

Abhishek