CONNE_IMPORT_WRONG_COMP_TYPE error

Question

hello guyz were having a problem, where implementing a function module and a datasource to be extracted to used by BW, we have 4 different Cluster Dev Boxes, namely: CD1, GDD, TD1, and QD1, the said function Module works in the 3 boxes excpt the CD1 box, the function module dumps and return this error, the function module works well on 3 boxes, GDD, TD1 and QD1. Ive also check and the Function Module is also in the CD1 box already.. thank you very much in advance....
<b>ABAP runtime errors    CONNE_IMPORT_WRONG_COMP_TYPE
       Occurred on     21.12.2005 at 09:48:26
Error when attempting to IMPORT object "MC12VC0ITM_TAB".
What happened?
The current ABAP/4 program "SAPLMCEX " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
When attempting to import data, it was discovered that the data
type of the stored data was not the same as that specified in the
program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.</b>

Answer 1

hi,
take a look oss note 328181
Symptom
If you change an extract structure in the Customizing Cockpit (Transaction LBWE) by importing a support package, a transport or by carrying out an upgrade, this can cause various errors if it had already been activated for update for quite some time:
The initialization on data that was generated before the change no longer works (CONNE_IMPORT_WRONG_COMP_LENG).
Delta requests terminate (CONNE_IMPORT_WRONG_COMP_LENG).
The V3 update is no longer processed.
The update from the extraction queue (update mode "Delta Queued", as of PI(-A) 2002.1) does not finish.
The protocol terminates(CONNE_IMPORT_WRONG_COMP_TYPE)
A change to one of the LIS communication structures which are the basis for the extract structure or, in individual cases, also to further application tables (e.g. MSEG, inventory management) may lead to the same symptoms.
Other terms
LBWE, CONNE_IMPORT_WRONG_COMP_LENG, CONNE_IMPORT_WRONG_COMP_TYPE, IMPORT_ALIGNMENT_MISMATCH, CONNE_IMPORT*, IMPORT, V3, SM13, update, MCEX_UPDATE_02, MCEX_UPDATE_03, MCEX_UPDATE_04, MCEX_UPDATE_05, MCEX_UPDATE_05_1, MCEX_UPDATE_08, MCEX_UPDATE_11, MCEX_UPDATE_12, MCEX_UPDATE_13, MCEX_UPDATE_17, MCEX_UPDATE_17_1, MCEX_UPDATE_18, MCEX_UPDATE_18_1, MCEX_UPDATE_40, MCEX_UPDATE_43, MCEX_UPDATE_44, MCEX_UPDATE_45, MCEX_UPDATE_45_1, MCEX_BW_LO_API
Reason and Prerequisites
When you change a structure, the data which is stored in the old form of the structure can no longer be interpreted correctly.
Since changes can be also be made to extract structures (or to other update-relevant structures) as well as to basic data definitions for an R/3 upgrade or plug-in upgrade and (in very seldom cases) when importing an R/3 standard or plug-in Support Package, the precautions mentioned below should also be followed beforehand.
Solution
You should carry out the following steps before you change a structure:
1. Make sure that the following steps are carried out at a time when no updates are performed so that no data is lost.
2. Start the update collective run directly from within the Customizing Cockpit. Up to PI(-A) 2001.2 , this collective run exclusively concerns the V3 update. As of PI(-A) 2002.1, depending on the update mode setting of the application, the collective run concerns either the V3 update or the update from the extraction queue ("Delta Queued", see Note 505700).
3. Load all data of the respective DataSource into the BW System.
Now you can make the change.
After a change you can no longer use the statistical data already recreated. If such data still exists, you should delete it (Transaction LBWG).
We recommend in particular to upload the data immediately after a restructuring and (after checking in BW) delete them from the restructuring tables.
Moreover, the update log (Transaction LBWF) can no longer be read. Post a document in this case so that the last log entry is overwritten. This log entry then has the correct new format of the extract structure.
As of PI 2000.2 the program RMCEXDELETELOG is available. It can be used to delete log entries.
Remark:
The program RMCEXDELETELOG is available in the current PI 2000.1 patch.
However, no success message is displayed.
You can also import the program from the sapserv computers. It can be found in the directory /general/R3server/abap/note.0328181. However, only German texts have been maintained.
If you forget to process the V3 update before a change the only option is to delete the records that still exist, that is, this data is lost.
To do this,
for V3 update methods, go to the update overview (Transaction SM13), select the records (user *, V2 executed, set date), and select Update records -> Delete -> All records. Do not forget to deactivate the flag "Only incorrect".
for update method "Delta Queued" (as of PI(-A) 2002.1) go to the logistics queue overview (Transaction LBWQ). Mark the queues for the applications concerned one after the other (MCEXnn, nn = number of the logistics application, see Transaction LBWE), and choose the display function. Then choose the display function again to list all entries of the queue. Then select and delete all entries that had been stored before the structure change. In case of a very large number of entries in a queue it may be required to delete the entire contents of the queue. This is possible already on the initial screen of Transaction LBWQ.