Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG

Former Member
0 Likes
1,488

Hello Everyone,   I got the abap dump with exception CX_SY_IMPORT_MISMATCH_ERROR. and  Runtime Errors         CONNE_IMPORT_WRONG_COMP_LENG In Error Analasys:   Runtime Errors         CONNE_IMPORT_WRONG_COMP_LENG Exception              CX_SY_IMPORT_MISMATCH_ERROR Date and Time          24.07.2013 17:03:44                 Short text           Error when attempting to IMPORT object "DATA".                 What happened?           Error in the ABAP Application Program                      The current ABAP program "Z..._MAIN" had to be terminated because it has           come across a statement that unfortunately cannot be executed.                 What can you do?           Note down which actions and inputs caused the error.                                 To process the problem further, contact you SAP system           administrator.                      Using Transaction ST22 for ABAP Dump Analysis, you can look           at and manage termination messages, and you can also           keep them for a long time.                 Error analysis           An exception occurred that is explained in detail below.           The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was            not caught and           therefore caused a runtime error.           The reason for the exception is:           When importing the object "DATA", the component 1 in the dataset           had a different length from the corresponding component of the           target object in the program "Z...".                      The length is 20 in the dataset, but 40 in the program.                 How to correct the error           Try to find out why the length of the object should be 20.           There are various possible options:                      1. The length of the imported field has changed in the Data Dictionary.              Make sure that the length of the imported field matches the length              of the field in the Data Dictionary.                         If the data cannot be restored from another source, the data must be              read by the 'old' structure, converted und again eported with the new              structure, so that future IMPORTs will always function with the new              structure.                      2. A new program version is active, which no longer fits the dataset.              Try to solve the error generating the program "Z..._MAIN" again. This              works as follows: Select transaction SE38 in the SAP system. Enter              the program name "Z..._MAIN". Then activate the function 'Generate'.                                 If the error occures in a non-modified SAP program, you may be able to           find an interim solution in an SAP Note.           If you have access to SAP Notes, carry out a search with the following           keywords:                      "CONNE_IMPORT_WRONG_COMP_LENG" "CX_SY_IMPORT_MISMATCH_ERROR"           "Z..." or "..."           "START-OF-SELECTION"                                                  System environment           SAP-Release 700                      Application server... "ECC-DE2-00"           Network address...... "..."           Operating system..... "SunOS"           Release.............. "5.10"           Hardware type........ "sun4u"           Character length.... 16 Bits           Pointer length....... 64 Bits           Work process number.. 0           Shortdump setting.... "full"                      Database server... "ECC-DE2-00"           Database type..... "ORACLE"           Database name..... "..."           Database user ID.. "..."                      Terminal................. "..."                      Char.set.... "C"                      SAP kernel....... 700           created (date)... "..."           create on........ "SunOS 5.9 Generic_117171-13 sun4u"           Database version. "OCI_102 (10.2.0.2.0) "                      Patch level. 333           Patch text.. " "                      Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"           SAP database version. 700           Operating system..... "SunOS 5.9, SunOS 5.10, SunOS 5.11"                      Memory consumption           Roll.... 16192           EM...... 33518784           Heap.... 0           Page.... 270336           MM Used. 1698776           MM Free. 2488472                                  Information on where terminated           Termination occurred in the ABAP program "Z..._MAIN" - in            "START-OF-SELECTION".           The main program was "Z..._MAIN ".                      In the source code you have the termination point in line 82           of the (Include) program "Z..._MAIN".                 Source Code Extract      Line     SourceCde         52              53     DATA: it_tabdescr TYPE abap_compdescr_tab,         54            wa_tabdescr TYPE abap_compdescr.         55     DATA: ref_table_descr TYPE REF TO cl_abap_structdescr.         56              57     DATA: ws_dd03l TYPE dd03l.         58              59     *----------------------------------------------------------------------*         60     * Selection screen         61     *----------------------------------------------------------------------*         62     AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.         63       PERFORM help_fichier_pc USING p_file.         64              65     *-----------------------------------------------------------*         66     * Start-of-selection         67     *----------------------------------------------------------------------*         68     START-OF-SELECTION.         69       SELECT SINGLE * INTO ws_custo FROM zbc_extr_cust         70                                   WHERE modul = p_modul         71                                   AND conv = p_conv         72                                   AND modif = p_modif.         73       IF sy-subrc = 0.         74         PERFORM prep_data.         75         EXPORT fieldcat FROM it_fieldcat TO MEMORY ID 'FIELDCAT'.         76         SUBMIT (ws_custo-programm)         77                 WITH p_file = p_file         78                 VIA SELECTION-SCREEN         79                 AND RETURN.         80              81         IMPORT data TO  FROM MEMORY ID 'DATA'.      >>>>>         FREE MEMORY ID 'DATA'.         83       ELSE.         84         MESSAGE e029.         85       ENDIF.         86              87              88     ************************************************************************         89     *                        FIN DE SELECTION         90     ************************************************************************           Please help me out,  Your inputs will be helpufl   Thanks,  AKREM

2 REPLIES 2
Read only

arindam_m
Active Contributor
0 Likes
906

Hi,

When you IMPORT from MEMORY ID the variable should match the TYPE of the data saved in that location so there is a length mismatch in your case.

Cheers,

Arindam

Read only

Former Member
0 Likes
906

This message was moderated.