ABAP Dump: CONVT_CODEPAGE

[Former Member]

Hi All,

Our SAP version is ECC 6.0 and Oracle DB version : 10.2.0.2.0. Every day 2 dumps are generated in our Dev and QA server.

The dump details are:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Runtime Errors CONVT_CODEPAGE

Exception CX_SY_CONVERSION_CODEPAGE

User and Transaction

Client.............. 000

User................ "R3MONITOR"

Language Key........ "D"

Transaction......... " "

Transactions ID..... "4D2D30B42884008B00000000AC17C00B"

Program............. "SAPLZMC1"

Screen.............. "SAPMSSY1 3004"

Screen Line......... 2

Information on caller of Remote Function Call (RFC):

System.............. "M03"

Database Release.... 610

Kernel Release...... 620

Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "asynchron with reply and non-transactional (emode 0,

imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

Client.............. 200

User................ "IMSBATCH"

Transaction......... " "

Call Program........."SAPLZMSFGM01"

Function Module..... "Z_RFC_MCFGM01"

Call Destination.... "DO1_MONITOR"

What happened?

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

- 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 'SAPLZMC1' 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.

What can you do?

Please make a note of the actions and input which caused the error.

-

To resolve the problem, contact your

SAP system administrator.

With transaction ST22 for the ABAP dump analysis, you can analyze and

administrate termination messages, or store them for a longer time

period.

If you were requested by the application to enter a codepage, the

termination may be avoided after the restart of the application if you

enter a different codepage.

If characters could not be converted: Please use transaction SCP to

analyse the codepages used by you. Search for characters you wanted to

convert, which are not entered in the table. (If you changed a codepage,

you can use transaction SP12 to invalidate the character set buffer

(CCC).

You find further help tools to codepages in transaction SNLS.

Error 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 "READ_HEALTHCHECK_LOG" "(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 '4102' is not known to the system.

If the conversion error occurred at read or write of screen, the file

name was '/tmp/sapgetuser.log_DO1'. (further information about the file: "X

16311 19940rw-rr201101120547112011011117000320110111170003")

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Please give me your valuable suggestions to solve the issue. Thanks in advance!!!

Regards,

Veera

[former_member182034 · Accepted solution]

hi veerab,

check this thread..

regards,

[Former Member]

have you checked the existing code page? see below error:

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