ABAP Runtime Errors

CONNE_IMPORT_WRONG_COMP_DECS SAP ABAP Runtime Error conne import wrong comp decs







CONNE_IMPORT_WRONG_COMP_DECS 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_WRONG_COMP_DECS ABAP Runtime Error

Try to find out why the number of decimal places in the object is <runtime parameter>.
There are several possibilities:

1. The number of decimal places in the imported field has changed in the Data Dictionary. Make sure that the number of decimal places in the imported field is the same as the number of decimal places in the field in the Data Dictionary.

If the data cannot be restored from another source, the data must be read, converted and exported using the "old" structure. This ensures that future IMPORTs always use the new structure.

2. A new program version is active which no longer matches the data set.
Try to correct the error by regenerating program <runtime parameter>. To do this, proceed as follows: Call transaction SE38 in the SAP system. Enter the program name <runtime parameter>. Then choose "Generate". 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.

Error during IMPORT of object <runtime parameter> Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

When importing object <runtime parameter>, component number <runtime parameter> in the dataset had a different number of decimal places to the number of decimal places in the corresponding component of the target object in program <runtime parameter>.

The number of decimal places in the dataset is <runtime parameter> but <runtime parameter> in the program. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.