CONVT_NO_CONVERSION_OBJ SAP ABAP Runtime Error convt no conversion obj

CONVT_NO_CONVERSION_OBJ is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: A - ABAP Programming Error

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.

CONVT_NO_CONVERSION_OBJ ABAP Runtime Error

Look in the developer trace file for entries with CX_SY_CODEPAGE_CONVERTER_INIT. These entries specify which codepages were involved.

If the exception CX_SY_CODEPAGE_CONVERTER_INIT is not caught then a runtime error occurs, which gives further clues as to the cause for the error.

Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.

Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.

Inconsistent codepage converter object. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

The conversion of data from one code page to another was not possible becasue the object of the class CL_ABAP_CONV_*_CE was not consistent. It does not contain a character set convertor object.

It is probable that the exception CX_SY_CODEPAGE_CONVERTER_INIT was caught in the ABAP program and tried to carry out the conversion. This is not possible. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.