CONNE_IMPORT_CONVERSION_ERROR SAP ABAP Runtime Error conne import conversion error

CONNE_IMPORT_CONVERSION_ERROR 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.

CONNE_IMPORT_CONVERSION_ERROR ABAP Runtime 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.

Object name ..................................: <runtime parameter>
Error code in conversion.........................: <runtime parameter>
Length of data to be converted....................: <runtime parameter>
Length of target area............................: <runtime parameter>
Length of data already processed...............: <runtime parameter>
Length of result data so far.........................: <runtime parameter>
Code page of data to be converted..................: <runtime parameter>
Codepage of the system ........................: <runtime parameter> Error in IMPORT statement: Invalid characters or change of length during conversion. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

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

If the IGNORING CONVERSION ERRORS addition is specified, the system does not terminate if it finds inconvertible characters. During conversion of a text from code page <runtime parameter> to code page <runtime parameter>, one of the following occurred:
1) Characters were discovered that cannot be dislayed in one of the code pages
2) A length change was made
3) The conversion could not be performed for some other reason (see below for more details)

Excerpt from the source buffer from the first character that could not be converted, displayed in hexadecimal form (with the ASCII characters in brackets):
<runtime parameter>
If nothing is specified here, scenario 2 or 3 applies.

The ABAP program <runtime parameter> had to be terminated, as the conversion would have resulted in incorrect data.