Application Development 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: 

CONVT_CODEPAGE CX_SY_CONVERSION_CODEPAGE from codepage '4110' to codepage '

Former Member
0 Kudos

Hi Experts,

I'm really new with ABAP and I'm trying to ivestigate as to why a job got cancelled previously. As per DUMP information:

Short text

A character set conversion is not possible.

What happened?

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 'RFEKA400' had to be terminated as the conversion

would have produced incorrect data.

The exact line of code where its having trouble with is inside UPLOAD_FROM_UNIX of the program RFEKA400:

READ DATASET AUSZUGFILE INTO SWIFT-ZEILE.

My custome program's code is as follows:

OPEN DATASET file1 FOR INPUT IN TEXT MODE ENCODING

NON-UNICODE MESSAGE mess IGNORING CONVERSION ERRORS .

OPEN DATASET file2 FOR OUTPUT IN TEXT MODE ENCODING

NON-UNICODE MESSAGE mess IGNORING CONVERSION ERRORS .

The dump just happened once and didn't occur again. Is there a way for me to know, which character made this program to terminate(job cancelled)? I have the input files with me, but just by looking at the contents, it seems impossible to figure it out without replicating the dump.

I had this question posted on ABAP general before and moved it here as one of the experts suggested I might be able to get more help from here.

I'm not really sure on what to do next. I checked if the standard program got the OSS notes release. I think it did for I saw the Notes #. I already read some of the responses from around here, some have the same issue but it did not got a reply.

Please help me, your response would be much appreciated.

Thank you in advance!

8 REPLIES 8

Former Member
0 Kudos

Hi,

Note 810519 exactly describes this problem but the note is only for Pilot Release/or specifc customers only.

I would recommend to get in touch with SAP Support to get the note corrections.

Regards,

Srikishan

0 Kudos

Hi Srikishan,

Thanks for your response, sorry for the late reply I've been a little busy.

Anyway, I'm going to check if the note you were referring to was already applied on our system, otherwise, guess I'm gonna have to look for this update.

I'll be updating this post ASAP.

0 Kudos

Hi Srikishan!

I've checked RFEKA400 and it still doesn't have that note.

I would just like to verify, is this note applicable to RFEKA400?

Really appreciate your response!

Thanks!

0 Kudos

Hi,

From the Symptom description of the Note, the same is applicable for RFEKA400 as well.

Extract from symptom part of the Note:

A dump occurs when you import an electronic account statement from the application server: CONVT_CODEPAGE CX_SY_CONVERSION_CODEPAGE in the RFEKA400 or RFEKA200 program in the coding line:

READ STATEMENT FILE DATASET SWIFT ROW INTO.

or

READ DATASET AUSZUG-FILE INTO AUSZUG-ZEILE.

The account statement file is in Swift MT940 or in the Multi Cash Format and contains characters that cannot be interpreted that are represented with '#'.

Regards,

Srikishan

0 Kudos

Many thanks!

This must be really for pilot release/specific customer, for I can't find it on OSS.

Thanks for sharing!

I'd update this thread as soon as I confirmed that this is indeed what we really need.

0 Kudos

Hi Srikishan!

When was 810519 pilot released?

Sorry for bugging you this much if only I have the rights to email sap support I could have emailed them right away.

Thanks!

0 Kudos

Hi,

Note was released for piltot customers on 25.07.2008.

Regards,

Srikishan

Former Member
0 Kudos

Try following :


CALL FUNCTION 'NLS_GET_FRONTEND_CP'
    EXPORTING
      langu                 = sy-langu
      fetype                = 'MS'
    IMPORTING
      frontend_codepage     = lv_codepage
    EXCEPTIONS
      illegal_syst_codepage = 1
      no_frontend_cp_found  = 2
      internal_or_db_error  = 3
      OTHERS                = 4.

OPEN DATASET lv_filename FOR INPUT IN LEGACY TEXT MODE CODE PAGE lv_codepage.

This should resolve your problem.