Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Runtime error analysis

Former Member
0 Likes
506

Hi could someomne explain what this error means.


   At the conversion of a text from codepage '4110' to codepage '4103':

   - 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 'ZWELL_UPLOAD' 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 234. If this number is 0, the second error case, as
   mentioned above, has occurred.



rror analysis
   An exception occurred that is explained in detail below.
   The exception, which is assigned to class 'CX_SY_CONVERSION_CODEPAGE', was not
    caught in
   procedure "UPLOAD_AS" "(FORM)", nor was it propagated by a RAISING clause.
   Since the caller of the procedure could not have anticipated that the
   exception would occur, the current program is terminated.
   The reason for the exception is:
   Characters are always displayed in only a certain codepage. Many
   codepages only define a limited set of characters. If a text from a
   codepage should be converted into another codepage, and if this text
   contains characters that are not defined in one of the two codepages, a
   conversion error occurs.

   Moreover, a conversion error can occur if one of the needed codepages
   '4110' or '4103' is not known to the system.

   If the conversion error occurred at read or write of  screen, the file
   name was '/oracle/SBX/sapreorg/zwell/zwell_gz/wmi_nts_extract_20090109_1.txt.gz
   '. (further information about the file: "X 570
    1404683rw-r--r--200901191017522009011214215520090116114917")

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
471

Hello,

Try using IGNORING CONVERSION ERRORS in the OPEN DATASET statement.

Thanks!

3 REPLIES 3
Read only

Former Member
0 Likes
472

Hello,

Try using IGNORING CONVERSION ERRORS in the OPEN DATASET statement.

Thanks!

Read only

amit_khare
Active Contributor
0 Likes
471

.gz extension...I think you are trying to upload a zip file with TEXT MODE addition.

Load text file.

Read only

nkr1shna
Contributor
0 Likes
471

Hi,

We faced the same error while during upgrade recently. There are two appraoches you can think of.

1) Use OPEN DATASET command with option IGNORE CONVERSION ERRORS. When it finds

character which it does not understand, it will replace it with # character.

2) You can use exception handling by using construct. TRY.......

You can check for the exception CX_SY_CONVERSION_CODEPAGE and you can either

do nothing or replace the character with any other. By default it replaces with # character.

Best Regards,

Krishna